× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. June 2009

RE: BRMS CPF5140 Error

Aaah.

So ops con has it's own TCP/IP stack?

Theoretically, could my PC have a 2nd NIC, a cat5 direct to a port on the
520 (like T5), and be the console; then, if my PC takes a powder, any other
PC could take over the console so long as the ops con portion of i Access is
loaded, even if that PC has only 1 NIC?

--
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 Charles Wilt
Sent: Tuesday, June 09, 2009 4:12 PM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS CPF5140 Error

Jeff,

Basically what you are missing is that having the OS in restricted
state with the OS TCP stack down, doesn't mean that you can't have an
application with its own built in alternative TCP/IP stack running.

In fact, you can write such an app yourself.

Charles

On Tue, Jun 9, 2009 at 3:08 PM, Jeff Crosby<jlcrosby@xxxxxxxxxxxxxxxx>
wrote:
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.