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)      ??

What am I missing?   Please share your experiences either on/off list is fine.  
 Just looking to learn from others and be able to implement general best 
practices BEFORE the masses hit the systems.

Thanks, Dave

_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
[email protected]
1830 East Paris, Grand Rapids, MI  49546 MD RSCB2H
p 616.653.8429
f 616.653.2717

This e-mail transmission contains information that is confidential and may be 
privileged.
It is intended only for the addressee(s) named above. If you receive this 
e-mail in error,
please do not read, copy or disseminate it in any manner.  If you are not the 
intended 
recipient, any disclosure, copying, distribution or use of the contents of this 
information
is prohibited. Please reply to the message immediately by informing the sender 
that the 
message was misdirected. After replying, please erase it from your computer 
system. Your 
assistance in correcting this error is appreciated.




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to