|
> as I am not aware of the issue and concerns discussed and addressed > previously, could you please enlighten me on this? Sob!! ..... I guess the fact that you don't know about it kinda answers my question but .... Code/400's insistence on having a current library and more significantly that the library be unique to a user is a real problem for many people. I know that it is possible to get round it to some degree but have yet to find consistent work-arounds that deal with all situations. Let me describe two customer situations that we have encountered recently: One customer I recently trained in the use of Code/400 has a policy of having _all_ current development being in a single library. There are six developers and they all share this library as their Current library. You can imagine that this gets "interesting" at times! As a temporary expedient they are manually changing to a unique current library and using STRCODE (which they don't want to use long term) but this has the effect of screwing up a number of in-house tools that they use for compiles and promotion of code to production. Second situation is similar in effect but different in cause. The customer has an initial program in the signon that does a number of things, one of which is to set up their library list based on current project assignments. The last thing this does is to set the current library. Guess what, the autostart servers won't. Using STRCODE doesn't help for the reasons described earlier - multiple people use the same current library. I'd be interested in the experience of others on the list in this area. As to the previous discussions, and suggested solutions I won't fill the list with that. E-mail me off list if you wish to discuss further. Jon Paris Partner400
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.