A fix is available
APAR status
Closed as program error.
Error description
MQ panels shows shared channels status 'START' when PF11 shows them in RUN. Also MQExplorer shows them in RUNNING as well. This started after DB2 was unavailable and then became available shortly after. The following messages is issued every minute to the CHIN joblogs: CSQX478E - CSQXRCTL Channel xxx.TO.xxxx is active on AAAA, connection tag in use CSQX599E - CSQXRCTL Channel TQSG.TO.RBCTOQ02.POS ended The CSQX478E messages generated at regular intervals are caused by start commands issued internally by the CHIN supervisor because the DB2 SCST (Shared channel status table) shows that channels require restart but the start channel commands fail as the channels are already active. The shared channel status is not updated in the SCST when the start command fails. This APAR is raised to resync the DB2 shared channel status during a START channel command that finds that channel is already running.
Local fix
Stop the channel to STOPPED state and then manually start the channel. If the status changes to RUN it will clear the issue. If not, a restart of the queue manager will clear it.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: After a DB2 outage, shared channel * * status shown in MQ ISPF panels and/or * * DIS CHSTATUS command is "START" or * * "STARTING" while local channel status * * is "RUN" or "RUNNING". * * * * The CHIN is issuing a START CHANNEL * * command to all shared channels in * * "START" or "STARTING" status every 60 * * seconds. This command fails with * * message CSQX478E indicating that the * * channel is already running. * **************************************************************** * RECOMMENDATION: * **************************************************************** A DB2 outage can prevent queue managers in a QSG to update the shared channel status in DB2 from "STARTING" to "RUNNING" causing the incorrect status displays and the CHIN to try to restart channels that are already running.
Problem conclusion
The Start channel command has been enhanced to synchronise the shared channel status in DB2 with the local channel status when the channel is running on the local queue manager. 100Y CSQXRSER
Temporary fix
Comments
APAR Information
APAR number
PI36127
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-03-02
Closed date
2015-03-24
Last modified date
2015-05-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI37189 UI26234
Modules/Macros
CSQXRSER
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI26234
UP15/04/30 P F504
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.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 May 2015