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



Pete

The "main" is named the same as your program.

Now if you are creating a service program with NOMAIN in the H-spec, you won't have this - only subprocedures.

I wish the ILE RPG manuals were clearer about how to replace *ENTRY PLIST with a procedure interface like this!!

Just trying to muddy the waters some more!

Vern
-------------- Original message --------------
From: Pete Helgren <Pete@xxxxxxxxxx>

Thanks Scott. It was the P vs D spec issue that was coming back to
haunt me. My foray into RPG IV and ILE over the past couple of years
has been:

1. Simple conversion to RPG IV syntax and using new op codes and built-ins
2. Replacing subroutines with sub procedures
3. Calling C routines and others from the RPG programs
4. Moving to /free syntax
5. Building everything in WDSc and using only RPG IV

Most of this has been "seat of the pants" development with some reading
("The Modern RPG IV language" and "Free-Format RPG IV" are kept close
by) and lots of searches.

My next steps will take me into modules and binding and all the other
stuff I haven't had to do from "scratch" (yet).

So, if I understand you correctly, I will always have a "main" procedure
that will be coded with D specs that has both a procedure prototype and
a procedure interface if I plan to call the program from CL (for
example). Anything else coded would probably be a sub procedure that
would use P specs for the procedure interfaces.

I'll file this in a safe place in case I get confused again.

Pete

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