RE: Old Journal Receivers problem

["Walden Leverich" <walden@xxxxxxxxxxxxxxx>]

FYI, it is no longer (V4R1 I think) necessary to have all the files in a
commitment boundary journaled to the same journal. When two-phase commit
(multi-machine commit) came to the AS/400 the restriction went away since
files on two machines cannot be journaled to the same journal there was no
reason to require files on the same machine to be journaled to the same
journal. Your vendor could be doing something really strange, but most
likely they haven't been reading their release notes.

-Walden

-----Original Message-----
From: owner-midrange-l@midrange.com
[mailto:owner-midrange-l@midrange.com]On Behalf Of BKstaple
Sent: Friday, April 24, 1998 9:47 PM
To: MIDRANGE-L@midrange.com
Subject: Old Journal Receivers problem


Greetings All;

I have a journal problem.  This journal starts to exceed 1.5 gig every day,
so
I have wrote a program that will go out 3 times a day to detach the journal
reciever, then generate and attach a new one. (The software vendor says that
they need all of their files journaled to one journal for commitment
control)

What I want to know is, is there a way to programatically delete the old
recievers after they have been saved?

Thanks for any help that you can give.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---