$HASP100

Explanation

A JOB statement has been detected in the input stream from the indicated device, and JES2 has assigned the associated job a JES2 job identifier. The programmer name is displayed if it was specified on the JOB statement. In the message, text is one of the following:

jobid jobname
userid at nodename

In the message:

jobname: The name that appears in the name field of the JOB JCL statement.
devname: The name of the device on which this job entered the system. If the device name is INTRDR, this message also displays ijobid and ijobname.
programmer: The programmer name that appears in the NAME field of the JOB JCL statement.
ijobid: The identifier of the job that is submitting jobname. This information is displayed only if the device name is INTRDR, and the submitter has a job identifier. If the submitter does not have a job identifier, N/A is displayed.
ijobname: The name of the job that is submitting this job. This information is displayed only if the device name is INTRDR.
userid: The TSO/E user ID that originated this job. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the user ID that originated this job, this field displays *UNKNOWN.
nodename: The name of the node from which this job originated. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the node from which this job originated, this field displays *UNKNOWN.

Note: A job identifier may precede HASP100. See JES2 message format.

System action

Processing continues.

Operator response

None.

System programmer response

None.

Module

HASPRDR, HASCINJR, HASCNJJR

Routing Code: 7

Descriptor Code: 4

$HASP101

Explanation

The indicated job has been placed in JES2 HOLD status for one of the following reasons:

