Re: connection names (was SQL strangeness)

And the answer is - My employer has a group policy in place that prevents me from changing that file, even though I have administrator privileges on my PC.  Bummer.
 
Dave Shaw


________________________________
From: Dave Shaw <daveshaw@xxxxxxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, January 9, 2014 1:34 PM
Subject: Re: [WDSCI-L] connection names (was SQL strangeness)


Oh, I see.  Hmm - sorry I didn't read that more carefully.  Thanks, Paul, that's an interesting approach.  I'll play with it when I get time and see if how it works.

Thanks, Buck and Vern, for making me look at it again.

 
Dave Shaw


________________________________
From: Buck Calabro <kc2hiz@xxxxxxxxx>
To: wdsci-l@xxxxxxxxxxxx
Sent: Thursday, January 9, 2014 12:24 PM
Subject: Re: [WDSCI-L] connection names (was  SQL strangeness)


On 1/9/2014 11:51 AM, Dave Shaw wrote:

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.

I understood the idea to mean I would go into my hosts file and create
dummy host names - aliases - for each environment on the same physical
machine.  Then, when I create a connection, I would chose the alias I'd
like to see displayed as a mnemnonic in the title bar.

That may be a tad cumbersome for me (my current workspace has 13
connections to the same machine) but it's a workaround that could be
implemented immediately while waiting for more RDi-specific support to
come from IBM.
  --buck

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