 |
 |
 |
 |
 |
 |
 |
 |
 |
The above processing is all that is required to take a PLOG file and transform this file into usable data. This processing can certainly be done without any 3rd party tools, it can be done with 3rd party tools that cost well above $70,000 - or it can be done with NatQuery and NatCDC for a cost that is significantly less.
The reason that NatWorks products are so cost-effective is simple: We leverage what functionality you already own, and provide the functionality that is missing.
With other solutions, you pay a very dear price for what can only be called redundant functionality to the processing that ADABAS utilities already provide.
In proof of this statement, consider one of the most important aspects of the proper handling of ADABAS PLOGs: Record Decompression. In order to properly process an ADABAS PLOG into usable data, the PLOG records must be decompressed from the internal ADABAS format. Of all the processing that must occur on a PLOG, Record Decompression processing is by far the most CPU intensive aspects.
Fact: With the exception of NatWorks, virtually every other ADABAS PLOG solution on the market today will make you PAY for a “utility” to handle the decompression of PLOG records, when you already have this capability through existing ADABAS utilities.
Fact: On a single ADABAS mainframe file, ADASEL, will consistently out perform any 3 rd-party utility at decompressing records of interest by virtually any measure: CPU resources, CPU time, or Clock Time.
Fact: Since PLOG processing will be an ongoing activity, a process that ultimately must handle every transaction that occurs against your source file(s), even if the savings of using ADASEL were just minimal for a single PLOG processing run, when these savings are extrapolated across an entire year - these savings become huge.
Fact: To the best of NatWorks’ knowledge, Software AG does not publish the internal layout of an ADABAS PLOG. This raises a very interesting question: How can a third-party vendor properly understand all of the nuances that may internally exist in a PLOG, or become aware of any changes in this format, unless they use the output of the ADABAS utilities that SAG provides to handle the PLOG?