The disaster recovery feature automates the creation of Job JCL and control cards to recover DB2 resources. Without the user's assistance, the tool will create the Utility Job JCL, RBAs/LRSNs and control cards to:
1. Recover BSDS from latest Archive tape
2. Register the latest archive log in BSDS
3. Delete/Newlog entries for Active Logs in bsds
4. Delete/Newlog entries for Archive Logs to replace copied archives in BSDS
5. STARTRBA for the DSN1LOGP utility
6. CRCR Crestart ENDRBA/ENDLRSN for disaster recovery restart in BSDS
7. Recovery Cat/Dir Tablespaces (Forward,TORBA) with/without LOGONLY is automated
8. Recover User Tablespaces (Forward,TOCOPY,TORBA) with/without LOGONLY is automated.
9. Recover SAP Tablespace or any Tablespace Groups in Multiple Databases (Forward) and (TORBA) using Archive Log Mode(Quiesce) RBA System Wide consistency.

BSDS, Active Logs, Cat/Dir, User Tablespaces, and all DB2 resources recoveries are simplified and automated off-site as well as on-site.

Disaster Recovery Archive Log Copy Recording:
This feature enables users to automatically record archive log copy input and output data. At the DR site, the Delete/Newlog control cards, with the new archive dsnames and correct RBAs/LRSNs is automated to replace the BSDS information. Archive log copy tape to disk is also automated for faster tablespace recoveries.

Local and Off-site Disaster Recovery:
Complete or partial disaster recovery testing is available at the local site with the GENDB2 software. The user can execute a partial disaster recovery test using a DR set of BSDS data sets. This gives the customer an opportunity to verify the GENDB2 generated Jobs JCL, RBA numbers, and control cards necessary to bring up the DB2 Subsystem at the DR Site. The customer may also generate the Jobs to recover the Cat/Dir and User Tablespaces in this test, which allows the customer to verify the generation and pre-allocation of Image Copy files to minimize the tape mounts for stacked IC files. The Operation Guide contains step-by-step execution procedures for DR testing at local sites. A complete DR test can also be performed at the Local and DR site using the GENDB2 software.

IDCAMS Automation Feature:
The IDCAMS automation feature automates the creation of all DB2 VSAM datasets for DB2 Catalog and Directory Tablespaces, User Application Tablespaces, Active Logs, and BSDS. Space allocation for these DB2 resources is included. Time and resources at the Local Site will be better utilized by eliminating the need for Disk Pack Dump of these resources. Time and resources at the DR Site will also be saved by eliminating the need for Disk Pack Restore. The Delete/Define of these DB2 resources is panel-driven.

