z/OS PAS library member
z/OS PAS started task procedure statements
The following table lists the z/OS PAS started task procedure statements:
JCL statement | Description |
|---|---|
//procname PROC | This statement identifies the started task procedure and its parameters. You can override these parameters with the START command for the PAS, as described in Administering. |
//PAS EXEC | This statement references a program named BBM9DA00 that processes EXEC parameters and performs basic initialization tasks. You can use the PARM parameter to override the default parameter values that are specified with the PROC statement. The REGION parameter specifies the size of the private region that is required by the PAS. TIME=1440 defines unlimited processing time for the PAS. |
//STEPLIB DD | This statement defines the BBLINK load library, which contains load modules for all BMC AMI Ops products. The CAS requires some of these load modules; each product address space requires other modules. This statement should be deleted if BBLINK is added to your system link list. |
//CMFCPM xx DD | (BMC AMI Ops Monitor for CMF only) This statement specifies one or more data sets where the Extractor records data that is collected by the CPM monitor. 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 add the following statement for each data set that you want defined during Extractor initialization: //CMFCPMxx DD DISP=SHR,DSN=&BAVSHLQ..&SYSID..CMFOUTxx 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. During installation, these statements are dynamically defined, if required. Specifying alternate data sets is optional; however, alternate data set support is provided only if an alternate data set is specified. For more information about the CPM monitor, allocating CPM data sets, and alternate data set support, see Customizing-after-installation. For more information about the REPORT Extractor control statement, see Extractor-control-statements. |
//CMFIPM xx DD | (BMC AMI Ops Monitor for CMF only) This statement specifies one or more data sets where the Extractor records data that is collected by the IPM monitor. 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 add the following statement for each data set that you want defined during Extractor initialization: //CMFIPMxx DD DISP=SHR,DSN=&BAVSHLQ..&SYSID..CMFOUTxx 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. During instsallation, these statements are dynamically defined. Specifying alternate data sets is optional; however, alternate data set support is provided only if an alternate data set is specified. For more information about the IPM monitor, allocating IPM data sets, and alternate data set support, s ee Customizing-after-installation . For more information about the REPORT Extractor control statement, s ee Extractor-control-statements. |
//CMFDUMP DD | (BMC AMI Ops Monitor for CMF only) This statement defines a print data set for snapshot dumps. When a program fails in BMC AMI Ops Monitor for CMF, the abend is intercepted by an ESTAE routine, and a formatted dump of the failing component is printed. |
//CMFLOG DD | (BMC AMI Ops Monitor for CMF only) This statement defines an optional file that can direct the BMC AMI Ops Monitor for CMF Control Card Log to an alternative data set. When no CMFLOG DD statement is present, the data set for the Control Card Log is dynamically allocated and deallocated as needed. The CMFLOG data set allows for immediate inspection of messages, regardless of how long an Extractor job runs. Dynamic allocation is to the MSGCLASS that is specified on the JOB statement for batch jobs or to CLASS A for started tasks. |
//CMFMSG DD | (BMC AMI Ops Monitor for CMF only) This statement defines a print data set that contains non-initialization messages for the system. When no DD statement is present, the CMFMSG DD data set is dynamically allocated to SYSOUT class A. To print this data set, issue a MSGFREE command by using the MODIFY command. The data set is dynamically deallocated and printed, and a new allocation occurs immediately. |
//CMFXDSLG DD | (BMC AMI Ops Monitor for CMF only) This statement defines a print data set that contains XDS initialization messages and control cards. If this DD statement is not present, XDS messages are issued as WTO. |
//PARMLIB DD | (BMC AMI Ops Monitor for CMF only) This statement defines a partitioned data set that contains control statement members for the Extractor to read. This data set must be a fixed-block data set with a logical record length of 80, such as security hlq.UBBPARM. |
//BBSECURE DD | This statement defines the data set that contains security resource definitions. These definitions are used by the CAS and PAS to determine whether security checking should occur for access to systems, products, views, and actions. The same data set name must be defined for the CAS started task procedure BBSECURE statement and the PAS started task procedure BBSECURE statement. Defining a BBSECURE data set is only one part of setting up security to function with your external security manager (ESM). For more information about customizing security, see Managing-security-for-BMC-AMI-Ops-products. |
//BBVDEF DD | This statement defines the library that contains distributed views. |
//BBACTDEF DD | This statement defines the data set that contains distributed action and view tables. |
//BBDTNQxx DD | (Optional, used for BMC AMI Ops Monitor for CMF and BMC AMI Ops Monitor for z/OS only) This statement controls exclusion of major names from data collection. For more information, seeFiltering out selected enqueue majors. |
//USSDUMP DD | (BMC AMI Ops Monitor for UNIX System Services only) This statement is used by the OEDGTRC trace function for problem diagnosis at the request of BMC Support. |
//PARMFILE DD | This statement defines a VSAM data set that contains:
|
//HISTDS00 DD //HISTDS01 DD //HISTDS02 DD | This statement defines up to 100 VSAM data sets that compose the historical database. |
z/OS PAS PROC statement parameters
The following table explains each parameter that is available for use with the PROC statement in the z/OS PAS started task procedure:
Parameter | Description | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AHS | The optional AHS parameter specifies the suffix of the BBUTAHxx PARMLIB member that is used for BMC AMI Ops Monitor for UNIX System Services Ad Hoc Data Management. This parameter is ignored if BMC AMI Ops Monitor for USS is not installed or not enabled. This parameter uses the following syntax: AHS={xx | S0} The default is S0. | ||||||||||||||||||||||||
BAVSHLQ | The required BAVSHLQ parameter defines the high-level qualifier for the VSAM data sets that are used for historical data and internal and user-defined system workloads. This parameter uses the following syntax: BAVSHLQ=hlq | ||||||||||||||||||||||||
BBCHILV | The required BBCHILV parameter defines the high-level qualifier for the product libraries. This parameter uses the following syntax: BBCHILV=hlq | ||||||||||||||||||||||||
BBLINK | The optional BBLINK parameter defines the name to be assigned to the BBLINK data set. This parameter uses the following syntax: BBLINK=name | ||||||||||||||||||||||||
BBSOUT | The required BBSOUT parameter defines a valid SYSOUT class for started tasks. This parameter uses the following syntax: BBSOUT=class | ||||||||||||||||||||||||
BBX | The optional BBX parameter specifies the name of the BBX SubSystem to be used. This parameter uses the following syntax: BBX=name The default is BBX=BBXS. | ||||||||||||||||||||||||
CASWAIT | The optional CASWAIT parameter (used for BMC AMI Ops Monitor for CMF and BMC AMI Ops Monitor for z/OS only) specifies the amount of time that the PAS should wait for the CAS to start, both during initial PAS startup and if the CAS terminates while the PAS is executing. This parameter uses the following syntax: CASWAIT=nnnn nnnn can be any number of minutes from 0 to 9999. The default is 10 minutes. If you specify CASWAIT=0, the initialization process does not retry the connection to the CAS. | ||||||||||||||||||||||||
CFCACHE | The optional CFCACHE parameter specifies whether the Coupling Facility Data Collector (CFAC) gathers additional data for cache structures. Specifies whether the Coupling Facility Data Collector (CFAC) gathers additional data for cache structures. Since obtaining this information requires making an additional CF API (IXLMG) call for each cache structure, the default is not to obtain this information. When CFCACHE=Y has NOT been requested, various fields in Coupling Facility Structure views relating to the cache structure activity, such as Directory Reclaims, are zero (0). This parameter uses the following syntax: CFCACHE={Y | N} The default is N. | ||||||||||||||||||||||||
CMDID | The optional CMDID parameter defines a single character to be used as the "command id" character for use when issuing commands to the PAS or SYSPROG. Commands prefixed with the command id character are routed to the PAS. Commands prefixed with the command id characterrepeated twice are routed to SYSPROG. CMDID=symbol You can use the CMDID value as a quick method for issuing commands. You must manually add the CMDID parameter to the PAS procedure statement to enable this support. Valid operands are as follows:
Certain operands might need to be enclosed within quotation marks to work in your environment. Alternatively, operands can be specified as a two-digit hexadecimal representation. For information about using the MODIFY command to control the z/OS PAS, see Controlling-z-OS-PAS-operation. | ||||||||||||||||||||||||
CPM | The optional CPMparameter (used for BMC AMI Ops Monitor for CMF and BMC AMI Ops Monitor for z/OS only):
This parameter uses the following syntax: CPM={xx | 00 | STOP} The default is 00. The control statement member contains Extractor REPORT and sampler control statements. This member controls the operation of the CPM mode samplers and defines the resources that the Extractor monitors. CPM mode samplers execute either when a MODIFY command is issued or when the CPM parameter is used. Sample control statement members are in the hlq.UBBPARM data set that was created during installation. The CPM mode control statement member that the Extractor uses can be changed while the Extractor is active by using the MODIFY command; for more information, see Controlling-z-OS-PAS-operation. | ||||||||||||||||||||||||
CXEN | The optional CXEN parameter specifies whether the CMF Extractor can issue an Enqueue, preventing another extractor from running. CXEN=Y is required if SMF=YES is specified on the CMFCPMxx or CMFIPMxx REPORT control statement. The purpose of this parameter is to allow more than one CMF PAS to run on the same system. Only one PAS can specify CXEN=Y (and hence write to SMF). All others must specify CXEN=N. CXEN={ Y | N} The default is Y (Yes), which allows enqueue sampling, workload sampling, and writing to SMF data sets. You can run more than one CMF Extractor on your system at a time. However, only one Extractor can sample workload data or enqueue data. | ||||||||||||||||||||||||
DC | This parameter indicates whether or not the normal Data Collectors should be started. CPM and IPM are used to indicate that the Data Collectors should be started using the associated BMC AMI Ops Monitor for CMF CPM or IPM Extractor session. START uses the BMC AMI Ops Monitor for CMF CPM session. This parameter uses the following syntax: DC={ START | STOP | CPM | IPM} The terms NORMAL Data Collectors and REGULAR Data Collectors are used interchangeably for the same set of Data Collectors that are based on the interval specified | ||||||||||||||||||||||||
DCDL | The optional DCDL parameter specifies the suffix of the BBDTDCxx PARMLIB member that is used to disable the Data Collectors for BMC AMI Ops Monitor for z/OS, BMC AMI Ops Monitor for UNIX System Services, and BMC AMI Ops Monitor for CMF. To use this member (default or alternate name), you must copy the BBDTDCDL PARMLIB member to the appropriate UBBPARM Data Set and then modify it. The distributed member in the BBPARM Data Set should remain unaltered. This parameter uses the following syntax: DCDL={xx | DL} The default is DL. | ||||||||||||||||||||||||
DYNSAMP | The optional DYNSAMP parameter specifies the use of dynamic sample timing for the Data Collectors. Data collector sampling is once a second, with various Data Collector called every second, every four seconds, every 15 seconds, etc. Prior to this parameter, after each set of Data Collector calls, the PAS would wait a full second before the next sample cycle. This parameter uses the following syntax: DYNSAMP={Y | N} The default is Y. With DYNSAMP=Y (default), the wait will be reduced by the elapsed time the previous Data Collector sample cycle took. For example, if a Data Collector sample cycle took 150 milliseconds, the wait until the next cycle would be 850 milliseconds instead of a full second. This allows more samples to be taken during an interval. | ||||||||||||||||||||||||
EM | The required EM parameter (used for BMC AMI Ops Monitor for z/OS only) specifies the two-character suffix of the PWSCPMxx control statement member that you want the BMC AMI Ops Monitor for z/OS Exception Monitor to use. The suffix for the PWSCPMxx control statement can be specified by the AEWSTART=xx parameter in the SYSPROG Services $$INSYS0 PARMLIB member. The value specified by the EM=xx parameter overrides the AEWSTART value. If the EM parameter is omitted or coded as simply EM=, the value in the AEWSTART parameter is used. If neither EM=xx nor AEWSTART=xx is specified, AEW is NOT started. This parameter uses the following syntax: EM={xx} There is no default. | ||||||||||||||||||||||||
FMNTHFS | The optional FMNTHFS parameter specifies whether the BMC AMI Ops Monitor for UNIX System Services Mounted File System Data Collector should collect the detailed HFS or not. This parameter takes the place of specifying the HFS=YES or HFS=NO on the FMNT statement in the BBDTDCxx PARMLIB member. This parameter uses the following syntax: FMNTHFS=( YES|NO} The default is YES. | ||||||||||||||||||||||||
HISTCOMP | The optional HISTCOMP parameter specifies whether the history data files should be compressed before being written out. This parameter uses the following syntax: HISTCOMP ={ YES | NO} The default is YES. | ||||||||||||||||||||||||
IPM | The optional IPM parameter specifies the suffix of the CMFIPMxx control statement member you want the CMF Extractor to use when running in IPM mode. Change this to the IPM member that you want to start. CMF control statement members are stored in the parameter library allocated by the DDName PARMLIB. A sample set of control statements for the CMF Extractor samplers commonly used in IPM mode is located in the CMFIPM00 member of the hilevel.BBPARM library. This parameter uses the following syntax: IPM={xx | STOP} The default is STOP. | ||||||||||||||||||||||||
JST | The optional JST parameter specifies the suffix of the BBDJSTxx PARMLIB member used for the BMC AMI Ops Monitor for z/OS Job Step Data Collector. This parameter uses the following syntax: JST = xx The default is 00. | ||||||||||||||||||||||||
LPARINAC | The optional LPARINAC parameter specifies whether the BMC AMI Ops Monitor for z/OS LPAR Data Collector should gather information on LPARs that are inactive. By default, inactive LPARs appear in various LPAR views with very little useful data. Specifying LPARINAC=NO eliminates inactive LPARs from appearing in the LPAR views. This parameter uses the following syntax: LPARINAC={ YES | NO } The default is YES. | ||||||||||||||||||||||||
LTDC | The optional LTDC parameter specifies the suffix of the BBDTLTxx PARMLIB member that is used to enable the Long-term Data Collectors. The normal Data Collectors must also be started, that is, DC=START. This parameter uses the following syntax: LTDC={xx | DC} The default is DC. | ||||||||||||||||||||||||
MSDP | The optional MSDP parameter specifies the suffix of the BBDTMSxx PARMLIB member that provides the defaults for MVScope. This parameter uses the following syntax: MSDP={xx | DP} The default is DP. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
MSCGSC | The optional MSCGSC parameter specifies whether MVScope Granular Security is to be enabled, which prevents a user from mapping a program if they don't have read access to the program library dataset. If the feature is turned on, you may see a user ID read access error message on the MSMONSET view while running the MVScope monitor command. The PAS log will have BBDDM039I messages to indicate which data set the user ID does not have read access to. MSCGSC={Y | N} The default is N. | ||||||||||||||||||||||||
The optional NQ parameter (used for BMC AMI Ops Monitor for CMF and BMC AMI Ops Monitor for z/OS only) specifies the two-character prefix of the BBDTNQxx PARMLIB member, which control exclusion of major names. For more information, seeFiltering out selected enqueue majors. | |||||||||||||||||||||||||
OMVSLIM | The optional OMVSLIM parameter specifies the number of short running OMVS forked address spaces that can occur in a single interval before Address Space records are no longer created for them. This parameter uses the following syntax: OMVSLIM=nnnnn The default is OMVSLIM=1000. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
PRCSTHR | The optional PRCSTHR parameter specifies whether the BMC AMI Ops Monitor for USS Process Data Collector should collect the thread data or not.This parameter takes the place of specifying THREAD=YES or THREAD=NO on the PRCS statement in the BBDTDCxx PARMLIB member. This parameter is ignored if BMC AMI Ops Monitor for USS is not installed or not enabled. This parameter uses the following syntax: PRCSTHR={YES | NO} The default is NO. | ||||||||||||||||||||||||
PVTLOW | The optional PVTLOW parameter specifies the threshold of storage (in kilobytes) in the 24-bit private area of the Product Address Space. If the amount of contiguous free storage in the 24-bit private area of the PAS falls below this value, a warning message will be issued. Specifying a value of zero disables this check. This parameter uses the following syntax: PVTLOW=nnnn The default is PVTLOW=512. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
PVTHIGH | The optional PVTHIGH parameter specifies the threshold of storage (in megabytes) in the extended private area of the Product Address Space. If the amount of contiguous free storage in the extended private area of the PAS falls below this value, a warning message is issued. Specifying a value of zero disables this check. This parameter uses the following syntax: PVTHIGH=nnnn The default is PVTHIGH=64. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
QRJ | The optional QRJ parameter specifies the suffix of the BBDTQRxx PARMLIB member used to provide Job execution state information for the JESTATR view. This parameter is ignored if BMC AMI Ops Monitor for z/OS is not installed or not enabled. This parameter uses the following syntax: QRJ=xx The default is QRJ=J0. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
RGN | The required RGN parameter assigns a region size of 32 megabytes. This parameter uses the following syntax: RGN=32 | ||||||||||||||||||||||||
RLS | The optional RLS parameter specifies the suffix of the BBDTRLxx PARMLIB member that is used to provide the Data Set filtering parameters for the VSAM RLS Data Collector. This parameter uses the following syntax: RLS=xx The default is RLS=SI. | ||||||||||||||||||||||||
SAS | The optional SAS parameter specifies the suffix of the BBUTSAxx PARMLIB member used for the BMC AMI Ops Monitor for USS Action Security Controls. This parameter is ignored if BMC AMI Ops Monitor for USS is not installed or not enabled. This parameter uses the following syntax: SAS=xx The default is SAS=S0. | ||||||||||||||||||||||||
SRH | The optional SRH parameter specifies the suffix of the BBUTSHxx PARMLIB member used for the BMC AMI Ops Monitor for USS Required and Continuously File Systems. This parameter is ignored if BMC AMI Ops Monitor for USS is not installed or not enabled. This parameter uses the following syntax: SRH=xx The default is SRH=H0. | ||||||||||||||||||||||||
SRP | The optional SRP parameter specifies the suffix of the BBUTSPxx PARMLIB member used for the BMC AMI Ops Monitor for USS Required Process PARMLIB member. This parameter is ignored if BMC AMI Ops Monitor for USS is not installed or not enabled. This parameter uses the following syntax: SRP=xx The default is SRP=P0. | ||||||||||||||||||||||||
SSID | The required SSID parameter specifies the subsystem ID of the CAS to which the z/OS PAS should connect. This parameter uses the following syntax: SSID=xxxx For a PAS to connect to a CAS, the SSID values in both the CAS and PAS startup procedures must be the same. | ||||||||||||||||||||||||
STDC | The optional STDC parameter specifies the suffix of the BBDTSTxx PARMLIB member used to start the Short-term Data Collectors. The normal Data Collectors must also be started, e.g., DC=START. This parameter uses the following syntax: STDC={xx | NO} The default is NO. | ||||||||||||||||||||||||
TSP | The optional TSP parameter specifies the suffix of the BBATSPxx PARMLIB member used to enable or disable individual products that can run within the BMC AMI Ops Monitor for z/OS or BMC AMI Ops Monitor for CMF Product Address Space. This parameter uses the following syntax: TSP=xx The default is TSP=00. | ||||||||||||||||||||||||
TZOVRLAP | The optional TZOVRLAP parameter (used by BMC AMI Ops Monitor for CMF CPM and IPM sessions only) specifies the recording of CMF SMF records when the Time Zone offset is changed and an overlap exists in the local time. This parameter uses the following syntax: TZOVRLAP= RECORD | DISCARD
This parameter is applicable only to BMC AMI Ops Monitor for CMF CPM and IPM sessions that are writing SMF records (to SMF or to the CMFCPMx or to CMFIPMx DDs). Otherwise, this parameter is ignored. This value can be altered at any time by using a MODIFY command. | ||||||||||||||||||||||||
UBBPARM | The required UBBPARM parameter defines the name to be assigned to the user parameter library. This parameter uses the following syntax: UBBPARM=name | ||||||||||||||||||||||||
USEZIIP | The optional USEZIP parameter (used by products that are enabled to offload work to zIIP processors) specifies whether eligible CPU processing should be offloaded to zIIPs if zIIPs are online. This parameter uses the following syntax: USEZIIP=( Y | N) The default is Y (Yes). This value can be altered at any time by using a MODIFY command, which gives you control over whether zIIP-eligible processing should be offloaded from standard CPs to zIIPs. | ||||||||||||||||||||||||
XDM | The optional XDM parameter indicates whether the z/OS PAS should execute in extended diagnostic mode (XDM). This mode produces additional messages and suspends some PAS error-recovery processing, and is not recommended for normal operation. This parameter uses the following syntax: XDM={Y | N} The default is N (No). | ||||||||||||||||||||||||
XDS | The optional XDS parameter (used for BMC AMI Ops Monitor for CMF only) specifies the suffix of the CMFXDSxx control statement member that you want the BMC AMI Ops Monitor for CMF to use when starting the CMF Cross-System Data Server facility (XDS). To start XDS, change this to the XDS member that you want to start. XDS control statement members are stored in the parameter library allocated to the DDName PARMLIB. A commented set of XDS control statements is located in the CMFXDS01 member of the hlq.BBPARM library. This parameter uses the following syntax: XDS={xx | STOP} The default is 00. The default of XDS=00 causes the CX10XGDS API to be available, but does not buffer any SMF records for the CA10XDGY/CX10XDRC APIs to access. This value may be changed at runtime via the z/OS MODIFY (F) command, such as "F mvspas,XDS=01". Requirements for sharing cross-system data are as follows:
To collect XDS data, specify XDS=xx, where xx indicates the suffix of a CMFXDS xx member in the hlq.UBBPARM data set that was created during installation. You can switch to a different XDS member without stopping the z/OS PAS or XDS by using the MODIFY command. |