Re: BRMS Console Issues -- MIDRANGE-L

Group:

It looks like a PTF is needed at the V6 and V7 levels when the system is controlled by an HMC. There is some code in LIC that does not handle the call between the HMC 5250 and the LIC properly and the console is what hangs up. I am downloading the PTF now ( looks to be really small with no co/pre requisites ) and I'll give it a try.

Ankush: We are doing almost what your suggesting however I never thought to put a CL in there to check the status that's a good idea, however, even if the CL detects a problem, it's only out is to crash the entire job stream since BRMS will not check return codes or the finish status of the control group line. I will however look into a method of doing it. Good idea!

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On 10/8/2012 8:38 PM, ankush agrawal wrote:

Extract from V7r1 BRMS pdf :

*"Due to the nature of batch restricted state processing, which ends the
system console session*, BRMS ignores Signoff Exception processing when
running in this mode." So console will not work.

Jim, you may try this strategy on one of your V7R1 test box.

1. Schedule a job in AJS or native schedular for the backup ( which calls
the control group). The job should be submitted in QCTL sbs.

2. Once the job gets submitted in QCTL sbs, it will start the control
group.

STRBKUBRM CTLGRP(OURSYSTEM) SBMJOB(*CTLSBS)

2. End all the subsystem's from inside the control group. Like the one I
suggested earlier.

Backup
Seq Items Exit command
10 *EXIT CALL SHUTDOWN
20 *EXIT *ENDSBS SBS(*ALL) DELAY(30) BCHTIMLMT(480)
* 30 *EXIT DLYJOB DLY(300)
40 *EXIT SNDMSG MSG('XXXXXXX SPECIAL RESTRICTED BACKUP STARTED')
50 *SAVSYS
60 *IBM

you mentioned that your backup controlgroup is like *SYSTEM.

You may also add a sequence after 30 to call a program to check the
restricted state. (as you have mentioned the system does not come to a
restricted state, so the job just hangs at this point.)

After 15-20 minutes of backup submission time, look for SRC *A900 3C70 on
HMC.* System should be in restricted state to let the batch restricted
backup run.

I am just trying to help you. If the above strategy doesn't work, then I
would definitely like to hear the solution from IBM.

Thanks,

Ankush Agrawal
On Mon, Oct 8, 2012 at 12:48 PM, Jim Oberholtzer<
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> What's got me concerned is it does work at V5R4 (client skipped V6
> altogether) just fine. V7 brings in some troubles.
>
> We'll let IBM chew on it for a bit and I'll let everyone know what I
> find out.
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 10/8/2012 12:31 PM,brad.lovelady@xxxxxxxxxxxxxx wrote:

> > Jim,
> >
> > Sounds like you have everything covered from a BRMS configuration

> standpoint. I do this successfully each weekend 6 times over, but those six
> systems of are on v6. When the STRBKUBRM *CTLSBS command is issued from my
> CL run stream BRMS submits a job named after the control group to Q1ACTLSBS
> job queue which is routed to your controlling subsystem. This is going to
> sound like Captain Obvious but you did review that job log? Seems like that
> log would at a minimum contain some evidence relative to why BRMS is unable
> to restrict the system. Otherwise just wait for IBM to finish the flight
> recorder analysis. I would be interested to hear your solution. I don't
> want to run into this @ v7....it would result in multiple untimely phone
> calls early Sunday morning:-)

> >
> > ***********************************
> > Bradford Lovelady
> >
> > Operating Systems Engineer
> > Technology Infrastructure Services
> >
> > Wells Fargo Bank l 200 Wildwood Pkwy l Birmingham, AL 35209
> > MAC W2691-010
> > Tel 205-938-1999 l Cell 205-826-2834
> >
> > brad.lovelady@xxxxxxxxxxxxxx
> >
> >
> > Wells Fargo Confidential
> >
> > This message may contain confidential and/or privileged information. If

> you are not the addressee or authorized to receive this for the addressee,
> you must not use, copy, disclose, or take any action based on this message
> or any information herein. If you have received this message in error,
> please advise the sender immediately by reply e-mail and delete this
> message. Thank you for your cooperation.

> >
> >
> > -----Original Message-----
> > From:midrange-l-bounces@xxxxxxxxxxxx [mailto:

> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer

> > Sent: Monday, October 08, 2012 11:36 AM
> > To: Midrange Systems Technical Discussion
> > Subject: Re: BRMS Console Issues
> >
> > 1) yes the applications are brought down and TCP is ended in the CL. It

> is not at a restricted state so things like the job scheduler will still
> work.

> > 2) System policy allows batch backups
> >
> > Jim Oberholtzer
> > Chief Technical Architect
> > Agile Technology Architects
> >
> >
> > On 10/8/2012 10:51 AM, ankush agrawal wrote:

> >> > Out of curiosity,
> >> >
> >> > 1. are you calling the CL to end all the subsystems from outside the
> >> > control group? I System console session should be ended. In system
> >> > policy, Allow backups in batch should be *Yes
> >> >
> >> >
> >> > Thanks,
> >> > Ankush Agrawal
> >> > On Mon, Oct 8, 2012 at 10:14 AM, Paul Nelson<nelsonp@xxxxxxxxxxxxx>

> wrote:

> >> >

> >>>> >> > Heehee
> >>>> >> >
> >>>> >> > Paul Nelson
> >>>> >> > Cell 708-670-6978
> >>>> >> > Office 512-392-2577
> >>>> >> > nelsonp@xxxxxxxxxxxxx
> >>>> >> >
> >>>> >> > -----Original Message-----
> >>>> >> > From:midrange-l-bounces@xxxxxxxxxxxx
> >>>> >> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim

