Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
PDSE directory entry returned by DESERV (SMDE data area) z/OS MVS Program Management: Advanced Facilities SA23-1392-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This section describes the format of a PDSE entry returned by the DESERV macro. This is the SMDE data area, which is mapped by the IGWSMDE mapping macro. The formats shown here are specific to PDSE program libraries. The system managed directory entry (SMDE) can represent either
a program object in a PDSE or a load module in a PDS. The SMDE also
represents both primary (member) entries and aliases. The SMDE consists
of several sections that appear depending on the type of directory
entry being provided:
The basic SMDE format is shown in Table 1.
Table 2 through Table 7 shows the optional SMDE_SECTIONS, or extensions to the SMDE.
If the SMDE represents a directory entry for a program (either a load module or a program object) the program's attributes are defined by the PMAR structure. The PMAR is a subfield of the SMDE and its offset is defined by the field SMDE_PMAR_OFF. For the PMAR structure and mapping, see IEWPMAR in z/OS MVS™ Data Areas in z/OS® Internet Library at http://www.ibm.com/systems/z/os/zos/bkserv/. If the SMDE represents a data member of a PDS or a PDSE, the SMDE_USRD_OFF field indicates the offset into the SMDE for the user data of the directory entry. |
Copyright IBM Corporation 1990, 2014
|