|
Doesn't the deletion of a journal receiver warrant it's own code in the
current receiver? Meaning if RCVR0020 is deleted and the current receiver
is RCVR0032 then wouldn't RCVR0032 had record of the other receiver being
deleted? Then you could determine what process deleted that other
receiver. Granted, if it's what you suspect, then it's some obscure
system task and we need to focus on your original target area. However,
if someone is running a custom PRGJRNRCV, like we do on our non Mimix
machines, then that might be your issue.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: William_Milyard@xxxxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Date: 04/22/2010 03:36 PM
Subject: Deletion of Journal Receivers
Sent by: midrange-l-bounces@xxxxxxxxxxxx
We're trying to prevent journal receivers from being deleted before we
want them to be deleted. We need to keep receivers for several days,
however, no matter what we've tried, there are always 12 receivers for
this journal.
The application that uses the journal has a job that can be called at
specified intervals to clean up receiver but we disabled the job several
months ago so it can't be deleting them.
I've tinkered with the journal settings, however, nothing affects their
removal. The journal settings that I thought would control deleting
receivers was originally set as follows: MNGRCV(*SYSTEM) DLTRCV(*NO)
RCVSIZOPT(*NONE)
I changed them to: MNGRCV(*SYSTEM) DLTRCV(*NO) RCVSIZOPT(*RMVINTENT
*MAXOPT2)
and to MNGRCV(*USER) DLTRCV(*NO) RCVSIZOPT(*RMVINTENT *MAXOPT2)
but no combination of these options works. No matter the settings, as one
receiver is created, the oldest is deleting leaving 12 receivers.
How can I gain control of when receivers are deleted? What am I missing?
Bill Milyard
AS400 Programmer
Bob Evans Farms, Inc.
3776 South High Street, Columbus, OH 43207
Phone: 614/497-4712 Fax: 614/409-2016
Visit us on the web! www.bobevans.com
--
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.
--
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 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.