Problem Reporting Procedures › Identifying an Error › Client Service Process › Possible Documentation Needed

Possible Documentation Needed

The following is a list of documentation that might be requested by a Technical Support Representative:

• Any dumps that are taken.
  • SYSUDUMP—Usually this is sufficient. Send a printed copy. Be sure to include all subtasks.
• Any tapes that are sent must be accompanied by the JCL that created the tape as well as a list of the data sets on the tape.
  • SYSABEND—Only if requested. A tape can be used. Be sure to include all subtasks.
  • SYSMDUMP—Only if requested. This must be on tape and unformatted.
• Screen prints of all screens from initial entry of CA‑PanAPT until the error occurs.
• The TSO LOGON procedure CLIST used to allocate the CA‑PanAPT software libraries (hardcopy).
• All installation output (hardcopy).
• Copies of any modules with site‑specific modifications, with the modifications highlighted. Include any altered ISPF panels.
• Copies of any batch output showing the error.
• Library Code, Control, Inventory and partial Pending file reports produced by jobs APJJ5111, APJJ5102, APJJ5103, APJJ5104, APJJ5105, and AJJJ6111.
• Severe problems might require an IDCAMS PRINT of the VSAM files in hex and character.