On 05/06/2013 08:58 AM, John McKown wrote:
Or maybe just for a PDSE since PDSes are basically moribund.
This is just a weird thought, feel free to call me an idiot. But there are
two "classes" of members in a PDS at present. There are normal member and
there are ALIASes. It generally seems that an ALIAS does not contain a TTR
per se, but actually contains the actual member name. Am I remembering
correctly? If so, then why not extend the ALIAS concept (a member name
which points to another member name) to a new class of member, which I will
call a CONCAT member. This is a member name which contains multiple member
names, perhaps in the user data area. When you OPEN a CONCAT member for
reading, what you get is the contents of all the members listed in the
order listed.
No, I can't think of a reason why this should be over a standard
concatenation of DD statements. But I've only had a few hours sleep per
night for the past week and so my mind is misfiring.
The format of an "alias" directory entry does contain the actual TTR for
the member, as well as the "main" member name (from the time the alias
was created), and the alias entry TTR was the TTR used to access the
data. One of the weird, confusing things that used to be possible,
either deliberately or by accident, was that one could end up with an
"orphaned" (but still functional) alias entry that pointed to a
different TTR and data than the TTR in the then-current entry for the
main member name.
--
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
