Subject: | |
From: | |
Reply To: | |
Date: | Tue, 30 Sep 1997 09:48:33 +1200 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
This is a very timely discussion, I am just doing some long overdue
housekeeping, and after consulting Eugene's words of wisdom from
ebook.vecsl, I added (device='DISC') to my %altfiles. However it seems that
this is unnecessary, 'cos attempting to move a file off ldev1 with
device='$SYSTEM_MASTER' give the following error ...
-----Altering TT44.PUB.SYS
Error: Can't move system bootfile off DEV=$SYSTEM_MASTER.
Tony Knowles [log in to unmask]
[log in to unmask]
----------
> From: Paul Taffel <[log in to unmask]>
> To: [log in to unmask]
> Subject: MPEX %ALTFILE and LDEV 1
> Date: Tuesday, 30 September 1997 07:18
>
> > Original Question - Why does the operating system allow me to move
files off
> > of LDEV1 that are needed to boot and start the system?
>
> -----------
>
> Before y'all rush to judgment and blame MPEX for allowing
PERFLOG.MPEXL.SYS
> to be moved off of LDEV 1, please note the following:
>
> 1) MPEX %ALTFILE will *NOT* allow you to move files off LDEV 1, if
their
> volume restrictions (as reported by MPEX's %LISTF,-3) contains the
string
> $SYSTEM_MASTER. This volume restriction is also visible using the
CI's
> :LISTF,-1 command. MPEX has enforced this restriction for at least
the
> last four years.
>
> 2) On my system, PERFLOG.MPEXL.SYS is *NOT* restricted to LDEV 1.
Likewise
> for the files [log in to unmask]
>
> So, the question is: why does START require these files to be located
on
> LDEV 1, if the file labels don't contain this restriction?
>
>
> Paul Taffel
> Quest Software
|
|
|