CRTDUPOBJ of a table with long name

IBM does not intend to provide a solution to this request at this time, so it is being closed. The database team has a long list of higher priority requirements, so this request is not likely to be implemented anytime soon.

Rather than using RUNSQLSTM to make the change, you could use the RUNSQL CL command. That would fit in your current CL processing stream with less disruption than using RUNSQLSTM.

There would still leave the problem of duplicate constraint names. But this is a step forward at least. +1

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Db2 for i
Operating system - IBM i
Source - Client

For recording keeping, the previous attributes were:
Brand - Servers and Systems Software
Product family - Power Systems
Product - IBM i
Component - Other
Operating system - IBM i
Source - Client

IBM has modified some of the information in this request. Please contact us if you have any questions.

Namely, the text for the headline, description, and use case have been converted to English, since RFEs require English in order for others in the community to understand and vote on them.

Previous Headline: CRTDUPOBJ d'une table avec nom long

Previous description: Comme indiqué dans le document N1017004, lorsque je veux faire un CRTDUPOBJ d'une table avec un nom long, je ne peux que changer le nom court de la table, pas son nom long.
Du coup, si je veux copier ma table plusieurs fois dans la même bibliothèque avec des noms courts différents (comme par exemple pour faire un archivage mensuel), je suis bloqué dès la deuxième copie car le système indique qu'il existe déjà une table avec ce nom long dans la bibliothèque de destination.
Je suis alors obligé de faire un RUNSQLSTM avant la copie pour retirer le nom long.
Serait-il possible d'ajouter un paramètre au CRTDUPOBJ qui nous permettrait d'indiquer un nouveau nom long en plus du nouveau nom court ?

Previous Use Case: Archivage mensuel de notre table comptabilité arrêté à fin de mois dans la bibliothèque d'archivage

Translated description with https://clientcare.mybluemix.net/newTicket.html :
As indicated in the document N1017004 , ( http://www-01.ibm.com/support/docview.wss?crawler=1&uid=nas8N1017004 ) when I want to make a " CRTDUPOBJ " of a table with a long name, I can only change the short name of the table, not its long name.
So if I want to copy my table several times into the same library with different short names (like for example to make a monthly archive), I am blocked from the second copy because the system indicates that there is already a table with this long name in the destination library.
I am therefore obliged to make a RUNSQLSTM before copying to remove the long name.
Would it be possible to add a parameter to the CRTDUPOBJ that would allow us to specify a new long name in addition to the new short name ?

avez vous essayé de remplacer le CRTDUPOBJ par un RUNSQL pour faire le CREATE TABLE directement dans le CL, plutôt que de passer par un RUNSQLSTM + un membre source ?