eclipse - "The import com.ibm.jzos cannot be resolved" when exporting CICS bundle to zOS UNIX File System - St

admin管理员组

文章数量:1291037

I'm trying to export a CICS bundle to a z/OS Unix file system using IBM Developer for z/OS.

One of the projects in my bundle has a library I'm importing (ibmjzos-2.4.11.3.jar). I added the library to the lib folder and have added it as an external jar in my project settings under Java Build Path > Libraries. The project builds with no errors.

When I right click on the bundle and "Export Bundle Project to z/OS Unix File System", I select the path where I want the bundle exported to and click Finish.

I'm then met with

 Error occurred performing plugin export.  Please check the log file for further details: C:\Users\chris\AppData\Local\Temp\explorer1739468339578\logs.zip

The contents of which are:

# 2/13/25 12:39:03 PM EST
# Eclipse Compiler for Java(TM) v20180528-0519, 3.14.0, Copyright IBM Corp 2000, 2015. All rights reserved.
----------
1. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 21)
    import com.ibm.jzos.Exec;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
2. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 22)
    import com.ibm.jzos.RcException;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
3. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 23)
    import com.ibm.jzos.ZUtil;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
4. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 68)
    Exec exec = new Exec(getStatusCommand(job), getEnvironment());
    ^^^^
Exec cannot be resolved to a type
----------
5. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 68)
    Exec exec = new Exec(getStatusCommand(job), getEnvironment());
                    ^^^^
Exec cannot be resolved to a type
----------
6. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 84)
    throw new RcException("REXX 'jobStatus' process failed: " + line, rc);
              ^^^^^^^^^^^
RcException cannot be resolved to a type
----------
7. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 150)
    Exec exec = new Exec(getJobOutputCommand(mvsJob), getEnvironment());
    ^^^^
Exec cannot be resolved to a type
----------
8. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 150)
    Exec exec = new Exec(getJobOutputCommand(mvsJob), getEnvironment());
                    ^^^^
Exec cannot be resolved to a type
----------
9. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 165)
    throw new RcException("REXX 'jobOutput' process failed", rc);
              ^^^^^^^^^^^
RcException cannot be resolved to a type
----------
10. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 197)
    Properties p = ZUtil.getEnvironment();
                   ^^^^^
ZUtil cannot be resolved
----------
11. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 204)
    for (Iterator<Object> iter = p.keySet().iterator(); iter.hasNext();) {
                  ^^^^^^
Syntax error, parameterized types are only available if source level is 1.5 or greater
----------
11 problems (11 errors)

The root problem appears to me that the com.ibm.jzos library is not being included when bundled. How do I fix the libraries when the bundle is being exported?

I'm trying to export a CICS bundle to a z/OS Unix file system using IBM Developer for z/OS.

One of the projects in my bundle has a library I'm importing (ibmjzos-2.4.11.3.jar). I added the library to the lib folder and have added it as an external jar in my project settings under Java Build Path > Libraries. The project builds with no errors.

When I right click on the bundle and "Export Bundle Project to z/OS Unix File System", I select the path where I want the bundle exported to and click Finish.

I'm then met with

 Error occurred performing plugin export.  Please check the log file for further details: C:\Users\chris\AppData\Local\Temp\explorer1739468339578\logs.zip

The contents of which are:

# 2/13/25 12:39:03 PM EST
# Eclipse Compiler for Java(TM) v20180528-0519, 3.14.0, Copyright IBM Corp 2000, 2015. All rights reserved.
----------
1. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 21)
    import com.ibm.jzos.Exec;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
2. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 22)
    import com.ibm.jzos.RcException;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
3. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 23)
    import com.ibm.jzos.ZUtil;
           ^^^^^^^^^^^^
The import com.ibm.jzos cannot be resolved
----------
4. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 68)
    Exec exec = new Exec(getStatusCommand(job), getEnvironment());
    ^^^^
Exec cannot be resolved to a type
----------
5. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 68)
    Exec exec = new Exec(getStatusCommand(job), getEnvironment());
                    ^^^^
Exec cannot be resolved to a type
----------
6. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 84)
    throw new RcException("REXX 'jobStatus' process failed: " + line, rc);
              ^^^^^^^^^^^
RcException cannot be resolved to a type
----------
7. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 150)
    Exec exec = new Exec(getJobOutputCommand(mvsJob), getEnvironment());
    ^^^^
Exec cannot be resolved to a type
----------
8. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 150)
    Exec exec = new Exec(getJobOutputCommand(mvsJob), getEnvironment());
                    ^^^^
Exec cannot be resolved to a type
----------
9. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 165)
    throw new RcException("REXX 'jobOutput' process failed", rc);
              ^^^^^^^^^^^
