×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
The host name tells me nothing - I have (as previously stated) 6 different connections to one host, 2 different ones to another, and could easily double that if I created connections for all of our different production library lists and had more projects underway. I don't confuse hosts (I know exactly what Mohawk1 and Mohawk5 are and which members I've opened from each), I confuse connections and therefore have members open with the wrong library lists.
Dave Shaw
________________________________
From: Paul Bailey <PaulBailey@xxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, January 9, 2014 11:23 AM
Subject: Re: [WDSCI-L] connection names (was SQL strangeness)
Every source member you edit is downloaded to a temporary file on your PC, and one of the folders in the path of that temporary file is named as the host name of the connection used to open it, so another tip that may be of use is to rename your IBM i machines in your hosts file (Windows\System32\drivers\etc) and then use those renames as the "host name" for each connection you have in your RDi workspace.
e.g. in your hosts file:
192.168.0.2 Live-iSeries
192.168.0.2 Test-iSeries
192.168.0.2 Dev-iSeries
(You must edit the hosts file using the "run as administrator" context menu option on your favourite editor's icon.)
Then, whenever you have a source member open you can see the renamed hostname in RDi's window's title bar when it displays the full source name. The same temporary file name is displayed in the editor tab's tooltip.
midrange.com
