$HASP121

jobname device name

Explanation

>>-jobname device name--ERROR RECEIVING------------------------->

>--+-NETWORK JOB HEADER------+--RC=--rc------------------------><
   +-NETWORK DATA SET HEADER-+            
   '-NETWORK JOB TRAILER-----'            

 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) will not be
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