Skip to Content

Cloud Data Sets considerations

Review this topic to learn more about Cloud Data Sets limitations.

Expiration considerations

The expiration of Cloud Data Sets is done by the BMC AMI Cloud life cycle process. To configure the life cycle JCL, see Working with BMC AMI Cloud life cycle.

Related topic

Cloud Data Sets

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. 
  • Multi-volume data sets are not supported. Multi-volume is not allowed, size limitation is dependent on the block size (32k is 120GB, 64K is 244GB, and 256K is 976GB).
  • Data set tape stacking is tolerated. File sequence is set to 1 regardless of what is specified in the JCL. 
  • Data set concatenation is not supported. 
  • 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.
  • Multiple CDS environments in the same LPAR are not supported. 
  • Creating temporary data sets on CDS is not supported. 
  • Broadcom CA-Disk Backup and Restore and IBM DFSMShsm are not supported.
  • IBM EXCPVR is not supported.

  • 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*

BMC AMI Cloud Data and BMC AMI Cloud Vault 4.1