|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Sounds like one of those things we'll just have to live with until IBM figures it out. The sad part is that with the new users here in my office, when things like this pop up they tend to think "Why bother learning this tool if it doesn't work properly". They won't use it long enough to figure out that the package is a great set of tools. I'll just have to keep reinforcing that! Thanks for the info, Jon. Chris -----Original Message----- From: Jon Paris [mailto:Jon.Paris@Partner400.com] Sent: Wednesday, May 29, 2002 5:14 PM To: code400-l@midrange.com Subject: Library list problem in Code >> I told Steve what you had suggested and he said that he did that already and the library that contains the file was in the libl..... This is too weird!!! I've seen this a couple of times recently when teaching Code classes (V5R1 with SP4 and with SP5) - I thought it was a caching problem originally but the error continued when we turned caching off. It eventually went away after we ran a successful compile or three. In none of the cases I have experienced was the situation repeatable, but I have to believe it is a bug somewhere in Code. Jon Paris Partner400 _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l.
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.