IAT6304 NO UCB EXISTS FOR DEVICE ddd devname Explanation: A JESEXCP has been issued to the indicated JES3 device that was defined during JES3 initialization with no UeB (for example, JUNIT=NONE on the DEVICE statement).
System Action: No EXCP is issued and an intervention-required condition is returned to the caller of JESEXCP.
Operator Response: None.
Module: IATGROP
IAT6305 INVALID SPEC RESCHD,JOB=jobno,
ERRDEV = (ddn,type), DSP=dspname CANCELED Explanation: After the DSP requested specialized rescheduling (the unit was not available), the JSS driver (IATGRJP) received an error return from GETUNIT. This indicates that the GETUNIT list to which FCT (FCTGLIST) pointed is invalid.
System Action: The DSP is canceled.
Operator Response: Notify the system programmer.
Module: IA TGRJR
IAT6306 JOB jobno IS dspname, CALLED BY {con I INTERCOM I OPERATOR}, PRTY =dsp-priority
Explanation: A background DSP requested by the operator or another DSP has been added to the.JES3 job queue (JCT).
System Action: The DSP is subsequently scheduled as a JES3 job by normal JSS processing.
Operator Response: None.
Module: IATGRCD
IAT6307 CANNOT CALL 'dspname', err
Explanation: An operator *CALL command was rejected. One of the following reasons (err) is given:
DSI ONLY ON LOCAL
the operator attempted to call a DSP other than DSI (dynamic system interchange) on the local processor;
the only DSP that may be called on the local processor is DSI. Error descriptions follow.
NAME NOT GIVEN
no DSP name was specified in the request.
MORE THAN 8 charas
the parameter exceeds the DSP name length.
NOT IN LIBRARY
the requested DSP is not in the DSP dictionary.
NOT CALLABLE DSP
the requested DSP may not be called by the operator.
SYSTEM ERROR
the routine was entered in error; either the command is not *X or *CALL, or an unrecoverable JESIO error occurred.
REJ'D-USER EXIT
the *CALL was rejected by the user exit.
System Action: The *CALL command is ignored.
Operator Response: Correct the error, and reissue the call.
Module: IATGRCD
IAT6308 RC=rc ALOADING mod
Explanation: The work-to-do driver (IATGRWD) has been unable to load (using the ALOAD macro) the specified module while processing an operator command or a TSO STATUS, CANCEL, HOLD, RELEASE, or OUTPUT command.
System Action: The command is ignored.
Operator Response: Reissue the command if possible. If not, or if the error recurs, notify the system programmer.
Problem Determination: See Table I, item 29; Table III, items 4 and 7.
Module: IATGRWD
IAT6309 RETURN CODE rc ABEND CODE ac FROM LOAD OF MODULE mod
Explanation: The JSS driver (IATGRJR) was unable to load the specified module. Return code rc and abend code ac from the MVS LOAD macro instruction are given.
System Action: JES3 purges the DSP.
Operator Response: Notify the system programmer.
Problem Determination: See Table I, item 29; Table III, items 4 and 7.
Module: IA TGRJR
IAT6310 DSP WAITING FOR {RJP
I
SNARJP}Explanation: A DSP has unsuccessfully attempted to obtain a BSC RJP or SNA RJP controlled device as indicated by the message text because the RJP DSP or SNA RJP DSP was not active.
System Action: None.
Operator Response: Call the RJP or SNARJP DSP to begin operation.
Module: IATGRGU
IAT6320 CRITICAL VIRTUAL STORAGE SHORTAGE IN THE JES3 ADDRESS SPACE
Explanation: The JES3 address space has encountered a critical shortage of virtual storage.
System Action: JES3 has released two reserved 8K areas of storage in an attempt to make recovery processing possible.
Operator Response: Notify the system programmer. Consult your installation's procedures andlor the system programmer before starting any new functions in the JES3 address space.
Programmer Response: An out-of-space abend has occurred;
check SYS I.LOGREC to determine the cause. Lighten the storage load by reducing activity (such as the number of C/I subtasks) in the JES3 address space.
Module: IATGRCT
IAT6325 MODULE mod CHANGED IN SIZE SINCE LAST ALOADED
Explanation: While refreshing module mod, JES3 determined that the module had changed in size since it was last loaded (using the ALOAD macro).
System Action: Processing continues; the module is loaded in a different location.
Operator Response: None.
Module: IATGRLD
IAT6330 ID=xxx, SET=yyy, TOD=hh.mm.ss.t, ADDR=adr Explanation: This message is issued as a result of the trace dump command, *F,E,DUMP=.
System Action: Processing continues.
Operator Response: None.
Module: IA TGRED
IAT6332 TRACE DUMP COMPLETE
Explanation: Processing of the last trace dump command,
*F,E,DUMP=, is complete.
System Action: Processing continues.
Operator Response: None.
Module: IA TGRED
IAT6333 STOJ;l ON TRACE ID=xxx
Explanation: This message is issued only in conjunction with an
*F,E,sTOP=WAIT command. The stop was invoked for trace 10 xxx (a 4-digit decimal number).
System Action: The FCT of the trace caller is placed in the AWAIT state on the STOP ECF.
Operator Response: Use the *F,E,START=PGMCHK or
*F,E,START=RESUME command to post the STOP ECF as required.
Module: IATGRTX
IAT6334 TRACE ACTIVE - NO DUMP
Explanation: The trace routine is busy; no trace dump can be taken at this time.
System Action: Processing continues.
Operator Response: If an exclusive trace stop occurred, enter the *F,E,START=RESUME command to free the trace routine, then try another trace dump. For a normal busy condition, simply retry.
Module: IATGREO
IAT6340 THERE ARE NO AVAILABLE JOB NUMBERS Explanation: All numbers in the job number table are currently in use.
System Action: Any job unable to obtain a number is held until a job number becomes available.
Programmer Response: Restart the system with an increased job number range on the JES3 OPTIONS initialization statement.
Operator Response: Notify the system programmer.
Module: IATGRJN
IAT6350 CHECKPOINT ERROR. DRY UP SYSTEM AND COLD START
Explanation: A permanent I/O error occurred while writing the JES3 checkpoint records.
System Action: No further checkpoints are taken.
Operator Response: Terminate the system and. cold start it as soon as possible. Use the dump job (OJ) OSP to save and restore jobs in the system across the restart.
Module: IATGRCP
IAT6351 P{ERMANENT I/O ERROR READINGl
WRITING
f
CHECKPOINT DATASET, TRACK (xxxi
Explanation: A permanent I/O error occurred while JES3 was reading or writing the checkpoint data set.
System Action: JES3 processing continues.
Operator Response: Inform your system programmer.
Programmer Response: Analyze SYSl.LOGREC and error message to determine the reason for the I/O error.
Module: IATGRCP
IAT6352 MASTER TAT WILL BE RECREATED.
{
CHECKPOINTED COPY IS INVALID. } CAN'T READ CHECKPOINTED COPY.
Explanation: The master track allocation table (T AT) on the checkpoint data set 1s invalid or JES3 could not read it. JES3 recreates the T AT. At JES3 restart time, any data sets having their job or data set T AT on an unavailable spool data set are canceled.
System Action: Processing continues.
Operator Response: None.
Module: IATGRCP
IAT6353 CHECKPOINTED {SPOOL VOLUME}
TRACK/FORMAT
RECORD DOES NOT MATCH STORAGE COPY Explanation: The record read from the checkpoint data set does not match the storage copy of the record.
System Action: JES3 bypasses the checkpoint request.
Operator Response: Inform your system programmer.
Programmer Response: Take a dump of the checkpoint data set and obtain a JES3 dump. Contact IBM for programming support.
Module: IATGRCP
IAT6354 CHECKPOINT BYPASSED FOR {
SPOOL VOLUME(S) STATUS CHANGE}
SPOOL PARTITION CONFIGURATION·
CHANGE.
({NO STORAGE}) I/O ERROR
Explanation: This message, issued after message IAT6351, indicates that the checkpoint request cannot complete. Either an I/o error occurred or JES3 failed to obtain needed storage.
System Action: JES3 bypasses the checkpoint request.
Operator Response: Inform your system programmer.
Programmer Response: If an I/O error occurred, analyze SYSl.LOGREC to determine cause. If the I/O error is permanent, JES3 will fail at the next restart. A cold start may be required.
Module: IATGRCP