IBM z/OS DFSMS Cloud Data Manager (DFSMScdm) 1.2 became generally available on 6 December 2024. Packed with powerful new features, it enhances z/OS cloud storage strategies by enabling scalable sharing of z/OS data across other sysplexes and hybrid cloud applications in other environments. With DFSMScdm you can:
· Seamlessly transfer data to and from cloud storage at scale
· Leverage hybrid cloud environments to optimize storage
· Connect to any S3-capable cloud provider without requiring additional server infrastructure
DFSMScdm makes it easier to share data for hybrid cloud applications by using a z/OS started task that can process up to 32 cloud upload/download requests simultaneously. The cloud requests are initiated by DFSMScdm TSO commands and can be controlled and monitored by authorized DFSMScdm users or administrators. DFSMScdm is built on the IBM z/OS DFSMSdfp Cloud Data Access (CDA) technology.
IBM DFSMS includes a utility called GDKUTIL, a JCL-based tool built on CDA for batch access to cloud objects. It allows users to upload or download sequential datasets to and from cloud storage. GDKUTIL is ideal for initial testing and experimentation with cloud data transfers in z/OS environments.
However, GDKUTIL has certain limitations. It is single-threaded, making it unsuitable for large-scale data transfers. Additionally, it processes requests through the user’s address space rather than leveraging a started task. As a result, it is best suited for smaller, less complex use cases rather than high-volume, production-level cloud integrations.
DFSMScdm addresses these limitations by providing scalable access to cloud objects.
In this use case, we will show you how DFSMScdm 1.2 can help you develop multi-platform hybrid cloud applications that use z/OS data in conjunction with data from other platforms using the cloud as a secure and resilient intermediate storage medium.
Use case description
Portions of a hybrid cloud application run on non-z/OS systems and require daily updates of z/OS data. After the daily z/OS batch cycle is run, application data is extracted into sequential data sets and sent to the cloud. In this example, there are 100 sequential extract data sets created that need to be distributed to 100 different non-z/OS systems and to another z/OS sysplex.
1. Configure and start the DFSMScdm started task.
First, you configure your cloud provider for use with CDA. This component of DFSMS became available in z/OS 2.5. The documentation for this process can be found in the z/OS High Level Callable Services manual. Next define a RACF user ID to be used by the DFSMScdm started task for all its cloud requests. The third step is to authorize users to send requests to the DFSMScdm started task via the RACF FACILITY class.
Finally, start the DFSMScdm started task (STC), for example:
S CDMSTC.CDM,REUSASID=YES
2. Send daily application z/OS data sets to the cloud.
The following DFSMScdm command is used to send the 100 daily extract data sets to the cloud. The name of the cloud provider where we want to send the extracted data sets is SHRCLOUD1. This was configured in the CDA provider file. The container name that is used by z/OS and the other non-z/OS systems is App1shr. A data set name mask is used to specify the 100 z/OS sequential extract data sets. The cloud object name will be daily_from_ZOS-BRxxx where BRxxx is the 4th node of the z/OS data set name. Using the DFSMScdm &DSN variable and a node index value, the 4th node is used to construct the cloud object name. The data is converted to UTF-8 for use on other platforms.
CDMSEND -
CLOUD(SHRCLOUD1) -
CONTAINER(App1shr) -
DSN(APP1.DAILY.EXTRACT.BR*) –
OBJECT(daily_from_ZOS-&DSN(4) -
CONVERT_UTF8(YES)
3. Retrieve daily application files from the cloud to another z/OS sysplex.
The daily extract file in the cloud can also be used by other z/OS sysplexes where DFSMScdm 1.2 is installed. Using the CDMRET command, the cloud, container, and object name specified are the same as those on the CDMSEND command; however, each object is retrieved via an individual command. Since the z/OS data set names that were used on the CDMSEND do not exist on the other sysplex, the z/OS data sets will be allocated on the retrieving sysplex with the same z/OS metadata (space, LRECL, RECFM, DSORG) as they had on the sending sysplex. The CONVERT_UTF8 parameter converts from UTF-8 back to EBCDIC. The following example shows the CDMRET command for one of the data sets:
CDMRET -
CLOUD(SHRCLOUD1) -
CONTAINER(App1shr) -
DSN(APP1.DAILY.EXTRACT.BR*) –
OBJECT(daily_from_ZOS-BR001) -
CONVERT_UTF8(YES)
Summary
The ability to send and retrieve z/OS data to and from the cloud without additional virtual devices or external servers makes DFSMScdm 1.2 an important tool in your cloud storage strategy. DFSMScdm 1.2 offers a simple installation, a small footprint, and scalable flexibility, which is built on the continually enhanced CDA technology.
Adopting cloud storage strategies can reduce costs, but it shouldn’t come at the cost of losing data accessibility. With the new z/OS DFSMS Cloud Data Manager 1.2, cloud storage no longer means relinquishing control, availability, and accessibility of your critical data.
Want to learn more about DFSMScdm and other cloud storage solutions for z/OS? Join us for our webcast on 12 December at 11 AM Eastern Time (ET).
https://ibm-zcouncil.com/events/cloud-storage-dec-12/