Re: issue with compile

On 2/2/2016 5:32 PM, Hoteltravelfundotcom wrote:

HI - I am looking at a working program that is not compiling. I use option
14. It will compile successfully as a module but not 14. I must be leaving
out a step in the compile?
1.
7503+D* I: Pointer to instance

RNF3788 30 7498 059600+ DFTACTGRP(*NO) must be specified for a prototype
that does not have the EXTPGM keyword.
A650AP/QASWCPYPRC(SROARL)

7504+D this_object * CONST



2. there is also an error here maybe its' connected
*RNF3788 30 994 DFTACTGRP(*NO) must be specified for a prototype that
does not have the EXTPGM keyword.


1002+ * RETURN type: Business object attribute
*RNF3788 30 992 028100+ DFTACTGRP(*NO) must be specified for a
prototype th
not have the EXTPGM keyword.
1003+D ASWLDA_getCodeForNo...
1004+D PR EXTPROC('ASWLDA-
1005+D _getCodeForNo')
1006+D LIKE(ASWLDA...

Hi Joe,

The error message is very clear, but perhaps the context is not.

Did you add these sub-procedures, or is this existing code?
Sub-procedures (and not simply prototypes for external program calls)
require the program to be running in a real activation group, not the
default.

So. If you added these sub-procedures, you should add an H-Spec for
DFTACTGRP(*NO). An alternative is to specify these parameters on each
CRTxxxRPG command. You need to check with people there to see what
their activation group strategy is: we can't tell you. An additional
thought: If there is a change management system there, the CM should
handle the activation group question.

On the other hand, if these are pre-existing sub-procedures, then
someone has already compiled the program by overriding the defaults on
the CRTBNDRPG command. DSPPGM will show the name of the activation
group, but there's no harm in double checking with people there.