Hello Mark ,
Thanks a lot for your inputs..... It really helps !
Regards,
baby
On Thu, Aug 22, 2013 at 6:54 PM, Mark Zelden <m...@mzelden.com> wrote:
> On Thu, 22 Aug 2013 00:46:26 +0530, baby eklavya <baby.ekla...@gmail.com>
> wrote:
>
> >Hello Everyone ,
> >
> > Apologize in advance for this dumb question .
> >
> > I have a requirement to put some maintenance on Java filesystem which is
> >currently mounted on a shared sysplex root .We have 4 lpars (including the
> >sandbox) in same sysplex sharing the root file system . My customer wants
> >to test the change on sandbox system before i roll out on other lpars.So ,
> >it just looks as below
> >
> >/JAVA64 => OMVS.JAVA64.ZFS
> >
> >I thought of taking a copy of OMVS.JAVA64.ZFS with a different name and
> >mount it on a newly created mount point (such as /JAVA64T) for sandbox
> lpar
> >specifically . But i am not sure who all would be still looking for the
> >original mount point /JAVA64 . Is there any way i can test it specifically
> >for sandbox lpar without disturbing the other 3 lpars ?
> >
> >Any help would be much appreciated
> >
> >Thanks in Advance,
> >Baby
> >
>
>
> There's almost no point in applying maintenance to Java. A single PTF
> replaces the
> entire contents. Just download / install whatever level you need. You
> can still
> use SMP/E if you desire, but I don't bother for the reason I just sited.
> <soap box> SMP/E is a tool to keep track of maintenance and keep you (or
> the
> vendor) from shooting yourself in the foot. It does nothing in regards
> to that
> for Java. </soap box>
>
> To test, just create a different mount point and have whatever user /
> process
> that needs it set JAVA_HOME when they login or use .profile or create a
> script or do "whatever" it takes to set the environment variables for
> the software / user that needs it.
>
> The example below is in my /etc/profile and is where I have 31bit Java V6,
> but you can change JAVA_HOME to whatever mount point you create / mount
> your new level. BTW, you may be able to tell from my example
> that I keep a "system level" Java as part of the "version" sysres set,
> so if I change the level, it goes in with rolling IPLs and nothing
> is disturbed in the rest of the sysplex.
>
>
> # ==========================
> # Start Java Definitions =
> # ==========================
>
> JAVA_HOME=/usr/lpp/java/J6.0
>
> export JAVA_HOME
> export PATH=$JAVA_HOME/bin:$PATH
> export DISPLAY=<hostname>:0.0
>
> LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/
> LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
> export LIBPATH="$LIBPATH":
>
> # ==========================
> # End Java Definitions =
> # ==========================
>
> --
> Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
> mailto:m...@mzelden.com
> Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
> Systems Programming expert at http://expertanswercenter.techtarget.com/
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
