AFFINITY keyword - SELECT and REJECT subcommands

Use the AFFINITY keyword to select or reject messages with a specific affinity. The AFFINITY keyword allows a seven-character affinity mask. Consider the following when specifying the AFFINITY keyword:

  • The affinity is the IMSID for non-XRF systems. For XRF systems, the affinity is the first seven characters of the RSENAME.
  • You can specify a list of affinities for the AFFINITY keyword value. The list can include the special values that are described in the below table. For example, AFFINITY=(&NONE,IMSA) returns only destinations with no affinity or with affinity to IMSA.
  • If you do not specify the AFFINITY keyword, Message Advisor returns all destinations which otherwise match, with or without an affinity.
  • You can specify AFFINITY=&NONE or AFFINITY=' ' to return only destinations with no affinity.
  • If you specify a mask for the AFFINITY keyword value, Message Advisor only returns destinations with an affinity that matches the mask. Message Advisor does NOT return destinations without an affinity (i.e., Message Advisor treats AFFINITY=* the same as it treats AFFINITY=?*).
  • Local queue destinations (on non-shared queues systems or on shared queues systems) are considered to have no affinity and will only match a blank or a SELect subcommand without an affinity.
  • AFFINITY is a message-related keyword when used on a SELect or REJect subcommand with the REQueue command, but is a destination-related keyword for all other commands.
  • If you specify either (but not both) &EXISTS or &ORPHAN, processing occurs as follows:
    • Message Advisor performs a FNDEST CREATE for destinations that it finds on the shared queues with an affinity for the current IMS.
    • If Message Advisor cannot find or create the destination, the destination matches &ORPHAN.
    • If Message Advisor finds or creates the destination but the destination is not of the correct type for that queue, the destination matches &ORPHAN.
    • For queue 7 and queue 9, the destination will also match &ORPHAN if the shared queues token does not match the IMS token.
    • Destinations that exist or that Message Advisor can create as the correct type match &EXISTS.

The intent of the above processing is to allow finding messages on the shared queues which can no longer be processed, and are thus 'orphaned.'

Parameter

Description

mmmmmmm

matches destinations with the specified affinity

Note

mmmmmmm is a value that you specify. You can specify a list of values or patterns.

&EXISTS

matches only destinations with affinity to the current IMS and which CAN be created on the current IMS

Note

&EXISTS is not allowed on SELect or REJect subcommands with the REQueue command.

&IMS

matches only destinations with an affinity for the current IMS

Note

&IMS is not allowed on SELect or REJect subcommands with the REQueue EXTRACT command.

AFFINITY=(&EXISTS,&ORPHAN) is the same as AFFINITY=&IMS.

&NONE

matches only destinations with no affinity

&ORPHAN

matches only destinations with affinity to the current IMS and which CANNOT be created on the current IMS

Note

AFFINITY=&ORPHAN will not necessarily find all messages that cannot be processed. Messages without affinity will never match, since there may be another IMS that can process them even if the IMS is not currently active. There may also be LTERMs that can still be created by VT or ETO, which are no longer used. You may need to specify a time interval to locate these messages and LTERMs.

&ORPHAN is not allowed on SELect or REJect subcommands with the REQueue command.

Related topic

SELECT-and-REJECT-subcommands-for-shared-queues



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*