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



Back to my incomplete statement about the prototype for the "program" - actually for the implicit "main" procedure - there appears to be a long-standing error in the manual. Here is something from the Procedures and Subprocedures section of pre-v6r1 reference -

"The name of the main procedure must be the same as the name of the module being created. You can either use this name for the prototype and procedure interface, or specify this name in the EXTPROC keyword of the prototype."

This says to use the EXTPROC keyword. But the example below it uses EXTPGM, which is the correct keyword, AFAIK. Or can it be either? V6R1 seems to be addressing issues related to calling the cycle-main procedure from a subprocedure - I assume that is possible only from within the module - cycle main cannot be exported?

Too much for 4 am in the morrning - and I AM being redundant in the AM!

Vern

David FOXWELL wrote:
Hi,

Can someone clarify this for us waiting for V6? The main procedure you are talking about is surely not the same procedure type. You mean a main SUB procedure surely. Otherwise, when I switch to V6.1 and recompile, all my global variables would become local !

-----Message d'origine-----
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] De la part de BMay@xxxxxxxxx
Envoyé : mardi 4 août 2009 22:04

I did a quick test on my 6.1 box. Variables in the "MAIN"
procedure are not global. Globals must be defined before the
first "p" spec.

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.