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



If you put something into double quotes it becomes case sensitive.
So there in no "Current_User" column but a "CURRENT_USER" column.

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!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Donnerstag, 27. April 2017 16:16
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Querying an IBM supplied UDTF where some columns are reserved
words

So is the doc wrong then?
SQL State: 42703 Vendor Code: -206 Message: [SQL0206] Column or global
variable Current_User not found. Cause . . . . . : Current_User was not
found as a column of table *N in *N and was not found as a global variable
in *N. If the table is *N, Current_User is not a column of any table or view
that can be referenced, or Current_User is a special register that
cannot be set in an atomic compound statement. Recovery . . . : Do one
of the following and try the request again: -- Ensure that the column and
table names are specified correctly in the statement. -- If this is a SELECT
statement, ensure that all the required tables were named in the FROM
clause. -- If the column was intended to be a correlated reference, qualify
the column with the correct table designator. -- If the column was intended
to be a global variable, qualify the name with the schema where the global
variable exists or ensure the schema is in the path. -- If this is a SET
statement for a special register within an atomic compound dynamic
statement, remove the statement or remove the ATOMIC keyword.

http://ibm.biz/DB2foriServices


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: "Tyler, Matt" <matt.tyler@xxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 04/27/2017 10:07 AM
Subject: RE: Querying an IBM supplied UDTF where some columns are
reserved words
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Reserved Name as "Reserved Name"

select "Reserved Name" from Table
where "Reserved Name" = Value
order by "Reserved Name"

-Matt

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Thursday, April 27, 2017 7:57 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Querying an IBM supplied UDTF where some columns are reserved
words

How do I query an IBM supplied UDTF where some of the columns are reserved
words?

SELECT journal_code, journal_entry_type,
"Current_User", job_name, Job_user, job_number,
Remote_port, Remote_address, system_name,
Entry_Timestamp, Receiver_name,
Program_name, Program_library,
OBJECT, object_type,
X.*
FROM TABLE(QSYS2.Display_Journal('QSYS', 'QAUDJRN', -- Journal library and
name STARTING_TIMESTAMP => CURRENT TIMESTAMP - 24 HOURS -- Time period
)) AS x
where "CURRENT_USER" in('TOM', 'DICK', 'HARRY') or
Job_user in('TOM', 'DICK', 'HARRY');


http://ibm.biz/DB2foriServices



Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.