There is one additional feature - client special registers. These can be set to identify information about the client issuing the SQL statement.
I’ll be publishing a blog on client special registers this week.
Dawn
On Feb 10, 2019, at 10:03 AM, Dawn May <dawnmayican@xxxxxxxxxxx<mailto:dawnmayican@xxxxxxxxxxx>> wrote:
There is no ability to see what job requested the work in a QZDASOINIT job. Typically the work request comes from outside of the system (ODBC), but can come from within the system (JDBC).
However, there are several things you can find out about the work running in those jobs and who requested it.
See these articles (there are several others on prestart jobs, but these are most pertinent to this question).
Retrieving the Current SQL Statement for a Job<
http://ibmsystemsmag.com/blogs/i-can/january-2019/retrieving-the-current-sql-statement-for-a-job/>
Prestart Job Messages<
http://ibmsystemsmag.com/blogs/i-can/january-2019/prestart-job-messages/>
Managing Prestart Server Jobs by Remote IP Address<
http://ibmsystemsmag.com/blogs/i-can/october-2018/managing-prestart-server-jobs-by-remote-ip-address/>
Subsystem Configuration for Prestart Jobs<
http://ibmsystemsmag.com/blogs/i-can/august-2018/subsystem-configuration-for-prestart-jobs/>
Dawn
On Feb 8, 2019, at 9:27 AM, Steinmetz, Paul via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx><mailto:midrange-l@xxxxxxxxxxxxxxxxxx>> wrote:
I noticed, via my performance tools, that one of my QZDASOINIT jobs, was taking 30% of CPU, for a 12 1/2 hour period.
From the performance data/graphs, the process started 2/6 15:00, ended 2/7 3:16, due to an error.
Only thing in the QZDASOINIT joblog is CPIAD07 Host server error occurred with reason code 7.
How can I find what job requested the use of the QZDASOINIT job?
Message ID . . . . . . : CPIAD07
Date sent . . . . . . : 02/07/19 Time sent . . . . . . : 03:16:50
Message . . . . : Host server error occurred with reason code 7.
Cause . . . . . : A error with reason code 7 occurred during host server
processing; the reason codes and their meanings are as follows:
1 -- Resolve to the host server daemon program failed.
2 -- Retrieval of the host server daemon program lock failed.
3 -- Submit job to start the host server daemon job failed.
4 -- Allocation of the host server daemon program failed.
5 -- Starting of the host server job failed.
6 -- Ending of the host server daemon job failed.
7 -- Activation of the host server job failed.
8 -- Processing of exchange random seed request failed.
9 -- Processing of start server request failed.
10 -- Reallocation of server buffer failed.
11 -- Deallocation of the host server daemon program failed.
12 -- Resolve to the server specific user space failed.
13 -- Resolve to the trace buffer user space failed.
14 -- Resolve to the trace buffer user queue failed.
15 -- Read operation from the server specific user space failed.
16 -- Read operation from the trace buffer user space failed.
17 -- Write to server specific user space failed.
18 -- Write to server trace buffer space failed.
19 -- Enqueue operation to the trace buffer user queue failed.
99 -- Unknown processing error occurred.
Recovery . . . : Determine the cause of the error; if necessary, correct
the error and retry the request.
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx><mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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:
https://amazon.midrange.com
midrange.com
