I defined our production queue manager on OS/390 5 years ago, maybe more than that. Since then our use of MQ has exploded. We now have many more applications that use persistent messages, including one that puts lots of large objects (PDFs, TIFFs, etc.) on a queue persistently. My MQ logs and page sets were originally sized for something on a much smaller scale, and, frankly, they are a mess. We offload logs way too frequently, and our page sets are mostly in 30 extents or so. I expanded one of the page sets a couple of years ago, and added one new one, but other than that things are defined as they were back in 1997.
Some time in January I'd like to revamp the queue manager. The OS/390 setup manual (we're running 5.2, BTW) has formulas on how to size things, and I plan to read that thoroughly sine it may be years before I do this again. My initial thinking is to build a temporary queue manager, copy any production persistent messages to it, delete and redefine my real queue manager, and copy the messages back. What I'm wondering about is whether anyone has any tips/techniques/gotchas that I should know about. Would it be smarter to expand the existing page sets instead of redefining the queue manager? One constraint is that I would like to redesign my storage classes as part of this process (they are a mess, too). Another constraint is that I do NOT have authority to update the MQSeries procs. So I probably won't be able to add or delete page sets from the proc on the reconfig day. All tips are welcomed! 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
