*INZSR runs before the first cycle.  One can establish constants, headings,
clear files, open files, and do whatever else needs doing before the program
does any repetitive work.  Having a 'Setup' subroutine is fine of course but
it doesn't run until the first cycle starts.  I suppose some would say it is
a matter of style but the effects are not the same.  When one refuses to use
*INZSR one gives away some of RPG's power.
 
I am curious: How much impact is there when *INLR is set on repeatedly as
compared to leaving *INLR off until some end of job signal is sent?
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: 1/13/2004 8:14:53 AM
To: RPG programming on the AS400 / iSeries
Subject: RE: *INZSR - I still love you!!!
 
Hi List,
 
  I may be mistaken, haven't used it for quite a while, but isn't the *INZSR
run only at Program startup?  I generally use a 'Setup' subroutine which I
can call on my terms when a program is possibly called repeatedly.
 
Regards
 
Rick DuVall
Systems Manager
Dealer's Auto Auction of Okc, Inc.
Rick@xxxxxxxxxx <mailto:Rick@xxxxxxxxxx>
(405) 947-2886

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.