×
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.
Sorry if this has been mentioned and I missed it but I find it helpful to
include a comment with "*ENTRY" as Aaron did.
I make this a comment near the /COPY statement as well.
That way anyone searching for *ENTRY will also find the prototype.
hth
Dave B
"albartell" <albartell@xxxxxxxxx> 05/18/07 8:29 AM >>>
I was thinking the same thing. I know how to do it for subprocedures, but
not for "main" programs.
Just wrote this program yesterday. This shows how to use prototypes vs. the
traditional way. I simply put this in the global area of my program. I
don't think you need to use extpgm keyword if you name the pr and pi the
same as the pgm object, but I am not sure on that. I just always use
extpgm.
// Prototype for this program (same purpose as *ENTRY and/or PLIST)
D HTLRES pr extpgm('HTLRES')
D ppXMLFile 50a
D HTLRES pi
D ppXMLFile 50a
Then you call it like you normally would:
CALL PGM(MYLIB/HTLRES) PARM('/rxs/contract/abccompany/hotelres.xml
')
The thing that drives me nuts is you have to pad the call parms with spaces
(even in WDSC's debugger).
HTH,
Aaron Bartell
http://mowyourlawn.com
midrange.com
