the command i created can be used in WDSC and PDM, you'll have to
"register" the compile command in WDSC and create a user defined option in
PDM. since it's your program you can code it to execute any compile
command you want to.


Thanks,
Tommy Holden



From: Jeff Buening <JeffBuening@xxxxxxxxxxxxxxxxxxx>
To: cobol400-l@xxxxxxxxxxxx
Date: 10/26/2009 07:47 AM
Subject: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)
Sent by: cobol400-l-bounces@xxxxxxxxxxxx



Thanks for all the replies, so I can assume that there is not a PROCESS
type statement to set this in a program by program basis like RPG (for
scenarios that I didn't use even the default I select). And I assume IBM
has not said anything about adding this?

Also Jon/Tommy,

1. So there is a way that I can create a compile command in WDSC and share
with PDM OPM programmers?

OR

2. I create the command on the ISeries for PDM users and create a command
in WDSC for those users?

Thanks,
Jeff Buening

message: 5
date: Fri, 23 Oct 2009 17:20:53 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: Re: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)

which is why i wrote a custom compiler to run from inside WDSC, just add
it to WDSC compile options and i don't have to worry about CHGCMDDFT, etc.
All developers use that compile option for all programs, service
programs, etc. CHGCMDDFT can be a devil...especially when used on other
commands not compiler related.


Thanks,
Tommy Holden



From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: COBOL Programming on the iSeries/AS400 <cobol400-l@xxxxxxxxxxxx>
Date: 10/23/2009 05:15 PM
Subject: Re: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)
Sent by: cobol400-l-bounces@xxxxxxxxxxxx



True - but isn't that one of the sharable options - can't check -
can't load it right now.


Jon Paris


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

message: 5
date: Fri, 23 Oct 2009 17:20:53 -0500
from: Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx
subject: Re: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)

which is why i wrote a custom compiler to run from inside WDSC, just add
it to WDSC compile options and i don't have to worry about CHGCMDDFT, etc.
All developers use that compile option for all programs, service
programs, etc. CHGCMDDFT can be a devil...especially when used on other
commands not compiler related.


Thanks,
Tommy Holden

message: 3
date: Fri, 23 Oct 2009 15:36:10 -0600
from: Jim Essinger <dilbernator@xxxxxxxxx>
subject: Re: [COBOL400-L] ILE COBOL setting ACTGRP(name-group)

But it would not change defaults for the other programmers the OP is
looking
for.

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.



On Fri, Oct 23, 2009 at 3:22 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx>
wrote:

Yes - but I hate changing system defaults. It always strikes me as
being in the category of "accident waiting to happen".

And by changing the default in WDSC/RDi it would be specified to the
compile.


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?


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