× 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.






Hello Midrange experts.

I have the following question regarding journaling and journal receivers.

During the last three months we have been running a couple of
batch jobs that run at noon and midnight.

They generate the next Journal receiver for a list of Journals.

The job runs the command:

CHGJRN JRN(&JrnName) JRNRCV(*GEN)

The program just changes the value of &JrnName
with a list of different Journal Names

and we never have had a problem with this procedure.


Today, we saw something pretty strange.
The batch job started working and
the command created the *next Journal receivers
for a couple of journals.

However for the third Journal .. it "never executed".

No messages in QSYSOPR
No error messages associated to the Job
No error messages or any abnormalities associated to the Job
No History log clues ...

The Job just waited and waited and waited .. just hoping for
some wonderful thing to happen.

Has anybody experienced something like this ?

I will be very appreciative of your responses

Regards

Jorge Moreno
Systems Analyst
Overseas Military Car Sales
Woodbury, New York






As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.