PK21536: INPUTMSGLEN(0) BEING IGNORED WHEN RECEIVE ISSUED UNDER A BRIDGE FACILITY.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• SCENARIO: Transaction A is started. Trans A does a RECEIVE and
  obtains the input data. Transaction A does a XCTL to program B
  with INPUTMSGLEN(0). Program B issues a RECEIVE.
  
  When running transaction A under a terminal facility, program B
  receives an EOC condition since it received control with
  INPUTMSGLEN(0). This is true for all versions of CICS TS
  that customer has to test with.
  However, when transaction A is executed under a Bridge facility
  (either Start bridge or Link bridge), what occurs depends on the
  version of CICS TS:
  Under TS 2.2 (or previous), the RECEIVE issued by program B
  causes an EOC condition to be returned stemming from
  INPUTMSGLEN(0). No additional Bridge interactions occurs.
  This behavior models what happens when using a terminal.
  Under TS 2.3 (or later), the RECEIVE issued by program B causes
  a RECEIVE vector to be generated. Thus, the fact that program B
  received control with INPUTMSGLEN(0) was ignored.
  
  From examining the trace, the critical difference between TS22
  and TS31 is at the following trace point after the RECEIVE:
  
  AP 2163 BRTC ENTRY - FUNCTION(PROCESS_EXEC_ARGUMENTS)
  
  Under TS22, this function decided NOT to call the Bridge
  Formatter (presumably because INPUTMSGLEN=0 was specified).
  
  Under TS31 (and TS23), this function ignores the fact that
  INPUTMSGLEN=0 was specified and DOES call the Bridge Formatter.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: EXEC CICS RECEIVE command hangs when    *
  *                      issued from task running under the CICS *
  *                      3270 web bridge.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An EXEC CICS RECEIVE command may hang when issued from a task
  running under the CICS 3270 web bridge. This will occur if the
  RECEIVE is issued by an application which was called with a zero
  length INPUTMSG. The receive should be satisfied with zero bytes
  of data but instead the bridge exit is called to process the
  EXEC CICS RECEIVE. No data is available so the bridge exit
  suspends waiting for more data to arrive from the browser. The
  browser is waiting for a response from CICS so the application
  issuing the RECEIVE now hangs.
  

Problem conclusion

• RECEIVE_TC routine in DFHBRTC has been altered to process the
  RECEIVE using any TIOA which is present even if the data
  length is zero.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK17635

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

  UK13655

Modules/Macros

•    DESBREX  DFHBRIC  DFHBRMS  DFHBRSP  DFHBRSPA
  DFHBRSPM DFHBRSPT DFHBRTC
  

Fix information

• Fixed component name

  CICSTS 3.1 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK13655

     UP06/04/26 P F604

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.