User Response
Do as follows:
- If the program is being called from a Java™ wrapper, the linkage properties file
must be named link.properties, where link is
the name of the linkage options part used at generation. Make sure the file
exists, has an entry for the called program, and is in a directory or archive
specified in the CLASSPATH variable.
- If the program is being called from a program running in the J2EE environment,
the linkage properties file can be identified by the cso.linkageOptions.link environment
variable in the deployment descriptor, where link is
the name of the linkage options part used at generation. If the environment
variable is not set, the linkage properties file must be named link.properties,
where link is the name of the linkage options part
used at generation. Make sure the file exists, has an entry for the called
program, and is in a directory or archive specified in CLASSPATH.
- If the program is being called from a program not running in the J2EE
environment, the situation is as follows:
- The linkage properties file can be identified by the cso.linkageOptions.link property,
where link is the name of the linkage options part
used at generation. If the property is not set, the linkage properties file
may be named link.properties, where link is
the name of the linkage options part used at generation. In these two cases,
make sure the file exists, has an entry for the called program, and is in
a directory or archive specified in CLASSPATH.
- If the linkage properties file cannot be found, the linkage properties
must be in the program properties file; in that case, make sure the program
properties file includes an entry for the called program and that the program
properties file is in a directory or archive specified in CLASSPATH.
For other details, see the EGL help pages on the callLink element,
on Java runtime
properties, and on setting up the environment.
If the problem persists,
do as follows:
- Record the message number and the message text.
Note: The error message
includes the following important information:
- Where the error occurred
- The type of internal error
- Record the situation in which this message occurs.
- For further instructions on how to report possible defects to the IBM® Support
Center, refer to the EGL Installation Guide.