Advanced Topics › Message Processing › How You Create Message Collection Sets

How You Create Message Collection Sets

Message routing definitions, or collection sets, are defined using the COLLECT command. A collection set is identified by its local destination unless the SETNAME parameter is also specified.

The COLLECT command differs from the LINK command in that collection sets are used to route UNSOLICITED WTOs, such as tape mounts, job start and end messages, and printer messages. Linkages are used to issue cross-system commands and automatically receive command responses (SOLICITED WTOs). These responses are returned to the issuing system, regardless of any collection sets defined.

Collection sets define the routing of unsolicited cross-system messages. The COLLECT command defines a collection set by identifying:

• Types of messages that need to be imported to the local system
• Systems from which the messages are to be imported
• Local destination to which the imported messages are to be routed

Message selection criteria are quite flexible, as is the number of local destinations that can receive imported messages. As a result, you can create collection sets tailored to the requirements of your site. Some of the most common uses of collection sets are:

• Direct imported messages to all local consoles, individual local consoles, local products, or local TSO users
• Record imported messages to the local SYSLOG
• Direct messages from specific jobs to specific TSO users

Note: For more information about the COLLECT command and COLLECT command syntax, see the Statement and Command Reference Guide.

You can create a collection set that broadcasts messages to all consoles assigned the same routing code or monitor type. For example, you can route cross-system tape messages to any local console that receives local tape messages, while cross-system unit record messages are only presented to local consoles accepting local unit record messages.