|
I have seen references to this table before in an IBM Redbook from 2003 called the "Oracle to DB2 UDB Conversion Guide". It is something I use frequently, since I still know Oracle PL/SQL better than the DB2 SQL flavor. This table is analogous to Oracle's DUAL, generally used to select system information like system time or do date calculations. In this case, you are not really selecting from a table at all but still need to put something in the from clause. SYSIBM/SYSDUMMY1 has only one column and one row to guarantee a minimum overhead when using it this way. Evidently, it has been carried over from DB2 UDB to iSeries. I know I have used it in V5R2, but can't really test it since we have already upgraded to V5R3. Hope that helps, Jim Reinardy Badger Meter, Inc. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Wilt, Charles Sent: Wednesday, August 10, 2005 1:36 PM To: Midrange Systems Technical Discussion Subject: RE: v5r2 question Maybe somebody created it manually? Can you check the created by user? Charles Wilt -- iSeries Systems Administrator / Developer Mitsubishi Electric Automotive America ph: 513-573-4343 fax: 513-398-1121 > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of > daparnin@xxxxxxxxxxxxxx > Sent: Wednesday, August 10, 2005 2:31 PM > To: Midrange Systems Technical Discussion > Subject: RE: v5r2 question > > > > > > > I tried it on our V5R1 system and got the following: > > > CREATE VIEW QTEMP/TESTINGMYVIEW AS SELECT * FROM SYSIBM/SYSDUMMY1 > View TESTINGMYVIEW created in QTEMP. > > SELECT * FROM QTEMP/TESTINGMYVIEW > TESTINGMYVIEW in QTEMP type *FILE not found. > > There does appear to be a SYSIBM library. I'm no SQL expert so that's > about all I know. > > Dave Parnin > -- > Nishikawa Standard Company > Topeka, IN 46571 > daparnin@xxxxxxxxxxxxxx > > > > > > > > "Wilt, Charles" <CWilt@xxxxxxxxxxxx> > > > Sent by: > To: "Midrange Systems Technical Discussion" > > > midrange-l-bounces+daparnin=niscoseals.com@m > <midrange-l@xxxxxxxxxxxx> > idrange.com > cc: > > > Subject: RE: v5r2 question > > > > > 08/10/2005 01:25 PM > > > Please respond to Midrange Systems > Technical > > Discussion > > > > > > > > > > Elvis, > > SYSIBM didn't exist on v5r1. > > At least there is no mention of it in that "SQL Catalog Views" page of > the > v5r1 Infocenter. > > http://publib.boulder.ibm.com/iseries/v5r1/ic2924/info/db2/rba > fzmstcatalog.htm > > > Charles Wilt > -- > iSeries Systems Administrator / Developer Mitsubishi Electric > Automotive America > ph: 513-573-4343 > fax: 513-398-1121 > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Elvis Budimlic > > Sent: Wednesday, August 10, 2005 1:50 PM > > To: 'Midrange Systems Technical Discussion' > > Subject: v5r2 question > > > > > > I have access to V5R1 and V5R3, but not V5R2. Can someone test this > > for me: > > > > > > > > STRSQL > > > > CREATE VIEW QTEMP/TESTINGMYVIEW AS SELECT * FROM SYSIBM/SYSDUMMY1 > > > > SELECT * FROM QTEMP/TESTINGMYVIEW > > > > > > > > And tell me if they get SQL0204 message or not. > > > > It didn't work for me on v5r1, but it did on v5r3 and maybe I'm just > > missing a PTF but don't know which one. > > > > Thanks. > > > > > > > > Elvis > > > > -- > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, > > unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please > > take a moment to review the archives at > > http://archive.midrange.com/midrange-l. > > > > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, > unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take > a moment to review the archives at > http://archive.midrange.com/midrange-l. > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, > unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take > a moment to review the archives at > http://archive.midrange.com/midrange-l. > > -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.