The STEPLIB concatenation defined in the JES3 procedure, if used.
A library included in the linklist specified in response to message IEAI01A, SPECIFY SYSTEM PARAMETERS FOR RELEASE xxx.yy.zz.
Problem Determination: See Table I, items 2, Sa, 7c, 13, and 16;
Table III, items 2, 6, and 21.
Module: IATINAT
IAT3010 JES3 IS NOT THE PRIMARY SUBSYSTEM Explanation: JES3 has been started with another subsystem functioning as the primary job entry subsystem. JES3 must be the primary job entry subsystem.
System Action: JES3 is terminated.
Operator Response: Terminate the other job entry subsystem before invoking JES3.
Problem Determination: See Table III, item 21.
Module: IATINGL
IAT3011 SPECIFY JES3 START TYPE: (L H HA W WA WR WAR OR C)
Explanation: The operator must specify the type of JES3 start that is to occur.
System Action: JES3 initialization waits for an operator reply.
Operator Response: Enter one of the following:
L
H HA
W WA
WR
WAR
C
local start (not valid on the global processor) hot start as the global (not valid on a local processor) hot start as the global, and perform spool control block validity analysis on all jobs in the queue
warm start as the global
warm start as the global, and perform spool control block validity analysis on all jobs in the queue warm start as the global processor and allow replacement of spool data sets
warm start as the global processor, perform spool control block validity analysis for all jobs in the queue, and allow replacement of spool data sets
cold start as the global
CANCEL
immediately terminate JES3 initialization
If you reply W, WA, WR, WAR, or C, you must repeat the IPL of all JES3 processors in the complex-. If your reply is invalid, JES3 reissues the message.
Module: fA TINGL
IAT3012 SELECT JES3 INISH ORIGIN (N M= or U=), AND OPTIONAL EXIT PARM (,P=)
Explanation: The operator replied W, WA, WAR, WR, or C to message fAT3011. The location of the JES3 initialization statements must now be supplied. As distributed by IBM, the JES3 procedure specifies member JES3fNOO in SYS1.PARMLIB as the default source of initialization statements. Ignore the P=
parameter unless directed to do otherwise by your system programmer.
System Action: JES3 initialization waits for an operator reply.
Operator Response:
N
M=nn U=ddd
no change. Use the data set member specified in the J ES3 procedure.
use the member whose name is JES3INnn.
use the available card reader whose address is ddd to read the initialization deck.
,P=xxxxxxxx
the 1-8 character sequence that is to be made available to the user exit. Special characters may be included, but are not advised. Do not use an equal sign, a comma, or a blank in the string.
CANCEL
immediately terminate JES3 initialization.
If your reply is invalid, JES3 reissues the message.
Module: fA TINGL
IA T30 13 INVALID REPLY
Explanation: The reply to a preceding JES3 initialization write to operator (WTOR) was incorrect or did not specify a valid option.
System Action: JES3 reissues the original message and waits for an operator reply.
Operator Response: Select the desired response and enter it.
Problem Determination: See Table III, items 6 and 21.
Module: fA TINGL
IAT3014 ddn DID NOT OPEN, INIT TERMINATED Explanation: The data set specified by the DD statement ddn failed to open. The JES3 procedure probably does not include a valid DD statement with this name.
System Action: JES3 initialization is terminated.
Programmer Response: Verify that the named DD statement in the JES3 procedure represents a valid data set or unit allocation.
Problem Determination: See Table III, items 5, 6, 20, and 21.
Module: IA TINGL, IA TINIC
IAT3015 JES3IN BLKSIZE NOT MULTIPLE OF 80, INIT TERMINATED
Explanation: The data set represented by the DD statement JES3IN in the JES3 procedure is not in blocked 80-character card image format. Only 80-character mUltiple blocks are acceptable for use as JES3IN.
System Action: JES3 initialization is terminated.
Programmer Response: Recreate the data set that contains the JES3 initialization statements, specifying a block size that is an integer multiple of 80. Or correct the DD statement in the JES3 procedure to specify the proper data set.
Operator Response: Reinitialize JES3, but use a card reader (reply U=ddd to message IAT3012) for reading an initialization deck, or, if available, specify an alternate JES3 procedure.
Problem Determination: See Table III, items 6, 20, and 21.
Module: IA TINGL
IAT3016 DEALLOCATION OF JES3IN FAILED
Explanation: An attempt to dynamically deallocate the JES3IN data set has failed. JES3IN is deallocated when the current start is for a JES3 local processor or when a card reader is to be used for reading initialization statements. The disk-resident data set is not needed in either instance.
System Action: JES3 initialization continues.
Operator Response: None.
Module: IA TINGL
IAT3017 UNABLE TO ALLOCATE UNIT ddd
Explanation: A dynamic allocation of the card reader whose address is ddd was not successful. In reply to message IAT3012 the operator specified a unit address of a unit which was not available.
System Action: JES3 issues message IA T3030, giving diagnostic information on the failed allocation, and then reissues message IAT3012.
Operator Response: If available, select another card reader; or make available the originally specified reader.
Problem Determination: See Table III, item 6.
Module: IA TINGL
IAT3018 NO UCB FOR UNIT ddd
Explanation: The MVS system generation for this processor did not include a definition of the device whose address is ddd.
This address was specified by the operator in a U=ddd response to message IA T30 12.
System Action: JES3 reissues message IAT3012.
Operator Response: Specify a valid unit address.
Problem Determination: See Table I, item 17a; Table III, item 6.
Module: IATINGL
IAT3019 ddd IS NOT A CARD READER
Explanation: The operator specified U =ddd in response to message IA T30 12. The device at this address, according to the UCB, is not a card reader.
System Action: JES3 reissues message IA T30 12.
Operator Response: Select a valid card reader address.
Problem Determination: See Table I, item 17a; Table III, item 6.
Module: IA TINGL
IAT3020 UNABLE TO LOAD JES3 MODULE mod Explanation: A LOAD macro request for the specified module has failed. The ERRET return was taken.
System Action: If the module is the next in execution sequence or if it is in LPA, JES3 terminates with a S2FB abend. If the module name starts with IA TUX, initialization continues, but message IA T31 02 indicating probable failure is issued at the end of initialization.
Programmer Response: Verify that the module is present in one of the following:
The library concatenation defined by the JES3UB initialization statements, if used.
The STEPUB concatenation defined in the JES3 procedure.
The linklist specified in response to message lEA 1 0 1 A SPECIFY SYSTEM PARAMETERS FOR RELEASE xx.yy.zzz.
If the module in error is required in LPA, you must make sure it is not in a JES3 STEPUB, JOBUB, or JES3UB data set.
Problem Determination: See Table I, items 2, 7d, and 13; Table III, items 4, 5, 6, 20, and 21.
Module: IATINTK, IATINGL, IATINSV, IATINIT, IATINIC IAT3021 JES3 ALREADY ACTIVE
Explanation: JES3 has already been started as the primary subsystem. Only one JES3 subsystem can be active at a time.
System Action: The last JES3 subsystem that was started is terminated.
Operator Response: The active JES3 subsystem must be terminated before a second START JES3 is issued.
Module: IATINGL
IAT3022 MEMBER NAME ON JES31N DD IS ABSENT.
DEFAULT SET TO JES31NOO
Explanation: The operator replied N or M=nn to message IAT3012, but the DD statement JES3IN in the JES3 procedure does not specify a specific member of the data set to be used for JES3 initialization.
System Action: The member name JES31NOO has been internally set as the default. JES3 initialization continues with a member JES3INOO, if N was specified, or a member JES3INnn, if M=nn was specified.
Programmer Response: Specify the desired default member name in the JES3 procedure.
Operator Response: If another member is desired, reinitialize and select it by specifying M=nn in response to message IAT3012.
Problem Determination: See Table III, items 6 and 21.
Module: IA TINGL
IAT3023 mem IS A NONSTANDARD MEMBER NAME FOR JES3 INISH DECK, DEFAULTING TO JES3INxx
Explanation: The operator replied N or M=nn to message IAT3012, but the DD statement JES3IN in the JES3 procedure specifies a member whose name mem starts with characters other than JES3IN. The xx is set to 00 if the reply to message IAT3012 was not M=nn; if the reply was M=nn, then xx is set to nn.
System Action: The member name JES3INOO has been internally set as the default. JES3 initialization continues.
Programmer Response: Change the JES3 procedure to specify a member whose name starts with JES3IN for the DD statement JES3IN.
Problem Determination: See Table III, item 21.
Module: IA TINGL
IAT3024 {HOTST ART I LOCALST ARTJ DENIED --PREVIOUS JES3 ADDRESS SPACE
TERMINATION FAILED -- IPL IS REQUIRED TO RESTART JES3
Explanation: The previous JES3 address space termination processing terminated abnormally because of errors encountered by cleanup routines. I/O may be lost for USAM and CTCs.
System Action: JES3 does not allow the attempted hot start or local start.
Operator Response: To prevent further system damage, you must IPL the processor before attempting another hot start or local start. Inform the system programmer.
Programmer Response: Check SYS1.LOGREC to determine the cause of the previous address space failure. Acquire the termination dump and notify your IBM representative. If no dump was taken, take a stand-alone dump.
Module: IATINGL
IAT3025 MEMBER mem NOT FOUND IN dsn
Explanation: The member mem of the indicated data set was not found. The data set was specified in the JES3 procedure. The member was either specified in the JES3 procedure (reply N), specified by the operator (reply M=nn), or defaulted by the system (reply N or M=nn, followed by messages IAT3022 or IAT3023).
System Action: JES3 reissues message IAT3012.
Programmer Response: Verify that the JES3IN DO statement in the JES3 procedure correctly names a valid member.
Operator Response: Specify a member known to exist, or read initialization statements from a card reader.
Problem Determination: See Table· III, items 6 and 21.
Module: IA TINGL
IAT3026 DIRECTORY ERROR SEARCHING FOR mem Explanation: There was a permanent I/O error encountered while searching for the member-name entry in the directory of the JES3IN data set. This message is issued after return code 08 from a BPAM FIND. It is possible that an out-of-storage condition caused the error.
System Action: JES3 reissues message IA T30 12.
Programmer Response: Recreate the data set involved.
Operator Response: Specify the same (N or M=nn) initialization deck member again. If this second attempt fails, specify an alternate member, if one is applicable. You may specify a card deck (U=) if one is available.
Problem Determination: See Table III, items 6 and 21.
Module: IATINGL
IAT3027 IPL REQUIRED FOR WARM OR COLD START Explanation: In reply to message IAT3011, the operator selected a warm start or a cold start, but the IPL of the processor has not been repeated since JES3 was last initialized on this processor. An IPL is required to ensure that JES3 control blocks residing in the common service area (CSA) are rebuilt according to the current initialization statements. Conversely, when CSA is intact (no IPL) during a hot (or local) start, it is not necessary to perform the initialization routines that build those control blocks.
System Action: JES3 reissues message IAT3011.
Operator Response: If a warm start or a cold start must be performed, first repeat the IPL. Otherwise, perform a hot start or local start, as appropriate.
Problem Determination: See Table III, item 6.
Module: IA TINGL
IAT3029 UNABLE TO ALLOCATE ddn dsn
Explanation: A dynamic allocation attempted for the indicated ddname/ dsname combination has not been successful.
System Action: JES3 issues message IA T3030 to detail the reason for the failure. The rest of the DYNALLOC and/or JES3LIB statements in the initialization stream are checked for validity.
Programmer Response: Correct the conditions that caused the allocation to fail. You may have to change only the initialization statement, or you may have to make available a data set or unit that was previously not found. Other MVS messages may have been issued that will help to determine the cause of failure.
Problem Determination: See Table III, items 5, 6, and 21.
Module: IATINGL
IAT3030 RETURN CODE IS rc, REASON CODE IS xxx Explanation: This message details the reason for the failure of the dynamic allocation specified in messages IAT3017, IAT3029, and IAT3031, one of which preceded this message.
See OS/VS2 System Programming Library: Job Management for an explanation of the dynamic allocation return codes and the error reason codes in this message.
System Action: JES3 initialization continues as specified for message IAT30 17, IAT3029, or IA T3031, whichever preceded this message.
Operator Response: None.
Module: IA TINGL
IAT3031 UNABLE TO CONCATENATE ddn
Explanation: A dynamic allocation concatenation function for the indicated ddname has not been successful.
System Action: JES3 issues message IA T3030 to detail the reason for the failure. The rest of the DYNALLOC and/or JES3LIB statements in the initialization deck are checked for validity. JES3 initialization is then terminated.
Programmer Response: Correct the condition that caused concatenation to fail. Other MVS messages may have been issued that will help to determine the cause of failure.
Problem Determination: See Table III, items 5, 6, and 21.
Module: IA TINGL
IAT3032 ILLEGAL mVNALLOC I JES3LIB} CARD Explanation: A DYNALLOC or JES3LIB statement had an invalid keyword. The statement containing the error is duplicated on the operator's console immediately preceding this message.
System Action: The rest of the DYNALLOC and/or JES3LIB statements in the initialization deck are checked for validity.
JES3 initialization is then terminated.
Programmer Response: Correct the statement in error.
Problem Determination: See Table III, items 5 and 6.
Module: IATINGL
IAT3033 CONFIRM JES3 COLD START REQUEST (U) Explanation: The operator replied C to message IAT3011. To operator now must confirm the validity of existing data in the JES3 queue.
System Action: JES3 waits for an operator response.
Operator Response: Reply U to continue with the cold start.
Reply CANCEL to terminate JES3. The queue is left intact.
Any other reply will cause message IA T30 11 to be reissued.
Module: IA TINGL
IAT3034 DVNALLOC CARDS MUST PRECEDE JES3LIB CARDS
Explanation: A DYNALLOC statement is preceded by one or more JES3LIB statements. All DYNALLOC statements must be submitted ahead of the first JES3LIB statement. The out-of-sequence statement is duplicated on the operator's console immediately preceding this message.
System Action: The rest of the DYNALLOC and/or JES3LIB statements in the initialization deck are checked for validity.
JES3 initialization is then terminated.
Programmer Response: Place the DYNALLOC statements ahead of the JES3LIB statements.
Problem Determination: See Table III, items 5 and 6.
Module: IATINGL
IAT3035 CONCATENATION LIMIT EXCEEDED Explanation: An attempt has been made to dynamically concatenate more. than 16 DO statements with the same ddname. The statement card that exceeded the limit is duplicated on the operator's console immediately preceding this message.
System Action: The rest of the DYNALLOC and/or JES3LIB statements in the initialization deck are checked for validity.
JES3 initialization is then terminated.
Programmer Response: Remove the excess statement.
Problem Determination: See Table III, items 5 and 6.
Module: IATINGL
IAT3036 DVNALLOC LIMIT EXCEEDED
Explanation: The DYNALLOC initialization statement limit has been exceeded. The maximum number of DYNALLOC statements allowed is 102.
System Action: JES3 initialization is terminated.
Programmer Response: Remove the excess DYNALLOC statements.
Problem Determination: See Table III, items 5 and 6.
Module: IATINGL
IAT3040 STATUS OF JES3 PROCESSORS IN COMPLEX mpname (status) (,mpname(status) ... )
Explanation: The status of the processors in this complex as last recorded in the complex status record (CSR) is provided for operator information. The first detailed entry pertains to the global processor; an additional entry is included for each JES3 local processor. The parentheses enclosing the status
information are changed to
< >
for the entry pertaining to the processor being initialized and issuing this message. The status field can be as follows:UP
IN DS
blank
the processor has completed initialization
Note: If this value appears for the processor now being initialized, that processor has abnormally terminated since the status was recorded.
the processor has not completed initialization the processor has not completed dynamic system interchange
the processor either has been through normal termination or has never been initialized by JES3 The status is updated at the beginning and end of JES3 initialization and cleared at JES3 termination. The status may be incorrect if normal termination has not been possible (e.g., processor failure) or if an I/O error has precluded complex status record (CSR) update.
System Action: JES3 initialization continues.
Operator Response: None.
Module: IA TINGL
IAT3041 CHECKPOINT DATA SET INVALID OR NOT FOUND. COLD START REQUIRED
Explanation: JES3 initialization has determined that its checkpoint data has either been destroyed or that there is no useful residual data on the CHKPNT data set. A cold start is required;
System Action: JES3 issues message IA T30 11.
Operator Response: The only valid reply to message IAT3011 (issued next) is C (cold start).
Problem Determination: See Table III, items 6, 20, and 21.
Module: IA TINGL
IAT3042 CHECKPOINT DATA SET INVALID.
WARM OR COLD START REQUIRED Explanation: JES3 initialization has determined that its checkpoint data records on the CHKPNT data set are not usable. A warm start or a cold start is required to renew them.
The queue checkpoint records on the CHKPNT data set are probably still valid, permitting a warm start rather than forcing a cold start.
System Action: JES3 issues message IA T30 11.
Operator Response: The only valid replies to message IAT3011 (issued next) are W, WA, WR, WAR, or C.
Problem Determination: See Table III, items 6, 20, and 21.
Module: IATINGL
IAT3043 GLOBAL IS REINITIALIZING CHECKPOINT DATA. DO YOU NEED TO TAKE CONTROL?
(YES NO OR RETRY)
Explanation: JES3 initialization has determined that there is another processor undergoing a warm start or a cold start. This processor cannot be initialized until global initialization has successfully completed. Initialization data for local and hot starts is not available until the end of a successful initialization performed from initialization statements.
System Action: JES3 waits for an operator reply.
Operator Response: Reply NO or CANCEL to terminate JES3.
Reply YES to ignore any other global initialization in process;
message IA T30 11 is then issued. The only valid replies to message IAT3011 (issued next) are W, WA, WR, WAR, or-Co To continue, reply RETRY after the global has successfully completed JES3 initialization. A reply of YES is needed only if JES3 had started a warm or cold initialization and had not successfully completed it. This might be due to hardware or software failure, invalid initialization deck, or operator intervention.
Problem Determination: See Table III, items 5 and 6.
Module: IA TINGL
IAT3044 THIS CPU NOT DEFINED, WARM OR COLD START REQUIRED TO CONTINUE.
DO YOU WISH TO PROCEED? (YES OR NO) Expianation: This processor was not defined by its seriai number on a MAINPROC statement the last time a warm start or cold start was performed for the global processor. Before this
DO YOU WISH TO PROCEED? (YES OR NO) Expianation: This processor was not defined by its seriai number on a MAINPROC statement the last time a warm start or cold start was performed for the global processor. Before this