Re: File Trigger Question

The answer is that the application had a variable set to specifically
ignore the trigger program process when run in a batch environment. Once
we turned that off, then it worked just fine.

A typical dumb problem.

Rich

--------------------------------------------------------------------------

On 3/27/2017 12:55 PM, Evan Harris wrote:

So what was the answer ?

I feel a bit like I've read the start of a crime novel and want to see how
it turns out.

On 28/03/2017 2:53 AM, "Rich Loeber" [1]<rich@xxxxxxxxx> wrote:


You can ignore this question. The issue has been resolved. Sorry if
anybody dove into this already.

Rich

------------------------------------------------------------
--------------

On 3/27/2017 9:35 AM, Rich Loeber wrote:

I have a trigger program that I register to a file to capture file
record
read activity. It is not a new program, has been around for quite some
time and has always worked satisfactorily. Today, while doing some
testing, I ran a Query against a file with this trigger registered
(WRKQRY). When I run the query interactively, it captures the reads.
When I run the query through the job queue, it does not capture the
reads.

Now, for issues of full disclosure, I am filtering out reads so that
only
reads for specific user profiles are captured. The joblog from the
batch
job shows that it ran under the same user profile as the interactive
iteration.

Any ideas what might be happening here?

Rich Loeber - @richloeber
Kisco Information Systems
[1][1][2]http://www.kisco.com

------------------------------------------------------------
--------------

References

Visible links
1. [2][3]http://www.kisco.com/

References

Visible links
1. [4]http://www.kisco.com/
2. [5]http://www.kisco.com/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [6]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [7]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [8]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [9]http://archive.midrange.com/midrange-l.

Please contact [10]support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [11]http://amzn.to/2dEadiD

References

Visible links
1. mailto:rich@xxxxxxxxx
2. http://www.kisco.com/
3. http://www.kisco.com/
4. http://www.kisco.com/
5. http://www.kisco.com/
6. mailto:MIDRANGE-L@xxxxxxxxxxxx
7. http://lists.midrange.com/mailman/listinfo/midrange-l
8. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
9. http://archive.midrange.com/midrange-l
10. mailto:support@xxxxxxxxxxxx
11. http://amzn.to/2dEadiD