Create Java Program (CRTJVAPGM)

The Create Java Program (CRTJVAPGM) command creates a Java program from a Java class file, JAR file, or ZIP file. The resulting Java program object becomes part of the class file, JAR file or ZIP file object. The Java program runs when started by the JAVA (Run Java Program) command.

Restrictions: The file must be in one of the following file systems: QOpenSys,"root", or a user-defined file system.

Parameters

Keyword	Description	Choices	Notes
CLSF	Class file or JAR file	Path name	Required, Positional 1
CLASSPATH	Classpath	Path name, NONE, ENVVAR	Optional
JDKVER	Java developer kit version	Character value, *NONE	Optional
OPTIMIZE	Optimization	10, *INTERPRET, 20, 30, 40	Optional
USRPRF	User profile	USER, OWNER	Optional
USEADPAUT	Use adopted authority	NO, YES	Optional
REPLACE	Replace program	YES, NO	Optional
ENBPFRCOL	Enable performance collection	NONE, ENTRYEXIT, *FULL	Optional
PRFDTA	Profiling data	NOCOL, COL	Optional
SUBTREE	Directory subtree	NONE, ALL	Optional
TGTRLS	Target release	Character value, *CURRENT	Optional
LICOPT	Licensed Internal Code options	Character value, *OPTIMIZE	Optional
LICOPTFILE	LIC options file	Path name, *NONE	Optional

Top

Class file or JAR file (CLSF)

Specifies the class file , JAR file, or ZIP file name from which to create the Java program. The file name may be qualified by one or more directory names.

class-file-name: Specify the name of the class file or a pattern for identifying the class file or files to be used. A pattern can be specified in the last part of the name. An asterisk matches any number of characters and a question mark matches a single character. If the name is qualified or contains a pattern it must be enclosed in apostrophes. An example of a qualified class file name is '/directory1/directory2/myclassname.class'. An example of a pattern is '/directory1/directory2/myclass*.class'.
JAR-file-name: Specify the name of the Java archive (JAR) file or pattern for identifying the JAR or ZIP file or files to be used. A file is assumed to be a JAR file if the file name ends with '.jar' or '.zip'. A pattern can be specified in the last part of the name. An asterisk matches any number of characters and a question mark matches a single character. If the name is qualified or contains a pattern it must be enclosed in apostrophes. An example of a qualified JAR file name is '/directory1/directory2/myappname.jar'. An example of a pattern is '/directory1/directory2/myapp*.zip'.

Classpath (CLASSPATH)

Specifies the path used to locate classes for inter-JAR binding. Directories are separated by colons.

*NONE: No additional directories or JAR files are added to the class path for locating classes.
*ENVVAR: The class path is determined by the environment variable CLASSPATH.
class-path: Path used to locate classes. An example class path is '/directory1/directory2:/QIBM/ProdData/Java400'.

Either CLASSPATH or JDKVER must be specified for inter-JAR binding to occur. CLASSPATH must be *NONE when CLSF is a class file.

Java developer kit version (JDKVER)

Specifies the Java Development Kit (JDK) version to add to the class path for locating classes for inter-JAR binding.

*NONE: No additional directories for this JDK version are added to the class path for locating classes.
Java-Development-Kit version: The jar files and directories for this JDK version are added to the class path for locating classes. An example JDK version is '1.2.2'.

Either CLASSPATH or JDKVER must be specified for inter-JAR binding to occur. JDKVER must be *NONE when CLSF is a class file.

Optimization (OPTIMIZE)

Specifies the optimization level of the Java program.

The OPTIMIZE parameter is only used when creating Java programs for a target release prior to Version 6 Release 1 Modification 0. For target release V6R1M0 and later, the value is ignored and OPTIMIZE(*INTERPRET) is used.

As of V6R1M0, Java programs do not contain machine instructions. The class file is pre-verified and converted to an internal form. However the Java program is either interpreted from the bytecodes or else run with the Just In Time compiler (JIT).

For target releases prior to V6R1M0, the OPTIMIZE parameter specifies the optimization level of the Java program. When creating a Java program for a target release prior to V6R1M0, the value of the OPTIMIZE parameter is encapsulated within the Java program, but no machine instructions are generated. The encapsulated value of the OPTIMIZE parameter is used during Java program retranslation on the target release of the operating system.

10: The Java program contains a compiled version of the class bytecodes but has only minimal additional compiler optimization. Variables can be displayed and modified while debugging.
*INTERPRET: The Java program created does not contain machine instructions. The Java program is interpreted from the bytecodes or run with the JIT compiler when it is started. Variables can be displayed and modified while debugging.
20: The Java program contains a compiled version of the class bytecodes and has some additional compiler optimization. Variables can be displayed but not modified while debugging.
30: The Java program contains a compiled version of the class bytecodes and has more compiler optimization than optimization level 20. During a debug session, user variables cannot be changed, but can be displayed. The presented values may not be the current values of the variables.
40: The Java program contains a compiled version of the class bytecodes and has more compiler optimization than optimization level 30. All call and instruction tracing is disabled.

User profile (USRPRF)

