----- Message from Jeff Buening <JeffBuening@xxxxxxxxxxxxxxxxxxx> onthe
Fri, 30 Oct 2009 13:02:44 -0400 -----
[COBOL400-L] DFTACTGRP(*YES) vs ACTGRP(*Caller)
I have seen the below on some post...........
Programs compiled with DFTACTGRP(*YES) do not behave the same as
ACTGRP(*CALLER), even if the ACTGRP(*CALLER) program was called from
default activation group. This is because specifying DFTACTGRP(*YES)does
more than control which activation group the program is compiledinto,
it also controls some other OPM compatibility things.convert
I have seen post that say DFTACTGRP(*YES) was to help RPG programs
to ILE with out all the goodies of ILE, but still use SEP, contentassist
etc.. CRTBNDCBL for cobol does not have a DFTACTGRP parm just ACTGRPparm.
So can I assume using ACTGRP(*CALLER) in cobol is similar to theDFTACTGRP
(*YES) that RPG has? Not sure what the other compatibility things are?program
If I have Cobol "Program A" calls "Program B" and "Program B" is a
that gets used all throughout the system not just in my "Program A" Callwould
"Program B" application. If I am changing just my application to ILE
making "Progam B" ACTGRP(*Caller) be the way to go since otherapplications
that are still ALL IN OPM COBOL will still be calling "Program B"? Hasbecause
anyone done something similar and sees issues with this thinking,
one post will say one thing and the next another? Or did you create
duplicate programs one for ILE and one for OPM?
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.