RE: BRMS CPF5140 Error -- MIDRANGE-L

A different Jeff here. :)

Per that archived post, this can be done even when doing a full backup,
including the *SAVSYS, right?

--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of lgoodbar@xxxxxxxxxxxxxx
Sent: Thursday, June 04, 2009 2:40 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: BRMS CPF5140 Error

Jeff,

If you are on V5R4 or newer, can I suggest you submit the backup to the
controlling subsystem instead of to the console? It is then a hands-off
operation independent of the console. Here is a note from the archives:
http://archive.midrange.com/midrange-l/200802/msg00770.html

Excerpt:
"*SYSTEM policy page 2
Controlling subsystem
Allow backups in batch: *YES
Restricted state end time: nnn
This allows BRMS to end the batch job if restricted state time in
minutes is exceeded. Otherwise, need to force DST on console and take
option to end restricted batch job.

"Then in your job scheduler:
STRBKUBRM CTLGRP(WEEKLTOCG) SBMJOB(*CTLSBS)"

We've run this since we upgraded to V5R4 and had only one issue which
required going into DST and force ending the backup. We use this for our
weekly (Sunday) full system save and had no issues with it for over a
year or so.

If you pursue, make sure the restricted state end time (expressed in
minutes) is large enough to accommodate your backup window. Last week
our system pulled out of restricted state automatically (good!) near the
end of the backup (bad!), so we had to increase the restricted state
time. Other than that had wonder experience with it.

HTH,
Loyd

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Curtis
Sent: Thursday, June 04, 2009 8:05 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS CPF5140 Error

Could it be that either

a.) there were two DSP01 jobs on the iSeries and BRMS did not know
which
one to use so it aborted with the CPF5140 error?

b.) the BRMS console job was not signed on with the same id which runs
the
BRMS save job?

On Wed, Jun 3, 2009 at 9:51 AM, Jeff Curtis <jcurtis1027@xxxxxxxxx>
wrote:

It was a shared session.

On Tue, Jun 2, 2009 at 5:03 PM, <rob@xxxxxxxxx> wrote:

Was your hmc 5250 session "shared" or "dedicated"? We never use
"dedicated" anymore. With "shared" you can:
- kill the session on the hmc (but not the hmc) and it should stay

running

- share the session from your pc, etc
The CPF5140 error really sounds like a drop between the console and

the

box. You should be able to do a
WRKJOB DSP01 or whatever your console is called, and look at that

joblog.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

From:
Jeff Curtis <jcurtis1027@xxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
06/02/2009 04:20 PM
Subject:
BRMS CPF5140 Error
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

I am hoping someone can help me here. While running a BRMS backup

(a

full
system save) with the *Console option and the BRMS console running on

our

HMC 5250 session, a CPF5140 error appeared and killed the backup and

the

console. We had to reconnect and do an IPL. Has anyone had this
happen
before and what can be done to correct it?

Thanks,

Jeff

--
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.