× 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'd leave purges for the weekend.  If you're running cash, posting, daily
reports, etc., overnight and you schedule an application backup too, you
won't have much time and the system will be active anyway.  Purging is a
disk-intensive task.

If you use system-managed journal receiver sizes {CHGJRN MGNRVC(*SYSTEM)
DLTRCV(*NO)} command, the system will automatically change journal receivers
if  the active receiver reaches the maximum (user-specified) size.  Setting
this up does not affect the operation of AAM808; there isn't any reason for
a journal to lock because of a receiver size problem.  As long as you have
enough DASD, you'll be fine.  AAM808 will play catch-up; if there's a tape
problem, the receivers will stay on the system until you address the tape
issue and start AAM808 again.

I think we have a better version of AAM808 in newer releases; the current
version starts at the beginning of the journal chain, saves each receiver
individually, and deletes the receiver when the save is complete.  This
granularizes the save process and makes restoring much easier (but I hope
you never have to do it).

Regards,
Reeve

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of JMBauman@wardtrucking.com
Sent: Monday, April 01, 2002 1:23 PM
To: rpg400-l@midrange.com
Subject: Skip Writing to Journal Receiver When Updating a Journaled File


>John, are you running a freight bill purge?  If so, I suggest you do it on
a
>weekly basis.  Otherwise, if you can schedule six hours of downtime: end
>QINTER, end journaling of FRP001, FRP002, etc., run the purge, restart
>journaling, and restart QINTER.  Don't forget to let the system manage the
>journal receiver size; this will prevent your job from filling a single
>journal receiver and locking the job.  Finally, you can solve the journal
>receiver size problem by scheduling AAM808 to run hourly when the purge
>process is running.

Hey Reeve, How did you guess?  Right now I am running the purges on the
weekend and I would like to be able run them during the week (as you can
imagine).  Being relatively stupid concerning about journaling, how do I
have the system manage the journal size?  I am also enticed by the idea of
scheduling AAM808 to run every hour.  Do you think this is often enough?  I
want to make sure I absolutely do no fill the receiver, this caused a
system lockup before because of the commitment control.  Thanks for all the
help (To all)!

Regards

John M. Bauman


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



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.