I developed a simple benchmark for Acucobol, which is a translation of another benchmark I did for xBASE products. (See Linux Journal #14, June 1995, p. 27.) This benchmark processed a file containing 33,830 records and was run on a 66 mHz 486 with a SCSI disk.
It's reasonable to expect that Acucobol would be noticeably slower than Flagship, since Flagship programs are compiled into machine code, and Acucobol programs are compiled into b-codes, which must be interpreted at run time.
Figure 1. Benchmark Results
Acucobol Inc. hosts a developers' conference in San Diego every year. The next one is September 18-20. I haven't been to one of these yet, but I've had good reports from them; attendees are treated well by Acucobol, Inc.
There are references in the manuals to GUI and mouse support, but they seem to be only for Windows NT. Acucobol, Inc. does seem to be interested in offering some sort of UNIX GUI support eventually.
This product will probably not be of much interest to hard-core Linux people; they would rather program in C for free than pay big bucks to use COBOL. It should be of interest to the Linux community, though, that Acucobol, Inc. went to the trouble of porting their product, because it gives Linux more legitimacy.
However, the Linux version of Acucobol should be of great importance to another community: system houses that develop and maintain COBOL application software. When these system houses sell a product to an end user, the end user must not only purchase the application, s/he must also purchase the hardware the application runs on and the rest of the software environment. For example, if the application runs under Windows 95 or SCO Unix, either the customer or the systems house must buy a copy of Windows 95 or SCO Unix. A system house that has a COBOL application to sell can now try to convince customers to accept Linux as the software environment instead and can offer a lower total cost to the customer.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide