The topics in this section describe the manual tasks that you perform when you are not deploying your product using CA CSM.
In a deployment, the SMP/E target libraries are copied to the target system. The CAL2JCL member AL2IDPL1 can be used to create an IEBCOPY physically sequential file suitable for sending to another system using methods such as shared DASD, a network transmission through JES, or FTP.
See the comments within the JCL to customize the data sets to be copied and the names on the installation site. Name the output files so that they can be sent to the target site.
After this job has executed, send to the files to the target site. The method of moving the file to the target system is left up to the site. Various ways are available to send the data: FTP, data transmission products such as CA XCOM, IBM NDM, TSO XMIT and more.
To restore the target libraries, use the CAL2JCL member AL2IDPL2. This job takes the physical sequential files and restores the PDS target files that are used in the configuration process. After these PDS files are restored, configuration for that site and specific instance of CA 7 can proceed.
Consider replicating some libraries, like CAL2JCL and CAL2OPTN, per CA 7 instance (CA71 compared to CA72 compared to CA73). The load module library and selected other files can be shared between CA 7 instances when nothing site- or instance- specific is placed in those libraries. Before you start the configuration, now is a good time to evaluate the CA 7 topology for the sysplex/LPAR.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|