zJOS-XDI© The Integrated z/OS Automation Solution www.zjosxdi.com © 2004 Deru Sudibyo Product Highlight
zJOS-XDI Solution to Integrated Automation
What is Offered by zJOS-XDI? Event management system (EMS) Automates actions firing against event occurrence for either a single z/OS host or cross inter-hosts for networked z/OS hosts.  Product/component name is  zJOS/Sekar   Automatic jobs/workloads scheduling  Automates JES2-based jobs and other workloads scheduling based on occurrences of combination of any types of events.  Schedule flow can either for a single z/OS host or cross inter-hosts for networked z/OS hosts.  Product/component name is  zJOS/Puspa Automatic spool file distribution  Automates spool files download and distribution.  Product/component name is  XDI/AutoXfer
zJOS-XDI Technology Run on z/OS MVS platforms with JES2 Provides EMS functions ( zJOS/Sekar ) Provides events-driven workloads scheduling functions ( zJOS/Puspa ) Support networked-z/OS total automation  Provides spool distribution functions ( XDI/AutoXfer )  zJOS XDI z/OS (mainframe) Event Mgr Scheduler
Networked-z/OS Automation z/OS Agent zJOS XDI z/OS (mainframe) Event Mgr Scheduler z/OS Agent z/OS Agent
Networked-z/OS Automation  (cont’d) For example:  SYSPROD and DR Events in DR can be automated from SYSPROD Jobs in DR can be scheduled and controlled from SYSPROD z/OS - SYSDR Agent zJOS XDI z/OS - SYSPROD Event Mgr Scheduler
zJOS/Sekar©   Events Management Solution
zJOS Event Management Solution zJOS/Sekar  – EMS Solution:  Facilitates users to define sets of actions against selected system events.  Automates firing of all user’s defined action-sets based on event occurrences.  In networked z/OS hosts, event–actions relationship can be one-to-one or one-to-many among hosts in the network.  Features:  Supports message (WTO and WTOR), command, timing (TOD), end-of-job (EOJ),  end-of-jobstep (EOS) and dataset/file access and release types of system events.  Supports command, reply (to WTOR) and rule types of actions.  Supports networking agent (TCP/IP) for:  Inter-hosts event intercepting  Inter-hosts actions propagation  Supports timeframe filter to control action execution based on user’s specified date-range, time-range, day-of-week and national holiday calendar.
Integrated Event Management  z/OS – SYS 2  zJOS EMS Manager z/OS – SYS 1 Event Action Event Action Event Action Event Event Action Action Action
zJOS/Puspa©   Event-driven Scheduling Solution
zJOS Automatic Scheduling Solution zJOS/Puspa  – Jobs Scheduling Solution: Facilitates users to define event-based workload or jobs schedule flows.  Automates scheduling of all user’s defined workloads based on timing, job status, messages, commands and/or dataset access/release events occurrences.  In networked z/OS hosts, predecessors-current-successors relationship can be crossed among hosts in the network.  Features:  Supports both jobstep-level and job-level triggering mechanism Supports almost unlimited combination of multi-condition triggering logic  Supports networking agent (TCP/IP) for:  Inter-hosts job-status information intercepting  Inter-hosts jobs propagation  Supports timeframe filter to control schedule execution based on user’s specified date-range, time-range, day-of-week and national holiday calendar.  Supports special/advanced calendar control in addition to timeframe filter such as first work-day after off-day, first and work-day of week or of month etc.
zJOS/Puspa - Ultimate Scheduler Workload pipelining – the most efficient workload managemet.  By supporting job-step level triggering/tracking mechanism, schedule flow path can be minized to lower turn around time.  Boolean logic CC multitesting – the most flexible workload management.  By supporting multigroup boolean logic comparison of CC in 2
Workload Pipelining  A job may depend on its predecessor only for a certain job-step.  Such job should not wait until the predecessor end.  By supporting job-step level triggering/tracking mechanism, schedule flow path can be minized to lower turn around time.  step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4
Conventional vs Pipelining Conventional scheduling  Pipelined scheduling  step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 Start JOB0 Start JOB1 Start JOB2 Start JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 Start JOB4 Start JOB5 End of all jobs step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 Start JOB0 Start JOB1 Start JOB2 Start JOB3 Start JOB4 Start JOB0 Start JOB5 End of all jobs
Boolean Logic CC Multitest Users have more chance to implement any level of schedule flow complexities easily.  Application developers have more chance to provide their own multiple recovery flows mechanism.  step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 AND OR ABEND CC = 0 CC < 8 CC = 0 CC < 4 CC = 0 OR CC = 0 CC < 4 AND CC > 4
Any Event Can Trigger Schedule Schedule more than just inter-jobs dependencies and timing.  Any other types of events can also be used to triggers schedule.  Supported events are messages, commands, dataset access and dataset release.
Integrated Automatic Scheduling z/OS – SYS 2  zJOS Jobs Scheduler z/OS – SYS 1 JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7
XDI/AutoXfer©   Spool/Outputs Distribution Solution
XDI Spool Distribution Solution XDI/AutoXfer  – Spool Distribution Solution: Facilitates users to define distribution parameters which include destinations and recipients, and spool files selection criteria.  Each destination can have one or more recipients.  Automates all user’s defined parameters based on spool file occurrences.  Features:  Supports text format conversion from MCC to ASA  Supports the following recipient’s PC text format:  Microsoft Wordpad  CA-Dispatch for PC Supports disposition option to:  Keep original files Purge original files
Increase DR Utilization with zJOS-XDI
How is DR Operated? Does disaster recovery (DR) system just to keep data backup? Don’t you think that DR machine can help the production machine? zJOS-XDI would help you exploring the expensive DR machine, instead of just sleeping all the time.
zJOS-XDI Concept of DR  zJOS-XDI approach you to have GDPS without parallel sysplex.  DR and production machines are at the same level Make both contents are the same.  DR and Production are just a matter of operation logic.  Select separatable programs and data, and make them as 2 groups of jobs.  One group runs on production machine and use DR machine as its backup.  The other group runs on DR machine and use production machine as its backup.  Lets zJOS-XDI manages both machines as productions and DR in flip-flop according to each group position.
zJOS-XDI Concept of DR  (cont’d) SYSPROD DR JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Production JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Production
zJOS-XDI Concept of DR  (cont’d) DRC zJOS Jobs Scheduler SYSPROD JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Production JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Production
zJOS-XDI Concept of DR  (cont’d) DRC zJOS EMS Scheduler SYSPROD JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7 zJOS Jobs Scheduler SYSPROD JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7
zJOS-XDI Future
zJOS Server Design Supports up to 99 agent connections  Support SAF exit interface for non-agent connection security checking Supports IPv6 Automatic ASCII-EBCDIC detection and translation.  zJOS XDI z/OS (mainframe) Event Mgr Scheduler
zJOS Agent Design Simple and smart interaction protocols Simple and smart data structures IPv6 support No bother with ASCII-EBCDIC type of platform since it will resolved by zJOS Server automatically Agent
Strategic Enterprise Plan Options  Extend R&D to develop various zJOS agents for all possible non-z/OS platforms.  Lets users develop their own zJOS agents.  Any one who expert in certain platform can develop zJOS agent for that platform  Lets open source communities develop zJOS agents for open system platforms.
zJOS in Enterprise Environment Linux Agent zJOS XDI z/OS (mainframe) Event Mgr Scheduler Unix Agent Other Agent Linux Agent zJOS XDI z/OS (mainframe) Event Mgr Scheduler Unix Agent Other Agent
Demo & Offering
Download Demo  Should you curious, kindly download the demo package  zJOS-XDI  Notes:  Packeage is in WinZIP file format Read README.txt before you install it To complete the trials, refer to the following files: InstallGuide.pps TrialGuide.pps UserGuide_EMS.pps UserGuide_Scheduler.pps
Offering zJOS-XDI “crazy project” is looking for sponsor or partnership or even acquisition.  If you are representing a mainframe software vendor, you would find this zJOS-XDI project is much more cost-effective than you develop yourself.  Take time and lots of resources to develop.  Meanwhile, at the moment not many vendors to compete in this strategic market sector.  Sponsorship from any skill building foundation who really understand and care of potential economic and moral aspect of such project to the developing country like Nusantara, is very welcome.

