Our philosophy has always been to leave the 19E/Y-disk for IBM. 3rd
Party and homegrown "public" tools were put on our "P-disk" (public),
19A at MSU. A hook into SYSPROF accessed this for all users.
(Sysprog tools were on a separate disk, as are Ops-only tools) Accessing
our public disk at P meant that it was searched prior to the S or Y, so
that we could put "cover" Execs and the like on it. Some tools (certain
compilers and database software --- things with lots of individual
files) were kept on their own disks, with front-end wrappers placed put
on our P-disk to Link/Access/Execute those tools. These wrappers were
1-liner execs which called a generic "table-lookup/link/access" tool,
also on our P-disk.
Thus when changes we needed to the "wrappers" they could be done in a
single executable.
Stephen Frazier wrote:
The answer is yes. A tool that is only needed by a few would be placed
on its own mini-disk and linked to by those who need it. A tool that
is used by almost everyone is placed on the Y disk so everyone has
access to it all the time.
[EMAIL PROTECTED] wrote:
What is the best practice for installing tools into the z/VM space?
1. Do you create a mini-disk for each tool and have everyone who
needs it link to that disk for the time needed to use the tool?
2. Do you create a common mini-disk that is accessed by every user?
(in z/OS I would put the tools into their own libraries and then put
those libraries into the linklist if everyone needed access or
provide information on how to steplib for those infrequent uses).
Thanks (and please forgive the mention of z/OS)
