Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Parameter-to-DSECT mapping z/OS Communications Server: SNA Programmer's LU 6.2 Guide SC27-3669-00 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The following tables illustrate which fields of the RPL DSECT (IFGRPL) and the RPL extension DSECT (ISTRPL6X) correspond to the RPL and RPL extension field names used in this book. They show the RPL fields that are meaningful for an RPL used for an APPCCMD macroinstruction. Table 1 shows the DSECT labels for the RPL fields used for LU 6.2 support. For a complete description of the RPL DSECT (IFGRPL), refer to z/OS Communications Server: SNA Programming. This manual shows the RPL extension fields in which the application program passes information to and receives information from VTAM®, along with the corresponding DSECT label in the ISTRPL6X DSECT. For the actual storage layout of the RPL extension, refer to z/OS Communications Server: SNA Programmer's LU 6.2 Reference. The figure shows the DSECT label for each field, followed by the symbolic name of the field (if any) in parentheses. Blank fields in the figure indicate fields that should not be used or examined by application programs. Table 2 shows the RPL extension fields that are returned for the ATTN exit.
|
Copyright IBM Corporation 1990, 2014
|