On Sat, 25 May 2024 09:45:57 -0400, billogden wrote:
>> What you described about VSAM is what I heard too, a replacement of the
>then dominant access methods.
>>
>Wow -- I distinctly remember that goal. It really scared many of us
>(customers and IBMers) and made some of us aware of the gaps between
>"developers" and "users".
>
It is IBM's culture, when confronting a requirement, to provide an
alternative but not to generalize. For example, DSORG=PS/PO did
not meet the needs of JES so the Spool was invented, but no access
method simply treats PS/PO/Spool alike. OMVS did slightly better:
z/FS files can be allocated as if PS, and directories read (but not
written) by BPAM. And they are not supported as SYSEXEC or as
STEPLIB. And IEBGENER can't copy load modules. Not general.
TRANSMIT/RECEIVE handle PS/PO nicely, but not zFS.
This thread discussed attributes in VTOCs vs. catalogs vs.
VVDS. And OMVS, MacOS, and Linux all support some version
of "Extended Attributes". An example from Linux:
523 $
523 $ xattr -l *
example.com: user.mime_type: text/html; charset=UTF-8
example.com: user.xdg.origin.url: https://example.com/
524 $
But they're not portable and not supported by common transport
utilities such as zip.
Where should extended attributes (sometimes called metadata)
reside?
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
