× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

For anyone who is interested, this was resolved. The customer had saved one of our application libraries in QGPL and named the save file with the same file name. It looks like there was a *LIBL reference to the file in our code and it ended up trying to process the save file as a physical file resulting in this CPF4133 error. The CPF4133 error was misleading because it reported the file name as the library name, not the file name, in QGPL.

Rich Loeber - @richloeber
Kisco Systems LLC


On 4/1/2022 9:20 AM, Rich Loeber wrote:

I have an RPG program, generated from ProGen, that works fine on my 7.3 test system but the exact same program running on a customer's box (also on 7.3) is generating this strange message that is a new one on me:

Message ID . . . . . . : CPF4133 Severity . . . . . . . : 40
Message type . . . . . : Escape
Date sent . . . . . . : 04/01/22 Time sent . . . . . . : 08:49:00

Message . . . . : Option IOUD not valid option for device *N.
Cause . . . . . : The option (I-input, O-output, U-update, D-delete) used to
open file MYLIB in QGPL is not a valid option for device *N.
Recovery . . . : Change the option used to open the file, and try the
request again.

We don't have any code that runs from from QGPL and there is no file in our software called MYLIB. MYLIB is, however, the name of the application library.

Anybody ever see this one? Google has not been my friend on this one.

Rich Loeber
Kisco Systems LLC

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.