Previous Topic: Configuring Your ProductNext Topic: Step 2: Allocate the PMO/XSYS Control File (Optional)


Parameters to Specify at Installation Time

There are several different groups of parameters that you need to consider:

  1. The first set of parameters concerns basic CA PMO operation. Specify the following parameters:
    CPUCOST=monetary cost 
    EXCPCOST=monetary cost 
    USERCOST=monetary cost 
    MONEYSYM=monetary symbol 
    EXCPCPU=microseconds per EXCP 
    SVCCPU=CPU time 
    LLA=interface option 
    OPERMSG=LLA refresh option 
    REFDELAY=time 
    SYSOUT=report destination 
    RPTDSN=data set name,VOL=volser
    

    Notes:

  2. Specify the following parameter:
    LLAPRMLB=data set name
    
  3. To activate the CA PMO cross-system communication option to propagate locally detected library changes to all systems in the PMOplex, you will need to consider XCF and the control file. XCF may be used to send update information to other PMO systems on the same sysplex. The control file may be used to send update information to other PMO systems that are on different sysplexes.

    For XCF:

    XCFGROUP=group name
    XCFMEMBR=member name
    

    Specifying these values causes PMO to automatically start the PMO/XCF Enhanced Data Transmission component. It causes CA PMO to communicate directory entry update information to each PMO defined within the group. All PMO systems within the sysplex are defined within the same group. Each PMO system has a unique member name. When an update occurs, PMO communicates the update to all other members of the group. Default: None

    For the control file, the parameter is:

    XSYS= (sysa, sysb, sysc, 
    

    etc

    )

    Specifying values in this parameter causes CA PMO to automatically start the PMO/XSYS component. It causes CA PMO to communicate directory entry update information to each system defined on the XSYS= parameter. Default: None

    For both XCF and the control file:

    XSYSCOMM=(PMO,ALL)
    

    A value of ALL tells CA PMO to communicate information about all library updates. A value of PMO tells CA PMO to communicate library update information only about eligible libraries and libraries being managed by CA PMO Default: ALL

    For more information, see Determine the Multiple System Communication Path.

  4. By default, CA PMO runs in ACTIVE mode. You probably will want to accept this default. However, if desired, you can cause CA PMO to run in PASSIVE mode by specifying:
    MODE=PASSIVE
    

    Note: PASSIVE mode causes CA PMO to keep statistics as if it were optimizing directory searches, but it will not actually perform this function.

  5. The next set of parameters addresses compatibility with the following products:

    If your site runs any of these products, you must specify values for one or more of the parameters listed in the following sample:

    DESIZE=directory entry size 
    JES3ALLC=allocation option 
    PANEXEC=co-exist option 
    ROSCOE=co-exist option 
    TOPSECRT=co-exist option
    

    For more information, see the chapters "Using Parameters" and "Compatibility with Other Products" in the CA PMO Systems Programmer Guide.

  6. By default, CA PMO automatically decides what private libraries to manage, and it manages these libraries in hash tables only. Be sure that LLA is not managing any private libraries.

    If you wish, you may restrict CA PMO management of private libraries by specifying the INCLAUTO or EXCLAUTO parameters. For details on these parameters, see the chapter "Using Parameters" in the Systems Programmer Guide.

    The EXCLAUTO parameter prohibits CA PMO from managing certain libraries:

    EXCLAUTO=data set name,VOL=volser
    

    The INCLAUTO parameter defines a set of private libraries that CA PMO can manage automatically:

    INCLAUTO=data set name,VOL=volser
    

    Note: Specify either INCLAUTO or EXCLAUTO, not both.

  7. If you have a severe paging problem on your system, you may want to prevent CA PMO from automatically selecting any private libraries for management. If this is the case, specify:
    EXCLAUTO=*
    

    If you specify EXCLAUTO=*, you must specify which private libraries CA PMO will manage with INCLPRVT parameter statements:

    INCLPRVT=data set name,VOL=volser
    

    In the future, if you want CA PMO to manage additional libraries, you can refer to the PMOMON D9 display. This display provides a list of good candidates for management.

    Note: CA PMO does not automatically include any CA Panexec libraries.

  8. The DESERV exit installation is by default set to NO. This exit is installed during CA PMO initialization and allows CA PMO to intercept directory requests issued against the LNKLST concatenation when a PDSE library is present in the LNKLST.
  9. BLDLTRIM is by default set to NO. This parameter activates the CA PMO optimization enhancements associated with trimming DEB chains in the BLDL exit.