You certainly do not need to end all the subsystems to save your data,
only the programs that are using the files. You do not need to do Full
System Saves daily, only when the system changes. You do need to
clearly identify user data and system data.
See:
http://www-03.ibm.com/systems/i/support/brms/pdf/savpost3.pdf
Create a subsystem and JobQ to run your BRMS backup in, then end the
others and do STRBKUBRM CTLGRP(*BKUGRP) JOBQ(BACKUP)
Create a startup program that restarts your application programs and
call that from your BRMS exit. You don't want to have to IPL every time
you need to restart your application programs.
If you do not have physical access to the console you need remote
console access. What are you going to do if your backup hangs (Media
error, power failure) while you are restricted?
Do not try to build a backup plan without a restore plan. Start with a
restore plan and build your backup around that.
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Fiserv Midwest
-----Original Message-----
From: franz400@xxxxxxxxxxxx [mailto:franz400@xxxxxxxxxxxx]
Sent: Tuesday, February 19, 2008 8:57 AM
To: midrange-l@xxxxxxxxxxxx
Subject: BRMS restricted system
Does BRMS allow a FULL backup (not SYSTEM) to execute from scheduler
putting the system in restricted condition?
I did this on scheduler
STRBKUBRM CTLGRP(*BKUGRP) SBMJOB(*CTLSBS)
Within *BKUGRP I did an *Exit - endsbs *all *immed
then saves
then *Exit - call qstrup
Many errors in job log, and basically did save without ending
subsystems.
Mgr insists on no SWA, and without endsbs many files in use by various
pgms.
(new to BRMS)
Jim
midrange.com
