ADSM-L

FW: Information

1996-02-07 07:43:00
Subject: FW: Information
From: "PITTSON, TIMOTHY" <PITTSON1 AT BWMAIL1.HCC DOT COM>
Date: Wed, 7 Feb 1996 07:43:00 EST
For ADSM V2.1 on MVS, there's a facility that allows you to deal with a
situation like this by extending the log at ADSM startup to allow the server
to come up......

//SERVER EXEC GM=DSMSERV,PARM='/EXTEND LOG <volname> <mb>'

Is this facility also available on AIX ???

Tim Pittson
pittson1 AT bwmail1.hcc DOT com
 ----------
From: owner-adsm-l
To: Multiple recipients of list ADSM-L
Subject: Information
Date: Wednesday, February 07, 1996 11:24AM

We are using ADSM 2.1.0.2 on a RS/6000
580 server with serial disks for the
database, recovery log, and storage
pools migrating the data to an escon
attached 3495 tape robot which is
shared with three mainframes.
We are using the 'DBBACKUPTRIGGER' to
perform an incremental backup
when the recovery log reaches 70%
utilisation, but occasionaly when the
mainframes are IPL'd they 'steal' the
tape drives assigned to our adsm
server
and the server is unable to perform
it's backup to tape and the recovery
log
keeps filling up until it is full and
the server is rendered useless. At
this point
we have to perform a point in time
recovery to restore the database and
lose
some of the db updates, prior to the
log being full because, adsm is not
sensible
enough to restore the database to a
point just prior to the log becoming
full, it
deems it necessary to restore the
database and roll forward the log
updates until
it is full and halts !!
We are in the process of creating a
daemon to run on the rs/6000 to
monitor the
the log utilisation and if necessary
halt the server normally before the
recovery log
becomes full,  and invoke automation
procedures to page support to fix the
problem
manually and restart the server,
without the need to perform any
restores.
This is fairly clumsy and it would be
nicer if the adsm server had similar
code to
DFHSM on the mainframe, where if its
log fills, it will hold all functions
and wait for
the log to be cleared before allowing
any further transactions to take
place. If anyone has any comments or
suggestions about this predicament I
would be
pleased to here them.

Phil Reynolds.
NWW Ltd.
England.
<Prev in Thread] Current Thread [Next in Thread>
  • Information, Phil Reynolds
    • FW: Information, PITTSON, TIMOTHY <=