In DFSMS V1.7, the direction of extending DFSMSrmm™ to the enterprise continues. This Technote provides a brief overview.
DFSMSrmm enterprise enablement
DFSMSrmm started to expand to the enterprise in z/OS® 1.6, first with enabling an RMM z/OS client, and by adding the RMM class library for use of the RMM API from object-oriented languages. You could use the high-level language application programming interface from C/C++ and Java™ (using the JNI) code running on the same z/OS system as the DFSMSrmm subsystem. A series of calls to the application programming interface were necessary to run the subcommand and to receive the output.
In DFSMS V1.7, the direction of extending DFSMSrmm to the enterprise continues. Extending DFSMSrmm to the enterprise is being accomplished through enabling the object-oriented interface to the RMM API to be used via Web Services and creating a plug-in adapter for use with SNIA SMI-S CIMOM. For more information about the SNIA SMI-S standards, visit:
With z/OS V1R7 and the DFSMSrmm enterprise enablement enhancement, you can use the high-level language application programming interface as a Web service. This enables the API to be used from any system or platform that can run Java, C++, or any language that supports the Web services standards. Now it is as though the high-level language application programming interface is available as a locally callable program. A single call to the application programming interface to run a subcommand and receive all of the output is all that is needed. The Web service is provided as a programming interface so other applications that need tape management services can use RMM. The CIM agent support exploits this to access RMM from anywhere.
A sample Java Web service application, rmmSampleWSClient.java, is located in /usr/lpp/dfsms/rmm/. The sample code shows how the application programming interface can be used via a Web service. For further information, see:
- DFSMSrmm Application Programming Interface, SC26-7403
- DFSMSrmm Implementation and Customization Guide, SC26-7405
This material has not been submitted to any formal IBM test and is published AS IS. It has not been the subject of rigorous review. IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a client responsibility and depends upon the client's ability to evaluate and integrate them into the client's operational environment.