 Total
Automation Solution for z/OS
FOR SALE |
|
Total
Automation Solution for z/OS
FOR SALE |
| Product Summary | ||
| zJOS-XDI - Integrated Automation & Scheduling Solution for z/OS | ||
| Product name |
zJOS-XDI |
|
| Functions |
An integrated automation solution,
which includes
Click the above icon to see further about the products. Notes:
|
|
| Platform |
Currently available platforms:
|
|
| Product type & characteristics |
Executable codes:
Source codes:
Hooks/Offsets:
|
|
| Development terms |
Development date:
Launching date;
|
|
| Strong points |
zJOS has 3 strong points of its
competitors:
|
|
| Prospects |
Automation is very strategic IT
solution. On the right hand, zJOS-XDI will be very prospective
product, in accordance to the following reasons:
|
|
| Local marketing |
In Indonesia, zJOS-XDI marketing is
handled by PT Sumbersolusindo
Hitech (SSH), which acts as sole distribution for local market.
Contract with customers are handled by SSH and made between SSH and
customer. Between SSH and the author/owner is made in separate
contract. Current sales status reported by SSH as follow:
Notes:
|
|
| Demo & brochures |
Demo is located
here, then click the appropriate link to
download the demo. Downloaded materials are bundled in a ZIP file,
which should consists of:
Author strongly recommend everyone who interested not to believe it until he/she proves it him/herself by doing some trials. Installation procedure is very easy, just follow instructions in README file. There are 2 packages, zJOS 2.1.3 and zJOS 2.1.9 zJOS 2.1.3 package:
zJOS 2.1.9 package:
Should you receive other than both above packages, kindly contact directly to the author by phone or email as shown in contact section below. |
|
| Constraints |
Author/Owner is facing complicated constraints to
market and enhance zJOS-XDI:
|
|
| Offerings |
As author/owner understand the above
constraints, he then concluded that zJOS-XDI is no future unless it's
handled by the right corporate. Therefore he has decided to sell the
whole zJOS-XDI materials and copyright/patent to any vendor who
interested. Understand the above sales status, he feels no
bargaining power to position zJOS-XDI in normal acquisition price.
Therefore he decided to offer very cheap price:
Just found a gold in the trash basket!!!
Once zJOS-XDI is sold, author will also available to continue maintain and develop zJOS-XDI in separate contract. He also available to handle any offshore systems software development project for z/OS and VM. Deliverable materials
Notes
|
|
| Contact |
Deru Sudibyo
(author/owner)
Emails: Phones:
Notes:
|
|
zJOS-XDI - an Integrated Mainframe Automation Solution
|
As an integrated automation solution, zJOS-XDI is a proven package. However, currently only supports z/OS platform. As shown in the project summary, all other platforms developments are pending for finance reason, since author unable to do it himself. Nevertheless, author has prepared agent technology design to accommodate other platforms involvement in zJOS enterprise automation solution. The agent technology has proven in networked z/OS environment. By completing with agent for Linux, OS/400, Unix and Windows systems, author believe zJOS-XDI will be one of the top ranked enterprise automation solution in the market. The inspiration and idea why zJOS-XDI project was started, is because author knows the weaknesses of the existing such solution in the market which mostly because their products derived from very old legacy. Especially for the workload scheduling system, most of existing products in the market do not support job-step level triggering mechanism, nor flexible Boolean logic CC multi-testing for both job and job-step level triggering mechanism. Hence, compared with existing mainframe automation product in the market, zJOS-XDI has a killing punch to get more chances. Should you curious to prove it, please kindly download this demo and install it on your z/OS system. Follow provided manuals to have it properly setup, and then do some trials to prove it. |
|
The core of zJOS/Puspa (scheduler component) by design has strong points against its rivals, which are combined workload pipelining and multi-Boolean logic CC testing mechanism. Both features not only just give chance to users managing their workload more efficient, rather, also encourages users draw their own idea of recovery mechanism in their scheduling flow. Workload Pipelining Means job-step level triggering mechanism, especially for workload type of batch-job and STC. Inter-jobs dependency, in fact, not always depend on final result of predecessors. In most cases, a job depends on the readiness of its datasets. However, trapping the datasets status is not a good method since a dataset can be processed by many jobs which can yield many opens and closes events occurrences during certain time range. The best way to have an exact readiness status of a dataset for a job is by knowing which job-step was recently accessing it. Considering this idea and fact, this "crazy project" then design zJOS/Puspa with job-step level triggering mechanism as a standard core function to provide pipelining method of workload management. Multiple Boolean Logic CC Testing zJOS/Puspa by design, lets users to decide to where schedule flow is directed, instead of just success and fail. This design also lets users to have their schedule much more flexible. A job can have dependencies with multi sets of predecessors, by using multiple stages of AND and OR logic operators, instead of just a series of AND like in ordinary scheduler products. |
|
Integrated EMS for Automation
 |
