Each side of the optical platter would be considered a volume and
     should be defined separately.  Each side should be internally labled
     with a volser.  Your C62 library should keep track of the inventory
     via barcode.  ADSM will call each side as an individual storage pool
     volume.  This can be a problem if you expect to use both sides of the
     optical CD, but intend to rotate this media to off site storage.



______________________________ Reply Separator _________________________________
Subject: Optical Library Problem
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at INTERNET
Date:    9/16/97 8:04 AM


Hello ADSM Experts,

I am running an IBM C62 optical library with ADSM Server (AIX 2.1/5.13).

The optical platters are rewritable and the capacity is 1.3GB on each side.
I defined several storage pools with 6 and 20 scratch volumes respectively.

Now all volumes of one of the storage pools are in use, but the migration value
in the query stg result is shown to be 50% !!

Storage      Device       Estimated  %Util  %Migr  High   Low  Next
Pool Name    Class Name    Capacity                Mig%  Mig%  Storage
                               (MB)                            Pool
-----------  ----------  ----------  -----  -----  ----  ----  -----------
ODLPOOL2     ODL           99,661.8   45.1   50.0    90    70  TAPEPOOL2
ODLPOOL2     ODL           99,661.8   45.1   50.0    90    70  TAPEPOOL2

Also most of the platters are full, but adsm tries to allocate new scratch
volumes and refuses migration to the next storage pool.

I assume, that either adsm does not use both sides of the platters or something
is wrong with the volume count / or Format definition of the odl device-class.

So my question: is an optical disk

1.: one volume with 2600MB (as I assumed when defining the dev-class and
storage pools) or
2.: two volumes with 1300MB each?

If option 2 is correct, how can I update my definitions?

Now my definitions look like this:

Device-Class:

Device       Device        Storage    Device       Format     Est/Max    Mount
Class        Access           Pool    Type                   Capacity    Limit
Name         Strategy        Count                               (MB)
---------    ----------    -------    ---------    ------    --------    -----
ODL          Sequential          4    OPTICAL      2600MB     2,600.0        2
ODL          Sequential          4    OPTICAL      2600MB     2,600.0        2

Storage pool:

               Storage Pool Name: ODLPOOL2
               Storage Pool Type: Primary
               Device Class Name: ODL
         Estimated Capacity (MB): 99,661.8
                           %Util: 45.1
                           %Migr: 50.0
                       High Mig%: 90
                        Low Mig%: 70
             Migration Processes:
               Next Storage Pool: TAPEPOOL2
          Maximum Size Threshold: 50 M
                          Access: Read/Write
                     Description:
           Cache Migrated Files?:
                      Collocate?: Yes
           Reclamation Threshold: 60
 Maximum Scratch Volumes Allowed: 20
...

Sorry for that much text.

Any hints are appreciated.

Best regards,

Karl Molter





--
     Dr. Karl Molter                  Voice: +49-651-8103-215
     Dr. Karl Molter                  Voice: +49-651-8103-215
     Fachhochschule Trier             Fax:   +49-651-8103-214
     Computing Centre                 Mail:  K.Molter AT fh-trier DOT de
     Schneidershof                    WWW:   http://www.fh-trier.de/~molter
     D - 54293 Trier / Germany
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
 !!-> Please note: Our domain-name trier.fh-rpl.de will time out on 1/1/98 <-!!
 !!-> Please change all addresses to our new domain FH-Trier.de now.       <-!!
 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!