jzos in the sample

[tucker01]

It might make sense to include some jzos stuff in the sample? It's probably pretty common for folks to need those capabilities.

[dkelosky]

I think the jzos licensing thing was an issue, and why it's not included. Is that correct @plavjanik ?

[plavjanik]

It makes sense. But is more complicated. We cannot use JZOS directly in an open-source project since the JZOS JAR file is a part of IBM SDK for Java on z/OS. The only way how to call is to use Java Reflection or ask developers to download it themselves as this sample does - https://github.com/zowe/spring-boot-jzos-sample. I do not like the second option because it complicates automated builds.

An internal closed-source example can be done since it is OK to have the JAR on private Artifactory.

Another option is to write/generate a wrapper for JZOS functions that would use the Java Reflection to call the real JZOS that is in z/OS Java. This would have also the benefit that we can create an interface with different implementations:

• Calling real JZOS on z/OS
• Mock for unit testing
• Fake that emulates what can be done on PC so you can do more development on PC
• Some RPC to a backend server on z/OS (or to z/OSMF REST API) so you can get real data from z/OS without the need to deploy your application to z/OS during development (uploading huge JARs from Prague to Las Vegas takes some time).

The JZOS Java API itself is not private. We can publish code that is using it. The issue is publishing the JZOS JAR that uses proprietary native interfaces.

[github-actions[bot]]

This issue has not been updated in a long time.