MustGather: Guidelines for IMS™ High Performance Sysgen Tools customers in gathering proper diagnostic documentation

Question & Answer

Question

When reporting an incident to the IMS High Performance Sysgen Tools (HPST) support team, what documentation should I have available?

Answer

For each HPST problem, be prepared to provide:

A description of the problem
The HPST software release and last PTF installed
The IMS system release

Additionally, because problem types vary, different documentation might be required for different problem types. In general, you will be asked to submit the following documentation for these two problem types:

Problem 1: HPST appears to have processed incorrectly.

- The entire job output including JCL, control cards, allocation messaging, and reports
- Output from any diagnostic report (upon request)
- Any other material that indicates a discrepancy between expected results and actual results

Problem 2: HPST abends.

- The entire failing job output, including SYSUDUMP output, JCL, control cards, allocation messaging, and reports
- Output from any diagnostic report (upon request)
- A console hardcopy of events that might indicate product failure
- Screen prints or line commands that demonstrate product failure
- Special DUMP or TRACE information might also be requested

Related Information

1271756

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVC5","label":"IMS High Performance System Generation Tools for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvZ9AAI","label":"IMS High Performance System Generation Tools for z\/OS"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Historical Number

5655F4300

Was this topic helpful?

Document Information

Modified date:
16 November 2020

UID

swg21107275

Tips