QZDASOINIT management

[Jon_E]

I understand QZDASOINIT is a connection job to serve SQL requests.

We have several different external systems connecting to our iSeries
database via JDBC. We would like to manage the connections by
application, possibly grouping these different applications into a few
different subsystems for ease of management. For example, if the
subsystem is not active, then the application could not get it's data
via the SQL server QZDASOINIT program running in that subsystem.

Thoughts?

[iseriesflorida]

I believe there are many applications that would utilize these jobs
(ODBC etc.).

Curious, maybe look at using multiple interface(s) to control access
to your applications if that is possible. Maybe explore using exit
programs if they would work for your situations. I have not created
seperate subsystems for control of the QZDASOINIT before.

[dieter...@t-online.de]

Hi,

you can configure this with oops nerv (operations Navigator) only (it must
be right click context menu of the server Job). As far as I know its a
little bit tricky to prevent the jobs from running in the default
subsystem.

D*B

[Thad Rizzi]

Try looking in System i Access - Network/Servers and right click on
properties on the Database server. If you go under the Subsystem tab
you set up the server to start jobs in a certain Subsystems based on
specific clients IP address.

Thad Rizzi