Re: Reset data
- From: "Rick Smith" <ricksmith@xxxxxxx>
- Date: Wed, 28 Feb 2007 09:27:29 -0500
"Pete Dashwood" <dashwood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:54ktfkF208kl3U1@xxxxxxxxxxxxxxxxxxxxx
"Arnold Trembley" <arnold.trembley@xxxxxxxxxxxxxxxx> wrote in message[snip]
news:BC6Fh.19799$as2.5112@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Pete Dashwood wrote:
[snip]How would the result of doing that (taking twice as much storage as you
actually need, and running the risk of forgetting to update one of the
tables when the structure changes) differ from...
INITIALIZE TABELLE ?
If you are INITIALIZE'ing a structure, the generated code will have an
explicit move for each elementary field. I know it works this way in
Enterprise COBOL for zOS.
In this case you are sayingtable
that the size of a second table will be less than all the move statements
required to initialize it, if INITIALIZE is used. So, it is the second
and a single group move, against the elemental moves required for each
element.
No! No! Size doesn't matter! It's performance that
counts! <g>
.
- Follow-Ups:
- Re: Reset data
- From: HeyBub
- Re: Reset data
- From: Howard Brazee
- Re: Reset data
- References:
- Reset data
- From: Mitch Steens
- Re: Reset data
- From: Howard Brazee
- Re: Reset data
- From: Pete Dashwood
- Re: Reset data
- From: Arnold Trembley
- Re: Reset data
- From: Pete Dashwood
- Reset data
- Prev by Date: Re: Reset data
- Next by Date: Re: Help! GO TO and PERFORM THRU!
- Previous by thread: Re: Reset data
- Next by thread: Re: Reset data
- Index(es):
Relevant Pages
|