×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
... might have been about 30 years ago...
if i recall correctly, you would simply need a loop around your call of
RCVJRNE and in case of CHGJRNRCV your exit will be started again for the now
new *current receiver. To handle ending your receiving job by some other
scenarios (endjob, endsbs) it might be a good idea to register an exit
handler with cee4rage and restart automatically in the CEE4RAGE exit.
handling all errors might become a little bit more tricky.
D*B
<Reeve>
RCVJRNE passes two entries to an exit program--a buffer and a three-byte
control field. When the journal receiver changes, RCVJRNE passes data into
the control field and my exit program sees "3N0", where byte 1 ('3')
indicates the RCVJRNE command is ending. It ends--and so does my
application. The return code in the job log is 0 and no message is posted.
</Reeve>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