Specifies whether the authority checking done while this program is running should include only the user who is running the program (*USER) or both the user who is running the program and the program owner (*OWNER). The profiles of the program user or both the program user and the program owner are used to control which objects can be used by the program, including the authority the program has for each object. Only the program owner or a user with QSECOFR authority can change the user profile attribute.

*SAME: The user profile attribute does not change.
*USER: The program runs under the user profile of the program's user.
*OWNER: The user profiles of both the program's owner and the program's user are used when the program is processed. The collective sets of object authority in both user profiles are used to find and access objects during program processing. Authority from the owning user profile's group profile is not included in the authority for the running program.

Use adopted authority (USEADPAUT)

Specifies whether program adopted authority from previous programs in the call stack will be used as a source of authority when this program is running.

*NO: Program adopted authority from previous call levels is not used when this program is running.
*YES: Program adopted authority from previous call levels is used when this program is running. If an authorization list is specified for the QUSEADPAUT system value and the user is not authorized to that authorization list, *NO is used.

Replace program (REPLACE)

Specifies whether an existing Java program associated with this file is replaced with the new Java program being created.

*YES: The existing Java program associated with this file is replaced by the new Java program created.
*NO: An existing Java program associated with this file is replaced only if the class file was changed since the existing program was created; otherwise, creation of the new Java program is stopped and a message is displayed. If a pattern was used to indicate multiple creations, processing continues with the next file.

Enable performance collection (ENBPFRCOL)

Specifies whether collection of performance data is enabled.

The ENBPFRCOL parameter is only used when creating Java programs for a target release prior to Version 6 Release 1 Modification 0. For target release V6R1M0 and later, the value is ignored and ENDPFRCOL(*NONE) is used.

For a target release prior to V6R1M0, the following values may be specified, but values *ENTRYEXIT and *FULL will not be effective until the Java program is retranslated on the target release of the operating system.

*NONE: The collection of performance data is not enabled. No performance data is to be collected.
*ENTRYEXIT: Performance data is collected for procedure entry and exit.
*FULL: Performance data is collected for procedure entry and exit. Performance data is also collected before and after calls to external procedures.

Directory subtree (SUBTREE)

Specifies whether directory subtrees are processed when looking for files that match the CLSF keyword.

*NONE: Only the files that match the object name pattern will be processed. No subtrees are processed. If the directory has subdirectories, neither the subdirectories nor the objects in the subdirectories are processed.
*ALL: The entire subtree of the path specified in CLSF is processed to create java programs for files matching the name specified on CLSF parameter.

Target release (TGTRLS)

Specifies the release of the operating system on which you intend to use the object being created. When specifying the target-release value, the format VxRxMx is used to specify the release, where Vx is the version, Rx is the release, and Mx is the modification level. For example, V5R2M0 is version 5, release 2, modification level 0.

Valid values depend on the current version, release, and modification level, and they change with each new release.

*CURRENT: The object is to be used on the release of the operating system currently running on your system. The object can also be used on a system with any subsequent release of the operating system installed.
target-release: Specify the release in the format VxRxMx. The object can be used on a system with the specified release or with any subsequent release of the operating system installed.

Licensed Internal Code options (LICOPT)

Specifies one or more Licensed Internal Code compile-time options. This parameter allows individual compile-time options to be selected, and is intended for the advanced programmer who understands the potential benefits and drawbacks of each selected type of compiler option.

*OPTIMIZE: Use the set of compile-time options which are implicitly associated with the optimization level specified on the OPTIMIZE parameter. If OPTIMIZE(*INTERPRET) is specified, no compile-time optimizations will be performed.
'Licensed-Internal-Code-options-string': The selected Licensed Internal Code compile-time options are used when creating the Java program object. Certain options may reduce your ability to debug the created Java program.
Note: Additional information about the LICOPT options can be found in the IBM Developer Kit for Java topic collection in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.

LIC options file (LICOPTFILE)

Specifies a file name which lists one or more Licensed Internal Code compile-time options.

*NONE: There is no file specified.
'Licensed-Internal-Code-options-filename': The file is used for specifiying which Licensed Internal Code compile-time options are used when creating the Java program object. Certain options may reduce your ability to debug the created Java program.
Note: Additional information about the LICOPT options can be found in the IBM Developer Kit for Java topic collection in the IBM i Information Center at http://www.ibm.com/systems/i/infocenter/.

Examples

Example 1: Create a Java Program

CRTJVAPGM   CLSF('/projectA/myJavaclassname.class')

This command will create a Java program and associate it with the class file myJavaclassname. The Java program will contain pre-verified class file information which is used when the Java program is invoked via the RUNJVA (Run Java) or the JAVA CL command.

Example 2: Create a Java Program Specifying a LICOPT File

CRTJVAPGM   CLSF('/projectA/myJavaclassname.class')
            LICOPTFILE('/projectA/mylicoptfile.txt')

This command will create a Java program and associate it with the class file myJavaclassname. The command will read the Licensed Internal Code options contained in the text file mylicoptfile.txt and prepend them to the default Licensed Internal Code Options.

Example 3: Create Numerous Java Programs

CRTJVAPGM   CLSF('/projectA/*.class') SUBTREE(*ALL)

This command will create a Java program and associate it with any class file in the projectA directory and any class file in directories below projectA.