iraf.net

Hello again Steve - The command you used for submitting imheader to the fast batch queue
was exactly right - it should have worked. Are the batch queues defined
properly for IRAF in the hlib$irafuser.com file? These definitions should
have been made at installation time. I tried some tests on Draco this
morning and verified that batch jobs do show up in the 'jobs' output, as do
background jobs. When I submitted imheader to our fast queue, it
processed so quickly I could never catch it with the "show que/all" command.
I had to put it in the slow queue to see it processing. But, in each
case the batch job left a log file in my login directory. Did you
get any log files? If not, then the job didn't execute as a batch job
and you should have seen an error when the job submit failed. So, check out the definition of the IRAF queues in irafuser.com. Then
make sure you were looking in the proper VMS queue for the job; you
could also do a "show sys" and see the batch job running as a detached process.
Submit the job to the slow queue to increase the chances of your seeing it. The way in which IRAF submits a batch job is very OS dependant, and
so isn't written up in any general IRAF documentation. The code is
in iraf$vms/os; queue.c is the procedure that actually calls sys$sndjbcw.
If you continue to have a problem, we can delve into this more deeply.Suzanne Jacoby
sjacoby@noao.arizona.edu
5356::sjacoby or draco::sjacoby
602-325-9364