You can define multiple instances to execute a test copy of CA 7, separate job scheduling and control by customer or internal systems, or applying and testing maintenance before introducing into the production environment. The flexibility exists for CA7ONL and ICOM, but anything that is set up using the CAIRIM processes can be restricted, as only one copy of the CA 7 SVC and SMF exits exist in an LPAR.
Follow these steps:
U7GEN macro
Add an INSTANCE= keyword as follows: INSTANCE=CA74
U7PARMS macro
If you have a TARGET= keyword, do not change it. If you do not have one, code one using the DSN prefix of your production target libraries (CAL2LOAD, CAL2HELP, CAL2SRC, and so forth).
Add/change the NODE= data set name prefix to one different from your production prefix. For example: NODE='CAI.CA74'
If you have a VSAM= keyword, change the data set name prefix to one different from your production prefix. For example: VSAM='CAI.CA74.VSAM'
U7PNAMES macro
If you want to generate another set of JCL procedures automatically, add/change the U7PNAMES macro with a different prefix. For example: 'U7PNAMES PREFIX=CA74'
U7IFACE macro
Add/change the VTAM= keyword to specify a different application ID for this instance. For example: 'U7IFACE VTAM=(CA74)'
U7VOL and U7SPACE macros
If you want to change the DASD packs or sizes of the instance set, you can use these macros to change those settings.
CA07N010 - Allocates instance copy files
CA07N030 - Allocate / initialize instance files
Copy the VTAM definition members from the new JCLLIB to your system VTAMLST library. Copy member CA7VTAM renaming it to CA7VTAM4. Copy member CA7ISPF renaming it CA7ISPF4. Vary these active before you can use the new instance of CA WA CA 7 Edition (that is, V NET,ACT,ID=CA7VTAM4).
After the previous steps have been performed, run CAIRIM to add this tracking instance to the CA WA CA 7 Edition system environment. Run CAIRIM on every LPAR hosting an ICOM for the instance. This example assumes that the CA WA CA 7 Edition system environment has already been created with a GLOBAL INIT statement. When CAIRIM runs with the following System Configuration File statement, the CA74 instance is added with an alias of SYS4:
ADD CA74 ALIAS(SYS4)
If the instance is added successfully, the following messages are issued:
To run the new instance, you need separate PROCs and initialization file. You can use the members in the new version of JCLLIB created in the preceding second step. Run job CA07N020 from the new JCLLIB to copy them to a system or user PROCLIB.
Following is a summary of the differences between production and CA74 CA WA CA 7 Edition JCL procedures and options.
Code the SVCNO statement of the new initialization file as follows: SVCNO,SASSVC=YES,CA7=CA74
On the CA74 ICOM PROC, set the CA7= PROC variable to CA7=',CA7=CA74'. Note the leading comma.
On the CA74 TRAILER PROC (or through a PROC variable override), set the CA7= PROC variable to CA7='CA7=CA74,'. Note the trailing comma. If you are executing a test trailer step without using a JCL procedure, add 'CA7=CA74' to the EXEC statement PARM= string.
On the CA74 U7SVC PROC (or through a PROC variable override), set the CA7= PROC variable to CA7='CA7=CA74;'. Note the trailing semicolon. If you are executing a test U7SVC step without using a JCL procedure, add 'CA7=CA74;' at the beginning of the EXEC statement PARM= string.
If you want to use the Batch Card Load Program (SASSBCLP) to run under CA74, add a 'CA7=CA74' parameter to the EXEC statement PARM= string.
If you want the BTI Program (SASSBSTR) to point to instance CA74, add a 'CA7=CA74' parameter to the EXEC statement PARM= string.
If you want to submit cross-platform jobs from this system, tailor the associated CA7XTRK Cross-Platform Tracker to route the cross-platform feedback to that CA 7 instance. Add 'CA74' as the second positional value in the EXEC statement PARM= string.
If you want to use the interface with CAICCI to communicate with this system, specify 'CA74' as the 'CA-7 SSCT Name' in the invocation. The CAICCI Interface can be invoked from batch, REXX, and program-to-program modes. For the specifics on how to specify the instance name, see the Interface Reference Guide. Also, while the instance name is the default identifier for the CA WA CA 7 Edition CAICCI terminal that can be overridden in the initialization file.
|
PROC Name |
Program Executed |
|---|---|
|
CA7BTI |
SASSBSTR |
|
CA7ICOM |
SASSICOM |
|
CA7TRLR |
SASSTRLR |
|
CA7SVC |
U7SVC |
|
(none) |
SASSBCLP |
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|