The JOB statement specified TYPRUN=HOLD. Check to see if the job card specified TYPRUN=HOLD.
The JOB statement specified TYPRUN=JCLHOLD. Check to see if the job card specified TYPRUN=JCLHOLD.
The device from which the job was read was set to HOLD all jobs. Run the $D command with the input device to see if HOLD=YES is specified.
The class of the job has been set by JES2 initialization parameters such that all jobs that are entered in that class are held. Run the $D JOBCLASS command with the initial class that was specified for the job to see if HOLD=YES was specified.
The job had a /* SETUP JCL control statement. Check to see if the job card specified a /* SETUP control card.
HOLDUNTL keyword on the SCHEDULE statement was used to specify a time in the future when the job should be released. Job is held until the specified time or until the job is released.

In the message text:

jobname: The name of the held job.

Note: A job identifier may precede HASP101. See JES2 message format.

System action

Processing continues on other jobs.

Operator response

Determine the reason the job was placed in JES2 HOLD status. When appropriate, release the job for further processing.

System programmer response

None.

Module

HASPCNVT

Routing Code: 1,2

Descriptor Code: 4

$HASP102

Explanation

The indicated job has been placed in HOLD status by the JES2 input service because a /*SETUP control statement was encountered. The text of the control statement is displayed with accompanying HASP103 messages.

In the message text:

jobname: The name of the held job.

Note: A jobid may precede HASP102. See JES2 message format.

System action

The system continues processing and holds the job on the execution queue.

Operator response

Ensure that the requested volumes are available to be mounted, and release the job.

System programmer response

None.

Module

HASCSRIP

Routing Code: 1–6

Descriptor Code: 4

$HASP103

Explanation

The indicated job has been placed in HOLD status by the JES2 input service pending availability of the volumes indicated by volser,...,volser.

In the message text:

jobname: The name of the held job.
volser ,..., volser: The one to eight character volume identifier of the volumes.

Note: A jobid may precede HASP103. See JES2 message format.

System action

The job is placed in JES2 HOLD status, and input processing continues.

Operator response

Ensure that the requested volumes are available to be mounted and release the job.

System programmer response

None.

Module

HASCSRIP

Routing Code: 1–6

Descriptor Code: 4

$HASP104

Explanation

The input service processor has detected a /*MESSAGE control statement or an //*OPERATOR control statement in the input stream.

In the message text:

jobname: The name of the job.
devname: The name of the device.
text: The text of the /*MESSAGE control statement or the //*OPERATOR control statement.

Note: A jobid may precede HASP104. See JES2 message format.

System action

Processing continues.

Operator response

Respond to the message accordingly.

System programmer response

None.

Module

HASCSRIP

Routing Code: 1–6

Descriptor Code: 4

$HASP105

Explanation

In a line of a JCL statement, the system found either a non-blank character in column 72, or a comma at the end of the last operand, and expected a continuation on the next line. A continuation begins with //. Instead, the next line began with /*.

In the message text:

jobname: The name of the job.

System action

Input servicing for jobname terminates.

Programmer response

If the continuation line is missing, provide it.

If the continuation line is present, but mistakenly begins with /*, correct it to begin with //.

If no continuation was intended, correct the first line so that column 72 is blank, and the last operand ends with a blank.

Module

HASPRDR, HASCINJR, HASCNJJR

Routing Code: 7

Descriptor Code: 4

$HASP106

Explanation

JES2 places this message in the job log:

If the jobname contained a JECL error
The operator canceled the job before the jobname processed.

In the message text:

jobname: The name that appears in the name field of the JOB JCL statement.

Note: A job identifier may precede HASP106. See JES2 message format.

System action

Processing continues.

Operator response

None.

System programmer response

None.

Module

HASPHOPE

Routing Code: –

Descriptor Code: –

$HASP107

Explanation

While parsing JCL statements, JES2 detected an error on the xxxxxxxx statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.
statement: The JCL statement affected.

reason is one of the following:

KEYWORD LENGTH NOT VALID: A keyword longer than 8 characters was encountered.
VALUE FOR xxxxxxxx KEYWORD NOT VALID: The value for the keyword listed is syntactically not valid (for example, unbalanced parentheses or apostrophes might exist).
UNEXPECTED KEYWORD DETECTED – xxxxxxxx: An unknown keyword was encountered on the statement.
UNEXPECTED POSITIONAL OPERAND DETECTED: A positional operand was encountered where one was not expected. Typically this is caused by a missing '=' or improper apostrophes.
VALUE FOR POSITIONAL OPERAND NOT VALID: A syntactically invalid positional operand was detected.
value for DLM keyword not valid: The syntax of the delimiter keyword value is incorrect.
operand field does not terminate in comma or blank: Operand field must terminate with a comma or blank.
Continued quote starts before column 16: Continuation of a quoted string must start in column 16.
Cannot have continued quote on same card as PASSWORD=: Quoted strings coded on the same card image as the PASSWORD= parameter, cannot be continued. If string value requires continuation, move quoted string to a different card image - that does not have PASSWORD= parameter coded.

Note: A job identifier may precede HASP107. See JES2 message format.

System action

The message is written to the JCL data set and JES2 ends input service processing for the job. The job is queued for output processing.

Operator response

None.

Programmer response

See z/OS MVS JCL Reference for correct forms of the listed statement. Correct the JCL error and rerun the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP108

Explanation

While parsing JCL statements, JES2 detected an error on the XMIT statement. The problem encountered is identified by reason. In the message text:

JOB name: The name of the affected job.

The reason is defined as one of the following:

operand field does not terminate in comma or blank: Operand field must terminate with a comma or blank.
DEST keyword error, RC=1: The DEST= keyword specified null destination.
no operand supplied, RC=2: No operands were specified on the //XMIT card. The DEST= keyword is required.
DEST= value in error, RC=3: The DEST= keyword specified a destination that was not valid.
delimiter error, RC=4: Error processing DLM= parameter.
NON-VALID CONTINUATION, RC=5: A continuation that is not valid was detected.
UNEXPECTED KEYWORD DETECTED, RC=6: An unsupported or unrecognized keyword was detected.
DEST keyword missing, RC=7: DEST= keyword is required but not found.
duplicate DEST keyword, RC=8: Multiple DEST= keywords detected
duplicate DLM keyword, RC=9: Multiple DLM= keywords detected.
placement in JCL is not correct, RC=10: An XMIT statement must be placed after the JOB card and before any other JCL/JECL statements, except comments. This did not occur in the affected job stream.

System action

The message is written to the console and to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion, unless the message is a warning only.

Operator response

None.

Programmer response

See z/OS MVS JCL Reference for the correct format of the //XMIT JCL statement. Correct the statement and rerun the job.

Module

HASPRDR, HASCINJR, HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP109

Explanation

The JECL/JCL installation exit routine (Exit 4/54) has notified the input service processor that it has detected an illegal control statement. The installation may use the exit routine to replace the text of this message.

In the message text:

jobname: The name of the job.

Note: A jobid may precede HASP109. See JES2 message format.

System action

JES2 ends input service processing for the job.

Programmer response

See z/OS MVS JCL Reference for the correct format of the control statement in error. Correct the control statement and resubmit the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP110

Explanation

Operator console form:

JESYSMSG message form:

While parsing JCL and JECL statements, JES2 detected an error on the JOB JCL statement or MAIN JES3 JECL statement. The problem encountered is identified by reason. In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

account field incorrect

JES2 requires both an account number and a room number. This requirement is due to the ACCTFLD=REQUIRED on the JOBDEF initialization statement. Check for a missing or incorrect account number or room number.

ERROR DETECTED BY EXIT nnn OR error detected by exit nnn

The listed exit has detected an error on the JOB statement. See processing in that exit to determine the cause of the error.

Illegal job card - Multiple job/jobgroup cards detected

Under normal conditions, multiple job/jobgroup statements are allowed. For example, they are allowed from an internal reader (a SUBMIT from ISPF EDIT). However, JES2 does not permit multiple job/jobgroup statements in the following situations:

An NJE job stream from VM RSCS or from another JES2 node that uses /*XMIT.
Started jobs that use IEFJOBS support, where only one JOB card is permitted in the started member.

If the problem is a started job, for example, and this message is preceded by HASP100 ON STCINRDR, see z/OS MVS JCL Reference for more information.

Illegal JOB card - password and pass phrase are mutually exclusive

Old password can only be replaced by a new password. Similarly, old password phrase can only be replaced by a new password phrase.

Illegal JOB card - user identity for the job already set

After the owner of a job is defined, it can no longer be changed by another JCL, JECL statement, or keyword.

Illegal JOB card - SYSTEM and SYSAFF cannot both be specified

SYSTEM= and SYSAFF= are mutually exclusive keywords.

Illegal JOB card - dddddddd specified more than once

dddddddd has been specified more than once.

Illegal JOB card - dddddddd not valid, begins with "-" on second or later value

"-" is allowed only before the first dddddddd.

Illegal JOB card - dddddddd of -ANY not valid

It is not valid to remove all members from dddddddd by using "-ANY".

JOB statement warning - SYSTEM= names JGLOBAL and JLOCAL are ignored

JGLOBAL and JLOCAL are used in a JES3 environment. They are tolerated in a JES2 environment but provide no function. This situation results in one of the following:

The message ID and the reason text are the only text written.
The message appears only in the JESYSMSG data set.
The condition is treated as a warning, not an error.

Illegal JOB card - SYSTEM= names JGLOBAL and JLOCAL must not appear with other names

The JES3 generic names of JGLOBAL and JLOCAL cannot be specified with other SYSTEM names.

Illegal JOB card - dddddddd invalid, begins with "-" on second or later value

"-" is allowed before only on the first member name.

Illegal JOB card - password and pass phrase are mutually exclusive

The password and pass phrase cannot be specified more than once.

Illegal JOB statement - JOB class cccccccc is not active

The job class used for the job by default is not active.

Illegal JOB statement - JOB class cccccccc is not valid

The job class used for the job by default is not valid.

INVALID JOB CARD - INVALID SCHENV VALUE

The value provided for SCHENV is not valid.

MULTIPLE cccccccc CARDS SPECIFIED

cccccccc cards has been specified more than once.

cccccccc VALUE CANNOT MATCH JOB NAME

Card name cccccccc cannot match the job name.

INVALID /*CNTL CARD -- BAD RESOURCE NAME

The resource name is bad for the control card.

INVALID /*CNTL CARD -- SECOND POSITIONAL MUST BE SHR OR EXC

The second positional operand on a /*CNTL CARD statement must be SHR or EXC.

INVALID /*BEFORE CARD

The /*BEFORE card is not valid. Check to see if the correct name was specified.

MULTIPLE /*BEFORE CARDS SPECIFIED

Multiple /*BEFORE cards detected.

/*BEFORE VALUE CANNOT MATCH JOB NAME

The /*BEFORE card value cannot match the job name.

value of accounting string is too long

The accounting string positional operand is longer than the maximum value allowed.

value of programmer name is too long

The programmer name positional operand is longer than the maximum value allowed.

value of keyword= exceeds n characters

The value provided for the specified keyword exceeds the maximum value allowed.

value of keyword= has too many operands

The specified keyword is a list for which too many values have been specified.

value of keyword= parameter is greater than nnn

The specified keyword has a value larger than the maximum allowed for the keyword.

value of keyword= parameter is not numeric

The specified keyword is required to be numeric.

value of EMAIL= parameter is not valid

Length of the value provided for EMAIL= parameter is incorrect.

value of USER= parameter is not valid

The specified keyword has a value longer than the maximum allowed for the keyword.

value of USER= exceeds 8 characters

The value provided for the specified keyword is not valid.

value of keyword= parameter is not valid

The value provided for the specified keyword is not valid.

value of keyword= parameter is null

The specified keyword cannot be specified as null.

value of CLASS= parameter is an inactive class

The specified class is not valid because the class is inactive.

JOB CLASS FAILED AUTHORIZATION

Job submitter or job owner is not authorized to submit jobs for the job class specified for this job.

Value of UJOBCORR has embedded blanks

The user portion of the job correlator cannot contain embedded blanks, and an embedded blank was provided.

Value of UJOBCORR has invalid characters

The user portion of the job correlator contains characters other than alphanumeric, national (@, #, $), or underscore (_) characters.

Value of UJOBCORR has greater than 32 characters

The user portion of the job correlator is limited to 32 characters, and more than 32 characters were supplied.

default class cccccccc is not valid

The job class used for the job by default is not valid.

default class cccccccc is not active

The job class used for the job by default is not active.

value of CLASS= parameter is not valid

The specified job class is not valid.

value of CLASS= parameter is an inactive class

The specified job class is not active.

keyword= not valid for this job type

The keyword, and value, are not allowed for a started task.

SYSTEM and SYSAFF cannot both be specified

SYSTEM= and SYSAFF= are mutually exclusive keywords.

SYSTEM specified more than once

SYSTEM= cannot be specified more than once.

SYSAFF not valid, begins with "-" on second or later value

"-" is allowed only before the first member name.

SYSAFF of –ANY not valid

It is not valid to remove all members from SYSAFF by using "-ANY".

SYSTEM= names of JGLOBAL and JLOCAL must not appear with other names

The JES3 generic names of JGLOBAL and JLOCAL cannot be specified with other SYSTEM names.

SYSTEM of –ANY not valid

It is not valid to remove all systems from consideration by using "-ANY".

SYSTEM not valid, begins with "-" on second or later value

"-" is allowed only before the first system name.

SYSTEM= values of JGLOBAL and JLOCAL are ignored

JGLOBAL and JLOCAL are used in a JES3 environment. They are tolerated in a JES2 environment, but provide no function. This situation results in:

The message ID and the reason text are the only text written.
The message appears only in the JESYSMSG data set.
The condition is treated as a warning, not an error.

SYSTEM= not valid for this job type

SYSTEM keyword is not valid for started tasks (STC) and TSO jobs.

Operand field does not terminate in comma or blank

Operand field must terminate with a comma or blank.

Unable to access JCT extension

JES2 processing failed when it attempted to access a JCT extension.

unable to map EMAIL to USER: System cannot map email address provided on EMAIL= keyword to a user identifier.

Note: A jobid can precede HASP110. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion, unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for information about coding JOB statements. Correct the JOB statement or remove the additional job cards and resubmit the job.

Module

HASCINJR, HASCSRIP, HASPRDR

Routing Code: 7

Descriptor Code: 4

$HASP111

Explanation

While parsing JCL statements, JES2 detected an error on the /*ROUTE statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

destination not valid: The destination that is specified on the /*ROUTE statement is not valid, or this user does not have access to the destination.
missing positional operand: The destination operand was not specified.
not valid for this job type: A ROUTE XEQ card was specified for a started task.
PRINT, PUNCH, OR XEQ required: The first positional operand on a /*ROUTE statement must be one of the values listed.
//*NET card must follow /*ROUTE XEQ card: A //*NET card was found before a valid /*ROUTE XEQ card. Any //*NET cards must be placed after the /*ROUTE XEQ card.
Placement in JCL is not correct: The //*ROUTE XEQ JECL statement must be placed after a job card but before any other JCL statements. Some other JCL statement (other than a comment) was detected before the //*ROUTE XEQ statement.
XEQ required: The first positional operand on a //*ROUTE statement must be XEQ.

Note: A jobid can precede HASP111. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for correct forms of the /*ROUTE statement. Correct the JCL error and rerun the job.

Module

HASCINJR, HASCSRIP, HASPRDR

Routing Code: 7

Descriptor Code: 4

$HASP112

Explanation

While parsing JECL statements, JES2 detected an error on the /*JOBPARM JES2 JECL statement or //* MAIN JES3 JECL statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

reason is one of the following:

JOB CLASS FAILED AUTHORIZATION

The supplied job class did not pass the authorization check.

SECURITY AUTHORIZATION FAILURE FOR JOB CLASS

The supplied job class did not pass the authorization check.

keyword= not valid for this job type

The keyword, and value, is not allowed for a started task.

unknown positional operand

A positional operand was encountered that was not recognized.

value of keyword= EXCEEDS nnnnnnnn

The numeric value provided for the specified keyword exceeds the maximum value allowed for the keyword.

value of keyword= exceeds n characters

The character values provided for the specified keyword is longer than the maximum allowed length.

value of keyword= must be Y or N

The only allowed values for the specified keyword are 'Y' or 'N'.

value of keyword= parameter is not valid

The value provided for the specified keyword is not allowed. It might be that the value is null and the keyword requires a value.

PROCLIB in prior /*JOBPARM statement not valid if PROCLIB also on JCLLIB statement

PROCLIB= can be specified on the /*JOBPARM statement or on the JCLLIB statement, but not both.

Not valid to specify PROCLIB if also specified in JCLLIB statement

PROCLIB= can be specified on the /*JOBPARM statement or on the JCLLIB statement, but not both.

SYSAFF not valid, begins with "-" on second or later value

"-" is allowed before only on the first member name.

SYSAFF of – ANY not valid

It is not valid to remove all members from SYSAFF by using "-ANY".

Value of keyword= ignored – prior value used

The value provided for the specified keyword was provided earlier on a prior JCL or JECL statement. The prior value is used. The value from the current statement is ignored. This situation results in:

The message ID and the reason text are the only text written.
The message appears only in the JESYSMSG data set.
The condition is treated as a warning, not an error.

SYSAFF ignored because SYSAFF or SYSTEM specified on JOB card

The value provided for SYSAFF has been ignored because SYSAFF or SYSTEM was specified on the JOB card. This situation results in:

The message ID and the reason text are the only text written.
The message appears only in the JESYSMSG data set.
The condition is treated as a warning, not an error.

value of PROC= parameter is not valid

PROC= keyword must specify two character suffix of PROCxx DD statement used during invocation of JES2 subsystem.

Invalid /*JOBPARM card - cccccccc specified when dddddddd specified on JOB card: The value provided for cccccccc has been ignored because dddddddd was specified on the JOBPARM card.
Invalid /*JOBPARM card - cccccccc not valid, begins with dddddddd on second or later value: cccccccc is allowed only before the first member name.
Invalid /*JOBPARM card - cccccccc of dddddddd not valid: The value provided is not valid.
Invalid JOB statement - cccccccc of dddddddd not valid: The job class used for the job by default is not valid.
Invalid JOB statement - cccccccc invalid, begins with dddddddd on second or later value: cccccccc is allowed only before the first member name.
Invalid JOB statement - cccccccc specified when dddddddd specified on JOB card: The value provided cccccccc has been ignored because dddddddd was specified on the JOB card.
Invalid JOB statement - cccccccc names JGLOBAL and JLOCAL must not appear with other names: The JES3 generic names of JGLOBAL and JLOCAL cannot be specified with other SYSTEM names.
Invalid JOB statement - cccccccc and dddddddd cannot both be specified: cccccccc and dddddddd are mutually exclusive keywords.
Invalid JOB statement - cccccccc specified more than once: cccccccc is specified more than once.
Second cccccccc statement ignored: The second cccccccc statement is ignored by JES2. It is flagged by the converter as an error.
Value of cccccccc ignored - value from JOB statement used: The request is ignored and the value from the JOB statement is used.
cccccccc names JGLOBAL and JLOCAL are ignored: The cccccccc names of JGLOBAL and JLOCAL cannot be specified with other SYSTEM names.
Invalid JECL card - PROCLIB/PROC in prior JECL statement not valid if PROCLIB also on JCLLIB statement: PROCLIB= or PROC= can be specified on the /*JECL statement or on the JCLLIB statement, but not both.
Invalid cccccccc card - Value of dddddddd not a valid destination: dddddddd is not a valid destination.

A jobid can precede HASP112. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for correct forms of the /*JOBPARM statement. Correct the control statement and resubmit the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP113

Explanation

While parsing JCL statements, JES2 detected an error on the /*OUTPUT statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

The reason text is one of the following strings:

incorrect code value: The code value specified is not valid (too long or invalid characters).
incorrect continuation: An attempt to continue an OUTPUT statement was made but no previous output statement exists for the job.
value of keyword= exceeds nnnnnnnn: The numeric value provided for the specified keyword exceeds the maximum value allowed for the keyword.
value of keyword= exceeds n characters: The character values provided for the specified keyword are longer than the maximum allowed length.
value of keyword= has too many operands: The specified keyword is a list for which too many values have been specified.
value of keyword= must be Y or N: The only allowed value for the specified keyword is 'Y' or 'N'.
value of keyword= parameter is not valid: The value provided for the specified keyword is not allowed. It is possible that the value is null and the keyword requires a value.

Note: A jobid can precede HASP113. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for correct forms of the /*OUTPUT control statement. Correct the control statement and rerun the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP114

Explanation

While parsing JCL statements, JES2 detected an error on the /*XEQ or /*ROUTE XEQ statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

execution node not valid: The node specified on the XEQ statement is not a valid NJE node or DESTID of a valid node.
missing positional operand: The required node name operand was not specified on the JCL statement.

Note: A jobid can precede HASP114. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for the correct format of the /*XEQ control statement. Correct the control statement and rerun the job.

Module

HASCINJR, HASCSRIP, HASPRDR

Routing Code: 7

Descriptor Code: 4

$HASP115

Explanation

While parsing JCL statements, JES2 detected an error on the /*NETACCT statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

value of account exceeds 8 characters: The network account number specified is more than 8 characters in length.
missing positional operand: The required network account number was not specified on the NETACCT statement.

Note: A jobid can precede HASP115. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for the correct format of the /*NETACCT control statement. Correct the control statement and resubmit the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP116

Explanation

While parsing JCL statements, JES2 detected an error on the /*NOTIFY statement. The problem encountered is identified by reason.

In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

destination not valid: The notify destination specified is not valid.
missing positional operand: The required notify destination was not specified on the NOTIFY card.

Note: A jobid can precede HASP116. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion unless the message is just a warning.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for the correct format of the /*NOTIFY control statement, correct the control statement and rerun the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP117

Explanation

The input service processor encountered an error when writing Job Symbol Table (JSMT) to SPOOL.

In the message text:

jobname: The name of the affected job.

System action

The message is written to the job log data set and JES2 ends input service processing for the job. The job is queued for output processing.

Operator response

Try to resubmit the job. Report this problem to the system programmer.

Programmer response

Contact the IBM® Support Center.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP118

Explanation

The input service processor has detected an unrecognizable JECL control statement.

In the message text:

jobname: The name of the affected job.

Note: A jobid can precede HASP118. See JES2 message format.

System action

JES2 ends input service processing for the job.

Programmer response

See z/OS MVS JCL Reference for the correct format of the control statement in error. Correct the statement and resubmit the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP119

Explanation

The input service processor has deleted the indicated job. The cause for the deletion may be that the operator entered a command to cause the deletion or an error may have been encountered while inputting the job (for example, if JESYSMSG could not be created). When input errors are encountered, a previously displayed message details the nature of the error. In addition to previous messages, text, if present, describes the reason for the deletion.

In the message text:

jobname: The name of the affected job.

text is one of the following:

ILLEGAL JOB CARD, RC=1: The JOB statement was found to be incorrect by the input service processor.
ILLEGAL CONTROL CARD (EXIT 4/54), RC=2: The JECL/JCL installation exit routine (Exit 4/54) has notified the input service processor that it has detected an illegal control statement.
MISSING CONTINUATION, RC=3: On an input JCL line, the input service processor found either a non-blank character in column 72 or a comma at the end of the last operand and the following input JCL line began with a /*.
/*DEL or /*PURGE JECL, RC=4: The input service processor detected a /*DEL or /*PURGE JECL statement in a JCL stream from an internal reader.
Note: JES2 generates a /*DEL if MVS closes an open internal reader data set on behalf of an ABENDing TCB.
OPERATOR COMMAND, RC=5: An operator command was issued against the job in input processing that requested the job to be deleted.
INTERNAL PROCESSING ERROR, RC=6: An internal logic error was detected by the input service processor.
I/O ERROR, RC=7: When attempting to read the JCL stream for a job, the input service processor detected an I/O error.
ILLEGAL JECL CARD, RC=8: The input service processor detected an error on a JECL card.
ILLEGAL EXECUTION NODE, RC=9: The input service processor detected an incorrect execution node for a JOB.
EXCESSIVE SYSIN STATEMENTS, RC=10: The job being processed by the input service processor has more SYSIN data sets than can be represented within the total number of buffers available on this member.
DEVICE CANCELLED OR STOPPED, RC=11: The input service processor has detected that the associated device has been canceled or stopped. This may be the result of an operator command or a request by the device to terminate processing.
ILLEGAL JOB CARD ACCT FIELD, RC=12: The input service processor detected that the accounting information on the job card is missing or incorrect.
SECURITY PROCESSING ERROR, RC=13: An internal logic error was detected by the input service processor while attempting to perform security validation.
NJE PROTOCOL ERROR, RC=14: The input service processor detected a violation of the NJE protocol.
NON-VALID // XMIT CARD, RC=15: The input service processor detected an error on a // XMIT JCL card.
NON-VALID // DD DATA CARD, RC=16: The input service processor detected an error in a // DD DATA JCL statement.
Error writing job symbols, RC=17: The input processor encountered an error when writing job symbols to SPOOL.
Continuation error on JOBGROUP card, RC=18: The input processor detected invalid continuation syntax used on a JOBGROUP card.
JECL card not allowed, RC=19: The input processor encountered a JECL card in the JCL stream for the job, for which the JECLDEF command/initialization statement specifies action FAIL.

Note: A jobid may precede HASP119. See JES2 message format.

System action

The job is routed to the print phase for appropriate action and then purged.

Operator response

Report this message to the system programmer.

Programmer response

Correct the problem as appropriate and resubmit the job.

Module

HASCINJR, HASCSRIP, HASPRDR

Routing Code: 7

Descriptor Code: 4

$HASP120

Explanation

The displayed command has been entered from the device indicated.

In the message text:

devname: The name of the device from which the command was entered.
cmd: The text of the entered command.
jobid: If the command was submitted from an internal reader (devname is INTRDR), this is the jobid of the job that allocated the internal reader (submitter of the command).
jobname: If the command was submitted from an internal reader (devname is INTRDR), this is the jobname of the job that allocated the internal reader (submitter of the command).

System action

The command is passed to the JES2 command processor for the further action.

Operator response

None.

Module

HASPRDR, HASCINJR, HASCNJJR

Routing Code: 7,8

Descriptor Code: 4

$HASP121

Explanation

The device (either a JES2 job receiver or SYSOUT receiver) detected an error in the NJE header of the specified type. RC=rc contains a reason code that indicates why JES2 rejected the header or trailer.

In the message text:

jobname: The name of the job containing the error.
device name: The JES2 job receiver or the JES2 SYSOUT receiver.
rc: The reason code indicating why JES rejected the header or trailer.

The return codes:

00: The complete header could not be created because of a line error or record sequencing error. A symptom record ($SYMREC) is not issued for this error.
04: The length of the header/trailer exceeds the maximum allowed by JES2.
08: The first section of the header or trailer is not the general section.
12: JES2 processing found a section with a length of less than 4 in the header or trailer.
16: The sum of the length of the header and trailer sections does not equal the total header length.

Note: A jobid may precede HASP121. See JES2 message format.

System action

The indicated job is deleted from this JES2 member. JES2 processing sends a negative response to the sending system, which should cause the job to be held there. A symptom record ($SYMREC) might be written to the LOGREC data set to capture significant information in this header/trailer.

System programmer response

If other systems communicating with JES2 have specified their headers and trailers correctly, a hardware problem can be the only other cause for this message.

Module

HASPNET

Routing Code: 1,2,10

Descriptor Code: 4

$HASP122

Explanation

The specified job has been received at the node where the job runs. This message is displayed to the TSO/E or VM/RSCS user if either the NOTIFY parameter is specified on the JCL JOB statement or the JECL /*NOTIFY statement is specified.

The fields displayed in the message and their meanings are:

jobname: The job name.
jobid: The jobid at the input node.
nnnnnnnn: The input node for this job.
nodename: The node where the job runs.

Note: A jobid may precede HASP122. See JES2 message format.

System action

Processing continues.

Operator response

None.

System programmer response

None.

Module

HASCNJJR, HASPRDR

Routing Code: 7

Descriptor Code: 4

$HASP123

Explanation

In the NJE header for the specified job, an incorrect combination of password, new password, and password encryption bits were set.

One of the following 2 conditions exist:

The bit indicating that the new password is encrypted is set but the bit for the old password is not.
The bit indicating that the old password is encrypted is set and the corresponding bit for the new password is not set, and a new password is present in the header.

In the message:

nodeid: The origin node for this job.

System action

JES2 ends input service processing for the job.

Operator response

Report this message to the local system programmer and to the node which originated the job.

System programmer response

Inform the origination node that the network headers created at that node do not conform to NJE protocols. The origin node can de-activate password encryption until the problem is resolved.

Module

HASCINJR, HASPRDR

Routing Code: 7,8,10

Descriptor Code: 4

$HASP124

Explanation

The JES2 input service processor at node xeqnode is scanning the input stream for a JOB card. If the input stream enters the system (xeqnode) from the network, this message is displayed to the user from which the input stream originated. The operator at node xeqnode receives the HASP125 message from this input stream and may receive other diagnostic messages indicating errors encountered in the reading of jobs.

In the message text:

devname: The name of the device on which the input was entering the system (xeqnode).
xeqnode: The name of the node at which this job was to execute.
orgjobid: The job identifier or VM/RSCS spool file identifier from which this job originated.
orgjname: The job name associated with this job identifier that was found in the Network Job Header.

System action

The input service processor continues to read the input stream until a JOB card is encountered or until an end-of-data condition is recognized.

Operator response

None.

Programmer response

Correct the JCL and resubmit, or contact the system operator at the execution node to resolve any errors with the receiving of jobs on the network. This message can be cross referenced with orgjobid to the HASP125 message received by the operator at the execution node.

Module

HASCSRIP

Routing Code: 7,8,10

Descriptor Code: 4

$HASP125

Explanation

The JES2 input service processor is scanning the input stream for a JOB card. This message may be accompanied by diagnostic messages indicating that errors have been encountered in the reading of jobs. In the message, text is one of the following:

ijobid ijobname
userid AT nodename

In the message:

devname: The name of the device on which the input was entering the system. If the device name is INTRDR, this message also displays ijobid and ijobname.
orgjobid: The job identifier or VM/RSCS spool file identifier from which this job originated. JES2 only displays this information if the job enters the system from the network.
ijobid: The job identifier of the job that is submitting this job. This information is displayed only if the device name is INTRDR.
ijobname: The name of the job that is submitting this job. This information is displayed only if the device name is INTRDR.
userid: The TSO/E user ID that originated this job. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the user ID that originated this job, this field displays *UNKNOWN.
nodename: The name of the node from which this job originated. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the node from which this job originated, this field displays *UNKNOWN.

System action

The input service processor continues to read the input stream until a JOB card is encountered or until an end-of-data condition is recognized.

Operator response

If you entered a command to delete a job currently on the device, perform the appropriate action consistent with the reason for deletion. If skipping is caused by the deletion of a job because of an error encountered, inform the programmer of the error. Otherwise, check the input stream to make sure that the cards are in correct order and resubmit the corrected jobs after canceling any that were incorrectly entered.

Programmer response

Correct the JCL in accordance with the accompanying error messages.

Module

HASPRDR, HASCINJR, HASCNJJR

Routing Code: 7

Descriptor Code: 4

$HASP126

Explanation

A $#ADD macro has found a bad class in the JOE. A disastrous error is issued previous to this message.

In the message text:

grpid: The group identifier name assigned by the user or JES2.
joeid1: The number of job output elements in output group grpid.
joeid2: The number of job output elements in the output group identified by grpid and joeid1.

System action

JES2 deletes the data set.

Operator response

Notify the system programmer.

System programmer response

Investigate disastrous error.

Module

HASPMSG, HASPJOS

Routing Code: 2,10

Descriptor Code: 4

$HASP128

Explanation

A program check occurred while a JES2 processor was using device devname. JES2 is simulating a $C® command for the device to prevent JES2 from ending. If the device was processing a job when the program check occurred, JES2 flushes the job and identifies it in the message text.

In the message text:

devname: The device name.
jobid: The job identifier of the flushed job.
jobname: The name of the flushed job.

System action

Recovery processing continues.

Operator response

None.

System programmer response

None.

Module

HASPRDR

Routing Code: 7,10

Descriptor Code: 4

$HASP129

Explanation

A user submitted a job stream to JES2 with such a large number of SYSIN //ddname DD * or DD DATA JCL statements that they could not be represented within the total number of buffers allocated to JES2 by the EXTBUF parameter on the BUFDEF initialization statement.

In the message text:

jobname: The name of the failed job.

Note: A jobid may precede HASP129. See JES2 message format.

System action

JES2 ends input service processing for the specified job.

Programmer response

If the failing job was submitted by a program that entered a loop, correct the program. Otherwise, use the failing job's output to determine the largest number of SYSIN DD cards that can be included in one job stream on your system. Correct the JCL and rerun the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP130

Explanation

Or:

The JOB statement has an error in the second operand of the JESLOG= operand, or the DD statement has an error in the second operand of the SPIN= operand.

In the message text ssssssss=:

SYNTAX: The operand is not of the form nnn, nnnK, nnnM, hh:mm, h:mm +hh:mm, or +h:mm. If of the proper form, then the minute value may be greater than 59.
SEMANTICS: The line count is less than 500, the time interval is less than 10 minutes or the time of day, hh, is greater than 23.

In the message text:

jobname: Specifies the name of the job.
procstepname: Specifies the name of the step invoking the PROC.
stepname: Specifies the name within the PROC.
ddname: Specifies the name of the DD statement that returned the error.

System action

The job fails JCL conversion, or the job fails allocation.

Programmer response

Fix the JCL specification.

Module

HASCCNVS or HASCDSAL

Routing Code: None. The message appears only in the JESYSMSG data set.

Descriptor Code: None

$HASP131

Explanation

JES2 builds this message when the first character following the ampersand (&) on the DSNAME value specified on a SYSIN or SYSOUT DD statement is not alphabetic, @, #, or $.

In the message text:

dsname: The name of the data set.

System action

JES2 uses the job name instead of the DSNAME specification when building the data set name.

Note: The JCL converter/interpreter (C/I) includes this message in the job's JESJCL data set; this message is not issued to a JES2 operator console.

User response

The DSNAME specification is incorrect. For more information, see the description of the DD DSNAME parameter in z/OS MVS JCL Reference. You may want to change the JCL and rerun the job.

Module

HASCSRDS

Routing Code: –

Descriptor Code: –

$HASP132

Explanation

JES2 builds this message when an incorrect character is found in the DSNAME value specified on a SYSIN or SYSOUT DD statement.

In the message text:

dsname: The name of the data set.

System action

JES2 uses the job name instead of the DSNAME specification when building the data set name.

Note: The JCL converter/interpreter (C/I) includes this message in the job's JESJCL data set; this message is not issued to a JES2 operator console.

User response

The DSNAME specification is incorrect. For more information, see the description of the DD DSNAME parameter in z/OS MVS JCL Reference. You may want to change the JCL and rerun the job.

Module

HASCSRDS

Routing Code: –

Descriptor Code: –

$HASP133

Explanation

JES2 builds this message when the DSNAME value specified on a SYSIN or SYSOUT DD statement contains more than eight characters.

In the message text:

dsname: The name of the data set.

System action

JES2 uses the job name instead of the DSNAME specification when building the data set name.

Note: The JCL converter/interpreter (C/I) includes this message in the job's JESJCL data set; this message is not issued to a JES2 operator console.

User response

The DSNAME should contain no more than eight characters. For more information, see the description of the DD DSNAME parameter in z/OS MVS JCL Reference. You may want to change the JCL and rerun the job.

Module

HASCSRDS

Routing Code: –

Descriptor Code: –

$HASP134

Explanation

JES2 builds this message when the DSNAME value specified on a SYSIN or SYSOUT DD statement is reserved for JES2 use. This message can also be built as a result of dynamic allocation's creation of a data set.

In the message text:

dsname: The name of the data set.

System action

JES2 uses the job name instead of the DSNAME specification when building the data set name.

Note: The JCL converter/interpreter (C/I) includes this message in the job's JESJCL data set; this message is not issued to a JES2 operator console.

User response

The following data set names are reserved for use by JES2:

JESJCL
JESJCLIN
JESMSGLG
JESYSMSG

For more information, see the description of the DD DSNAME parameter in z/OS MVS JCL Reference. You may want to change the JCL and rerun the job.

Module

HASCSRDS

Routing Code: –

Descriptor Code: –

$HASP135

Explanation

The JES2 input service processor is scanning the input stream for a JOB card when it encounters a /*XMIT control card. This card is not valid when it is not preceded by a valid JOB card. This message may be accompanied by diagnostic messages indicating that errors have been encountered in the reading of jobs. In the message, text is one of the following:

ijobid ijobname
userid AT nodename

In the message:

devname: The name of the device on which the input was entering the system. If the device name is INTRDR, this message also displays ijobid and ijobname.
orgjobid: The job identifier or VM/RSCS spool file identifier from which this job originated. JES2 only displays this information if the job enters the system from the network.
ijobid: The job identifier of the job that is submitting this job. This information is displayed only if the device name is INTRDR.
ijobname: The name of the job that is submitting this job. This information is displayed only if the device name is INTRDR.
userid: The TSO/E user ID that originated this job. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the user ID that originated this job, this field displays *UNKNOWN.
nodename: The name of the node from which this job originated. JES2 only displays this information if the job enters the system from the network. If JES2 cannot identify the user ID that originated this job, this field displays *UNKNOWN.

System action

The input service processor flushes the input stream until a delimiter is encountered or until an end-of-data condition is recognized. The delimiter is determined by the DLM parameter on the /*XMIT control card if specified correctly. Otherwise, the delimiter is determined by the defaults.

Operator response

If you entered a command to delete a job currently on the device, perform the appropriate action consistent with the reason for deletion. If flushing is caused by the deletion of a job because of an error encountered, inform the programmer of the error. Otherwise, check the input stream to make sure that the cards are in correct order and resubmit the corrected jobs after canceling any that were incorrectly entered.

Programmer response

Check the input stream to make sure that the cards are in the correct order and there is a valid JOB card before the /*XMIT card. Correct the JCL accordingly and resubmit the job.

Module

HASCSRIP

Routing Code: 7,8,10

Descriptor Code: 4

$HASP136

Explanation

The JES2 input service processor at node xeqnode is scanning the input stream for a JOB card when it encounters a /*XMIT control card. This card is not valid when it is not preceded by a valid JOB card. If the input stream enters the system (xeqnode) from the network, this message is displayed to the user from whom the input stream originated. The operator at node xeqnode receives the HASP135 message from this input stream and may receive other diagnostic messages indicating errors encountered in the reading of jobs.

In the message text:

devname: The name of the device on which the input was entering the system (xeqnode).
xeqnode: The name of the node at which this job was to execute.
orgjobid: The job identifier or VM/RSCS spool file identifier from which this job originated.
orgjname: The job name associated with this job identifier that was found in the Network Job Header.

System action

The input service processor flushes the input stream.

Operator response

None.

Programmer response

Check the input stream to make sure that the cards are in the correct order and there is a valid JOB card before the /*XMIT card. Correct the JCL accordingly and resubmit the job. This message can be cross referenced with orgjobid to the HASP135 message received by the operator at the execution node.

Module

HASCSRIP

Routing Code: 7,8,10

Descriptor Code: 4

$HASP137

Explanation

JES2 displays all RJE workstations that are active in the multi-access spool (MAS) configuration in response to the $D ACTRMT command.

All RJE workstations displayed do not need to be defined on the member from which the $D ACTRMT command was entered.

In the message text:

nnnn: The number of the active RJE workstation.
memname: The name of the MAS member on which this RJE workstation is active.

System action

Processing continues.

Operator response

None.

System programmer response

None.

Module

HASCSCAN

Routing Code: #/1,2,10

Descriptor Code: 4

$HASP138

Explanation

The first three versions of this message appear at the bottom of the spun data set segment. The data set with DDNAME of dddddddd was spun and made available for processing.

In the message text if:

SPIN REQUESTED BY OPERATOR, DDNAME=ccccccccc
A $T jnnn/snnn/tnnn,spin has been issued specifying a particular DDNAME.
dddddddd SPIN HAS OCCURRED BECAUSE OF TIME INTERVAL OR TIME OF DAY
A result of the time interval for data set (JESLOG=(SPIN,+hh:mm) or SPIN=(UNALLOC,+hh:mm)) expiring or the time of day (JESLOG=(SPIN,hh:mm) or SPIN=(UNALLOC,hh:mm)) occurring.
dddddddd SPIN HAS OCCURRED BECAUSE OF LINE COUNT
A result of the line count criterion that is being reached (JESLOG=(SPIN,nnn) or SPIN=(UNALLOC,nnn)).
SPIN successful
A result of a $TJnnn,SPIN $TSnnn,SPIN or $TTnnn,SPIN command with or without a DDNAME=dddddddd addition.
SPIN rejected, no spinnable data set
A result of a $TJnnn,SPIN $TSnnn,SPIN or $TTnnn,SPIN command with or without a DDNAME=dddddddd addition.

If the command source is a console within the JESplex, versions 4 and 5 of the message appear on the operator console and SYSLOG, including the joblog of the job. If the command source is NJE or RJE, then the response is not seen on the operator console.

System action

Job processing continues.

Operator response

None.

System programmer response

None.

Module

HASCDSOC, HASCSIRQ

Routing Code: None.

Descriptor Code: None.

$HASP139

Explanation

The specified exit returned JCL to be processed by input processing. However, the JCL that was returned had continuation or other errors that prevented input processing from correctly processing the job stream.

In the message text:

jobname: The name of the affected job.
nnn: The exit, or exits, that returned the invalid JCL.

Note: A jobid may precede HASP139. See JES2 message format.

System action

The message is written to the JCL data set and JES2 ends input service processing for the job. The job is queued for output processing.

Operator response

None

System programmer response

Review the exit and any JCL that is being modified or added by the exit. Review documentation for the exits in z/OS JES2 Installation Exits for more information on how to code a user exit.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP140

Explanation

During initialization, JES2 encountered a failure attempting to set up an ENF listen exit. This message is followed by message HASP428.

In the message text:

nn: Relative number of the ENFREQ CODE=LISTEN that failed.
xx: The hexadecimal return code from the ENFREQ CODE=LISTEN macro.

System action

JES2 initialization ends.

System programmer response

Contact the IBM Support Center.

Module

HASPIRSI

Routing Code: 1,2,10

Descriptor Code: 4

$HASP141

Explanation

During termination, JES2 encountered a failure attempting to delete an ENF listen exit.

In the message text:

nn: Relative number of the ENFREQ CODE=DELETE that failed.
xx: The return code from the ENFREQ CODE=DELETE macro.

System action

JES2 continues termination processing.

System programmer response

Contact the IBM Support Center.

Module

HASPTERM

Routing Code: 1,2,10

Descriptor Code: 4

$HASP142

Explanation

During JOE index verification, logical errors have been found in the JOE index.

In the message text:

xxx: The reason code that identifies the detected problem.

System action

The JOE index is suspended and can no longer be used for the SYSOUT work selection. This might degrade performance of SYSOUT work selection, but otherwise does not impact JES2 functions.

System programmer response

Contact the IBM Support Center.

Module

HASPJOS

Routing Code: 2,10

Descriptor Code: 4

$HASP143

Explanation

During JOE index verification, logical errors have been found in the JOE index.

In the message text:

xxx: The reason code that identifies the detected problem.

System action

The JOE index rebuild is initiated to rebuild the JOE index and to restore JOE index functions. This is an asynchronous process running in the background. When the JOE index build is complete, message HASP145 is issued.

System programmer response

Contact the IBM Support Center.

Module

HASPJOS

Routing Code: 2,10

Descriptor Code: 4

$HASP144

Explanation

The JOE index build was initiated by the $TOUTDEF,WS_OPT=YES command.

System action

The JOE index build is initiated. This is an asynchronous process running in the background. When the JOE index build is complete, message HASP145 is issued.

Module

HASPXIT

Routing Code: 2,10

Descriptor Code: 4

$HASP145

Explanation

The JOE index build is complete. The JOE index build was initiated by the $TOUTDEF,WS_OPT-YES command or by the JOE index verification process during JES2 member start if logical errors were found in the JOE index.

System action

The JOE index build is complete. The JOE index is fully functional and can be used for SYSOUT work selection.

Module

HASPJOS

Routing Code: 2,10

Descriptor Code: 4

$HASP146

Explanation

Operator console form:

JESYSMSG message form:

While parsing JCL statements, JES2 detected an error on the JCLLIB statement. The problem encountered is identified by reason. In the message text:

jobname: The name of the affected job.

The reason is one of the following strings:

VALUE OF keyword= EXCEEDS n CHARACTERS: The character values provided for the specified keyword are longer than the maximum allowed length.
VALUE OF keyword= PARAMETER IS NOT VALID: The value provided for the specified keyword is not allowed. If the specified value is null, the keyword might require a value.
Second JCLLIB statement ignored: The second JCLLIB statement is ignored by JES2. It is flagged by the converter as an error.
PROCLIB in prior /*JOBPARM statement not valid if PROCLIB also on JCLLIB statement: A prior /*JOBPARM statement has specified PROCLIB. Specifying PROCLIB on a subsequent JCLLIB statement is an error.

Note: A jobid can precede HASP146. See JES2 message format.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion, unless the message is a warning only.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for information about coding JCLLIB statements. Correct the control statement and resubmit the job.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP147

Explanation

JES2 detected an error while validating the user portion of the job correlator that was returned by exit 2, 20, 50, or 52 in the XPL. The message text indicates the error, as follows:

embedded blank: The user portion of the job correlator cannot contain embedded blanks, and an embedded blank was found in the supplied value.
invalid character: The user portion of the job correlator contains characters other than the supported alphanumeric, national (@, #, $), and underscore (_) characters.

System action

The message is written to the JESYSMSG data set when the job is converted. The user portion of the job correlator supplied by the exit is ignored, and any existing setting of the user portion is retained. The job continues processing because the message is a warning message only.

Operator response

None

Programmer response

Investigate the installation exit code to determine where the data is placed in the user portion of the job correlator contained in the XPL.

Module

HASCSRIP

Routing Code: -

Descriptor Code: -

$HASP148

Explanation

JES2 conversion processing detected an error while validating the keyword input on the SCHEDULE statement. The message text indicates the error, as follows:

SCHEDULE statement ignored for STC/TSU

SCHEDULE statement can be used in the JCL used for started tasks and TSO sessions, but is ignored and does not influence execution in any way.

STARTBY time in the past

STARTBY keyword specifies time in the past.

Conflict between STARTBY and HOLDUNTL

There is a conflict between time specified on STARTBY keyword and time specified on HOLDUNTL keyword. This message is issued in the following situations:

STARTBY time is earlier than HOLDUNTL time.
STARTBY and HOLDUNTL use different formats. One of them specifies an interval time and the other a point in time.

Conflict between STARTBY and JOBGROUP

STARTBY keyword is mutually exclusive with the JOBGROUP keyword.

Job Group ID is not valid

The supplied job group job ID does not match an existing, active job group.

Missing Job Group name

A job group name must be supplied for the JOBGROUP parameter.

Job Group name is too long

The supplied job group name is greater than 8 characters in length.

HOLDUNTL ignored - overridden by TYPRUN=HOLD

HOLDUNTL specification that is on a SCHEDULE statement is ignored when JOB statement specified TYPRUN=HOLD.

DELAY has incorrect value

DELAY value is not correct.

Job group not found

Job group is not found.

Job group not in correct state

Job group is in invalid state.

Internal error trying to locate job group

An internal error was found when trying to locate a job group.

Job not associated with job group

Job is not associated with a job group.

Job not authorized to register to job group

Job submitter or job owner is not authorized to register jobs for the job class specified for this job.

Job already exists in job group

Job already exists in job group.

Failed to obtain AIS JCT Extension ($JCTX) for HOLDUNTIL

An error occurred while trying to Add or Get a required JCT Extension. A holduntil value, which requires the AIS JCT Extension, was specified by the SYS_HOLDUNTIL symbol, on JCL's SCHEDULE statement, or both.

System action

The message is written to the JESYSMSG data set when the job is converted. The job is queued for output processing after conversion.

Operator response

None

Programmer response

See z/OS MVS JCL Reference for information about coding SCHEDULE statements. Correct the statement and resubmit the job.

Module

HASCCNVS

Routing Code: N/A

Descriptor Code: N/A

$HASP149

Explanation

The listed command cannot be processed. This is generally the result of an environmental problem and should resolve itself. The command might work if it is reissued later. The message text indicates the error, as follows:

PRIOR COMMAND ACTIVE: A prior instance of the command is still active. A new instance of the command cannot be started until the current instance completes.
$SUBIT SERVICE ERROR: The command requires use of the internal $SUBIT service. The service is not able to complete the request at this time.

In the message text:

command: The beginning of the command text.

System action

The command is not processed. Processing continues.

Operator response

Wait for current processing to complete, and then reenter the command. If the condition does not clear, contact your system programmer.

Programmer response

Determine what condition is preventing the currently active command from completing (perhaps some resource is unavailable or an outstanding WTOR). Once the active command completes, reissue the command.

Module

HASPCOMM

Routing Code: #

Descriptor Code: -

$HASP150

Explanation

Device devname is beginning to process the output identified in the grpid.joeid1.joeid2 fields for the indicated job.

The record count includes only records with a nonzero text length and, which do not use immediate machine control characters. The page count includes begin page structured fields only. Other AFP control records (records that start with the X'5A'control character) are not included in either the record or page count. Count information is omitted is not available.

In the message text:

jobname: The name of the job
grpid: The group identifier assigned by user JCL or generated by JES2 if the user did not specify it
joeid1: The number of job output elements in output group grpid
joeid2: The number of job output elements in the output group identified by grpid and joeid1
devname: The name of the device
nnnn: The number of records, pages, or both to be processed
mmmm: The number of records, pages, or both initially represented by the job output element identified by OUTGRP=grpid.joeid1.joeid2

If nnnn and mmmm are not equal, the job output element was partially processed at an earlier time, but that processing was interrupted.

Note: A jobid may precede HASP150. See JES2 message format.

System action

JES2 processing continues.

Operator response

None.

System programmer response

None.

Module

HASPPRPU, HASPFSSM

Routing Code: 7,10

Descriptor Code: 4/6

$HASP151

Explanation

An error occurred while SETPRT processing was setting up the 3800 printer identified by prtname for the indicated job.

In the message text:

jobname: The name of the job.
prtname: The name of the printer.
text: The message number and text of a SETPRT error message.

See z/OS MVS Programming: Assembler Services Reference ABE-HSP under the SETPRT macro instruction for the explanation of the return code in the SETPRT error message.

Note: A jobid may precede HASP151. See JES2 message format.

System action

JES2 stops processing the specified job. Message HASP190 is issued when this job requires that the setup for the device be altered. The SETPRT error message and message HASP154 are issued to the programmer.

Operator response

Respond as indicated in the SETPRT error message. If necessary, issue the $DU command to display the current status of the printer and use the $T command to correct the error.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2

$HASP152

Explanation

A repositioning command for the 3800 printer or impact printers identified by prtname cannot be processed. If – PRIOR COMMAND ACTIVE appears, the repositioning command is rejected because a previous command is still being processed by JES2.

If the optional text is not displayed, the command is rejected for one of the following reasons:

The output that is currently located at the 3800 transfer station does not allow the specified command.
For impact printers, no output is active for the specified command.

In the message text:

prtname: The name of the printer.

System action

The command is not processed. Processing continues.

Operator response

If this message is issued because a previous command is active, wait for processing to complete and then reenter the command. If this message is issued because the output is not valid for the specified command, ensure that the page currently at the transfer station is not a dummy page between jobs. Reenter the command when valid output is being printed.

System programmer response

None.

Module

HASPPRPU, HASPFSSP

Routing Code: 7,10

Descriptor Code: 4

$HASP153

Explanation

The printer identified in the message has lost some data.

In the message text:

prtname: The name of the printer.

System action

If the operator does not reposition the printer, output processing resumes with the output last fused by the printer. If the operator wants to reposition the printer, the operator must wait for JES2 to resume output processing.

Operator response

If automatic recovery is acceptable, the operator need not respond. If automatic recovery is not acceptable, the operator must wait for JES2 to complete its backspacing process. If the operator does not wait, JES2 does not accept any operator commands. The operator may enter a $F command or $B command to reposition the printer to the page you want. The operator may even choose to enter a $E command to restart the printer.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 4

$HASP154

Explanation

An error occurred while SETPRT processing was setting up the 3800 printer identified by prtname for the specified job. This message appears in the programmer's listing, preceded by the appropriate SETPRT error message. The operator receives message HASP151 or HASP157.

In the message text:

prtname: The name of the printer.
jobname: The name of the job.
jobid: The identification number assigned to the job by JES2.
rrr: The programmer's room number entered on the job statement.

System action

Processing of the specified job halts.

System programmer response

Respond as indicated in the SETPRT error message and rerun the job.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 4

$HASP156

Explanation

The operator entered a repositioning command for the 3800 printer identified by prtname. At least some (and possibly all) of the output for the specified job has crossed the 3800 transfer station. This job is requeued on the output queue.

In the message text:

jobname: The name of the job.
prtname: The name of the printer.

Note: A jobid may precede HASP156. See JES2 message format.

System action

The repositioning command is processed. The requeued job is printed on any eligible device.

Operator response

None.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 4

$HASP157

Explanation

An error occurred while SETPRT processing was setting up the printer (with universal character set (UCS) specifications) identified by prtname for the specified job.

In the message text:

jobname: The name of the job.
prtname: The name of the printer.
rc: The return code.

Note: A jobid may precede HASP157. See JES2 message format.

System action

JES2 stops processing the specified job. Depending on the type of error, message HASP190 might be issued. The appropriate SETPRT error message is issued. For the 3800 printer, message HASP154 is issued to the programmer's listing.

Operator response

Enter the $DU command to display the current status of the printer, and use the $T command to attempt to correct the error. If necessary, contact the system programmer.

System programmer response

Respond as indicated by the return code in register 15, which appears in this message. See the SETPRT macro instruction in z/OS DFSMS Macro Instructions for Data Sets for the meanings of return codes 18 through 50.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2

$HASP158

Explanation

JES2 detected a critical resource shortage during processing for the 3800 printer.

In the message text:

jobname: The name of the job.
prtname: The name of the printer.
cde: A decimal code indicating the type of shortage.

Possible values of cde are:

cde: Description
04: The PPQ (pending page queue) of the 3800 printer has been exhausted.
08: GETMAIN attempted to expand the PPQ of the 3800 printer and failed.
12: An error has been detected in the PPQ of the 3800 printer.

Note: A jobid may precede HASP158. See JES2 message format.

System action

When cde=04, the printer is halted.

When cde=08, the current job is interrupted and the printer is drained.

When cde=12, all jobs queued to the printer that has the error are requeued to another printer. The printer that has the error is drained.

Operator response

Possible responses are:

cde: Response
04: Entering a $S PRTnnnn command attempts to expand the PPQ of the 3800 printer. If the expansion is successful, normal processing continues. If you enter a command to stop a printer ($C, $E, or $I), the command processes against the current job and the printer drains.
08: Hold or cancel the job and restart the printer. Notify the system programmer.
12: Notify the system programmer.

System programmer response

If this message appears frequently, increase the CKPTPAGE parameter in the printer initialization statement. If this message is associated with a particular job, increase the CKPTPGS parameter in the /*OUTPUT control statement or the CKPTPAGE parameter on the JCL OUTPUT statement.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2,4

$HASP160

Explanation

The indicated device found no work in the queue(s) specified by class [class...class].

In the message text:

devname: The name of the device searching for work.
class[class...class]: The names of the queues.

System action

The specified device remains INACTIVE until work becomes available.

Operator response

You can use the set ($T) command to:

Alter the setup to match work in the listed classes.
Alter the current class list.

System programmer response

None.

Module

HASPPRPU, HASPFSSP

Routing Code: 7

Descriptor Code: 4

$HASP165

Explanation

JOBRC

The following values are displayed in the message text:

jobname: The job name. If apostrophe characters are embedded in the job name, they are replaced by quotation mark characters.
jobid: The job identifier on the input node.
nnnnnnnn: The input node for this job. This is displayed only if nodename is not the job input node.
nodename: The node that the job ran on, or attempted to run on.
[xxx yyy] ENDED AT nodename – cc=dddd: JES2 stopped the specified job at nodename by a condition test specified in the COND parameter of the job statement being satisfied by the completion code dddd of the running step xxx. If step xxx is a step of a cataloged procedure, then yyy is the step that called step xxx.
ENDED AT nodename: The specified job on nodename did not complete for the specified reason.

For ENDED AT nodename inclusive, one of the following reasons is displayed:

MAXCC=code: The job maximum condition code was reached (JOBRC was not specified).
JOBRC=code: The job returned code.
MAXRC=code: The job maximum return code was reached (JOBRC was specified but MAXRC was returned).
ABENDED Sxxx,Uyyy: The job abended with system code xxx and user code yyy.
ABENDED abend_code, JOBRC=code - JOBRC=(STEP,stepname),: The job abended with code abend_code and JOBRC code. The job step stepname executed, but a subsequent step abended.
JCL ERROR: The converter/interpreter or initiator phase of job processing could not be completed because of an error in the JCL.
CANCELLED: The job was cancelled by the operator.
CONVERSION ABEND: The job conversion phase abended.
SECURITY VIOLATION: The specified job did not run because of an unsuccessful authorization check during input processing.
CONVERSION ERROR: An error occurred during the job conversion phase.
SYSTEM FAILURE: A failure occurred on the system that the job was running on.
FLUSHED: The job is associated to a job group, and the job was flushed because of the state of the job group.
msgid message-text: A message from a component other than JES2 appears with the HASP165 prefix, and could be related to the reason the job ended (whether normally or abnormally). To determine the appropriate actions to take, see the description of the msgid message.

The following values are displayed in the message text:

grpname: The job group name.
MAXCC=code: The maximum condition code of any job in the completed job group.

Note: A jobid or grpid value might precede $HASP165. See JES2 message format.

System action

The job was ended for the specified reason or the job group completed. This message is displayed to an interactive user if the NOTIFY parameter is specified on the JCL JOB statement, or the JECL /*NOTIFY statement is specified or the NOTIFY JCL statement was used. This message is also sent as an email message when the NOTIFY JCL statement requests notification by way of an email.

Programmer response

In the case of a JCL ERROR message, check the system output for the actual error message. Correct the indicated error and resubmit the job. In the case of an ABENDED message, check system output for the ABEND code. In the case of SECURITY VIOLATION, verify the user ID, group ID, and password used, if any.

Module

HASPHOPE

Routing Code: 7

Descriptor Code: 4

$HASP170

Explanation

Output processing on the indicated device has been aborted, forward-spaced, deleted, backspaced, repeated, restarted, or interrupted.

In the message text:

devname: The name of the device.

System action

The system action depends on the specified function:

ABORTED: An unrecoverable error has occurred on the 3800 printer. Output processing is stopped. Job(s) currently active on the device are requeued from their last checkpoint and the device drains.
FWD-SPACED: The requested number of pages or cards is skipped without printing or punching, and processing continues. If the end of the data set is encountered while skipping, processing continues with the beginning of the next data set.
Note: If FWD-SPACED appears in the message, the operator might have pressed the cancel key on a printer that has cancel-key support.
DELETED: The output being processed on the indicated device is queued for the next processing phase. Output processing is stopped.
BACKSPACED: The requested number of pages or cards is backspaced, and processing continues. If the beginning of the data set is encountered while backspacing, processing continues at the beginning of the data set.
REPEATED: The output being processed on the indicated device is requeued. Output processing is continued.
RESTARTED: The output being processed on the indicated device is requeued. Output processing for the job is stopped.
INTERRUPTED: The output being processed on the indicated device is requeued. When it is processed again, processing begins from the last checkpoint taken. The device selects new output to process. If the interrupted output is the highest priority output available for the device, it is selected.

Operator response

None.

System programmer response

None.

Module

HASPPRPU, HASPFSSP

Routing Code: 7

Descriptor Code: 4

$HASP175

Explanation

Output processing on the indicated device is stopped at an end-of-job boundary.

In the message text:

devname: The name of the device.

System action

Processing continues with the device unavailable.

Operator response

After removing the processed output, the operator can cause the device to continue its function by either depressing first the STOP then the START key on the device or by entering a $S device command on the system console. To prevent future device pauses, enter $T devname,P=NO.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 4

$HASP176

Explanation

The specification of a JES system symbol was not correct. Or alternatively, the AIS JCT Extension could not be obtained.

System action

JES2 deletes the job.

Operator response

Report this message to the system programmer.

System programmer response

If the message indicates a system symbol's syntax is not valid, then verify the value specified for the symbol indicated in the message.

Module

HASCSRIP

Routing Code: 7

Descriptor Code: 4

$HASP180

Explanation

The specified job has requested that image id be loaded into either the printer device forms control buffer (FCB), or the universal character set (UCS). A search of all images has shown that an I/O error occurred during an attempt to read from SYS1.IMAGELIB or a load error occurred during an attempt to load the image into the printer. Channel 1 must be defined in the image, otherwise the INVALID message results. This error can occur if the FCB or UCS was added to SYS1.IMAGELIB after JES2 was up and the new FCB or UCS caused SYS1.IMAGELIB to expand into a new extent. In this case, JES2 must be restarted to pick up the new FCB or UCS.

In the message text:

jobname: The name of the job.
devname: The name of the device.
id: The identifier of the image.

Note: A jobid may precede HASP180. See JES2 message format.

System action

Processing of the indicated job is halted.

Operator response

Enter the $DU command to see the current status. Then use the $T command to correct the indicated error. If FCB is indicated in the message and you have a non-impact printer, ensure that the forms settings on the printer correspond to the FCB specifications.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2,4

$HASP181

Explanation

During output processing to a printer, JES2 encountered an error while attempting to obtain buffers for the printer error log or MDR area.

System action

Output processing to the printer continues. However, there might be a loss of error log data or inappropriate error recovery procedures on some devices.

Operator response

Use the $P PRT(nnnn) command to stop the printer, then restart it with the $S PRT(nnnn) command. If the problem persists, notify the system programmer.

System programmer response

None.

Module

HASPNUC

Routing Code: 2,7

Descriptor Code: 4

$HASP182

Explanation

During JES2 initialization processing for a printer, the $GETBUF routine could not get enough buffers for JES2 to determine if the UCS or the FCB is a standard image. JES2 sets the DCT to show that the UCS or the FCB is a standard image.

System action

JES2 initialization processing continues.

Operator response

You might want to reset the printer because if the UCS or the FCB is not a standard image, jobs on the device might run incorrectly.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 4

$HASP183

Explanation

During the indicated process, sufficient free buffers were not available to process the specified job. If the number of buffers required is less than the number defined, this is likely a temporary condition. If the number required is greater than the number defined, then additional buffers must be defined to process the job.

In the message text:

jobname: The name of the held job.
mmmm: The number of required buffers.
nnnn: The number of defined buffers.

Note: A jobid may precede HASP183. See JES2 message format.

System action

As indicated in the message, the job is held, or delayed until the number of free buffers exceeds the number required by the job. Note that on a busy system, the job might fail additional time with this message if the needed buffers are consumed by another process before this job can use them resulting in additional HASP183 messages. This could indicate that the number of EXTBUFs defined on BUFDEF is not sufficient.

Operator response

If the job is held, release the job when fewer JES2 devices are active. If the job continues to receive this message, or if the number of required buffers (mmmm) is greater than the number defined (nnnn), notify the system programmer.

If the job is delayed, then it is selected again when the number of free buffers is greater than the number required by the job.

System programmer response

Increase the value of the limit for the EXTBUF parameter on the BUFDEF initialization statement, or use the PURGE option to cancel the specified job.

Module

HASPHOPE, HASPCNVT

Routing Code: 1,2

Descriptor Code: 4

$HASP184

Explanation

JES2 was unable to obtain storage for a DCB/DEB for the specified device.

In the message text:

devname: The name of the device.

System action

JES2 continues processing without the device.

Operator response

Notify the system programmer. Try to start the device at a later time.

System programmer response

Determine why there is insufficient storage in the JES2 address space and correct the error.

Module

HASPDYN

Routing Code: 7,10

Descriptor Code: 4

$HASP185

Explanation

JES2 stops processing the data set identified by grpid.joeid1.joeid2 on the specified device.

In the message text:

jobname: The name of the job.
grpid: The group identifier either assigned by the user JCL or generated by JES2 if the user did not specify it.
joeid1: The number of job output elements in output group grpid.
joeid2: The number of job output elements in the output group identified by grpid and joeid1.
nnnn: The relative block number of the data set in which the error was detected.
rsnc: The reason code.
text: The explanatory text accompanying the reason code.

Note: A jobid may precede HASP185. See JES2 message format.

The device is stopped for the reasons associated with the following reason codes:

rsnc: text
01: DATA SET NOT CLOSED
JES2 stopped processing the current data set because it encountered an error while attempting to read the next block of data. The data set was not closed. This may be because either the job was running during a system failure and is now being printed without being rerun or an abend occurred in CLOSE processing.
02: INVALID TRACK ADDRESS
JES2 detected that the track address of the next data block to be read is incorrect. It may be incorrect because a storage overlay of the track addressing field of the next spool block occurred before the block was written out. If BLOCK=1 is displayed, the error occurred in the control block pointing to the start of the data set (PDDB in the IOT). If BLOCK=1 is not displayed, the error occurred in a data block. If a dump is issued, the $PCE contains the value of the incorrect track address in the PCESEEK field.
03: I/O READ ERROR
An I/O error occurred while JES2 was attempting to read the data block numbered nnnn for the specified data set. A hardware problem is the probable cause for the error.
04: INVALID JOB KEY
The job key field of the data block numbered nnnn does not match the current job key because the same spool address has been allocated to more than one job. This is most likely caused by a JES2 abend after the JES2 checkpoint processor replenished the TGMs but before the next checkpoint write started.
05: INVALID DATA SET KEY
The data set key field of data block numbered nnnn does not match the current data set key. Allocation of the same spool address to more than one data set within a multitasking program is most likely caused by an error within the JES2 subsystem interface.
06: OBSOLETE OUTPUT ELEMENT
JES2 selected an output element that is ineligible for processing because its corresponding data set was already purged. The probable cause for this error is that, after a JES2 failure, the spin data set was purged without the JOE being removed.
07: AUTHORIZATION FAILED
The user identification associated with the output group is not eligible to use the device that selected this group.
08: BAD I/O FOR SWBIT READ
An I/O error occurred while JES2 was reading the SWBIT(s) for a data set during print separator processing. This is probably a hardware error.
09: NO DATA SET IN THE IOT
JES2 did not find a matching data set for the job output element (JOE) in the IOT during print/punch processing. This is probably an IOT chaining error.

System action

JES2 discontinues output processing on the device.

Operator response

Notify the system programmer.

Programmer response

If RC=06, no response is necessary. Otherwise, rerun the job.

Module

HASPPRPU, HASPFSSM

Routing Code: 7

Descriptor Code: 4

$HASP186

Explanation

JES2 processing does not select the output group element identified by grpid.joeid1.joeid2 on the specified device.

In the message text:

jobname

The name of the job.

grpid

The group identifier. This is a 1– to 8–character alphameric name either specified by the user's JCL or generated by JES2.

joeid1

This number is assigned by JES2 and is used to uniquely identify job output elements within the output group.

joeid2

This number is assigned by JES2 and determines the number of job output elements within the output group identified by grpid and joeid1.

device

The device name for an output device or the job number/procname.identifier of the task attempting output selection through the PSO interface.

JES2 device name for physical device (for example, PRT1)
job number/procname.identifier of the requesting task for the PSO interface
job number/procname.identifier.threadid of the requesting task for the SAPI interface. The SAPI application provides the threadid.

Note: A jobid may precede HASP186. See JES2 message format.

System action

JES2 discontinues HARDCPY processing on the device for the specified job output group element ($JOE), and continues to scan for the next BEST JOE. JES2 remembers that the device cannot select the specified JOE and skips that JOE for the specified device until the device is restarted, JES2 is restarted, or the output group element is modified through operator commands.

If an access violation occurs, and you have DEBUG SECURITY=YES, JES2 issues this message, and RACF® issues message ICH408I and writes an SMF TYPE80 (X'50') record which includes LOGSTR information. The LOGSTR identifies the problem as either:

JES2 DEVICE WORK SELECTION SCREENING
EXTERNAL WRITER WORK SELECTION SCREENING
SAPI - DATA SET ACCESS

Operator response

Notify the system programmer.

System programmer response

Select one of the following actions based on your environment set up:

If security is intended to act as a work selection criterion and another device can select the output group element, no action is required.
If the output group element was routed to the wrong device, modify the output to go to a device on which it can be processed using operator commands.
If the output group element should have been selected by the device, update any security definitions or profiles for the device and restart the device.
If you need to determine why JES2 issued this message or you are running in RACF warn mode and need to know if this message would also occur in fail mode, set DEBUG SECURITY=YES.

System programmer response

None.

Module

HASPJOS, HASPPSO

Routing Code: –

Descriptor Code: –

$HASP190 (Variant 1)

Explanation

If devname specifies a punch device, the indicated job requires that the setup of that punch device be altered to forms = ffff. If devname specifies a printer device, the indicated job requires the setup be altered to forms = ffff, carriage control = cccc, and print train = tttt.

Note: Another version of this message follows. Use the form that corresponds to the HASP190 message on your console.

In the message text:

jobname: The name of the job.
devname: The name of the print or punch device.
fff: The forms name.
cccc: The carriage control name.
tttt: The print train name.

Note: A jobid may precede HASP190. See JES2 message format.

System action

Output processing is halted on the specified device until an appropriate operator response is received.

Operator response

Verify that the requested setup has been completed and enter a start ($S) command for the indicated device. If you want to override any or all of the setup specifications, do so with the set ($T) command followed by a start ($S) command. Current activity may be suspended by the restart ($E), interrupt ($I), and cancel ($C) commands. In this event, all intervening set ($T) commands are ignored and the device setup is the same as before the setup message.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2,4

$HASP190 (Variant 2)

Explanation

The indicated job requires that the setup of the 3800 printer device or AFP1 printer device with burster indicated by prtname be altered to forms = ffff, forms overlay = name, and burst mode or no burst mode.

Note: JES2 only issues HASP190 for:

Channel-attached printers that are defined with PRINTER(nnnnn) SETUP=HALT,WS=(...F/).
Non-channel-attached (PSF FSS-driven printers that are SNA or TCP/IP attached) printers that are defined with PRINTER(nnnnn) SETUP=HALT,WS=(...F/) and with the PSF PRINTDEV statement that includes SETUP= in the PSF PROC. Be aware that this SETUP= setting is application-specific and you need to consult the appropriate user's guide before setting this value. For example, see the PSF book that documents the use of PRINTDEV SETUP=ALL | NONE | FORMS | BURST to understand which settings prompt the HASP190 message.

This allows JES2 to stop, issue this message, and wait until the operator verifies printer changes.

In the message text:

jobname: The name of the job.
prtname: The name of the printer.
ffff: The forms name.
name: The name of the overlay.

Note: A jobid may precede HASP190. See JES2 message format.

System action

Output processing is halted on the specified device until an appropriate operator response is received. For burst mode, if the burster is not threaded, this message is repeated.

Operator response

Verify that the requested setup has been completed and enter a start ($S) command for the indicated 3800 printer device. If you want to override any or all of the setup specifications, do so with the set ($T) command followed by a start ($S) command. Current activity may be suspended by the restart ($E), interrupt ($I), and cancel ($C) commands. In this event, all intervening set commands are ignored, and the device setup is that before the setup message.

System programmer response

None.

Module

HASPPRPU, HASPFSSP

Routing Code: 7

Descriptor Code: 2

$HASP191

Explanation

A channel or I/O error has occurred while printing a data set. Printing does not continue until the operator takes some action, although during error recovery, JES2 may cause the data set to be printed again.

In the message text:

jobname: The name of the halted job.
prtname: The name of the printer on which the job was processing.

Note: A jobid may precede HASP191. See JES2 message format.

System action

The printer prtname is halted until the operator takes some action. The error may have caused data to be duplicated or lost.

Operator response

Use the $S command to restart the printer if automatic recovery is acceptable. If automatic recovery is not acceptable, use the $B command to reposition the printer to the top of the page in error, or to a page before the page that has the error. Then use the $S command to restart the printer. If you must be sure that the data set prints correctly, use the $E command to reposition the printer to the beginning of the data set, and then use the $S command to restart the printer.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7

Descriptor Code: 2

$HASP196

Explanation

JES2 detected an error or abend during an installation exit or a scheduler JCL facility (SJF) service while printing or punching a job's output.

In the message text:

devname: The name of the printer or punch.

text is one of the following:

EXIT 1: JES2 encountered a problem while Exit 1 was in control.
EXIT 15: JES2 encountered a problem while Exit 15 was in control.
SWBTUREQ RETRIEVE: JES2 was processing a scheduler JCL facility SWBTUREQ RETRIEVE request.
SWBTUREQ SPLICE: JES2 was processing a scheduler JCL facility SWBTUREQ SPLICE request.
SJFREQ SWBTUMERGE: JES2 was processing a scheduler JCL facility SJFREQ SWBTUMERGE request.
SWBTUREQ RETRIEVE RC=nn,REASON=nnnn: JES2 was processing a scheduler JCL facility SWBTUREQ RETRIEVE request. This form of the text includes a return code (RC) and a reason code.
SWBTUREQ SPLICE RC=nn,REASON=nnnn: JES2 was processing a scheduler JCL facility SWBTUREQ SPLICE request. This form of the text includes a return code (RC) and a reason code.
SJFREQ SWBTUMERGE RC=nn,REASON=nnnn: JES2 was processing a scheduler JCL facility SJFREQ SWBTUMERGE request. This form of the text includes a return code (RC) and a reason code.

System action

When text is SWBTUREQ RETRIEVE with an ERROR, JES2 stops processing the output and then purges the output. When text is SWBTUREQ SPLICE, JES2 does not insert the SWBTU into the SMF type 6 record, and processing continues. For all other cases, JES2 puts the output into hold (HOLD=SYS) and continues processing.

Operator response

See the operator response for message HASP197.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7,10

Descriptor Code: 4

$HASP197

Explanation

A program check occurred while device devname was processing the output identified in the grpid.joeid1.joeid2 field for the indicated job. JES2 is simulating a $I command for the device to prevent JES2 ending.

In the message text:

devname: The name of the device.
jobid: The job identifier.
jobname: The name of the job.
grpid: The group identifier name assigned by the user or JES2.
joeid1: The number of job output elements in output group grpid.
joeid2: The number of job output elements in the output group identified by grpid and joeid1.

System action

JES2 puts the output in HOLD=SYS status. Recovery processing continues.

Operator response

Use the $L command to display the status of this job output element identified by grpid.joeid1.joeid2. and correct the error. Use the $TO command to put the output in REL=SYS status, or cancel the job and have the user resubmit it.

System programmer response

None.

Module

HASPPRPU

Routing Code: 7,10

Descriptor Code: 4

$HASP198

Explanation

The JES2 main task encountered an error and issued message HASP088 to describe the error. This message lists the termination options and precedes the HASP098 message.

Operator response

This is only an informational message; reply to the HASP098 message with one of the responses above.

System programmer response

None.

Module

HASPTERM

Routing Code: 1,2,10

Descriptor Code: 2,7