3592 Media Availability

[Mike Crawford]

I've been hearing varying stories from vendors regarding the availability of
3592 media.  Beyond the 20 tapes available through IBM with the installation of
the drive, are these tapes available through resellers now?  I've seen estimates
anywhere from today to March '04.

I'd also be interested in hearing comments from anyone with first-hand
experience using the 3592 in a production environment.  Do they live up to the hype?

Thanks,
Mie

3583 Inventory Command

[Mike Crawford]

Is there any way to report the barcodes of tapes physically in a 3583?
I'm able
to see the barcodes one at a time, using the Remote Management Unit (web
interface), but I'd prefer a comman-line approach.

Using tapeutil (under Solaris) doesn't quite cut it, unless there is
something
I'm not seeing.

The command:
tapeutil -f /dev/rmt/1smc -o inv

reports all the cells, and whether media is present, but not the barcode
label.

Any suggestions?

Thanks,
Mike

Re: Transaction Failed

[Mike Crawford]

Geoff,

I saw the same message last night.  The funny thing is, the node in question
should not have been writing to the first pool listed in the ANRD error.
The two pools are not in the same hierarchy at all.  Does that agree with your
situation?


10/29/02   00:03:11  ANRD bfcreate.c(1906): ThreadId<56> Destination
  switched from KTI_WRK_BKUPDISKPOOL to KTI_DISKPOOL in the
  middle of  a transaction.
10/29/02   00:03:11  ANR0530W Transaction failed for session 3732 for node
   (WinNT) - internal server error detected.

We've only seen this error once since upgrading to TSM 5.1.5.0 on AIX 5.1.

Mike.





Forum:   ADSM.ORG - ADSM / TSM Mailing List Archive
 Date:  Oct 23, 23:25
 From:  Gill, Geoffrey L. <[EMAIL PROTECTED]>

 I just saw this pass by on the screen and thought I'd send it off. This
 morning I upgraded the TSM Server to 5.1.5.1, it's on AIX 4.3.3. Don't
 recall ever seeing this error before so thought I'd ask. It is just a
 standard backup, no TDP going on.

 10/23/02 20:09:43 ANRD bfcreate.c(1906): ThreadId<134> Destination

switched from DIRECTORY_DPOOL to NOTES_DPOOL in the

middle of  a transaction.

 10/23/02 20:09:43 ANR0530W Transaction failed for session 1436 for node

 (WinNT) - internal server error detected.


 Geoff Gill
 TSM Administrator
 NT Systems Support Engineer
 SAIC
 E-Mail: [EMAIL PROTECTED]
 Phone:  (858) 826-4062
 Pager:   (877) 905-7154

Retrieve partial damaged file

[Mike Crawford]

All,

I've encountered a tape with damaged files on it, for which no copypool exists
(business decision).

The question the user has asked me is:  This is a 942 mb file, the retrieve
fails at 940 mb, and deletes the file.  The data type is such that data could be
usable even if the file is truncated.

Is there a way to stop the file from being deleted when the retrieve fails?

Thanks,
Mike

Re: Occupancy comparison script

[Mike Crawford]

Simple:

backup stgpool primarypool copypool preview=yes

Check the activity log, it will show which volumes would need to be
mounted for a backup, if any.

Mike.




Jolliff, Dale wrote:

>I know someone has already invented this wheel...
>
>I need to create a script to compare occupancy of primary sequential pools
>to copypools to verify a complete stgpool backup.
>
>Anyone got one handy that won't bring a server to it's knees?
>

Re: Restoring Data on A Damaged Tape

[Mike Crawford]

Any suggestions for a worst case scenario, where it is a primary pool tape which
has not yet had a backup made?

Had this happen this morning.  Wrote 33GB onto a 3590E.  The tape then became
unreadable, the server error being "I/O error reading label for libvolume 101144
in drive RMT1 (/dev/rmt/6st)."

Has anyone used any data recovery services?  Is it even possible in this sort
of situation?

Thanks,
Mike

>If it is a primary pool tape you just do a RESTORE VOLUME command on the TSM

>Server.  The current tape will get marked destroyed and the data will
>actually go to other tapes in the pool from your copypool.
>
>If it is a copy pool tape, just do a DELETE VOLUME DISCARDDATA=YES.  The
>next time you run a BACKUP STG command to the pool it will recreate the data

