Re: journal receiver sequence

On 02 Aug 2012 09:00, Miguel Peralta wrote:

<<SNIP>> it's working, but now whats is a "*omitted"? I think the
web application has a some kind of error, a system internal error,
I try to see the application logs, but it's another story

DSPJRN JRN(LCLJRNLIB/JRNIFS) INCHIDENT(*YES)

Sequence Code Type Object Library Job Time
25393 B FS <<SNIP>>
25401 C PC *OMITTED 0:00:01
25402 C CM CGIDEV2 0:00:01
25403 C EC CGIDEV2 0:00:01
25404 B FS /CgidevE> BKPDIARIO 6:00:07

So presumably the DSPJRN command invocation was modified to Include Hidden Entries [INCHIDENT(*YES)] and the "gap" in the sequence is since displayed as an Entry Type C-PC "Prepare commit block" where the JOB name is listed as *OMITTED. The help text for the JOB columns suggests that this data gives the "name of the job that caused the journal entry to be deposited" and that the "job name will be *OMITTED if a receiver size option (RCVSIZOPT) or fixed length data option (FIXLENDTA) that would have omitted this data was in effect for the journal when this journal entry was deposited."

I doubt there is anything to be concerned with regard to the internal entry. If the non-internal converted entries are of no assistance, then probably accessing the joblog and any logs of the processing, and possibly even debug, will probably be of more value in trying to find whatever is origin for your difficulty with that job\processing.

Regards, Chuck