Remote Jobs
Before starting a remote job, you must establish an ECP connection and set the netjob parameter to true. This enables the server to handle job requests from remote ECP client systems.
You must configure the ability to receive remote job requests on any system that will receive them.
On the receiving system, go to the Management Portal, select System Administration, Configuration, Additional Settings, Advanced Memory. Locate netjob to view and edit. When “true”, incoming remote job requests via ECP will be honored on this server. The default is “true”.
The license on the remote system must support enough users to run remotely initiated jobs. You can determine the number of available InterSystems IRIS licenses using class methods of the %SYSTEM.LicenseOpens in a new tab class, as described in the InterSystems Class Reference.
JOB Syntax for Remote Job Request
You can send a remote job from one InterSystems IRIS system to another using the following syntax:
JOB routine[joblocation]
JOB routine|joblocation|
The two forms are equivalent; you can use either square brackets or vertical bars to enclose the joblocation parameter. A remote job cannot pass routine parameters, process parameters, or a timeout.
The action InterSystems IRIS takes depends on the job location syntax you are using.
| joblocation Syntax |
Result |
| ["namespace"] |
InterSystems IRIS checks whether this explicit namespace has its default dataset on the local system or on a remote system. If the default dataset is on the local system, the system starts the job using the parameters you specify. If the default dataset is on a remote system, the system starts the remote job in the directory of the namespace’s default dataset. |
| ["dir","sys"] |
InterSystems IRIS converts this location to the implied namespace form ["^sys^dir"]. |
| ["^sys^dir"] |
The job runs in the specified directory on the specified remote system. InterSystems IRIS does not allow any routine parameters, process parameters, or timeout specification. |
| ["^^dir"] |
The job runs in the specified directory (implied namespace) as a local job on the current system using the parameters you specify. An implied namespace is a directory path preceded by two caret characters: "^^dir". |
| ["dir",""] |
InterSystems IRIS issues a <COMMAND> error. |
Global Mapping with Remote Jobs (Windows)
InterSystems IRIS does not provide global mapping for remote jobs, whether or not global mapping has been defined on the requesting system. To avoid the lack of global mapping, use extended references with your global specifications that point to the location of any globals not in that namespace. If the namespace you specify in an extended reference is not defined on the system you specify, you receive a <NAMESPACE> error. Namespaces and the syntax for extended global references are described in Formal Rules about Globals.
