

Using Parameters › The Purpose of the Parameters
The Purpose of the Parameters
The CA PMO parameters control various aspects of product behavior. The following list briefly summarizes CA PMO parameters by function:
- CA PMO calculations of the cost of user time, CPU time, and EXCPs involve the following parameters: CPUCOST, EXCPCPU, EXCPCOST, MONEYSYM, SVCCPU, and USERCOST.
- The LNKLST and private libraries that CA PMO manages, and those it does not manage, are affected by the following parameters: EXCLAUTO, EXCLLNK, INCLAUTO, INCLLNK, INCLPRVT, NUMCANDS, and NUMADDED.
- CA PMO compatibility with other products is determined by the DESIZE, DFDSS, FDR, JES3ALLC, PANEXEC, ROSCOE, and TOPSECRT parameters.
- The CA PMO interface to the LLA is controlled by the LLA, LLAPRMLB, OPERMSG, and REFDELAY parameters.
- The way CA PMO and PMO/XSYS communicate across systems is controlled by the XSYS, XSYSCOMM, and CYCLE parameters.
- Offline reports are affected by the RPTDSN, EXCLREPT, and SYSOUT parameters.
- The managed list is controlled with the FIX, MLSIZE, and RETNF parameters.
- CA PMO statistical measurements are affected by the INTVL and RESETPK parameters.
- Whether CA PMO runs in active or passive mode is determined by the MODE parameter.
- Whether CA PMO manages LNKLST requests for non-PDSE type libraries when a PDSE library resides in the LNKLST concatenation is determined by the value of the DESERV parameter.
- Whether CA PMO manages partitioned data sets in a LNKLST when a PDSE is present in the concatenation is determined by the value of the DESERV parameter.
- Whether CA PMO manages private library requests for non-PDSE type libraries when a PDSE library resides in the library concatenation is determined by the value of the DESERV parameter.
Copyright © 2011 CA.
All rights reserved.
 
|
|