RE: Calling Program with a Procedure Interface

[Buck Calabro <Buck.Calabro@xxxxxxxxxxxx>]

John M. Bauman wrote:

>OK, I am thoroughly confused now.  What I want
>to do is perform a call from one program to
>another.

The example I posted will allow you to do just that.  You can call AG07 from
another program like the command line.

>I don't want to define a procedure.
>I thought in RPG IV we are supposed
>to use the 'PI' to replace the *ENTRY
>PLIST.  Can someone make this easy for me? (Ha)

PR is defining a procedure.  Basically, it is calling the entire program a
procedure.  Here's where the vocabulary gets in the way.  When you say 'I
don't want to define a procedure' you really mean 'I don't want to define a
subprocedure.'  That is, you don't want to define a new procedure internal
to the callee program to be used by other processes, all you want to do is
replace the *ENTRY with 'PR'/'PI'.  So, yes you DO want to define a
procedure.  You just don't want to define a subprocedure!  Isn't vocabulary
grand?


David Rittenberg wrote:

>How do you bind the module to the other source?

You don't.  OPM can't bind.  Envision calling AG07 from another RPG program.
You'd specify the 'PR' specs and a callp:

dmain             pr                  extpgm('AG07')
d numberIn                      15p 5
c                   callp     main(someNumber)
  --buck

"This box Rocks!" - related to 2002 NE IBM
Conference attendees by IBM's Stephanie Joy