PI86429: Z/OSMF GET REST REQUEST FAILS WITH UNEXPECTED CLASSTYPE=4 FROM RECEIVERESPONSEHEADER

APAR status

• Closed as documentation error.

Error description

• If system is not using the default LE MSGFILE of SYSOUT, any
  z/OSMF GET request will encounter this error. When IZUFPROC is
  executed, the code will look for a TSO READY prompt to be
  returned. This will not happen if the code is unable to access
  the appropriate MSGFILE. Eventually, the request will time out
  and we will see the error.
  

Local fix

• In order to fix this, the IZUFPROC must be updated with a DD
  STATEMENT that points to the LE MSGFILE. For example, if you are
  using a MSGFILE name of LEMSG, you are required to add the
  following to your IZUFPROC:
  
  //LEMSG   DD SYSOUT=*
  
  This will allow the code to process the TSO READY prompt
  successfully and continue the GET request.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of IBM z/OSMF V2R3, V2R2 and V2R1.                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The logon procedure use the Language Environment Message     *
  * file(MSGFILE), which is used for storing runtime             *
  *                                                              *
  * messages from the z/OS data set and file REST service.       *
  *                                                              *
  * If the MSGFILE defined in the logon procedure unable to      *
  * match                                                        *
  *                                                              *
  * with the MSGFILE definition on the system, z/OS data set     *
  *                                                              *
  * and file REST service will not work correctly and may return *
  *                                                              *
  * error message like ?message: receiveResponseHeader: received *
  * unexpected classType=4?.                                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The z/OS data set and file REST service write runtime
  messages to a common messages file. The messages describe
  error conditions and suggest possible solution to the errors.
  
  The logon procedure use the Language Environment Message
  file(MSGFILE), which is used for storing runtime
  messages from the z/OS data set and file REST service.
  If the MSGFILE defined in the logon procedure unable to match
  with the MSGFILE definition on the system, z/OS data set
  and file REST service will not work correctly and may return
  error message: ?message: receiveResponseHeader: received
  unexpected classType=4?.
  
  
  To control the destination of message output from
  application, your installation can use Language Environment
  MSGFILE runtime option. Otherwise, if a message file ddname
  is not declared, messages are written to the IBM-supplied
  default definition SYSOUT.
  
  In the logon procedure that is used by the z/OS data set
  and File REST service, ensure that the message file ddname
  is Specified, as follows:
     1. If your installation does not specify a message file
  ddname, you must ensure that the SYSOUT DD statement is
  specified in the logon procedure. For example:
  //SYSOUT DD SYSOUT=H
  
  2. If your installation uses the Language Environment
  MSGFILE runtime option, you must ensure that the logon
  procedure is changed accordingly.
  To view the current MSGFILE definition on your system,
  you can use the following command:
  D CEE,ALL
  
  Which display output, such as the following:
  PARMLIB(CEEPRM60)	MSGFILE(LEMSG,FBA,121,0,NOENQ)
  
  In this example, the message file ddname is LEMSG
  (not SYSOUT).Thus, you would modify the logon
  procedure, as follows:
  //LEMSG DD SYSOUT=H
  
  Or, to write the data to a specific data set, you can
  modify the logon procedure, as follows:
  //LEMSG DD DSN=YOUR.CREATED.DATASET,DISP=OLD
  
  In this example, the diagnostic logs or runtime
  messages are written to the data set that you
  specify. Ensure that data set is created with the
  format FBA,121,0,NOENQ.
  

Problem conclusion

• z/OSMF Configuration Guide was updated to correct the
  
  descriptions.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels