cancel
Showing results for 
Search instead for 
Did you mean: 

Powerdesigner 16.5 SP05 PL03 reverse engineer DB2 11 ZOS

Former Member
0 Kudos

When trying to reverse engineer from DB2 11 on ZOS all identity columns and timestamp columns with 'FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP' are not handled correctly. These attributes seems to be ignored by Powerdesigner.

This is how identity columns look like after beeing reverse engineered:

Source column defined like this:

id integer not null generated by default as identity (cycle)

And columns defined like this:

last_login timestamp not null generated by default for each row on update as row change timestamp 

is looking like this after after beeing reverse engineered (ordinary timestamp column):


Any suggestions how to get this to work properly?

Arild

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member200945
Contributor
0 Kudos

I ran the reverse engineer for the following code and it worked.

Create Table TB1

(

   TS1 TIMESTAMP NOT NULL GENERATED BY DEFAULT

                                 FOR EACH ROW ON UPDATE AS ROW CHANGE TIMESTAMP,

   TS2 TIMESTAMP NOT NULL

)

Can you upload a code sample here?

Former Member
0 Kudos

This is how my table is defined in DB2 11 for z:

CREATE TABLE TESTVIP.ROITASKS (                                  

  id integer not null generated by default as identity (cycle),  

  investor_Id char(11) not null,                                 

  created timestamp not null with default,                       

  from_Date date,                                                

  to_Date date                                                   

) VOLATILE                                                       

  IN DVIP.SVIP16                                                 

;                                             

And this is how it turns out in Powerdesigner after reverse engineering:

former_member200945
Contributor
0 Kudos

I use 16.5.5 PL04. This is the result :