Positioning XD Compute Grid Role of JZOS

1
Positioning XD Compute Grid- Role of JZOS
JES
J2SE JVM
ZFS
JZOSLauncher
JZOSAPIs
HFS
Java
JCL
VSAM

• JZos delivers 2 technologies 1. JZOS Launcher-
  seamless way to initialize a J2SE runtime from
  JCL 2. JZOS APIs- set of library functions for
  accessing traditional z/OS
  resources (MVS datasets, VSAM files, etc) from
  Java
• JZOS launcher not efficient for 1000s 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

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
EnterpriseScheduler
ZFS
WAS z/OS
JES
HFS
JZOSAPIs
XD CG
JCL
Op. Plan
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 Apis can be leveraged from XD CG
  applications
• JZOS Apis provide a strong integration point for
  Java 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