Re: QZDASOINIT Jobs -- JAVA400-L

I'd argue that using WRKODBCJOB is MUCH easier. Sure you can useWRKACTJOB JOB(QZDASOINIT) and then laboriously step through each job tosee who the user is that is being serviced, or you can just useWRKODBCJOB and SEE who the serviced user is without looking at the joblog. I LOVE this utility!

However, to get calling application information into the job log youcould just call a CL program from your app that simply outputs thatinformation (Passing the application function as a parameter perhaps).

We call a CL program to set member overrides for the connection and weoutput what application is running and what overrides we are setting andwhat library list is being used in the job log (yes, you can also getthis from viewing the job but outputting it in the joblog makes iteasier to view).


Pete Helgren


NGay@xxxxxxxxxxxxx wrote:

It looks like WRKODBCJOB only gives you the user ID being serviced and
their IP address - you can get that info from the job log anyway, there's
always a message in the job log such as:
"User ABCDEFG from client 192.168.0.25 connected to server."

What I'd really like to be able to do is to simply be able to output
messages into the job log.  We have a number of different applications all
firing SQL at our iSeries (most of them using the same user ID coming from
the same IP address) and it would be really helpful if we could output a
message like "This is the XYZ application." into the job log, or even
better "Now running query to get list of addresses for account 1234567" so
that if we spot a job eating up tons of CPU, we can examine the job log and
see what SQL query its currently running.

Does anyone know a way to do this, or anything even similar?

Thanks very much,

Nigel Gay,
Computer Patent Annuities


java400-l-bounces@xxxxxxxxxxxx wrote on 05/01/2006 11:04:33:

Get the WRKODBCJOB utility from Bryan Dietz

http://home.columbus.rr.com/jbmmdietz/iseries.html

Pete Helgren

Larry wrote:

Can anyone recommend the best way to monitor performance on

QZDASOINIT jobs?  We have a number of these that hit the 400 from
various sources - most calls from java programs on other platforms.

I know if I am testing SQL calls I can set them up in ops nav SQL

script tool, execute them and look at the joblog for lots of good
info about how the sql executes.

Can this be done for the QZDASOINIT jobs as they execute in

production?  I don't see any detailed information if I catch the
jobs as they are executing and look at their joblogs.

Larry



_______________________________________________
No banners. No pop-ups. No kidding.
Make My Way  your home on the Web - http://www.myway.com

--
This is the Java Programming on and around the iSeries / AS400
(JAVA400-L) mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.




********************************************************************************
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee; access to this
email by anyone else is unauthorised.

If you are not the intended recipient: (1) you are kindly requested
to return a copy of this message to the sender indicating that you
have received it in error, and to destroy the received copy; and (2)
any disclosure or distribution of this message, as well as any action
taken or omitted to be taken in reliance on its content, is prohibited
and may be unlawful.
********************************************************************************