× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello!  

We use this quite often in interactive applications.  Typically, we will
code "one time only" (field definitions and such) in *INZSR, and create
another subroutine that initializes all other variables.  This second
subroutine is called every time the program begins.

Not setting on *INLR is of great use whenever you have one program that
repeatedly calls another since you save on the opening/closing of the
files.


Donna Zukowski
Y2K Project Manager
BIC Corporation

> -----Original Message-----
> From: Vernon Hamberg [SMTP:hambergv@goldengate.net]
> Sent: Tuesday, May 26, 1998 2:05 PM
> To:   MIDRANGE-L@midrange.com
> Cc:   egarske@cts.com
> Subject:      Re: Programming Performance
> 
> Erick
> 
> At 10:43 AM 5/26/1998 -0700, you wrote:
> >Recently, I read an article that suggested that using a return in an
> RPG
> >program would improve system performance simply by staying resident
> in
> >memory during the job stream. 
> >
> >If this is the case, would all the data areas and work variables have
> to
> >be reinitialized?
> 
> The key point here is that you have not turned on *INLR. Then your
> data,
> file cursors, etc., remain in the state they were in when you exited.
> 
> One detail: Things done in *INZSR (and initialization, as in data
> structures, I think) are not repeated when the program is called
> again.
> 
> Cheers
> 
> Vernon Hamberg
> Systems Software Programmer
> Old Republic National Title Insurance Company
> 400 Second Avenue South
> Minneapolis, MN  55401-2499
> (612) 371-1111 x480
> 
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.