Interpreter Messages - JES3 Messages

Module: IATIICC

IAT4210 INTERPRETER GOING PERMANENTLY OFFLINE

Explanation: This message is issued in conjunction with message IAT42I2 and usually indicates there is a bad object or load module.

System Action: The interpreter subtask is disabled to prevent recursive abends.

. Programmer Response: Print the stand-alone dumps found in the SYS I.DUMP data set, and resolve the problem.

Operator Response: After the problem is resolved, issue the

*F,X, ... MC command to reset the interpreter DSP maximum count to reschedule and reattach interpreter subtasks.

Problem Determination: See Table I, items 13 and 29; Table III, items 4, 5,6, and 20.

Module: IATIICC

IAT4211 INTERPRETER HAS ABENDED Explanation: One of the interpreter subtasks (C/I) has terminated execution abnormally. The job currently being interpreted is canceled with print from the system, with message IAT4205 in the JESMSG data set.

System Action: The job is terminated.

Programmer Response: Print the dump from the SYS1.DUMP data set and correct the error.

Operator Response: Check for an associated message IAT4210 to find whether an operator response is needed; if so, refer to message IAT421O.

Problem Determination: See Table I, items 13 and 16; Table III, item 20.

Module: IATIICC

IAT4212 INTERPRETER HAS ABENDED ON TWO CONSECUTIVE JOBS

Explanation: The MVS converter/interpreter operating as a subtask of JES3, terminated execution abnormally on a job immediately following a previous abnormal termination. This consecutive abend is treated as a recursion. The specified converter/interpreter is marked offline to JES3, and the job being processed is flushed from the system.

System Action: The job is terminated.

Operator Response: If another converter/interpreter is executing normally, rerun the job that was flushed due to the termination.

Module: IA TIICC

IAT4213 JOB FAILED BY JCLTEST FACILITY Explanation: The user's job called for processing through the JCLTEST facility of the interpreter DSP. That function, having completed processing of the job, is terminated after the interpreter OSP. The job is not passed to MAIN.

System Action: The job is canceled with print.

Operator Response: None.

Module: IA TIIPR

IAT4215 SYSOUT ERROR ... USER-WRITER AND 3540-CLASS/DSID SPECIFIED

Explanation: The job's JCL contains a SYSOUT 00 statement which specifies that 3540 SYSOUT class data will be processed by a non-3540 class writer.

System Action: The job is canceled with print after the interpreter OSP.

Programmer Response: Either correct the JCL to avoid specifying a user-writer or OSlO, or correct the SYSOUT class table so that the class in question is not defined as being held for the reserved writer (3540 class).

Problem Determination: See Table III, items 5 and 20.

Module: IATIICX, IATIICC

IAT4216 SYSOUT ERROR ... DSID SPECIFIED WITH NON-3540 CLASS

Explanation: A SYSOUT 00 statement specifies a OSlO keyword, but the SYSOUT class called for is not 3540.

System Action: The job is canceled with print after the interpreter OSP has completed.

Problem Determination: See Table III, items 5 and 20.

Module: IATIICX, IATIICC

IAT4217 SYSOUT ERROR ... NO DSID SPECIFIED WITH 3540 CLASS

Explanation: JES3 encountered a SYSOUT 00 statement which specified a 3540 SYSOUT class, but which failed to provide the mandatory OSlO information associated with such a class.

System Action: The job is canceled with print following completion of the interpreter OSP.

Programmer Response: Either correct the problem SYSOUT 00 statement and resubmit the job, or correct the JES3 SYSOUT class table by modifying the initialization deck and reinitializing the system.

Problem Determination: See Table III, items 5 and 20.

Module: IA TIICX, IA TIICC

IAT4218 VOLUMES HAVE DIFFERENT MOUNT ATTRIBUTES FOR xxx,yyy, ddn

Explanation: Some volumes defined on the 00 statement were not specified as permanently resident, where xxx is the procedure step name, yyy is the job step name, and ddn is the ddname.

System Action: The job is canceled with print.

Programmer Response: Correct the problem 00 statement, and resubmit the job.

Problem Determination: See Table III, item 5, 14a, 20, and 22.

Module: IATIIPI

