A fix is available
APAR status
Closed as program error.
Error description
SERVER - INFINITE LOOP DURING SEND TO MQ WHEN SPECIFIC DCB LRECL IS USED FOR DATASET BEING SENT TO QUEUE Environment: WDI 3.3.0 for z/OS with current PTF maintenance Intermittent program loop when sending XML data to MQ. The intermittency seems to be due to the data being sent, which varies. When reprocessing the same data, the loop is reproducible. Further analysis found that the intermediate file allocation (DCB) for the data being sent makes a difference. The client's original issue is a DT map going from EDI to XML where the document destination is an MQ queue. L2 support has recreated as such, as well as with a simplified PERFORM SEND command. This allocation seems to trigger the pgm loop: //XMLOUT DD DSN=EDI.XMLOUT, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=2590,DSORG=PS), // SPACE=(TRK,(1000,400),RLSE), // UNIT=SYSALLDA Kewords: WMQ MQSERIES PUT program pgm loop looping loops infinite unbounded hard cancel cancels cancelled logical record rec len length lrecl hang hangs hung
Local fix
A possible work-around is to allocate the (intermediate) file being sent with a different DCB. For example, //XMLOUT DD DSN=EDI.XMLOUT, // DISP=(NEW,CATLG,DELETE), // DCB=(RECFM=VB,LRECL=32750,DSORG=PS), // SPACE=(TRK,(1000,400),RLSE), // UNIT=SYSALLDA
Problem summary
SERVER - INFINITE LOOP DURING SEND TO MQ WHEN SPECIFIC DCB LRECL IS USED FOR DATASET BEING SENT TO QUEUE. The error happens when invalid EDI data is used in the SEND process and the network program incorrectly identifies a segment within the data.
Problem conclusion
The code is changed to avoid EDI envelope scan during OUTTYPE(MQ) when the target syntax is not EDI. The communications interface is also changed to avoid any looping while parsing out segments.
Temporary fix
Comments
WDI 3.3 on all platforms
APAR Information
APAR number
PM94865
Reported component name
WEBS DI ZOS
Reported component ID
5655I4003
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-08-09
Closed date
2013-08-23
Last modified date
2013-10-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK96981
Modules/Macros
C EDITRRE EDIVNPT
Fix information
Fixed component name
WEBS DI ZOS
Fixed component ID
5655I4003
Applicable component levels
R330 PSY UK96981
UP13/09/13 P F309
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.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
22 August 2022