Jopaz 1.2.0 | Compiling with Jopaz | Compiling on z/OS
 
Compiling on z/OS
 
Compiling and Running with Jopaz using JZOS
You can find two sample JCL jobs in the jpz-jcl-templates folder from the delivery package to enable you to compile on z/OS. JPZCOMP allows the compilation from Cobol to Java using the Jopaz compiler. JPZEXEC then executes the Java class (.class) compiled from the Jopaz compiler directly with JZOS. Both jobs are for Java in 64-bit addressing mode.
Each job uses a configuration file that you can find in the jpz-jcl-templates folder. If the installer script was used at the beginning, these two files were also automatically copied to the desired dataset and adapted to the installation. COMPCONF is the Jopaz configuration file for compilation. EXECCONF is the Jopaz configuration file for execution.
Accordingly, the references look like:
*JPZCOMP
*&JVM64 = JVMPRC86
*&CONFIG = COMPCONF
*JPZEXEC
*&JVM64 = JVMPRC86
*&CONFIG = EXECCONF
Both configuration files are necessary for their respective jobs. They use a configuration library, which is stored in the UNIX system services under the directory /jpz-compiler/conf/jvm_default_conf.sh. This file contains a number of standard configurations that can be included in the configuration files by means of method calls.
The examples of COMPCONF and EXECCONF shown here demonstrate how the standard configurations can also be overwritten.
Note:
Alternatively, the configuration and execution scripts can be stored in a USS directory like /jpz/jpz-scripts and referenced via path specification. To do this, specify directly in the JCL job the absolute path to the file in quotation marks. For example, in JPZCOMP:
SET CONFIG = ’/.../jpz-scripts/COMPCONF.sh’
For testing the setup, you can use the HELLO.cbl program included in the delivery package.
Note:
Regarding the CVE-2021-44228 Apache Log4j vulnerability, we have added the JVM option "-Dlog4j2.formatMsgNoLookups=true" to all configuration files to mitigate it.