|
Without going into why LVLCHK(*NO) is a really bad idea, either an OVRDBF was issued before the call with LVLCHK(*YES) or the file being opened is not the file you think it is. A check of the files in the library list at the time the message was issued might show another file with LVLCHK(*YES). You might also check the job log to determine the actual library and file name being opened by the program. Hope that helps. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> I had them do a DSPFD on the file named in the message just to be sure... What in tarnation is going on? Could this be a bad PTF? <clip>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.