New version of JZOS - 1.2.4 now available at IBM Alphaworks

Post by **dovetail** » Fri May 19, 2006 4:01 pm

See: http://www.alphaworks.ibm.com/tech/zosj ... k/download

This version includes fixes for BPXWDYN, which was broken in -some- environments. Also included are fixes to the LE runtime options so that they match the java command line launcher.

orr94 · Post by **orr94** » Mon May 22, 2006 9:34 pm

Do you know if version 1.2.4 fixes the problem with ZFile.exists()?
The problem was discussed in a previous thread on this forum

http://dovetail.com/forum/viewtopic.php?t=227

The Change History in the download does not address it.

Post by **dovetail** » Mon May 22, 2006 9:45 pm

Sorry....the ZFile.exists() method still does not support PDS members.
However, you should look for this feature (and more) in an upcoming release.

I can't elaborate any more than the IBM announcement:

"IBM intends to integrate JZOS technology into its SDK for z/OS, Java 2 Technology Edition products in 2006."

(from:)
http://www-03.ibm.com/servers/eserver/z ... press.html

christianstrauer · Post by **christianstrauer** » Sat Jun 03, 2006 5:51 am

Does this new version also fix the problem of the 100 character limitation for LE options under a z/OS 1.6?

Post by **coz** » Sat Jun 03, 2006 6:46 am

No - this is still a z/OS limitation.

From the way you've worded your question, this probably won't help, but under z/OS 1.7 (and later) you can use the new CEEOPTS DD statement.

christianstrauer · Post by **christianstrauer** » Sat Jun 03, 2006 9:50 am

Too bad

BPXBATCH had the same problem, but a colleague of mine told me that in the newest PTF level of BPXBATCH this problem was solved. Do you know how they did that?

Post by **coz** » Mon Jun 05, 2006 9:57 am

The BPXBATCH APAR doesn't address this problem - you still can't put more than 100 characters of LE options in PARM=, and the new STDPARM DD that can be specified for BPXBATCH can't be used for this purpose. FWIW - here's the link to the features added by the BPXBATCH APAR:

http://publibz.boulder.ibm.com/cgi-bin/ ... 0602070819

We've discussed this, and have a couple of suggestions:

1.) If your total LE options length is less than 100 characters, you can specify all of them with the PARM= value. Then, you can specify program parameters with the JZOS_MAIN_ARGS environment variable and/or the JZOS_MAIN_ARGS_DD.

If your total LE options length is more than 100 characters, you can either:

2.) Relink the JZOS load module, replacing the CEEUOPT CSECT with the runopts that you need.

3.) (not guaranteed to work, but worth a try): Use the ENVAR LE option in combination with _CEE_ENVFILE and _CEE_RUNOPTS to specify your options. The sample JCL would look something like this:

//JAVA EXEC PROC=EXJZOSVM,VERSION='50',
// JAVACLS='com.ibm.jzos.sample.HelloWorld',
// PARM='ENVAR("_CEE_ENVFILE=DD:ENV")/'
//ENV DD DSN=MY.RUNOPTS,DISP=SHR

Where MY.RUNOPTS would contain an entry of the form:
_CEE_RUNOPTS='run time options'

christianstrauer · Post by **christianstrauer** » Mon Jun 19, 2006 9:17 am

When trying to relink the JZOS load module, we get an Abend 0C1.

Can you tell me the link options for relinking?

Post by **dovetail** » Mon Jun 19, 2006 1:53 pm

The JZOSVMxx load module for alphaworks V1.2.4 is linked with these commands:

LMLFLAGS = "-W l,COMPAT=MIN"
LMOBJS = JzosVM.o adoptEnv.o JniUtil.o ZLog.o
SIDEDECKPATH = $(JAVA_HOME)/bin/classic

c++ -o "//'$(LOADLIB)($(PROGNAME))'" $(LMLFLAGS) $(LMOBJS) $(SIDEDECKPATH)/libjvm.x

You should be able to get a map and detailed options report by running the loadmodule through the linker/binder.

christianstrauer · Post by **christianstrauer** » Tue Jun 20, 2006 6:59 am

Steve, thank you!

For your information: We have found another method to solve the 100 character limitation.

Just put in the following export statements in the JCL:
export _CEE_RUNOPTS="HEAPP(ON)"
export _CEE_RUNOPTS="${CEE_RUNOPTS}"",ALL31(ON)"
export _CEE_RUNOPTS="${CEE_RUNOPTS}"",RPTSTG(OFF)"
export _CEE_RUNOPTS="${CEE_RUNOPTS}"",RPTOPTS(OFF)"
export .....

Works fine

Post by **dovetail** » Tue Jun 20, 2006 11:53 am

Christian,

Have you verified that this works? What happens if you set RPTOPTS(ON) this way.... are your other options set in this manner in effect when the program completes?

Its more than a little confusing to me, since these options don't get set until after the program starts, which the way that I understand it, is too late.

Its great if it works, but it breaks my conceptual model for how LE runtime options work

Kirk

Post by **dovetail** » Tue Jun 20, 2006 11:55 am

Also, I'm curious... what LE runtime options do you find that you need to set in your environment?

Are you using the 1.2.4 alphaworks release (it fixes the default options to match the java command launcher)

christianstrauer · Post by **christianstrauer** » Wed Jun 21, 2006 4:13 am

Sorry, there was a misspell, but now it works:

export _CEE_RUNOPTS="HEAPP(ON)"
export _CEE_RUNOPTS="${_CEE_RUNOPTS},ALL31(ON)"
export _OPTS="${_CEE_RUNOPTS},STORAGE(NONE,NONE,NONE,1K)"
export ....
export _CEE_RUNOPTS="${_CEE_RUNOPTS},RPTSTG(ON)"
export _CEE_RUNOPTS="${_CEE_RUNOPTS},RPTOPTS(ON)"

This returns the right report in Sysout.

I am using JZOS 1.2.3., not 1.2.4.