Within a networked z/OS hosts (TCP/IP network), zJOS/Sekar capable to trap or capture occurrence of any type of system event such as message, command, end-of-job (EOJ) or end-of-jobstep (EOS) on any host in the network. Users can ask zJOS/Sekar to trap system event on any host and executes one or more actions on any one or more hosts in the TCP/IP network. Action can be a single or a set of commands, reply to WTOR message, or rule. Users don't need parallel sysplex to get an integrated EMS properly work using zJOS/Sekar. Rule can be any program which run as an STC. Although all provided samples are rexx modules, you however, may develop rule in other language you like. For rexx program, zJOS/Sekar provides a set of special functions related to automation mechanism. |
Integrated Workload Scheduler
|
Within a networked z/OS mainframe hosts, zJOS/Puspa capable to trap job or job-step status information exactly at the time the job or job-step terminated, regardless on which host the job or job-step is running. . Therefore, by using this internal function, Puspa allows user to draw schedule flow crossing inter-hosts. Combined with its strong points in workload pipelining and multi-logic CC testing, users are encouraged to manages and automate their workload exactly as their own idea. Users don't need parallel sysplex machine to get an integrated scheduling properly work using zJOS/Puspa. Such features can also be used when users want to explore their DR system to work more efficient as coproduction, instead of just a backup system. |
|
About the "Crazy Project"
|
Why zJOS-XDI is called as "crazy project"? Because, the project run just like a gamble. The idea, research, assessment, planning, design, and initial development were done by the author alone without any sponsorship or formal body behind the project. The gamble was because author had to quit from CA contract in mid 2002 just for this project. To get survive, author was doing some freelance jobs in both IT and non-IT sectors. Fortunately, in early 2004, while the initial codes were completed, author got access to client's z/OS 1.4 system. That was a chance for the author to assemble and bind the codes as his initial product skeleton. He then sell his idea to the client. He was lucky again. Client agree to license one of his 3 solution products, spool/report distribution system (zJOS-XDI/AutoXfer) to replace existing vendor's product which was very unstable by the time. AutoXfer was then installed in client's development system, and in mid 2004 was promoted to the production system. Come up with this relationship, author then always have chance to access to z/OS system to continue the project until today. . In mid 2005, zJOS/Sekar (EMS) and zJOS/Puspa (workload scheduler) were completed and installed in the development system for functional testing. In early 2006, both products were proven as a proper EMS and workload scheduler. To make it more fair, both zJOS products were competed against vendor's products. zJOS was proven as a winner. By the time, both product were also installed in other client for trials and compared to vendor's products they currently use. This is the different vendor. Again, zJOS won. In both cases, zJOS won because of its "killing punch" which normally not supported by most of vendor's products. In mid 2006 zJOS/Sekar (EMS) and zJOS/Puspa (workload scheduler) were then launched as commercial products. Since that, some mainframe sites in Indonesia then have been doing long long trials, until, finally one of them decided to accept zJOS/Sekar and zJOS/Puspa in their production system to replace the existing vendor's products. No wonder, they had to learn that long, because they were also facing the dilemma. They are interested to the zJOS functionalities, meanwhile, they also doubt its long term support. Anyway, now all of zJOS-XDI products have been proven in client's production system. Considering the above fact, zJOS products are supposed to be a marketable solutions.. Besides, currently there are not many competitors. The famous players on this sector so far only BMC, CA, ASG and IBM. The basic design of zJOS was proven better. Unfortunately, zJOS has 2 weaknesses which are somehow very mandatory. First, zJOS does not support multiplatform yet. Second, zJOS does not have corporate guarantee, as it is just only run under a "crazy project". Although currently zJOS is supported by quite solid technical team, both weaknesses constraint zJOS to go wider market. Author is facing "chicken and egg" dilemma. Playing on wider market without extending the support team is impossible. Extending the team needs more cost and no guarantee can play on wider market. Meanwhile, zJOS-XDI project needs to continue developing agent for non-z/OS platform. This will need cost since author can not do himself as his expertise is only mainframe. Project needs a number of non-mainframe architectural programming experts to develop non-mainframe agents for a number of platforms which to be included in the zJOS solution package. This will need extra cost, whereas total earned revenue from local market so far can't even cover author's cost of living . The only way to keep project running and zJOS future, is either partnership with or totally sell the project to certain software vendor who doesn't have overlapped solution. Author believes every vendor want to have complete solution to compete in the market. Besides, automation solution is quite strategic. However, to develop it is not very easy and needs quite long time. Whereas this "crazy project" is ready on the way. |
