× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Could have SWORN I done this before and looking in OPS NAV at existing
triggers it looks the same. Searched InfoCenter and I don't see a
reasoneither, might be lack of sleep, anyways I keep getting the following
in interactive SQL:

CREATE TRIGGER UNICMFIL/DEGREECONFERRED AFTER UPDATE OF RSI4AA ON
UNICMFIL/DGRHSP REFERENCING OLD AS OLD_ROW NEW AS NEW_ROW FOR EACH
ROW MODE DB2ROW WHEN ( OLD_ROW.RSI4AA <> NEW_ROW.RSI4AA )
BEGIN ATOMIC
INSERT INTO UNION/DGRCONFERP (RSNMID, OLD_ROW.RSI4AA ,
NEW_ROW.RSI4AA , USER, CURRENT DATE, CURRENT TIME) WITH NC
Keyword DATE not expected. Valid tokens: ) ,.

What OBVIOUS thing am I missing..... (and yes those date fields ARE 7 long,
vendor's way of dealing with Y2K)

The DDS for the DGRCONFERP file is:

A R RDGRCONFER
A RSNMID 9S 0 TEXT('Name ID')
A COLHDG('Name ID')
A OLRSI4AA 7S 0
A COLHDG('Old Date Conf')
A NWRSI4AA 7S 0
A COLHDG('New Date Conf')
A USERHS 10A
A TEXT('User Who Changed')
A COLHDG('User Who' 'Changed')
A DATEHS L
A TEXT('Changed Date')
A COLHDG('Changed' 'Date')
A TIMEHS T
A TEXT('Changed Time')
A COLHDG('Changed' 'Time')

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.