|
application.used instead.I was told that IBM pretty much demanded that Go SAVE option 21 be
What? Who told you that? IBM might recommend the option 21 save but
they would never "demand" it. Many, many installations cannot ever
run an option 21 save due to the needs of their business or
It would appear that you have all that you need for a full system
restore per "Are you saving the Right Stuff?"
http://wiki.midrange.com/index.php/Are_You_Saving_The_Right_Stuff%3F
I would expect that you could even run a native Option 21 restore on a
tape created with this backup, assuming "appropriate options" are
truly used. You *might* need to specify Prompt for commands: YES,
it's been a while since I've tested this. As with any and all backup
and restore procedures this should be tested and documented.
If you want to analyze the IBM full system backup do RTVCLSRC
PGM(QMNSAVE)
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest
-----Original Message-----
From: John McKee [mailto:jmmckee@xxxxxxxxxxxxxx]
Sent: Tuesday, August 26, 2008 9:01 AM
To: Midrange Systems Technical Discussion
Subject: Backup question
Our software package is provided by HBOC. They have a number of
commands that are based on IBM commands, with subtle changes. They
differentiate them by prefacing their versions with a 'B'.
Using their commands, a full save of the system was accomplished with
BBACKUP.
This command brings up a number of options. Ultimately, a set of user
defined commands is run. In our case, the commands were: SAVSYS,
SAVLIB, SAVDLO, and SAV, with appropriate options.
I was told that IBM pretty much demanded that Go SAVE option 21 be
used instead.
According to the command help, the only commands that appear different
are that the controlling subsystem is ended and restarted. That
process was performed by operators when BBACKUP command was used.
Is there something else that is going on that is different from the
scripted backup? One reason to ask is that the BBACKUP command logs
start and stop time of each step - which is sometimes an issue.
Thanks,
John McKee
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.