|
I keep getting these messages. Does someone have their auto responder turned an and sending to everyone? Am I the only one getting this? --------------------------- Your message To: as400-all@raleigh.ibm.com Subject: RE: Tracing programs Sent: 4/25/98 1:44 PM was deleted without being read on 4/27/98 5:04 PM. ----------------------------- Bradley V. Stone bvstone@taylorcorp.com http://prairie.lakes.com/~bvstone/ "Robble Robble" - The Hamburgler > -----Original Message----- > From: Walden Leverich [SMTP:walden@techsoftinc.com] > Sent: Monday, April 27, 1998 3:28 PM > To: MIDRANGE-L@midrange.com > Subject: RE: Old Journal Receivers problem > > 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 > +--- +--- | 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 +---
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.