Problem Determination Map

Edit online

The problem determination map that follows outlines the general approach and actions to take to isolate and resolve system problems. Note that several actions need to be completed before contacting IBM Support, and that specific documentation must be provided for problem analysis. Refer to Reporting a Problem to IBM Support. for procedures and documentation requirements when reporting a problem to IBM Support.

Installation related issues

  1. Is the problem associated with a recent installation of CL/SuperSession?
    • If Yes. If possible, test the failing function outside the CL/SuperSession product environment. Continue to question 2. (Continue to question 2A (Review IBM CL/SuperSession for z/OS Basic Configuration Guide 3.1) if it is not possible to test the failing function without CL/SuperSession.)
    • If No. Continue to section Recently installed maintenance, question 1.
  2. Does the problem go away when CL/SuperSession is not used?
    • If Yes. The problem may be related to CL/SuperSession. Review Chapter 2. Configuration planning and procedures and Chapter 3. Installation verification in the IBM CL/SuperSession for z/OS Basic Configuration Guide 3.1 to ensure that the product is properly installed. Continue to question 3.
    • If No. The problem is not related to CL/SuperSession. Refer to appropriate IBM or vendor documentation to continue diagnosis.
  3. Are there any installation or customization problems?
    • If Yes. Correct the installation and / or customization problems and then retest the failing function. Continue to section System or other product changes, question 5.
    • If No. Continue to section CL/SuperSession modifications, question 1.

Recently installed maintenance

  1. Have you recently installed maintenance (for example, PTFs, APARs, etc.) or parameter changes (for example, RLSPARM, RLSCMDS, or KLSSYSIN changes)?
    • If Yes. The problem may be related to the recently installed product maintenance changes. Review the maintenance installation and any product changes (for example, new initialization parameters) associated with the maintenance. Continue to question 2.
    • If No. Continue to section System or other product changes, question 1
  2. Are there any problems with the maintenance or change installation?
    • If Yes. Correct the maintenance/change installation problems and then retest the failing function. Continue to question 3.
    • If No. Continue to question 3A.
  3. Did the problem recur?
    • If Yes. Back out the maintenance and/or changes and retest the failing function. Continue question 4.
    • If No. The problem was probably related to a maintenance/change installation error. The problem is solved.
  4. Does the problem go away when CL/SuperSession is restored to the previous maintenance/change level?

System or other product changes

  1. Have you recently installed maintenance, tuning changes, network definition changes, or new product versions to the operating system or other system software (for example, VTAM, RACF, ACF2, DFP, CICS, IMS, PC 3270 emulators, TELNET server, etc)?
    • If Yes. Review the changes that were made to the other system software components. If necessary, contact other vendors to ensure that all appropriate maintenance is installed (for example, PTFs and/or APARs to resolve PEs). Continue to question 2.
    • If No. Continue to section CL/SuperSession modifications, question 1.
  2. Are there problems with the installation of other system software changes?
    • If Yes. Correct the other system software changes and retest the failing function. Continue to question 3.
    • If No. Continue to question 3A.
  3. Did the problem recur?
    • If Yes. Back out the other system software changes and retest the failing function. Continue to question 4.
    • If No. The problem was probably related to installation errors in the other system software. The problem is solved.
  4. Does the problem go away when the other system software is restored to the previous maintenance/change level?
    • If Yes. The problem may be with the other system software.

      OR

      The problem may be related to the interaction between the other system software and CL/SuperSession. Continue to section CL/SuperSession modifications, question 2A.

    • If No. Continue to section CL/SuperSession modifications, question 1
  5. Did the problem recur?
    • If Yes. Continue to section CL/SuperSession modifications, question 1.
    • If No. The problem was probably related to an initial installation error. The problem is solved.

CL/SuperSession modifications

  1. Did you modify any CL/SuperSession dialogs or user exits?
    • If Yes. The problem is possibly related to the modification:

      Follow these steps:

      • Use the SSPL LOG statement in one or more modified dialogs to locate the problem.
      • Back out the modified dialog.
      • Reinstall the previous working version.
      • Review and correct your modifications.
      • Retest the product using the modified dialog.

      Continue to question 2.

    • If No. Continue to question 2A.
  2. Did the problem recur?

Collecting trace information

  1. Is trace documentation required? (Refer to Chapter 4 Using Trace Facilities)
    • If Yes. Use the VSSTRACE command to invoke the General Trace Facility. Continue to question 2.
    • If No. Contact IBM Support for further assistance.
  2. Can you locate the problem on the trace? (Refer to Sample Traces.)
    • If No. Contact IBM Support for further assistance.
    • If Yes. Continue to question 3.
  3. Does analysis of the trace indicate that CL/SuperSession is the cause of the problem?
    • If Yes. Contact IBM Support for further assistance.
    • If No. The problem is not related to CL/SuperSession. Refer to appropriate IBM or vendor documentation to continue diagnosis.