In a recent note, McKown, John said:
> Date: Mon, 23 Apr 2007 10:08:51 -0500
>
> >
> > Not all systems that can write tape that is sent to a mainframe
> > (specifically, z/OS) write labels. It may be an application design
> > issue, but never-the-less, it happens.
>
> Like many Windows and Linux systems. It can be done, but it is a "pain"
> so they usually don't want to be "bothered" with it.
>
Compound this "bother" with overseas outsourcing of software development for
then Windows/Linux system, with attendant complexity of testing and debugging,
and outsourcing to a different vendor of media production.
And the problem, to which I still know no good solution, of conflict of the
volser with a local name. Instruct the customer to BLP and adjust the
supplied JCL accordingly (or supply JCL in two versions, the second for BLP)?
I still wish that either IBM or SHARE would declare a small range of volsers
as reserved for interchange. Then we could stay in that range and tell the
customer, "Your problem." (I know, one can never do that.)
I'm pretty satisfied with the way OS X deals with the equivalent problem.
If I mount two identically labelled volumes, the OS mounts them at different
mountpoints, generating a name for the second:
505 $ ls -ald /Volumes/UNIX*
drwxr-xr-x 5 paulgilm staff 1024 24 Mar 13:30 /Volumes/UNIX FS
drwxr-xr-x 5 paulgilm staff 1024 24 Mar 13:30 /Volumes/UNIX FS 1
Equivalent would be to tell z/OS, "Here's what the physical label is;
here's what I want the application to see in the UCB instead."
And, I wish z/OS supported volsers _much_ longer than six characters. Then
a vendor could incorporate a registered trademark in product volsers and
let the USPTO moderate conflicts.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
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
