|
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! > -----Original Message----- > From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On > Behalf Of Evan Harris > Sent: Sunday, May 05, 2002 2:05 AM > To: rpg400-l@midrange.com > Subject: RE: Reading journal entries in an RPG pgm > > > Hi Carsten > > I hate to be part of a "me, too" thing but I'd be interested as well. > > Regards > Evan Harris > > > > > > > You can specify an (f.x. RPG) exit program on the RCVJRNE > and retrieve > >the > > > > > journal entries as they arrive - or you can use the > > > > > QjoRetrieveJournalEntries to retrieve journal entries based on a > >variety of > > > > > selection criteria. I can email you an RPG/IV sample of > the Qjo... > >API if > > > > > you're interested. > > > > > > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > >
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.