×
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.
Jim,
The current library specified in the connection properties will be the one
used by the RSE job. I believe that when RSE starts other jobs (such as
batch compiles and searches) that it uses the library list of the RSE job at
the time it submits, including the current library. I believe that when
CODE is started from RSE, it's supposed to use that library list as well,
but I've encountered instances where that didn't seem to happen - it used
the library list from the CODE Communication Properties instead. It could
be something wrong with my installation, however, since I also have a
problem with Help not working in CODE. I'd suggest doing a little
experimenting - set up your connection with a *CURLIB different from that in
the user profile and see where the EVFEVENT file and STRCODE user space are
created. If they go where you want them to, you're probably okay; if not,
it's time to explore alternatives.
Good luck.
Dave Shaw
Mohawk Industries
----- Original Message -----
From: "Jim Essinger" <dilbernator@xxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Friday, September 26, 2008 11:50 AM
Subject: Re: [WDSCI-L] Current library question
Thank you Dave.
That is the kind of information I am looking for. I doubt that the
programmers I am going to try and teach will use the CODE editor
except to do compares - I like that compare better too. They might
use the designer. That is what I was remembering and wondering if the
connection specifies a current library that gets set when the
connection starts up will be where code and wdsc (if search is an
issue too) will put their needed information.
As an Amazon Associate we earn from qualifying purchases.
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.