Re: Properties init: Could not determine current working directory.

Hi David, the error is here:

* If systemProperties is unset, then create a new one based on the values
* provided by the virtual machine.

So I suspect the Jvm has no means to resolve CCSID to convert CCSID byte
array for parms:

Controlling how the Java Virtual Machine is set up
When RPG starts the Java Virtual Machine (JVM), there are several options
that control how the JVM is
started. See the Java System Properties section in the IBM i Information
Center.
• You can place these options in the SystemDefault.properties file.
• You can use the CLASSPATH environment variable to specify the classpath
(see above).
• You can place these options in an environment variable called
QIBM_RPG_JAVA_PROPERTIES. Any
options placed in this environment variable will override the options in
the SystemDefault.properties
file. If you specify the java.class.path option in this environment
variable, and you also specified the
CLASSPATH environment variable, it is undefined which value will take
precedence for the classpath.
To specify options in the QIBM_RPG_JAVA_PROPERTIES environment variable,
you code the options in
a string, one after the other, separated by any character that does not
appear in any of the options. Then
you end the string with the separator character. For example, if you want
to specify the options
java.version=1.4
os400.stderr=file:stderr.txt
then you would add the environment variable using the following command:
ADDENVVAR ENVVAR(QIBM_RPG_JAVA_PROPERTIES)
VALUE('-Djava.version=1.4;-Dos400.stderr=file:stderr.txt;')
If the options string is not valid, Java may reject one of the options.
Message JVAB55A will appear in
the joblog indicating which option was not valid. If this happens, RPG will
try to start the JVM again
without any of the options, but still including the java.class.path option
if it came from the CLASSPATH
environment variable.
Some parameters and return values require conversion between the job CCSID
and the CCSID that
Java uses for byte arrays. The file.encoding Java property is used by RPG
to obtain the CCSID
that Java uses. Ensure that the file.encoding property is set correctly for
your job CCSID. You can
allow Java to set the property implicitly using attributes of your job, or
you can set the property
explicitly using one of the mechanisms above. For example, you could add
'-Dfile.encoding=ISO8859_1'
or '-Dfile.encoding=Cp948' to your QIBM_RPG_JAVA_PROPERTIES environment
variable. For more
information about the file.encoding property, see the IBM Developer Kit for
Java topic in the Information
Center.
For more information about the properties you can specify to control the
Java virtual machine,
and other environment variables that may be required for Java to operate
correctly, such as the
QIBM_USE_DESCRIPTOR_STDIO environment variable, see the see the IBM
Developer Kit for Java topic
in the Information Center. You may also need to consult the documentation
for the specific Java classes
that you will be using.

HTH
--
Marco Facchinetti

Mr S.r.l.

Tel. 035 962885
Cel. 393 9620498

Skype: facchinettimarco


Il giorno ven 9 gen 2026 alle ore 20:13 David Gibbs via JAVA400-L <
java400-l@xxxxxxxxxxxxxxxxxx> ha scritto:

On Fri, Jan 9, 2026 at 1:01 PM Marco Facchinetti <
marco.facchinetti@xxxxxxxxx> wrote:

Make sure that *PUBLIC has at least *RX authority to the following
directory paths:
/QIBM/ProdData/OS400/Java400/jdk/lib/
/QIBM/ProdData/OS400/Java400/jdk/lib/ext/
/QIBM/ProdData/Java400/jdk11/lib/ext/

Those three directories don't exist on either of our systems.

The others all have at least *RX.

QIBM_MULTI_THREADED = 'Y'

Neither system has that environment variable set at the *SYS level.

/QOpenSys/QIBM/ProdData/JavaVM/jdk17/64bit/conf/security/java.policy

Both systems have that file and they are identical.

Is there a possibility that the JVM was already in error before the Java
class was executed in your RPG?

I don't think so ... the JVM is initialized, but fails about half a second
later.

Here's the fragment of the job log showing the error:

JVAB302 Diagnostic 10 01/09/26 07:42:19.694378
QJVAUTLJVM QSYS *STMT QJVAJVMXIF QSYS *STMT
From user . . . . . . . . . :
XXXXXXXX
From module . . . . . . . . :
QJVAUTLJVM
From procedure . . . . . . :
JvaSendMsg
Statement . . . . . . . . . : 10
To module . . . . . . . . . :
QJVAJVMXIF
To procedure . . . . . . . :
sendMessage__10QjvaJvmXifFPcPviT1
Statement . . . . . . . . . : 1
Thread . . . . : 00001E1D
Message . . . . : Java Virtual
Machine is IBM Technology for Java.
PID(3832342)
Cause . . . . . : JAVA_HOME
environment variable is

/QOpenSys/QIBM/ProdData/JavaVM/jdk11/64bit
MCH74A5 Escape 40 01/09/26 07:42:20.117156
QXJ9UTLJVM QJVM1164 *STMT QXJ9UTLJVM QJVM1164 *STMT
From user . . . . . . . . . :
XXXXXXXX
From module . . . . . . . . :
QXJ9UTLJVM
From procedure . . . . . . :
JvaSendMsg
Statement . . . . . . . . . : 16
To module . . . . . . . . . :
QXJ9UTLJVM
To procedure . . . . . . . :
JvaSendMsg
Statement . . . . . . . . . : 16
Thread . . . . : 00001E1D
Message . . . . : The Java Virtual
Machine has ended.
Cause . . . . . : Java Virtual
Machine 1 has ended because of reason 2. The
reason codes are defined as follows:
01- A Java program called the
java.lang.System.exit method with a
zero status code. 02- A Java program
called the java.lang.System.exit
method with a non zero status code of 1.
03- An unexpected system error was
detected. 04- A critical Java Virtual
Machine thread has ended and
processing cannot continue. Recovery . . . :
If the Java Virtual Machine ended
because of reason code 03, an internal
error has occurred. Contact you
service representative. Information about
the error was saved in the Licensed
Internal Code log.
JVAB544 Diagnostic 40 01/09/26 07:42:20.117357
QXJ9UTLJVM QJVM1164 *STMT QRNXUTIL QSYS *STMT
From user . . . . . . . . . :
XXXXXXXX
From module . . . . . . . . :
QXJ9UTLJVM
From procedure . . . . . . :
JvaSendMsg
Statement . . . . . . . . . : 16
To module . . . . . . . . . :
QRNXJNI
To procedure . . . . . . . :
_QRNI_getJNIEnv
Statement . . . . . . . . . : 75
Thread . . . . : 00001E1D
Message . . . . : Unmonitored
exception received.
Cause . . . . . : Received an
unmonitored exception. Recovery . . . : See
the messages listed on this display
or in the job log (use the DSPJOBLOG
command to display the job log).
Correct any errors and try the command
again.
MCH3601 Escape 40 01/09/26 07:42:20.117744 QRNXUTIL
QSYS *STMT QRNXUTIL QSYS *STMT
From user . . . . . . . . . :
XXXXXXXX
From module . . . . . . . . :
QRNXJNI
From procedure . . . . . . :
_QRNI_getJNIEnv
Statement . . . . . . . . . : 95
To module . . . . . . . . . :
QRNXJNI
To procedure . . . . . . . :
_QRNI_getJNIEnv
Statement . . . . . . . . . : 95
Thread . . . . : 00001E1D
Message . . . . : Pointer not set
for location referenced.
Cause . . . . . : A pointer was
used, either directly or as a basing
pointer, that has not been set to an
address.
--
This is the Java Programming on and around the IBM i (JAVA400-L) mailing
list
To post a message email: JAVA400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.