WFL jobs can be constructed to take advantage of distributed systems services between systems in several ways. For more information about how to use distributed systems services, refer to the Distributed Systems Services Operations Guide and the TCP/IP Distributed Systems Services Operations Guide.
If a terminal is attached to CANDE, then the names of available BNA hosts can be displayed using the CANDE ?HN command. The terminal can be transferred to another of the listed BNA hosts by entering the command:
CONNECT TO <host specification>
When the connection is complete, you can log on under a usercode recognized by the remote host. While the terminal is connected to the remote host, any commands you enter are directed to the remote host and executed there. The CANDE WFL and START commands can thus be used to run jobs on the remote host. The connection is terminated when you end the session with a BYE command.
Even if a terminal is not connected to a remote host, a job initiated at that terminal can be directed to run at a remote host by beginning the job with the AT <hostname constant>.
| Note: | A job including AT <hostname constant> cannot contain a job parameter list. Also, the <i> construct before the END JOB construct is required. |
Any messages generated by the job are still routed back to the original terminal, but are preceded by the name of the system the job is running on.
Examples
The following is an example of a job with an AT <hostname constant> specification. This job is stored in a file on the user's own system. However, when the job is initiated, it will run on the system named LA15D. The job will also look on LA15D for the object code files of the tasks that it runs.
?AT LA15D BEGIN JOB RUNNIT; RUN (WALLY)OBJECT/MAKEIT ON SHIPPK; RUN (ODCON)SNOBOL/REPL ON ORDSPK; ?END JOB.
Tasks can be made to run on different systems than the parent job by specifying the HOSTNAME attribute after the task initiation statement. The object code files for the tasks are also searched for on the system specified by the HOSTNAME attribute. Messages generated by the tasks are still routed back to the original terminal, but are preceded by the name of the system the job is running on.
?BEGIN JOB RUNNIT;
RUN (WALLY)OBJECT/MAKEIT ON SHIPPK;
HOSTNAME=SF15B;
RUN (ODCON)SNOBOL/REPL ON ORDSPK;
HOSTNAME=SD9A;
?END JOB. This job runs on the user's own system. However, it initiates tasks that run on systems SF15B and SD9A, respectively. The job looks for the object code files for those tasks on the systems that the tasks are run on.
Files can be copied between MCP hosts, BNA hosts, and hosts connected to a TCP/IP network by using the WFL COPY statement, which can reference sources or destinations on remote hosts. For example:
?BEGIN JOB COPYDATA; COPY *SYSTEM/CRUNCHER AS (WALLY)CRUNCHER/TUESDAY FROM ODDPACK (KIND=DISK,HOSTNAME=SF15B) TO MODPACK (KIND=DISK,HOSTNAME=LA15D); ?END JOB.
This example copies a file from the system named SF15B to the system named LA15D. The two hosts are BNA hosts and the file is transferred using Host Services file transfer which is part of the distributed systems services.
