|
Dave Smith, et al, Yes, there is a TABLE... "QSYS2"/"SYSTRIGGER". Therefore, is there any reason why you couldn't do things the SQL/DB2 way... use a SELECT statement and then an UPDATE or just an UPDATE? I think you are looking for columns: A.OPERATIVE, A.ENABLED. BTW, the query for the full table looks like (some columns have been cut off): SELECT -- Columns A.TRIGGER_SCHEMA, A.TRIGGER_NAME, A.EVENT_MANIPULATION, A.EVENT_OBJECT_SCHEMA, A.EVENT_OBJECT_TABLE, A.ACTION_ORDER, A.ACTION_CONDITION, A.ACTION_STATEMENT, A.ACTION_ORIENTATION, A.ACTION_TIMING, A.TRIGGER_MODE, A.ACTION_REFERENCE_OLD_ROW, A.ACTION_REFERENCE_NEW_ROW, A.ACTION_REFERENCE_OLD_TABLE, A.ACTION_REFERENCE_NEW_TABLE, A.SQL_PATH, A.CREATED, A.TRIGGER_PROGRAM_NAME, A.TRIGGER_PROGRAM_LIBRARY, A.OPERATIVE, , A.THREADSAFE, A.MULTITHREADED_JOB_ACTION, A.ALLOW_REPEATED_CHAN A.TRIGGER_UPDATE_CONDITION, A.LONG_COMMENT -- Tables FROM "QSYS2"/"SYSTRIGGER" A Dave
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.