FAQs

  1. What is Cloud Compiling?
  1. Cloud Compiling is a family of virtualized z/OS language compilers that reduce the need for multiple software licenses in your 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.
  1. What is a virtualized language compiler?
  1. 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.
  1. Is Cloud Compiling software or a service?
  1. Both.  Cloud Compiling is available for installation in your private cloud, or can be externally hosted with Cloud Compiling SaaS.
  1. What platforms do you support?
  1. Cloud Compiling is supported on all current versions of IBM z/OS.
  1. What programming languages is Cloud Compiling available for?
  1. Cloud Compiling is available for most versions of COBOL, PL/1, Fortran and C++
  1. Do I continue to use my existing compilers, or replace them with Cloud Compilers?
  1. There is no migration - you continue to use your existing compilers. With Cloud Compiling, you simply remove redundant installations from your environment, and your compiler licenses are located on just one mainframe. Because you continue to use your existing compilers, there is no change from your programmers perspective. They compile just like they do today, using the existing compilers.
  1. What is required for installation?
  1. Installation is easy and takes less than a day per programming language. The primary tasks are the upload and TSO RECEIVE of a single load library on the machine on which compiles will be submitted, and the creation of a userid on the machine on which the IBM compilers will actually run. There is no data migration, IPL's, authorized libraries, supervisor calls, z/OS parmlib changes and no changes to your existing JCL. For more information, see our installation guide at www.cloudcompiling.com/installation.html .
  1. How do I save money with Cloud Compiling?
  1. You recognize cost savings by centralizing your compiler licenses to one mainframe. To maximize your savings, leave your existing compilers on your lowest MSU rated system, remove redundant installations from your highest rated systems and install the Cloud Compiler, and immediately reduce your license fees.
  1. How is Cloud Compiling licensed?
  1. We simply share in your monthly savings and structure your license to guarantee a minimum cost savings of 50% per month off your existing fees.
  1. How long will it take before I recognize the guaranteed savings each month?
  1. 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. The ROI is immediate.
  1. How does Cloud Compiling actually work?
  1. Cloud Compiling directs your source code and any other pertinent information (i.e., copy members) to a remote compile machine, where it is compiled using your existing compiler, and returns the completed module back to you. As a result, the virtual compiler performs exactly the same functions as your existing compiler - but with a minimum of 50% cost savings and all the benefits of Cloud Computing.
  1. What about security?
  1. Many of our customers use a small in-house mainframe for their compiles, so your source code never leaves your secure internal network. It's just as secure as it would be if you were not using a cloud compiler. For those customers using our outsourced compile server, Cloud Compiling SaaS, we support all of the latest security technologies such as TLS, SSL, VPN and PassTickets.
  1. What if we don't run the compiler directly from JCL, but another product loads it?
  1. Cloud Compiling supports invocation from CALL, LINK, or ATTACH in the same manner as your existing compilers.
  1. What if we run the CICS or DB2 pre-compiler?
  1. 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.
  1. What if we use a product the processes the compiler output?
  1. You continue to run that product exactly as you do now and have the virtual compiler pass its output o your post-processor.
  1. How do we link-edit?
  1. 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
  1. What about COPY and INCLUDE members?
  1. The Cloud Compiler scans your source code for COPY or INCLUDE statements and transmits the appropriate members, just like your SYSIN dataset.
  1. What about performance?
  1. 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 ypical 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.
  1. Won't transmitting all of those files slow the compile down?
  1. Compile time will vary, but typically no. The 5489 statement compile (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 ten 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.
  1. Which compiler parameter options do you support?
  1. We support every IBM compiler option.
  1. What about compiler maintenance levels?
  1. Cloud Compiling supports all current IBM maintenance levels.

 

Close it