At the same time, I've seen clients with both copies on the same disk! On an IBM project '97-'00, where the messaging was all nonpersistent and it was MQ v2.1, we used single logging for performance reasons. Only time that I've seen it done.
--- Jim Nuckolls <[EMAIL PROTECTED]> wrote: > All of the accounts I have been involved with still > use the > dual-write attributes. I have seen Shark's crash so > I wouldn't > bet my shop and installation on that one. > > Cheers... > Jim Nuckolls > > Donald Blake wrote: > > > > > Currently, we're running duplexed BSDS's, Active > Logs and Archive logs. > > The dasd behind that is IBM Shark. Considering the > error correction and > > duplexing inside the DASD array, I'm considering > going to a single BSDS, > > Active and Archive logs. How many running queue > managers on the > > mainframe are still using duplexing on their > MQSeries datasets on zOS? > > If you are, what is your rationale for doing so? > > Instructions for managing your mailing list > subscription are provided in > the Listserv General Users Guide available at > http://www.lsoft.com > Archive: http://vm.akh-wien.ac.at/MQSeries.archive > Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