IAT4219 JSAM ERROR IN JOB jjj (jobno)

Explanation: A JSAM error occurred while processing the job specified by name and number. An attempt was made to either close or write to the JCBLOCK 00 data set.

System Action: The job is terminated.

Programmer Response: Check the job's JCL for keywords with parameters whose total length is greater than JES3 buffer size--32. Eliminate those which do not need to be specified, then rerun the job.

Operator Response: Rerun the job.

Problem Determination: See Table I, items 13 and 16; Table III, item 5.

Module: IATIIDR, IATIIPO, IATIIP1, IATUP2, IATIICM IAT4220 INTERPRETER DSP FAILSOFT IN PROCESS Explanation: A system abend occurred in the interpreter OSP while the job was running.

System Action: The job is terminated. This message is for programmer information only. A system dump has been taken, and the interpreter will reinstate itself.

Operator Response: Hold the dump for the system programmer.

Problem Determination: See Table I, items 13 and 16; Table III, item 5.

Module: IA TIIDR

IAT4225 JOB jjj(jobno) WITH nnn DD STATEMENTS EXCEEDED THE ISYSTEM

I

JOB I DD LIMIT OF mmm DD STATEMENTS. JOB CANCELLED Explanation: The job jjj(jobno) includes the indicated number of OD statements (nnn). This count exceeds the system or job limit of mmm DO statements.

System Action: Job jjj(jobno) is cancelled. Other processing continues.

Operator Response: None.

Programmer Response: Restructure the job into multiple jobs or a DJC network; or see the system programmer about having the DD statement limits modified.

Module: lATIICC

IAT4230 JOB jjj(jobno) WITH nnn DD STATEMENTS EXCEEDED THE AVAILABLE VIRTUAL STORAGE. JOB CANCELLED

Explanation: The job jjj(jobno) includes the indicated number of DD statements (nnn). The job passed all DD statement limit checks but sufficient virtual storage was not available for the MVS interpreter to process the job.

System Action: Job jjj(jobno) is cancelled. Other processing continues.

Operator Response: None.

Programmer Response: Restructure the job into multiple jobs or a DJC network. Notify the system programmer.

System Programmer Response: The DD statement limits are set too high. The system limit should be lowered to correspond to the actual virtual storage available. The JES3 address space may be in a critical storage situation. System activity and/or storage utilization should be reduced.

Module: lATIICC

IAT4300 ATTEMPT TO PASS DUPLICATE DATA SET NAME WITHIN SAME STEP - JOB FAILED Explanation: An error was encountered while processing the DISP=(NEW,PASS) parameter on a JCL DD statement.

System Action: The job is terminated.

Programmer Response: This is probably a JES3 error. Invoke the interpreter debug facility and rerun the job with

DEBUG=ALL specified. See JES3 System Programming Library: Diagnosis.

Module: IA TIIPR

IAT4301 UNIT TYPE PARAMETER FOR xxx,yyy, ddn NOT VALID - JOB FAILED

Explanation: The UNIT= keyword on the indicated DD statement did not include a valid unit parameter, and the job failed, where xxx is the procedure step name, yyy is the job step name, and ddn is the ddname.

Possible reasons why the unit specified was not valid are:

The UNIT parameter was not specified when one is required (for example, when defining a new data set).

The same volume serial number was given for two unlike devices in the job. For example, one DD statement called for the volume serial on a tape while another DD statement used the same volume serial for a DASD request. One of the DD statements is treated as invalid.

System Action: The job is terminated.

Programmer Response: Supply a valid unit type on the indicated DD statement and rerun the job.

Problem Determination: See Table III, items 1 14a, 20, and 22;

Table I, item 3.

Module: IA TIIPR, IA TIIP 1

IAT4330 UNABLE TO RESOLVE UNIT/VOLUME(S) FOR xxx,yyy, ddn

Explanation: The required unit or volume information for a temporary data set name was not available either on the statement, where xxx is the procedure step names, yyy is the job step name, and ddn is the ddname, or passed from

a

^DD

statement in a previous step. Since the temporary data set name is not cataloged, the job is failed during the prescan phase of the CI DSP to avoid unnecessary LOCATE processing.

