Turns out we are doing all you are except in a control language program
that has a bit more error handling in it, along with the appropriate
Chief Technical Architect
Agile Technology Architects
On 10/8/2012 9:14 AM, ankush agrawal wrote:
I would suggest you to modify your control group to end the applications
first and then issue ENDSBS SBS(*ALL) DELAY(30) *BCHTIMLMT(480)* before
processing of SAVSYS.
So your control group may look like:
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')
and so on.
where SHUTDOWN is my shutdown program to end all applications.
BCHTIMLMT is the time limit for which the system should stay in restricted
state. In above case, after 480 minutes, system will come up from
restricted state and cancel the backup, if the backup doesn't get complete.
After the backup you may want to IPL the system or just start QCTL (
modify control group accordingly).
I am using this on my 6 V7R1 systems and it is working fine.
If I understood your problem wrongly, then please let me know.
On Mon, Oct 8, 2012 at 8:33 AM, Jim Oberholtzer<midrangel@xxxxxxxxxxxxxxxxx
> No changes (except for V7) This have been running this way starting on
> V5R3 for many years. Applications are brought down "nicely" with a
> control language program. Yes, you are correct, it appears the system
> does not go into a restricted state, and therefore cannot proceed with
> the control group. This has only started with V7. Maddingly enough,
> it's also sproadic, it does not happen every time.
> When the upgrade to V7 was done, all the groups and cumulative available
> at the time were applied, so this is the base system, I suppose we could
> go to the A side but that will leave many more things without fixes, I
> believe causing a bigger mess. (namely good use of the TR code).
> Last time it worked (and continues to work fine) is on the V5R4 systems.
> At this time IBM has asked for the flight recorders and job logs. We'll
> see what they come up with. What I'm hoping for is another example to
> help in the diagnostics.
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
> On 10/8/2012 8:02 AM,brad.lovelady@xxxxxxxxxxxxxx wrote:
> > We run weekly/monthly saves to the BRMS batch controlling subsystem
> (*CTLSBS) on 6 systems. I have never had this problem. Sounds like BRMS
> cannot get your system into a restricted state. Did you just recently swap
> from *CONSOLE monitor to the automated batch controlling subsystem *CTLSBS?
> Make sure there is nothing else running in QCTL or whatever you have
> configured to be the controlling subsystem. Only one job can run while in
> restricted state and I am pretty sure you do NOT need to start the console
> monitor when using *CTLSBS. Check the job queue QBRM/Q1ACTLSBS. It should
> be released and added as a single threaded entry to your controlling
> first, leaving the system as close to restricted as possible. Write a
> > If this were my problem I would test by ending all application jobs
> simple CL that runs the command " STRBKUBRM CTLGRP(OURSYSTEM)
> SBMJOB(*CTLSBS)". Submit a job to qbatch or some other active subsystem
> that calls this program. (Do not start the console monitor beforehand.)
> Before doing so make sure subsystems to process is configured properly for
> control group "OURSYSTEM". Better yet, copy OURSYSTEM and have the new
> control group do a SAVSYS only which will ensure the test is quick and
> complete in terms of restricted state processing.
> you are not the addressee or authorized to receive this for the addressee,
> > ***********************************
> > 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 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.
> midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
> > -----Original Message-----
> > From:midrange-l-bounces@xxxxxxxxxxxx [mailto:
> > Sent: Monday, October 08, 2012 7:30 AM
> > To: Midrange Systems Technical Discussion
> > Subject: BRMS Console Issues
> > I am wondering if anyone else is witnessing similar behavior. Scenario
> class and move policy attributes.
> > 3584 tape library: SCSI attached to Power 6.
> > Internal LTO5 single tape on Power 7.
> > BRMS console monitor started
> > Run backup with STRBKUBRM CTLGRP(OURSYSTEM) SBMJOB(*CTLSBS)
> > OURSYSTEM control group is identical to *SYSTEM except for the media
> message indicating the processing is started "BRMS console beginning
> > The system submits the BRMS job to the controlling subsystem, but the
> request processing" is not issued and the system does not come to a
> restricted state, so the job just hangs at this point.
> > Most recent Cumulative and all groups as of 9/5/12, so really current on
> > It is now happening on multiple LPARS on two machines, a Power 6 and 7
> > At this time support does not have much in the way of an answer.
> > If this is happening to others I would like to get that on record as
> > --
> > Jim Oberholtzer
> > Chief Technical Architect
> > Agile Technology Architects
> > --