Troubleshooting
Problem
This document provides details on how to generate an IMS trace on IBM z/OS in order to investigate a problem with WebSphere MQ and IMS.
Cause
IMS trace can help to determine why there is a problem between WebSphere MQ and IMS. Minimize the length of time you trace in order to avoid generating excessively large files or filling up your disk. For other kinds of traces refer to:
Resolving The Problem
IMS provides several different trace types which support may ask you to run:
- Start tracing IMS as directed by IBM support. For example:
- To trace IMS™ Open Transaction Manager Access, use the "OTMT" keyword:
/TRACE SET ON TABLE OTMT
- To trace OTMA client activity and transaction pipe activity for clients with active transaction pipes:
/TRACE SET ON TMEMBER CLIENT1 TPIPE TPIPE1
- To trace OTMA client activity and transaction pipe activity for new transaction pipes:
/TRACE SET ON TMEMBER CLIENT1 TPIPE ALL
- Reproduce the problem with the IMS application.
- Stop the IMS trace using the syntax which matches your start command, for example:
- To stop IMS™ Open Transaction Manager Access trace:
/TRACE SET OFF TABLE OTMT
- To stop OTMA client activity and transaction pipe activity trace:
/TRACE SET OFF TMEMBER CLIENT1 TPIPE TPIPE1
- To trace OTMA client activity and transaction pipe activity trace:
/TRACE SET OFF TMEMBER CLIENT1 TPIPE ALL
- Switch the IMS online log dataset (OLDS) and save the one containing the current trace.
/SWITCH OLDS
Additional Information
[{"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Problem Determination","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"7.1;7.0.1;6.0","Edition":"All Editions","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21666630