Specifies how the command is executed when the queue manager is a member of a queue-sharing group. You can specify one of the following:
The maximum length is MQ_QSG_NAME_LENGTH.
This indicates whether the information about repository queue managers should be refreshed.
The value can be:
This value cannot be specified if the queue manager is itself a repository queue manager.
MQCFO_REFRESH_REPOSITORY_YES specifies that in addition to MQCFO_REFRESH_REPOSITORY_NO behavior, objects representing full repository cluster queue managers are also refreshed. Do not use this option if the queue manager is itself a full repository.
If it is a full repository, you must first alter it so that it is not a full repository for the cluster in question.
The full repository location is recovered from the manually defined cluster-sender channel definitions. After the refresh with MQCFO_REFRESH_REPOSITORY_YES has been issued the queue manager can be altered so that it is once again a full repository.
If you select MQCFO_REFRESH_REPOSITORY_YES, check that all cluster-sender channels in the relevant cluster are inactive or stopped before you issue the Refresh Cluster command. If there are cluster-sender channels running at the time when the Refresh is processed, and they are used exclusively by the cluster or clusters being refreshed and MQCFO_REFRESH_REPOSITORY_YES is used, the channels are stopped, by using the Stop Channel command with a value of MQMODE_FORCE in the Mode parameter if necessary.
This ensures that the Refresh can remove the channel state and that the channel will run with the refreshed version after the Refresh has completed. If a channel's state cannot be deleted, for example because it is in doubt, or because it is also running as part of another cluster, it is state is not new after the refresh and it does not automatically restart if it was stopped.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzac04231 |