Re: BRMS - does *CONSOLE automatically result in a restricted system save

[Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>]

I was asking more for the opposite direction.  Let me explain.

Saturday I'm going to test a new BRMS control group that, after the SAVSYS
is complete, will use an *EXIT to restart the controlling subsystem, then
proceed to backup everything else (*ALLUSR libs, folders, *LINK) as save
while active.

Assuming that works satisfactorily, I could duplicate that BRMS control
group and remove the SAVSYS from the new group.  If I also changed the Sign
off interactive users to *NO for this new group and ran it *CONSOLE, would
BRMS still restrict the system, even though it was unnecessary?

Depending on the results of the first test Saturday, I may try testing this
as well.



On Thu, Jan 17, 2013 at 12:49 PM, Gerald Kern <jp2558@xxxxxxxxx> wrote:

> I'm not sure but the help text shows the following:
>
>                        Start Backup using BRM (STRBKUBRM)
>
>
>
>  Type choices, press Enter.
>
>
>
>  Control group  . . . . . . . . .                 *BKUGRP, *SYSGRP,
> *SYSTEM...
>  Schedule time  . . . . . . . . .   *IMMED        hhmm, *IMMED
>
>  Submit to batch  . . . . . . . .   *YES          *YES, *CONSOLE, *CTLSBS,
> *NO
>  Starting sequ
> ................................................................
>    Number . .  :               Submit to batch (SBMJOB) - Help
>    :
>    Library  .  :
>    :
>  Append to med :  *CONSOLE
>    :
>                :      Transfers the processing of the control group to the
>    :
>                :      system console.  This special value is used with the
>    :
>                :      console monitoring function in BRMS.
>    :
>                :
>    :
>                :  *CTLSBS
>   :
>                :      Submits the control group to the Q1ACTLSBS job queue
>    :
>                :      in the controlling subsystem for batch processing.
>    :
>                :
>    :
>                :
> More...  :
>                :  F2=Extended help   F10=Move to top   F11=Search Index
>   :
>  F3=Exit   F4= :  F12=Cancel         F20=Enlarge       F24=More keys
>    :
>  F24=More keys :
>    :
>
>  :..............................................................:
>
> I looked in the manual and there weren't any entries in the index for
> 'restricted'.
>
> The only way I personally know of is to use (or a copy of) the *SYSTEM
> control group (which includes *SAVSYS as a backup item - and *SAVSYS will
> force the system into restricted state).
>
> My job scheduled entry looks like this: STRBKUBRM CTLGRP(DMCTC2S)
> SBMJOB(*CTLSBS) and the control group is a slightly altered version of the
> *SYSTEM control group - there are other changes I had to make so that the
> above can run fully unattended.
>
> The only other thing I can think of is use an exit program to 'endsbs *all'
> to get into restricted state.
>
> Hope that helps.
>
> --
> Thanks, Jerry
>
> Gerald Kern - Information Technology
> Programming Supervisor
> IBM Certified RPG IV Developer
> Lotus Notes/Domino Administrator
> The Toledo Clinic, Inc.
> 4235 Secor Road
> Toledo, OH 43623
> Phone 419-479-5535
> --
> 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.