Understanding the z/OS PAS JCL statements

specifies symbolic parameters for the z/OS PAS proc

For a detailed explanation of each parameter, see z/OS PAS library member.

specifies the program name (PGM=BBM9DA00)

A TIME parameter should be large enough to prevent the possibility of a timeout (use TIME=1440, if allowed).

The PARM subparameters are all symbolic and use the same values that are defined for the corresponding parameter in the proc statement. For a detailed explanation of each of these parameters, see z/OS PAS library member.

The REGION parameter is symbolic and uses the same value that is defined for the corresponding RGN parameter in the proc statement. (See Examples of the instructions in the BBILIB member BBMPAS for more information.)

defines a partitioned data set that contains the Extractor load modules

The partitioned data set must be an authorized library, such as hilevel.BBLINK.

This statement should be deleted if BBLINK was added to your system link list. For more information, see Manual customization.

specifies one or more data sets where the Extractor records data that was collected by the CPM submonitor

Do not define this statement if you are recording CPM data to SMF or if you are specifying the data set names on the REPORT Extractor control statement.

To manually customize the CMFCPMxx DD statements to point to your CPM data sets, remove the DUMMY parameter and specify the following statement for each data set that you want to be dynamically allocated during Extractor initialization:

//CMFCPMxx DD DISP=SHR,DSN=&BAVSHLQ..&SYSID..CMFCPMxx

In this statement, xx is a unique value for the allocated data set.

The //CMFCPMxx DD statements can be defined to write simultaneously to the same data sets as the //CMFIPMxx DD statements. If you used the Installation System to configure MainView for z/OS, these statements are defined dynamically, if required.

Specifying alternative data sets is optional; however, alternative data-set support is provided only if alternative data is specified.

For more information about the CPM submonitor, allocating CPM data sets, alternative data set support, and information about the REPORT Extractor control statement, see the CMF MONITOR documentation.

specifies one or more data sets where the Extractor records data that was collected by the IPM submonitor

Do not define this statement if you are recording IPM data to SMF or if you are specifying the data set names on the REPORT Extractor control statement.

To manually customize the CMFIPMxx DD statements to point to your IPM data sets, remove the DUMMY parameter and specify the following statement for each data set that you want dynamically allocated during Extractor initialization:

//CMFIPMxx DD DISP=SHR,DSN=&BAVSHLQ..&SYSID..CMFIPMxx

In this statement,xx is a unique value for the allocated data set.

The //CMFIPMxx DD statements can be defined to write simultaneously to the same data sets as the //CMFCPMxx DD statements. If you used the Installation System to configure MainView for z/OS, these statements are defined dynamically.

Specifying alternative data sets is optional; however, alternative data-set support is provided only if alternative data is specified.

For more information about the IPM submonitor, allocating IPM data sets, alternative data set support and information about the REPORT Extractor control statement, see the CMF MONITOR documentation.

is a required statement only if you want to use the security views, SERDEF, SERDEFD, and SERDEFL, to define security parameter definitions for CMF MONITOR and/or MainView for z/OS security resource calls

If specified, the data set name that is defined to the CAS proc BBSECURE statement must also be defined to the PAS proc BBSECURE statement. For information about creating the security data set, see Manual customization.

BMC Software recommends that you define a BBSECURE data set to the PAS proc; otherwise, your system must run with the default security calls that are made for CMF MONITOR or MainView for z/OS.

If you do not define a BBSECURE data set, you must either remove or comment out this statement from the PAS proc. An error results when the BBSECURE DD is present and there is no data set allocated.

The security resource definitions in the BBSECURE data set are used by the CAS and PAS to determine whether security checking should occur for system, product, view, or action access. Defining a BBSECURE data set is only one part of setting up security to function with your external security manager. For more information about customizing security, see Managing security for MainView products.

defines the view library containing all default views for CMF MONITOR or MainView for z/OS

For more information about this DD statement, see Using MainView products

defines a VSAM data set that contains:

• data set names for historical data sets, as defined by means of the DSLIST view For more information, see the CMF MONITOR documentation.

• user-defined workload definitions created through MainView for z/OS by means of the WKLIST view

This data set is allocated and initially loaded during the customization process.

defines up to 100 VSAM data sets that make up the regular historical database

For information about defining HISTDSnn DD statements, see Manual customization

The regular historical database is used for historical data support. For information about maintaining these data sets, see Managing historical data sets