topic Re: Who is accounted for login ? in Operating System - OpenVMS

Who is accounted for login ?

Wim Van den Wyngaert — Mon, 17 Mar 2008 15:03:30 GMT

spa logout/full
-> no DIO
show proc/acc
-> only 4 DIO's done for the spawn.

This while my login.com contains 10.000 lines
and @login.com consumes 86 DIO's.

I didnt find any process on the system that increased DIO count either.

Free lunch ?

Wim

Re: Who is accounted for login ?

Hein van den Heuvel — Mon, 17 Mar 2008 15:48:53 GMT

login.com is NOT executed for a spawn.

Your (logical name) environment is 'transferred' through mailbox IOs.

>> Free lunch ?

Ayup, as long as you just take water.

Hein.

Re: Who is accounted for login ?

Hoff — Mon, 17 Mar 2008 16:10:03 GMT

Loginout typically only runs once per job tree.

This implementation is also the basis for the NOCLI error triggered in some contexts, and some of the related baggage.

http://64.223.189.234/node/794

Re: Who is accounted for login ?

Jess Goodman — Mon, 17 Mar 2008 16:56:37 GMT

Well actually the SPAWN command and LIB$SPAWN do execute LOGINOUT.EXE, but Hein is correct that SPAWN will not execute a LOGIN.COM unless told to do so with either @LOGIN as the SPAWN command line parameter or with /INPUT=LOGIN.COM.

The HELP SPAWN subtopics /SYMBOLS, /KEYPAD, and /LOGICAL_NAMES state that the current set of DCL symbols, logical names, and key definitions are "copied to the suprocess" by default. As this is done via mailboxes it gets counted as buffered I/Os. You can see this by comparing:
$ SPAWN LOGOUT/FULL
with
$ SPAWN /NOSYMBOL/NOLOGICAL/NOKEY LOGOUT/FULL

Re: Who is accounted for login ?

Robert Gezelter — Mon, 17 Mar 2008 17:53:46 GMT

Wim,

Concur. While logical names and other things are copied, it is clear that changes to the command tables are not included in this list.

- Bob Gezelter, http://www.rlgsc.com

Re: Who is accounted for login ?

Wim Van den Wyngaert — Tue, 18 Mar 2008 06:10:36 GMT

Shame on me. Too long ago I used it.

Wim