×
 
 
  •  
$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 the z/OS PAS startup procedure

Use the following procedure (which uses member BBMPAS as a model) to set up your z/OS PAS started task procedure.

Tip

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

  • CMF MONITOR

  • MainView for z/OS

  • MainView for Unix System Services

  • MainView SYSPROG Services

  • MainView VistaPoint

Note

When you create the z/OS PAS started task procedure, specify the same subsystem ID on the SSID parameter of the PROC statement as you did in the CAS started task procedure. The PAS uses this SSID during initialization to identify its CAS connection.

To create the started task procedure

  1. Copy BBILIB member BBMPAS to SYS1.PROCLIB or another system procedure library and give it an appropriate name for a started task procedure.

    By default, configuration during installation creates a member called MVSPAS.

  2. Follow the instructions at the top of the member to modify the procedure to your site requirements.

  3. (Optional ) Define the z/OS PAS started task procedure to your IPL procedure so that the PAS starts at system initialization.

    BMC recommends that you modify the COMMNDxx member in SYS1.PARMLIB to add a START command for the PAS procedure:

    COM='S procname'

    procname is the name of the z/OS PAS started task procedure.

    Note

    The START commands are issued in the order that they appear in COMMNDxx. The z/OS PAS START command must occur after the CAS START command.

  4. If you do not define the z/OS PAS to start at IPL, see Managing the z/OS product address space for information about manually issuing a START command for the PAS.

Where to go from here

During PAS execution, BMC recommends that you:

  • Initiate the z/OS PAS as a started task (STC) through a system IPL procedure

  • Execute only one z/OS PAS per system image

  • Execute the z/OS PAS with a dispatching priority of 255

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

Comments

Log in or register to comment.

Creating a z/OS PAS PARMFILE data set
Creating a BBI-SS PAS PARMFILE data set
© 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.