|
RE: RPG Trigger Pgm Eric Don't bother with the offsets or SUBST business. Movel the After image into an externally defined data structure(Defined by the same file as being triggered). Then you can manipulate the field names directly with EVAL's MOVE's Z-adds whatever you like(with compares, IFEQ etc) then MOVEL the externally defined data structure back into the Image field. or whatever. why be complicated. John Carr I'm trying to work up a sample DB trigger pgm (RPG) to validate records at *insert and *update. Documentation (DB2 for OS/400 Database Programming V3R7) indicates that I can modify the new record image in the trigger buffer, but I can't see any way to apply changes to the trigger buffer at offset value. For example, I want to update a field RCDSTS to "SC04" to indicate the record contains errors before writing a record to a Status History file. I can't see how to move SC04 into the trigger buffer @ offset value corresponding to this field. (<-- Huh? I think I just confused myself....) I guess I'm looking for the opposite of SUBST.. something that will let me move a value into a field at location X. Am I going to have to learn basing pointers or what? Any hints, suggestions, or samples would be appreciated. Thanks. Eric A DeLong ericadelong@pmsc.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-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.