The AT <hostname constant> specification causes a job initiated on one system to be compiled and run on another system.
The WFL compiler at the receiving host system compiles the job; the sending host does not analyze the contents of the job, except for the END JOB construct. If the END JOB construct is missing, an “UNEXPECTED END OF FILE” error message is issued.
The host name specified must be an available host in a BNA or Open Systems Interconnection (OSI) network.
If the host specified is not available, the job compilation is aborted and the error message “UNKNOWN HOST SPECIFIED” is displayed. The CANDE ?HN command or the HOSTNAME (Host Name) system command can be used before the job is started to determine what BNA hosts are available. The CANDE ?AT local host NW OSIGATEWAY command or the NW OSIGATEWAY system command can be used to determine what OSI hosts are available.
A null character within a quoted string causes the transferred job to be incorrectly terminated, which causes erroneous syntax errors at the receiving host. This incorrect termination occurs because the sending host does not analyze the contents of the job; the sending host transfers data to the receiving host only until a null character is reached.
Using the START FOR SYNTAX statement is not allowed for jobs that include an AT <hostname constant> specification. Doing so generates the following syntax error:
START FOR SYNTAX IS ONLY VALID FOR LOCAL HOST
| Note: | A job that includes an AT <hostname constant> specification cannot have a job parameter list unless all the job parameters are optional and are not specified in the START statement. |
Example
The following job will run at the system named SF6B:
?AT SF6B BEGIN JOB ADDIT; . . . ?END JOB.
