Re: RCVJRNE - get name of procedure that performed the file output

On 11/5/2014 12:00 PM, Steve Richter wrote:

On Wed, Nov 5, 2014 at 11:42 AM, Buck Calabro wrote:

On 11/5/2014 10:49 AM, Steve Richter wrote:

No. The journal is an independent and asynchronous process from the

> actual database update.

that is interesting. But there must be some way the database tracks
individual outputs to a table. How else would the journal pick up those
changes as it asynchronously writes entries to the journal?

It's a one-way feed. The database manager sends the database buffers to
the journal component which then does its thing separately from the
database manager.

I follow. But the database system must be uniquely identifying changes that
are sent to the journal system.

I don't see why the database manager 'must' be assigning the journal ID.
That seems to be the journal component's job. Looking at traces it
seems to me that the database simply hands the buffers off without
processing.

What I am asking for is to have the ID number of the queue entries that are
fed to the journal system to both be stored in the journal entry and made
available to the ADDPFTRG trigger exit program. That way the trigger exit
program could retrieve the call stack and write it to a file with a key
that would be found in the journal entry. Assuming that the trigger exit
program runs in the same job as the procedure that performs the file
output.

Yes, it's clear what you're asking for, but I don't think such a thing
exists. Here's an example that might help clarify the problem. A does
a SNDMSG. Some time later, B does a RCVMSG. I want A to know the time
stamp when B actually received the message. The information only flows
one way, from A to B.

Or, IBM could just write the procedure name to the journal entry.

I think you'd have a chance of getting this added. Try the CAAC?