Re: SQL enhancements

["R. Bruce Hoffman, Jr." <rbruceh@xxxxxxxxxxxxx>]

----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Thursday, September 05, 2002 2:59 PM
Subject: Re: SQL enhancements


> This is a multipart message in MIME format.
> --
> [ Picked text/plain from multipart/alternative ]
> So should we ever refer to the files in QSYS2 anymore, or just use the
> ones in SYSIBM?

Migration implies that you should start using the SYSIBM schema. QSYS2, I
don't know, but my guess is it's gonna be around for a while. It's got other
things in it. Also note that most of the catalogs in QSYS2 were actually
views over files in QUSRSYS.

> Is there something in QSYS2 that is missing in SYSIBM?

I don't have access at the moment, and I have not checked but I believe the
new catalogs are going in SYSIBM and not QSYS2. Some of the names may be
different as well. SYSIBM traditionally has the tables TABLE, INDEX, VIEW,
CONSTRAINT, TYPE, FUNCTION, etc.


> And I take it, SYSIBM is preferred over accessing the files QSYS/QADB*
> directly?

For SQL, yes. And for SQL standards compliant packages.

For one advantage, the existing DB2-aware tools, that may not be
OS/400-aware, should now work. Erwin and lately, ERStudio from Embarcadero
are OS/400-aware.

===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified Specialist - iSeries Administrator
 -- IBM Certified Specialist - RPG IV Developer

"There is a crack in everything,
  that's how the light gets in.
    - Leonard Cohen