A fix is available
APAR status
Closed as program error.
Error description
The problem happens when queues are defined only on full repositories which are in more than one cluster, then one of the clusters is removed from the namelist. . FFST snap was issued due to missing subscription for cluster queue detected by rrmCheckSubsForQueue called by cluster maintenance routine. . * X...XFFSrrmCheckSubsForQ* *ueue............MOVR..........U.* *X...XINS........................* *................................* . PAGE 00000002 . * ....Missing subscription* *WQR .......M....<queue_name> * * * *QMGR.CEBE1D2A2B0BB60D * * ..N..... * * * * ........* *.................... * . In the CHIN log, you also see the error messages: . +CSQX053E SSID CSQXFFST Error information recorded in CSQSNAP data set +CSQX420I SSID CSQXREPO No repositories for cluster CLUS10009 +CSQX053E SSID CSQXFFST Error information recorded in CSQSNAP data set +CSQX053E SSID CSQXFFST Error information recorded in CSQSNAP data set +CSQX448E SSID CSQXREPO Repository manager stopping because of errors. Restart in 600 seconds . The following message will then be issued after 600 seconds if no action is taken: . +CSQX037E CSQXREPO Unable to get message from SYSTEM.CLUSTER.COMMAND.QUEUE, MQCC=2 MQRC=2016 Additional Symptom(s) Search Keyword(s):
Local fix
In order to get the repository manager back up again you should issue REFRESH CLUSTER(*)
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: Message CSQX420I is issued indicating * * no repository exists for a cluster. * * This is followed by an FFST indicated * * by message CSQX053E and then the * * repository manager terminates with * * CSQX448E. * **************************************************************** * RECOMMENDATION: * **************************************************************** The cluster maintenance routine finds a queue which has its refresh bit on but has no subscriptions for that queue. This can occur if the queue exists in a cluster which has since been removed. The maintenance routine tries to remake the subscriptions, however it finds that there are no longer any full repositories for that cluster and this causes the repository manager to terminate.
Problem conclusion
The cluster maintenance routine now tolerates the condition where no full repositories are found for a given cluster, allowing the repository manager to continue executing after issuing the FFST to report the missing subscription. 100Y CMQXRMNT
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI42288
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-06-03
Closed date
2015-07-29
Last modified date
2015-10-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI29819
Modules/Macros
CMQXRMNT
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI29819
UP15/09/09 P F509 ¢
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:
22 October 2015