Hi Dana and Andy, You can omit (ZPARM) OPMODE and let it default as a first attempt. You can code MEMLIMIT=3G, provided that OPMODE is set to either (NEWFUNC,800) or (NEWFUNC,900) (in a later attempt). You should also code REGION=0M in the MSTR Proc.
Just before shutting down the Queue Manager, issue DISPLAY Commands (in a batch job) which will allow you to re-create MQ entities (offloaded in Command format). Before doing anything, it is prudent to back up (with the Queue Manager down) all MQ VSAM Datasets (e.g. BSDS, Pagesets) before starting up the Queue Manager with the new level of software. Regards, David On 2019-08-29 11:55, Andy Cooper wrote: > Hi, Dana... > > I did this exact upgrade last year when our shop upgraded z/OS v1.13 to v2.2. > As far as I remember, this upgrade only needed an MQ parm changed for the > correct / new version - can't recall what parm it was, but I'm sure you can > find it. Didn't have to change anything else, and the upgrade was > successful, especially when you consider your "vanilla" system. Beware > though...at least in my experience, we ran into problems trying to go back to > v7 (due to a problem with the z/OS upgrade and that might have had everything > to do with the MQ problems at the time). All in all, again, to the best of > my memory, one parm change...point to the new MQ libraries...test / verify MQ > queue connections...and you should be good to go! > > > Andy > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > . > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
