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 Monitor for CICS, version 7.3

Customizing terminal types eligible for broadcast messages (CAOTTAB)

When the MainView AutoOPERATOR for CICS BROADCAST application is invoked, a list of all terminals eligible for the BROADCAST function is displayed.

The following criteria must be met before a terminal is eligible for broadcasting:

  • It must have a CICS status of INSERVICE.

  • If it is a VTAM terminal, it must be currently acquired.

  • Its model specification must match the specifications of the supplied terminal table.

Because the performance of terminals varies by model, you may need to customize the MainView AutoOPERATOR for CICS terminal table to include the terminal types used at your site.

The CAOTTAB macro generates the MainView AutoOPERATOR for CICS terminal table. The default table is distributed by BMC Software using the following CAOTTAB macro invocation:

CAOTTAB (L3277,R3277)

Any terminal type that can be specified for the CICS terminal definition operand TERMMODL can be specified for CAOTTAB.

The member TTABJCL in your BBSAMP data set contains sample JCL that can be used to assemble and link CAOTTAB.

To modify CAOTTAB

  1. Copy TTABJCL from BBSAMP to UBBSAMP, and make sure the new member name conforms to your site’s naming conventions.
  2. Read the comments in the member that was created in the previous step, and then modify the JCL accordingly.
  3. Modify the sample invocation of the CAOTTAB macro to make all terminal types eligible for BROADCAST messages.
  4. Submit the newly created JCL, and check the output to ensure that all steps are completed with a return code of 0.

    Note

    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 the BBI-SS PAS and restart it.

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

Comments