A fix is available
APAR status
Closed as program error.
Error description
When the customer runs CSQ1LOGP with EXTRACT(YES) and CSQINFLT DD, the data in CSQINFLT output appears corrupted. Customer have never seen this problem before. They didn't see the problem when they used any other archive log. Other outputs (e.g. summary, detail report, CSQCMT output) have no problem. . The change team has taken a look at the doc and they can see the cause of the problem. It occurs when an archive dataset contains the log records for an MQPUT of a message which is greater than 32K, but not all of the log records for the MQPUT are contained in the archive dataset being processed i.e. the rest of the log records for the MQPUT are in the following or next archive dataset.
Local fix
If CSQ1LOGP EXTRACT is run with current archive log together with the next archive log, then this problem should not be seen.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 0 Modification 1 and Release 1 * * Modification 0 * **************************************************************** * PROBLEM DESCRIPTION: When running CSQ1LOGP with EXTRACT(YES) * * the output in the CSQINFLT dataset * * appears incorrect. * **************************************************************** * RECOMMENDATION: * **************************************************************** When running CSQ1LOGP to extract data from an archive log CSQ1LEXT, the extract routine, may encounter the end of the log before it has managed to collect all of the log records for that message. In the case of a large message log records are written so that the IRH3 appears first, then the IRHA types, followed later by IRH8 / IRH9. CSQ1LEXT marks the very first page of the message with msg_page_type of 'F', however in the case of a long message this would be done on the IRH9, but CSQ1LEXT has reached the end of the log without collecting the IRH9. Having reached the end of the log CSQ1LEXT calls the Terminate procedure to write out the inflight record(s) to the CSQINFLT dataset but because the message doesn't have the msg_page_type of 'F' then it doesn't create any output header information and therefore the message written out to the dataset is incorrect.
Problem conclusion
CSQ1LEXT has been changed so that the incomplete data is not written out to the CSQINFLT dataset. 010Y 100Y CSQ1LEXT
Temporary fix
Comments
×**** PE16/04/18 FIX IN ERROR. SEE APAR PI60875 FOR DESCRIPTION ×**** PE16/04/18 FIX IN ERROR. SEE APAR PI60875 FOR DESCRIPTION
APAR Information
APAR number
PI30907
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
010
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-12-04
Closed date
2015-03-30
Last modified date
2016-04-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI35177 UI26367 UI26368
Modules/Macros
CSQ1LEXT
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
29 April 2016