We've recently made some MVS changes but now when looking at our WebSphere MQ channel status via the CSQOREXX panels, the status returned is not correct so we need direction on why that could be. Even though the initial display is incorrect, if we press the STATUS PFKEY, then the correct status is returned. Any idea why ?
Answer by womey (6115) | Apr 03, 2015 at 01:20 PM
You should check the concatenation of SYSEXEC in the LOGON proc. That's been known to cause odd symptoms like this.
See "Task 20: Set up the operations and control panels" in the Configuration section of the WebSphere MQ for z/OS System Setup Guide. There you will find instructions for setting up the libraries for the CSQOREXX panels.
To determine if concatenation is the issue use any of the following methods in the event any one method does not provide all necessary information:
Issue TSO ISRDDN while the main MQ panel is displayed to show current library concatenations. Issue M CSQOREXX, M CSQOXLST, or M CSQORLST on the ISRDDN panel to see which libraries that member is being loaded from. Use this to determine if a backlevel copy is being pulled in. (Note: this can be used for any member name).
Alternatively, use the ISPF call/return trace (ISPVCALL) to see if another library is concatenated before SYS1.MQM.SCSQAUTH(CSQOXLST) which contains CSQOXLST. Use these steps :
Issue the command, TSO ISPVCALL VDEFINE
Display the channels
When control is returned, enter TSO ISPVCALL
On the command line you will see a data set named : "userid.CALL.TRACE"
Use this output to review your library concatenation.
CSQX203E (RC=0000045C) when we start an MQ channel. What could be causing this? 1 Answer
What is the SUBSTATE parameter for DISPLAY CHSTATUS for MQ? 2 Answers
MQ Channel configure options 1 Answer
Can I create an AMQCLCHL.TAB file without including the default system client channel? 1 Answer
Will the connection of inbound channel be disconnected when the listener port is stopped? 1 Answer