× 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.



Hi Mike

You should have seen some kind of return or error code like 3401 - I'm not sure how much Jon does to surface those - those can be explained using DSPMSGD CPE3401 - put whatever the number is after CPE

HTH
Vern

On 11/30/2015 1:21 PM, Smith, Mike wrote:
Never mind, I finally figured it out.
I thought it was some sort of authority issue, but hadn't thought to check the IFS authority. I deleted the existing files and success.

Thanks

Mike

From: Smith, Mike
Sent: Monday, November 30, 2015 2:04 PM
To: RPG programming on the IBM i / System i (rpg400-l@xxxxxxxxxxxx) <rpg400-l@xxxxxxxxxxxx>
Subject: open access file I/O error

I'm trying to use an open access handler based on Jon Paris IFSHANDLR2 article.
I have gotten this to work in my development library, but after promoting to my QA environment, I get I/O error was detected in file TEMPLT

Running through debug, it appears to have this issue on the header and the detail lines both return -1

I can't seem to find a way to get to the root of the problem though. Program Dump doesn't seem to reveal anything.

Any idea how to get more detail on the problem?

Thanks

MIke
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.