The SESSION keyword restricts rules processing by session name, by a set of session names, or by session type. Using the SESSION keyword instead of complex WHEN clause improves overall message processing throughput. Multiple SESSION statements for the same MSGID rule are cumulative.
This keyword has the following format:
SESSION(name|$type)
Specifies the name of an enabled session defined to the active session definition set. Specifying SESSION(name) causes CA Automation Point to evaluate the message rule only if the message originated from the specified session. Specifying SESSION(*) causes CA Automation Point to evaluate the message rule for messages originating from all sessions.
To restrict the rule to only those messages issued by CA Automation Point itself, use the ”AXC” session name. To restrict the rule to messages generated by the Notification Server, use the “VOX” session name. To restrict the rule to messages received by the CA OPS/MVS Interface, use the “OPS” session name.
Specifies the type of session. Valid values are:
|
ASYNCH |
DTX |
JES3 |
|
JESMCS |
MCS |
RCS |
|
SYSPLEX |
TANDEM |
TANDEMALL |
|
VAX |
VAXALL |
VM |
|
VSE |
|
|
Specifying SESSION($type) causes CA Automation Point to evaluate the message rule only if the message originated from an enabled session of the specified type.
Note: The TPFASYNCH session type is included with other sessions of type ASYNCH. For TPF3270 sessions, you must use the session name to identify the session.
Examples:
MSGID(IEF4501I) SESSION(MACH1_PCON) ALARM(19)
MSGID(IEF4501I) SESSION(MACH1_PCONA) SESSION(MACH1_PCONB) SESSION(MACH1_PCONC) ALARM(19)
MSGID(IEF4501I) SESSION($MCS) WHEN(&WORD2 EQ OS390STC AND &WORD5(9:10) NE 22), COLOR(BRIGHT RED), ALARM(19)
|
Copyright © 2012 CA Technologies.
All rights reserved.
|
|