InfoVic
Planning and
Preparing Implementation of a Recovery Strategy after a Crash
- InfoVic displays all the
events occurring on a database (updates, backups, restores) to identify the
risks of loss of use exceeding the tolerated threshold
- InfoVic automates the
procedures to be followed in case of processing problems, thereby avoiding
human intervention, reducing batch overflows onto the TP, and the risk of
error
- With InfoVic, no JCL modifications are required to
handle changes in the applications (adding of a database or a Table). Whenever
a utility is replaced, only one skeleton needs to be modified instead of
rewriting and testing the many JCL streams that use the
utility.
Multiple database restore: InfoVic, synchronizes the restore for both DB2
and IMS databases in combined
applications.
Automated Database Restores
InfoVic provides an application
view of the restore:
- Using a powerful simplified syntax, it automatically
searches for the databases directly or indirectly impacted by the processing
errors
- It avoids fa stitedious writing of restore JCL for these
databases by generating them dynamically
- It automates the entire procedure, in particular by stopping
and restarting the databases, allocating the required number of tape decks,
etc.
Database Optimization and Synchronization
To be efficient, the restore must ensure the integrity of all the
databases, which requires carrying it out from a master synchronization point
(which can be taken both on IMS databases and DB2
Tablespaces). That is why InfoVic, introduces the concept of Virtual Image
Copy (VIC point) corresponding to a "gap" in operation without update (logical
log breakpoint). The VIC function ensures that this result is achieved. Such
synchronization points can be created for:
- One or more Tablespaces, databases or DBDS Groups selected
by generic criteria
- One or more PLAN, PACKAGE, PACKAGE-LIST or PSB
names.
The VIC function can also be extended to the complete Tablespace
Set taking referential integrity into account.