&INTCONT

Propagates a message read using &INTREAD to the next higher processing environment.

&INTCONT [ COLOR=color | COLOUR=colour] 
         [ HLIGHT=highlight ] 
         [ INTENS={ HIGH | NORMAL } ] 
         [ ALARM= { YES | NO } ] 
         [ NRD={ NO | OPER } ]

After an &INTREAD statement, a procedure can propagate the received message to the terminal (if the executing process is not a dependent of a higher level process), or to the dependent response queue of the next higher level process ( if the executing process is running in a dependent processing environment).

When an &INTCMD statement is processed, the command associated with it is executed in the issuing process's dependent processing environment. The command is processed in the normal manner but all command responses are returned to the originating process's dependent response queue and not the user's terminal. The issuing process can then use the &INTREAD statement to retrieve queued responses one by one.

&INTCONT allows the messages received by a process executing as a dependent to be passed up the hierarchy, without having to be the subject of explicit &WRITE statements. Optionally, some attributes of the message is altered.

Operands:

COLOR=color | COLOUR=colour: If the color attribute of the message received from &INTREAD is to be changed, specify the new color by using this operand. The existing color attribute of the message is tested by examination of the &ZMCOLOUR message profile variable set after execution of &INTREAD.
HLIGHT=highlight: If the display highlighting attribute of the message received from &INTREAD must be changed, use this operand to specify the new attribute. The existing highlighting attribute for the message is tested by examining the &ZMHLIGHT message profile variable set after executing &INTREAD.
INTENS={ HIGH | NORMAL }: If the INTENS (intensity) attribute of the message received from &INTREAD must be changed, use this operand to specify the new attribute. The existing INTENS attribute for the message is tested by examining the &ZMINTENS message profile variable set after executing &INTREAD.
ALARM={ YES | NO }: If the ALARM attribute of the message received from &INTREAD must be changed, use this operand to specify the new attribute. The existing ALARM attribute for the message is tested by examining the &ZMALARM message profile variable set after executing &INTREAD.
NRD={ NO | OPER }: If the non-roll delete attribute for the message received from &INTREAD must be changed, use this operand to specify the new attribute. The existing NRD attribute of the message is tested by examining the &ZMNRD message profile variable set after executing &INTREAD. NRD=YES is specified but is ignored; full non-roll delete with DOM correlation can only be set by the message originator, for example, &WRITE.

Examples: &INTCONT

&IF &ZMALARM = YES AND &INTYPE = RESP &THEN +
   &INTCONT ALARM=NO COLOR=RED 
&IF &ZMREQSRC = USER &THEN +
   &INTCONT HLIGHT=REVERSE

Notes:

&INTCONT only propagates messages that are received after executing &INTREAD TYPE=RESP, or after &INTREAD TYPE=ANY is satisfied by a message from the procedure's dependent response queue. Messages satisfying &INTREAD TYPE=REQ cannot be propagated by &INTCONT. The procedure will terminate in error if you attempt to use &INTCONT to propagate a request message.

&INTCONT operates on the previous $INT MDO retrieved by an &INTREAD. Values in the $INT MDO is modified before the &INTCONT is issued, and will be reflected in the message that is propagated. Care should be taken when modifying attributes that affect message flow control. Modification of the $INT.SOURCE.TIME, $INT.DOMID or $INT.PREFIX can cause unpredictable results.

The message profile variable &ZINTYPE is set to a value of RESP if &INTCONT is used to propagate the message.

Note: For more information, see the Network Control Language Programming Guide.

More information:

&INTREAD

&INTCLEAR