In general, any messages generated by a remote process are routed back to the local host. These include “BOT” and “EOT” messages, display messages, accept messages, and RSVP messages. The following are the only exceptions to this rule:
-
WFL jobs initiated by an AT <hostname> START command. No messages are returned to the local host for such a job. (On the other hand, messages are returned for WFL jobs that use an AT <hostname> specification in the job header.)
-
Non-WFL independent processes. These include any remote processes initiated by an ALGOL or COBOL RUN statement.
Remote process messages appear in the MSG (Display Messages) system command display at the local host, prefixed by the hostname of the remote host, as in the following example. If the controller option SEPARATEMSGS is set, use the MSG NW system command to see these entries.
---Mix-Time--------------------- MESSAGES ------------------------- * ** 19:33 [PARIS] 1057 EOT (JASMITH)OBJECT/REPORTER ON DPMAST. * ** 19:25 [PARIS] 1057 BOT (JASMITH)OBJECT/REPORTER ON DPMAST.
If the remote process was initiated from a CANDE or MARC session, the process messages are also routed back to the CANDE or MARC session. The following is an example of a CANDE command that initiates a remote task and the messages that are returned:
RUN REPORTER ON DPMAST;HOSTNAME=PORTLAND #RUNNING 6881 AT PORTLAND. #[PORTLAND] 6881 BOT (JASMITH)OBJECT/REPORTER ON DPMAST. #ET=1:00.2 PT=0.0 IO=0.2 #[PORTLAND] 6881 EOT (JASMITH)OBJECT/REPORTER ON DPMAST.
The message “#ET=1:00.2 PT=0.0 IO=0.2” is the termination message displayed for the process by CANDE. The elapsed time, processor time, and I/O time displayed in this message summarize the resource usage accumulated by the process on the remote host.
Note that the local termination message for the process appears before the EOT message from the remote host. This occurs because there is a slight delay in the forwarding of messages from the remote host.
