Allow me to resurrect this for a moment.

On Wed, Dec 9, 2015 at 7:31 AM <rob@xxxxxxxxx> wrote:

Do you know SQL? (just kidding, ducking and running...)

Yeah, its the DDS stuff that confuses me.


On 7.2

SELECT AUTHORIZATION_NAME, JOB_NAME, SUBSYSTEM, JOB_TYPE,
SERVER_TYPE
FROM TABLE(QSYS2.ACTIVE_JOB_INFO(
CURRENT_USER_LIST_FILTER => 'ROB')) X


....+....1....+....2....+....3....+....4....+....5....+....6....+....7....+....
AUTHO00001 JOB_NAME SUBSYSTEM JOB_TYPE SERVE00001

ROB 977161/QTMHHTTP/ADMIN QHTTPSVR BCI
QIBM_HTTP_ADMIN
ROB 203207/ROB/ROBS1 QINTER INT -
******** End of data ********


http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqudfactivejobinfo.htm?lang=en-us

Notice how the first job listed does not have my name in the job name?

On most unix variants root (administrator/QSECOFR,G-d equivilant) can
lower a processes privileges to another user. This is usually used by
servers for binding to a TCP socket below 1024 and then dropping to a
lesser user to do the actual work. I don't think that most kernels keep
track of the start up user versus the current user though.


If you try this on 7.1
SQL0104 - Token => was not valid. Valid tokens: ) ,.


I'd love my clients to update to 7.2, or at least install the latest PTFs
for 7.1. Glad to know this will work for me SOMEDAY.

I'm a little disappointed about the error message though. 7.1 supports
calling UDF parameters by name as well as positionaly, so why can't the
parser tell you instead that CURRENT_USER_LIST_FILTER parameter not found.


Check out the "What's new in DB2" on 12/15 offered free by COMMON.


I'm looking to see where the recording are. Too bad I missed it.

Justin

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2019 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].