<quote from Tom Marchant>
Still, the problem remains with
applications that need to have their HFS mounted at /service/usr/lpp/xxxx,
as clearly recommended in the SMP/E documentation.
It seems as if we have an SMP/E that can handle an arbitrary large number
of target zones and always access the correct target data sets through
DDDEFs, but we are expected to manually mount the corresponding HFSes for
the ROOT, JAVA, HOD, MQ, NetData, XML, and probably others.
I would not want to go back to the days of running SMP with a PROC
containing DD statements with VOL=SER=xxxxxx for every target data set.
The way I see it, the tools available for managing the system HFSes is
in a similar state.
Tom Marchant
</quote>
Tom,
What we do here, and I find the simplest, is a couple steps:
1) create a file system and mount it at /service.
2) Prefix all paths in the smp/e target zone with /service/RESVOL (where RESVOL
is the
name of your TARGET zone volume). If you have more than one target volume
for this
zone, use the first one, i.e. the one that you IPL off when testing.
3) Allocate the HFS for the target zone to contain the name RESVOL (see above)
in the
dataset name.
4) Use Unix System Services Automount facility for the /service directory, such
that whenever
you reference /service/RESVOL, it will automatically mount the proper HFS
dsn.
5) Code your BPXPRMxx member to reference the root hfs at IPL using the symbolic
&SYSR1.
This is the basic process we use, and it works great! I can be installing a
new release of z/OS,
and upgrading the current one, at the same time, no problems!
Peter I. Vander Woude
Sr. Mainframe Engineer
----------------------------------------------------------------------
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
