Didn't mean to cause such excitement - I put one too many
@ signs in the example.

As mentioned in another reply, you had best not mess
with the files in the SYS account unless you
are quite sure what they are for. For the system
to be able to boot in single disc mode (and other reasons)
many files must be contained totally on device 1.

However, many application files end up on the disc
as well, because it is typically configured as device disc.
If these files are just normal user files, they can be moved,
and then you can run VOLUTIL and the CONTIGVOL command
to try and get contiguous disc space for updates, etc.
(this is not really a defragmentation system, but it
sort of serves that purpose. I beleive the command will
even move files from ldev 1 if you use the unrestricted
option of CONTIGVOL, but the manual is not totally clear
on what is really happening.)


If you are in a typical user account, that doesn't much care
where its files are, you could move them with the example,
which has been noted as using an obsolete form of the
command (I go so far back using MPEX in good old MPE V days
that I tend to use obsolete commands.)

-----Original Message-----
From: Chuck Ciesinski [mailto:[log in to unmask]]
Sent: Thursday, October 19, 2000 11:09 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Finding files on LDEV 1


To all:

Donna wrote,
"> ALTFILE @[log in to unmask]@(DEV=1);DEV=2  (move files, that have at least one
>                              extent on dev 1)

this is a 'bad thing'.  some files *have* to live on ldev 1.  i believe the
above altfile -- if actually done -- would result in a serious dent being
put
in the poor system manager's tums bottle 8-|                   - d

I agree, depending on what third party software, i.e. Netbase from Quest,
and a
couple others, the command
should read something like

ALTFILE @[log in to unmask]@[log in to unmask]@[log in to unmask]@[log in to unmask]@.telesup(ONDEVICE(1));DEV=2

Chuck Ciesinski
Hughes Network Systems

My opinions, not my employers......