Limited supportBMC 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, seeBMC AMI Ops Monitor for IMS Online 5.5.

Establish workload conventions


IMS workload definitions are saved in BBPARM member BBFTWK00.

To minimize maintenance time, the BBPARM data set with the BBFTWK00 member should be shared by all MainView for IMS product address spaces. Otherwise, duplicate workload definitions must be created and maintained.

Establishing logical, consistent conventions for workload and composite names is important, especially if all your workload definitions are not stored in a shared BBPARM data set. If you must use multiple BBPARM data sets for workload definitions, maintaining the definitions is much easier if you can quickly identify similar workloads.

  • Workload names

    The information in MainView for IMS plex views can be sorted and filtered by workload name. Consistent workload names make it easier to sort and filter views to find the information that you want to display.

    Workload names can be up to eight characters long, and the names should clearly represent the work performed by the target IMS subsystem. For example, the workload name IMSPAY could be used for IMS payroll transactions.

  • Composite names

    Composite names should represent a common function of the workloads that are part of a MainView VistaPoint application. For example, a workload composite with the name FINANCE indicates that a workload is part of the financial application. Composite names can be up to eight characters long.

 

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