A fix is available
APAR status
Closed as program error.
Error description
MQ Development finds that a hostname lookup failed for a specified LOCLADDR while the associated channel was attempting to start. This caused the CHIN to build a CSQX235E message to report this, and the 0C4 abend occurred while building this message. The length of the first line of the message was long enough that it needed to be split over 2 lines, and it's in this processing where the problem lies. An invalid combination of flags in the CHINIT message control block (xMcb) results in a message LLZZ being interpreted as a buffer address. This problem was introduced by PTF UI68821.
Local fix
Ensure LOCLADDR value is resolvable.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 1 Modification 0 and * * Release 2 Modification 0 and * * Release 3 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Starting a channel with an invalid * * LOCLADDR value thats length is greater * * than 25 characters causes errors. * * * * At V910 an S0C4-00000011 abend in seen * * in CSQFSAMG in the channel initiator * * address space. * * * * At V920 & V930 the message CSQX235E * * is incorrectly formatted and the * * LOCLADDR value printed with the message * * is incorrectly truncated. * **************************************************************** When starting a channel with an invalid LOCLADDR value thats length is greater than 25 characters, errors are seen as part of printing the message CSQX235E in the channel initiators joblogs to report the invalid LOCLADDR value. At V910 an S0C4-00000011 abend in seen in CSQFSAMG in the channel initiator address space caused by a regression introduced by PTF UI68821. At V920 & V930 the message CSQX235E is incorrectly formatted as the LOCLADDR value printed with the message fails to be moved to a new line and is thus incorrectly truncated.
Problem conclusion
At V910 the regression introduced by PTF UI68821 has been corrected so that the CSQX235E message is correctly printed to the channel initiators joblogs and the S0C4 abend is not issued. At V920 & V930 the formatter processing message CSQX235E has been corrected to utilise multiple lines to display the LOCLADDR value if its length is greater than 25 characters long and will not be truncated.
Temporary fix
Comments
APAR Information
APAR number
PH47563
Reported component name
IBM MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
100
Status
CLOSED PER
PE
YesPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-06-28
Closed date
2023-03-20
Last modified date
2023-05-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI91039 UI91040 UI91041
Modules/Macros
CSQFXLAT CSQMCNAC CSQUMSG CSQXCCCX CSQXCCIS CSQXGINI CSQXMSG CSQXRPLY
Fix information
Fixed component name
IBM MQ Z/OS V9
Fixed component ID
5655MQ900
Applicable component levels
R100 PSY UI91041
UP23/04/08 P F304 {
R200 PSY UI91040
UP23/04/07 P F304 {
R300 PSY UI91039
UP23/04/07 P F304 {
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"100","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 May 2023