Space banner This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Troubleshooting

This troubleshooting information can help you diagnose some common installation problems. For most situations, start troubleshooting by running the procedures in Task-6-Verifying-installation and checking the log for any diagnostic messages describing errors.

Typical errors

U123 abend encountered

Indicates the VTAM release is not supported by Session Monitor Global Record.

Suggestions

  • Contact BMC Support to determine if there is a PTF available for Session Monitor to support the VTAM release.

  • If the VTAM release is not GA, contact BMC Support.

S047 abend encountered

The Session Monitor load library, SQQFLOAD, in not APF authorized.

Suggestion

Make the Session Monitor load library, SQQFLOAD, APF authorized.

Informational messages “SVMAN601I GLOBAL RECORD SUBSYSTEM IS ALREADY ACTIVE” and “SVMAN602I IT MUST BE SHUTDOWN FOR A START UP TO TAKE PLACE”

There can only be one global record started task running at a time on an LPAR. This can happen when there are production and test global record started tasks.

Suggestion

To avoid this error, add the following to all global record started tasks in the LPAR:

//ENQUEUE DD DSN=MY.EMPTY.DATASET,DISP=OLD

This will provide an exclusive lock on the dataset MY.EMPTY.DATASET. If one of the global records is running, the other global record job will not run until the one currently running has been brought down.

Global Record shuts down immediately

This can occur when either there are errors on the initial refresh of the Session Monitor PARMLIB member or Session Monitor is not configured to record any technology.

Suggestions

  • Ensure there are no errors with any of the parameters in the Session Monitor PARMLIB member by checking the output of the CMSC job. Correct any issues and refresh the Session Monitor PARMLIB member.
  • Edit the PARMLIB member for Session Monitor. Ensure that at least one of the following is in the PARMLIB member:
    • TCPIP_JOBNAMES
    • MQ_QUEUE_MANAGER_NAME
    • ENABLE_3270=YES
    • ENABLE_APPC=YES
    • ENABLE_LU0=YES

BMC Support

Go to BMC Support site to find product documentation, knowledge articles, and other technical resources. You can open a case with the BMC Support, order products, and much more.

Information for BMC Support

If problems arise, please check your manual for assistance. If problems persist, please obtain the following information before calling BMC for assistance. This information will help determine the exact cause of the problem as quickly as possible.

  • Identify the release number of BMC products in use.
  • Identify the operating system.
  • Identify the release of CICS Transaction Server that is being used.
  • If an abend occurs, note the displacement and the module in which it occurs. If possible, obtain a copy of the system dump.
  • Note the sequence of steps (including all commands issued) that resulted in the problem. Also, note any variable data types and programming languages involved.
  • To receive product fixes electronically, be ready to provide your email address.

 

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