Discussion:
MQ 7.1 on z/OS and OPMODE
Potkay, Peter M (CTO Architecture + Engineering)
2014-05-21 14:44:50 UTC
Permalink
MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll back to 7.0.1, but why does version still show 701? I was able to create a new CHLAUTH rule, so that's 7.1, so shouldn't version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE COMPAT 701. That's what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1 libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back to 7.0.1, what am I supposed to see for OPMODE? What the first link says (COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo in one of these links?

-Peter

************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Paul S Dennis
2014-05-21 14:56:36 UTC
Permalink
Hi Peter,

There are two different things at play here, what is compiled into the
zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have
OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC.
The version number here isn't specifying what you are compatible with
(that is determined by the qmgr at startup time), it is more to ensure
that you don't accidentally take an old zPARM job and reassemble with the
V7.1 libraries and accidentally set NEWFUNC straight away. If you have
OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble,
reminding you to go and check this value, and hopefully changing NEWFUNC
to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the
QMGR is started at V710 it will then determine what compatibility you have
etc, so will show (potentially) as different value for the DIS SYSTEM
output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and
you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701),
indicating that you can migrate back to 7.0.1. If you had come from V6, it
should show (COMPAT,600), indicating you can migrate back to v6. If you
have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show
(NEWFUNC,710) and there is no way after that to get it back to
(COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)"
<***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>



MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll
back to 7.0.1, but why does version still show 701? I was able to create a
new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE
COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from
WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set
OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does
not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the
version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1
libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back
to 7.0.1, what am I supposed to see for OPMODE? What the first link says
(COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo
in one of these links?

-Peter

************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************


List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Voges, P. (Pieter)
2014-05-21 15:04:40 UTC
Permalink
Very complete answer thanks Paul.

Note: This is something that has probably been rectified since – but when I did my first assembly of ZPARM with the OPMODE parameter in the middle of 2012, there was a typing error in one of the installation manuals whereby the 710, 701 was typed wrong in one instance. And like you said – you just can’t get it assembled.

Thanks - Pieter


[Description: cid:***@01CDD217.0FB0FAF0]

Pieter Voges
Technical Specialist | Group Technology | Nedbank Limited
Protea Heights, Brackenfell, Western-Cape, 7560 South Africa
c +27 (0)83 6455 300 @ ***@nedbank.co.za<mailto:***@nedbank.co.za>

Website: www.nedbank.co.za<http://www.nedbank.co.za/>


[Description: Description: Description: cid:***@01CDD20C.8E3FD180]

SAVE TREES, SAVE PAPER – THINK BEFORE YOU PRINT Nedbank is proud to be Africa’s first carbon-neutral bank and official conservation partner of the WWF-SA.





From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: 21 May 2014 04:57 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC. The version number here isn't specifying what you are compatible with (that is determined by the qmgr at startup time), it is more to ensure that you don't accidentally take an old zPARM job and reassemble with the V7.1 libraries and accidentally set NEWFUNC straight away. If you have OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble, reminding you to go and check this value, and hopefully changing NEWFUNC to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the QMGR is started at V710 it will then determine what compatibility you have etc, so will show (potentially) as different value for the DIS SYSTEM output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701), indicating that you can migrate back to 7.0.1. If you had come from V6, it should show (COMPAT,600), indicating you can migrate back to v6. If you have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show (NEWFUNC,710) and there is no way after that to get it back to (COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________



MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll back to 7.0.1, but why does version still show 701? I was able to create a new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1 libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back to 7.0.1, what am I supposed to see for OPMODE? What the first link says (COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo in one of these links?

-Peter


************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>

********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Potkay, Peter M (CTO Architecture + Engineering)
2014-05-21 16:18:59 UTC
Permalink
Regarding the version, thanks to Morag’s tip I now understand that 07010000 actual means 7.1

http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/sc12200_.htm?locale=en

VERSION
The version of the WebSphere MQ installation, the queue manager is associated with. The version has the format VVRRMMFF:
VV: Version
RR: Release
MM: Maintenance level
FF: Fix level



Back to OPMODE
.
So Paul, you are saying that by design what DISPLAY SYSTEM shows for OPMODE is not what OPMODE is set to in z/Parm? You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back to 7.0.1, and then it will display as COMPAT 701 when you do DISPLAY SYSTEM?







Peter Potkay



From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 21, 2014 10:57 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC. The version number here isn't specifying what you are compatible with (that is determined by the qmgr at startup time), it is more to ensure that you don't accidentally take an old zPARM job and reassemble with the V7.1 libraries and accidentally set NEWFUNC straight away. If you have OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble, reminding you to go and check this value, and hopefully changing NEWFUNC to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the QMGR is started at V710 it will then determine what compatibility you have etc, so will show (potentially) as different value for the DIS SYSTEM output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701), indicating that you can migrate back to 7.0.1. If you had come from V6, it should show (COMPAT,600), indicating you can migrate back to v6. If you have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show (NEWFUNC,710) and there is no way after that to get it back to (COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________



MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll back to 7.0.1, but why does version still show 701? I was able to create a new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1 libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back to 7.0.1, what am I supposed to see for OPMODE? What the first link says (COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo in one of these links?

-Peter


************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Paul S Dennis
2014-05-21 19:37:31 UTC
Permalink
Question: So Paul, you are saying that by design what DISPLAY SYSTEM shows
for OPMODE is not what OPMODE is set to in z/Parm?

Answer: Yes, that is exactly what I am saying. They do however sometimes
line up... for example, if you set OPMODE=(NEWFUNC,710) in your zPARM,
this would also be what you would see in DIS SYSTEM, because you would be
in NEWFUNC mode, and not able to migrate back to anything earlier than
710.


Question: You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to
come up as 7.1 and be able to fall back to 7.0.1

Answer: Sort of.... having COMPAT,710 doesn't make the QMGR come up in
v7.1... you need to point at the v7.1 libraries for that... but I guess
that wasn't quite what you meant! Setting COMPAT,710 in the zPARM enables
you to assemble a zPARM using the V7.1 libraries and specify that the mode
of the QMGR should be COMPAT. This means that when a QMGR that has been at
v7.0.1 is started with this zPARM and the v7.1 libraries, it will come up
in COMPAT,701... which means you can migrate back to v7.0.1. The rule is
that when you start up at a higher release with a zPARM that says COMPAT,
you can migrate back to wherever you came from... but only one hop, so if
you were at v6, then went to v7.0.1 COMPAT, and then v7.1 COMPAT, you
could go back to V7.0.1 COMPAT, but not back to V6 (as that would be a
double hop back). Another thing worth point out is that if you have a
V7.0.1 QMGR, with a zPARM of OPMODE=(NEWFUNC,701) and then start the QMGR
using the V7.1 libraries, but without reassembling the zPARM, you would
start in (COMPAT,701), not NEWFUNC.


Question: and then it will display as COMPAT 701 when you do DISPLAY
SYSTEM?

Answer: Yes.


Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)"
<***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 21/05/2014 17:19
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>



Regarding the version, thanks to Morag’s tip I now understand that
07010000 actual means 7.1

http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/sc12200_.htm?locale=en

VERSION
The version of the WebSphere MQ installation, the queue manager is
associated with. The version has the format VVRRMMFF:
VV: Version
RR: Release
MM: Maintenance level
FF: Fix level



Back to OPMODE
.
So Paul, you are saying that by design what DISPLAY SYSTEM shows for
OPMODE is not what OPMODE is set to in z/Parm? You’ll set it in z/Parm to
(COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back
to 7.0.1, and then it will display as COMPAT 701 when you do DISPLAY
SYSTEM?







Peter Potkay



From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf
Of Paul S Dennis
Sent: Wednesday, May 21, 2014 10:57 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the
zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have
OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC.
The version number here isn't specifying what you are compatible with
(that is determined by the qmgr at startup time), it is more to ensure
that you don't accidentally take an old zPARM job and reassemble with the
V7.1 libraries and accidentally set NEWFUNC straight away. If you have
OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble,
reminding you to go and check this value, and hopefully changing NEWFUNC
to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the
QMGR is started at V710 it will then determine what compatibility you have
etc, so will show (potentially) as different value for the DIS SYSTEM
output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and
you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701),
indicating that you can migrate back to 7.0.1. If you had come from V6, it
should show (COMPAT,600), indicating you can migrate back to v6. If you
have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show
(NEWFUNC,710) and there is no way after that to get it back to
(COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <
***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>




MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll
back to 7.0.1, but why does version still show 701? I was able to create a
new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm


Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE
COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm

Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from
WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set
OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does
not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the
version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1
libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back
to 7.0.1, what am I supposed to see for OPMODE? What the first link says
(COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo
in one of these links?

-Peter

************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************


List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************


List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Potkay, Peter M (CTO Architecture + Engineering)
2014-05-28 19:55:36 UTC
Permalink
How long can you run in COMPAT mode before you change to NEWFUNC?
Forever, no harm done?
Or maybe there is some internal checkpoint file that grows and grows that blows up after x days, so you better move to NEWFUNC before x days?


Peter Potkay

From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 21, 2014 3:38 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Question: So Paul, you are saying that by design what DISPLAY SYSTEM shows for OPMODE is not what OPMODE is set to in z/Parm?

Answer: Yes, that is exactly what I am saying. They do however sometimes line up... for example, if you set OPMODE=(NEWFUNC,710) in your zPARM, this would also be what you would see in DIS SYSTEM, because you would be in NEWFUNC mode, and not able to migrate back to anything earlier than 710.


Question: You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back to 7.0.1

Answer: Sort of.... having COMPAT,710 doesn't make the QMGR come up in v7.1... you need to point at the v7.1 libraries for that... but I guess that wasn't quite what you meant! Setting COMPAT,710 in the zPARM enables you to assemble a zPARM using the V7.1 libraries and specify that the mode of the QMGR should be COMPAT. This means that when a QMGR that has been at v7.0.1 is started with this zPARM and the v7.1 libraries, it will come up in COMPAT,701... which means you can migrate back to v7.0.1. The rule is that when you start up at a higher release with a zPARM that says COMPAT, you can migrate back to wherever you came from... but only one hop, so if you were at v6, then went to v7.0.1 COMPAT, and then v7.1 COMPAT, you could go back to V7.0.1 COMPAT, but not back to V6 (as that would be a double hop back). Another thing worth point out is that if you have a V7.0.1 QMGR, with a zPARM of OPMODE=(NEWFUNC,701) and then start the QMGR using the V7.1 libraries, but without reassembling the zPARM, you would start in (COMPAT,701), not NEWFUNC.


Question: and then it will display as COMPAT 701 when you do DISPLAY SYSTEM?

Answer: Yes.


Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 17:19
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________



Regarding the version, thanks to Morag’s tip I now understand that 07010000 actual means 7.1

http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/sc12200_.htm?locale=en

VERSION
The version of the WebSphere MQ installation, the queue manager is associated with. The version has the format VVRRMMFF:
VV: Version
RR: Release
MM: Maintenance level
FF: Fix level



Back to OPMODE
.
So Paul, you are saying that by design what DISPLAY SYSTEM shows for OPMODE is not what OPMODE is set to in z/Parm? You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back to 7.0.1, and then it will display as COMPAT 701 when you do DISPLAY SYSTEM?







Peter Potkay



From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 21, 2014 10:57 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC. The version number here isn't specifying what you are compatible with (that is determined by the qmgr at startup time), it is more to ensure that you don't accidentally take an old zPARM job and reassemble with the V7.1 libraries and accidentally set NEWFUNC straight away. If you have OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble, reminding you to go and check this value, and hopefully changing NEWFUNC to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the QMGR is started at V710 it will then determine what compatibility you have etc, so will show (potentially) as different value for the DIS SYSTEM output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701), indicating that you can migrate back to 7.0.1. If you had come from V6, it should show (COMPAT,600), indicating you can migrate back to v6. If you have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show (NEWFUNC,710) and there is no way after that to get it back to (COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________




MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll back to 7.0.1, but why does version still show 701? I was able to create a new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1 libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back to 7.0.1, what am I supposed to see for OPMODE? What the first link says (COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo in one of these links?

-Peter


************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________

List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________

List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>

************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Paul S Dennis
2014-05-28 23:02:29 UTC
Permalink
You can in theory run for as long as you want in COMPAT mode (and also in
practice!!). However, OPMODE is really intended to control whether you are
able to backwards migrate your QMGR. If you have migrated from V7.0.1 to
V7.1 COMPAT, and been there for any length of time, it would seem unlikely
that you would then want to backwards migrate to V7.0.1, therefore, the
next natural step would be to move to V7.1 NEWFUNC to be able to start
taking advantage of some of the new functionality that is controlled by
NEWFUNC. Once in NEWFUNC, you don't HAVE to start using the new function,
just have the option of doing so. What you might want to consider is
migrating to V7.1 COMPAT and then during your next maintenance window,
look at enabling NEWFUNC.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development




From: "Potkay, Peter M (CTO Architecture + Engineering)"
<***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 28/05/2014 20:55
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>



How long can you run in COMPAT mode before you change to NEWFUNC?
Forever, no harm done?
Or maybe there is some internal checkpoint file that grows and grows that
blows up after x days, so you better move to NEWFUNC before x days?


Peter Potkay

From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf
Of Paul S Dennis
Sent: Wednesday, May 21, 2014 3:38 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Question: So Paul, you are saying that by design what DISPLAY SYSTEM shows
for OPMODE is not what OPMODE is set to in z/Parm?

Answer: Yes, that is exactly what I am saying. They do however sometimes
line up... for example, if you set OPMODE=(NEWFUNC,710) in your zPARM,
this would also be what you would see in DIS SYSTEM, because you would be
in NEWFUNC mode, and not able to migrate back to anything earlier than
710.


Question: You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to
come up as 7.1 and be able to fall back to 7.0.1

Answer: Sort of.... having COMPAT,710 doesn't make the QMGR come up in
v7.1... you need to point at the v7.1 libraries for that... but I guess
that wasn't quite what you meant! Setting COMPAT,710 in the zPARM enables
you to assemble a zPARM using the V7.1 libraries and specify that the mode
of the QMGR should be COMPAT. This means that when a QMGR that has been at
v7.0.1 is started with this zPARM and the v7.1 libraries, it will come up
in COMPAT,701... which means you can migrate back to v7.0.1. The rule is
that when you start up at a higher release with a zPARM that says COMPAT,
you can migrate back to wherever you came from... but only one hop, so if
you were at v6, then went to v7.0.1 COMPAT, and then v7.1 COMPAT, you
could go back to V7.0.1 COMPAT, but not back to V6 (as that would be a
double hop back). Another thing worth point out is that if you have a
V7.0.1 QMGR, with a zPARM of OPMODE=(NEWFUNC,701) and then start the QMGR
using the V7.1 libraries, but without reassembling the zPARM, you would
start in (COMPAT,701), not NEWFUNC.


Question: and then it will display as COMPAT 701 when you do DISPLAY
SYSTEM?

Answer: Yes.


Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <
***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 21/05/2014 17:19
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>




Regarding the version, thanks to Morag’s tip I now understand that
07010000 actual means 7.1

http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/sc12200_.htm?locale=en


VERSION
The version of the WebSphere MQ installation, the queue manager is
associated with. The version has the format VVRRMMFF:
VV: Version
RR: Release
MM: Maintenance level
FF: Fix level



Back to OPMODE
.
So Paul, you are saying that by design what DISPLAY SYSTEM shows for
OPMODE is not what OPMODE is set to in z/Parm? You’ll set it in z/Parm to
(COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back
to 7.0.1, and then it will display as COMPAT 701 when you do DISPLAY
SYSTEM?







Peter Potkay



From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf
Of Paul S Dennis
Sent: Wednesday, May 21, 2014 10:57 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the
zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have
OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC.
The version number here isn't specifying what you are compatible with
(that is determined by the qmgr at startup time), it is more to ensure
that you don't accidentally take an old zPARM job and reassemble with the
V7.1 libraries and accidentally set NEWFUNC straight away. If you have
OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble,
reminding you to go and check this value, and hopefully changing NEWFUNC
to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the
QMGR is started at V710 it will then determine what compatibility you have
etc, so will show (potentially) as different value for the DIS SYSTEM
output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and
you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701),
indicating that you can migrate back to 7.0.1. If you had come from V6, it
should show (COMPAT,600), indicating you can migrate back to v6. If you
have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show
(NEWFUNC,710) and there is no way after that to get it back to
(COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <
***@THEHARTFORD.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>





MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll
back to 7.0.1, but why does version still show 701? I was able to create a
new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm


Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE
COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm

Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from
WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set
OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does
not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the
version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1
libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back
to 7.0.1, what am I supposed to see for OPMODE? What the first link says
(COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo
in one of these links?

-Peter

************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************



List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU



List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************


List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
************************************************************
This communication, including attachments, is for the exclusive use of
addressee and may contain proprietary, confidential and/or privileged
information. If you are not the intended recipient, any use, copying,
disclosure, dissemination or distribution is strictly prohibited. If you
are not the intended recipient, please notify the sender immediately by
return e-mail, delete this communication and destroy all copies.
************************************************************


List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html
Potkay, Peter M (CTO Architecture + Engineering)
2014-05-29 15:11:46 UTC
Permalink
According the following link it looks like only 3 new features are restricted by NEWFUNC, and all new 7.1 features should be available even in COMPAT mode.

http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21596103

OPMODE=NEWFUNC
OPMODE=NEWFUNC<http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/mi20120_.htm> controls functions to:
- allow connection to a CF structure at CFLevel (5)
- enable resilience to a coupling facility connectivity failure (CFCONLOS)
- enable OTMA Resource Monitoring

Is that a correct assumption Paul, that other than these 3 features it’s safe to start using all other MQ 7.1 features even in COMPAT mode?




Peter Potkay

From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 28, 2014 7:02 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: MQ 7.1 on z/OS and OPMODE

You can in theory run for as long as you want in COMPAT mode (and also in practice!!). However, OPMODE is really intended to control whether you are able to backwards migrate your QMGR. If you have migrated from V7.0.1 to V7.1 COMPAT, and been there for any length of time, it would seem unlikely that you would then want to backwards migrate to V7.0.1, therefore, the next natural step would be to move to V7.1 NEWFUNC to be able to start taking advantage of some of the new functionality that is controlled by NEWFUNC. Once in NEWFUNC, you don't HAVE to start using the new function, just have the option of doing so. What you might want to consider is migrating to V7.1 COMPAT and then during your next maintenance window, look at enabling NEWFUNC.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development




From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 28/05/2014 20:55
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________



How long can you run in COMPAT mode before you change to NEWFUNC?
Forever, no harm done?
Or maybe there is some internal checkpoint file that grows and grows that blows up after x days, so you better move to NEWFUNC before x days?


Peter Potkay

From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 21, 2014 3:38 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ 7.1 on z/OS and OPMODE

Question: So Paul, you are saying that by design what DISPLAY SYSTEM shows for OPMODE is not what OPMODE is set to in z/Parm?

Answer: Yes, that is exactly what I am saying. They do however sometimes line up... for example, if you set OPMODE=(NEWFUNC,710) in your zPARM, this would also be what you would see in DIS SYSTEM, because you would be in NEWFUNC mode, and not able to migrate back to anything earlier than 710.


Question: You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back to 7.0.1

Answer: Sort of.... having COMPAT,710 doesn't make the QMGR come up in v7.1... you need to point at the v7.1 libraries for that... but I guess that wasn't quite what you meant! Setting COMPAT,710 in the zPARM enables you to assemble a zPARM using the V7.1 libraries and specify that the mode of the QMGR should be COMPAT. This means that when a QMGR that has been at v7.0.1 is started with this zPARM and the v7.1 libraries, it will come up in COMPAT,701... which means you can migrate back to v7.0.1. The rule is that when you start up at a higher release with a zPARM that says COMPAT, you can migrate back to wherever you came from... but only one hop, so if you were at v6, then went to v7.0.1 COMPAT, and then v7.1 COMPAT, you could go back to V7.0.1 COMPAT, but not back to V6 (as that would be a double hop back). Another thing worth point out is that if you have a V7.0.1 QMGR, with a zPARM of OPMODE=(NEWFUNC,701) and then start the QMGR using the V7.1 libraries, but without reassembling the zPARM, you would start in (COMPAT,701), not NEWFUNC.


Question: and then it will display as COMPAT 701 when you do DISPLAY SYSTEM?

Answer: Yes.


Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 17:19
Subject: Re: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________




Regarding the version, thanks to Morag’s tip I now understand that 07010000 actual means 7.1

http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/sc12200_.htm?locale=en

VERSION
The version of the WebSphere MQ installation, the queue manager is associated with. The version has the format VVRRMMFF:
VV: Version
RR: Release
MM: Maintenance level
FF: Fix level



Back to OPMODE
.
So Paul, you are saying that by design what DISPLAY SYSTEM shows for OPMODE is not what OPMODE is set to in z/Parm? You’ll set it in z/Parm to (COMPAT,710) to tell a 7.0.1 QM to come up as 7.1 and be able to fall back to 7.0.1, and then it will display as COMPAT 701 when you do DISPLAY SYSTEM?







Peter Potkay



From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Wednesday, May 21, 2014 10:57 AM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT>
Subject: Re: MQ 7.1 on z/OS and OPMODE

Hi Peter,

There are two different things at play here, what is compiled into the zParm, and what is shown for display system output.

When you compile a zPARM using the v7.1 libraries you will need to have OPMODE=(xxxxxx,710) specified, where xxxxxx is either COMPAT of NEWFUNC. The version number here isn't specifying what you are compatible with (that is determined by the qmgr at startup time), it is more to ensure that you don't accidentally take an old zPARM job and reassemble with the V7.1 libraries and accidentally set NEWFUNC straight away. If you have OPMODE=(NEWFUNC,701) in your zPARM job, it will fail to assemble, reminding you to go and check this value, and hopefully changing NEWFUNC to COMPAT at the same time, resulting in OPMODE=(NEWFUNC,710). When the QMGR is started at V710 it will then determine what compatibility you have etc, so will show (potentially) as different value for the DIS SYSTEM output. For example, if you have OPMODE=(COMPAT,710) in your zPARM, and you have migrated from V7.0.1 it should show OPMODE as (COMPAT,701), indicating that you can migrate back to 7.0.1. If you had come from V6, it should show (COMPAT,600), indicating you can migrate back to v6. If you have ever started with OPMODE=(NEWFUNC,710) the DIS SYSTEM would then show (NEWFUNC,710) and there is no way after that to get it back to (COMPAT,701) etc.

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development



From: "Potkay, Peter M (CTO Architecture + Engineering)" <***@THEHARTFORD.COM<mailto:***@THEHARTFORD.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 21/05/2014 15:45
Subject: MQ 7.1 on z/OS and OPMODE
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________





MQ on z/OS
The QM is running at 7.0.1 happily for years.
MQ 7.1 is installed.

MQ Explorer and MO71 now show:
Command Level = 710
Version = 07010000
DISPLAY SYSTEM shows OPMODE COMPAT , 701

OK, I think I am good - My QM is ready to do 7.1 stuff, and we can roll back to 7.0.1, but why does version still show 701? I was able to create a new CHLAUTH rule, so that’s 7.1, so shouldn’t version also show 710?


This link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77119_.htm

Says if I want to be able to roll back to 7.0.1 I should be showing OPMODE COMPAT 701. That’s what I show. So far so good.


But this link:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm
Has this confusing statement

"As part of z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1, you must set OPMODE to (COMPAT,710). If you have not set OPMODE, the queue manager does not start.
The (COMPAT,710) setting does two things:
i.It checks that you are starting the queue manager that links to the version 7.1 libraries.
ii.It disables the use of new function in version 7.1.
You can revert to running the queue manager with the version 7.0.1 libraries, if you have never set OPMODE to (NEWFUNC,710)
"


???

So if I want to be running as 7.1, but still have the ability to fall back to 7.0.1, what am I supposed to see for OPMODE? What the first link says (COMPAT 701), or what the second link says (COMPAT,710)? Is there a typo in one of these links?

-Peter


************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________


List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________


List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>

************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________

List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________

List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>

************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************



________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>


Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
________________________________
List Archive<http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings<http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe<mailto:***@LISTSERV.MEDUNIWIEN.AC.AT?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com<http://www.lsoft.com/resources/manuals.asp>
************************************************************
This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies.
************************************************************


To unsubscribe, write to ***@LISTSERV.MEDUNIWIEN.AC.AT and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Loading...