PK53820: A LINKBRIDGE FLOW APPEARS TO LOOP. DFHMAVCP RECEIVES AN UNEXPECTED MAP AND JUST RETURNS IT TO THE LINKBRIDGE.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An application did a SENDMAP followed by a RECEIVE map with no
  intervening input.  These maps were presented to DFHMAVCP as
  two vectors in one commarea.  The SENDMAP was the first vector
  and the RECEIVE the second.  However, the SENDMAP vector was
  unexpected.
  DFHMAVCP returns the SENDMAP back to LINKBRIDGE, the backend
  application sees it as if no data entry had occurred and sends
  it back to acquire some, and the process repeats itself.  The
  vector log file fills up with repeating entries.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS SFR users.                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: A SEND MAP followed by a RECEIVE MAP    *
  *                      request travels back and forth between  *
  *                      CICS and SFR (via LINK3270).  The       *
  *                      request appears to loop.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the reported problem a SEND MAP was followed by a RECEIVE
  MAP with no intervening input.  This request presented itself
  to DFHMAVCP as 2 vectors in one commarea, the SEND followed
  by the RECEIVE.  However, this combination was unexpected.
  Usually, the SEND MAP would have been forwarded to SFR for
  field data entry in the ADSD. This did not happen, instead,
  DFHMAVCP returned the request to the backend via linkbridge.
  The back-end application interpreted that nothing had changed
  and returned the map where the process repeated itself.
  

Problem conclusion

• DFHMAVCP has been modified to correctly handle the way it
  processes maps.
  

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:

  UK30138

Modules/Macros

•    DFHMAVCP
  

Fix information

• Fixed component name

  SERVICE FLOW FE

• Fixed component ID

  5655M1502

Applicable component levels

• R200 PSY UK30138

     UP07/10/16 P F710

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.