|
This link
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backup%2C%20Recovery%20and%20Media%20Services%20(BRMS)%20for%20i/page/Specifying%20ASYNCBRING%20for%20IFS%20backups
Says "BRMS uses the Save Object (SAV) command and QsrSave API to backup
integrated file system (IFS) objects."
So I think you'll want the CALL to Q1AOLD
Charles
On Wed, Jul 16, 2014 at 9:07 AM, Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:
All,BRMS
A bit of confusion in regards to BRMS using this.
In the cover letter for 5770BR1-SI44710 it says:
<cover>
13. In V6R1 and above, override support for the new ASYNCBRING
key on the QsrSave API to help improve IFS save performance is
now possible using one of the following commands:
To enable the new ASYNCBRING key:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'ASYNCBRING' '*YES')
To disable the new ASYNCBRING key:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*ADD' 'ASYNCBRING' '*NO ')
To remove the override, use the following command (default is
*NO):
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*REMOVE ' 'ASYNCBRING')
To show the current override being used, use the following
command:
CALL PGM(QBRM/Q1AOLD) PARM('PARMOVR' '*DISPLAY' 'ASYNCBRING')
</cover>
If I run the last command to display the override, the result is blank,
which, I assume, means no override. I changed the default on the SAV
command to ASYNCBRING(*YES).
Does BRMS use the default on the SAV command ASYNCBRING parm? Or does
use the QsrSave API and therefore I must run the command above to enableit
in BRMS even though it's the default on the command?list
Thanks.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
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.