>from the primary disk and tape pools involved.
>
>Yes, it is just that simple.
>
>Paul D. Seay, Jr.
>Technical Specialist
>Naptheon, INC
>757-688-8180
>
>
>-Original Message-
>From: Al'shaebani, Bassam [mailto:Bassam.Al'[EMAIL PROTECTED]]
>Sent: Tuesday, May 14, 2002 9:22 AM
>To: [EMAIL PROTECTED]
>Subject: Restoring Data on A Damaged Tape
>
>
>Hello TSM'rs,
>Does anyone know the steps in recovering data on a damaged tape? I believe,

>we can recover the data from our onsite tape pool, i'm
>just not sure of the steps. Can anyone help?
>Thanks,
>-bassam
>

Re: Show Libr output

[Mike Crawford]

Zlatko,

Here's the other info you requested.  We are still running AIX 4.3.1, ADSM
3.1.2.55.  I'm working at upgrading to TSM4.2, then IBM can/will look at
the
problem, if the upgrade itself does not fix the problem.

Thanks,
Mike

$ lsattr -El rmt0
mode   yes  Use Buffered Writes
   True
block_size 0Block Size (0=Variable Length)
   True
compress   yes  Use Hardware Compression on Tape
   True
autoload   no   Use Autoloading Feature at End-of-Tape
   True
loggingno   Activate volume information logging
   True
