1. Systems events management for automation
2. Automatic workload scheduler (with pipelining method)
3. Spool output management 

1. zJOS-XDI Core development for z/OS platform
2. zJOS Agent development for z/OS platform
3. zJOS Agent development for other z platforms
4. xJOS Agent development for Linux/Unix platforms
5. pJOS Agent development for Microsoft platform
6. ?JOS Agent development for other non-z platforms
7. xJOS-XDI Core development for Linux/Unix platforms
8. pJOS-XDI Core development for Microsoft platform
9. ?JOS-XDI Core development for other non-z platforms

1. We are entering automation era
2. Events management is the core of automation for any type of computing environment
3. Workload scheduling is the core of automation for batch computing environment. 
4. Certain type of businesses will never batch free. 
5. Not many vendors provide automation solution, especially for event management and workload scheduling.   From about 300 mainframe vendors, there are less than 10 vendors have such solution. 
6. Most of scheduler solutions are legacy stuffs which do not support pipelining (step-level) and flexible Boolean multi stages condition test triggering methods    zJOS-XDI as a modern automation solution supports combined of both methods to encourage users to draw their scheduling flow and various schedule-recovery flows exactly as their own idea.   
7. Automation solution is quite expensive solution.    

To either be a partner or acquire zJOS-XDI, partner or buyer does not need the whole stages of project are done.  Because, for non-mainframe parts are not too hard to find expert to join.  As long as there is enough budget, project will certainly safely progressed. 

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.       

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 benchmarked 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 "brand image", as it is just only run under author's "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 on the achievement.  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. 

The author and owner of this "crazy project" is Deru Sudibyo, a Nusantaran (Indonesian) mainframe expert.  He crazily left his normal professional life and run this project is only for one thing, "just to prove that Nusantarans also capable to contribute in the core of IT industry, instead of just as users".  By doing this, when he got successful, he want to be a pioneer to encourage more talented people in Nusantara - Indonesia to take the same way.  

Anyone who really understand IT, is supposed to be able to understand how prestigious this crazy project.   For mainframers can even know deeper by downloading demo and doing some trials.  He expect what he has done is an evident which can change mindset of IT world community that Indonesia is also a good land of IT outsourcers, even for mainframe technology. 

At the time being, in order to survive while running this project, author has to keep his cash-flow meeting day-to-day cost of living, by offering freelance services in mainframe system software development and HR development project to anyone who need it.