In V5R4M5 of LIC there were some incompatibilities at the LIC level, that
were later fixed by PTF.
Al Barsa, Jr.
Barsa Consulting Group, LLC
"i" comes before "p", "x" and "z"
Our system's had more names than Elizabeth Taylor!
Sent by: Midrange Systems Technical
10/19/2007 09:49 Subject
AM SAVRSTLIB problem
Please respond to
I checked the archives, and there was no answer to help me, so here goes...
I have a 520 and a 515. I have configured AnyNet and can STRPASTHR both
ways. I am attempting SAVRSTLIB from the 520 pushing to the 515. I have
checked my Communication Entries, and tested with the user as *NONE, as
QUSER (which I think was installed when ObjectConnect was installed), and
also as *SYS.
Yet, I still get this error on the 520:
Message . . . . : Communications failure. Session was not started.
Cause . . . . . : The system has detected a communications failure. The
sense code is X'080F6051'.
The SNA Formats manual tells me that 080F6051 is:
Access Security Information Invalid: The request specifies an Access
Security Information field that is unacceptable to the receiver; for
security reasons, no further detail on the error is provided. This sense
data is sent in FMH-7 or UNBIND.
On the 515, I am getting this error:
Message ID . . . . . . : CPF1269 Severity . . . . . . . : 00
Message type . . . . . : Information
Date sent . . . . . . : 10/19/07 Time sent . . . . . . :
Message . . . . : Program start request received on communications device
SYSTEM was rejected with reason codes 715, 0.
Cause . . . . . : The program start request was rejected in job
001111/QSYS/QCMN. The device belongs to remote location SYSTEM. If the
device is an advanced program-to-program communications (APPC) device,
program start request was received on mode QSOCCT with unit-of-work
identifier APPN.SYSTEM-C15E493CFBFB-0001. The first reason code means:
Neither password nor user ID was provided, and no default user profile
specified in the communications entry. The second reason code means:
Recovery . . . : See the job log for more information about the problem.
I am using QSECOFR with the same pwd on both servers, so I have no apparent
security issues. QRMTSIGN was tested with *SAMEPRF and *VERIFY for the same
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives