uJES: Linking applications, services, databases & legacy systems.


Published on

Control your UNIX or Windows Batch Applications the same way you do it on a z/OS platform. ujES is a Java application that allows many nodes (Unix, Linux, Mac/OS, Windows platforms) to communicate with one another and optionally with a z/OS mainframe through the “uJES z/OS Bridge” using TCP/IP and a common language.
The Advantage?
uJES not only establishes transparent communication between heterogeneous platforms using JES commands. uJES also offers these platforms all the file management utilities and resource control capabilities available on z/OS mainframes. These z/OS services, not available on other platforms, are highly appreciated by mainframe staff in charge of the control and consolidation of decentralized applications. No specific knowledge is required. uJES uses a unique language to communicate with all the platforms, whatever the operating system flavor.
The Purpose?
uJES provides a centralized and consolidated monitoring feature to control hundred’s of processes taking place across many servers (nodes). With the JES based communication language, uJES is a universal “Agent” that can communicate with any application on any server. No “platform specific” knowledge required and no new learning curve for every platform type or “OS flavor”.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

uJES: Linking applications, services, databases & legacy systems.

  1. 1. Control your UNIX or Windows Batch applications the same way you do it in z/OS ! uJES™
  2. 2. 2 Other MVS users really want to control part of the UNIX batch production process while retaining their habits and working methods z/OS vs UNIX: Some facts uJES is intended to be used by people who understand the MVS production Some MVS users find themselves unwillingly involved with UNIX systems MVS has been a proven technology for many years, operated by reliable staff with highly valuable skills. The UNIX operating system was never designed to manage an IT batch production. # 1 # 2 # 3 # 4 # 5
  3. 3. 3 • No information centralization • Very poor incident management solution • No control facilities • No SYSOUT management • No traceability • No tools to enforce UNIX rules • No file organization • Directories search and scripts decoding are required to locate a file • No understanding of scripts and symbolic Unix: Major drawbacks
  4. 4. 4 • Complex file management system • No control of file usage or availability • No utilities to remove obsolete files • No knowledge outsourcing is available • Operator is required to have UNIX system programmer skills • Risky decision making process. • No impact measurement with restart actions • And more… Unix: Major drawbacks
  5. 5. 5 Centralized Output • An MVS / SDSF like SYSOUT management • A simple way to group and view all the outputs produced by all the processes in a unique location Focal Point • An MVS / JES like centralized system • Process control of UNIX environments • Complete control of the UNIX production from a central uJES console • Supports distributed systems or not Why uJES?
  6. 6. 6 File Identification • UNIX files are externalized with the use of the “Data Set” concept • Catalogs and Aliases offer a simplified view of the UNIX file system • MVS / JES like ”Generation Data Groups” Process Management • Optimize parallel process execution using “Initiators” • Resources balancing using Execution classes , Execution priority and initiators availability Why uJES?
  7. 7. 7 UNIX JCL • Separates the production rules from the UNIX program of scripts logic • Isolates the production concerns from the programming objectives • Simplifies the operator and the programmer tasks. Resources Management • MVS like file usage control with the “File Disposition” concept • Like in MVS , no shared or exclusive file usage conflicts • File allocation and release management Why uJES?
  8. 8. 8 uJES Technical overview
  9. 9. uJES provides JES facilities like in z/OS: • Readers, Initiators and Printers • Centralized Control of Jobs and Outputs • Job Management with Job Class and Priority • JES Data Sets for In Stream data (Sysin) and System Outputs (Sysout); • z/OS like Consoles and Console Management; • z/OS Catalogs and Data Sets; • z/OS JCL Interpretation and z/OS Utility emulation; • z/OS Partitioned Data Sets and Generation Data Group • z/OS Input Data Set Concatenation • Data Set Allocation / Release according to Disposition; • RACF like Security to control Program Execution and Data Set Access. 9 uJES Overview
  10. 10. In uJES, a Program is a UNIX Script or a Windows Batch File. uJES can run Programs as they are or by submitting a Job containing z/OS JCL Statements. When using a Job, uJES does exactly the same as z/OS: • DD Statements describe how to allocate Data Sets • Catalogs are used to assign Data Sets UNIX or Windows file paths; • File paths in the Script or Batch Files can be replaced by Environment Variables; • STEPLIBs, JOBLIBs and 'Link Lists' are used to locate Programs from EXEC Statements. uJES JCL also supports: • Procedure & Procedure Libraries • Include Members and Symbol Substitution. Jobs can be submitted from the outside, e.g a UNIX Scheduling System. 10 uJES Overview
  11. 11. the uJES network 11
  12. 12. • Several uJES Systems can be connected each other and controlled from a single Console. • Consoles are local or remote and operate in Graphic or Line mode. • Line mode Consoles allows external applications to control or monitor a uJES System. 12 uJES Network
  13. 13. the z/OS connectivity 13
  14. 14. z/OS Systems have a Job Entry Subsystem, JES2 or JES3. The uJES z/OS Bridge: •Makes JES look like a uJES Node •Allows z/OS and uJES to work together. 14 z/OS Connectivity
  15. 15. Behond uJES • uJES is not a Scheduling system • uJES provides a global solution to fix the UNIX deficiencies Runs Stand-Alone or not. Provides feed-back about submitted jobs & processes. Federates various scheduling systems. Reduces tracking agents Reduces product interfaces 15
  16. 16. uJES: Build your License 18 Create your configuration: • CPU models, MIPS, users independent • Each platform is a node (others call it ”Agent”) • Each z/OS is also a node (optional) • Web technical support and problem solving included Control your Budget: • Select the quantity and type nodes you need • Telephone support assistance (optional) • Purchase product upgrades (when necessary)
  17. 17. 19 Zelena.com 3850 S. Lake Dr. St Francis, WI Tel: (414) 481-8760 Fax: (419) 781-3625 E-mail: ujesinfo@zelena.com Questions, more Information? Or Request your Free 14 day Trial We are happy to help you! Soft4ops.com E-mail: info.us@soft4ops.com
  18. 18. Copyright Soft4ops USA 2010 20 uJES™ is a product of