×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I had expected that this control group, when run as a batch job in the controlling subsystem, would give similar results to GO SAVE-->21. During a recent upgrade, I had two different vendors who could not use the BRMS *SYSTEM save because expected labels needed during the restore process were not present.
Some details:
* A Job Schedule Entry calls a CL that runs in the controlling subsystem,
* The called CL:
o Holds some ERP job queues,
o Shuts down our ERP package,
o Runs STRBKUBRM CTLGRP(MONTHLY) SBMJOB(*NO) MEDCLS(ULTRIUM7)
o "MONTHLY" is a copy of the standard *SYSTEM BRMS backup control group. There are no additional exits, backup items, or omit lists on this copy. It *looks* like *SYSTEM, with the following sequence:
? *EXIT
? *SAVSYS
? *IBM
? *ALLUSR
? *ALLDLO
? *LINK
? *EXIT
The question is: would an experienced user expect the standard *SYSTEM control group to create a tape that is the equivalent of GO SAVE-->21 run manually? Can such a feat be accomplished?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
