×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Did you get this resolved?

If not, then you may have to run
RCLSTG SELECT(*DBXREF)

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Jim Smith" <jimsmith@xxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/29/2004 02:57 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
midrange-l@xxxxxxxxxxxx
cc

Subject
SYSTRIGGER in QSYS2 type *FILE not found






Hi guys,

I have an application that is trying to create a table trigger on our 
AS/400 without success. The error message states "[IBM][Client Access 
Express ODBC Driver (32-bit)][DB2/400 SQL]SQL0204 - SYSTRIGGER in QSYS2 
type *FILE not found. - SQLSTATE: S0002". If I open up a Client Access 
emulator session and issue WRKOBJ OBJ(*ALL/SYSTRIG*), the file SYSTRIGGER 
does not exist anywhere in the system. We are on V5R1M0. Is this file a 
system file? Should it even exist? If so, how do I get it there?

By the way, here are the results of WRKOBJ OBJ(*ALL/SYSTRIG*):

 SYSTRIGCOL  *FILE     QSYS2       LF
 SYSTRIGDEP  *FILE     QSYS2       LF
 SYSTRIGUPD  *FILE     QSYS2       LF

Any help is greatly appreciated,

Jim.



_______________________________________________
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.



This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.