Question & Answer
Question
What documentation is best to have available when reporting an incident to the IMS Index Builder support team?
Answer
Provide the following three pieces of documentation for every IMS Index Builder problem:
1) A description of the problem
2) The IMS Index Builder release and the last PTF that was installed
3) The IMS release
1) When IMS Index Builder ran successfully, but appears to have processed incorrectly, also provide the following documentation:
a) The entire job output
b) Any documentation supporting the incorrect processing
c) The DBD source
2) When an IMS Index Builder job abends, also provide the following documentation:
a) The entire failing job output
b) The SYSUDUMP dump output
c) The DBD source
1) A description of the problem
2) The IMS Index Builder release and the last PTF that was installed
3) The IMS release
Because incident types vary, different documentation is required for different incident types. Generally, it is best to have the following documentation for the two following incident types:
1) When IMS Index Builder ran successfully, but appears to have processed incorrectly, also provide the following documentation:
a) The entire job output
b) Any documentation supporting the incorrect processing
c) The DBD source
2) When an IMS Index Builder job abends, also provide the following documentation:
a) The entire failing job output
b) The SYSUDUMP dump output
c) The DBD source
Related Information
[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSAVF8","label":"IMS Index Builder for z\/OS"},"ARM Category":[{"code":"a8m0z000000cvZEAAY","label":"IMS Index Builder for z\/OS"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
16 November 2020
UID
swg21079034