|
1
|
- The Integrated z/OS Automation Solution
|
|
2
|
|
|
3
|
- Event management system (EMS)
- Automates actions 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 scheduling
- Automates JES2-based jobs scheduling.
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
|
- Run on z/OS or OS/390 platforms with JES2
- Provides EMS functions (zJOS/Sekar)
- Provides jobs scheduling functions (zJOS/Puspa)
- Support networked-z/OS total automation
- Provides spool distribution functions (XDI/AutoXfer)
|
|
5
|
|
|
6
|
|
|
7
|
- zJOS/Sekar – EMS Solution:
- Facilitates users to define set of actions against each selected event.
- Automates 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) and end-of-step (EOS) types of 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.
|
|
8
|
|
|
9
|
- zJOS/Puspa – Jobs Scheduling Solution:
- Facilitates users to define jobs schedule flows.
- Automates all user’s defined jobs schedule based on job status event
occurrences.
- In networked z/OS hosts, predecessors-current-successors relationship
can be crossed among hosts in the network.
- Features:
- Supports both step-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.
|
|
10
|
- Workload pipelining – the most efficient workload managemet.
- By supporting job-step level triggering/tracking mechanism, schedule
flow path can be minize to lower turn around time.
- Boolean logic CC multitesting – the most flexible workload management.
- By supporting multigroup boolean logic comparison of CC in 2
|
|
11
|
- 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 minize to lower turn around time.
|
|
12
|
|
|
13
|
- 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.
|
|
14
|
|
|
15
|
- 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
|
|
16
|
|
|
17
|
- Does 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.
|
|
18
|
- 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.
|
|
19
|
|
|
20
|
|
|
21
|
|
|
22
|
|
|
23
|
- Supports up to 99 agent connections
- Support SAF exit interface for non-agent connection security checking
- Supports IPv6
- Automatic ASCII-EBCDIC detection and translation.
|
|
24
|
- 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
|
|
25
|
- 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.
|
|
26
|
|
|
27
|
|
|
28
|
- Should you curious, kindly download the demo package zJOS-XDI version
2.1.3
- 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
|
|
29
|
- zJOS-XDI package is for sale.
- If you are representing a mainframe software company, you would find
this package is much more cost-effective than you develop yourself.
- If your company already have such products, you could still consider to
integrate them with zJOS to achieve optimum solution. zJOS author would like to do it for
you.
- Detail offering and contacts could be found in cover letter (file
zJOS-XDI Cover_letter.doc) in zJOS-XDI version 2.1.3 zip file.
|
Notes