Re: Attribute BASED and LINKAGE SECTION
- From: "Frank Swarbrick" <Frank.Swarbrick@xxxxxxxxxxxxxx>
- Date: Thu, 29 Jun 2006 09:21:23 -0600
I can only imagine that the based item would be assigned to the new storage,
and the old storage would be orphaned unless pointed to by another based
item or a data pointer. I just can't imagine that the data should be
automatically freed (unless one traces through every other data item to make
sure its not being referred to elsewhere). I just don't see any useful
middle ground between totally manual (programmatic) de-allocation and pretty
much full-blown garbage collection.
Frank
---
Frank Swarbrick
Senior Developer/Analyst - Mainframe Applications
FirstBank Data Corporation - Lakewood, CO USA
Which still does not answer the question of whetherRoger While<simrw@xxxxxxxxxxxx> 06/29/06 7:00 AM >>>
the memory acquired by an ALLOCATE for a
BASED LINKAGE/LOCAL item is automatically reaped.
(Taking into account possibly STICKY-LINKAGE).
And what (should) happen(s) when a BASED item is
subject to more than one ALLOCATE without an intervening FREE ?
.
- References:
- Attribute BASED and LINKAGE SECTION
- From: Roger While
- Re: Attribute BASED and LINKAGE SECTION
- From: Frank Swarbrick
- Re: Attribute BASED and LINKAGE SECTION
- From: Michael Wojcik
- Re: Attribute BASED and LINKAGE SECTION
- From: Roger While
- Attribute BASED and LINKAGE SECTION
- Prev by Date: Re: Attribute BASED and LINKAGE SECTION
- Next by Date: Simple? DISPLAY Question
- Previous by thread: Re: Attribute BASED and LINKAGE SECTION
- Next by thread: Re: Attribute BASED and LINKAGE SECTION
- Index(es):
Relevant Pages
|
|