|
I think what IBM is saying is that CRTDUPOBJ is not up to handling all the "properties" of objects created via sql. They are saying use SQL because CRTDUPOBJ isn't going to handle it. Now, what is different about an object file, with a trigger, created the "old way" versus the SQL way? jim franz----- Original Message ----- From: "Mark Allen" <allenmar@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Tuesday, December 13, 2005 4:56 PM Subject: RE: CRTDUPOBJ of file with trigger renders trigger inoperative
Sorry, long weekmeant that the IBM answer was to use SQL, no way in DDS (if I understand this thread right, which today is iffy)IBM answer "you should just modify the SQL statements to create them to the new library. It will not work if you mix them as you were."rob@xxxxxxxxx wrote: I don't understand the comment. Couldn't a trigger be created on a DDS created file with ADDPFTRG? And if you do the CRTDUPOBJ, SAVOBJ/RSTOBJ or SAVLIB/RSTLIB rstlib(DiffLib) wouldn't you have the same effect? No, I don't see this as a DDS vs SQL war at all. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Mark Allen Sent by: midrange-l-bounces@xxxxxxxxxxxx 12/13/2005 04:07 PM Please respond to Midrange Systems Technical Discussion To Midrange Systems Technical Discussion cc Fax to Subject RE: CRTDUPOBJ of file with trigger renders trigger inoperative Just another "push" to abandon DDS for SQLmaybe? rob@xxxxxxxxx wrote: Not me either. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Wilt, Charles" Sent by: midrange-l-bounces@xxxxxxxxxxxx 12/13/2005 03:15 PM Please respond to Midrange Systems Technical Discussion To "Midrange Systems Technical Discussion" cc Fax to Subject RE: CRTDUPOBJ of file with trigger renders trigger inoperative I open a PMR about this issue. Here's the last reply I got from IBM. The develop said the issue is that you are mixing SQL tables and triggers with non-SQL CRTDUPOBJ. He said you should just modify the SQL statements to create them to the new library. It will not work if you mix them as you were. Thanks for using the IBM Rochester Support Center!! I'm not real happy with that answer, how about you all? Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Monday, December 12, 2005 7:55 AM To: midrange-l@xxxxxxxxxxxx Subject: CRTDUPOBJ of file with trigger renders trigger inoperative I'm trying to use CRTDUPOBJ to create a duplicate of a file into a new library. The file has a trigger attached and I actually do want the trigger to be on the duplicate file. The problem is that while it seems that DB2 creates a duplicate trigger in the new library and associates the duplicate trigger with the duplicate file, the trigger's status is *INOPERATIVE. >From what I could find online, in the infocenter and via google, duplicating the file and attached trigger should work. Why doesn't it? I couple of things I found lead to be think that perhaps it was because the trigger references two files that weren't in the new library. However, the trigger's status is still *INOPERATIVE even after duplicating those two referenced files prior to duplicating the file with the trigger. Anybody know what is going on? This is on v5r3. Thanks, Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 -- 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 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 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. Mark Allen allenmar@xxxxxxxxx Home: 859 635 5980 --------------------------------- Yahoo! Shopping Find Great Deals on Holiday Gifts at Yahoo! Shopping -- 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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo 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. Mark Allen allenmar@xxxxxxxxx Home: 859 635 5980 --------------------------------- Yahoo! Shopping Find Great Deals on Holiday Gifts at Yahoo! Shopping --This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing listTo 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.
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.