Re: inter subprogram in initial state, but only sometimes
- From: "Richard" <riplin@xxxxxxxxxxxx>
- Date: 28 Dec 2005 14:52:51 -0800
Frank Swarbrick wrote:
> >What does cancel achieve that a few moves and closes would not ?
>
> Well, if you have a lot of VALUE clauses in your working storage
> definitions, then there would but quite a lot of moves. It would be nice
> just to let the COBOL runtime do it.
The VALUE clauses may be for values that will not change - eg report
headings or lookup tables of rates - or they may be just zero or space
as starting values and an INITIALISE may do the trick, it may be that
organizing the data items into unchanging, initializable, and 'other'
may make it less than 'a lot of moves'.
Most of my programs are dynamic in that they are mostly cancelled when
they exit program, but they claen up before exiting and don't rely on
being a fresh when entered - they check using a WS flag whether they
have been reloaded, even the ones that expect not to be canelled ever.
.
- References:
- inter subprogram in initial state, but only sometimes
- From: Frank Swarbrick
- Re: inter subprogram in initial state, but only sometimes
- From: Richard
- Re: inter subprogram in initial state, but only sometimes
- From: Frank Swarbrick
- inter subprogram in initial state, but only sometimes
- Prev by Date: Re: religion
- Next by Date: Re: inter subprogram in initial state, but only sometimes
- Previous by thread: Re: inter subprogram in initial state, but only sometimes
- Next by thread: Re: inter subprogram in initial state, but only sometimes
- Index(es):