homeabout usservicesproductscontact us


Download
Spec Sheet

 


View Presentation

(requires Macromedia Flash)

 

 


SYSPOINT Virtual Compiler Technical F.A.Q.

Q
What is the idea behind a virtual compiler?
A

Our software – our virtual compilers – automate the process of transmitting your source code to a remote compile machine where it is compiled using your existing IBM or third party compiler.   We then transmit the object code and listing back to your datasets.  The process is seamless to users, developers and operators.

______________________________________________

 

Q
How do you do that?
A

The SYSPOINT Virtual Compiler (SVC) directs your source code and any other pertinent information (i.e., copy book info) to a remote compile machine, where it is compiled using your IBM or third party 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 30% savings over your existing compiler costs - and increased mainframe utilization. 

The SVC can be hosted on a designated mainframe in your data center (insourced) or hosted by SYSPOINT (outsourced.)

______________________________________________

 

Q
How do we know we will really save money?
A

SYSPOINT charges a fixed percentage of what IBM charges you, so you know in advance exactly what your savings will be. 

You can estimate your savings now by using the Savings Calculator at www.syspointusa.com.

SYSPOINT charges on the same month-to-month basis as IBM, so there’s is no risk. 

______________________________________________

 

Q
What about the security of our source code?
A

SYSPOINT utilizes all available security measures, including RACF, PassTickets, VPN, etc.

______________________________________________

 

Q
We don't run the compiler directly from JCL – some other product loads it. Do you support that?
A

SYSPOINT SVCs support invocation from CALL, LINK, or ATTACH in the same manner as the actual IBM compilers.

See our product documentation at www.syspointusa.com for details.

______________________________________________

 

Q
We run the CICS or DB2 pre-compiler – how are you going to handle that?
A

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 SYSPOINT Virtual Compiler just like you would to the IBM compiler.

______________________________________________

 

Q
We use a product that processes the compiler output. How will you handle that?
A

Using the same process as for pre-compilers, you continue to run that product exactly as you do now and have the virtual compiler pass its output to your post-processor.

______________________________________________

 

Q
How do we link-edit?
A

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

______________________________________________

 

Q
What about COPY members?
A

One of the functions that the virtual compiler performs is scanning.  SYSPOINT Virtual Compilers scan your source code for COPY statements and transmitting the appropriate members just like your SYSIN dataset. In other words, COPY and BASIS (and PL/I, Fortran, and C-include) present no problem for the virtual compiler. Everything is transparent to your programmers.

______________________________________________

 

Q
How fast is it?
A

For most compiles, the virtual compiler uses up to 70% less CPU time than the IBM compiler because it off-loads most of the work of the compile to the remote compile machine. For example, one typical customer COBOL compile of 5489 statements used 3.91 CPU seconds – as opposed to the IBM compiler which was used to consume 6.02 CPU seconds on the same mainframe – a 35% savings.  Nearly all compiles will save you CPU resources. ______________________________________________

Q
But transmitting all of those files – isn’t that going to slow the compile down?
A

Less than you think. That 5489 statement compile (above) required the transmission of about 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’s less than ten seconds worth of data. Depending on how busy your mainframe is, the elapsed time to complete the entire process may actually take less time than they do now.

______________________________________________

 

Q
Which compiler parameter options do you support?
A

We pass whatever options you code to the actual IBM compiler, so we support every IBM compiler option except the seldom-used facility that lets you write a compiler exit to do your own compiler I/O.

______________________________________________

 

Q
What about compiler maintenance levels?
A

SYSPOINT is committed to keeping all of our compilers up to current IBM maintenance levels.

______________________________________________

 

Q
What do we do next?
A

Contact SYSPOINT at www.syspointusa.com or info@syspointusa.com to start saving money now.


Syspoint and Virtual Compiler are trademarks of Syspoint LLC.
The following terms are trademarks of the IBM Corporation in the United States or other countries or both:

IBM®, OS/390®, RACF, z/OS®

SYSPOINT | syspointusa.com
630 Main St. N. 
Suite 312
Stillwater, MN 55082 USA

 
 info@syspointusa.com
 
Toll Free:  866-SYSPOINT (866-797-7646)
Fax:  612-920-0142

copyright 2008
Virtual Software Solutions
 Site Developed and Hosted by:
Synergy Soup Interactive