Re: Colored comment code

Doesn't specifying the compile options within the CL member itself using
the DCLPRCOPT do this? The OP wanted to enforce ACTGRP(*NEW), and this
command does this.




From: MichaelQuigley@xxxxxxxxxx
To: wdsci-l@xxxxxxxxxxxx
Date: 07/26/2013 07:56 AM
Subject: Re: [WDSCI-L] Colored comment code
Sent by: wdsci-l-bounces@xxxxxxxxxxxx



The OP's problem was with people compiling via PDM so a new member type
won't help with that. What he needs is a method to compile similar to
Change Management tooling. That's what we've done--written a compile
command (a CL command) which allows us to specify our own defaults and
then uses comments to customize object compilation for an individual
source member. There have been posts about various tools to do that. I
recall at least one had the source to do it released as well. A search of
the archives should turn one up, but I'm not finding it off-hand.

Michael

wdsci-l-bounces@xxxxxxxxxxxx wrote on 07/25/2013 01:00:06 PM:

----- Message from Buck Calabro <kc2hiz@xxxxxxxxx> on Wed, 24 Jul
2013 15:56:14 -0400 -----

To:

wdsci-l@xxxxxxxxxxxx

Subject:

Re: [WDSCI-L] Colored comment code

On 7/24/2013 8:43 AM, darren wrote:

This just in from the InfoCenter. NOTE: This DCLPRCOPT comes after

the

'PGM' opcode

Example: Declaring compiler options to override CRTBNDCL
DCLPRCOPT DFTACTGRP(*NO) ACTGRP(MYAPP) +
BNDDIR(MYAPPLIB/MYBNDDIR)



My example:
PGM

DCLPRCOPT DFTACTGRP(*NO) ACTGRP(*NEW)

If OP is on an old release and can't yet do that, there's a left-handed
way to do that in RDi. Create a new source member type and have the
associated compile command have the defaults you need. All CLLE's that
need this compiler behaviour will then get the same treatment just by
changing their member type. A side benefit is that people compiling
with PDM will have to do something special because they can't take a
simple 14 to compile. Create a user command in PDM that has the exact
same text as your custom RDi compile command and they can then use the
same defaults in PDM that you use in RDi.

1) Change source member type from CLLE to CLLENEW
2) Document parser, map CLLENEW to parser: CL
3) Compile > Prompt
3a) Add new source type: CLLENEW
3b) New command
3bi) Label: crtbndcl_new
3bii) Command: CRTBNDCL PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N)
DFTACTGRP(*NO) ACTGRP(*NEW) OPTION(*EVENTF) REPLACE(&R) DBGVIEW(*SOURCE)
4) Compile

Just an idea.
--buck

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.