Managing Cross-System Message Traffic › Creating Collection Sets to Enable Cross-System Message Routing › Important Considerations for the COLLECT Command

Important Considerations for the COLLECT Command

Although the syntax of the COLLECT command does not change when using it to collect messages from z/VM systems, you should be aware of some important considerations:

• The ACTION/NOACTION parameters are useful only if you are using the ACTIONPREFIX, ACTIONTYPE, and ACTIONUSER parameters to designate selected messages as highlighted action messages.
• The JOBNAME/NOJOBNAME parameters are used to refer to user IDs issuing messages on a z/VM system. CA MIC for z/VM interprets job names as user IDs (the same as CA MIA for z/VM). Every message in z/VM has a user ID associated with it.

  The user ID represents the origin of the message. For SCIF messages, this is the user ID that is forwarding messages to its secondary user. For message types MSG, WNG, or SMSG, this is the user ID where CP MSG, WNG, or SMSG commands were issued. For all other types, this is the user ID receiving the message (the user ID where the message was originally captured).

• The LOGONLY/NOLOG parameters have no meaning when collecting messages from a z/VM system because there are no log only messages in z/VM.
• The MONITOR/NOMONITOR/DMONITOR parameters have no meaning when collecting z/VM messages because there are no monitor types associated with z/VM messages.
• The ROUTCDE/NOROUTCDE/DROUTCDE parameters have meaning only if route codes have been assigned to z/VM messages using the CA MIC for z/VM ROUTE command or GCMSRCXT exit routine.
• The WTOR/NOWTOR parameters have no meaning when collecting z/VM messages because there are no WTOR-type messages in a CMS environment.