info-vax@ucbvax.ARPA (06/19/85)
From: Flint.Wbst@Xerox.ARPA I am looking for a way to have access to a CLI (DCL) so that I can spawn a DCL command from a detached process. I am currently running under VMS 3.7, since use of 4.0 isn't in the immediate future. Unfortunately, I am forced to live with running from the detached process since it is part of a larger system which I don't have the liberty to modify...? I would appreciate any suggestions... ed flint flint.wbst@XEROX.ARPA
info-vax@ucbvax.ARPA (06/19/85)
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 -------
info-vax@ucbvax.ARPA (06/19/85)
From: sasaki@harvard.ARPA (Marty Sasaki) You might try doing a $creprc with sys$system:loginout as the image to run. There was also an undocumented routine (lib$execute_cli, I think) that does what you want. There was a submission on a DECUS symposium tape that does this as well. Unfortunately, I don't remember which tape, but the submission came from MIT. Marty Sasaki (sasaki@harvard)
info-vax@ucbvax.ARPA (07/03/85)
From: hutch@SDCSVAX.ARPA (Jim Hutchison) (ttysb) In article <8291@ucbvax.ARPA> you write: > >I am looking for a way to have access to a CLI (DCL) so that I can >spawn a DCL command from a detached process. I am currently running >under VMS 3.7, since use of 4.0 isn't in the immediate future. >Unfortunately, I am forced to live with running from the detached process >since it is part of a larger system which I don't have the liberty to >modify...? > >I would appreciate any suggestions... > >ed flint > >flint.wbst@XEROX.ARPA Well not that is much help, but the vfork() call to DEC C does make use of a CLI called VFORKCLI which is in SYSEXE generally. This is not of much aid if you don't have a DEC C compiler, but then again you could dig into those FAB's and make a simple one. Or perhaps connect to a pseudo user, but as I remember that hack leaves a rather gapeing security hole. (where are you again... :-) ). /* "When you are dying, a wombat is better than no company at all." Jim Hutchison UUCP: {dcdwest,ucbvax}!sdcsvax!hutch ARPA: hutch@sdcsvax < Ofcourse these statements are only mine, not my employers. > */