Look at the DDL is the easiest way. Go into navigator, double click on the table and investigate the column in the GUI. Alternatively you can right click the table and generate the SQL Script which will create the DDL script and you can tell from that.
In MS SQL there is a stored procedure called "sp_help" which gives table information, I don't think an equivalent exists in DB2. I believe you are forced to utilize the DB2 catalog views to get the same type of information.
From: Dean Eshleman [mailto:Dean.Eshleman@xxxxxxxxxxxx]
Sent: Monday, October 15, 2012 1:11 PM
Subject: Identity columns
I have just started to take advantage of Identity columns in some of our files that we have been creating. Someone was reporting a problem with one of the files in a test environment and I was trying verify that the file had been created with the Identity clause on the key field. When I did a display object description, the source file and source member were blank. All of the tools that I am used to using to look at the field definitions in a file do not include this information. I finally had to try adding data to the file to figure out that the Identity clause had not been added to the field. Does anyone know an easy way to verify that a field has the Identity clause without looking at the DDL?
Software Development Architect
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l