Package Ship Facility › How to Enable Backout and Shipment for Natural Objects

How to Enable Backout and Shipment for Natural Objects

As a CA Endevor SCM administrator, you can enable the shipment of Natural objects to a remote site and the backout of those objects from the remote site. This functionality is enabled by the Post-Ship Script feature, which lets you ship job steps (scripts) to the remote destination for conditional execution. In this case, the scripts are needed to write the Natural objects to the remote Natural library after shipment.

The following graphic shows how you enable backout and shipment for Natural objects:

Complete the following procedures to enable backout and shipment of Natural Objects:

1. Review the considerations for the backout and shipment of Natural objects.
2. Configure your C1DEFLTS table to enable the Post-Ship Script feature. This involves reviewing your C1DEFLTS table and updating the table if the feature is not already enabled.
3. Update your Move processors to add steps that will build your script output data sets for shipment and create backout records to enable backout of these data sets. The model processor steps enable package processing for shipment and backout, store unloaded Natural objects into PDS format, and put remote Natload JCL into the NATCMD library.
4. Define mapping rules for the data sets that contain your script files. For these script data sets, you always define the mapping rule remote destination as: (SCRIPT-FILE).
5. (Optionally) Create a Destination Configuration member to define unique symbol values for each package ship destination. This member is only required if you want the symbols in your script data sets to resolve to values that are based on the destination.
6. Create script steps that can be conditionally executed at the remote destination, based on the existence of a script data set in the shipment. The model script creates a sequential file from the NATCMD file PDS members being shipped and then loads the shipped Natural objects to their Natural libraries.

Backout and Shipment of Natural Objects

The shipment of Natural objects to a remote site and the backout of those objects from the remote site is enabled by the Post-Ship Script feature. This feature lets you ship job steps (scripts) to the remote destination for conditional execution. The scripts write the Natural objects to the remote Natural library after shipment.

For Natural objects, backout and shipment has the following limitations:

• The Natural objects that you plan to ship must have valid PDS names. The Move processor for Natural requires steps that write members to two PDSs, using the CA Endevor SCM element name as the member name. Therefore, all objects being shipped must have names that will be valid as member names of a PDS.
• Each package that you plan to ship can contain a maximum of about 250 elements. This limitation is due to a Natural utility requirement that sequential files be used. At the remote site, the script file is submitted to the internal reader as a single job that consists of sequential job steps created from the PDS members. This job uses the same job card as all other jobs executed at the remote location. Thus, the number of job steps limits the shipments to approximately 250 elements per package.

  To avoid the 250 element per package limitation, you can make each member its own job, by including the job card in the JCL written to the script file member.

• Delete of Natural objects is not supported. The backout of shipped objects is possible by shipping complementary files (a destination option):
  • Submission of the CRJOB file at the remote location (CHJOB for LOCAL shipments) will restore pre-existing Natural objects to their state prior to shipment.
  • Deletes of new objects at remote locations as part of backout processing is not handled by this process.