Path: utzoo!mnetor!uunet!munnari!vuwcomp!wnv!grv!srghamo
From: srghamo@grv.dsir.govt.nz
Newsgroups: comp.os.vms
Subject: Re: Continuous batch jobs
Message-ID: <247@grv.dsir.govt.nz>
Date: 15 Apr 88 15:02:08 GMT
References: <880405103235.000003D4071@naif.JPL.NASA.GOV>
Lines: 17
Organisation: DSIR, Gracefield, NZ


In article <880405103235.000003D4071@naif.JPL.NASA.GOV>, PJS@NAIF.JPL.NASA.GOV (Peter Scott) writes:
> We have a realtime communication interface setup here that we are
> interfacing a data reduction system to, and the guy doing it says he
> wants to do it via a batch job that never terminates (until the system
> goes down) because detached processes are too much work to set up. 

Actually, what he wants IS a detached job but one that LOOKs like a batch
job. The problem with a continuous batch job is that it requires a queue
to live in and is susceptible to nasty things like STOP/QUEUE/MANAGER.

Create a command procedure, as for a batch job, then, issue the command

	RUN /DETACH ... SYS$SYSTEM:LOGINOUT 
		/INPUT=commandfilename /OUTPUT=logfilename

Andrew Ollivier, Department of Scientific and Industrial Research, New Zealand
SRGHAMO@GRV.DSIR.GOVT.NZ