CXU - Business Case

In short CXU saves 63 hours yearly for each fulltime employed mainframe developer or mainframe supporter (DBA, test person, operations planner). In other words CXU enables you to put two more weeks of effort into one year without any extra work. CXU will provide larger savings for some and less for others. The assumptions for the savings you can acheive by using CXU is available below.

Why CXU is such a good investment

CXU has been underway for more than eight years in different prototypes. All prototypes have been heavily used. The experiences from daily usage shows that CXU saves between a half and one hour each day for the experienced, productive mainframe DB2 developer. The savings are primarily acheived, because the mainframe developer gets access to datasets and to DB2 directly from ISPF EDIT/VIEW instead of being forced to navigate through different ISPF tools. At the same time the SQL functions of CXU reduces the time it takes to develop performance efficient SQL statements, because it is possible to validate and test SQL statements directly from the source code. Thus CXU plays an important role in reducing the CPU consumption in the production environment.

The potential of CXU is not limited to mainframe DB2 developers, as all employees working with datasets and DB2 will benefit from using CXU. For these employees, CXU will save between a quarter and half an hour each day.

Another side of CXU is that it is a new mainframe tool, which will be highly appreciated by many mainframe people in a daily worklife where they feel PC software is stealing away their time. On the contrary CXU will give them more time, hence the slogan:

"Makes developers happy".

CXU is easy to install, does not require any special authorisations and does not require any general configuration. You only need to use time on the installation itself, which is just a matter of uploading a dataset to the mainframe, unpacking the dataset using one standard TSO command and copying two load modules from the unpacked dataset to a load library on the link-list. This is a one-off cost done in 10 minutes.

What a CXU business case may look like

In your mainframe IT-department 10 people works fulltime on mainframe DB2 development. They will daily save 30 minutes of work using CXU. On top of that you add test persons, DBA persons and operations planners. Let us assume 10 more people fulltime. Their daily time saving using CXU is estimated to 15 minutes. A fulltime employee works app. 200 days a year (in Denmark). CXU saves these 20 persons for 10 * 30 * 200 + 10 * 15 * 200 = 90.000 minutes of work which is equivalent to 1.500 hours annually.

As CXU is for free!! you free up one full-time employee by fully implementing CXU in this example.