RE: Command Parameter Question

[Mike.Collins@xxxxxxxxxx]

If your original CPP was an RPG program to which you had access to the
source, then I would say don't create a CL just for the sake of it, but
change the values in the initial subroutine of the RPG. In my product, the
CLs actually do various things that are best done in CL programs, eg
changing logging levels, so we always have an arrangement of a command
linked to a CL CPP, which normally calls another RPG. We don't actually
bind any modules together. As for naming conventions, the actual source
member used to create the command, is not the same name as the command
itself, as we use a precompiler to create the command with the correct
name. All the programs related to the command, then use the same first six
digits as the command source member, followed by a suffix related to the
type of program they are, eg

command source name - I@S010Z - actually creates command IWRKJOBFIL
CL CPP - I@S010C, which calls RPG program I@S010R
CL CVC - I@S010V, which calls RPG program I@S010RV
Help panel group - I@S010ZH

etc etc

So basically if you want to know all the related programs for command
IWRKJOBFIL, the DSPCMD will give you the command source member, and then
everything else is easily derived.

I guess that standard probably isn't appropriate for your site though, but
I can't see why you couldn't follow your idea of binding the modules in the
way you suggest.