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



Charles,

In the 36 environment running an RPG36 program, the file does not have to exist before the program runs. The combination of type 'O' on the File-spec and the DISP-NEW in the OCL says, in fact, that the file had better not exist before the program runs.

However, as you know, both RPG III and RPG IV require that the files be available (exist) when they are opened. Create the file before running the ILE program and then, if you still want to use OCL/36, change the DISP- parameter to OLD. My suggestion, though, is to convert the OCL to a CLP with all of the necessary overrides, CRTxx's, etc., that the OCL was expecting. Just as if you had created the necessary CL for the associated program from scratch.

* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Charles St-Laurent wrote:
Hi!

I converted a RPG/36 program to ILE (V5R1). The program is used in an OCL/36 with a LOAD instruction. In the FILE block, I have a DISP-NEW attribute for a file. With RPG/36 version of the program, everything works fine. With the RPG/ILE version of the file, I receive a CPF4102 message when the program tries to run...

Is there any limitation about using DISP-NEW with a ILE program?

Thanks in advance for your answers
Charles




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.