|
We have a new process by which we are using FTP to download a file from our Unix Oracle box to the AS/400. The *very* preliminary test data has shown some cases of decimal data errors. I have decided to implement some kind of a pre-processor that checks to see if there are *any* DDEs *anywhere* in the file; if a DDE is found, I'm rejecting the entire file. Is there a OS function, trade rag "program of the month", or other published code that takes the filename as a parameter and checks the file for DDEs? FWIW, all numerics are defined as zoned decimal - no packed data in this file. I tried using CPYF and was surprised that the bad data copied without incident. I did get the CPYF to bomb with CPF2906 by specifying INCREL((*IF SWPMSL *LE 999.99)) Field SWPMSL is defined as 5 digits, 2 decimal, so I figured any valid value would pass this test. The problem is that I've got several numeric fields in this file, and I would like to keep the solution generic enough to accommodate future definition changes to the file without having to modify the INCREL parameter. Also, the INCREL parameter is limited to 50 field value tests, which normally would not be a problem, especially in this case, but it would be nice not to have to worry about this limitation. NOTE that I do NOT want the function to "correct" the data; I just want to know if there's at least one DDE. I checked the archives, but could not find any reference to the solution I am seeking. Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.