max_log_size   500  Maximum size of log file (in # of entries)
   True
space_mode SCSI Backward Space/Forward Space Record Mode
   True
rew_immediate  no   Use Immediate Bit in Rewind Commands
   True
trailer_labels no   Trailer Label Processing
   True
retain_reserve no   Retain Reservation
   False
emulate_auto   no   Use Random Mode to Emulate Autoloader Tape Drive
  True
limit_readerp  no   Limit Read Error Recovery Time to 5 Seconds
   True
fail_degraded  no   Fail Tape Operation if Degraded Media is
Detected True
devtype03590E1A Device Type
   False
mtdeviceLibrary Device Number
   True
prime_parent   scsi5Primary SCSI Parent
   False
prime_id   0Primary Target ID
   False
alt_device  Alternate Device Name
   False
alt_parent  Alternate SCSI Parent
   False
alt_id  Alternate Target ID
   False
drive_port 0Drive Port Number
   False

$ lsattr -El rmt2
mode   yes  Use Buffered Writes
   True
block_size 0Block Size (0=Variable Length)
   True
compress   yes  Use Hardware Compression on Tape
   True
autoload   no   Use Autoloading Feature at End-of-Tape
   True
loggingno   Activate volume information logging
   True
max_log_size   500  Maximum size of log file (in # of entries)
   True
space_mode SCSI Backward Space/Forward Space Record Mode
   True
rew_immediate  no   Use Immediate Bit in Rewind Commands
   True
trailer_labels no   Trailer Label Processing
   True
retain_reserve no   Retain Reservation
   False
emulate_auto   no   Use Random Mode to Emulate Autoloader Tape Drive
  True
limit_readerp  no   Limit Read Error Recovery Time to 5 Seconds
   True
fail_degraded  no   Fail Tape Operation if Degraded Media is
Detected True
devtype03590E1A Device Type
   False
mtdeviceLibrary Device Number
   True
prime_parent   scsi2Primary SCSI Parent
   False
prime_id   2Primary Target ID
   False
alt_device  Alternate Device Name
   False
alt_parent  Alternate SCSI Parent
   False
alt_id  Alternate Target ID
   False
drive_port 0Drive Port Number
   False

$ lslpp -L adsm*
   Fileset  Level  State  Description


   adsm.client.aix42.admin   3.1.20.3CADSM Client - Administrative
  Command Line
   adsm.client.aix42.base3.1.20.3CADSM Client - Backup/Archive
   adsm.client.aix42.common  3.1.20.3CADSM Client - Common Files
   adsm.devices.NetTAPE-tlc   3.1.1.0CADSM Device Support for
NetTAPE
   adsm.devices.acsls 3.1.1.0CADSM Device Support for ACS
   adsm.devices.rte   3.1.2.1CADSM Device Support runtime
   adsm.html.en_US.clients.data
  3.1.2.0CADSM Clients Online Library -
  U.S. English
   adsm.html.en_US.server.data
  3.1.2.0CADSM Server Online Library -
  U.S. English
   adsm.license.rte   3.1.1.0CADSM Server License
Registration
   adsm.pdf.en_US.clients.data
  3.1.2.0CADSM Clients Online Library -
  U.S. English
   adsm.pdf.en_US.server.data
  3.1.2.1CADSM Online Library, Server
  Library - U.S. English
   adsm.server.gif3.1.2.1CADSM Server Web Administrator
  Icons
   adsm.server.rte   3.1.2.55CADSM Server Runtime
   adsm.server.util   3.1.2.1CADSM Server Utilities
   adsm.web.client.aix42 3.1.20.3CADSM Client - WebClient

$ lsdev -Cc tape
rmt0 Available 30-60-00-0,0 IBM 3590 Tape Drive and Medium Changer
rmt1 Available 30-60-00-1,0 IBM 3590 Tape Drive and Medium Changer
rmt2 Available 10-78-00-2,0 IBM 3590 Tape Drive and Medium Changer
rmt4 Available 10-60-00-5,0 SCSI 8mm Tape Drive
magstor1 Available  LAN/TTY Library Management Control Point
rmt3 Available 30-68-00-0,0 IB

[Fwd: Rejected posting to ADSM-L@VM.MARIST.EDU]

[Mike Crawford]

Zlatko,

Here's the output you requested.  As you can see, same model and
microcode levels (it's the same across all five drives.

I've done the same Show Libr on our other two servers, one with
3590B1A's, one with 3590E1A's.
The B1A's:
RMT0 (/dev/rmt0):
type=8, mod=17, busy=0 online=1,

The E1A's: (Sun server, others are AIX)
RMT0 (/dev/rmt/3st):
type=8, mod=48, busy=0, online=1,


The problem we are having with the one drive is that some tapes that are
written on it are not mounted on any other drives.  When a session needs
that tape and RMT2 is busy, the session immediately fails, the tape is
not mounted.

We have not removed the device and readded it through AIX, as we feel we
may risk losing the ability to mount these tapes.  But comparing the
output from the Show Libr commands, is it possible that RMT2 is correct
(it is the same as the 3590E1A's on the other server) and the other four
drives are not (they are the same as the 3590B1A's on the other server)?

Thanks,
Mike



$ lscfg -vl rmt0
   DEVICELOCATION  DESCRIPTION

   rmt0  30-60-00-0,0  IBM 3590 Tape Drive and Medium
   Changer

 ManufacturerIBM
 Machine Type and Model..03590E1A
 Serial Number...00026813
 Device Specific.(FW)E35A
 Loadable Microcode LevelA0B00E26

$ lscfg -vl rmt2
   DEVICELOCATION  DESCRIPTION

   rmt2  10-78-00-2,0  IBM 3590 Tape Drive and Medium
   Changer

 ManufacturerIBM
 Machine Type and Model..03590E1A
 Serial Number...00026920
 Device Specific.(FW)E35A
 Loadable Microcode LevelA0B00E26




Zlatko Krastev wrote:

 >what is the output of
 >lscfg -vl rmt0
 >lscfg -vl rmt2
 >
 >Zlatko Krastev
 >IT Consulant
 >
 >
 >
 >
 >Please respond to [EMAIL PROTECTED]
 >Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
 >To: [EMAIL PROTECTED]
 >cc:
 >
 >Subject:Show Libr output
 >
 >In investigating a tape drive problem, I found the output from the Show
 >Libr
 >command to be interesting, specifically the type=8, mod=## fields:
 >
 >RMT2 (/dev/rmt2):
 >  type=8, mod=48, busy=1, online=1,
 >  polled=0, available=1, createPending=0
 >  priorReadFailed=0, priorWriteFailed=0
 >  priorLocateFailed=0, update=0, checking=0,
 >  offline time/date: 00:00:00  1900/00/00
 >  Log sense counters last dismount:
 >349X-specific fields:
 >  devNo=2527744, isScsi=1
 >  last dismounted volume
 >RMT0 (/dev/rmt0):
 >  type=8, mod=17, busy=1, online=1,
 >  polled=0, available=1, createPending=0
 >  priorReadFailed=0, priorWriteFailed=0
 >  priorLocateFailed=0, update=0, checking=0,
 >  offline time/date: 00:00:00  1900/00/00
 >  Log sense counters last dismount:
 >349X-specific fields:
 >  devNo=2523440, isScsi=1
 >  last dismounted volume
 >
 >All five drives are 3590E1A's, four drives show type=8, mod=17, but RMT2
 >shows
 >something different.  This is the drive we are having problems with.
 >
 >Does anyone know what these fields mean, and what values mean what, under
 >AIX
 >4.3.1?
 >
 >Thanks,
 >Mike
 >
 >
 >
 >

Show Libr output

[Mike Crawford]

In investigating a tape drive problem, I found the output from the Show Libr
command to be interesting, specifically the type=8, mod=## fields:

RMT2 (/dev/rmt2):
  type=8, mod=48, busy=1, online=1,
  polled=0, available=1, createPending=0
  priorReadFailed=0, priorWriteFailed=0
  priorLocateFailed=0, update=0, checking=0,
  offline time/date: 00:00:00  1900/00/00
  Log sense counters last dismount:
349X-specific fields:
  devNo=2527744, isScsi=1
  last dismounted volume
RMT0 (/dev/rmt0):
  type=8, mod=17, busy=1, online=1,
  polled=0, available=1, createPending=0
  priorReadFailed=0, priorWriteFailed=0
  priorLocateFailed=0, update=0, checking=0,
  offline time/date: 00:00:00  1900/00/00
  Log sense counters last dismount:
349X-specific fields:
  devNo=2523440, isScsi=1
  last dismounted volume

All five drives are 3590E1A's, four drives show type=8, mod=17, but RMT2 shows
something different.  This is the drive we are having problems with.

Does anyone know what these fields mean, and what values mean what, under AIX
4.3.1?

Thanks,
Mike

Re: Offsite Mirror of TSM server

[Mike Crawford]

Could you not start a second instance of the server on the target server, restore
the db from the source server into this second instance?

Then the server-to-server would still operate, but it would be within the one
machine!

In theory, of course...

M.




>This is such a key point when considering server-to-server!  The short
>answer to this question does not begin to actually tell the story.
>
>Kelly J. Lipp
>Storage Solutions Specialists, Inc.
>PO Box 51313
>Colorado Springs, CO 80949
>[EMAIL PROTECTED] or [EMAIL PROTECTED]
>www.storsol.com or www.storserver.com
>(719)531-5926
>Fax: (240)539-7175
>
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
>Prather, Wanda
>Sent: Thursday, April 18, 2002 11:45 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Offsite Mirror of TSM server
>
>
>I did not intend to imply you can't restore the DB from the target server.

>What I meant is that you cannot restore client files from the target server.

>You have to get the source server up and running again.
>
>It's really no different from any other DR situation.  If you lose your
>primary TSM server, you have to go and get the tapes out of the vault and
>reload the DB before you can do client restores.  With server-to-server,
>your vault is electronic, so you don't have to physically go and get the
>tapes, the data comes over the wire.
>
>But you STILL have to reload the DB of the source server.
>
>
>
>-Original Message-
>From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, April 18, 2002 2:36 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Offsite Mirror of TSM server
>
>
>That is what I guessed from the docs. I was hoping I was wrong !
>
>So, of what value would a DB backup to a "target" server be ?  I could
>never recover from it !!!
>
>Sounds like a partially implemented and of very limited use feature, to me

>!!
>
>Is anybody out there using a "target" server to perform backups of any
>kind ?   If you do, the better question would be, why and how ?
>
>
>
>
>
>"Prather, Wanda" <[EMAIL PROTECTED]>
>Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>04/18/2002 01:03 PM
>Please respond to "ADSM: Dist Stor Manager"
>
>
>To: [EMAIL PROTECTED]
>cc:
>Subject:Re: Offsite Mirror of TSM server
>
>
>My understanding is that when you use source/target server, you think of
>the
>"target" TSM server as just an electronic vault.  It is NOT the same as
>having a backup TSM server.
>
>As you said, the objects in the target server's data base are archive
>objects.  The metadata needed to restore the data is still in the DB of
>the
>SOURCE server.
>
>So you won't be able to do restores, until you build a repair/recovery
>source server and reload its DB.  Now someone else might reasonably expect

>to reload the DB into a TSM server at the offsite location; but since you
>are planning for the target/source TSM's to be on different platforms,
>that
>won't be an option.
>
>You will need to rebuild the TSM server on your OS/390 recovery machine,
>wherever that is.
>
>
>
>-Original Message-
>From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, April 17, 2002 1:46 PM
>To: [EMAIL PROTECTED]
>Subject: Offsite Mirror of TSM server
>
>
>Let me preface this with, I am not sure how to completely ask these
>questions since I don't have all of the details but hopefully someone can
>give me some idea of how TSM can/will handle this, if at all possible.
>
>Current configuration:  TSM 4.1 on OS/390 using 3590B tape drives in a
>3494 ATL
>
>Requirements as I understand them:  Setup a off-location "hot site" backup

>TSM server that will have copies of everything the main server and/or
>other TSM server (we are working on splitting the TSM traffic/load onto
>another TSM server) has.   The "hot site" server will probably be an AIX
>box with 3590E (possibly FC) drives.
>
>I have looked into the source/target server issue but am a little confused

>since the "target" server will only see things that come from the "source"

>server as archive objects.
>
>If the building with the "source" server burns down (and this same
>building also houses a majority of the clients that are backed up !), how
>would the "target" server be used to restore all of the client nodes ?
>
>How about the database backups that are sent to the "target" server ? What

>use are they if you have to have the "source" server to identify what is
>on the "target" server ?
>
>Should I/could I setup database mirror volumes on a remote (target ?)
>server over simple IP connections or is this only possible with DASD using

>XRC processesespecially since the current, main database is on OS390 ?

>If this was moved to an AIX box, how would this be handled ?  NFS ???
>
>As you can tell, any and all guidance is greatly appreciated !!!
>

>
>Zoltan Forray
>Virgini

Re: No Drives Available errors

[Mike Crawford]

A quick look at past activity logs indicates this began the first day of production
after the 3590E drive upgrades.

This had required a newer version of Atape; would this have changed how messages
are passed back to ADSM?

Thanks,
Mike.





>Mike,
>
>I found the same issue.  It can be reproduced on ADSM version 3 and

>4.1.  I do not think it is limited to 3590E drives though.   Tivoli people,

>have you found a solution to this problem yet?
>
>Jeff Bach
>
>> -Original Message-
>> From: Mike Crawford [SMTP:[EMAIL PROTECTED]]
>> Sent: Wednesday, February 06, 2002 12:39 PM
>> To:   [EMAIL PROTECTED]
>> Subject:  No Drives Available errors
>>
>> Good morning,
>>
>> Since we upgraded our 3590B's to 3590E's, whenever all the drives in the

>> library
>> are full, we get these errors, under ADSM 3.1, AIX:
>>
>> 02/06/2002 11:13:43  ANR8447E No drives are currently available in library

>> MAGSTOR1.
>>
>>
>>
>> This causes restore/retrieves to fail, rather than queue, until a drive
>> becomes
>> available.  We are still using the save devclass definitions from before,

>> MOUNTLIMIT=5
>> (we have five drives in the 3494.)
>>
>> Is there some other setting that needs to change?
>>
>> Thanks,
>> Mike
>
>
>**
>This email and any files transmitted with it are confidential
>and intended solely for the individual or entity to
>whom they are addressed.  If you have received this email
>in error destroy it immediately.
>**
>

No Drives Available errors

[Mike Crawford]

Good morning,

Since we upgraded our 3590B's to 3590E's, whenever all the drives in the library
are full, we get these errors, under ADSM 3.1, AIX:

02/06/2002 11:13:43  ANR8447E No drives are currently available in library MAGSTOR1.



This causes restore/retrieves to fail, rather than queue, until a drive becomes
available.  We are still using the save devclass definitions from before, MOUNTLIMIT=5
(we have five drives in the 3494.)

Is there some other setting that needs to change?

Thanks,
Mike

Migration and Copypools

[Mike Crawford]

According to the ADSM Admin Guide:

Migration of files between primary storage pools does not affect copy storage
pool files. Copy storage pool files do not move when primary storage pool files
move.

If I have defined the following (AIX server, ADSM 3.1):
Primary Pool: Arcpool1
Copy Pool:Backuppool1
NextStgpool:  Arcpool2
Copy Pool:Backuppool2

Arcpool1 is backed up to Backuppool1.  Arcpool2 is the next storage pool, and
is backed up to Backuppool2.  If I migrate all the data in Arcpool1 to Arcpool2,
do the files in Backuppool1 expire?  Or do the files get backed up into the
second pool, duplicating the data again?

>From the explanation in the Admin Guide, I would have guessed that the files
in Backuppool1 would remain as is.  But from what I am seeing now, it looks
like I now have two copypools with the same data.

If this is the case, what can I do to eliminate the first Copypool?

Thanks,
Mike

Re: Reading 'J' tapes on 'E' drives

[Mike Crawford]

So far, we've upgraded one drive of three in this library.  While we do our testing,
I've kept this drive separate by defining it to a new library.  Once we're happy
with it, we'll do the other drives, then they all will exist in the same library.


The instructions from the server README file seem clear, there is a section
explaining how to do exactly this.

Mike


IN ORDER TO READ THE VOLUME PREVIOUSLY WRITTEN IN 3590 FORMAT
 ON 3590E DRIVE (THE STORAGE POOL THAT OWNS THE VOLUME POINTS
 TO A DEVCLASS THAT USES 3590E drive):
 - UPDATE ACCESS MODE TO THAT VOLUME TO READONLY
update volume volumename access=readonly;
 - CHECKOUT THE VOLUME FROM THE LOGICAL 3590 LIBRARY
   (THE DEVCLASS' OLD LIBRARY THAT HAD 3590 DRIVES);
 - CHECKIN THE VOLUME TO THE LOGICAL 3590E LIBRARY
   (THE DEVCLASS' NEW LIBRARY THAT CONTAINS 3590E DRIVES).


>did you just upgrade the drives ?
>You don't need to create a new library if you just upgraded existing drives.

>If you have a whole new library and new drives, then yes...
>   and then need to create a new device class because a device class is
>tied to a library...
>but the old and new drives are all 359x device type !
>
>hope this helps...
>I had a whole new/additional physical library when I did my switch...
>
>Dwight
>
>
>-Original Message-
>From: Mike Crawford [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, January 10, 2002 12:02 PM
>To: [EMAIL PROTECTED]
>Subject: Reading 'J' tapes on 'E' drives
>
>
>Ok, maybe I've misread the documentation but, this is causing me some grief.

>
>
>In testing the upgraded 3590E drive, I've followed the instructions for
>creating
>a new library, devclass, drive, and storage pools.  What I'm trying to do is

>move a full J tape from the old library to the newly defined library, and
>read
>it on the E drive.
>
>I am able to 'checkin libvol magstor3e 101008 status=private devtype=3590',

>but when I try to read the tape, ADSM requests it be mounted back in the
>origional
>library.
>
>What gives?  I'm at wit's end (not that far from wit's beginning, really!)

>
>Thanks,
>Mike
>

Reading 'J' tapes on 'E' drives

[Mike Crawford]

Ok, maybe I've misread the documentation but, this is causing me some grief.


In testing the upgraded 3590E drive, I've followed the instructions for creating
a new library, devclass, drive, and storage pools.  What I'm trying to do is
move a full J tape from the old library to the newly defined library, and read
it on the E drive.

I am able to 'checkin libvol magstor3e 101008 status=private devtype=3590',
but when I try to read the tape, ADSM requests it be mounted back in the origional
library.

What gives?  I'm at wit's end (not that far from wit's beginning, really!)

Thanks,
Mike

FILESPACE_NAME vs. HL_NAME

[Mike Crawford]

Good Afternoon,

A client is having trouble locating archived files using dsmc q ar.  The problem
seems to be that the filespace_name and hl_names differ between the files, even
though they were archived from the same place.

Server: AIX, ADSM v3.1
Client: SunOS, ADSM v3.1

An example:
select filespace_name,hl_name,ll_name,archive_date from archives where 
node_name='HUBER'
and ll_name='BS0266'


FILESPACE_NAME: /WORK
   HL_NAME: /DATA/MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:46:30.00

FILESPACE_NAME: /WORK/DATA
   HL_NAME: /MARTINE/
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-12-22 10:41:24.00

FILESPACE_NAME: /WORK/DATA/MARTINE
   HL_NAME: /
   LL_NAME: BS0266
  ARCHIVE_DATE: 2001-11-20 05:38:10.00


Depending on how the client specifies the request, they will get a different
version of the file.

The question is, how does ADSM determine which part of the path is considered
filespace_name, and which is hl_name?

Thanks,
Mike