jzos-1.1.2 - S0C4 running job run13 sample

ronmck · Post by **ronmck** » Thu Mar 17, 2005 11:47 pm

Our operating is OS/390 2.10 with ACF2, when I run job run13 it fails with
CEE3204S The system detected a protection exception (System Completion Code=0C4
From entry point JNIEnv_::ExceptionOccurred() at compile unit offset +2A2F8C20 at address 500000B0

I ran job RUNINV13 without any problems.

Post by **coz** » Fri Mar 18, 2005 9:40 am

This may be a region size issue. If you run the job with LOGLVL='+I', and post the results here (or send to dev@jzos.com), we can take a look.

Post by **dovetail** » Fri Mar 18, 2005 11:57 am

Also check the PTF levels of Java and LE. There are lots of problems with earlier versions of SDK 1.3.1 related to JNI. (The S0C4 seems to be in a Java JNI function).

Post by **dovetail** » Mon Mar 21, 2005 6:30 pm

I'm very sorry, but the problem that you are having is -completely- our fault.
When we first posted version 1.1.2, we had a rather nasty bug in the sample JCL. (We had found and fixed the problem in our actual JCL, but forgot to update the shipped sample JCL.... we have since corrected the sample JCL in the 1.1.2 build)

I didn't realize that that was your problem until I saw the trace output.

The fix is very simple... the sample JCL should set the PATH and LIBPATH variable like this:

export PATH=/bin:"${JAVA_HOME}"/bin:

LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic
LIBPATH="$LIBPATH":"${JZOS_HOME}"
export LIBPATH="$LIBPATH":

Note: this applies to both 1.3 and 1.4 users. If you were unfortunate enough to download the 1.1.2 build in the first few days that it was available, you will need to either get it again or patch the sample JCL to correctly set the PATH and LIBPATH variables.