|
Message: 8 Date: Wed, 14 May 2003 04:59:12 -0700 (PDT) From: Marco Facchinetti <facchinetti@xxxxxxxxx> 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." ...sigh... I wish that the thread would be *read* fully before people start in on why it's wrong, wrong, wrong. What I said earlier was that I'd looked through the manuals and couldn't find any text that explicitly said, "Thou shalt NOT put an *INZSR inside a subprocedure." The above says that you *CAN*, but the *INZSR doesn't behave as expected. Bob Cozzi posted that it can't be done because of the cycle. I agree. Makes perfect sense; a subprocedure doesn't follow the cycle. Buck went so far as to write a non-SQL dummy module, and that blew up. What I want to know is: why does my stinking module compile, and theirs don't. That's all. Oh, well, something to research as time permits. -Doc __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.