RE: Reading journal entries in an RPG pgm

["Phil" <sublime78ska@xxxxxxxxx>]

Yes, I would like that very much!

Thanks again,

Phil

> -----Original Message-----
> From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
> Behalf Of Carsten Flensburg
> Sent: Sunday, May 19, 2002 1:28 PM
> To: rpg400-l@midrange.com
> Subject: Re: Reading journal entries in an RPG pgm
>
>
> Hello Phil,
>
> As mentioned earlier, I think that IBM is currently trying to address the
> issue you mention - and hopefully a solution of some kind will be
> found.  It
> just got the thought that you - in the mean time - might be able to
> reproduce the current missing functionality if you include the use of the
> QjoRetrieveJournalInformation API.
>
> This API is able to retreive the journal receiver directory and therefore
> could substitute the *CURCHAIN function: Retrieve the list of journal
> receivers and for each receiver - one receiver at a time - retreive the
> entries in question.
>
> I have an example of the use of this API - it's quite tricky when it comes
> to resolve the offset of the key header information section, but thanks to
> the kind assistance of Bruce Vining I finally saw the light. If
> you want to
> pursue this possible (intermediate) solution, I can email you the sample.
>
> Best regards,
> Carsten Flensburg
>
>
> ----- Original Message -----
> From: "Phil" <sublime78ska@attbi.com>
> To: <rpg400-l@midrange.com>
> Sent: Sunday, May 19, 2002 6:49 PM
> Subject: RE: Reading journal entries in an RPG pgm
>
>
> > 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!
>
>
> _______________________________________________
> 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.
>
>