MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

RE: Identity columns



fixed

Years ago I was in a company (oil bidness) with systems in different
locations around the world and found the familiar/home-grown stuff
not always available as I travelled on projects and developed a habit
of not getting to "comfy" with such.

Coincidently, in my current job, I'm the "new" guy (only 7 years from
date of hire) and the only one using RDP, even though we bought licenses
for each one in my department some two years ago.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dean Eshleman
Sent: Monday, October 15, 2012 12:46 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Re: Identity columns

Matt,

Thanks for the information. I went into Navigator and looked at the table definition. There it was, "Is Identity" as one of the columns related to the columns in the table. I guess I will need to start using Navigator more.

I also just discovered that the DSPFFD command does show the information as well. We have a home grown LSTFFD command that we always use, so we never use DSPFFD. I guess I need to update our command or use DSPFFD.

Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com>


On 10/15/2012 2:25 PM, Matt Olson wrote:
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.






________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact