The client is preparing to upgrade their CA View databases and would like an idea as to how long it would take to run a SARDBASE VERSION.
Also, what would be a suggested test for the user support area to run after the database is updated?
Release : 14.0
Component : CA View
To determine how long a SARDBASE VERSION may run:
. From a run of SARDBASE STATUS FULL, for the Index statistics provided:
. . Multiply "Total cylinders" by "Percentage", to give you the number of cylinders used.
. . The job should run approximately 1 clock second per 50 used cylinders, or thereabouts.
. . Note: The above time could be affected by job priority, available resources, etc.
To determine how long a RMODBASE VERSION should run:
. From a run of RMODBASE STATUS FULL:
. . Multiply "Total cylinders" by "Percentage", to give you the number of cylinders used.
. . The job should run approximately 1 clock second per 50 used cylinders, or thereabouts.
. . Note: The above time could be affected by job priority, available resources, etc.
The standard upgrade, beyond upgrading libraries, JCL, and procs, would involve:
. Running SARDBASE/RMODBASE VERSION nn.n
. Running SARDBASE/RMODBASE OLOAD
. Running SARDBASE/RMODBASE BLOAD (optional)
. Updating coding of and reassembling of user exits
Deliver Test Plan
-----------------------
Add user
Delete user
Add Report
Delete Report
Add Job
Delete Job
Add Bundle
Delete Bundle
Giving Access
Run a job thru
Create Distribution list
E-mail Link (prod)
E-mail attachment Report (prod)
View Test Plan
--------------------
Index Report
Delete a Report
Run Backup
Inter-mid Backup
Def User
Restore a Report from Tape
Move reports from TEST to PROD
Browse a report from all the affected databases
Check ERO Entry on Reports
Check SECURITY
Run Status Command
Run SARDBASE utility STATUS FULL
Run SARBCH utility /LIST ID=* GEN=*