Re: CRTBNDCL DEFAULT WDSC -- WDSCI-L

Charles,
CRTBNDCBL only has the ACTGRP parameter instead of also having
DFTACTGRP parameter and if you use *CALLER that will get it to run in the
DFTACTGRP, if called from an OPM progam, from what I can tell. I would of
figured CRTBNDRPG and CRTBNDCL (for CL's) would ship with DFTACTGRP set to
(*NO), so that it would be put into IBM's default ACTGRP *QILE or (*STGMDL
(which means *QILE) when looking at CRTBNDCL command) since that is the
default on CRTBNDCBL ACTGRP parameter.
Just was trying to decide if there was some reason why IBM would want the
ILE CL to run in a different activation group by default than the ILE COBOL
program by default. I think I am confusing myself the more I look at
it :(. Thanks for the replies.

date: Thu, 15 Oct 2009 14:13:36 -0400
from: Charles Wilt <charles.wilt@xxxxxxxxx>
subject: Re: [WDSCI-L] CRTBNDCL DEFAULT WDSC

Jeff,

CRTBNDCBL doesn't have a DFTACTGRP parameter.

CRTBNDRPG defaults to DFTACTGRP(*YES)

I'm surprised at this given that there is an OPM COBOL. I always
assumed that ILE COBOL offered the same ILE compatiblity mode that ILE
RPG offered via the DFTACTGRP(*YES) parm.

Learn something new every day.
Charles

On Thu, Oct 15, 2009 at 1:30 PM, Jeff Buening
<JeffBuening@xxxxxxxxxxxxxxxxxxx> wrote:

Mark,
? ? ?Thanks for you quick response my basic question is why isn't

CRTBNDCL

DFTACTGRP defaulted to (*NO) in WDSC (or green screen). ?It shows (*YES)
when I compile by default which I assume means it won't be in the QILE
activation group but default activation group. ?Does CRTBNDRPG DFTACTGRP
default to (*NO) or (*YES) without having to change it? Or maybe my shop
has over ridden it to go to *YES and I am not aware of it :). ?I might of
put to much information in my last post.

subject: Re: [WDSCI-L] CRTBNDCL DEFAULT WDSC

Hi, Jeff:

AFAIK, this is because COBOL does not support running in the default
activation group. Period. End of story.

Perhaps Jon Paris can comment on why that is. ?I think it has something
to do with how the behavior of the COBOL "run unit" is specified in the
ANSI Standards for COBOL.

By the way, the CRTBNDC command does not support the use of the default
activation group either, for much the same reasons (the ANSI standards
for C specify certain behavior for C "main" programs.)

Only CRTBNDRPG and CRTBNDCL support the DFTACTGRP(*YES or *NO) parameter.

All the best,

Mark S. Waterbury

Jeff Buening wrote:
I am in the process of understanding ILE more, but was wondering what is
the reasoning for CRTBNDCBL default for Activation Group being set to

QILE

but CRTBNDCL default for Default Activation group is *YES. ?I know we

can

change it but was just wondering if anyone knew when the change to make
CRTBNDCBL QILE why not do the same thing for CRTBNDCL set to *NO.

? ?Thanks,
? ?Jeff

? Thanks,
? Jeff Buening