Follow this procedure to gather the recommended documentation and report the problem.

1. Obtain the dump output.
   SMP/E produces various types of dumps, depending on the type of abend that has occurred and the dump data sets you have defined. For example:

   • If you have defined SMPSNAP, a dump is taken before any cleanup operations are attempted. The dump reflects the state of SMP/E storage at the time of the abend.
   • If you have defined SYSABEND or SYSUDUMP, a dump is taken by the ESTAE routine after the cleanup operations.
   • If you have defined SMPSNAP and either SYSABEND or SYSUDUMP, dumps are taken before and after cleanup.

   See Collecting documentation for SMP/E problems for additional information about abend dumps.

2. Find the abend code.
   The SMP/E abend messages show the abend code for the failure:

   • GIM43201T is issued when SMP/E abends.
   • GIM4400x is issued when the SMP/E subtask that interfaces with utilities abends.
3. Find the program interrupt code in the supervisor request block (SVRB).
4. Find the save area trace.
5. For a hex 0C1 or hex 0C4 abend:
   1. Find the PSW at the time of the abend.
      The location of the PSW in dump output depends on the type of dump taken. Generally, it is on the top of the first page of the dump. You can also find the PSW in the recovery termination manager 2 work area (RTM2WA).

      Note: For a SNAP dump, you do not want the PSW at the time the dump was taken (the first PSW), but rather the next one, which should be the load module PSW.

      Make sure the PSW is for the last SMP/E module that was in control, not for an ISPF or TSO module.

   2. Find the failing address.

      The PSW may contain the address of either the failing instruction or the next instruction that was to be processed when the abend occurred (this depends on the type of abend).

   3. Find the ID of the module that contains the address in the PSW. Then find its entry point address and the displacement within the module of the failing instruction.

      You can use the save area trace in a formatted dump to find the module ID, compile date, and entry point address.

      If you do not have a save area trace, follow these steps to find the information in the dump:

      1. To find the module ID, scan the dump output to find the address given in the PSW. Starting at the failing address, scan in descending address order along the right-hand side of the listing until you see an SMP/E module ID. The module ID will be printed in EBCDIC.
      2. To find the entry point address of the module, continue scanning the listing in descending address order and look for the 47F0F0nn instruction. The address of this instruction is the module's entry point address.
      3. To find the displacement of the failing instruction, subtract the entry point address from the address in the PSW.
   4. Find the general registers.

      You can find the general registers being used at the time of the abend in the save area trace, in RTM2WA, or in the abend SVRB register save area.

   5. Determine which register has incorrect information.

      Often the failing instruction refers to a general register with an incorrect address, or it points to an incorrect location (such as low-address storage). Use the principles-of-operation manual, the program interruption code from the PSW, and the general registers used in the failing instruction to determine (if possible) the register that contains or points to incorrect data.

      You are now ready to report the problem. Go to step 7.

6. For other abend codes, see z/OS MVS System Codes, SA38-0665.

   A complete list of abend codes can be found in z/OS MVS System Codes. Each code has an explanation of the documentation required, and problem-determination steps to follow. For example, abends may occur during the processing of supervisor call (SVC) instructions. Parameter lists and register contents passed to SVC routines are documented in z/OS MVS Diagnosis: Reference. This information may suggest that you get additional information, such as a module name, a return code, a register containing incorrect information, or the name of a system control block containing incorrect parameters.

   After making a complete check of these sources, you are ready to report the problem. Continue with the next step.

7. Report the problem to the IBM® Support Center.

   After asking for your account name, license number, and other customer identification, the service representative will ask for a brief description of the problem.