ADSM-L

Re: Monitoring ADSM using MVS server

1996-08-01 18:52:03
Subject: Re: Monitoring ADSM using MVS server
From: "Jose A. Hernandez" <Jose_A._Hernandez AT CANDLE DOT COM>
Date: Thu, 1 Aug 1996 14:52:03 PST
     Bob

     We run ADSM's admin in batch mode and issue the following command:

     DSMADMC / -ID=ADMIN -PASSWORD=XXXX -OUT='XXXX.ADSM.OUTPUT' -
     Q EVENT * * BEGIND=TODAY-1 ENDD=TODAY-1 F=D


     We then tcpip transfer this information to all of our admins.










______________________________ Reply Separator _________________________________
Subject: Monitoring ADSM using MVS server
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at INTERNET
Date:    8/1/96 1:36 PM


Bob,
If you are running MVS as the server ADSM does cut SMF records (type 42,
subtype 14) if you have ACCOUNTING set to ON and the collection of this
record type enabled.  I am using Merrill's MXG to decode the records.
 The following data is available:
ADMS*COMMUNICATIONS*PROTOCOL USED
ADMS*NODE*TYPE
ADSM*ACCOUNTING*DATETIMESTAMP
ARCHIVE BYTES*SENT*CLIENT TO SERVER


ARCHIVE*BYTES*RETRIEVED
ARCHIVE*DB OBJECTS*INSERTED DURING SESS
ARCHIVE*DB OBJECTS*RETRIEVED
AUTHENTICATION*METHOD*USED
BACKUP BYTES*SENT*CLIENT TO SERVER
BACKUP*BYTES*RETRIEVED
BACKUP*DB OBJECTS*INSERTED
BACKUP*DB OBJECTS*RETRIEVED
CPU TIME*USED BY*SERVER FOR THIS CLIENT
ADSM CLIENT*NODE NAME
CLIENT*OWNER*NAME
TOTAL BYTES*COMMUNICATED*CLIENT-SERVER
INTERVAL*DURATION
NORMAL*TERMINATION*(1=NORMAL)  <---------------------- should be
useful,have not tried
SMF*RECORD*TIME STAMP
SYSTEM*ID
COMMUNICATIONS*WAIT*TIME
IDLE*WAIT*TIME
MEDIA*WAIT*TIME
ZEE DATE*ZEE OBS*WAS CREATED


Would be happy to share a basic SAS report which I wrote.
Regards,
Wayne Schumack
 ----------
From:  Bob Finnell[SMTP:finnell AT EROLS DOT COM]
Sent:  Thursday, August 01, 1996 2:28 PM
To:  "ADSM: Dist Stor Manager"
Subject:  Monitoring ADSM.

We're being asked to provide a single point monitor
for our ADSM backups. We are rolling ADSM out on a number
of Netware 4.1 servers, NT 3.51 application servers, OS/2
Notes Servers, and a large number of Solaris 2.5 servers.
Does anyone currently use or know of a good product or have
a workable procedure to allow a single operator to monitor
the success/failure and status of backups cross platform???
We'd prefer not to write/maintain a home grown product.

//----------------------------------------------------------
// Bob Finnell  finnell AT erols DOT com
// Rockville, MD
<Prev in Thread] Current Thread [Next in Thread>