IOPERDEV SAP (Informix Chunk I/O Statistics - I/O Per Device) Structure details
Description: Informix Chunk I/O Statistics - I/O Per Device
Structure field list including key, data, relationships and ABAP select examples
IOPERDEV is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Informix Chunk I/O Statistics - I/O Per Device" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_IOPERDEV TYPE IOPERDEV.
The IOPERDEV table consists of various fields, each holding specific information or linking keys about Informix Chunk I/O Statistics - I/O Per Device data available in SAP. These include PCHUNK (Informix Chunk I/O Statistics - Chunk Number), MIRRORED (Mirrored Chunk), DBSNAME (DBSpace Name), READS (Total Number of Disk Reads).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP IOPERDEV structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| FNAME | Informix Chunk I/O Statistics - Path Name | INFDEVNAME | CHAR | 50 | CHAR50 | ||||
| PCHUNK | Informix Chunk I/O Statistics - Chunk Number | CHUNK | INT4 | 10 | SINT4_NOS | ||||
| MIRRORED | Mirrored Chunk | MIRRORED | CHAR | 1 | CHAR1 | ||||
| DBSNAME | DBSpace Name | DBSNAME | CHAR | 18 | CHAR18 | ||||
| READS | Total Number of Disk Reads | INFIOREADS | INT4 | 10 | SINT4_NOS | ||||
| WRITES | Total Number of Disk Writes | INFIOWRITE | INT4 | 10 | SINT4_NOS | ||||
| PGREADS_S | Avg. pages read per second | STUIPGR_S | DEC | 8(2) | STUIPGIO_S | ||||
| PAGESREAD | Total Number of Disk Pages Read | INFIOPREAD | INT4 | 10 | SINT4_NOS | ||||
| PAGESWRITE | Total Number of Disk Pages Written | INFIOPWRIT | INT4 | 10 | SINT4_NOS | ||||
| PGWRITES_S | Avg. pages written per second | STUIPGW_S | DEC | 8(2) | STUIPGIO_S |
| Key field | Non-key field |
How do I retrieve data from SAP structure IOPERDEV using ABAP code?
As IOPERDEV is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on IOPERDEV as there is no data to select.How to access SAP table IOPERDEV
Within an ECC or HANA version of SAP you can also view further information about IOPERDEV and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects