RE: CRTDUPOBJ of file with trigger renders trigger inoperative

Well, they're not precisecly the same thing any more.....  There were some
discussions about how DDL described files have a performance edge over DDS
described files.  It seems that DDL files validate field data when it is
being written, while DDS files validate field data when it is being read.
This sort of behavior would seem to mean that the object types are not quite
the same.  Perhaps a dump might reveal where the difference lies....

There seems to be more to this than meets the eye.  What is your trigger
doing?  The documentation that Elvis references seems to be saying that some
object that's being referenced by the trigger is not available in the new
target library.....

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-297-2863 or ext. 1863



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
Sent: Wednesday, December 14, 2005 7:07 AM
To: Midrange Systems Technical Discussion
Subject: RE: CRTDUPOBJ of file with trigger renders trigger inoperative


That was actually the question I asked them after getting the
aforementioned reply.

>From the infocenter and various online articles.  It seems CRTDUPOBJ
works on files with triggers.  But IBM is saying it doesn't work with an
SQL defined file that has an SQL defined trigger.  So does it work on a
DDS defined file with an SQL trigger, or a SQL defined file with a RPG
trigger?

Why the difference?

Not only does it not make sense, it seems to violate the principles that
and SQL defined table is the same object as a DDS defined physical file.

Heck, this is supposed to be an object oriented OS.  Shouldn't the
object no how to duplicate itself?


I've yet to receive an answer.




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 Jim Franz
> Sent: Tuesday, December 13, 2005 6:18 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: CRTDUPOBJ of file with trigger renders trigger 
> inoperative
> 
> 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
>