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



Vern,

I guess I don't understand. Since EVFEVENT is multi-membered by program name, and is associated with the compile-to library (not the *CurLib), why would this be a reason? Even if EVFEVENT was in the *CurLib (which it isn't), why would that matter? I.e., why would 2-n programmers be working on the same program?

In my case, I set up project libraries for each, well, project. There are usually multiple programs being added/changed. When I compile via WDSc, the iSeries Error List always brings up the correct list (i.e., the one I just submitted for compile, not the one I did five minutes or two days ago).

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email: jerry@xxxxxxxxxxxxxxx

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of vhamberg@xxxxxxxxxxx
Sent: Friday, September 26, 2008 3:47 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Current library question

Felix

The reason is, there is a file called EVFEVENT that has members for each compile you do - it has the error listing. This file name is always the same, so for multiple programmers, they each need their own library, so that they do not step on the toes of other programmers.

Make sense?
Vern
-------------- Original message --------------
From: "Felix Cartagena" <fcartagena@xxxxxxxxxxxxxxxx>

May I ask what is the reason IBM recommends that every WDSc/RPG
programmer have a unique current library?

In our shop, programmers do have their unique current library to
separate each others objects (Source still resides in one main test
library). This has been in place many years ago. We do not use any SCM
yet?



-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jim Essinger
Sent: Thursday, September 25, 2008 6:25 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Current library question

My understanding was that error lists from compiles and search results
at least were dependent upon having unique current libraries for each
developer on the i. If that has changed, it would be nice to know. I
did some searching to make sure I was going the right direction when I
installed my instance on this PC, and found current library a
discussion of past posts. They all recommended unique current
libraries.

Jim

On Thu, Sep 25, 2008 at 3:33 PM, wrote:
Unless IBM fixed it, you still have problems even in RSE with the
error results of compiles, I believe, when everyone has the same current
library.

But I could be wrong - been there a couple times this year already -
heh!

Vern

-------------- Original message ----------------------
From: Justin Taylor
All of our developers have the same current library. The only issue
that we
have found is compiling out of CODE.
--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.