Re: QWVRCSTK - CSTK0200 for 'what program fired the trigger'

Technically, you are not accessing the data via SQL... You are accessing it via some ODBC/JDBC driver. What happens if you take SQL out of the loop? As you can see (and as I think we all expect) the JAVA SQL access gets sent through the same interface as would occur if the request came from "outside" (see QZDASOINIT). But I think there are JAVA direct DB calls (right?) that might produce significantly different result.
++
Dennis
++
"Inanimate objects are classified scientifically into three major categories - those that don't work, those that break down, and those that get lost."
-- Russell Baker


Sent from my Galaxy tablet phone. Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"Buck" <kc2hiz@xxxxxxxxx> wrote:

I'm implementing QWVRCSTK in a trigger program for the usual reason: to
find the name of the program that performed the database update that
caused the trigger to run.

I can understand why IBM includes CSTK0200 in a generic call stack
traverser; any given call stack may indeed have Java or PASE as the
originator. But for the purposes of finding the program that fired a
trigger, I don't see how Java or PASE could be in there.

A quick test of a Java class running on the i shows me that before
QDBUDR I get:
QSQRUN3 SQL_Update
QSQROUTX QSQROUTX
QZDASRV EXECUTE
QZDASRV QZDASQL
QZDASRV SQL_ECALL
QZDASRV SQL_EXTPGM
QZDASRV SQL_CODE
QZDASRV QZDACMDP
QZDASOINIT main

It appears to me that if I use CSTK0200, the only format returned will
be STKE0100 - for the purposes of finding the code that fired the
trigger. Empirical evidence is nice, but formal documentation would be
nicer.

My big 'problem' was that I was unable to get a Java stack frame to
test
with :-)
--buck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.