


EMASS_silo_files(8)                           EMASS_silo_files(8)


NNAAMMEE
       dasadmin - EMASS/Grau silo administrative utility
       libstlemass - shared library for communication to
                EMASS/Grau silo

SSYYNNOOPPSSIISS
       ddaassaaddmmiinn command [options] [parameters]
         lliibbssttlleemmaassss..ssoo (Solaris)
         lliibbssttlleemmaassss..ssoo..aa (AIX)
         lliibbssttlleemmaassss..ssll (HPUX)

DDEESSCCRRIIPPTTIIOONN
   ddaassaaddmmiinn
       commands used with dasadmin.  This is not a complete
       listing, but   does include those commands that are of use
       with NetWorker.   For     a  complete  discussion,  please
       see  the  DAS  Installation and       Administration guide
       provided by EMASS or Grau.
            mmoo[[uunntt]] [ --tt _t_y_p_e ] _v_o_l_s_e_r [ _d_r_i_v_e_-_n_a_m_e ]
               mounts the tape with the barcode label  of  _v_o_l_s_e_r
               into  either  the first available drive (if _d_r_i_v_e_-
               _n_a_m_e  is  not  specified)  or   into   the   drive
               specicified  by  _d_r_i_v_e_-_n_a_m_e If the tape is not the
               type defined by DDAASS__MMEEDDIIUUMM or AACCII__MMEEDDIIAA__TTYYPPEE , you
               can  use  the  --tt  _t_y_p_e  option  to  get  the tape
               mounted.  If the type of the tape and the  defined
               type for the drive do not match, the silo will not
               load  the  tape.  Note  that  the  drive  you  are
               attempting  to  use must be allocated for your use
               before you can mount or dismount tapes.  See lliissttdd
               and aallllooccdd below.
            ddiissmm[[oouunntt]] [ --tt _t_y_p_e ] _v_o_l_s_e_r | --dd _d_r_i_v_e_-_n_a_m_e
               dismounts  the  tape  that  is either specified by
               _v_o_l_s_e_r or whatever is in the  drive  specified  by
               _d_r_i_v_e_-_n_a_m_e_.   If  the  tape  or  drive  are  of  a
               different type than your default, use the --tt  _t_y_p_e
               parameter.  As with mount, you must have the drive
               allocated to you to use this command.
            eejj[[eecctt]] [ --cc ] [ --tt _t_y_p_e ] _v_o_l_s_e_r_-_r_a_n_g_e _a_r_e_a_-_n_a_m_e
               ejects one or more tapes to  the  specified  eject
               area.   As with other commands, if the type of the
               tape you  are  ejecting  is  different  from  that
               defined  by  DDAASS__MMEEDDIIUUMMorAACCII__MMEEDDIIAA__TTYYPPEE,  you will
               need the --tt  _t_y_p_e  option.   The  --cc  specifies  a
               'complete'  ejection for the specified volsers.  A
               complete  ejection  removes  the  entry  for  that
               volser   from   the   silo  controller's  internal
               database.  A NON-complete ejection will eject  the
               tape,  but the volser's entry in the database will
               remain, and the volser's  state  will  be  set  to
               'ejected'.   This  is  useful  if  you  anticipate
               replacing the tape into the silo soon.
            iinn[[sseerrtt]] _a_r_e_a_-_n_a_m_e
               Moves  all  tapes  that  are  currently   in   the



NetWorker rt_1998_4Q.BuildA.uMgJuFsetra2l8_,0011997                        1





