RE: external subprocedures setting on LR: performance impact?

> From: Dan
>
> Is this a no-brainer?  If I remove the LR from being set on, and
> just issue a Return, won't the
> files stay open until the job ends?  (This is a batch job.  And
> there are no USROPNs on the
> files.)

Batch jobs make this pretty easy.  However, if you wanted to do the same
thing even in an interactive job, you can compile the top program as
ACTGRP(*NEW) and all the called modules as ACTGRP(*CALLER).  When the top
program ends, it will clear all the called programs.  Very slick.


> The only things I think I need to watch for is to determine
> whether any *INZSR stuff needs to be
> moved out so that it runs on each invocation.  And also any
> working fields that are expected to be
> in a "cleared" state at the beginning of each invocation, I will
> need to explicitly clear those.
>
> Anything else?

Remember that your file pointers will not be changed.  If you expect files
to be at the beginning, you'll be unpleasantly surprised.  EOF conditions
don't get magically reset by subsequent calls.

Remember also that indicators are working fields.  If your programs still
use indicators to condition logic (horrors! <grin>), be sure they're all
cleared to *OFF before you begin.  MOVEA *ALL'0' *IN works quite nicely,
despite its lack of elegance.

HTH

Joe