Previously, I wrote:

...snip...

>As Bill Lancaster pointed out, you do run the risk of moving some
>ldev1-required system files off of ldev1.
>
>To solve this potential problem (more on that later) you could simply
>create an SLT tape and UPDATE from it.
>
>Whether or not a problem is created by moving files off ldev1 is debateable.
>
>I have recently intentionally placed such a file, NMCONFIG.PUB.SYS
>intentionally on ldev 2. A subsequent "start norecovery" worked without
>incident.
>
>I suppose, in that case a "start norecovery single-disk" would be
>problematic - haven't tried it.
>
>In any case, creating a new SLT and updating from it (or simply updating
>from a recent unmodified SLT) should correct any problems associated with
>system files straying off ldev 1.

Re-reading what I wrote, I realize I may have been a bit nonchalant about
the potential problem asscociated with moving certain files off ldev 1.

You can indeed run into problems if some files from the SYS account do
stray off ldev 1 - even with a standard "START" from disk reboot.

However, you can always correct such problems prior to any reboot by simply
performing an UPDATE CONFIG from a current SLT tape.

Also, to restore posix-named files and place on specific devices, simply
use the posix naming syntax.

For example to restore all files from the POSXTEST account onto ldev 2:

:file t;dev=tape
:restore *tape;/POSXTEST/;dev=2;show=offline;olddate;[create]


---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]  Compuserve: 71203,474
---------------------------------------------------------------------------