Manual cleanup
If you use the broker-based subscription store, we can operate cleanup manually from the command-line. The syntax for bindings attach is:
Cleanup [-m <qmgr>] [-r <interval>] [SAFE | STRONG | FORCE | NONDUR] [-t]or, for client attach:Cleanup -client [-m <qmgr>] -host <hostname> [-port <port>] [-channel <channel>] [-r <interval>] [SAFE | STRONG | FORCE | NONDUR] [-t]Where:
- qmgr, hostname, port, and channel determine connection settings for the queue manager to clean up.
- -r sets the interval between executions of cleanup, in minutes. If not set, cleanup is performed once.
- -t enables tracing, to the mqjms.trc file.
- SAFE, STRONG, FORCE, and NONDUR set the cleanup level, as follows:
- SAFE and STRONG cleanup behave like the CLEANUP(SAFE) and CLEANUP(STRONG) options discussed in Subscriber cleanup utility.
- FORCE cleanup behaves like STRONG Cleanup. However, STRONG cleanup leaves messages that could not be processed on the SYSTEM.JMS.REPORT.QUEUE; FORCE cleanup removes all messages even if it encounters an error during processing.
Warning: This is a dangerous option that can leave an inconsistent state between the queue manager and the broker. It cannot be run while any &mqjms; &pubsub; application is running against the queue manager; doing so causes the cleanup utility to abort.- NONDUR behaves like FORCE cleanup.
After clearing the SYSTEM.JMS.REPORT.QUEUE, it attempts to remove any remaining unconsumed messages sent to non-durable subscribers. If the queue manager's command server is running on any queue beginning SYSTEM.JMS.ND.*, messages are cleared and the queue itself might be deleted. Otherwise, only SYSTEM.JMS.ND.SUBSCRIBER.QUEUE and SYSTEM.JMS.ND.CC.SUBSCRIBER.QUEUE are cleared of messages.
uj24920_