zJOS - Mainframe Automation Solution

  • 1.
    zJOS-XDI© The Integratedz/OS Automation Solution www.zjosxdi.com © 2004 Deru Sudibyo Product Highlight
  • 2.
    zJOS-XDI Solution toIntegrated Automation
  • 3.
    What is Offeredby zJOS-XDI? Event management system (EMS) Automates actions firing against event occurrence for either a single z/OS host or cross inter-hosts for networked z/OS hosts. Product/component name is zJOS/Sekar Automatic jobs/workloads scheduling Automates JES2-based jobs and other workloads scheduling based on occurrences of combination of any types of events. Schedule flow can either for a single z/OS host or cross inter-hosts for networked z/OS hosts. Product/component name is zJOS/Puspa Automatic spool file distribution Automates spool files download and distribution. Product/component name is XDI/AutoXfer
  • 4.
    zJOS-XDI Technology Runon z/OS MVS platforms with JES2 Provides EMS functions ( zJOS/Sekar ) Provides events-driven workloads scheduling functions ( zJOS/Puspa ) Support networked-z/OS total automation Provides spool distribution functions ( XDI/AutoXfer ) zJOS XDI z/OS (mainframe) Event Mgr Scheduler
  • 5.
    Networked-z/OS Automation z/OSAgent zJOS XDI z/OS (mainframe) Event Mgr Scheduler z/OS Agent z/OS Agent
  • 6.
    Networked-z/OS Automation (cont’d) For example: SYSPROD and DR Events in DR can be automated from SYSPROD Jobs in DR can be scheduled and controlled from SYSPROD z/OS - SYSDR Agent zJOS XDI z/OS - SYSPROD Event Mgr Scheduler
  • 7.
    zJOS/Sekar© Events Management Solution
  • 8.
    zJOS Event ManagementSolution zJOS/Sekar – EMS Solution: Facilitates users to define sets of actions against selected system events. Automates firing of all user’s defined action-sets based on event occurrences. In networked z/OS hosts, event–actions relationship can be one-to-one or one-to-many among hosts in the network. Features: Supports message (WTO and WTOR), command, timing (TOD), end-of-job (EOJ), end-of-jobstep (EOS) and dataset/file access and release types of system events. Supports command, reply (to WTOR) and rule types of actions. Supports networking agent (TCP/IP) for: Inter-hosts event intercepting Inter-hosts actions propagation Supports timeframe filter to control action execution based on user’s specified date-range, time-range, day-of-week and national holiday calendar.
  • 9.
    Integrated Event Management z/OS – SYS 2 zJOS EMS Manager z/OS – SYS 1 Event Action Event Action Event Action Event Event Action Action Action
  • 10.
    zJOS/Puspa© Event-driven Scheduling Solution
  • 11.
    zJOS Automatic SchedulingSolution zJOS/Puspa – Jobs Scheduling Solution: Facilitates users to define event-based workload or jobs schedule flows. Automates scheduling of all user’s defined workloads based on timing, job status, messages, commands and/or dataset access/release events occurrences. In networked z/OS hosts, predecessors-current-successors relationship can be crossed among hosts in the network. Features: Supports both jobstep-level and job-level triggering mechanism Supports almost unlimited combination of multi-condition triggering logic Supports networking agent (TCP/IP) for: Inter-hosts job-status information intercepting Inter-hosts jobs propagation Supports timeframe filter to control schedule execution based on user’s specified date-range, time-range, day-of-week and national holiday calendar. Supports special/advanced calendar control in addition to timeframe filter such as first work-day after off-day, first and work-day of week or of month etc.
  • 12.
    zJOS/Puspa - UltimateScheduler Workload pipelining – the most efficient workload managemet. By supporting job-step level triggering/tracking mechanism, schedule flow path can be minized to lower turn around time. Boolean logic CC multitesting – the most flexible workload management. By supporting multigroup boolean logic comparison of CC in 2
  • 13.
    Workload Pipelining A job may depend on its predecessor only for a certain job-step. Such job should not wait until the predecessor end. By supporting job-step level triggering/tracking mechanism, schedule flow path can be minized to lower turn around time. step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4
  • 14.
    Conventional vs PipeliningConventional scheduling Pipelined scheduling step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 Start JOB0 Start JOB1 Start JOB2 Start JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 Start JOB4 Start JOB5 End of all jobs step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 Start JOB0 Start JOB1 Start JOB2 Start JOB3 Start JOB4 Start JOB0 Start JOB5 End of all jobs
  • 15.
    Boolean Logic CCMultitest Users have more chance to implement any level of schedule flow complexities easily. Application developers have more chance to provide their own multiple recovery flows mechanism. step02 step01 JOB0 step13 step12 step11 JOB1 step23 step22 step21 JOB2 step32 step31 JOB3 step53 step52 step51 JOB5 step43 step42 step41 JOB4 AND OR ABEND CC = 0 CC < 8 CC = 0 CC < 4 CC = 0 OR CC = 0 CC < 4 AND CC > 4
  • 16.
    Any Event CanTrigger Schedule Schedule more than just inter-jobs dependencies and timing. Any other types of events can also be used to triggers schedule. Supported events are messages, commands, dataset access and dataset release.
  • 17.
    Integrated Automatic Schedulingz/OS – SYS 2 zJOS Jobs Scheduler z/OS – SYS 1 JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7
  • 18.
    XDI/AutoXfer© Spool/Outputs Distribution Solution
  • 19.
    XDI Spool DistributionSolution XDI/AutoXfer – Spool Distribution Solution: Facilitates users to define distribution parameters which include destinations and recipients, and spool files selection criteria. Each destination can have one or more recipients. Automates all user’s defined parameters based on spool file occurrences. Features: Supports text format conversion from MCC to ASA Supports the following recipient’s PC text format: Microsoft Wordpad CA-Dispatch for PC Supports disposition option to: Keep original files Purge original files
  • 20.
  • 21.
    How is DROperated? Does disaster recovery (DR) system just to keep data backup? Don’t you think that DR machine can help the production machine? zJOS-XDI would help you exploring the expensive DR machine, instead of just sleeping all the time.
  • 22.
    zJOS-XDI Concept ofDR zJOS-XDI approach you to have GDPS without parallel sysplex. DR and production machines are at the same level Make both contents are the same. DR and Production are just a matter of operation logic. Select separatable programs and data, and make them as 2 groups of jobs. One group runs on production machine and use DR machine as its backup. The other group runs on DR machine and use production machine as its backup. Lets zJOS-XDI manages both machines as productions and DR in flip-flop according to each group position.
  • 23.
    zJOS-XDI Concept ofDR (cont’d) SYSPROD DR JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Production JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Production
  • 24.
    zJOS-XDI Concept ofDR (cont’d) DRC zJOS Jobs Scheduler SYSPROD JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Production JOB5 JOB9 JOB1 JOB3 JOB7 Group 1 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Backup JOB2 JOB4 JOB6 JOB8 Group 2 Production
  • 25.
    zJOS-XDI Concept ofDR (cont’d) DRC zJOS EMS Scheduler SYSPROD JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7 zJOS Jobs Scheduler SYSPROD JOB5 JOB8 JOB9 JOB6 Start JOB1 JOB3 JOB4 JOB2 JOB7
  • 26.
  • 27.
    zJOS Server DesignSupports up to 99 agent connections Support SAF exit interface for non-agent connection security checking Supports IPv6 Automatic ASCII-EBCDIC detection and translation. zJOS XDI z/OS (mainframe) Event Mgr Scheduler
  • 28.
    zJOS Agent DesignSimple and smart interaction protocols Simple and smart data structures IPv6 support No bother with ASCII-EBCDIC type of platform since it will resolved by zJOS Server automatically Agent
  • 29.
    Strategic Enterprise PlanOptions Extend R&D to develop various zJOS agents for all possible non-z/OS platforms. Lets users develop their own zJOS agents. Any one who expert in certain platform can develop zJOS agent for that platform Lets open source communities develop zJOS agents for open system platforms.
  • 30.
    zJOS in EnterpriseEnvironment Linux Agent zJOS XDI z/OS (mainframe) Event Mgr Scheduler Unix Agent Other Agent Linux Agent zJOS XDI z/OS (mainframe) Event Mgr Scheduler Unix Agent Other Agent
  • 31.
  • 32.
    Download Demo Should you curious, kindly download the demo package zJOS-XDI Notes: Packeage is in WinZIP file format Read README.txt before you install it To complete the trials, refer to the following files: InstallGuide.pps TrialGuide.pps UserGuide_EMS.pps UserGuide_Scheduler.pps
  • 33.
    Offering zJOS-XDI “crazyproject” is looking for sponsor or partnership or even acquisition. If you are representing a mainframe software vendor, you would find this zJOS-XDI project is much more cost-effective than you develop yourself. Take time and lots of resources to develop. Meanwhile, at the moment not many vendors to compete in this strategic market sector. Sponsorship from any skill building foundation who really understand and care of potential economic and moral aspect of such project to the developing country like Nusantara, is very welcome.