Home

 

Rules for naming WebSphere MQ objects

 

WebSphere MQ authentication information, channel, client channel, listener, namelist, process, queue, service and storage class objects exist in separate object name spaces, and so objects from each type can all have the same name. However, an object cannot have the same name as any other object in the same name space. (For example, a local queue cannot have the same name as a model queue.) Names in WebSphere MQ are case sensitive.

The character set that can be used for naming all WebSphere MQ objects is as follows:

• Uppercase A–Z

• Lowercase a–z (however, on systems using EBCDIC Katakana we cannot use lowercase characters, and there are also restrictions on the use of lowercase letters for z/OS console support)

• Numerics 0–9

• Period (.)

• Forward slash (⁄)

• Underscore (_)

• Percent sign (%). The percent sign (%) is a special character to RACF. If you are using RACF as the external security manager for WebSphere MQ for z/OS, you should not use % in object names. If you do, these names are not included in any security checks when RACF generic profiles are used.

1. Leading or embedded blanks are not allowed.

2. Avoid using names with leading or trailing underscores, because they cannot be handled by the WebSphere MQ for z/OS operations and control panels.

3. Any name that is less than the full field length can be padded to the right with blanks. All short names that are returned by the queue manager are always padded to the right with blanks.

4. Any structure to the names (for example, the use of the period or underscore) is not significant to the queue manager.

• Name lengths
  

• Generic values
  

 

Parent topic:

Using Programmable Command Formats

pc10510_

 

Home