MVSFORUMS.com

[anbesivam]

Hi,

In following way my existing table was created:

[dbzTHEdinosauer]

why did you waste a post for a question that you could have performed in spufi and determined the answer yourself.

suggestions:
1. since you are creating the table, then put the key columns together, it is easier on the eyes.
2. if you are going to call a column ..._number and there are going to be alpha char present, call it a ...._code.
If there are only going to be numerics present, then define it as a numeric datatype.
_________________
Dick Brenholtz
American living in Varel, Germany

[anbesivam]

Hi dbzTHEdinosauer,

Thanks for your response.

I cannot create the table on my own in my shop. That's why I posted that question. I can only request for the creation of table to DB2 Team. Before sending the request, I would like verify.

Hope you understand.

[dbzTHEdinosauer]

i am not a dba, so I always have to play in spufi to determine what actually happens.

sorry for the earlier post, though my suggestions stand.

hopefully, someone here will provide you with the answers.
_________________
Dick Brenholtz
American living in Varel, Germany

[Nic Clouston]

You should be able to create the table with your own high level name. How do the DBAs expect you to come to them with valid table requests if you cannot verify that they are valid.
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[jsharon1248]

If the question you're asking is, will DB2 allow more than one column defined in a primary key, the answer is yes. But I look at this and immediately start thinking about normalization. Product_Id and Product_Number define a unique Product? What is the difference between your Product_Id and Product_Number? Hopefully you're just making up an example. Remember, the key, the whole key, and nothing but the key.

[papadi]

[anbesivam]

Thanks to all for your suggestions.

I have discussed with my DBA and he mentioned that we need have the 'Not Null with Default' for the new column even though it is a primary key.

Thanks.

[jsharon1248]

Have you discussed with your DBA if adding the additional field to the primary key is the correct action? You could be creating a situation that could create years of headaches if you don't discuss normalization. I don't often encounter situations where the primary key needs to be modified after a table has been created, so I'm somewhat skeptical that the appropriate level of analysis has been done.

[papadi]