Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
GETE: Get ESD data z/OS MVS Program Management: Advanced Facilities SA23-1392-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
GETE returns data from ESD items. GETE must be used on a bound workmod. Four optional parameters allow you to specify selection criteria for the ESD items to be returned: section name, ESD record type, offset in the section or module, and symbol name. Only ESD records that meet all of the selection criteria will be returned. Multiple selection criteria can be specified to retrieve exactly the records you need. The syntax of the GETE call is:
Processing notesThe
binder returns ESD records that meet the selection criteria
specified on the call:
Note: Processing of the ESD
records returned by a GETE call should
not make assumptions about the order of the returned ESD records.
For example, such processing should not assume that LD type ESD records
are returned in the order of their offsets in the section.
The CURSOR value identifies an index into the requested ESD data beginning with 0 for the first ESD. The ESD buffer formats defined in Binder API buffer formats contain an entry length field in their headers. Multiplying the cursor value by the entry length provides a byte offset into the data. CURSOR is an input and output parameter. On input to the service, the cursor specifies the first record to return. On exit from the service, it is updated to the index of the next sequential ESD if not all data has yet been retrieved. The binder will typically return multiple entries in a single call, depending on the size of the buffer. Data is reformatted, if necessary, to conform to the version identified in the caller's buffer. The COUNT parameter is set to the number of records actually returned in the buffer. The ESD buffer formats defined in Binder API buffer formats contain a record length field in their headers giving the length of each ESD record. This provides a way for the caller to index through the returned records or to access a specific record in the returned data buffer. In some cases where OFFSET is specified and the parameter list is version 6 or less, return code 0 and reason code 0 will be returned on an end-of-data condition. The version 7 API call will always return return code 4 and reason code 83000800 on an end-of-data condition, while the COUNT may be non-zero indicating that data was returned. Return and reason codesThe common binder API reason codes are shown in Table 1.
Parameter listIf your program does not use the IEWBIND macro, place the address of the GETE parameter list in general purpose register 1.
Note: X'80000000' must be added to either
the COUNT parameter
(for Version 1) or the CLASS parameter (for Version 2 or higher).
|
Copyright IBM Corporation 1990, 2014
|