ADSM-L

Re: VM vs MVS for ADSM Server

1993-11-17 13:45:27
Subject: Re: VM vs MVS for ADSM Server
From: Bill Colwell <adsm-l-post AT DRAPER DOT COM>
Date: Wed, 17 Nov 1993 18:45:27 GMT
In <1993Nov14.193644.3713 AT draper DOT com>, SPGJAF%UCBCMSA.bitnet AT 
yalevm.ycc.yale DOT edu
 (Joseph A. Faracchio {510} 642-7638 {w}) writes:
>Here's one for the list that may prove valuable in the long run.
>I.E.  If you choose VM and need this its there.  I'm not sure about MVS.
>
>In VM the ability to control the ADSM server is available through PROP.
>And there are other commercial products to do this even better like HMF/VM.
>
>I don't think there are 'free' PROPLOG kinds of implementations for MVS
>and I'd bet the commercial ones are a bit more expensive.
>
>Until ADSM is perfect, :-) !  There will be times when extraneous routines
>will need to be implemented and a VM server sure beats any manual operator
>routine.
>
>My list of wants for ADSM that I'm putting in PROP for the time being are:
>
>Tape Twining
>Automatic Exporting for offsite storage
>Summary reports daily of the asst'd pools and whether there reaching full state
>Other reports of what users 'missed' their scheduled backup more than once.
>etc ...
>
>I've heard of PROPLOG things for MVS.  Are they any good?  Do they work?
>
I am not sure what PROPLOG does - my guess is that it captures messages
messages and the performs an action depending on the message.  There are a
number of products like this in MVS.  We use AUTOMATE and it works fine.
For ADSM, when the message ANR5321I is issued (tape full during migration),
a clist is triggered to submit a job to copy the tape -- thus the twining
feature you want.  It also issues periodic queries to get the status of the
storage pools, and collects the results into a file for easy viewing.
Most of the things you want are done here with AUTOMATE.

>cheers .. joe.f.


Bill Colwell
C. S. Draper Lab
Email: BColwell AT draper DOT com
Voice: 617-258-1550
<Prev in Thread] Current Thread [Next in Thread>