The Connection Manager uses a model queue for creation of temporary dynamic queues, used for command processing and message retrieval. The default is SYSTEM.DEFAULT.MODEL.QUEUE. Rather than alter the system queue if some parameter customization is needed, you can create a custom model queue to be used instead, say NSQCM.MODEL.QUEUE, with, for example, a very large MAXMSGL parameter value for retrieving very large messages. Enter the new queue name in the NASTEL.MODEL.QUEUE line in file [APWMQ_HOME]\config\groups\mqqual.ini. When the APWMQ agent starts, it will check the qualifiers file and use that model queue instead of the default.
Articles in this section
- Event ID 3242...Failed to send V2 trap...NoSuchElement in policy's event viewer
- Object name not displaying in Favorite Objects viewlet
- Why is the table adtinfo so large?
- Nodes not displaying in new viewlets, but are visible on the WorkSpace dashboard
- What do the blue lines in front of object definition fields mean?
- Why do I get error 2270 (MQRC_NO_DESTINATIONS_AVAILABLE) when trying to put messages on a cluster queue with APMW Explorer, Nastel Navigator or IBM sample amqsput?
- Can I use an alternate model queue with customized parameters in the Connection Manager instead of modifying SYSTEM.DEFAULT.MODEL.QUEUE?
- How do I audit usage of requests or changes made using Nastel Navigator?
- Benefits of Agent and Agentless Data Collection
- Updating your expiring Workgroup Server Expert 10.x license for Nastel Navigator