Middleware News

MAXHANDS (Maximum Open Handles) is the queue manager parameter that limits the number of handles that any one process can have at the same time. The details relating to it are as follows: Setting MAXHANDS: Alter the MAXHANDS queue manager parameter using the MQSC   alter queue manager   command. Example:   alter qmgr maxhands (300) On Windows you can also use the WebSphere MQ Explorer to alter the queue manager's Max handles, extended property. MAXHANDS(integer):   The maximum number of open handles that any one task can have at the same time. This is a value in the range zero through 999 999 999.   For clarification:   MAXHANDS refers to the maximum number of objects that a single connection can have open at the same time. So, if an application thread issues an MQOPEN for a queue, that counts as 1, and so on for each queue that is opened in that thread. A separate thread in the same or in a different process also has its own MAXHANDLES objects that it can open. The

The tables on this page list all the attributes that you can set for local and remote queue managers. For each attribute, there is a brief description of when you might need to configure the attribute. Where relevant, the tables also give the equivalent MQSC parameter for the ALTER QMGR and DISPLAY QMGR commands. For more information about MQSC commands, see   Script (MQSC) Commands   in the   IBM®   online WebSphere®   MQ   information center. Those attributes for a queue manager that are changed through MQSC using the ALTER QMGR commands are the ones that are shown for both local and remote queue managers. Note, that the   WebSphere   MQ   Explorer does not show all the properties for remote queue managers. Those attributes that are defined in the   qm.ini   file (for UNIX systems) or in the Registry (for Windows), are the ones that are shown only for local queue managers. For example, the specification for the Recovery Logs and the XA apply to the   qm.ini   file, and so, is