WEBSPHERE MQ V6 QUEUE MANAGER ON OPENVMS DOES NOT START LISTENER OR OTHER SERVICES AT STARTUP DUE TO KN246001 FDC IN AMQZXMA0.EXE - Middleware News

WEBSPHERE MQ V6 QUEUE MANAGER ON OPENVMS DOES NOT START LISTENER OR OTHER SERVICES AT STARTUP DUE TO KN246001 FDC IN AMQZXMA0.EXE - Middleware News


Error Description:

WebSphere MQ v6 queue managers use a program called the process
manager (AMQZMGR0.EXE) to start and monitor services such as
listeners and the command server. In certain environments this
process manager can fail to start queue manager services due to
an unexpected condition. The queue manager may generate FDCs
showing symptoms like the following:
.
Probe Id :- KN246001
Component :- kpiAncillaryProcessStartup
Program Name :- AMQZXMA0.EXE
Major Errorcode :- zrcX_INVALID_OBJECT_TYPE
VMS Errorcode :- -RMS-E-FNF, file not found (00018292)
.
Probe Id :- KN246002
Component :- kpiAncillaryProcessStartup
Program Name :- AMQZXMA0.EXE
Major Errorcode :- ocmRC_UNEXPECTED_CSV_STATE
VMS Errorcode :- -RMS-E-FNF, file not found (00018292)
.
Probe Id :- ZT208001
Component :- zupSetProcessState
Program Name :- RUNMQLSR.EXE
Major Errorcode :- zrcX_PROCESS_NOT_RUNNING
VMS Errorcode :- -RMS-E-FNF, file not found (00018292)
.
.
The process manager itself may not generate any FDC entries, but
a Websphere MQ trace during queue manager startup will show this
program ending shortly after the following pattern:
.
-{ zxpProcessMessage
--{ xcsSimplePipeRead
--} xcsSimplePipeRead rc=OK
Expected 1716 bytes got 1432 bytes
0x0000: 5a535354 35210000 03000000 00000000 |ZSST5!
...
--{ xcsSimplePipeWrite
--} xcsSimplePipeWrite rc=OK
--{ xcsDisconnectSimplePipe
...
--} xcsDisconnectSimplePipe rc=OK
-} zxpProcessMessage rc=OK

Local fix

Problem summary

It is observed that in some cases of third party software
usage as a transport layer, users issuing STRMQM command are
unable to perform remote administration. In Queue Manager
startup, the processes such as "Command Server", "Channel
Initiators", and "Listeners" are not spawned automatically.
As a result remote administration is not possible.
.
In this particular scenario when third party software is
used partial reads are likely to happen. When the partial
read happens, the control comes out of the read loop in the
code and the data read is not equal to the expected bytes.
At later stages a check is made for verifying the number of
bytes read. Since the number of bytes read is not meeting the
expected value, MQ functionality will be not be rendered.
This problem is likely to be noticed when Process Software
"Multinet V5.3" is installed on the system.

Problem conclusion

The common services component of MQ has been changed to fix
these partial reads. The loop containing the read() calls is
modified to ensure that complete data over the socket is read.
The fix for this APAR will be included in next fixpack release
on OpenVMS Alpha and Itanium.
.
In order to make this fix functional, it is mandatory to define
below the mentioned logical before queue manager start.
.
The command to define the logical: AMQ_SUPPORT_MULTINET :
.
$ Define /system AMQ_SUPPORT_MULTINET "1"