If I recall correctly: when you create a file with the standard JVM, the
*PUBLIC data authority is *RW. But with the 32-bit JVM, it's only *R. I
tried putting a "umask" command in my script which ran the JVM, but that
didn't change the situation. (I may have the details not quite right,
this was about a year ago when I was trying out the 32-bit JVM.)
This prevented me from using the 32-bit JVM, as the code which creates
the files isn't under my control.
PC2
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: January 20, 2009 07:10
To: Java Programming on and around the iSeries / AS400
Subject: Standard vs. 32bit JVM?
Folks:
Has anyone noticed any incompatibilities between the standard and 32bit
JVM's?
Assuming no native code, I'm not expecting that there would be any ...
but thought I would throw the question out to the field anyways.
david
--
IBM i on Power Systems - For when you can't afford to be out of business
--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.
midrange.com
