In some cases, it might be convenient to store a WFL job source program on the local host, even though the job is to be run on a remote host. For these cases, you can include an AT <hostname> specification at the start of the job.

You can submit the WFL job for execution by entering a START command at the local host. If the AT hostname specification in the job requests a hostname that is not currently available, the system rejects the job and displays the message “SPECIFIED HOST NOT REACHABLE.” If the requested hostname is available, the system transfers the job to the remote host. The entry “JOB/HANDLER/<local hostname>“ appears in the mix at the remote host and indicates that a job has been transferred to the remote host. The job compilation, job queuing, and job execution all take place at the remote host.

If the AT <hostname> phrase is used, the job cannot include a job parameter list, any BINARY data specifications, or a null character within a quoted string. In addition, if the WFL source program is stored in a disk file, a question mark must be included before the END JOB statement. If the WFL source program is submitted in array form, it should not include any strings with embedded null characters; otherwise, the job receives a syntax error at the remote host.

The following is an example of the job heading for a job that is to run on a remote host named CHICAGO:

?AT CHICAGO BEGIN JOB REMOTE/RUNNER;