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



Jon/Jeff,

Wouldn't changing the default on CRTBNDCBL do this for him? Unless the
parameter is specified in WDSC/RDi, wouldn't it honor the command default?

Michael
The Way International

cobol400-l-bounces@xxxxxxxxxxxx wrote on 10/23/2009 01:00:08 PM:

----- Message from Jon Paris <jon.paris@xxxxxxxxxxxxxx> on Thu, 22
Oct 2009 15:45:49 -0400 -----

To:

COBOL Programming on the iSeries/AS400 <cobol400-l@xxxxxxxxxxxx>

Subject:

Re: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)

You should be able to set it in your compile options in WDSC Jeff and
it should remember. Worst case scenario design your own compile
command.


Jon Paris

www.Partner400.com
www.SystemiDeveloper.com



On 22-Oct-09, at 3:28 PM, Jeff Buening wrote:

Does ILE COBOL CRTBNDCBL have a way in the PROCESS statement to set
the
compiler to always compile a program in ACTGRP(name-activation)
(whatever I
choose for the name-activation)? I have noticed ILE RPG has an H-
Spec that
seems to do this, but have not found anything for ILE COBOL. The
problem
is that I want to use ILE COBOL with WDSC but others still use PDM
and OPM,
so what to make sure they get the correct default if they compile.
If this
isn't an option why has IBM not done this?


Thanks,
Jeff Buening

Programmer/Analyst
jeff.buening@xxxxxxxxxxxxxxxxxxx
Phone: 419-586-8599
FAX #: 419-586-6224
www.celinainsurance.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.