Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Managing system-managed tape library volumes: EDGLCSUX z/OS DFSMSrmm Implementation and Customization Guide SC23-6874-00 |
|||||||||||
DFSMSrmm uses the OAM installation exits CBRUXCUA, CBRUXEJC, CBRUXENT, and CBRUXVNL as described in Table 1 to manage the tape volumes defined in system-managed tape libraries. DFSMSrmm supplies Assembler source code for these installation exits, which is installed on your system as modules CBRUXCUA, CBRUXEJC, CBRUXENT, and CBRUXVNL. The sample CBRUXEJC, CBRUXENT, and CBRUXVNL exits show how to call the DFSMSrmm API. The use of the API is optional and must be enabled by the customer. The customer must also write code to process the results of the call to the API. The sample code shows how to list the volume being processed by OAM using the DFSMSrmm API. You can modify the source code to include your own function or merge with another product's supplied code. DFSMSrmm uses EDGLCSUX to support these functions:
The OAM exits that DFSMSrmm supplies call EDGLCSUX, the DFSMSrmm program that supports the OAM interface. EDGLCSUX is a callable program interface to DFSMSrmm that you can use only from the OAM installation exits. If you do not have a license for DFSMSrmm, the DFSMSrmm OAM exits set a return code of 16, telling OAM to never call the exit again. For information on licensing, see Enabling DFSMSrmm. If you are licensed for DFSMSrmm, and you have performed some of the installation steps, but have not added EDGSSSI to the IEFSSNxx member of parmlib, or have not started the DFSMSrmm procedure, DFSMSrmm sets return code zero, allowing all OAM requests to be accepted. Once you have performed the installation steps, but do not start the DFSMSrmm subsystem, the OAM exits set a return code 8 and fail all requests. |
Copyright IBM Corporation 1990, 2014
|