Each agent requires a separate log file to write informational or diagnostic messages during execution. The number and type of messages written depends on the value specified on the CAUNIDEBUG and CAUNITRACE parameters, covered later in this section. Since there are two cooperating agents, two additional DD statements must be added to the CA OPS/MVS started task procedure for the log files. The ddnames are as follows:
|
DDname |
Description |
|---|---|
|
ENVFILE |
Points to the CCS for z/OS ENVFILE, typically found in the CCS for z/OS SCRLIB data set |
|
OPSALOG |
The log file of the main agent |
|
OPSBLOG |
The log file of the secondary agent |
|
SYSTCPD |
Points to the TCP/IP profile data set |
The following are the ddnames associated with the STDERR and STDOUT files for the two agents. These files are redirected at agent initialization because the two agents may otherwise overwrite the STDERR and STDOUT files of each other:
|
DDname |
Description |
|---|---|
|
OPSAERR |
Redirected STDERR DD of the primary agent |
|
OPSBERR |
Redirected STDERR DD of the secondary agent |
|
OPSAOUT |
Redirected STDOUT DD of the primary agent |
|
OPSBOUT |
Redirected STDOUT DD of the secondary agent. |
|
CEEDUMP |
Dump data set for the C language Environment. |
Note: If CA OPS/MVS is started with SUB=MSTR specified, then the data sets described above must be pre-allocated as permanent data sets using the CA OPS/MVS CCLXCNTL(ALLOCAWS) JCL. In addition, dynamically allocate the data sets using the CA OPS/MVS initialization REXX EXEC (usually OPSSPA00). If SUB=MSTR is not specified, then the DD can specify SYSOUT instead of a DSN specification.
In addition to the files listed in the preceding tables, the CA OPS/MVS started task procedure must include the following APF authorized data sets, concatenated to the STEPLIB DD, unless they are defined as LINKLST data sets:
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|