> 
> I cannot locate the message description for the following in z/OS V1R12.0
JES2
> Messages SA22-7537-10:
> 
> $HASP5121 NJE L3.SR1 ERROR RECEIVING NETWORK DATA SET HEADER, RC=16
> 
> It's accompanied by message:
> 
> $HASP5532 NJE L3.SR1 SEVERE ERROR - HEADER/TRAILER BUILD ERROR RC=8
> 
> Which does have an explanation. A JES2 trace using ids 21-24 shows the NJE
Job
> Header (NJH) but not the Data Set Header it appears to be complaining
about so I can't
> identify what in particular it is objecting to. Does anyone have any
insight into 5121?
> 
> This occurs on both z/OS 1.9 and 1.12.
> 
> Neale
>

You may need to open an ETR with IBM on this.

Only reference I could find is for


  ***************************************************************
  *                                                             *
  *      If you are using TCP/IP for NJE communication, you     *
  *      should apply both OA13667 and OA13512 to both ends     *
  *      of the NJE connection.                                 *
  *                                                             *
  *      If OA13667 is applied on the transmitting end          *
  *      of a TCP/IP NJE connection but not the receiving end,  *
  *      the following symptoms may occur:                      *
  *      MSGHASP5121 $HASP5121 ERROR RECEIVING <header type>    *
  *      MSGHASP5532 $HASP5532 SEVERE ERROR - RECORD SEQUENCE   *
  *                  ERROR RC=9                                 *
  *      ABENDSEC8 RC09 in IAZNJSTK                             *
  *      These errors can occur because header/trailer          *
  *      segments may now span buffers as of OA13667, and       *
  *      the receiver cannot tolerate these records spanning    *
  *      buffers without OA13667.                               *
  *                                                             *
  *      If OA13667 and OA13512 are not both applied,           *
  *      unpredictable errors may occur if a $E Lnnn.dvn        *
  *      command is issued.  The use of RC=8 from JES record    *
  *      exits is inconsistent both in its use from JES2        *
  *      code and its handling by the common code.  Possible    *
  *      symptoms include subdevices draining erroneously,      *
  *      jobs being held by a transmitter, or the connection    *
  *      dropping.                                              *
  *                                                             *
  ***************************************************************

So, it looks like there may not have been a document update for this message

Lizette

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to