Re: db access to iseries from pc's via ?

[tim <iseriesstuff@xxxxxxxxx>]

Thanks for all the feedback. Im am getting closer to what i want. In 
testing, i created the following sql:

SELECT * FROM TABLE (QSYS2.ACTIVE_JOB_INFO('NO','','','')) A,
              TABLE(QSYS2.GET_JOB_INFO(JOB_NAME)) B
where b.V_SQL_STATEMENT_TEXT <> ' '

This does a great job returning what i need, but i dont want to run this 
24x7. I only need to run this when a user tries to access DB2 with an 
external program such as access, Vb program, etc. I like the idea of 
using and exit program. I see a plethora of options for this. Is there 
one i should focus on such as QIBM_QZDA_SQL1 that will allow me to get 
the info i need?




On 4/10/2018 11:55 AM, Justin Taylor wrote:
> They should have QZDASOINIT (or QZDASSINIT) jobs in QUSRWRK subsystem.
>
>
>
> -----Original Message-----
> From: tim [mailto:iseriesstuff@xxxxxxxxx]
> Sent: Tuesday, April 10, 2018 10:39 AM
> To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Subject: db access to iseries from pc's via ?
>
> is there a way of telling who is connecting to the iseries db using things like access, excel, etc?
>
> i want to be able to control these functions. I believe all our users have odbc set up as part of client access install.