|
>> We have just had this problem and have stumbled on to an answer that may work for you. Thanks Scott, we did have this situation and I knew this was a problem but thought we'd dealt with it. Now that I've read your note though it occurs to me that we may not have gone far enough in cleaning up after our initial attempts. The customer uses the same library list for _everyone_ and sure enough they all share the same CURLIB. We didn't realize this until _after_ we started getting all the completion messages popping up on a single workstation. Subsequently we switched to using STRCODE servers (which we had hoped to avoid) just so that they could switch the library list before starting the server. We did not delete the user spaces though. I wonder if there is a point in the process where the Code server just uses the library list to find the space and only uses CURLIB when creating it? That would explain the fact that even after we switched to STRCODE servers at least a couple of the users were getting their messages mixed up. I do hope this has been fixed in the new release. It really is very restricting to insist that each user have a separate current library. Indeed the way this customers source control system works it would make it impossible for them to use Code without a major overhaul of their regular working environment. +--- | This is the CODE/400 Mailing List! | To submit a new message, send your mail to CODE400-L@midrange.com. | To subscribe to this list send email to CODE400-L-SUB@midrange.com. | To unsubscribe from this list send email to CODE400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: larry@paque.net +---
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.