RE: Complier is not recognize CALLP with procptr array

that work.  Thanks everybody.

Question:  If those procedures are all in-line procedures.  Would this dynamic 
call cause performance issue?

-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@xxxxxxxxxxxxxx]
Sent: Thursday, May 29, 2003 4:54 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Complier is not recognize CALLP with procptr array


 >> why is complier not able to recognize that factor 2 on 'CALLP
genChgA(ix)' statement is an array of procptr? ......Complier error:
*RNF5410 30     21 006150  The prototype for the call is not defined.

I suspect that you are really confused here as to how CALLP and proc
pointers work.  I am guessing that you intend that the call _target_ be
identified by a procptr. In which case you are just going about it the wrong
way.

No matter what, the answer is that you can't use CALLP without defining a
prototype - and I don't see one in your source.

IF you want to have a dynamic call via procedure pointer then the prototype
should be something like this:

      // Notice no 'quotes round the procedure name in the next line
     D CallProc        Pr                  ExtProc(ProcToCall)
     D   Parms go here if you have any

     D   ProcToCall                     *   procptr
      // Set up procedure pointer for call
       ProcToCall = genChgA(ix);
      // And call it
       CallProc( parms go here);

If I haven't guessed correctly you're going to have to be more explicit.


Jon Paris
Partner400
www.Partner400.com

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.