Collecting data about OTMA-related DC problems

IMS DC-related problems are frequently related to either OTMA or VTAM®. Use these guidelines to collect diagnostic information about OTMA when you experience a problem.

There are four main tools that you can use to diagnose problems with OTMA message traffic:
  • OTMT table trace
  • /DISPLAY commands
  • OTMA tmember and tpipe traces
  • IMS log records

Procedure

  1. Enable the OTMT trace table.
    Issue the following command: 
    /TRA SET ON TABLE OTMT OPTION LOG VOLUME HIGH
    This trace data is used by IBM® Software Support to diagnose OTMA problems. You can also specify OTMADB=Y in the DFSPBxxx member of the IMS.PROCLIB data set to get more trace data. However, using OTMADB=Y causes a large amount of WTO output to be written to the MVS console, and the setting can be removed only by recycling IMS.
    Recommendation: Do not set OTMADB=Y unless instructed to do so by IBM Software Support.
  2. Get the current status of OTMA clients and servers.
    Issue the following command:
    /DISPLAY OTMA
    Save the console output.
  3. Enable the OTMA tmember trace.
    Issue the following command: 
    /TRA SET ON TMEMBER XXXXXXXX
    Where XXXXXXXX is the tmember name. If you cannot identify a specific OTMA tmember, specifyALL for the tmember name to enable the trace for all members.
  4. If you know that the problem is associated with a specific OTMA tmember, you can get the current status for that tmember.
    Issue the following command: 
    /DISPLAY TMEMBER XXXXXXXX TPIPE ALL
    Where XXXXXXXX is the tmember name. Save the console output.
  5. If you know that the problem is associated with a specific OTMA tpipe, you can enable tracing at the tpipe level.
    Issue the following command:
    /TRA SET ON TMEMBER XXXXXXXX TPIPE YYYYYYYY
    Where XXXXXXXX is the tmember name and YYYYYYYY is the tpipe name.
  6. For CM1 and CM0 problems that are associated with a specific PSB, enable DL/I tracing.
    Issue the following command:
    /TRA SET ON PGM pppppppp
    Where pppppppp is the PSB name.
After you enable the required traces, preserve the X'67D0' and X'6701' log records and the console output from the /DISPLAY commands.