Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
rkusenet found his sysmaster-based tools worked on 9.3 but failed on 9.4, as columns such as physaddr in sysptntab and pe_phys in sysptnext were gone. John Carlson noted those tables are marked internal use only in sysmaster.sql and may change. rkusenet objected that this undermines sysmaster as an SQL interface to system data. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
A friend of mine is using some tools I have written. They work fine in
9.3 but started failing on 9.4.
For e.g. columns physaddr is no longer there in table sysptntab.
Column pe_phys is no longer there in table sysptnext.
Did I make the mistake of assuming that sysmaster will always be compatible
in future releases.
Ravi
↪ replying to rkusenet
John Carlson — — source: Usenet: comp.databases.informix
On Fri, 13 Jun 2003 09:45:13 -0400, "rkusenet" <rkusenet@sympatico.ca>
wrote:
Those tables are listed as "internal use only" in
$INFORMIXDIR/etc/sysmaster.sql, which sounds to me that they are
subject to change.
>A friend of mine is using some tools I have written. They work fine in
>9.3 but started failing on 9.4.
>
>For e.g. columns physaddr is no longer there in table sysptntab.
>
>Column pe_phys is no longer there in table sysptnext.
>
>Did I make the mistake of assuming that sysmaster will always be compatible
>in future releases.
>
>Ravi
>
"John Carlson" <john_carlson@whsmithusa.com> wrote in message
news:1lljev06dt2srm6pmfehfg0tdmjdqaiqkf@4ax.com...
> On Fri, 13 Jun 2003 09:45:13 -0400, "rkusenet" <rkusenet@sympatico.ca>
> wrote:
>
> Those tables are listed as "internal use only" in
> $INFORMIXDIR/etc/sysmaster.sql, which sounds to me that they are
> subject to change.
hmm...
then how we are we suppose to use those tables. The tools I
have developed (extent_Report and listtabchunk) give lot of valuable
information about a chunk or table. The only alternative seems to
be to use onstat and massage the output. Ugly way. I hate it.
I thought the whole idea of sysmaster is to give SQL interface to
system parameters so that tools can be developed using SQL and not
onstat -.
I would give a D- to Informix for this.
↪ replying to rkusenet
John Carlson — — source: Usenet: comp.databases.informix
On Fri, 13 Jun 2003 10:03:22 -0400, "rkusenet" <rkusenet@sympatico.ca>
wrote:
What is included in sysextents or systabextents according to
sysmaster.sql?
>
>"John Carlson" <john_carlson@whsmithusa.com> wrote in message
>news:1lljev06dt2srm6pmfehfg0tdmjdqaiqkf@4ax.com...
>> On Fri, 13 Jun 2003 09:45:13 -0400, "rkusenet" <rkusenet@sympatico.ca>
>> wrote:
>>
>> Those tables are listed as "internal use only" in
>> $INFORMIXDIR/etc/sysmaster.sql, which sounds to me that they are
>> subject to change.
>
>hmm...
>
>then how we are we suppose to use those tables. The tools I
>have developed (extent_Report and listtabchunk) give lot of valuable
>information about a chunk or table. The only alternative seems to
>be to use onstat and massage the output. Ugly way. I hate it.
>
>I thought the whole idea of sysmaster is to give SQL interface to
>system parameters so that tools can be developed using SQL and not
>onstat -.
>
>I would give a D- to Informix for this.
>
>
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.