Defining BBI-SS PAS interval services parameters

To define BBI-SS PAS interval services parameters

1. In member BBIISPxx, specify the name of a BBPARM member that defines the group of timer-driven services that are to be started at BBI-SS PAS startup:AUTOID=userid

   TARGET=tgtname,BLK=blkName[,USRID=userid][,ALERTQ=qname]

    

   AUTOID	TARGET Specify the logon ID of a user that is to be associated with automatically started timer requests. AUTOID is the default if USERID is not specified. AUTOID must be on a separate line from TARGET and BLK, as in the following example: AUTOID=ADMIN TARGET=DB2A,BLK=BLKDB2A TARGET=DB2B,BLK=BLKDB2B
   TARGET	Specify the target system that is to receive the requests for BLK. It can be the target system ID or the subsystem ID. TARGET must be on the same line as BLK and can be repeated.
   BLK	Specify the one- to eight-character name of a BBPARM member that defines a collection of timer-driven SET requests for product services that can be initiated at the same time. BLK must be on the same line as TARGET and can be repeated. The BBPARM members are as follows:
   	MainView for CICS
   	CMRBLK1	Contains a group of background service requests that are used when MainView for CICS data collection is not active
   	CMRBLK2	Contains a group of background service requests that are used when MainView for CICS data collection is active
   	CMRBLK3	Contains a group of background service requests that are used when MainView for CICS data collection is active
   	MainView for DB2
   	BLKDMRW	Can be used to create a starter set of monitors and traces to provide recent Db2 history
   	MainView for DBCTL
   	BLKDBTW	Can be used to create a starter set of monitors for a DBCTL system
   	MainView for IMS Online
   	BLKIMFW	Can be used to create a starter set of monitors for IMS
   	Note: You can use the BLKxxxx members as a base from which to build a list of monitors to be started automatically. These members define suggested warning thresholds; some show only your site's activity.
   USRID	(Optional) Specify the logon ID of a user that is to be associated with the timer requests in the member specified by the BLK parameter. This user has the authority to modify or purge the timer requests. The value for userid must match a BBPARM user authorization member (see BBPARM member USERID). USRID is optional and is written on the same line as TARGET and BLK. It supersedes AUTOID and associates the specified user with the group of requests defined for that BLK parameter, as in the following example: TARGET=DB2A,BLK=BLKDB2A,USRID=$TDB2AR If USRID is not specified, the default is AUTOID. If AUTOID and USRID are not specified, a default user ID of USERID is used. A USERID member must exist in the BBPARM data set.
   ALERTQ	(Optional) Specify an alert queue name for CICS, Db2, IMS, or DBCTL targets. This parameter activates automatic creation of alerts for monitor exception messages, including background exception messages in MainView for DB2. The alerts are displayed in the Alert Manager views.

   Note

   If these exception messages are already being processed into alerts by MainView AutoOPERATOR rules for journal messages, the ALERTQ parameter is not needed. Specifying ALERTQ could result in duplicate alerts.

2. Identify the name of the data set that will be used as a trace directory by the following products:

   • MainView for CICS
   • MainView for DB2
   • MainView for DBCTL
   • MainView for IMS Online

   Note

   This data set cannot be shared by multiple BBI-SS PASs.

   Specify the data set name of the trace directory as :

   TRDIR=dsn[,SUBSYS=ssid]

   • dsn is a valid data set name.

   • ssid (optional) is the subsystem name to which this trace directory applies.

     This parameter allows multiple BBI-SS PASs to share the same BBIISPxx member.

   Trace logging can be set up automatically by using the configuration procedures that are described in Installation System. Your product customization guide describes how to set up and maintain trace logging manually.