AW: sysibm.sysdummy1

Hi,

Values could always be used in SQL programming in the same way as SELECT ...
INTO.

Values for dummy files was introduced with release 6.1.
If you are not yet on release 6.1 and want to do a quick select for example
to try (scalar) functions, you need to use a dummy file.
SYSIBM/SYSDUMMY1 is as good as any other table (with a single column with a
single row).

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von ibm
Gesendet: Friday, 31. July 2009 16:25
An: Midrange Systems Technical Discussion
Betreff: RE: sysibm.sysdummy1

Using VALUES makes it easier. How do I know what VALUES are available?
I would have never thought that CURRENT TIMESTAMP is a valid call.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, July 31, 2009 8:20 AM
To: Midrange Systems Technical Discussion
Subject: Re: sysibm.sysdummy1

sysdummy1 was a forerunner to the VALUES statement. Before you could do

something like
VALUES CURRENT DATE
or
VALUES CURRENT DATE INTO :myvar

you had to do something like
Select CURRENT DATE from sysdummy1
or
select current date into :myvar from sysdummy1

In my mind - it's pretty much deprecated.

Rob Berendt