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



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.








As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.