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


  1.  Home
  2. WDSCI-L
  3. October 2009

Re: 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


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.