RE: ExtProc() keyword confusion

In my Definition specification session I do when I'm doing on-site training
at clients... I have a final page that has the following example of a long
procedure name:

DName+++++++++++EUDS.......Length+TDc.Functions+++++++++++++++++
D TheseAreTheTimesToRemember...
D CauseTheyWillNotLastForever...
D TheseAreTheDaysToHoldOnTo...
D CauseWeWontAlthoughWellWantTo...
D                 PR                   ExtPgm('QCMDEXC')

You have to be a fan of Billy Joel to get the joke.


-Bob Cozzi
www.RPGxTools.com
If everything is under control, you are going too slow.
- Mario Andretti


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Christen, Duane J.
Sent: Friday, July 08, 2005 1:50 PM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: ExtProc() keyword confusion

You could use a short story as a procedure name, IIRC a procedure name can
be over 4000 characters.



-----Original Message-----
From: Tony Carolla [mailto:carolla@xxxxxxxxx]
Sent: Friday, July 08, 2005 12:23 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: ExtProc() keyword confusion


On 7/8/05, Bob Cozzi <cozzi@xxxxxxxxx> wrote:
> 
> That's what the prototype name is for--to allow you to use whatever name 
> you
> want inside the RPG IV program regardless of the true name of the 
> procedure
> you're calling.
> 
> D MyBigAssLongProcName...
> D PR ExtProc('GetTBatchPats')


I get it. I haven't tried any long names as of yet -- it turns out that 
GetTBatchPats doesn't even need the '...'

Thanks. 

ps. Perhaps I should have named it:

D MyBigFatGreekProcedureName...