Feature to allow the customer to display GENDB2 tables regarding Disaster Recovery.
A. The Archive Log Copy recording information (Original and Copied volume serial number, and data set names (BSDS and Archive) with TIMESTAMP.
B. Start/End RBA and LRSN for latest Archive Log Registration.
C. Conditional Restart CRestart
D. Start RBA for DSN1LOGP

PDS Automation Feature:
The PDS Automation feature automates the recording of PDS type datasets (dsnload, dsnexit, runlib, dsnlink), backups and automates the recovery.

Single Tape Mounting Feature:
When Cataloged Image Copies are stacked on single or multiple tape volumes, GENDB2 will generate the necessary JCL to retain the tape on the drive for multiple recoveries in the same job on-site and off-site disaster recovery.

Datasharing
GENDB2 supports the DB2 datasharing environment.

SMS supported
GENDB2 supports user option to define DB2 VSAM datasets at DR site using SMS.

RECOVER SAP TABLESPACES – Or Grouping of any DB2 Tablespaces.
(1) Recovery Forward
(2) Recovery TORBA using System Wide Quiesce RBA residing on BSDS.

Dropped Tablespace Recovery Feature:
GENDB2 records all DBIDs, PSIDs, and OBIDs. When a dropped tablespace need to be recovered the customer use GENDB2 ISPF panel driven procedure to match the old IDs with the current IDs using timestamp to recover the dropped tablespaces. No longer will the customer be required to run reports and key-in OLD and Current IDs. All required information (DBID, PSID, all OBIDs, input and output dsnames) are displayed on the panel to be selected (not typed from a report).

DSN1COPY – Using Image Copies – Automated generation of JCL and Control cards for DBID, PSIB, and OBIDs
(1) To same DB2
(2) To another DB2 with IDs on same complex sharing datasets.
(3) To another DB2 with IDs on another complex NOT sharing datasets.
(4) Check
(5) Print

DB2 Data Cloning Feature:
Unload/Load - Copy all tables in a database from a DB2 to another DB2 with options to include an (exclude list to exclude certain tables) and (change) the creator of the tables. RESTART ABILITY: In order to save rerun time the ability to restart the load process at any step in case of a failure. REFRESH ABILITY: The ability to use the same input (data and control cards) to load and reload to different DB2 or same DB2 over and over using the same input resources. Nice feature for testing applications and migrating Tables from PROD to TEST in both directions. Customer may save/retrieve Unload/Load information parameters for later use without retyping. Save time while eliminating typing errors.

UNLOAD/LOAD The unloaded information tables and control cards is now stored in DB2 tables allowing the customer to retrieve and load tables as far back as the first unload using the GENDB2 software.

UNLOAD – Option to take backups of unloaded data and control cards to be used at Local site or Remote site.

UNLOAD – Now GENDB2 will do the BLDG for SYSPUNCH and SYSRECXX to create generation data groups for these tablespaces unloaded tables.

LOAD – Now the customer can do a restart of the Load process in case of abends.

LOAD – Now the customer can select only certain tables to be loaded when tables are destroyed.

PRODUCTION STATUS - The customer may now implement the UNLOAD and LOAD GENDB2 generated jobs into production status.

Complete Database Automation Feature:
Complete database automation allows the user to create recovery jobs from a SINGLE panel for ALL Tablespaces and Indexes in a specified database.
1. Recover (Forward, TOCOPY, TORBA) on all spaces in a database.
2. Recover Talespace Groups in Multiple Databases (Forward) and (TORBA) using Archive Log Mode(Quiesce) RBA System Wide consistency. System Wide Consistency is nice to have in a Disaster Recovery situation.
3. Recover all spaces in a TablespaceSET.
4. Check Indexes and Data on all Tablespaces in a database.
5. Image Copy all Tablespaces in a database. Customer may save/retrieve image copy information parameters for later use without retyping. Save time while eliminating typing errors.
6. Reorg all Tablespaces in a database.
7. Quiesce all Tablespaces in a database.
8. Modify all Tablespaces in a database.
9. Repair all Tablespaces in a database.
10. Report all Tablespaces in a database.

On-site Recovery
On-site recovery simplifies and automates the generation of the recovery Job JCL and CNTL statement for all DB2 resources at on-site as well as off-site environments. This tool will display each of the different recovery points of a Tablespace by RBA, Image Copy, Timestamp, Tocopy, etc. as selected by the user using an ISPF Dialog Manager panel. This method eliminates the guesswork from recovery of your User Tablespaces, BSDS, Active Logs, Cat/Dir, etc. as well as the possibility of typing errors. To further ensure accuracy, the recovery of the BSDS and active logs is based on Error Messages issued by the DB2 system. This tool is as close to the one-button approach as is possible.

History Recording Feature:
A history recording feature has been placed on the recovery of your user tablespaces, which is useful for determining what recoveries were previously executed on a tablespace (Forward/Tocopy/Torba with RBA number). All history records contain a timestamp and the user ID of each user submitting a recovery job.

Security Feature:
A security feature allows the user to restrict the use of some features of the tool by user ID’s. Some user ID’s are authorized to recover only user tablespaces while others are allowed to recover only BSDS, or Active Logs, or any combination of the features.

Customization
Open architecture allows the user to customize recovery jobs by identifying all variable names in ISPF tables, skeleton members, and column names in GENDB2 DB2 tables.

Request Additional Information
For free information, please select FREE INFORMATION in the left column, then complete the form or email db2Tech@recoveryknowledge.com