This is probably a user error. Either the DISP parameter on the JCL DD statement was erroneously coded (implying the presence of a nonexistent temporary data set) or the job may consist of a series of conditionally executed steps, one of which may have terminated the passing of the data set name. Since JES3 does not consider conditional steps when determining setup requirements, the passing of the data set inay appear to be prematurely terminated.

System Action: The job is terminated.

Programmer Response: Correct the DISP parameter on the DD statement or make provisions to circumvent the conditional step restriction using the JES3 user exit facility or DJC facility.

Problem Determination: See Table I, items 1 and 15; Table III, item 23.

Module: IA TIIPR

IAT4401 LOCATE FOR STEP=stepname, DD=ddn DSN=dsn

Explanation: The ALOCA TE macro instruction issued for the specified data set name dsn was executed against the catalog.

System Action: Message IA T4402 is issued.

Programmer Response: None.

Module: IA TIIPO

IAT4402 UNIT=devname, VOL(S)=

J

vol(,vol)... } ) N/ A: UNIT NOT JES3

Explanation: The LOCATE for data specified in message IAT4401. If the unit is not a JES3-managed device, the volume serial numbers will be replaced by the phrase: N/ A: UNIT NOT JES3.

System Action: Not applicable.

Programmer Response: None.

Module: IA TIPO

IAT4403 SPECIFIED VOLUME SEQUENCE INVALID FOR xxx,yyy, ddn

Explanation: A volume sequence number has been specified which exceeds the number of volume serials given for the statement specified where xxx is the procedure step name, yyy is the job step name, and ddn is the ddname.

System Action: The job is terminated.

Programmer Response: Change the JCL to eliminate the inconsistency, and resubmit the job.

Problem Determination: See Table III, items 14a, 20, and 22;

Table I, item 3.

Module: IA TIIPR

IAT4404 DATA SET NOT FOUND ON MAIN PROCESSOR mpname

Explanation: The data set in the preceding message IAT4401 was not found on the indicated processor mpname (refer to the job listing).

If the Hierarchical Storage Manager (HSM) is in the system, one of the following may have occurred:

A VSAM data set that was eligible only for command migration was migrated.

A VSAM data set was migrated automatically, but there was an error in the migration of the data set. Therefore, the data set is not eligible to be automatically recalled.

System Action: The job is canceled with print.

Programmer Response: Make the necessary corrections and resubmit the job. If a VSAM data set was migrated automatically and HSM is in the system, a command recall of the data set must occur before the data set can be used. When an HSM-managed VSAM data set was automatically migrated but there was an error, do one of the following:

Access the data set by the base cluster name and it will be automatically recalled.

Do a command recall on the base cluster name.

Issue an HLIST OAT ASETNAME base cluster name SELECT VSAM command.

Problem Determination: See Table III, items 14a, 20, and 22.

Module: IA TIl PO

IAT440S LOCATE ERROR ENCOUNTERED ERROR INLOC INPUT DATA RC=nn PASSWORD FAILURE

REQUEST ABORTED

I/O ERROR SEARCHI~~ CATALOG NO UNIT TYPE AVAILABLE DSN NEEDS CVOL

CATALOG ALLOCATE ERROR GDG SPECIFIED IN DCB PARM

HSM CATALOG LOCATE ERROR RA=nn HSM ERROR OCCURRED RA=nn

Explanation: An error occurred during LOCATE processing for the data set indicated by the preceding message, IAT4401. For specific error texts, see individual explanations below.

System Action: The job is canceled with print.

Programmer Response: See programmer response under individual error texts below.

Module: IA TIIPO issues the message. See individual error texts below to determine the JES3 module that originally set or detected the error.

ERROR IN LOC INPUT DATA RC=nn

Explanation: See the values and meanings of the return code as follows:

Return Code FF

FA, FB, FC, or FD

Meaning

Problems in L VS (the data set name locate table) such as invalid data set name, or the L VS entry was not found.

(Module: IATIIPR)

LET chain (locate entrance table) problems. (Module: IATIIPO) JES3 was unable to resolve assignments for multi-volume, multi-unit returns from catalog management. (Module: IA TL VLC) Programmer Response: Consult the system programmer.