1. Positioning XD Compute Grid- Role of JZOS
JES
J2SE JVM
ZFS
JZOS Launcher
JZOS API’s
HFS
Java
JCL
VSAM
JZos delivers 2 technologies: 1. JZOS Launcher- seamless way to initialize a J2SE runtime from JCL 2. JZOS API’s- set of library functions for accessing traditional z/OS resources (MVS datasets, VSAM files, etc) from Java
JZOS launcher not efficient for 1000’s of batch jobs to be run within a batch window
J2SE JVM has no: - security, transaction, or connection management - checkpoint or restart facility for batch jobs - inherent high availability, or other WAS z/OS qualities of service
JVM is not persistent or reusable.
Great to get started…
Second, the role of Compute Grid and JZOS; JZOS is a technology for enabling java on z/OS to access and leverage traditional z/OS facilities. This technology is composed of two components: first is a launcher, whose job is to efficiently initialize a J2SE runtime from JCL; second are the programming interfaces available to applications for accessing traditional z/OS resources such as datasets.
The JZOS launcher technology initializes a J2SE runtime; a runtime that lacks features such as: transaction, security, and connection management; checkpoint and/or recoverability facilities for batch jobs; inherent high availability and other WebSphere qualities of service provided by enterprise middleware such as WebSphere.
The JZOS programming interfaces (API’s) serve a different purpose than the launcher

2. Mainframe Java Batch – Relative Base-line Cost
CPU time spent on JVM startup
JZOS
WebSphere Batch (Compute Grid)
Number of job steps

3. Positioning XD Compute Grid- Role of JZOS
Enterprise Scheduler
ZFS
WAS z/OS
JES
JZOS API’s
HFS
XD CG
Op. Plan
JCL
VSAM
XD Compute Grid is built on WebSphere z/OS
leverages QoS and services provided by the WAS z/OS runtime (security, transaction, connection management; thread pooling; HA, etc)
Runs within a persistent, reusable JVM and Execution Container
JZOS Api’s can be leveraged from XD CG applications
JZOS Api’s provide a strong integration point for Java and traditional z/OS
The programming interfaces can be leveraged by Compute Grid applications, enabling these applications to access traditional z/OS artifacts such as ZFS, HFS, VSAM, and others. The JZOS programming interfaces coupled with Compute Grid delivers a strong integration point for enterprise java batch applications and traditional z/OS.

4. Grow into Compute Grid
Batch Application
BDS Framework
Batch Application
Batch Simulator
BDS Framework
JZOS/J2SE
Compute Grid
Start with JZOS or J2SE-based Java batch infrastructure
Grow into Compute Grid-based Java batch infrastructure
Leverage FREE Compute Grid development tools and frameworks to build Compute-Grid-Ready batch applications