You can now do this with the mode *CTLSBS mode. No command necessary for
the console.
We start from the job scheduler every Sunday morning.
You must run a CL first that ends Linux partitions, xSeries, Domino
servers, and any thing else you need to be shut down.
STRBKUBRM CTLGRP(*SYSTEM) SBMJOB(*CTLSBS)
Thanks,
Carl Novit
Vice President
FRS, Inc.
843.720.7436 ext. 7708
Carln@xxxxxxxxx
"Pete Massiello" <pmassiello-ml@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/19/2008 11:29 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc
Subject
RE: BRMS restricted system
You do this using the BRMS console function, I have a few sites that run
it
this way. From the console they
Enter the BRMS console mode, and then they have a job on the scheduler
than
does a complete system save.
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
franz400@xxxxxxxxxxxx
Sent: Tuesday, February 19, 2008 9: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
