Re: Closed system (was: PC connection via twinax ?)

Thanks Simon,

When I looked at the qqquery api in the past I recall that I saw extensive
documentation on preparing the query, but nothing on the actual call to
receive the data. A "Call this pgm with a ptr to the query template and a
return buffer and the system returns the next xxx rcds that satisfy the
query" api. I am not and would never ask you to investigate for me, but if
your vast store of knowledge<g> contains the answer to this question I would
be interested in reading it.  My guess, based on what could be a faulty
premise, is that you use qqquery in a way similar to opnqryf, then call the
undocumented QDM* pgms to read the data.

You are right though, that there is openness to the database.  I need to
know more to concede that a 3rd party vendors product can have the
documented access to the system to compete with ibm's query products.

More so, I suspect that roch uses access to undocumented api's as a way to
keep 3rd party vendors in line. Not so much to enforce system standards and
integrity ( which is good ) but as a way for the software bureaucrats in
roch to perpetuate themselves.

Keeping to the post topic, "is the system open", your answer re: a 3rd party
( what is the 2nd party? ) language updating the dsppgmref tables, I think
your answer is evidence that it is not open.  If you cant update the table
thru a documented interface, then you cant update the table.


Thanks for the info,

Steve Richter






-----Original Message-----
From: Simon Coulter <shc@flybynight.com.au>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Sunday, August 19, 2001 8:06 AM
Subject: Re: Closed system (was: PC connection via twinax ?)


R
Hello Steve,

You wrote:
>What api's do they call?

<---- stuff deleted ---->

>Is that documented?  How is that space built?

So you want me to do the investigation for you ... :)

There are the SQL CLI, SQL APIs, and the QQQQRY API for the adventurous.
The input to QQQQUERY is a Query Definition Template or QDT.  This is
exactly the same structure that is used by Rochester, and some vendors, to
get the query engine to do its work (Query/400, OPNQRYF, etc).  Rochester
have said that this API will not be enhanced to handle new DB features so
that leaves the CLI and the various SQL APIs for those wanting access to the
DB.  You could also use SQL directly.

The where-used space is not publicly documented (as far as I know) but it is
part of the Object Information Repository (OIR).

I think Leif may have written something about this space in his book (which
I don't have 'cause I'm waiting for the Australian exchange rate to improve
-- it might be a long wait :), however it's not difficult to decipher the
where-used space from a program dump.  It's basically a count of references
as a BIN(2), followed by an array of objects in the form: object name as
CHAR(10), a CHAR(1), object library as CHAR(10), another CHAR(1), object
type as CHAR(1), and object subtype as CHAR(1).

If you want to know more than that you'll have to do your own research.

Regards,
Simon Coulter.

«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
«» FlyByNight Software         AS/400 Technical Specialists       «»
«» Eclipse the competition - run your business on an IBM AS/400.  «»
«»                                                                «»
«» Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   «»
«» Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /   «»
«»                                                           X    «»
«»               ASCII Ribbon campaign against HTML E-Mail  / \   «»
«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»«»
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com