|
One problem with this idea....the user would have to have an exclusive lock on the file(s) to add the constraint. In a live production environment this would hardly be feasible. The most flexible way to do this realistically in a production environment is through software validation. Use control table(s) that can be modified on the fly & service programs,etc to perform necessary validation functions. It would STILL be a major pain to design, code & implement but it is a do-able project. Thanks, Tommy Holden -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx Sent: Wednesday, December 21, 2005 10:33 AM To: RPG programming on the AS400 / iSeries Subject: Re: Possible SPAM: RE: Dynamic Variable Names in RPGLE One radical way for the users to define their own rules might be through ADDPFCST. Write/update the record with the (e) extender and check for the error. I believe the file information data structure should be filled in with the name of the constraint. (name 'em, don't use system generated names). I am not suggesting the users enter in the raw ADDPFCST command but you handle that programmatically. Rob Berendt
This mailing list archive is Copyright 1997-2026 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.