WebSphere MQ dmpmqcfg output is truncated and only has subset of objects
When using WebSphere MQ dmpmqcfg command to create a backup copy of a queue manager's configuration, only a partial list of objects and attributes is stored in the output file.
If your queue manager has a large number of objects, the dmpmqcfg process may fill the SYSTEM.ADMIN.COMMAND.QUEUE which has a default maxdepth of 3,000. This will cause the dmpmqcfg script to stop before it has completed writing all object definitions to the output file.
The dmpmqcfg command uses PCF command messages. If the number of objects and attributes to be documented in the output file is more than can be processed by the command server before reaching the maximum depth on the command queue, it can fill up and you may see error message:
AMQ9511: Messages cannot be put to a queue
Resolving the problem
If your queue manager has a large number of objects and you encounter this problem, you may avoid it by raising the MAXDEPTH attribute on the SYSTEM.ADMIN.COMMAND.QUEUE to resolve the problem.