RE: *INZSR Issue

This quote, however is only when you use that ill-advised technique that IBM
introduced prior to "real" subprocedures. This technique allows you to bind
to separately compiled RPG IV source member, which may have previously been
independent programs, together. Then you replace a previous CALL with a
CALLB to the "module". You're actually calling the main procedure or "entry
procedure" of that module. Effectively you're starting up the RPG cycle
which is a PIG and hence loosing any performance advantage you might have by
using CALLB over CALL.


Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Marco Facchinetti
Sent: Wednesday, May 14, 2003 6:59 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: *INZSR Issue

This is from RPG reference:

"There is no *INZSR associated with subprocedures. If a
subprocedure is the first procedure called in a module, the
*INZSR of the main procedure will not be run, although
other initialization of global data will be done. The
*INZSR of the main procedure will be run when the main
procedure is called."

> Within
> that subprocedure is an *INZSR routine.  It compiles just
> fine.
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.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.