Re: QZDASOINIT Jobs -- JAVA400-L

Well, I created a quick couple of programs to demonstrate what I amdoing. I am using the JDBC driver from jt400.jar but it is a standardSQL execute statement that calls the program through the JDBCconnection. You can view the very bare bones code here:http://code.midrange.com/index.php?id=8b06e71f66

The JDBC connection job log displays the following (using the WRKODBCJOBcommand):


Job 228822/QUSER/QZDASOINIT started on 01/05/06 at 20:51:41 in subsystem

QUSRWRK in QSYS. Job entered system on 01/05/06 at 20:51:41.User PETE from client 10.0.20.117 connected to server.CURRENTLY RUNNING PROGRAM IS:MyProgramYou could pass any value into the CL. I created a String variable inthe Java program and set it to "MyProgram" and then passed it asparameter in the call.


Hope this helps a bit.

Pete Helgren


NGay@xxxxxxxxxxxxx wrote:

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

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


Pete,

How would this work?  If I have a Java program making an SQL connection to
one of the iSeries, and this uses the toolbox/PCML to call a CL program,
that CL program will execute in the Remote Command Daemon job, QZRCSRVSD.
Any messages that the CL outputs (presume you mean using SNDPGMMSG) will
appear there, not in the QZDASOINIT job.  Is there any way from Java to
make a message appear in the QZDASOINIT job log?

Thanks very much,

Nigel Gay,
Computer Patent Annuities.



********************************************************************************
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.
********************************************************************************