Caché ObjectScript Reference - InterSystems Documentation

JOBProcess parameters are optional. However, a remote job cannot specify the first processparameter (nspace) because this would conflict with the joblocation parameter. Therefore,only the second, third, and fourth process parameters can be specified, and the missing nspaceparameter must be indicated by a colon.joblocationA specification of the location of the job. The enclosing squarebrackets or vertical bars are required.The action Caché takes depends on the job location syntax you are using.joblocation Syntax["namespace"]["dir","sys"]["^sys^dir"]["^^dir"]["dir",""]ResultCaché checks whether this explicit namespace has its defaultdataset on the local system or on a remote system. If the defaultdataset is on the local system, Caché starts the job using theparameters you specify. If the default dataset is on a remotesystem, Caché starts the remote job in the directory of thenamespace's default dataset.Caché converts this location to the implied namespace form["^sys^dir"].The job runs in the specified directory on the specified remotesystem. Caché does not allow any routine parameters or timeoutspecification.The job runs in the specified directory (implied namespace) asa local job on the current system using the parameters youspecify. An implied namespace is a directory path or OpenVMSfile specification preceded by two caret characters: "^^dir".Caché issues a error.Global Mapping with Remote Jobs (Windows)Caché does not provide global mapping for remote jobs, whether or not global mapping hasbeen defined on the requesting system. To avoid the lack of global mapping, use extendedreferences with your global specifications that point to the location of any globals not in thatnamespace. If the namespace you specify in an extended reference is not defined on the systemyou specify, you receive a error. Namespaces and the syntax for extendedglobal references are described in Global Structure in Using Caché Multi-Dimensional Storage.Caché ObjectScript Reference 67