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



 >> Why must I specify DFTACTGRP(*NO) when compiling?  The only thing I'm
doing different in my program is I'm using prototypes or subprocedures
(which ever is the correct name) instead of using subroutines.

_Because_ you are using subprocedures.  (Prototyping of PGM calls can be
done with DFTACTGRP(*YES).

Understand that this is probably the most misleading parameter name on the
planet.  What it _really_ means is "Do you want me to create an RPG III
style program" - if the answer is *Yes - then you can only do the types of
calls that RPG III supports i.e. dynamic program calls.  If the answer is
*NO then you are creating a real RPG IV ILE program and can do ILE only
"stuff" like bound calls - which is what you are doing when you call a
subprocedure.

The other interpretation of the parameter is "Do you want me to create an
OPM compatible program" (in fact OPMCMPMOD - or whatever OPM Compatibility
Mode would come out as - would be a much better name).  Compiling in
compatibility mode allows the program to respond OPM style to RCLRSC among
other things, but the limitation is that you can't do ILE stuff.

Personally I never do anything but DFTACTGRP(*NO) - I tend to embed the
option on the H spec so I can't forget.  Why is this an issue for you?


Jon Paris
Partner400
www.Partner400.com



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.