New version of JZOS - 1.2.4 now available at IBM Alphaworks
New version of JZOS - 1.2.4 now available at IBM Alphaworks
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.
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.
Last edited by dovetail on Mon May 22, 2006 9:31 pm, edited 1 time in total.
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.
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.
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
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
-
- Posts: 6
- Joined: Sat Jun 03, 2006 5:49 am
-
- Posts: 6
- Joined: Sat Jun 03, 2006 5:49 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'
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'
-
- Posts: 6
- Joined: Sat Jun 03, 2006 5:49 am
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.
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.
-
- Posts: 6
- Joined: Sat Jun 03, 2006 5:49 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
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
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
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
-
- Posts: 6
- Joined: Sat Jun 03, 2006 5:49 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.
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.