RE: BRMS CPF5140 Error -- MIDRANGE-L

YOMAK = You Owe Me A Keyboard

--
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 rob@xxxxxxxxx
Sent: Wednesday, June 10, 2009 8:24 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS CPF5140 Error

I used an acronym finder for pfm, but yomak strikes out. Well, there were
two sites returned by google but attempts to click on them resulted in a
redirect to an internal website that the site is blocked and expect a
visit from some company employees.

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

From:
"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
06/09/2009 05:02 PM
Subject:
RE: BRMS CPF5140 Error
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

Thanks Jerry. That explanation was very good.

PFM

I had never seen that before, but it only took about 2 nanoseconds to
figure
it out. Close to a YOMAK. :)

--
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 Jerry Adams
Sent: Tuesday, June 09, 2009 4:36 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS CPF5140 Error

Jeff,

We brought in a tech from our BP to do the actual set-up. I'm not much

of
a

hardware person (as noted in an earlier thread today!), but the only
"hardware" thing that I remember was running an Ethernet cable from, I

think,

the T5 slot to a slot in our Cisco switch. (The tech had to fix an

error
I

created when I first set up the 520 because I had plugged something into

T5

which he had to change to T6 - didn't take notes.)

I know that we did *not* install any cards in either the System i or the
PC's. In Service Tools you have to define a unique "device id" for each
console that you want. This is not the same thing as the device

description.

Anyway, when you set up the PC to be a console, there is a "hard-wired"
connection of sorts between the specific PC and the device id (which can

be

reset later if the PC goes completely belly up). I don't know if the

System

i writes a file to the PC to make this connection or uses the PC's mac
address or what. But it's a security feature; unlike the

direct-attached
ops

console you don't want just anyone logging in and becoming a console. My
boss uses one device id and I use another one (the third one is a spare

right

now).

Obviously only one person at a time can be the console.

As for the TCP/IP being down in a restricted state, I don't know that it

is

or isn't. I do know that I have done a few Save 21's, and installed two
cume's since setting up the LAN console. During the latter, the console

does

goes "away" during the IPL, but, when it has reached the right state, it
comes back to the PC (mine) that started the IPL. I just powered down

our

backup system so we could change the UPS. Did it from my desk. After

the

power up, my PC was the console - but my boss could have taken it over

if
he

wanted to.

I don't know how all of this stuff works, Jeff. As far as I'm concerned

it's

just PFM. The only extra hardware was the Ethernet cable that I

mentioned.

Pete, Larry, et al, would do a better job of explaining how it works. I

just

know that it beats the heck out of a twinax terminal or OPS console.

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Tuesday, June 09, 2009 2:08 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS CPF5140 Error

How do you do this? (3 PCs that could each be the console.) When we

got

our 520 some years back, I opted for the Direct Attach ops con because I
couldn't understand how a LAN ops con would work for restricted state
backups, with no TCP/IP running. Recently, Pete described the LAN ops

con

as a cat5 direct from a port on the I to a 2nd NIC in the PC. That made
sense to me. It's direct attach with a network cable instead of a

serial

cable.

Now you say you have 3 PCs that can be the LAN ops con. You surely

don't

have a 2nd NIC as well as a completely separate network in your office

just

for this, do you? Do your LAN consoles go over the regular TCP/IP

network?

If so, how do you do *SAVSYS in restricted state without TCP/IP up?

I must fundamentally not understand something here.

--
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 Jerry Adams
Sent: Tuesday, June 09, 2009 2:23 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS CPF5140 Error

Jeff,

The LAN Console, next to an HMC, is the way to go. I have three

defined

in

SST. First before you can never tell when a PC is going to die; it is
Windows after all (except for the lucky ones running Linux). Second,

I

have

it defined so that one of the others can take over the console. For

example,

I usually start the daily backups on my PC/Console and then leave; my

boss,

if he wants, can just take over the console function while the console

is

running this job (or any other).

Jerry C. Adams
IBM System i Programmer/Analyst
--
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Tuesday, June 09, 2009 12:27 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS CPF5140 Error

Jeff,

I have 3 customers using the *CONSOLE, and 2 are on Operations

LAN

Console, and 1 is on Operations Direct Console. They all love it.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

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

Pete do you have customers using the *console option and if so has any

had

the problem with the BRMS job killing any DSP01 jobs?

On Thu, Jun 4, 2009 at 4:08 PM, Pete Massiello
<pmassiello-ml@xxxxxxxxxxxx>wrote:

Rob,

You can do this with BRMS as of V5R4 I believe. I am doing

it
at

a

few customers who use BRMS, and it works rather nicely.

Pete

Pete Massiello
iTech Solutions
http://www.itechsol.com

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, June 04, 2009 3:56 PM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS CPF5140 Error

I suspect that running a batch job in QCTL does not qualify as being

in

"restricted state".

http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/experience/wmr

stateabstract53.htm?resultof=%22%72%65%73%74%72%69%63%74%65%64%22%20%22%72%6

5%73%74%72%69%63%74%22%20%22%73%74%61%74%65%22%20
"Restricted state is a condition where all the subsystems on the

i5/OS

system have ended and only a single user job remains active in the
controlling subsystem."
I would suspect that the "single user job" would normally be DSP01

or

some

such thing.

So maybe you have a choice:
- that single user batch job with your console totally killed
- having a system console.

Maybe the programmer at the other company is right. And if you try

the

batch job you're SOL trying to check it's status?

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

From:
"Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx>
To:
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Date:
06/04/2009 03:37 PM
Subject:
RE: BRMS CPF5140 Error
Sent by:
midrange-l-bounces@xxxxxxxxxxxx

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.

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

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

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

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

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

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

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

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

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

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