Re: Problem with multiple simultaneous searches

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

Here is a "work-around" -- ensure that each developer has their own 
CURLIB, and it is specified as their default CURLIB, in their user 
profile, e.g.:
       CHGUSRPRF   USRPRF(MARKW)   CURLIB(MARKW)

This is generally a "good idea" or "best practice" for developers 
anyway, IMHO. Each developer should have their own private "workspace" 
(CURLIB); they own this *LIB and all objects in the library, and the 
library has *PUBLIC *EXCLUDE (or at most, *PUBLIC *USE) authority.

Regards,

Mark S. Waterbury

Joe Pluta wrote:
> I was just giving an onsite class on WDSC to a group of nine RPG programmers
> and while they were generally pretty enthusiastic about the tool, we did hit
> one really nasty snag.
>
> At one point, I had the entire class do an iSeries Search.  At that point,
> odd things happened.  Some people got other people's results, and some
> people got the following error:
>
> "EVFF9007E: Cannot remove and create member EVFEVENT in file QGPL/EVFEVENT
> to hold the search result.  Release the file and try again."
>
> Hmm.  It seems like all search requests hit the same member.  They should at
> the very least be different members for different connections (you could use
> the job number of the connection job as the differentiator).  There are
> issues with cleaning up those members when the jobs end, but there are ways
> to handle that (e.g., you can register a cancel handler for the connection
> job).
>
> Anything is better than everybody sharing the same member.
>
> In our class, we had people searching two source members in their own
> library for a string; some people got results from other libraries, and some
> didn't get anything at all or got the halt mentioned above.
>
> Joe
>
>
>