|
Jon, Not sure about whether it needs the current library to find the user space or only to create it. But we never deleted the copy in QGPL but changed our two users to have unique current libraries and everything started working fine so it appears that it needs the current library but would take some further experimenting to determine for sure. By the way, we are using the latest version and just received the cd's about 2 weeks ago so this isn't fixed in the latest release. You would sure think that they could create the user space by user id or something like that to eliminate this requirement. Scott > -----Original Message----- > From: Jon.Paris@hal.it [mailto:Jon.Paris@hal.it] > Sent: Tuesday, December 19, 2000 5:01 AM > To: CODE400-L@midrange.com > Subject: RE: Completion messages going to wrong PC > > >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.