Yes. Perhaps there is a better way, but at least we had it working (before we replaced the partition)

Pete

Ingvaldson, Scott wrote:

Are you using AnyNet?

Regards,

Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Fri, 27 Jan 2006 10:19:18 -0700
from: Pete Helgren <Pete@xxxxxxxxxx>
subject: Re: Problem with connection between LPARS

Answers for all posts (thanks!):

Chris: There are no errors on the target system. Authority seems not to be an issue.

Michael: Yes.  The mode descriptions are the same.

And I guess I am not surprised by those findings since the SAVSYS on the

production side would have copied everything to the development side.

Rob: Hmmm. The target system descriptions weren't in the directory or routing entries (since they were clones of the production system) and, more interesting, there aren't any *ANY entries for the development partition in the production side or vise a versa, yet the production side is still "finding" the development side.

I used CRTCTLAPPC when I created the controller description and it is identical, except the object name and description, to the controller on the production side. If I vary off the controller on the production side I can no longer pass through to development so I know I have the right controller. On the development side the device description is created automatically under the controller I created so I think I have that correct as well.

Pete


rob@xxxxxxxxx wrote:

Those SNA error codes are fun, eh?
Did you verify CFGDSTSRV options 1 & 2?
Does WRKDIRE have a valid *ANY entry for the opposite system on each
lpar?
You could try deleting the sna controller and device and see if they autocreate. I've done that.


Rob Berendt


DISCLAIMER:
This message and accompanying documents are covered by the Electronic 
Communications Privacy Act, 18 U.S.C. ?? 2510-2521, and contains information 
intended for the specified individual(s) only. This information is 
confidential. If you are not the intended recipient or an agent responsible for 
delivering it to the intended recipient, you are hereby notified that you have 
received this document in error and that any review, dissemination, copying, or 
the taking of any action based on the contents of this information is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.