Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!ames!uhccux!munnari.oz.au!otc!metro!basser!nuts!cc!sysnet
From: SYSNET@cc.nu.oz (David Morrison - Network Manager)
Newsgroups: news.software.anu-news
Subject: Re: QUEUE checking for hourly SKIM
Message-ID: <8470@cc.nu.oz>
Date: 19 Jul 89 14:51:34 GMT
References: <34@mscf.med.upenn.edu> <5673@kuhub.cc.ukans.edu>
Organization: University of Newcastle
Lines: 23

In article <5673@kuhub.cc.ukans.edu>, SLOANE@kuhub.cc.ukans.edu (Bob Sloane) writes:
> There are a couple of different ways you can synchronize these batch jobs. I
> suspect the command you want to use is the SYNCHRONIZE DCL command.  You can
> say "SYNC <job-name>/QUE=<que>" and the job issuing the SYNC command will wait
> until the specified job is finished.  Another possibility is to do use the

The drawback is that the second job just sits on the queue until the other
finishes.  If by chance you end up with several of these jobs running (after 
the machine has been down for several hours), you might find that your batch 
queue is full of jobs waiting for others to finish, and nothing else gets 
processed.

> "SET PROCESS/NAME=HOURLY_SKIM" command near the beginning of the batch file.
> This command will die with a fatal error if there is another user in the same
> group with a process name of HOURLY_SKIM, causing the job to delete.  I have
> used this method occasionally, but I would recommend using the SYNC command
> for what you want to do.

This method gets around the disadvantage above.
-- 
David Morrison, Network Manager, Uni of Newcastle, Australia
Try sysnet@cc.nu.oz.au or sysnet@cc.nu.oz  (mail only)
or (VAX PSI) psi%newcastle.edu.au::sysnet or psi%0505249626002::sysnet