|
Mark wrote: >What would be the preferred method for checking >for Physical File Constraint Violations using >the native interface (ie ILE RPG Program)? >I'm trying to create service programs for file >I/O and would like to place as much of the field >level validation in the database as possible. I couldn't be so bold as to say preferred, but fundamentally, there isn't a very nice way of handling these. When an update falls over because of an RI violation, it literally falls over - you get an I/O error. I pass the file information feedback DS to a "standard" program to log the error, but my error _recovery_ is quite primitive. I post a generic message with the name of the constraint in the second level text so that a programmer can interpret for the user if required. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.