[David Kosenko: Re: turbo extents used]

Dave K writes in response to my request for help on determining how many extents are in use in Turbo 2.10.03G: >If the table is active (and you can make it active by going into isql and >issuing a LOCK TABLE statement), then tbstat -t will show the number of >extents allocated for the table (nextns). There is a trick, however, in that >tbstat shows the table with its tblspace number (partition number in Turbo >parlance) not the table name. To get a list of table names and their >respective (hex) partition/tblspace numbers, use the following query: > > select tabname, hex(partnum) from systables;>> >Dave Good idea, and I had been told that before, but on our system that gives a syntax error. It doesnt like the hex word. We are running ISQL 2.10.03G on a Unisys 5000. Is that a "bug?". Yes, we are on our way to On-Line, but not until our application programmers get the application ready to go. The Unisys platform has only progressed to 4.1 that I am aware of, there is no 5.0 or 6.0 like all you Sun etc. types are longing for or even using. Yes, it is an "antique" platform, but we do the best we can with your tax dollars, and right now that doesnt include new hardware. Is there any further assistance on the problem of hex(partnum) or how to tell what extents are being used? Thank you for your responses. PS: Dave K, I cannot seem to succesfully e-mail to you. My phone is 717-267-9869. Please call re: ISAM info you wrote about. Thanks. Ann Barnes, Letterkenny Army Depot, Chambersburg, PA