COBOL software for XML generation & parsing, AES encryption, data compression and source code obfuscation from Redvers Consulting

Technical Solutions for COBOL

Germany

USA, Canada, Australia, UK

COBOL XML conversion, AES encryption, data compression and source code obfuscation software

Redvers Compression Device - Frequently Asked Questions

Why have you written this product in COBOL?

We've taken the unusual step of writing and delivering this device in the form of COBOL source code subroutines because we understand how important it is to have a product that is easily integrated with existing applications.

Another advantage is that customers already running COBOL applications will already be familiar with the terminology, characteristics and capabilities of COBOL based programs.

What are the technical limitations?

As the product is written in COBOL and compiled using the standard site compiler, the limitations are the same as those placed on all other applications at the site.

Can I use another product to decompress data compressed by the Redvers Compression Device?

No. The Redvers Compression Device uses a unique algorithm to compress and decompress data and therefore other products will not be able to interpret the necessary bit patterns.

Is this device compatible with ASCII as well as EBCDIC based character sets?

Yes, all our products and devices run on ASCII and EBCDIC platforms. No code changes are necessary.

Is this device compatible with sites using "little-endian" binary storage?

Yes, all our products and devices will run on "big-endian" and "little-endian" platforms. No code changes are necessary.

Can I use this device to encrypt data?

No. Data compressed using the Redvers Compression Device, may look similar to an encrypted data file but it is not secure from someone trying to access your data. Please use our Redvers Encryption Device to safely encrypt/decrypt your data.

What are the benchmark statistics?

Actual compression rates range from 35% to 75%, depending on the length of the input data string and the length of the "sliding window".

Compression time is 0.3 megabytes per CPU second (using a "sliding window" of 400 bytes) and decompression is more than 14 megabytes per CPU second. All benchmark timings were performed on an IBM zSeries mainframe running z/OS 1.10.

You haven't answered the question I had in mind.

If your question isn't listed above please use our Contact page to ask any questions you may have and we will provide an answer as soon as possible.

Download a free 30 day trial here...