Re: CL Prompting (was Another enhancement request)

Hi Joe,

The CL prompter is supposed to use the connection that the member exists
on.
For local files, it uses the connection set by the default verify
connection (for which you can set a specific server, or ask WDSC to prompt
you for each file when opened).

I've tried out various scenarios with different connections, but I was not
able to reproduce the problem you describe.
You might want to try to clear the _file_ cache from all the temp files
that RSE generates and see if that helps.

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab



wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/06/2006 11:40:51 AM:

Hi Violaine!

Here's an interesting one.  I have four connections to four different
iSeries machines.  Only one is currently connected, and I am editing CL
source in it.  When I go to prompt a CL command in the source, the parser
tries to connect to a different connection.  I think this is the first
connection I ever made in this workspace, but I can't be sure.

I tried moving the connection I am working on to the top of the

connections

in RSE just to see if that would help, but no.  Also, I went in and

changed

the preferences in CL to say V5R2 (since the machine I am working on is

at

V5R2).  Again, no help.

How does the CL prompter determine which connection to use?

Joe


--
This is the Websphere Development Studio Client for iSeries  (WDSCI-
L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.