z/OS DFSMSrmm Implementation and Customization Guide
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 1. EDGLCSUX return and reason codes returned in register 15 and register 0
Return Code Reason Code Description
0 0 Processing successful. LCSUP_LCSRC contains the return code for OAM. LCSUP_LCSRS contains a reason code that provides information about DFSMSrmm processing. The reason codes are described by variables LCSUP_RS_xxxx listed in the EDGLCSUP macro.
0 1 Processing successful. LCSUP_LCSRC contains the return code for OAM.
0 2 Processing successful. DFSMSrmm is not licensed for use on this processor. LCSUP_LCSRC contains the return code 16 for OAM.
4 0 Processing not performed because the DFSMSrmm subsystem was not available. LCSUP_LCSRC contains the return code for OAM.
8 0 Processing not performed because there was a logic error during processing. LCSUP_LCSRC contains the return code for OAM.
12 Various reason codes set Processing is unsuccessful. The reason codes are described by variables LCSUP_RS_xxxx listed in the EDGLCSUP macro. The supplied exits set RC 8 for OAM to fail requests.

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.

Table 2. EDGLCSUX return and reason codes based on DFSMSrmm reason code setting
Reason Code Description Related Message Number Change Use Return Code Volume Entry Return Code Volume Eject Return Code Volume- Not in- Library
0 DFSMSrmm accepted request n/a UXCNOCHG or UXCCHG1 UXENOCHG or UXECHG1 UXJNOCHG or UXJCHG1 UXNNORML or UXNCHG1
LCSUP_RS_DEB Specified destination is not current library EDG8192I n/a UXEFAIL n/a n/a
LCSUP_RS_DUPLV Volume duplicates an existing logical volume EDG8183I n/a UXEFAIL n/a n/a
LCSUP_RS_DUPPV Volume duplicates an existing physical volume EDG8182I n/a UXEFAIL n/a n/a
LCSUP_RS_DUPSV The volume duplicates an existing stacked volume. EDG8181I UXCFAIL UXEFAIL UXJFAIL n/a
LCSUP_RS_IRK Volume rack number inconsistent EDG8189I UXCFAIL UXEFAIL UXJNOCHG n/a
LCSUP_RS_IVU User ID not valid for DFSMSrmm EDG8195I UXCFAIL UXEFAIL UXJNOCHG n/a
LCSUP_RS_NMV Volume not to be used with z/OS EDG8191I UXCFAIL UXEIGNOR UXJFAIL n/a
LCSUP_RS_NOTEXP Imported volume is not exported EDG8183I n/a UXEFAIL n/a n/a
LCSUP_RS_NRM Volume not defined in a manual tape library n/a UXCNOCHG UXENOCHG UXJNOCHG UXNNORML
LCSUP_RS_PBD Inconsistent parameter list EDG8190I UXCFAIL UXEFAIL UXJFAIL UXNFAIL
LCSUP_RS_PNI Volume matches to PRTITION, type NORMM, action IGNORE n/a UXCNOCHG UXEIGNOR Eject: UXJNOCHG, Export: UXJIGNOR n/a
LCSUP_RS_PRI Volume matches to PRTITION, type RMM, action IGNORE n/a UXCNOCHG UXEIGNOR Eject: UXJNOCHG, Export: UXJIGNOR n/a
LCSUP_RS_RIU Rack to match volser not available EDG8198I UXCFAIL UXEFAIL UXJNOCHG n/a
LCSUP_RS_RJP Undefined volume rejected by reject prefix EDG8193I 2 UXCFAIL UXEIGNOR Eject: n/a, Export: UXJIGNOR n/a
LCSUP_RS_RPX Retention period exceeds installation maximum EDG8196I UXCFAIL UXEFAIL UXJNOCHG n/a
LCSUP_RS_SCR Private to scratch status not permitted EDG8194I UXCFAIL UXEFAIL UXJFAIL n/a
LCSUP_RS_SMM Entry status and DFSMSrmm status of volume mismatch EDG8180I n/a UXENOCHG n/a n/a
Notes:
  1. When these conditions are true:
    • Status is private and no expiration date is supplied
    • Status is private and last read or write dates are lower than the DFSMSrmm equivalent dates
    • Status is scratch and owner information exists; the first 8 bytes are set to blanks
    • Volume entered into a system-managed tape library and DFSMSrmm has values for either storage group name, owner, or tape device selection information
  2. Not issued during entry processing.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014