Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1

Nothing positive to say, it's SNA. IBM probably retired all the people
who worked on that.
However, you could search for SNA sense codes

ftp://ftp.software.ibm.com/software/network/commserver/publications/csnt_60/snafmt.pdf


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: 05/19/2014 09:57 AM
Subject: RE: Intermittent EE failure initiated by SAVRSTOBJ - V6R1
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



I had first repeat EE failure caused by SAVRSTOBJ in 6 months.
This is the first since both LPARS are on V7R1.
We run this command, scheduled, 3 to 4 times a day.
Last year, did many traces with IBM, no resolution.
Any suggestions from the group?


CPF1124 Information 00 05/19/14 06:30:52.401217 QWTPIIPP
QSYS 04C0 *EXT *N
Message . . . . : Job
897420/PRODUCT/PENCOR05 started on 05/19/14 at
06:30:52 in subsystem QCMN in QSYS.
Job entered system on 05/19/14 at
06:30:52.
CPC2196 Completion 00 05/19/14 06:30:52.427145 QLICUSRL
QSYS 0114 QSVRCI QSR 01AF
Message . . . . : Library QSR added
to library list.
CPFAD85 Information 00 05/19/14 06:30:53.061802 QSVRSRA
QSR 0363 QSVRCI QSR 005A
Message . . . . : Corresponding
source information from location PENCOR05.
CPF3734 Diagnostic 30 05/19/14 08:19:15.947577 QSRRSPST
QSYS 1326 QSRRSLIB QSYS 1399
Message . . . . : FILE DSPOBJD in
P05USAGE not restored.
CPF3770 Diagnostic 30 05/19/14 08:19:16.061658 QSRROCPR
QSYS 065B QSVRSRA QSR 0090
Message . . . . : No objects saved
or restored for library QGPL.
CPF389C Escape 30 05/19/14 08:19:15.889749 QSRRSDEQ
QSYS 0B9C QSVRSRA QSR 0090
Message . . . . : ObjectConnect
internal error, function code F5, return
code BF.
CPF9897 Information 40 05/19/14 08:19:16.072989 QSVRSRA
QSR 0B06 QSVRSRA QSR 0B06
Message . . . . : QSVRSRA End_Agent
Ending Agent
CPC1125 Completion 50 05/19/14 08:20:31.138285 QWTCCCNJ
QSYS 0C03 *EXT *N
From user . . . . . . . . . : PAULS

Message . . . . : Job
897420/PRODUCT/PENCOR05 was ended by user PAULS.

Paul

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steinmetz, Paul
Sent: Friday, October 18, 2013 10:11 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Intermittent EE failure initiated by SAVRSTOBJ - V6R1

Use EE only, ANYNET not supported at V7R1.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Friday, October 18, 2013 10:08 AM
To: Midrange Systems Technical Discussion
Subject: Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1

Here is another good link, was your intention to keep both ANYNET and use
EE or to convert to just EE.


http://pic.dhe.ibm.com/infocenter/iseries/v6r1m0/index.jsp?topic=/rzajt/rzajtanytoee.htm



On Thu, Oct 17, 2013 at 9:07 PM, Neil Palmer
<neilpalmer400mr@xxxxxxxx>wrote:

Another Enterprise Extender tip.
AnyNet does not care if the data sent back to the source system is
routed back from the same IP you sent to.
Enterprise Extender DOES.

If your SystemA has an Enterprise Extender controller to SystemB at an
IP address of say 12.100.200.15 BUT SystemB routes outbound traffic
over a different route so that SystemA sees the data coming back from
say 12.100.200.95 then you will have problems.
One of the symptoms can be that if you are on SystemB you can always
originate a connection (say STRPASTHR over Enterprise Extender) back
to SystemA. But System A can only originate a STR{ASTHR connection to
System B within a short time period (a minute or two) of when System B
initiated a connection to SystemA (or maintains an active connection)
- if you follow me.

In other words, if the location of the remote SystemB has multiple
Public WAN IP addresses for Internet traffic, make sure the one
SystemA has defined for the Enterprise Extender controller is the same
Public IP that routes traffic back from SystemB.



And yes, check all Enterprise Extender PTFs here:
V5
http://www-01.ibm.com/support/docview.wss?uid=nas8N1017409

V6

http://www-01.ibm.com/support/docview.wss?uid=nas8N1013733

V7
http://www-01.ibm.com/support/docview.wss?uid=nas8N1012511


Neil Palmer, Waterloo, Ontario, Canada


(This account not monitored for personal mail, remove the last two
letters before @ for that)


________________________________
From: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, October 17, 2013 2:01:20 PM
Subject: Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1


Keep in mind you are running over the network, so don't rule out
network issues.

Make sure the required ports are open in your firewalls, especially
the
12000 thru 12004 UDP ports


On Fri, Oct 18, 2013 at 4:20 AM, Steinmetz, Paul
<PSteinmetz@xxxxxxxxxx

wrote:

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.

--

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.

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