Re: Create SQL Trigger Issue

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')
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.