×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Wow. Good question. I'm the same way. Hover on the tabs will tell you the server name, but doesn't do you any good if multiple connections use the same server.

I tried doing a "Save As". That produces a tree at your current source file. Go to the toward the top of the tree to its connection. Then, you cancel out.

HTH,
Matt Qualls

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Kerwin Crawford
Sent: Thursday, October 25, 2018 1:54 PM
To: 'wdsci-l@xxxxxxxxxxxx' <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] Source came from what connection

I got a quick (I hope) RDi question. I am running Version 9.6.0.4 of RDi.
I have several connections created, each to the same system but different library list. This is working.
My question is. When I have a source member open in the LPEX editor how can I tell from what connection was it opened from?

#
Kerwin S. Crawford
IBMi Programming Team Leader
IBMi Systems/Applications Programmer
ASI (Application Software Inc.)
201 W. Broadway Suite 4C
Columbia, MO 65203
1-573-442-3035 ext. 5622
1-800-659-3035 ext. 5622
KCrawford@xxxxxxxxxxx<mailto:KCrawford@xxxxxxxxxxx>
www.asiflex.com<http://www.asiflex.com/>

--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-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-2026 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.