EMASS_silo_files(8)                           EMASS_silo_files(8)


               specified insert _a_r_e_a_-_n_a_m_e from the insert area to
               the normal storage locations for tapes.
            iinnvveennttoorryy
               Starts a full inventory of  the  silo.   UUSSEE  WWIITTHH
               CCAAUUTTIIOONN!!   An  inventory  of  this sort can take a
               very long time!  An inventory of our silo with 180
               slots takes over 20 minutes.
            vviieeww [ --tt _t_y_p_e ] _v_o_l_s_e_r
               Will  display  the current status of _v_o_l_s_e_r_.  This
               will  show  the  volser,   type,   attribute   and
               coordinate.
            aallll[[ooccdd]] _d_r_i_v_e_-_n_a_m_e UUPP||DDOOWWNN _c_l_i_e_n_t_n_a_m_e
               allocd  is  used to allocate and deallocate drives
               for different clients.  Before you can use a  tape
               drive,  the  drive  must  be aallllooccdd''eedd UUPP for your
               system.  If it is currently  aallllooccdd''eedd  UUPP  for  a
               different  client, if must first be aallllooccdd''eedd DDOOWWNN
               for that client before being aallllooccdd''eedd UUPP for your
               system.  You cannot aallllooccdd DDOOWWNN a drive that has a
               tape in it.  The tape must be dismounted first.
            ll[[iisstt]]dd
               lliissttddorlldd will show the current state of  all  the
               tape  drives defined in the silo.  The information
               presented will include  the  _d_r_i_v_e_-_n_a_m_e_,  the  amu
               drive  (the  location  in the silo), status (UP or
               DOWN), type, client the drive is allocated to, and
               the volser of any loaded tape.
            sshhooww --oopp | --aacc _c_l_i_e_n_t_-_n_a_m_e
               Shows the operational or access parameters for the
               specified _c_l_i_e_n_t_-_n_a_m_e_.  You  must  include  either
               --aacc  if  you wish to see access parameters, or --oopp
               if you wish to see operational parameters for  the
               _c_l_i_e_n_t_-_n_a_m_e_.   Access  parameters  include  volser
               ranges and drive ranges that  the  _c_l_i_e_n_t_-_n_a_m_e  is
               allowed  to  use.   Operational parameters include
               whether  the  _c_l_i_e_n_t_-_n_a_m_e  has  complete   access,
               dismount  priviledges  along  with  the IP address
               entered for _c_l_i_e_n_t_-_n_a_m_e
            lliisstt _c_l_i_e_n_t_-_n_a_m_e
               Lists any outstanding requests that have been made
               by _c_l_i_e_n_t_-_n_a_m_e_.  If there are any, they are shown,
               along with the request number and type.
            ccaann[[cceell]] _r_e_q_u_e_s_t_-_i_d
               Allows  you  to  cancel  an  outstanding  request,
               assuming  that you have the necessary priviledges.
               Use the _r_e_q_u_e_s_t_-_i_d that  was  shown  by  the  lliisstt
               command.
            qqvveerrssiioonn
               This  shows the version of the DAS server that you
               are connected  to  and  the  version  of  the  ACI
               protocol you are using to talk to DAS over.
            qqvvoollssrraannggee _b_e_g_i_n_v_o_l_s_e_r _e_n_d_v_o_l_s_e_r _c_o_u_n_t [ _c_l_i_e_n_t_n_a_m_e ]
               qqvvoollssrraannggee is the way to  obtain  a  list  of  the
               volsers   that   are   available   in   the  silo.



NetWorker rt_1998_4Q.BuildA.uMgJuFsetra2l8_,0011997                        2





EMASS_silo_files(8)                           EMASS_silo_files(8)


               _b_e_g_i_n_v_o_l_s_e_r and _e_n_d_v_o_l_s_e_r are volsers of the  form
               "123456".   To use the first available or the last
               available, you can use "".   _c_o_u_n_t  specifies  the
               maimum number of volsers you wish to see.

EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS
          These environment variables affect the operation of the
          silo, and since  the  processes  that  are  using  them
          include both commands the user will enter and processes
          that are spawned from nnssrrdd,, they need to be  set  in  a
          location  where  they  will  be  in  place when nnssrrdd is
          started.   The  three  DAS_  variables  are   used   by
          lliibbssttlleemmaassss,, while ddaassaaddmmiinn uses AACCII__MMEEDDIIAA__TTYYPPEE instead
          of DDAASS__MMEEDDIIUUMM

          For  Solaris,  the  definitions  should  be  placed  in
          //eettcc//rrcc..22//SS9955nneettwwoorrkkeerr..

          For   AIX,   the   definitions   should  be  placed  in
          //eettcc//rrcc..nnssrr..

          For  HPUX,  the  definitions  should   be   placed   in
          //ssbbiinn//rrcc22..dd//SS990000nneettwwoorrkkeerr..

       DAS_SERVER
          This  is  either  the network name of the IP address of
          the system that is running DAS. For a single silo, this
          will  usually be the silo controller system.  In larger
          installations, there will  probably  be  only  one  DAS
          server for the whole network.  It is case sensitive.

       DAS_CLIENT
          This  is  the network name of the system that NetWorker
          is running on.  It is case-sensitive.

       DAS_MEDIUM
          This variable is used by libstlemass.  It should be the
          same as ACI_MEDIA_TYPE.
          This  is  the  type of tape drive you are connected to.
          If this is not specified, the default value of DLT will
          be used.  Acceptable values are:
               3480,  3590,  OPTICAL_THICK, OPTICAL_THIN, DECDLT,
               DLT, 8MM, 4MM, D2, VHS, CD, TRAVAN and DTF

       ACI_MEDIA_TYPE
          This variable is used by dasadmin.  It  should  be  the
          same as DAS_MEDIUM
          This  is  the  type of tape drive you are connected to.
          If this is not specified, the default value of DLT will
          be  used.   Acceptable  values  are  the  same as those
          listed under DDAASS__MMEEDDIIUUMM..

EEXXAAMMPPLLEESS
       NOTE on ranges:



NetWorker rt_1998_4Q.BuildA.uMgJuFsetra2l8_,0011997                        3





EMASS_silo_files(8)                           EMASS_silo_files(8)


         dasadmin will accept volser ranges  for  some  commands.
         There are three acceptable variations for these ranges:
         single volser: "000635"
         multiple volsers: "000635, 000789, 098732"
         true range: "000610 - 000745"

       NOTE on _a_r_e_a_-_n_a_m_e and _d_r_i_v_e_-_n_a_m_e:
         _a_r_e_a_-_n_a_m_e_s  usually  consist  of  a letter and 2 digits.
         The letter corresponds to whether you are  referring  to
         an  insert  area ("I") or an eject area ("E").  You will
         need  to  get  the  correct  values   from   your   silo
         administrator before using them.
         _d_r_i_v_e_-_n_a_m_e_s  are  essentially free-form labels concocted
         by whomever installed the silo.  They  may  or  may  not
         have any relevance to physical reality, so you will need
         to see the silo admin to get the correct names.  If  the
         silo  admin  is  not  available,  you  can  get the same
         information using ddaassaaddmmiinn  lliissttdd  along  with  ddaassaaddmmiinn
         sshhooww  --oopp  _c_l_i_e_n_t_-_n_a_m_e  followed  by  ddaassaaddmmiinn  sshhooww --aacc
         _c_l_i_e_n_t_-_n_a_m_e commands.

         To setup the environment variables  necessary  for  silo
         operations:
              setenv DAS_SERVER emask
              setenv DAS_CLIENT aurora
              setenv DAS_MEDIUM DLT
              setenv ACI_MEDIA_TYPE DECDLT

         To see a listing of all volsers available in the silo:
              dasadmin qvolsrange "" "" 10000

         To see the current status of the drives in the silo:
              dasadmin listd

         To  change  the  allocation of a drive from client a4 to
         client aurora:
              dasadmin allocd DLT1 DOWN a4
              dasadmin allocd DLT1 UP aurora

SSEEEE AALLSSOO
       nnssrrjjbb(8), jjbb__ccoonnffiigg(8), lliibbssttllssttkk(8), mmiinnii__eell(8), ssssii(8),
       lliibbssttlliibbmm(8)

DDIIAAGGNNOOSSTTIICCSS
            The  only  available  diagnostic information is error
            messages that may be printed out by dasadmin and lib-
            stlemass in the course of normal operations.










NetWorker rt_1998_4Q.BuildA.uMgJuFsetra2l8_,0011997                        4


