Propagates a message read via &INTREAD to the next higher processing environment, and optionally changes its message text.
&INTREPL [ COLOR=color | COLOUR=colour ]
[ HLIGHT=highlight | HLITE=highlight ]
[ INTENS={ HIGH | NORMAL } ]
[ ALARM={ YES | NO } ]
[ SCAN={ YES | NO }
[ NRD={ NO | OPER } ]
[ DATA=replacement text ]
After an &INTREAD statement, a procedure might choose to propagate the entire received message to the terminal (provided the executing process is not the 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 the statement 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 to the user's terminal. The issuing process can then use the &INTREAD statement to retrieve queued responses one-by-one.
&INTREPL allows messages received by a process executing as a dependent, to be passed up the hierarchy without having to use explicit &WRITE statements—the message text is changed before propagation occurs.
Operands:
If the color attribute of the message received from &INTREAD must be changed, use this operand to specify the new color. The existing color attribute of the message is tested by examining the &ZMCOLOUR message profile variable set after executing &INTREAD.
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.
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 of the message is tested by examining the &ZMINTENS message profile variable set after executing &INTREAD.
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 of the message is tested by examining the &ZMALARM message profile variable set after executing &INTREAD.
Indicates that the text of the message does or does not include the highlighting character, (@). Specify SCAN=YES if your replacement text includes this character to highlight individual words in the message.
If the non-roll delete attribute of 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.
Specifies the text for the message that is to replace the text received after the &INTREAD operation. The entire text must be coded. DATA can only be specified as the last keyword on the statement, because the data string is regarded as being everything right of the DATA= keyword, to the end of the statement.
Examples: &INTREPL
&IF &ZMALARM = YES &THEN +
&INTREPL COLOR=RED INTENS=HIGH +
DATA=*IMPORTANT* &ZMTEXT
Notes:
&INTREPL only propagates messages received by executing &INTREAD TYPE=RESP, or after &INTREAD TYPE=ANY is satisfied by a message from the procedure's dependent response queue. Messages that satisfy &INTREAD TYPE=REQ cannot be propagated by &INTREPL. The procedure terminates in error if you attempt to use &INTREPL to propagate a request message. The message profile variable &ZINTYPE is set to a value of RESP if &INTREPL is used to propagate the message.
Attributes of the message can also be changed by modifying the $INT by modifying the $INT MDO before issuing the &INTREPL or &INTCONT. Some care should be taken when modifying message attributes in this way, as some attributes affect processing control. Also, some attributes will be reset by the system during message re-delivery.
Note: For more information, see the Network Control Language Programming Guide.
| Copyright © 2009 CA. All rights reserved. |
|