Tom, There was a flash or something quite a while ago that explained just what to do for creating the /service directory and how to apply maintenance. I spent too long looking for it, but I can't find it now. I'm not sure if it's what you want, but I know someone sent the link to IBM-Main a year or 2 ago, and it helped me to set up correctly to do maintenance. Before I read that, I just did maintenance, and anything in the HFS was updated live. I was lucky - I never got burned.
Hopefully, someone has the link bookmarked. I thought it would be under SMP/E, but I didn't see it there. Eric Bielefeld P&H Mining Equipment On Tue, 16 Aug 2005 12:03:25 -0500, Tom Marchant <[EMAIL PROTECTED]> wrote: >How do you manage the mountpoints when applying service with SMP/E? >I am planning on discussing this at a BOF at SHARE next week, and I'd >appreciate any thoughts that you have. I have a PMR open with IBM also. > >All of the documentation simply says to mount the alternate HFS >at /service, but I don't find that to be a very adequate solution. >To me it is akin to running SMP/E with a PROC that includes DD >statements for every target data set that specifies the target volumes, >and it is asking for trouble. > >My preference is to use Automount to manage /service and set the PATHs in >my DDDEFs to /service/IPLVOL/... where IPLVOL is the first sysres for the >target zone. Automount would then mount OMVS.IPLVOL.ROOT as needed. > >In the old days, with only one HFS per target zone, this worked fine. >Now that we have other products broken out into their own HFS, it becomes >a little more complicated. > >For example, Java is designed to be mounted at /usr/lpp/java/ and the >DDDEF PATH is to be -PathPrefix-/usr/lpp/java/J1.4. Since I am automount >managing /service/ I need another place to mount the Java HFS for SMP/E. > >I set my automount policy to manage /service/mvs with the corresponding >change to the PATHs to /service/mvs/IPLVOL/.... To provide a mount point >that I can use for Java, I also manage /service/java and changed the path >to /service/java/J1.4. Unfortunately, this does not work, because when >it comes time to run AJVSCRPT, it expects the path to be of the form >-PathPrefix-/usr/lpp/java/J1.4. > >My solution to this was to create a /usr directory in the Java root. >Within that directory I created a lpp directory with a symbolic link >at /usr/lpp/java in the Java HFS. This symbolic link has a value >of "../.." (without the quotes). The result is that AJVSCRPT can >find /service/java/IPLVOL/usr/lpp/java/J1.4. This allows everything to >work. When I clone my target zone the /usr/lpp/java structure that is in >the Java HFS gets copied along with everything else. There are ZONEEDITs >to fix the DDDEF PATHs and I don't have to manually ensure that the >correct HFSes are mounted for SMP/E. > >I think that XML, Host on Demand and MQ Series have similar requirements, >but I have not spent much time investigating them yet. The PMR that I >have open is against Unix System Services, but I think it might more >appropriately be against SMP/E. The SMP/E manuals have numerous >references to /service/usr/lpp/ without giving any hint of how to manage >the mounting of the HFSes needed when applying service. I have looked >at the AJVSCRPT script and it looks to me as if the limitation of using >-PathPrefix-/usr/lpp/java is a result of the way that SMP/E calls the >script. > >Any thoughts would be greatly appreciated. > >Tom Marchant ---------------------------------------------------------------------- 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
