[WDSCI-L] Can't resolve to EVSDSPCH problem solved - and a caution

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

I've posted a few items about having trouble with the MCH3401 that EVFDSPCH 
could not be found. Lots or uninstall/reinstalls were tried. I finally 
submitted a PMR and, after some online conversations (love that Internet!), 
we got the problem fixed.

Turns out it is involved with an exit point. When a CODE connection is 
made, including a right-click in WDSC to open the CODE Editor or when 
trying to open a member in CODE, the client adds QDEVTOOLS as a product 
library (there can be 2). The exit point detected the product library, 
saved it, added its own product libraries, then restored the old one when 
it was done. Trouble was, it restored the product library only once - the 
first time the exit point program was called for a given connection. Seems 
it assumed no client would change a product library. Guess we know what 
"assume" does.

Changing the product library back every time invoked will take a little 
more time, but it makes sure things work.

The exit point is QIBM_QZRC_RMT - Remote Command/Program Call.

All is fine now. Don't know what IBM could do to detect changes that would 
not also add a lot of overhead (QUSRJOBI could be called, but...)

Thanks to Mark Phippard and many others who tried to help with this problem.

HTH
Vern