Implementing MainView AutoOPERATOR for CICS function security

This section discusses function security for MainView for CICS and MainView AutoOPERATOR for CICS, how it is specified by assembling and linking the CMRSECU module using the CMRSECU macro. This section includes the following topics:

The sample security member is distributed in BBSAMP member CMRUSECU. Use the following procedure to update this member:

  1. Copy member CMRASM from prefix.BBSAMP to prefix.UBBSAMP. Make sure the new member name conforms to site naming conventions.
  2. Edit the member created in step 1. Read the comments in the member and then modify the JCL accordingly.


    You can dynamically reset the CMRSECU table with the command:


    See the MainView Administration Guide for a description of the RESET control command and supported parameters.

  3. Modify the sample invocations of the CMRSECU macro according to your site’s security requirements.

    The CMRSECU macro can contain up to three types of statements:


    The CMRSECU TYPE=INITIAL statement defines security for each

    • MainView for CICS function or action service

    • MainView AutoOPERATOR for CICS action service


    The CMRSECU TYPE=ENTRY statement further defines security per operator ID. (For example, a specific function may be accessed but only by a specific operator or operators.)


    A single CMRSECU TYPE=FINAL statement ends the input.

    Multiple sets of CMRSECU TYPE=INITIAL and CMRSECU TYPE=ENTRY statements can be specified. Each statement and its parameters are described in the sections that follow.

  4. Submit the newly created JCL; check the output to insure that all steps are completed with a return code of 0.


    S106 ABENDs can occur if the newly link-edited module causes the BBLINK data set to enter secondary extents and the active BBI-SS PAS attempts to load the module. If this situation happens, stop BBI-SS PAS and restart it.

Was this page helpful? Yes No Submitting... Thank you