Cloud Data Sets considerations
Related topics
Cloud Data Sets supports the use of special dates. For more details on how they are handled by the life cycle process, see Cloud data sets special dates support.
Known limitations
- The DCB parameter TRTCH=COMP is ignored. Compression is controlled internally by CDS, using the compression.type parameter in the m9cdswk properties file.
An IEC706I TRTCH IGNORED message will be issued to the job log. - DFDSS write is fully supported. For read, use the M9CLDDSS JCL provided in the BMC AMI Cloud SAMPLIB data set.
- Data set tape stacking is tolerated. File sequence is set to 1 regardless of what is specified in the JCL.
- A single Cloud data sets environment working with multiple buckets is not supported.
- Applications using QSAM/BSAM which initiate the rewind, backspace, point or note calls are not supported and are expected to fail.
- You can allocate up to 360 versions with the same CDS name.
- CYCLE based expiration is not supported.
- Creating temporary data sets on CDS is not supported.
- Broadcom CA-Disk Backup and Restore and IBM DFSMShsm are not supported.
- Unprotected data sets are not supported. All CDSs must be defined to SAF under the DATASET class.
- IBM EXCPVR is not supported.
- Messages with MSGIDs IEF233D and IEF455D will not roll off if your CONSOLE setting uses DEL=RD. Consider deleting these messages with one of your automation tools.
- DISP=MOD is not supported. If specified, the job fails with a ZM9WJ003E Unsupported disposition message.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*