&AOMDEL

&AOMDEL is used within an AOMPROC procedure to request that the message that was previously delivered for processing by &AOMREAD be deleted.

Options allow deletion as follows:

Completely, thus indicating that no further delivery of the message occurs
From the local system only. Automatic ISR delivery can still occur.
From ISR automatic delivery only. The message can still be locally delivered.
From a specific ISR link, or from all ISR links.

If the current message is an MVS DOM-notify message, &AOMDEL is treated as an &AOMCONT.

This verb has the following format:

&AOMDEL [ ALL | LOCAL | REMOTE | LINK={ * | link } | DOMAIN={ * | domain } ]
        [ DOM-NOTIFY={ NO | YES } ]

Operands:

ALL

Deletes the current message completely. No further processing takes place. The message is not delivered to authorized AOM receivers, nor is it logged. No automatic ISR delivery takes place. Following this statement, this AOMPROC no longer owns the message, and until another &AOMREAD is executed, the message-related system variables are null.

For a multiline message, only the current line is processed, and the next line is made available by issuing &AOMREAD MINOR=YES. If this line was the last line, or if the next &AOMREAD has MINOR=NO specified, then the entire message is released.

LOCAL

Deletes the current message from the local system. Possible automatic ISR delivery is still to be processed. Following this statement, this AOMPROC no longer owns the message, and until another &AOMREAD is executed, the message-related system variables are null.

This operand is invalid when processing minor lines of a multiline message. If specified for the major line, the entire message is processed.

REMOTE

Delivers the current message to the local system. Possible automatic ISR delivery is not performed. Following this statement, this AOMPROC no longer owns the message, and until another &AOMREAD is executed, the message-related system variables are null.

This operand is invalid when processing minor lines of a multiline message. If specified for the major line, the entire message is processed.

Because the message is locally delivered, if the message had the NRD=YES attribute, the system variable &ZDOMID has the region-assigned DOMID. This DOMID is used to delete the message later from OCS consoles.

LINK={ * | link | DOMAIN={ * | domain }

Allows the prevention of automatic or specific delivery to a specific ISR link, specified by LINK=link or DOMAIN=domain, or prevents any further automatic or specific delivery to all ISR links, specified by LINK=* or DOMAIN=*.

In either case, the message remains under the control of the current AOMPROC.

When LINK=link or DOMAIN=domain is specified, the &ZFDBK system variable is set as follows:

0: Indicates that the message is blocked from delivery to the specified ISR link.
4: Indicates that the specified ISR link is not found or not enabled for AOM flow.
24: Indicates that an &AOMCONT verb or previous automatic ISR delivery has already sent a copy of the current message.

When LINK=* or DOMAIN=* is specified, the &ZFDBK system variable is always set to 0.

DOM-NOTIFY={ NO | YES }

Indicates whether this AOMPROC wants to be notified of any future MVS DOM for this message. This option is not valid with LINK= or DOMAIN=.

DOM-NOTIFY=YES causes the procedure to receive a DOM=notify message when AOM receives an MVS DOM that matches the message.

This operand is abbreviated to DN.

Note: Many messages never have a matching DOM generated, because they were never intended to be NRD messages. Careless use of DOM-NOTIFY=YES can waste excessive storage in the system as it notes all messages that are to be DOM-NOTIFIED.

Examples: &AOMDEL

&AOMDEL

&AOMDEL LOCAL DN=YES

&AOMDEL LINK=NY

Notes:

&AOMDEL LOCAL and &AOMDEL REMOTE complement &AOMCONT REMOTE and &AOMCONT LOCAL, except that no message attributes is altered with &AOMDEL.
&AOMDEL LINK=* or DOMAIN=* also prevents the following &AOMCONT LINK= or DOMAIN= from sending a message. The &ZFDBK system variable is set to 4.
Issuing an &AOMDEL when no message is current causes the procedure to terminate abnormally with an error message.

More information:

&AOMCONT

&AOMREAD

&AOMREPL