× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



FWiW... I have always tried to stay away from using that IBM file. Instead, I've created my own version called NULLTABLE. It just is more intuitive to me and easier to type.



To: midrange-l@xxxxxxxxxxxx
From: zreclay@xxxxxxxxx
Subject: Re: SQL views missing after Cumulative PTF's applied
Date: Mon, 26 Aug 2013 13:42:51 -0400
To: midrange-l@xxxxxxxxxxxx

V6.1.0 LPAR

And...viola! Give that man a prize.

Object . . . . . . . : SYSDUMMY1 Attribute . . . . . : PF
Library . . . . . : SYSIBM Owner . . . . . . . : QSYS
Library ASP device . : *SYSBAS Library ASP group . : *SYSBAS
Type . . . . . . . . : *FILE Primary group . . . : *NONE
Creation information:
Creation date/time . . . . . . . . . : 08/26/13 00:01:01
Created by user . . . . . . . . . . : QSYS
System created on . . . . . . . . . : S101F63M
Object domain . . . . . . . . . . . : *SYSTEM

So, syntactically, how would I make the change to using the VALUES
clause with a UNION ALL?

CREATE VIEW mylib.companyv1 AS (
SELECT 0 AS compid, 'Unknown/unmaintained' AS compdesc FROM
sysibm.sysdummy1
UNION ALL
SELECT cocoid AS compid, codesc AS compdesc FROM mylib.company ) ;

Everything that I've tried comes up with syntax errors.

Thanks for the help!

Robert

"Contrariwise, if it was so, it might be; and if it were so, it would
be; but as it isn't, it ain't. That's logic."--Tweedledee

On 08/26/2013 1:14 PM, rob@xxxxxxxxx wrote:
Ok, I know we were told "don't ask" so I won't. Instead, I'll assume.
Much of the use for SYSDUMMY1 has vanished. I would suspect it's only
there for compatibility reasons. There are two different statements which
should be able to replace most, if not all, of the use of SYSDUMMY1. They
are SET and VALUES.

For example, I can replace:
select days('2013-09-30') - days(current date) from sysibm.sysdummy1
with
values days('2013-09-30') - days(current date)
Either will tell me the number of days until V5R4 expires - 55. I will
turn 52 when it is 52 days until V5R4 expires. (Guess that means I'll
finally be playing with a full deck.)

Perhaps, based on Charles statement, if you can replace your usage of
sysdummy1 your issues may go away.

Guess when I put my last cume on?
Object . . . . . . . : SYSDUMMY1
Library . . . . . : SYSIBM
Library ASP device . : *SYSBAS
Type . . . . . . . . : *FILE
Creation information:
Creation date/time . . . . . . . . . : 06/08/13 08:00:20
Created by user . . . . . . . . . . : QSYS



Rob Berendt

--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.