|
Bill Meecham wrote :
> In an ILE environment what are you folks doing to manage the
> procedures that you have created? Do you keep all of your
> procedures in 1 service program? How do you track the names and
> what they do, with notes in the prototype file? Are you using
> modules as well as procedures in programs? Are you using modules
> in procedures?
We use several service programs, which in turn consists of one or more
modules, which in turn contains one or more procedures. The procedure
description (comment line in both prototype and code source member) should
describe (briefly) the purpose of the procedure.
After compilation we use API's to extract imports and export to
physical files. These files are used in a "where defined/used" command.
e.g.:
proc crwgetstdbyhrs
CRWGETSTDBYHRS defined in:
CRWSTATUS
Used in:
CRWBOOKED
RFOS142
RFOS151
RFOS158
RFOS159
RPDS048
We've also created a tool that reads the prototype members and displays
the input/output parameters of procedures
e.g.:
RVCS015 Display Service Program Prototypes
Service program . : FLI Flight routines
Position to . . . .
Type options, press Enter.
5=Display parameters 7=Generate prompt
Opt Procedure Description
5 FliGetLegs Get flight legs
FliGetLoadInf Get Load Information
<-snip->
More...
F3=Exit F5=Refresh F12=Cancel
RVCS016 Display Procedure Parameters
Service program . : FLI Flight routines
Procedure . . . . : FLIGETLEGS Get flight legs
Return variable . : Pointer
Parameter Len
xCompany 2
xFlNo 4
xFlDate 8 0
xIncDep 1 const options(*nopass)
<-snip->
Bottom
Press Enter to continue.
F3=Exit F5=Refresh F12=Cancel
The Generate Prompt creates "template source" line(s) for the prototype,
used by a SEU exit program to "generate" RPG source, e.g.:
C eval pRtn = FliGetLegs (xCompany : xFlNo : xFlDate
C : [xIncDep])
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.