Lars Appel wrote:
> Well, the following worked ok for what I tried...
>
> !job lars,mgr.telesup
> !xeq fscheck.mpexl.telesup "de stmxl.diag.sys"
> !eoj
ok. guess it's just my memory, then :-)
> However, this will probably not be useful to parse out the results.
uh....can you say 'bloomin pain in the seating area'? :-)
> Well, I might be wrong, but in the case of SYSSTART, I somehow
> would not feel too worried to see it somewhere else than on LDEV 1.
> It is used pretty late in the system startup procedure, way after
> the mounting of volumes takes place. So I don't believe it must live
> on LDEV 1 at all.
that got me to wondering if 'sysstart on ldev 1' was an urban ledgend or
not. please check this posting from steve hammond:
<http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind9910B&L=hp3000-l&P=R6391>
he says -- the documentation says it's got to be on ldev 1.....type type
type...and sure enough:
=============
The SYSSTART file must be created by MANAGER.SYS and needs to reside on LDEV
1 to function properly. Once the file is created, use the following commands
to copy the file to the appropriate location:
HELLO MANAGER.SYS
FILE SYSSTART;DEV=1
FCOPY FROM=tempfilename;TO=*SYSSTART;NEW
If an error exists in the SYSSTART file, the startup process ignores it and
continues execution.
===============
i'm curious about the effects of the above file equation and the fcopy. it
doesn't look to me like sysstart (created as suggested above) would
necessarily reside entirely on ldev 1. (and i won't comment lack of
security in the above example....) - d
--
Donna Garverick Sr. System Programmer
925-210-6631 [log in to unmask]
Come, my friends, 'Tis not too late to seek a newer world.
Tho' much is taken, much abides; and tho'
We are not now that strength which in old days
Moved earth and heaven, that which we are, we are.
"Ulysses", A. Tennyson
>>>MY opinions, not Longs Drug Stores'<<<
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
