×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Limited support

 

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 Open link .
MainView Infrastructure 6.3 ... Customizing after installation Manual customization

Creating a BBI-SS PAS startup procedure

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:

  • MainView AutoOPERATOR

  • MainView for CICS

  • MainView for DB2

  • MainView for DBCTL

  • MainView for IMS Online

  • MainView for IMS Offline

  • MainView for MQ

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

Note

  • 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 MainView 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. (MainView AutoOPERATOR and MainView for MQ) Complete this step only if one of the following conditions applies to you:

    • You plan to use MainView AutoOPERATOR General Message Exchange (GME) or MainView AutoOPERATOR Command MQ Automation Power Line (APL).

    • You plan to connect a BBI-SS PAS from MainView for MQ without using a PATROL for MQ node manager.

    If either condition applies, perform the following actions to enable the BBI-SS PAS to use the IBM TCP/IP product or the BMC Generic TCP/IP Server (GTS):

    1. If the following TCP/IP libraries are not available in the system linklist, add the libraries to the STEPLIB:

      tcpprefix.SEZATCP

      tcpprefix.SEZALINK

      tcpprefix is the prefix that was defined when you installed TCP/IP.

    2. (MainView for MQ only) If the following TCP/IP library is not available in the system linklist, add the library to STEPLIB:

      tcpprefix.SEZALPA

    3. (MainView for MQ only) Add the following MQ-authorized program library to the STEPLIB DD statement:

      wmqprefix.SCSQAUTH

      wmqprefix is the prefix that was defined when you installed MQ.

    4. If you are running multiple TCP/IP stacks and you want to specify which stack the PAS should use, add the following TCP/IP configuration DD statement to member SSJCL:

      //SYSTCPD DD DISP=SHR,DSN=tcpprefix.CNTL(tcpipdata)

      tcpipdata is the name of the member that contains the TCP/IP configuration information that is required by TCP/IP client programs.

      You do not need to identify a specific TCP/IP stack to the BBI-SS PAS. If more than one stack is running, the PAS will use the first stack that is found with the latest release.

    5. To add BMC Generic TCP/IP Server (GTS) support, in BBPARM member BBISSPxx, specify

      GTS=xx

      xx is the suffix of your BBTTCPxx member.

    6. (Required for MainView for MQ; optional for MainView AutoOPERATOR) Create BBPARM member BBTTCPxx in your copy of the BBPARM library where xx is 00 or the suffix that you specified with the GTS parameter in member BBISSPxx.

      Note

      If you decide not to complete this step, you must specify GTS=00 in BBPARM member BBISSPxx (see Step 3.e).

      BBTTCPxx defines your TCP/IP environment and has the following statements:

      TCPNAME=name

      Note

      BMC recommends that you not specify any parameters in member BBTTCPxx. The parameters are designed mostly for testing or support purposes. When parameters are not specified, the BBI-SS PAS chooses the most current TCP/IP stack that is active on the system.

      If you are starting the BBI-SS PAS address space before TCP/IP, GME will not activate during BBI-SS initialization. Both GTS and GME must be activated after TCP/IP is started. You can activate them by issuing the following two BBI control commands:

      .S GTS

      .E P AAOGMExx,RECYCLE

      For complete information about BBTTCPxx, see BBTTCP00 parameters.

  4. (MainView AutoOPERATOR only) Perform the following steps:
    1. Create a SYSPROC DD statement that points to the libraries that contain MainView AutoOPERATOR 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 MainView AutoOPERATOR restarts:

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

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

        Note

        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.

  5. (MainView for DB2 only) If you are also installing the MainView 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.

  6. (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.

Related topics

Defining configuration members to BBI-SS PAS

BBTTCP00 parameters

Allocating BMC AMI Ops Automation data sets

Manual customization




Was this page helpful? Yes No Submitting... Thank you
Last modified by Mary Cameron on Sep 02, 2020
customization task

Comments

Log in or register to comment.

Allocating MainView AutoOPERATOR data sets
Adding the CICS EXCI library to the BBI-SS startup procedure
© Copyright 2013 - 2020 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.