These topics describe the manual tasks that you perform when you are not configuring your product using CA CSM. A configure without CA CSM checklist is provided.
The SMP target data sets are now copied to the target system where CA WA CA 7 Edition executes. Some target libraries can be used across multiple CA 7 instances. Consider separating some data sets by instance identifier because these contain JCL/procedures for CA 7 instances. Consider duplicating the following SMP/E libraries:
This library contains sample JCL members for various functions, such as backup, recovery, and reporting.
This library contains sample option members. The library also has parameters, security setup, and user exits source.
This library contains sample CLIST CA7CLIST that sometimes requires a customization that is based on your system needs.
This library contains sample email templates. You can use this library or can establish a separate data set of your own. The data set is referenced in the CA7ONL initialization file EMAIL statement.
This library contains sample Service Desk Templates. You can use this library or can establish a separate data set of your own. The data set is referenced in the CA CAISDI/els parameters.
This library contains sample CA Datacom SQL Queries.
If you are executing CA IAS, consider duplicating the CIASJCL and CIASOPTN to set up different agent destinations and files to go with each instance of CA 7.
The other SMP/E target libraries can be shared between multiple CA 7 instances on a system. The other library, the CA 7 JCLLIB, is created by executing the SYSGEN process. This should be separated by CA 7 instance, as this contains the specific instance information.
If you are executing multiple instances within the sysplex, duplicate these libraries now. Identify the instance associated with the library. In these topics, we refer only to the SMP/E DD definition name (like CAL2JCL or CAL2OPTN) or the JCLLIB that is produced as a result of the SYGEN process.
To configure, you:
If you are installing for the first time or if you are upgrading and want to try out features of the new version before using your production database, you can:
Important! If you are upgrading to CA 7 Version 12.0, you must create a logical database containing your production scheduling data before you can begin using the product in production. Information about this process is discussed in Database Conversion.
Note: If you are upgrading CA 7 from r11.3, you can use the L2OPTS file from r11.3 without changes. The CAIRIM process can still invoke the CA 7 r11.3 load modules.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|