Before using this section, examine z/OS MVS System Codes and z/OS MVS System Messages, Vol 1 (ABA-AOM),
through z/OS MVS System Messages, Vol 10 (IXC-IZP).
These might help you generate additional keywords by identifying failure-related
functions and providing message-to-module
cross-reference tables.
Message IGD300I
This message always accompanies an SMS abend. If SMS cannot find
the SDWA and recover, message IGD312I might appear. This message
usually does not appear.
- Figure 1 shows a sample SMS abend-related
job log, which always contains message IGD300I.
- Because this message reports an abend type-of-failure, do not
specify the message identifier as a keyword. See Procedure for SVC dump and use that section to identify the
failure-related keywords.
Figure 1. Sample
SMS Failure Related Job Log Output*******************************************************
J E S 2 J O B L O G -- S Y S T E M 3 0 8 1 -- N O D E N 1
07.39.08 JOB 29 $HASP373 S2RAS031 STARTED - INIT 1 - CLASS A - SYS 3081
07.40.13 JOB 29 S2RAS031 STEP 0 IKJEFT01 0000
07.40.19 JOB 29 DFPWTX30 ISSUING COMMAND.
07.40.20 JOB 29 *41 S2RAS031--REPLY GO STEP1
07.40.46 JOB 29 R 41,U
07.40.52 JOB 29 S2RAS031 STEP1 WTORPGM 0000
07.42.31 JOB 29 S2RAS031 STEP2 AMBLIST 0000
07.42.58 JOB 29 S2RAS031 STEP2 AMBLIST 0000
IGD300I AN ABEND OCCURRED DURING SMS PROCESSING
ABEND SYSTEM CODE=06F ASID=0010
COMPONENT NAME=SMS COMPONENT ID=28462
ACTIVE LOAD MODULE NAME=IGDZILLA ADDRESS=01BE1000
CSECT IN ERROR DESCRIPTION=BUILD MSG RTN 2
NAME=IGDMCSC2 ADDRESS=01BF5758 OFFSET=00000026
ASSEMBLY DATE=032487 PTF LEVEL=HDP3310
PSW AT TIME OF ERROR 071C0000 81BF577E
DATA AT PSW 01BF5778 - C5404040 400090EC D00C18CF
GPR 0-3 008C7444 7F70FC78 00000010 00000000
GPR 4-7 00000018 7F70FD10 7F70F434 7F70FD14
GPR 8-11 7F70FDD8 01BF58B2 01BF48B3 7F70FAB0
GPR 12-15 81BF38B4 7F70FAB0 81BF41B6 81BF5758
07.43.03 JOB 29 IGD306I UNEXPECTED ERROR DURING IGDMCSCN PROCESSING
RETURN CODE IS 8, REASON CODE IS 12008
THE MODULE THAT DETECTED THE ERROR IS IGDMCSCN
SMS MODULE TRACE BACK - MCSCM DSP00 SSIRT
SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00025
07.43.04 JOB 29 S2RAS031 STEP3 IGDRAS00 0000
07.43.04 JOB 29 $HASP395 S2RAS031 ENDED
Message IGD306I
This message indicates that an SMS failure has occurred and that
SMS has written a symptom record to SYS1.LOGREC.
- Print SYS1.LOGREC to obtain structured search keyword information.
See EREP User's Guide for
instructions on how to print SYS1.LOGREC. See the sample record in Storage Management Subsystem records written to logrec data set. Use these keywords as the complete
keyword string.
- See Searching with the keyword string.
If the CSECT IN ERROR is not an SMS load module or CSECT, then
SMS detected an error from a component or subcomponent that was called
to perform a service. The return and reason codes might also belong
to the called component or subcomponent.
SMS return and reason codes are in Storage Management Subsystem return and reason codes.
Errors returned from the called component or subcomponent should be
pursued with that component or subcomponent. Use Table 1 to help identify the failing component
or subcomponent.
Note: The called components or subcomponents might issue
messages preceding the IGD306I message. These initial messages can
describe the error.
Message IGD311I
This message reports the same condition as IGD306I,
except that SMS was unable to write a symptom record to SYS1.LOGREC.
- Record the module in error, the return code, and the reason code
as keywords.
The failure to write a symptom record to SYS1.LOGREC
is usually unrelated to the problem for which the record was being
written. Message IGD311I also contains the return
and reason codes from the unsuccessful attempt to write the SYS1.LOGREC
record. Do not specify these codes in the keyword string.
- If you want to do a keyword search for the failure to write to
SYS1.LOGREC, do not include the failing module name, return code,
or reason code associated with the original failure. Specify only
the message identifier, return code, and reason code related to the
SYS1.LOGREC write failure.
- If you want to do a keyword search for the original failure, specify
the original failure-related module name, return code, and reason
code.
- See Modifier keywords.