---------------------<snip>-------------------
I haven't tried lately, either; I'm pointing out that program
behavior, especially in the early days of OS/360, was due more to
resource constraints (coding time, transient area fits, etc.) than
intent. It would be nice if the documentation matched the code, and
every aspect of the system prevented careless or stupid errors. A
friend and I each found an SVC that returned information to an area it
did not perform an access check on, along any klutz to destroy the
system, but at least IBM fixed them when notified (though in one case
it took two tries).
And, B.D., I'm more familiar with SMP 4 than I want to be. I've
written extracts for customized reports from the directory data, and
worse still am using it for MVS 3.8 project.
---------------------<unsnip>-------------------
AFAIK, STOW has only one restriction on a member name: it can't be
8X'FF'; that's the "special value" that marks the end of the directory.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
