|
CPF502B is a error stating "error in trigger program" Since triggers are at the DB level, it doesn't matter who or what does the update/add that "fires" the trigger. I suspect but I haven't actually tried this, but I bet you can put a trigger on ANY file and cause it to fire when RPGII or any other program that updates/adds to the file. The trigger program would proably "have to" be RPGIII at least..... > Jim Franz wrote: > > Is there any known problems with a trigger pgm on a file updated by > various pgms, > including s36 screen & batch, rpg3 & rpg4 & rpgsql? Error is cpf502B, > very vague. > Only halting when s36 pgm was involved, and not halting on every > update. > Previous msg in joblog indicates reference to missing or deleted > object, > but doesn't say what it was looking for.At V4R4 cum 00350 and very old > database > group ptf (from 99) - any help appreciated > jim +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.