Many suspected SMP/E problems can be corrected by responding to
SMP/E error messages. Therefore, when you get an SMP/E error message,
refer to SMP/E messages to find its explanation
and the recommended response. If you receive a message (such as GIM35302E)
containing an MVS™ error code,
refer also to z/OS MVS Programming: Authorized Assembler Services Guide, SA23-1371,
to find an explanation of the error code and the recommended response.
If the recommended response does not correct the problem, follow
these steps to determine the cause of the problem and the correct
recovery methods:
- Examine the return codes in each job step and subsequently the
return codes for each command.
Starting with the final code
(the one returned by the failing job step), trace back through the
job log to find the SMP/E command return codes that caused the job
step return code. Remember, a single return code can be the product
of multiple errors.
The job step return code issued for SMP/E
is the highest return code generated by all SMP/E commands in that
step. The job step return codes are:
- Return Code
- Meaning
- 00
- SMP/E processing ran successfully and without errors. The severity
code in associated SMP/E messages is I.
- 04
- SMP/E processing ran, but warning messages were issued. The severity
code in associated SMP/E messages is W.
- 08
- SMP/E processing ran, but processing errors occurred and processing
stopped for at least one SYSMOD. The severity code in associated SMP/E
messages is E.
Check the reports produced to see which SYSMODs
were not successfully processed.
- 12
- SMP/E processing stopped for at least one SMP/E command. The severity
code in associated SMP/E messages is S.
- 16
- SMP/E processing stopped because of a severe error. The severity
code in associated SMP/E messages is T.
- 20
- SMP/E processing stopped because of an internal SMP/E error. For
example, there may be an interface problem between SMP/E modules or
a data error on the SMPCSI data set. The severity code in associated
SMP/E messages is T.
For specific return codes for each of the
SMP/E commands, see SMP/E return codes.
- As you trace back through the return codes in SMPOUT, check for
error and
warning messages issued with the return codes. Use the information
supplied by the messages to help you interpret the meaning of the
return codes.
- If an APPLY, ACCEPT, or RESTORE command completes with a return
code greater than 4, first check the Causer SYSMOD Summary Report
in SMPRPT to determine the root failures.
- Check to see whether you coded the RC operand on any SMP/E commands.
The RC operand
enables you to specify the maximum acceptable
return codes from specified SMP/E commands in order to bypass normal
SMP/E return code processing. If a specified command returns a code
higher than the maximum specified in the RC operand, the command that
contains the RC operand is not processed and issues a return code
of 12.
For example, if you specify RC(RECEIVE=04) on the APPLY
command, and the previous RECEIVE command returns a code of 08, APPLY
processing is not performed and the APPLY return code is 12.
For
further information about the RC operand, refer to the discussion
of it under the description in each command in SMP/E for z/OS Commands.
- Check the SYSPRINT data set for information about the success
or failure of the system utility programs invoked by SMP/E commands.
- Use the LIST command to check the contents of the SMPLOG data
set. If you
need to check SYSMOD status but do not have the reports and messages
that include it, use the LIST command as follows: