Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: CLIs and detached processes
Message-ID: <8293@ucbvax.ARPA>
Date: Tue, 18-Jun-85 21:18:09 EDT
Article-I.D.: ucbvax.8293
Posted: Tue Jun 18 21:18:09 1985
Date-Received: Thu, 20-Jun-85 20:16:02 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 28

From: Richard Garland <OC.GARLAND@CU20B.ARPA>

To run a detached process under DCL, you run the LOGINOUT image with
a command file as input.  Th command file runs your program.

Thus instead of saying

	RUN FOO/INPUT=.../OUTPUT=.../ERROR=.../UIC=.../PROC=... etc.

You say

	RUN SYS$SYSTEM:LOGINOUT/INPUT=DRA1:[MYDIR]FOO.COM/OUTPUT=... etc

where FOO.COM is something like

	$ SET DEFAULT DISK:[DIRECTORY]
	$ RUN FOO

FOO can then do a LIB$SPAWN.  In version 3.x I'm not sure you can do
a DCL SPAWN but you should try.  Since this whole thing looks like a batch
job, why not run a batch job instead of a detached process?

I have run LOGINOUT in similar cases so I could use the DCL call-back stuff
such as CLI$DCL_PARSE and the like which you can't do by just running
a program detached.  I have not done it with a LIB$SPAWN or DCL SPAWN and
I'm not sure what I could use that for.
					Rg
-------