RcException cannot be resolved to a type
----------
10. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 197)
    Properties p = ZUtil.getEnvironment();
                   ^^^^^
ZUtil cannot be resolved
----------
11. ERROR in C:\Users\chris\src\com.ibm.cics.server.examples.hello\src\examples\hello\MvsJobOutput.java (at line 204)
    for (Iterator<Object> iter = p.keySet().iterator(); iter.hasNext();) {
                  ^^^^^^
Syntax error, parameterized types are only available if source level is 1.5 or greater
----------
11 problems (11 errors)

The root problem appears to me that the com.ibm.jzos library is not being included when bundled. How do I fix the libraries when the bundle is being exported?

• eclipse
• mainframe
• zos
• cics

Share Improve this question Follow asked Feb 13 at 17:46 rockzombie2rockzombie2 2,92544 gold badges1818 silver badges2020 bronze badges 4

• The last error message might refer to the root problem: Syntax error, parameterized types are only available if source level is 1.5 or greater. What's your project setting for this (1.5 means Java 5 which is outdated for years)? I don't know the "Export Bundle Project to z/OS Unix File System" function since it is not standard Eclipse. The log says Eclipse Compiler for Java(TM) v20180528-0519, 3.14.0 (v20180528... means May 28, 2018) which is almost 7 years behind and won't work with recent Java versions. – howlger Commented Feb 13 at 19:22
• I selected JavaSE 1.8 in my build path but I'm still getting that error message in the output. I don't get any build errors locally in IDZ with my project, these errors only appear when I try to export my bundle to z/OS. Then, it's as if my build path is ignored and I get these errors. I don't know how IDZ is building the bundle, but I suspect it's different from the way it's built locally and thus the build path is getting ignored. – rockzombie2 Commented Feb 13 at 19:52
• Two clarifications... what type of application are you building? Is it an OSGi bundle, a WAR (web application), etc. Second, do you want to be creating Eclipse-style projects, or would you rather be constructing Maven or Gradle projects? If so, there's probably a better set of answers. – Ben Cox Commented Feb 13 at 22:49
• Set the java version in the "Java Compiler" page of the project Properties not just the build path. – greg-449 Commented Feb 14 at 8:02

Add a comment  | 

3 Answers 3

Sorted by: Reset to default 1

It sounds like you are attempting to add the jzos library into your OSGi bundle in the lib folder. Normally what we would expect to do is a wrapper OSGi bundle that is used within the IDE. This wrapper bundle exports the com.ibm.jzos classes and your bundle imports them. This should allow the compiling and IDE to be happy.

For full instructions have a look at https://www.ibm/docs/en/cics-ts/6.x?topic=djariojs-developing-java-applications-use-jzos-toolkit-api-in-osgi-jvm-server

The jar you are referencing I believe is a stub library so that jzos can be referenced in IDEs but does not contain the complete classes. The JZOS library is present in z/OS Java but not as a jar you can download.

For instance, I've downloaded the jar your referencing to my local system for development so I can reference the classes and methods during development on my Mac but I do not need to package that jar as it exists in the Java distribution on z/OS.

JZOS is a collection of Java classes and native code so the library you are referencing is a convenience jar for development and not execution.

Getting the classpaths right when creating Eclipse projects can get tricky when trying to export them, and trickier still when trying to create CI builds to do the same thing.

If you were instead building your application with Maven or Gradle, you would avoid this work and inconsistencies. However, there are some things you could still trip over. Here are some hints and tips.

Get hold of JZOS

The stub of JZOS is findable on Maven Central and can be mirrored to downstream internal repositories like Artifactory and Nexus. Its coordinates are:

• com.ibm.jzos:ibmjzos for Java 8
• com.ibm.jzos:ibm.jzos for Java 11 and beyond, when JZOS becomes a Java module.

You can work out exactly which version you need using pages like Managing IBM JZOS dependencies by using Maven.

Make sure you don't package JZOS

JZOS is included within the JVM and available on the classpath automatically. To avoid inconsistencies, you want it to not be packaged into your application. You do this with the Maven scope:

<dependencies>
    <dependency>
        <groupId>com.ibm.jzos</groupId>
        <artifactId>ibm.jzos</artifactId>
        <version>3.1.3.3</version>
        <scope>provided</scocpe>
    </dependency>
</dependencies>

Or the Gradle configuration name:

dependencies {
  compileOnly "com.ibm.jzos:ibm.jzos:3.1.3.3"
}

Create and deploy the CICS bundle

The creation of the CICS bundle can be automated using the CICS bundle Maven plugin or CICS bundle Gradle plugin.

Either plugin offers the opportunity to create a module which is the CICS bundle and pulls in other modules, or to simply turn an existing Java module into a CICS bundle.

You can even do the deployment directly to your development CICS region in Maven or Gradle, which is a big time saver.

本文标签：