very long LEPARM field

General discussion on the JZOS batch launcher and toolkit
Post Reply
mertened
Posts: 1
Joined: Wed Apr 12, 2006 9:00 am

very long LEPARM field

Post by mertened »

Hello,

in order to run our Java Application we start a shell script through BPXBATCH, that sets all variables, and then runs our Java class. No we want to use JZOS. Problem: In the current version we define a very large _CEE_RUNOPTS. With JZOS we have to pass these values via the PARM-Field of the JCL, but the resulting parmfield exceeds the limit of 100 bytes. Is there a chance, that this will be changed in z/OS 1.7 or any other way to pass the leparms?
coz
Posts: 391
Joined: Fri Jul 30, 2004 5:29 pm

Post by coz »

Setting Runtime options via the PARM field will not work as they have to be established prior to the invocation of JZOS.

However, z/OS 1.7 allows LE runtime options through the new CEEOPTS DD statement.

See the z/OS 1.7 "Language Environment Customization" document:
http://publibz.boulder.ibm.com/epubs/pdf/ceea5160.pdf

Or section 26.3 of this Redbook http://www.redbooks.ibm.com/redbooks/pdfs/sg246755.pdf
dovetail
Site Admin
Posts: 2022
Joined: Thu Jul 29, 2004 12:12 pm

Post by dovetail »

To clarify; you can set LE options in the PARM= field (preceding a slash), and they will affect the loaded program (JZOS). But, as you point out, the length limitation can be a problem. The CEEOPTS DD statement is the best way under 1.7 and beyond.
Post Reply