> Oberholtzer

> >>>> >> > Sent: Monday, October 08, 2012 10:14 AM
> >>>> >> > To: Midrange Systems Technical Discussion
> >>>> >> > Subject: Re: BRMS Console Issues
> >>>> >> >
> >>>> >> > That was done long ago, well, Rochester support anyway.
> >>>> >> >
> >>>> >> > Jim Oberholtzer
> >>>> >> > Chief Technical Architect
> >>>> >> > Agile Technology Architects
> >>>> >> >
> >>>> >> >
> >>>> >> > On 10/8/2012 10:10 AM, Paul Nelson wrote:

> >>>>> >>> > > Sounds like it's time to call Miss Debbie. :-))
> >>>>> >>> > >
> >>>>> >>> > > Paul Nelson
> >>>>> >>> > > Cell 708-670-6978
> >>>>> >>> > > Office 512-392-2577
> >>>>> >>> > > nelsonp@xxxxxxxxxxxxx
> >>>>> >>> > >
> >>>>> >>> > > -----Original Message-----
> >>>>> >>> > > From:midrange-l-bounces@xxxxxxxxxxxx
> >>>>> >>> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of

> Jim

> >>>>> >>> > Oberholtzer> Sent: Monday, October 08, 2012 10:08 AM> To:
> >>>>> >>> > Midrange Systems Technical Discussion> Subject: Re: BRMS
> >>>>> >>> > Console Issues> > I just checked the system shutdown

> program

> >>>>> >>> > used pre-save.
> >>>>> >>> > >
> >>>>> >>> > > All the applications, WAS servers, Domino, etc are

> brought

> >>>>> >>> > down nicely> with time limits. Then TCP is ended, prior

> to the

> >>>>> >>> > control group> starting. So, all of what we came up with

> to be

> >>>>> >>> > in the way seems to be> dealt with in a proper way.
> >>>>> >>> > >
> >>>>> >>> > > Kinda narrows it down to a processing issue within

> BRMS.

> >>>>> >>> > >
> >>>>> >>> > > Jim Oberholtzer
> >>>>> >>> > > Chief Technical Architect
> >>>>> >>> > > Agile Technology Architects
> >>>>> >>> > >
> >>>>> >>> > >
> >>>>> >>> > > On 10/8/2012 9:58 AM,rob@xxxxxxxxx wrote:

> >>>>>>> >>>>> > >> > Keep in mind that BRMS Network is rather

> fond of TCP/IP.

> >>>>>>> >>>>> > >> >
> >>>>>>> >>>>> > >> >
> >>>>>>> >>>>> > >> > Rob Berendt
> >>>>>>> >>>>> > >> > -- IBM Certified System Administrator - IBM

> i 6.1 Group Dekko Dept

> >>>>>>> >>>>> > >> > 1600 Mail to: 2505 Dekko Drive Garrett, IN

> 46738 Ship to: Dock 108

> >>>>>>> >>>>> > >> > 6928N 400E Kendallville, IN 46755

> http://www.dekko.com From: Jim

> >>>>>>> >>>>> > >> > Oberholtzer<midrangel@xxxxxxxxxxxxxxxxx>

> To: Midrange Systems

> >>>>>>> >>>>> > >> > Technical Discussion<

> midrange-l@xxxxxxxxxxxx>, Date: 10/08/2012

> >>>> >> > 10:54

> >>>>>>> >>>>> > >> > AM Subject: Re: BRMS Console Issues Sent by:
> >>>>>>> >>>>> > >> > midrange-l-bounces@xxxxxxxxxxxx Rob, I

> had not considered that. I

> >>>>>>> >>>>> > >> > wonder if the TCP is getting in the way of

> the back up? I highly

> >>>> >> > doubt

> >>>>>>> >>>>> > >> > that it could affect it much since by that

> time everything using TCP

> >>>>>>> >>>>> > >> > is down, but still... You have to wonder.

> Jim Oberholtzer Chief

> >>>>>>> >>>>> > >> > Technical Architect Agile Technology

> Architects On 10/8/2012 9:50 AM,

> >>>>>>> >>>>> > >> > rob@xxxxxxxxx wrote:

> >>>>>>>>>> >>>>>>>> > >>>> >> > Ok, here's something that

> may differ between V7 and prior

> >>>> >> > releases.

> >>>>>>>>>> >>>>>>>> > >>>> >> > TCP/IP. ENDSBS *ALL

> doesn't kill TCP/IP like it used to.

> >>>>> >>> > > Possibility?

> >>>>>>>>>> >>>>>>>> > >>>> >> >
> >>>>>>>>>> >>>>>>>> > >>>> >> >
> >>>>>>>>>> >>>>>>>> > >>>> >> > Rob Berendt
> >>>>>>>>>> >>>>>>>> > >>>> >> > -- IBM Certified System

> Administrator - IBM i 6.1 Group Dekko

> >>>> >> > Dept

> >>>>>>>>>> >>>>>>>> > >>>> >> > 1600 Mail to: 2505 Dekko

> Drive Garrett, IN 46738 Ship to:

> >>>> >> > Dock
> >>>> >> > 108

> >>>>>>>>>> >>>>>>>> > >>>> >> > 6928N 400E Kendallville, IN

> 46755http://www.dekko.com

> >>>>>>>>>> >>>>>>>> > >>>> >> > --

> >>>>>>> >>>>> > >> > --

> >>>>> >>> > > --

> >>>> >> > --

> > --

> --