× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




i find a mesage help, thanks, and now i try to read a systems logs and application logs to determine better the problem, mmm i find in internet a problem whit RCLSTG do similar errors in the journals, but i need more information in the logs, regards


La felicidad es frecuente, no pasa un día en que no estemos un instante en el Paraíso.

To: midrange-l@xxxxxxxxxxxx
From: CRPbottle@xxxxxxxxx
Subject: Re: journal receiver sequence
Date: Thu, 2 Aug 2012 10:16:56 -0700

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.