Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1

I remember all to well varying stuff off and on and resetting things to try
and get it to work - but that was usually because a line or something had
failed.
I don't lump all that under "SNA"

EE has been exceptionally stable in my experience at a number of different
sites and the only problems I have seen have been network or configuration
related.



On Fri, Oct 18, 2013 at 7:07 AM, <rob@xxxxxxxxx> wrote:

I seem to remember otherwise, but I'm not going to fight that battle. But
maybe it's our definition of network. Me, I'm thinking network means the
consultants problem. Your's may mean a more holistic approach to also
include some underlying appc/appn issue pointed to by the suggested logs
in the trouble shooting steps that needs to be reset.


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: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 10/17/2013 02:02 PM
Subject: Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I only ever had to do this when there were network issues.
Nothing has changed on that score.


On Fri, Oct 18, 2013 at 5:41 AM, <rob@xxxxxxxxx> wrote:

thank you. Now I remember some of the reasons I abandoned SNA.

I used to have documented steps I would take when STRPASTHR would work

one

way but not the other.
sorry, but I've forgotten them.

Here are some good troubleshooting steps, starting with STRPASTHR
failures:

http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzahj/rzahjtrb.htm

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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 10/17/2013 11:22 AM
Subject: Intermittent EE failure initiated by SAVRSTOBJ - V6R1
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Since migrating from ANYNET to EE
SAVRSTOBJ from LPAR A to LPAR B results in failure, intermittently
Strpasthr from A to B also fails.
Strpasthr from B to A works.

On B, Object Connect retries for 2 hours, before reporting the error.
ObjectConnect internal error, function code F5, return code BF.

On A, error occurs, 30 minutes earlier.
CPF3808 Diagnostic 30 10/17/13 04:21:46.431277

QSRSVDEQ

QSYS 0388 QSREVTHD QSYS 03FD
Message . . . . : Save file

OBCSAVF

in QTEMP not complete.
Cause . . . . . : An error

occurred

during the save operation. Recovery . .
. : Do not use the save file

for

restoring because the restore operation
may not end normally. See

message

CPF389C for corrective action.
CPF389C Escape 30 10/17/13 04:21:46.431538

QSREVTHD

QSYS 0568 QSVRSINT QSR 00DC
Message . . . . : ObjectConnect
internal error, function code F4, return
code BF.
Cause . . . . . : An error

occurred

during an ObjectConnect communications
request. Recovery . . . : Try
the request again. See the Backup and
Recovery - Basic book, SC41-4304
for an explanation of the codes. If the
problem persists, report the
problem using the Analyze Problem (ANZPRB)
command.


It appears the "timers" are different on A and B,
LPAR A tries for 90 minutes.
LPAR B tries for 120 minutes.

Sometimes, the issue resolves itself, no interaction done.
Other times, varying off/on EE controller on A that points to B

"appears"

to resolve the issue.

Open PMR with IBM, nothing yet.

Could it be a configuration issue.

Anyone experience similar issue?


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

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

--

Regards
Evan Harris
--
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.