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



hi Dave you already got the best answer from Mark so I would just like to
point out a possible solution that saved us from spending on a CMS that we
could not afford: STRPREPRC.
It is very flexible and is seamlessly integrated into RDI using iSphere
(thanks to Thomas Raddatz & C.).
Alternatively it can be used as a PDM option.

Specifically Thomas has activated the use of includes, so adding a few
lines in your source's:
MARCO * >> PRE-COMPILER <<
MARCO * >> INCLUDES << QCPYLESRC $RPGPGM4;
MARCO * >> END-PRE-COMPILER <<
allows you to stop worrying about compilation parameters.

All compilation instructions will be contained in a few files (by type:
RPGLE / CLLE / SQLRPGLE or by project: WEBRPG / WEBCL / WEBSQL)
standardizing the generation of programs.
So when you need to change the compilation parameters just change few files
and mass recompile:

Dcl-pr Compile extpgm('BUILDCL');
xPgm char(10);
xSrcF char(10);
xSrcL char(10);
xDes char(50);
End-Pr;

EXEC SQL
DECLARE L1 CURSOR FOR SELECT System_Table_Member , PARTITION_TEXT
FROM Qsys2.Syspartitionstat
WHERE System_Table_Schema = :wSrcl AND System_Table_Name = :wSrcF

ORDER BY System_Table_Member ;
EXEC SQL OPEN L1;
EXEC SQL FETCH L1 FOR 9999 ROWS INTO :ElM;
for i = 1 to %elem(ElM);
if ElM(i).Nome <> *blanks;
// Filters
if %scan('_':ElM(i).Nome) > 0;
iter;
EndIf;
if ElM(i).Nome = 'MUSO00 ';
iter;
EndIf;
// Compile in batch
Compile(ElM(i).Nome:wSrcF:wSrcL:ElM(i).laDesc);
if not *inu1;
leave;
EndIf;
EndIf;
EndFor;
EXEC SQL CLOSE L1;

This is BUILDCL:

PGM PARM(&PGMN &SRCF &SRCL &DESC)
/* >>PRE-COMPILER<< */
/* >>INCLUDE<< QCPYLESRC TSCLLEPGM; */
/* >>END-PRE-COMPILER<< */
DCL VAR(&PGMN) TYPE(*CHAR) LEN(10) /* Pgm name */
DCL VAR(&SRCF ) TYPE(*CHAR) LEN(10) /* Source file
*/
DCL VAR(&SRCL ) TYPE(*CHAR) LEN(10) /* Source lib
*/
DCL VAR(&DESC ) TYPE(*CHAR) LEN(50) /* Obj
Description */

SBMJOB CMD(ISPHERE/STRPREPRC USESRCFILE(&SRCL/&SRCF)
USESRCMBR(&PGMN) OPTION(*EVENTF) +
CHGOBJD(*NO) LIB(MULOBJ4) OBJ(&PGMN)
SRCLIB(&SRCL) SRCFILE(&SRCF) SRCMBR(&PGMN) +
USER0(&DESC)) JOBD(*USRPRF) JOB(&PGMN)

ENDPGM

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno mer 17 ago 2022 alle ore 15:36 Mark Waterbury <
mark.s.waterbury@xxxxxxxxxxxxx> ha scritto:

Dave,
There is a relatively "new" command in CLLE named DCLPRCOPT ...
You use this in a manner similar to the H-spec of ILE RPG IV ...
Place the DCLPRCOPT in your source, and specify the parameters you want,
e.g.:
DCLPRCOPT DFTACTGRP(*NO) ACTGRP('QILE')

and then whenever anyone compiles this CLLE member, whether using PDM
option 14 or the equivalent actions in WDSCi or RDi, or even when typing
the command CRTBNDCL on a command line, it will use these defaults to
override what was specified on the command, just like what the ILE RPG IV
compiler does with H-specs or CTL-OPT statement.
Hope that helps...
All the best,
Mark S. Waterbury
On Wednesday, August 17, 2022 at 09:25:00 AM EDT, Dave <
dfx1@xxxxxxxxxxxxxx> wrote:

Hello,



How can I automatically compile my CL program to run in a named ACTGRP as I
can with RPG programs using the header specifications ? We don’t have any
custom compile commands. If I do it manually, theres a risk that someone
recompiles and it runs in the DFTACTGRP.



Thanks in advance for your help!!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


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.