On Oct 31, 2012, at 9:48 AM, Jousma, David wrote:
All,
Looking for some feedback - publications, real world experience,
etc on managing the z/OS environment to support JAVA application
development in our shop. Up until now, JAVA has been a service
provider for systems level(and controlled) functions.
A couple things come to mind immediately that have never been a
real concern before, and maybe are a pipe dream:
1) Unix Systems Services for the masses - today no one outside
of tech services can get to unix command prompt. I suspect
developers will need their own filesystems, etc. Don't want to
make it complicated or require a lot of administrative overhead.
Security?
2) Isolating JAVA release levels from applications. Is this
possible? We tend to keep several versions of JAVA available(1.4,
5,6, and 7) but make the most current, the "default" as in the path
in JAVA_HOME. What I don't want is applications coding for
specific versions(if possible) causing upgrade nightmares.
3) Shared file systems. Today we do not share filesystems for
read/write across the lpars in our sysplex. We share sysres
filesystems readonly. Filesystems for write access are system
specific today.
4) ??
For #4 do not forget to take back up and recovery into the mix. For
most shops (That I have seen) its a major issue and the only way to
fix it is with $$$.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
