Creating a BBI-SS PAS startup procedure

Important

If you have customized a product via EZCONFIG, the started task procedure for BBI-SS PAS is created automatically.


Use the following procedure to set up a started task procedure for the BBI-SS PAS.

Tip

This task is required for the following products but does not apply to other products:

  • BMC AMI Ops Automation
  • BMC AMI Ops Monitor for CICS
  • BMC AMI Ops Monitor for Db2
  • BMC AMI Ops Monitor for DBCTL
  • BMC AMI Ops Monitor for IMS Online
  • BMC AMI Ops Monitor for MQ

Related topics

Defining-configuration-members-to-BBI-SS-PAS

Allocating BMC AMI Ops Automation data sets

Manual-customization

 Use member SSJCL to help you set up your BBI-SS PAS started task procedure.

Important

  • The default region size for the BBI-SS PAS is 64 MB.

    If you reduce this allocation and not enough working storage is available after initialization, the BBI-SS PAS terminates with an error message.

  • The job contained in member SSJCL should run as a started task; if not, a JES initiator is occupied for the duration of the BBI-SS PAS session.

    To run SSJCL as a started task, remove the JOBCARD statement and the PEND and EXEC statements at the end of the JCL. Then copy the SSJCL JCL procedure to a JES PROCLIB.

  • For optimum BBI-SS PAS performance, the BBI-SS PAS dispatching priority should be equal to or greater than any of the target subsystems that the PAS manages.

    If the dispatching priority is too low, loss of data or excessive storage usage could occur.

  • If you have IBM RACF or an equivalent external security manager (ESM), verify that the BBI-SS PAS has authorization to access and update all BMC AMI Ops product data sets.
  • The PARM statement in member SSJCL defines the subsystem ID that is assigned to the BBI-SS PAS.

To create a BBI-SS PAS started task procedure

  1. In BBSAMP member SSJCL, make the following changes:
    1. Change the PREFIX parameter to the prefix that was used to load the product libraries to DASD.
    2. Change the SS parameter value to the subsystem ID of the BBI-SS PAS.
    3. Use the default parameter START=WARM.START=COLD should be used only as instructed by BMC Customer Support or when the BBI-SS PAS requests it through WTOR after maintenance.
  2. Ensure that your UBBPARM data set is concatenated before the BBPARM data set.

  3. (

    BMC AMI Ops Automation

     only) Perform the following steps:

    1. Create a SYSPROC DD statement that points to the libraries that contain BMC AMI Ops Automation EXEC members:
      • Uncomment the SYSPROC DD statement.
      • Ensure that the UBBPROC data set is concatenated before the BBPROC data set.
    2. Allocate a BBIDIV data set to store binary large objects and data across BMC AMI Ops Automation restarts:

      • Insert the following DD statement immediately before the PEND statement:

        //BBIDIV DD DSN=&PREFIX.&SS..BBIDIV,DISP=OLD

        Important

        Do not specify the BBIDIV DD statement by using a DUMMY (or null) data set. Such a statement might cause an S013-64 abend.

      • For information about how to allocate the BBIDIV data set, see Allocating BMC AMI Ops Automation data sets.

  4. (

    BMC AMI Ops Monitor for Db2

     only) If you are also installing the BMC AMI Ops Monitor for Db2 Data Collector component, include the Data Collector load library in the PAS STEPLIB concatenation with the correct high-level qualifier.You can use the sample CDCLOAD DD statement that is included in the procedure as an example.

  5. (optional) Add the following statement to your configuration members://BBCFG DD DSN=&PREFIX..&SS..UBBPARM(xxxxxxxx),DISP=SHR

    xxxxxxxx is the one- to eight-character name of the member that you created for BBCFG in Defining-configuration-members-to-BBI-SS-PAS.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*