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.

or devices, OpenVMS grants maximum access. This feature does not concern you if you run<strong>Caché</strong> in an application environment, but does apply if you use <strong>Caché</strong> in Programmer mode.Input and Output DevicesOnly one process can own a device at a time. Under OpenVMS it is impossible to close yourprincipal input or output device. This means that a job executing in a JOB Server is unableto perform input or output to your principal I/O devices even though you may close device0.Therefore, if you expect a JOB Server to perform input, you must specify:• An alternative input device for it• The null device for an output device (if you do not want to see the output)Failure to follow these guidelines may cause the job executing in the JOB Server to hang ifit needs to do any input or output from/to your principal I/O devices. You may find that frequentlyjob output does get through to your terminal (for example, if you have the SHAREprivilege), but typically it will not.Troubleshooting Jobs That Won't ExecuteIf your job does not start, check your I/O specification. Your job will not start if <strong>Caché</strong> cannotopen the devices you requested. Note that the null device (NL: on OpenVMS and /dev/nullon UNIX) is always available.If your job starts but then halts immediately, make sure you have sufficient swap space. Yourjob receives an error if you do not have enough swap space.If your job does not start, make sure that you have used the correct namespace in the JOBcommand. You can test whether a namespace is defined by using $ZUTIL(90,10).If the JOB command is still not working, try the following:• Execute the routine with the DO command.• OpenVMS: Jobbed processes all execute the system login file, SYS$MANAGER:SYLO-GIN.COM. Check to make sure it contains no statements that will cause a jobbed processto hang.• OpenVMS: Jobbed processes that do not run in JOB Servers also execute yourLOGIN.COM file. Check this file as well.• Make sure you are not exceeding the number of processes for which you are licensed inOpenVMS or <strong>Caché</strong>.JOB<strong>Caché</strong> <strong>ObjectScript</strong> <strong>Reference</strong> 69

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

Saved successfully!

Ooh no, something went wrong!