If I was being driven mad by this I would add another dataq into the mix
and write a program to log what goes in and out and transfer it to the
target dataq. That way I could determine if it was the C# read or the
application vendor write that was at fault.

Application writes to my dtaq; my program logs it and puts it on the
sharepoint dataqueue.


On Tue, Aug 4, 2015 at 9:45 AM, Voris, John <john.voris@xxxxxxxxxxxxx>
wrote:

My project has changed all around due to other reasons - like we are
taking out the File Triggers.
I still think that putting the QSNDDTAQ into a batch job will keep the
problem at bay . . .
I will probably leave the QSNDDTAQ in the separate job that is the batch
job.
(IBM did not have anything to add to the discussion.)

Thanks everyone for your time and attention.

- John Voris, Crown Holdings, Phila PA

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





This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].