ADSM-L

Re: ADSM - Assessing the ADSM DB

1998-05-27 10:04:38
Subject: Re: ADSM - Assessing the ADSM DB
From: Christo Heuer <christoh AT ABSA.CO DOT ZA>
Date: Wed, 27 May 1998 16:04:38 +0200
Hi Mark,

You don't have to use IDCAMS utilities to ensure that you have a backup of
the database. You can just use the ADSM backup db command to copy all
the records either to a tape or to a device class of file while the server
Started task is up and running. The mirror of your database is something
you don't have to worry about - let the ADSM code take care of having the
database mirror in sync - it only uses this databases mirror for contineous
availability - like in the case where you have a drive die which happens to
contain the Primary database - you will not have to restore your database
but carry on running.

Hope this has answered your question.

Regards
Christo Heuer
ABSA Bank
Johannesburg
South Africa


>Environment : ADSM Server 2.1.0.18  - O/S 390 1.3.0 (Plan to go to ADSM V3)
>                     Clients - many of the flavors
>
>
>Hi fellow ADSMers,
>
>With all these questions about the ADSM DB I began to wonder.............
>
>1) When you backup the DB, is the "primary" DB backed-up, the "mirrored"
>     DB backed-up or BOTH? If I issue the following:
>
>     BACKUP DB TYPE=FULL DEV=DBBUCARTRIDGE
>
>     what do I back-up?
>
>
>2) Our database is mirrored (syncronized) with log recovery normal,
>    the ADSM STC has enqueued the DB, therefore standard VSAM
>    utility operations (IDCAMS PRINT) can't be used against the DB.
>    The DB is VSAM linear so LISTCAT should show zero for REC-TOTAL.
>
>    Aside from shutting down the STC to run IDCAMS, whats the best
>    way to ensure DB records exist in the SYNCRONIZED (mirrored-copy)
>    of the DB? (Just because the GUI says its synch'd doesn't satisfy moi!)
>
>
>Mark Owens
>Prodigy Communications Corporation
<Prev in Thread] Current Thread [Next in Thread>