home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!cs.utexas.edu!sun-barr!ames!nsisrv!author.gsfc.nasa.gov!rkoehler
- From: rkoehler@author.gsfc.nasa.gov (Bob Koehler)
- Subject: re: Re: Running LOGINOUT [SYS$CLI]
- Message-ID: <8JAN199309141528@author.gsfc.nasa.gov>
- News-Software: VAX/VMS VNEWS 1.4-b1
- Sender: usenet@nsisrv.gsfc.nasa.gov (Usenet)
- Nntp-Posting-Host: author.gsfc.nasa.gov
- Organization: CSC System Sciences Division
- References: <9301071240.AA03083@uu3.psi.com> <1993Jan7.182111.1081@dbased.nuo.dec.com>
- Date: Fri, 8 Jan 1993 14:14:00 GMT
- Lines: 42
-
- In article <1993Jan7.182111.1081@dbased.nuo.dec.com>, lionel@quark.enet.dec.com (Steve Lionel) writes...
- >
- >Regarding the issue of whether or not it is "supported" to run LOGINOUT.EXE
- >to start a process with a CLI, I have a meeting with the writer of the
- >VMS System Services Reference Manual later this afternoon to go over just what
- >needs to be added to the $CREPRC description to make it clear that this IS
- >supported. I note that the $CREPRC description already has a lot more mention
- >of LOGINOUT than does the DCL manual (I hadn't found it because it wasn't
- >listed in the master index under LOGINOUT), in particular it says:
- >
- > "... This is so because SYS$SYSTEM:LOGINOUT.EXE causes a
- > command interpreter to be mapped into the created process..."
- > ("Description" section of $CREPRC documentation)
- >
-
- Pardon me for not responding quickly to all those who asked "where" when I
- claimed this behaviour was documented. And thanks to those who did respond
- with the various places and pieces of documentation which do relate to this
- behaviour.
-
- IMHO, statements in the documentation such as the above are sufficiently strong
- to warrant my claim that the use of LOGINOUT to map a CLI is documented. In
- particular, I beieve that DEC should not alter this behaviour without
- appropriate documentation in the Release Notes, including:
- 1) statement of the change
- 2) provision for, and documentation of, a new technique for
- achieving the same results
- 3) justification for the change (a lot of code would be broken)
-
- This is, in fact, what I expect for any known change to a documented interface
- or behaviour, and I would anticipate from past experience that DEC would go
- beyond the Release Notes in efforts to educate the affected sites.
-
- OBTW, this behaviour of LOGINOUT was also documented in the Release Notes for
- an early version of VMS (pre 3.0, possibly 2.0) when the behaviour of LOGINOUT
- was changed to recognize that it did not need a username and password when
- invoked by $CREPRC or RUN from a process belonging to a user who is already
- logged in (basically, a process other than the job controller).
-
- ------------------------------------------------------------------------------
- Bob Koehler | Any illusion to these opinions being other
- rkoehler@author.gsfc.nasa.gov | than just mine alone is just that.
-