Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Using save-area module linkage conventions—Subarea z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures GC27-3667-00 |
|||||||||
VTAM® traces the flow of
the execution of three VTAM components,
SSCP, PUS, and LUS, by saving the work areas of modules in these components.
The addresses of the module work areas are stored in either of these
control blocks:
The NCSPL or RUPE work area contains the work and save-areas for each module invoked for the command that the NCSPL or RUPE represents. The module work and save-areas provide status information that pertains to both the processing of that command and any interruptions in the processing. This status information includes a record of which modules were entered, which modules returned to their callers, and which modules returned with a return code. Each module save-area contains the 4th, 5th, 7th, and 8th characters of the module name and the register 15 value that includes a pointer to the last module called by this module. If this address is not in the dump, the module can be obtained by comparing the address to the addresses in the VTAM module list pointed to by ATCMDLST out of the ATCVT. See VTAM load module list. The high-order byte of the register 15 save-area also indicates the status of the last module called. (In 31-bit mode the address fills register 15, causing the status to overlay the high-order byte of the address in the register 15 save-area.)
Figure 1 is an example of what the NCSPL or RUPE work area might contain for modules invoked for a VTAM process using save-area module linkage conventions. Using this convention, the save-area contains a 4-byte module identifier, such as ACRT, at the location pointed to by register 13 for each entry in the chain. Figure 1. Save-area module linkage conventions—subarea
|
Copyright IBM Corporation 1990, 2014
|