Dear all,
We use an IFS Monitor to trigger programs when a file is added to an IFS folder. This works Ok, when a file is placed on the IFS, the processing program is triggered instantly. But once in a while it took longer sometimes up to 20 minutes. In the job-log we found on the moment this happens the following message ?638316 entries received from journal QAUDJRN in QSYS.? (CPC7061) at the moment of the delay.
When we did some more investigation, we found that this occurred always exactly at the time a new journal receiver was attached to journal QAUDJRN.
The CL command we use to receive the journal entries is
RCVJRNE JRN(QAUDJRN) EXITPGM(GIFS20) +
RCVRNG(*CURCHAIN) FROMENTLRG(&SEQNBRA) +
JRNCDE((T)) ENTTYP(CO) ENTFMT(*TYPE4) +
DELAY(*NEXTENT 60)
We only receive the entry type CO. At this moment we keep about one month history in the audit journal, and when we count all CO-entries in all receivers, and the total number of CO entries in all receivers is the same as the number of entries in the message.
So it looks like, when a new receiver is attached, the RCVJRNE read all entries again, although the exit program is not called. My questions are
1. Why are all entries (re-)read, when a receiver is changed?
2. How can we avoid this?
Thanks......
We use an IFS Monitor to trigger programs when a file is added to an IFS folder. This works Ok, when a file is placed on the IFS, the processing program is triggered instantly. But once in a while it took longer sometimes up to 20 minutes. In the job-log we found on the moment this happens the following message ?638316 entries received from journal QAUDJRN in QSYS.? (CPC7061) at the moment of the delay.
When we did some more investigation, we found that this occurred always exactly at the time a new journal receiver was attached to journal QAUDJRN.
The CL command we use to receive the journal entries is
RCVJRNE JRN(QAUDJRN) EXITPGM(GIFS20) +
RCVRNG(*CURCHAIN) FROMENTLRG(&SEQNBRA) +
JRNCDE((T)) ENTTYP(CO) ENTFMT(*TYPE4) +
DELAY(*NEXTENT 60)
We only receive the entry type CO. At this moment we keep about one month history in the audit journal, and when we count all CO-entries in all receivers, and the total number of CO entries in all receivers is the same as the number of entries in the message.
So it looks like, when a new receiver is attached, the RCVJRNE read all entries again, although the exit program is not called. My questions are
1. Why are all entries (re-)read, when a receiver is changed?
2. How can we avoid this?
Thanks......
Comment