|
Phil I haven't done enough to make any suggestions that would add value to what Carsten is saying. My needs for this stuff were slightly different and so far things look good. Carsten - ditto re Phil's PS Regards Evan Harris >Evan, > >Did you work with the API? I'm having trouble when reading journal entries >which span an IPL because the journal sequence number is reset at IPL. When >I come across this using the api, the api will reprocess the same journal >entries until the job ends abnormally. > >Phil > >PS: Thanks for all your help, Carsten! I do appreciate it. I wouldn't >have gotten as far as I have without your help. My current work around is >for the user to enter the specific journal receiver name or *CURRENT. It's >an ok workaround because this is used by MIS people. Ultimately, though, I >hope to get it working so that the user can enter *CURCHAIN and not kill the >system!
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.