A system variable that contains the MVS-assigned Delete Operator MessageĀ (DOM) ID of the current message.
Every WTO/WTOR message has an associated DOMID. This ID is normally used to associate a non-roll delete WTO/WTOR message with a subsequent DOM. A DOM is generated to delete a particular non-roll delete WTO/WTOR message that is no longer required by the system.
For example, when an address space terminates it can generate a DOM message to delete outstanding non-roll-delete messages that were associated with the address space.
This DOMID is supplied in the &AOMDOMID system variable following an &AOMREAD that returns a WTO, WTOR, or MVS-sourced EVENT. &AOMALERT-generated WTO or EVENT messages are also assigned a DOMID. It is also supplied when a DOM-Notify message is received by AOMPROC.
The DOMID is formatted as 8 hexadecimal digits. The first 2 are a system ID and the last 6 are the message number.
Examples: &AOMDOMID
-* read messages and DOM-notifies.
.LOOP
&AOMREAD SET
-* if NRD001 save domid
&IF .&AOMMSGID = NRD001 &THEN &DO -* want notify
&SAVEID = &AOMDOMID -* save domid
&AOMCONT DOM-NOTIFY=YES -* indicate notify
-* wanted & GOTO .LOOP
&DOEND
&IF &AOMTYPE = DOM &THEN &DO -* got dom notify
&if .SAVEID = .&AOMDOMID &THEN &DO
.
. -* process notify
.
&GOTO .LOOP
&DOEND
Notes:
ID contained in this system variable is generated by MVS, and as such is useful only for message correlation within an AOMPROC, or for use as the ID for an &DOM verb. Automation Services generates its own internal DOMID for messages sent to OCS consoles.
The DOMID is used to correlate a message with the arrival of the associated DOM-NOTIFY.
Another use is to issue an MVS DOM using the &DOM verb for NRD messages that MVS does not itself delete.
| Copyright © 2009 CA. All rights reserved. |
|