Re: Plain old RPGLE program in /Free

Pete,
Here's how I usually do it.

* Entry Parameters
D entryParms PR ExtPgm('YOUR_PROGRAM_NAME')
D myParm 8a const
D entryParms PI
D myParm 8a const

...


Hope this helps.
James R. Perkins



Pete Helgren <Pete@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
22.10.2007 08:41
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Plain old RPGLE program in /Free







I was feeling pretty comfortable with my transition from RPGIII to RPGLE
and /free until I needed to write a program from scratch that wasn't
using *ENTRY to pass parms to the program. I must not understand the
differences between the way RPGIII passed parameters and the way RPGLE
operates.

What I have been doing (cheating) was to have a short, initial non-free
calculation section like this:

C *ENTRY PLIST
C PARM MyParm
C/free

What I want to do is to do it "correctly". So after poking around the
Internet I thought I came up with the solution:

D Main PR
D 8A
D*********************************************************
D*Main Procedure
D*********************************************************
P Main B
D PI
D MyParm 8A
C/free
// Body of the program here

It wouldn't compile until I used dftactgrp(*no) actgrp(*caller) on the H
specs.

Although it compiles, when I run it in debug mode, the program is
invoked but "hangs" at the command line, it never progresses to the
first statement of the program which is where I have my breakpoint set.

So the question is: What is the correct way to write a simple program
in RPGLE that takes parameters? What do I do with the *ENTRY PLIST
method of passing parameters? I could go back to using the *ENTRY PLIST
approach but I'd like to use the "correct" way, if there is such a
thing...

Thanks,

Pete Helgren