Skip to Content
avatar image
Former Member

Identity lost after Upgrading from 16.5 to 16.6

After Upgrading from PD 16.5 to 16.6 all de Identity statements are wrong. PD1655.jpg shows the statement generatet with PD 16.5 PD16.6 shows the statement generatet with PD 16.6 . Anyone knows that problem ?

pd-166.jpg (30.2 kB)
pd-1655.jpg (34.4 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Sep 01, 2017 at 04:06 PM

    What DBMS did you use to generate the code?

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 05, 2017 at 06:42 PM

    You must have used Z/OS 9 DBMS in 16.5.5.

    For Z/OS 10 or 11 DBMS, somehow the syntax got changed.

    Please open a ticket with SAP.

    Add comment
    10|10000 characters needed characters exceeded

  • Sep 07, 2017 at 12:44 PM

    One of the advatnages of using PD to generate your database DDL is that you don't have to wait for SAP to issue a fix and then upgrade the software to apply it. The way that PD handles each DBMS is described in special resource files; if you don't like how the DDL is presented, you can change it, via the Tools menu - Tools|Resources|DBMS. DON'T EDIT the supplied DBMS file, create a new one based on it (click on the 'New' tool to do this)

    The tricky part is knowing which part of the file to edit. There are two likely places for this particular chunk of the syntax - the 'Create' options for the Table Object

    or one of the Column Templates

    I know nothing about z/OS, so I can't advise any further, apart from saying that you need to change the DBMS in your PDM, to pick up the new resource file - see 'Change Current DBMS' on the Database menu.

    Make sure you also raise this with SAP, as they could possibly fix it quicker than you can work out what to change :)

    George


    Add comment
    10|10000 characters needed characters exceeded

  • Sep 07, 2017 at 12:46 PM

    Rats - my answer had more than image before I selected it. I'll try again:

    One of the advantages of using PD to generate your database DDL is that you don't have to wait for SAP to issue a fix and then upgrade the software to apply it. The way that PD handles each DBMS is described in special resource files; if you don't like how the DDL is presented, you can change it, via the Tools menu - Tools|Resources|DBMS. DON'T EDIT the supplied DBMS file, create a new one based on it (click on the 'New' tool to do this)

    editing-a-dbms.jpg

    I know nothing about z/OS, so I can't advise any further, apart from saying that you need to change the DBMS in your PDM, to pick up the new resource file - see 'Change Current DBMS' on the Database menu.

    Make sure you also raise this with SAP, as they could possibly fix it quicker than you can work out what to change :)

    George

    Add comment
    10|10000 characters needed characters exceeded