Re: PDM option that submits customized compile

I have created a utility that can read comment in a source member and
execute them. This way, the compile instructions are within the sources
them selve.

Here is an example:

*%%%* Compiling instructions -------------------------+ 
*%%% crtrpgmod                                          
*%%%   module(%LIBO/%OBJ)                               
*%%%   srcfile(%LIBS/%FIC)                              
*%%%   srcmbr(%MBR)                                     
*%%%   DBGVIEW(*LIST)                                   
*%%%#                                                   
*%%% crtpgm                                             
*%%%   pgm(%libo/%obj)                                  
*%%%   module(*pgm)                                     
*%%%   bndsrvpgm(gevdataq gevstring)                    
*%%%   actgrp(*CALLER)                                  
*%%%#                                                   
*%%% dltmod                                             
*%%%   module(%libo/%obj)                               
*%%%&                                                   

So when I do "CP" instead of 14 or 15, (in this example) a module is
created with debug(*list), then a program is created and then the module
is removed. tle text %libo, %obj, %mbr and so on are replace by the pdm
values &N, &F ...

This technique works on any kind of program (RPG, CL), command, DDS,
UIM ...

If you are interested, email me and I could send you the sources of
this command.

Denis Robitaille
Directeur services technique TI
819 363 5187

>>> dbcerpg@xxxxxxxxx 02/20/03 03:43pm >>>
I know this has been discussed before, but a couple of searches turned
up nothing in the archives.
 (So feel free to either point me to specific archive posts or the
search terms you used.)

I am looking for an already-invented wheel that someone would be
willing to share that can be used
as a PDM option; replacements for options 14 & 15.  (I've finally had
it with not having any way
to change the command default for DBGVIEW on our dev box.)

Ideally, this would be a "smart" option, which uses &N, &F, &L, and &T,
to decide which source
member to compile, and with which command it should be compiled. 
Another parameter should handle
the preference to compile as a program or as a module.

Ideally, it would handle CLP, RPG, RPGLE, SQLRPGLE, (and more) member
types, but if what's
available doesn't have all these, I'm sure I can add the functionality
if I have something to work
off of.

TIA, Dan

__