FREQUENTLY ASKED QUESTIONS

Cloud Compiling is a family of virtualized z/OS language compilers that either eliminate or reduce the need for software licenses in your mainframe environment. Whether installed in your private cloud or externally hosted, Cloud Compiling delivers virtual compiling with all of the benefits of cloud computing, including lower costs, improved efficiency, increased system controls and the ability to scale quickly.

Cloud Compiling directs your source code and any other pertinent information (i.e., copy members) to a remote cloud-based compile machine, where it is compiled using the same IBM Compiler, and returns the completed module back to you. As a result, the cloud-based compiler performs exactly the same functions as your existing compiler – but with a minimum of 50% cost savings and all the benefits of Cloud Compiling.

Our virtualized language compilers automate the process of transmitting source code to a remote compile machine where it compiles using your existing compiler. We then transmit the object code and listing back to your datasets. The process is seamless to users, developers and operators.

Cloud Compiling is supported on all versions of IBM® z/OS®.

It is really your choice; Cloud Compiling is available for installation in your private cloud, or can be externally hosted with Cloud Compiling’s Secure Cloud.

Cloud Compiling is available for all versions of COBOL, PL/1, Fortran and C++.

Installation is as simple as downloading a zip file installing it on your mainframe.  And with our Proof Of Concept (POC) package, you be up and running with a test drive of the software in less than an hour.  For full customization and detailed installations, see our installation guide located here.

You recognize cost savings by suspending your existing compiler licenses and using the same version provided via the cloud by Cloud Compiling. You can also realize significant savings by having all of your contracted ISV’s use this process, offloading their MSU’s to our mainframe and lowering your rolling 4-hour rolling averages (R4HA).

We simply share in your monthly savings, then structure your license to guarantee a minimum cost savings of 50% per month off your existing license fees.  We do not ask for a long-term commitment or any money upfront; this is the essence of a cloud model for your mainframe.

Because compilers are typically licensed monthly, and there is no upfront investment, if you move to Cloud Compiling this month, you will recognize your savings the following month. You will begin a ROI immediately.

Customers using Cloud Compiling’s Secure Cloud are secured by RACF, we also support all of the latest security technologies such as TLS, SSL, VPN and PassTickets.

Cloud Compiling supports invocation from CALL, LINK, or ATTACH in the same manner as your existing compilers.

You continue to run any pre-compiler before your compile jobstep, just as you do now. You pass the output of the pre-compiler to the virtual compiler just like you would pass it to your existing compiler.

You continue to run that product exactly as you do now and have the virtual compiler pass its output to your post-processor.

You continue to link-edit just as you do now. Cloud Compiling does not replace the link-edit or binder, which is part of z/OS DFSMS, not a separate product.

You continue to link-edit just as you do now. Cloud Compiling does not replace the link-edit or binder, which is part of z/OS DFSMS, not a separate product.

Most often, you will save CPU resources with Cloud Compiling. Cloud Compiling off-loads most of the work to the remote compiler machine, resulting in up to 70% less CPU time than the IBM Compiler. One typical customer COBOL compile of 5489 statements used 3.91 CPU seconds, as opposed to the IBM compiler, which used 6.02 CPU seconds on the same mainframe – a 35% savings. Here is another customer case study.

Compile time will vary and generally only takes seconds, but the quick answer is no. The 5,489-statement compile (mentioned above) required transmission of approximately 1.8 megabytes of data, including source code, control statements, listing and object code. A typical corporate T1 line runs at 1.5 megabits, or about .2 megabytes per second, so that is less than 10 seconds’ worth of data. Depending on how busy your mainframe is, the elapsed time to complete the entire process may take less time than they do now.

We support every IBM compiler option.  In addition to our long-term membership in IBM PartnerWorld we are also part of IBM’s Confidently Disclosure Group.  This gives us a year of advance notice of any changes needed to ensure we are always able to support the latest options and features.