Erik Vistica wrote:

> Do you have just the STARTUP module?

yes

> It sounds like the STARTSESS command is not being seen (as
> though it is not in the STARTUP module nor the COOLSTART module, but
> rather in some other specific module) and the default logon for
> OPERATOR.SYS is being done instead.

no, it's being seen.  on the console, you'll easily see
LOGON FOR: "CONSOLE,OPERATOR.SYS...."

"Johnson, Tracy" wrote:

> I'm under the impression that starting the computer
> by default automatically invokes a logon at the console,

this is true.  a sysstart file with no startsess for operator.sys will try
to log operator.sys by default if it hasn't been overridden with 'logon='
(ie, start norecovery logon=yomama,operator.sys)

> therefore, a STARTSESS command in SYSSTART seems to be
> redundant, and probably won't work because the default
> logon is already at OPERATOR.SYS the console to begin with,
> and hence, has already logged on.

it may seem redundant, but i'd guess a fair number (a majority?) of shops
use startsess to get the operator logon on.  additionally, in the sysstart
file (on the startsess line) i include 'console,operator.sys' because we
enforce session names.

so since i could do some experimenting, i did the following:
1 - removed the startsess line from the sysstart file, took the system down
and did a start norecovery.  as expected, the system tried to log
'operator.sys' on.  since no password was (nor could it have been) supplied,
the system prompted for the password.  i typed it in.  the operator logged
on and was immediately logged off because so session name was given.  i
expected this to happen.

2 - did as erik suggested, and moved the startsess line into the coolstart
section of the sysstart file (which really makes no difference, but...).
the startsess line contained 'console,operator.sys' but *no* embedded
password.  blah blah blah, the system prompted for a password.  i typed it
in.  the operator logged on and was immediately logged off because so
session name was given.  here's the text from the console...

=====================================================
              COOLSTART startup block processing
=====================================================

STARTSESS 20;CONSOLE,OPERATOR.SYS;NOWAIT;HIPRI
13:47/1/INVALID PASSWORD FOR "CONSOLE,OPERATOR.SYS," ....
(see 'console' is clearly present and it's being sent to the system via
startsess)
<<snippage>>
13:47/#S1/49/LOGON FOR: "OPERATOR.SYS,SYSOPER" ON LDEV #20.

3 - ok fine!  change the sysstart file again to include the password on the
startsess line.  blah blah blah.  here's the text from the console....

==============================================================
              COOLSTART startup block processing
==============================================================

STARTSESS 20;CONSOLE,OPERATOR/.SYS/;NOWAIT;HIPRI
<<snippage>>
13:56/#S1/49/(PROGRAMMATIC) LOGON FOR: "CONSOLE,OPERATOR.SYS,SYSOPER"

friggin' fraggin' -- to me this is clearly a bug.  the absence of the
password makes the startsess command fail.  and since sysstart lives in
.pub.sys, that means the whole freakin' world can look at the file and see
how to logon as operator.sys.

so...is anyone altsec'ing their sysstart file?            - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<