11.07.2015 Views

Caché ObjectScript Reference - InterSystems Documentation

Caché ObjectScript Reference - InterSystems Documentation

Caché ObjectScript Reference - InterSystems Documentation

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Caché</strong> <strong>ObjectScript</strong> CommandsRemote Job Success ConfirmationYou do not receive a direct message on the requesting system indicating whether job initiationwas successful on the target system. However, <strong>Caché</strong> does write a message indicating jobinitiation success or failure on the console log of the target system.Configuration File on Remote SystemsYou must configure the ability to receive remote job requests on any system that will receivethem.On the receiving system, go to the System Management Portal, select System Configuration,select Advanced Settings, on the pull-down Category list select Connectivity. Select NetworkRemoteJobs.When “true” , incoming remote job requests via DCP or ECP will behonored on this server. The default is “true” .The license on the remote system must support enough users to run remotely initiated jobs.Using the $ZCHILD and $ZPARENT Special Variables$ZPARENT contains the PID (process ID) of the process which jobbed the current process,or 0 if the current process was not created through the JOB command.$ZCHILD contains the PID of the last process created by the JOB command, whether or notthe attempt was successful.Using JOB ServersJOB Servers are <strong>Caché</strong> processes that wait to process job requests. Jobbed processes thatattach to JOB Servers avoid the added overhead of having to create a new process. Whenevera user issues a JOB command with the switch parameter set to use JOB Server if available,<strong>Caché</strong> checks to see if any JOB Servers are available to handle it. If not, it will create a process.If there is a free JOB Server, the job attaches to that JOB Server.When a job halts while running in a JOB Server, the JOB Server hibernates until it receivesanother job request. A jobbed process not running in a JOB Server exits and the process isdeleted.There are some unavoidable differences between the JOB Server environment and the jobbedprocess environment, which may be a security concern with jobbed processes executing inJOB Servers. A jobbed process normally takes on the security attributes of the process thatissued the JOB command at both the <strong>Caché</strong> and the OpenVMS level.However, a jobbed process that runs in a JOB Server uses the UIC of the JOB Server at theOpenVMS level. The UIC of a JOB Server is the same as the UIC of the <strong>Caché</strong> systemmanager, usually [1,4]. This means that when the JOB Server accesses OpenVMS RMS files68 <strong>Caché</strong> <strong>ObjectScript</strong> <strong>Reference</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!