Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Output z/OS DFSMSrmm Implementation and Customization Guide SC23-6874-00 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The DFSMSrmm control data set and OAM parameter list are updated depending on the type of processing performed. Register 15 contains the return code which indicates what processing should be performed next. Register 0 contains the reason code. Use the return code and the reason code to determine the processing that DFSMSrmm has been able to perform. Table 1 shows the return and reason codes that EDGLCSUX sets in register 15 and register 0.
Table 2 defines the return codes generated for each OAM function based on the reason codes set by DFSMSrmm in field LCSUP_LCSRS. The return code variables used in the table are defined in the OAM macros, CBRUXCPL, CBRUXEPL, CBRUXJPL, and CBRUXVNL. If the DFSMSrmm parmlib OPTION SMSTAPE(UPDATE(EXITS)) operand is not set or if DFSMSrmm is running in warning or record-only mode, the OAM return codes UXxFAIL are changed to UXxNOCHG.
|
Copyright IBM Corporation 1990, 2014
|