Method 1: Write directly to cloud

This method will intercept the data while it is being written to tape or DASD and write it to a cloud server within the same job step.

To write data directly to a cloud server, filter criteria must be specified to inform Cloud Connector which cloud to use to back up this data. From the Main Menu, a filter can be defined through Option 1 (Cloud Connector Settings – Parmlib Options), then by choosing Option 4 (Backup Filter Criteria). Filter criteria can be defined based on a data set name, esoteric unit or SMS storage class.

This method may cause your production batch process to be elongated while waiting for cloud writes to occur, depending on your cloud transmission speeds. Clouds defined within your data center (private clouds) will generally be very fast, and external clouds (public clouds requiring transmissions outside your data center) may be slow.

The one drawback to this method is that if the cloud server transmission is interrupted in any way, Cloud Connector has no way of restarting the "cloud write" function. If Cloud Connector detects a transmission error, one of these actions will occur:
  • If the "Abend on Errors" option is set to YES, the job will abend.
  • If the "Abend on Errors" option is set to NO, the job will continue with no data written to the cloud.