HP3000-L Archives

November 1998, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Fri, 6 Nov 1998 13:43:20 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
Hi,

> ok, It's clear to me now.... It has to be on ldev 1 except it doesn't.  Got
> it?

You got it! :)

> As a note to one of the original problems, we do the headoff , limits,
> jobsecurity etc. stuff in SYSSTART, as well as any other mundane "MASTER
> OPERATOR ONLY" commands, as by definition, at startup on a standalone
> system, the startup process IS the master operator as the initial boot
> is usually done at the system console (ldev20) unless of course you put
> a console 999 command in SYSSTART, which I would not personally recommend.

Me either...we don't have an ldev 999 :)

BTW, our SYSSTART file ends with:  STREAM STARTUP.JOB.SYS
...which is where we put most of our other startup stuff.


> Just for the record, our sysstart file is also on ldev1.

Historical note: it was actually possible, IIRC, to configure an MPE V
machine such that ldev 1 didn't exist, and the boot disk was ldev 2.
It sure fouled up programs that assumed ldev 1 should exist, or that
LUN 1 = LDEV 1.   (LUN = Logical Unit Number, sort of a counter of
disk ldevs.  You might have ldevs 1, 3, and 5, with LUNs 1, 2, 3)

I haven't tried this with MPE/iX.


SS

ATOM RSS1 RSS2