 |
|
| Below are some common questions asked by prospective users of $AVRS. If you have further questions, or need further information on the below questions please contact us. |
|
|
$AVRS can manage multiple SYSLOGS coming from different systems, even
if they come thru the same SYSLOG class. $AVRS will accumulate and maintain
the autonomy of each system's Syslog within $AVRS. The SID or the SYSLOG
ID can be used as filtering criteria when searching for work. There is
no $AVRS limit on the number of different system's SYSLOGS that may be
accumulated. |
 |
|
|
|
$AVRS can be set up to process dumps and can
recognize 2 different types of dumps, IBM dumps and non-IBM dumps. $AVRS
can manage both types, each type individually, or not process dumps at
all. If dumps are not processed and sent to $AVRS they can automatically
re-spun to a different JES output class. |
|
|
|
|
All annotations and acknowledgements that are
attached to work within $AVRS at the time of archived are written to the
backup. If work needs to be restored to the database the annotations and
acknowledgments are restored with the work. |
|
|
|
|
$AVRS comes with a batch program called Forward Merge. This program take
a grouping of backup datasets, a weeks worth for example, and merges them
into one new GDG dataset. The $AVRS database gets updated with the information
for the new dataset. This process is transparent as far as restores are
considered. This allows for the retention of archived work within GDG
datasets for an unlimited amount of time. |
|
|
|
|
Yes, $AVRS is running on z900 processors in
many environments. $AVRS is fully hardware independant and only dependant
on the JES2/JES3 operating system they are runnign under. |
|
|
