Re: Weird request

Nope. No tricks, that's how its done (at least for simple data types - for extended data types you have to also look in sysxtdtype). One thing you can try if you like, is get my utils2_ak package and look at the source for my dbschema replacement utility. It is possible to edit the myschema.ec and print_coltype.ec file to produce simpler listing (or just steal - um borrow - the code in print_coltype for you own use in a simpler app). Art. On Thu, Jul 10, 2008 at 2:35 PM, MIKE MAGIE <jmmagie@yahoo.com> wrote: > Pertinents: > > Informix 10.00.UC8 on Solaris 2.8 > > Mission: > > Create a file that contains the following - > > database_name|table_name|column_name|column_data_type > > For like a bajillion databases with gobs of tables and oodles of columns. > > I have already began playing with awk and sed - and looking at sysmaster > queries and stuff. Coltype is the main issue - as many of you probably know > the coltype is stored as a smallint, in decimal, that when converted to hex > can be mapped to the actual data type, i.e if you had a coltype value of > 257 > you'd convert it to hex, get 101, map it to the coltype values and figure > that > you had a not null integer column. But that is like hard and stuff. I am > sure > I am trying to reinvent the wheel here and would love to see what some of > you > ladies and gents might come up with. > > MM > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.