On 01/20/2012 08:54 AM, Paul Gilmartin wrote:
On Thu, 19 Jan 2012 17:37:12 -0600, Joel C. Ewing wrote:
On 01/19/2012 02:55 PM, Paul Gilmartin wrote:
On Thu, 19 Jan 2012 11:09:27 -0800, Schwarz, Barry A wrote:
Someone might be failing to issue a DISConnect or RELEASE.
(It's not at all clear to me why this problem shouldn't occur similarly
with a classic PDS.)
...
How could this be an issue with the classic PDS? Surely the "connection
to members" concept doesn't exist for a traditional PDS, as old member
data can only be eliminated by completely reorganizing, compressing the
PDS. With no re-use of deleted-member space, there is no need for a
special mechanism to prevent over-write of a deleted member while some
other task is still reading the now-deleted version of the member.
The issue reported by the OP wasn't that a member was
overwritten; the issue was that the data set ran out of space.
Not really. The context of "this problem" in "It's not clear to me why
this problem..." was a discussion of member disconnect or release, and
the original problem that started the thread was more along the lines of
why isn't deleted space for a LNKLST PDSE library being freed and and
available for reuse, even after an LLA REFRESH, as one would expect,
rather than why is the data set out of space (which would have been
obvious for a PDS that hadn't been compressed).
JC Ewing
Conceptually, any user who has done a BLDL and saved the TTR
has a connection to the member. PDSE merely formalized the
process.
-- gil
...
--
Joel C. Ewing, Bentonville, AR [email protected]
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
