SELECT, REJECT, CHANGE, and GROUP subcommand keyword groups

The following table lists the keywords that are common to the SELECT, REJECT, CHANGE, and GROUP subcommands.

Keyword Group	Description	Keywords
destination-related keywords	select which destinations to process Note: Most of the destination-related keywords (except AFFINITY) are mutually exclusive. In general, you should only specify one destination-related keyword; however, the following combinations are allowed: DESTINATION and DESTYPE DESTINATION and QTYPE TPNAME and LUNAME TMEMBER and TPIPE HELD and CONVID The AFFINITY keyword is message-related for the REQUEUE command. The QTYPE keyword is destination-related and message-related.	AFFINITY CNT CONVID¹ DBD DEADQ DESTINATION DESTYPE DYNAMIC HELD KEY¹ LTERM LUNAME MSNAME PSB QTYPE RSMB SMB STATIC TMEMBER TPIPE TPNAME TRANSACTION VSPCNT
queue-related keywords	select which queues to process for the selected destinations	QUEUE REGION² REGION_ID²
message-related keywords	select which messages to process for the selected queues	DRRN¹ ENTRYID¹ MFSNAME MSGTYPE NEWER_THAN NODENAME OIMS OLDER_THAN ORIGIN ORGQNAME ORGQMANAGER ORGTPIPE ORGTMEMBER OTMAQ¹ OTOKEN PIMS PTOKEN QPOSITION¹ RCNT START STOP SYSID UOWID USERID
data-related keywords	select which messages to process for the selected queues	DATA DATASIZE OFFSET SEGMENT
other keywords	special purpose	LABEL SCRAPCODE³

^{1 Keyword not allowed with the REQUEUE command}

^{2 Keyword allowed only on the DISPLAY command}

^{3 Keyword allowed only on the REQUEUE command}

Some of the SELECT and REJECT keywords and values are not allowed with certain commands. The following table identifies the command and keyword combinations that are not allowed.

Command	Keywords not allowed
DEQUEUE/UNLOAD	REGION REGION_ID SCRAPCODE
DISPLAY	SCRAPCODE
REQUEUE	CONVID DESTYPE=HELD DRRN ENTRYID HELD KEY OTMAQ QPOSITION QUEUE=SUSPEND, BACKUP, or HELD REGION REGION_ID

Consider the following when specifying SELECT and REJECT subcommand keywords:

If you only use destination- and queue-related keywords, processing will be fastest since there is no need to examine individual messages.
If you use message prefix-related keywords, each message prefix must be examined, so processing will be slower.
If you use message data-related keywords, processing will be slowest, since all records for each message must be examined.

Related topic

SELECT and REJECT subcommands

SELECT, REJECT, CHANGE, and GROUP subcommand keyword groups

Comments