Re: SQL Question

SELECT * FROM QPFRDATA.QAPMCONF
where GKEY in (' S', ' 6' )

' S' = System Name (Hostname)
' 6' = Serial Number


El 22/07/18 a las 21:27, Evan Harris escribió:

I just queried QAPMCONF but didn't see anything usable (unless I am missing

something)

Vern's solutions works for me because I was looking for something
reasonably general purpose even though I used a performance table for my
example.

On Mon, Jul 23, 2018 at 1:58 PM, Diego Kesselman <
diegokesselman@xxxxxxxxx>
wrote:

Have you tried with QAPMCONF?

2018-07-22 20:28 GMT-05:00 Evan Harris <auctionitis@xxxxxxxxx>:

Hi Vern

thanks for that, that works perfectly.

On Mon, Jul 23, 2018 at 1:03 PM, Vernon Hamberg <

vhamberg@xxxxxxxxxxxxxxx>

wrote:

Hi Evan

There's a special register - CURRENT SERVER - that would gives the
identity of the server where the statement is running - at least,
that's
what I think it does - give that a try.

Using the view or UDTF will cost more than using one of the many
special
registers.

HTH
Vern

On 7/22/2018 5:41 PM, Evan Harris wrote:

Hi all

I am running some SQL queries to extract data and thought that adding
a
"system" column to the extracted would be a good idea, rather than

trying

to keep track of it in the file name, or having it hardcoded in the

query.

So, for example, I have an SQL Statement as follows:

SELECT INTNUM,
(SELECT HOST_NAME FROM QSYS2.SYSTEM_STATUS_INFO) as SYSNAME
FROM QPFRDATA.QAPMSYSTEM

Which returns a bunch of SYSNAM and INTNUM columns.

My question is, is this the most efficient/best practise way of doing

this

? I am wondering if running it this way will cause the query to be

executed
for every row that gets returned.

What other ways are there that might be preferable or more efficient ?


--

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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--

Regards
Evan Harris
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link: http://amzn.to/2dEadiD



--

Saludos

Diego E. KESSELMAN
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD