Managing Cross-System Message Traffic › COLLECT Command

COLLECT Command

COLLECT commands must be issued on the system where you want to see the messages, not on the system where messages are generated. The COLLECT command is not supported in CA MIC for z/VM, but CA MIC for z/OS can issue a COLLECT command that will cause messages generated on a z/VM system to be sent to a console on the z/OS system.

When you create a collection set, you create a rule that tells CA MIC for z/VM which messages you want to see, the systems from which those messages should be collected, and where on the z/OS system to send the collected messages.

Collection sets define the routing of 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. The following lists the most common uses of collection sets:

• Combine messages from z/VM and z/OS systems on one console.
• Direct selected messages to any specific consoles, TSO users, and products.
• Direct messages from specified z/VM service machines or z/OS jobs to TSO users.