If you're going to roll your own journal receiver management program I would probably write it in SPL (Stored Procedure Language).
It's really easy to use the journal services at https://www.ibm.com/docs/en/i/7.5?topic=services-journal
And process a cursor which meets your criteria.
- Sure beats trying to shoehorn SQL into CL.
- Learning SPL increases your marketability.
- APIs are great but if you can drastically reduce development time with services you should.
- New hires can probably grasp this easier than APIs, etc.
Note: If you are using a H/A journal product read their documentation carefully before proceeding with journal maintenance outside of their processes.
Jack, I replied to yours because you mentioned python and I'm just tossing out SPL as possibly a better fit.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.