×
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.
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
Programmer/Analyst
jeff.buening@xxxxxxxxxxxxxxxxxxx
Phone: 419-586-8599
FAX #: 419-586-6224
www.celinainsurance.com
midrange.com
