HSM is specifically designed NOT to use the nodename parameter because,
unlike backup, the data on the ADSM server is the REAL copy of the data,
and it must remain in-sync with the stub files on the local file system.
If you were to accidentally run a dsmreconcile, while the NODENAME
parameter was incorrect, we could very well expire data which is still
valid on the local file system.  To protect against this, HSM does not
honor the NODENAME parameter, and always uses the true system name.

The interesting thing is that we may need to relax this restriction when
we do HACMP support for HSM.

To answer your second question, the dls command will show the status of a
file.

Matt Anglin
ADSM Development

On Fri, 22 Nov 1996, Henk ten Have wrote:

> Hi all,
>
> after setting up HSM (put some HSM options in dsm.sys and dsm.opt),
> space management is contacting the server with the 'nodename':
>
>  Session X for node ISIS-S315 (AIX) refused - node name not registered.
>
> In dsm.opt I used NODENAME for the backupclient (N315_C):
>
>  Session X started for node N315_C (AIX).
>
> Question: why is HSM not using NODENAME (=N315_C) from dsm.opt?
>
> Second question: how does a user see if a file is migrated?
>
> (running ADSM V2.1.0.9 on a SP2 (AIX 4.1.4.0) using 3494 with 4 3590 units,
>  backup/archive client's 2.1.0.5 on AIX 3.2, AIX 4.1.4, SunOs, Solaris, SGI)
>
> Regards,
>
> Henk ten Have                   SARA, Academic Computing Services Amsterdam
> Systems Programmer              Kruislaan 415
> E-mail: hthta AT sara DOT nl           1098 SJ Amsterdam
> Phone : +31205923000            The Netherlands
>