Thomas,

     I'm afraid I have to agree with your co-worker.  Let ADSM handle its
own work with TMS, and leave the REXX code out of it.

     We have an MVS server (3.1.2.20) and use CA-1 TLMS, but I'm sure it
works very similar to TMS.  I would continue with the TMS vault definitions
for ADSM by data set name.  Then allow ADSM, through administrative
commands, to perform the following:

          1. Incremental backup to a storage pool designated for data to be
moved offsite.
          2. Copy of data from above storage pool to a 'vault' storage
pool.
          3. "Outcoding" of the volumes in the 'vault' storage pool (i.e.
defining them as 'offsite').*
          4. Reclamation of tape from both the onsite and offsite storage
pools.

     * NOTE:  It is imperative that the outcoding is performed PRIOR to
your process for ejecting or pulling of tapes for offsite shipment.  If
this is done, you should not have a situation wherein the tape is offsite
and ADSM thinks it is onsite.

                              Ginny
---------------------- Forwarded by Virginia L Hysock/GIS/CSC on 07/20/99
08:46 AM ---------------------------
08:46 AM ---------------------------

       (Embedded image moved to file: PIC02149.PCX)


Virginia L Hysock/GIS/CSC
07/20/99 08:35 AM

To:   Virginia L Hysock/GIS/CSC@CSC
cc:
Subject:

From:    Thomas Denier <Thomas.Denier AT MAIL.TJU DOT EDU>
Subject: ADSM and CA-1 Vault Management System
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit



My site has an ADSM server running on an MVS system with the CA-1 TMS (Tape
Management System). The TMS recognizes ADSM offsite tapes by the dataset
names
used on the tapes and sends such tapes to a vault. This happens twice each
morning. ADSM marks tapes offsite at the end of its daily cycle of
inventory
expiration, storage pool backup, and database backup. There is no interlock
between the TMS and ADSM processes for handling offsite tapes. We have
occasionally had failures when ADSM thought a tape was onsite and TMS had
just
sent it offsite.
If I am reading the CA-1 documentation correctly, we could eliminate the
Vault
Pattern Dataset entries currently used to identify ADSM offsite tapes and
have
the ADSM batch jobs flag tapes as candidates for vaulting by updating the
OUTCODE and OUTDATE fields for the tapes involved. This would be done by
having a Rexx script generate control records for the TMSUPDTE utility. One
of
my co-workers insists that this will not work, and suggests a more complex
set
of scheduling constraints on the ADSM and CA-1 batch jobs as a means of
avoiding problems. Has anyone successfully carried out the sort of scheme
outlined above? Does anyone know of a better approach to maintaing
coordination between ADSM and CA-1 regarding the movement of offsite tapes?