Discussion:
Question about v7.1 QSG DB2 jobs to be run
Phil Miller
2014-06-12 15:28:52 UTC
Permalink
We are currently running MQ v7.0.1 on z/OS and I am working on the upgrade to MQ v7.1. We are running QSG, so I have a question about the DB2 jobs to run for the upgrade.

According to this link: http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm?lang=en (z/OS: Migrating a queue manager from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1) which says that if required by any PTFs, I make configuration changes to DB2 and rebind DB2. I looked at the HOLDDATA and there are 4 SYSMOD that say you need to run CSQ45BPK. So I thought that's all I needed to do.

But then I found this link http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77109_.htm (z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1) which says that you need to run CSQ457TB (migrate schema from v7.0.1 to v7.1), and then CSQ45BPL (rebind) and CSQ45GEX (grant execution authority).

I did a Google search, and found this link: http://www-01.ibm.com/support/docview.wss?uid=swg21643097 (What is CSQ45BPK), which attempts to explain CSQ45BPK, but to me it confuses the picture even more.
It states:
"PM60589 for WebSphere MQ (WMQ) 7.1.0 and PM65422 for WMQ 7.0.1 implemented a change to use the DB2 pre-compile VERSION(AUTO) option. This means that a BIND PACKAGE of the collection matching the DBRM is all that is needed to add a new package version to the relevant plan when a new DBRM is shipped in WebSphere MQ maintenance. After these APARs, new plan names will not be introduced by maintenance.
CSQ45BPK was added to SCSQPROC to bind the DB2 packages. See the comments in it for customization instructions.

Following PM60589 for WMQ 7.1.0 only CSQ45BPK needs to be run.

While CSQ45BPL and CSQ45GEX do need to be run following the apply of the PTF for PM65422 for WMQ 7.0.1, this is a one time run only because this APAR fixes new plan names permanently for each application plan. Future maintenance for WMQ 7.0.1, following PM65422, will not require these jobs to be run again. If DBRMs are shipped in such maintenance only CSQ45BPK will be required to be run.

CSQ45BPL and CSQ45GEX will still need to be run at installation of each release of base WMQ."

Huh?

Also, I have PM65422 for WMQ v7.0.1 on already if that helps and PM60589 has been Applied to the v7.1 Target files.

So at this point, I am a bit confused. When I upgraded from v6.0 to v7.0.1 I ran 1) CSQ45ATB, 2)CSQ45BPL and then 3) CSQ45GEX and had no issues.

Since I did that on the last upgrade, I am thinking that I need to run 1) CSQ457TB, 2) CSQ45BPL and 3) CSQ45GEX. If that's true, then where does CSQ45BPK come into the picture?


So do I?
A: Run 1) CSQ457TB, 2) CSQ45BPL , 3) CSQ45GEX
B: Run 1) CSQ457TB, 2) CSQ45BPL, 3) CSQ45GEX, 4) CSQ45BPK
C: Run 1) CSQ45BPK
D: None of the above.

Phil Miller | Software Systems Engineer
IT Technical Support Services
Aflac Worldwide Headquarters

________________________________

Confidentiality Notice:
This e-mail and any attachments may contain confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, any distribution, copying, or use of this e-mail or its attachments is prohibited. If you received this message in error, please notify the sender immediately by e-mail and delete this message and any copies. Thank you.

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-06-12 18:28:54 UTC
Permalink
Option A sounds correct. CSQ45BPK is basically a subset of CSQ45BPL, in
that it only BINDs the PACKAGEs, not the PLANs. So, when installing a new
release you need to run CSQ45BPL, which does everything that is contained
in CSQ45BPK, plus a bit more. After that initial run of CSQ45BPL, if you
apply any maintenance to that release which requires the PACKAGEs to be
rebound, you will need to run CSQ45BPK at that point. In the future, when
you migrate to MQ V8, you will need to run CSQ45BPL from the V8 install.

Because we add new attributes to tables etc at release boundaries, the
tables will need to be modified to add these fields, you will need to run
the CSQ457TB job to add the fields (required for v7.1) to your current
tables which are currently configured for v7.0.1.

Hope that makes!

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development




From: Phil Miller <***@AFLAC.COM>
To: ***@listserv.meduniwien.ac.at,
Date: 12/06/2014 16:48
Subject: Question about v7.1 QSG DB2 jobs to be run
Sent by: MQSeries List <***@listserv.meduniwien.ac.at>



We are currently running MQ v7.0.1 on z/OS and I am working on the upgrade
to MQ v7.1. We are running QSG, so I have a question about the DB2 jobs
to run for the upgrade.

According to this link:
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm?lang=en
(z/OS: Migrating a queue manager from WebSphere MQ version 7.0.1 to
WebSphere MQ version 7.1) which says that if required by any PTFs, I make
configuration changes to DB2 and rebind DB2. I looked at the HOLDDATA and
there are 4 SYSMOD that say you need to run CSQ45BPK. So I thought that’s
all I needed to do.

But then I found this link
http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77109_.htm
(z/OS: Review and modify queue manager customizations from WebSphere MQ
version 7.0.1 to WebSphere MQ version 7.1) which says that you need to run
CSQ457TB (migrate schema from v7.0.1 to v7.1), and then CSQ45BPL (rebind)
and CSQ45GEX (grant execution authority).

I did a Google search, and found this link:
http://www-01.ibm.com/support/docview.wss?uid=swg21643097 (What is
CSQ45BPK), which attempts to explain CSQ45BPK, but to me it confuses the
picture even more.
It states:
“PM60589 for WebSphere MQ (WMQ) 7.1.0 and PM65422 for WMQ 7.0.1
implemented a change to use the DB2 pre-compile VERSION(AUTO) option. This
means that a BIND PACKAGE of the collection matching the DBRM is all that
is needed to add a new package version to the relevant plan when a new
DBRM is shipped in WebSphere MQ maintenance. After these APARs, new plan
names will not be introduced by maintenance.
CSQ45BPK was added to SCSQPROC to bind the DB2 packages. See the comments
in it for customization instructions.

Following PM60589 for WMQ 7.1.0 only CSQ45BPK needs to be run.

While CSQ45BPL and CSQ45GEX do need to be run following the apply of the
PTF for PM65422 for WMQ 7.0.1, this is a one time run only because this
APAR fixes new plan names permanently for each application plan. Future
maintenance for WMQ 7.0.1, following PM65422, will not require these jobs
to be run again. If DBRMs are shipped in such maintenance only CSQ45BPK
will be required to be run.

CSQ45BPL and CSQ45GEX will still need to be run at installation of each
release of base WMQ.”

Huh?

Also, I have PM65422 for WMQ v7.0.1 on already if that helps and PM60589
has been Applied to the v7.1 Target files.

So at this point, I am a bit confused. When I upgraded from v6.0 to
v7.0.1 I ran 1) CSQ45ATB, 2)CSQ45BPL and then 3) CSQ45GEX and had no
issues.

Since I did that on the last upgrade, I am thinking that I need to run 1)
CSQ457TB, 2) CSQ45BPL and 3) CSQ45GEX. If that’s true, then where does
CSQ45BPK come into the picture?


So do I?
A: Run 1) CSQ457TB, 2) CSQ45BPL , 3) CSQ45GEX
B: Run 1) CSQ457TB, 2) CSQ45BPL, 3) CSQ45GEX, 4) CSQ45BPK
C: Run 1) CSQ45BPK
D: None of the above.

Phil Miller | Software Systems Engineer
IT Technical Support Services
Aflac Worldwide Headquarters


Confidentiality Notice:
This e-mail and any attachments may contain confidential information
intended solely for the use of the addressee. If the reader of this
message is not the intended recipient, any distribution, copying, or use
of this e-mail or its attachments is prohibited. If you received this
message in error, please notify the sender immediately by e-mail and
delete this message and any copies. Thank you.


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
Phil Miller
2014-06-12 21:13:29 UTC
Permalink
Thank you for responding Paul. That answers my question and clears up the confusion.

From: MQSeries List [mailto:***@LISTSERV.MEDUNIWIEN.AC.AT] On Behalf Of Paul S Dennis
Sent: Thursday, June 12, 2014 2:29 PM
To: ***@LISTSERV.MEDUNIWIEN.AC.AT
Subject: Re: Question about v7.1 QSG DB2 jobs to be run

Option A sounds correct. CSQ45BPK is basically a subset of CSQ45BPL, in that it only BINDs the PACKAGEs, not the PLANs. So, when installing a new release you need to run CSQ45BPL, which does everything that is contained in CSQ45BPK, plus a bit more. After that initial run of CSQ45BPL, if you apply any maintenance to that release which requires the PACKAGEs to be rebound, you will need to run CSQ45BPK at that point. In the future, when you migrate to MQ V8, you will need to run CSQ45BPL from the V8 install.

Because we add new attributes to tables etc at release boundaries, the tables will need to be modified to add these fields, you will need to run the CSQ457TB job to add the fields (required for v7.1) to your current tables which are currently configured for v7.0.1.

Hope that makes!

Thanks
Paul


Paul Dennis
WebSphere MQ for z/OS Development




From: Phil Miller <***@AFLAC.COM<mailto:***@AFLAC.COM>>
To: ***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>,
Date: 12/06/2014 16:48
Subject: Question about v7.1 QSG DB2 jobs to be run
Sent by: MQSeries List <***@listserv.meduniwien.ac.at<mailto:***@listserv.meduniwien.ac.at>>
________________________________



We are currently running MQ v7.0.1 on z/OS and I am working on the upgrade to MQ v7.1. We are running QSG, so I have a question about the DB2 jobs to run for the upgrade.

According to this link: http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77118_.htm?lang=en (z/OS: Migrating a queue manager from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1) which says that if required by any PTFs, I make configuration changes to DB2 and rebind DB2. I looked at the HOLDDATA and there are 4 SYSMOD that say you need to run CSQ45BPK. So I thought that’s all I needed to do.

But then I found this link http://www-01.ibm.com/support/knowledgecenter/api/content/SSFKSJ_7.1.0/com.ibm.mq.doc/mi77109_.htm (z/OS: Review and modify queue manager customizations from WebSphere MQ version 7.0.1 to WebSphere MQ version 7.1) which says that you need to run CSQ457TB (migrate schema from v7.0.1 to v7.1), and then CSQ45BPL (rebind) and CSQ45GEX (grant execution authority).

I did a Google search, and found this link: http://www-01.ibm.com/support/docview.wss?uid=swg21643097 (What is CSQ45BPK), which attempts to explain CSQ45BPK, but to me it confuses the picture even more.
It states:
“PM60589 for WebSphere MQ (WMQ) 7.1.0 and PM65422 for WMQ 7.0.1 implemented a change to use the DB2 pre-compile VERSION(AUTO) option. This means that a BIND PACKAGE of the collection matching the DBRM is all that is needed to add a new package version to the relevant plan when a new DBRM is shipped in WebSphere MQ maintenance. After these APARs, new plan names will not be introduced by maintenance.
CSQ45BPK was added to SCSQPROC to bind the DB2 packages. See the comments in it for customization instructions.

Following PM60589 for WMQ 7.1.0 only CSQ45BPK needs to be run.

While CSQ45BPL and CSQ45GEX do need to be run following the apply of the PTF for PM65422 for WMQ 7.0.1, this is a one time run only because this APAR fixes new plan names permanently for each application plan. Future maintenance for WMQ 7.0.1, following PM65422, will not require these jobs to be run again. If DBRMs are shipped in such maintenance only CSQ45BPK will be required to be run.

CSQ45BPL and CSQ45GEX will still need to be run at installation of each release of base WMQ.”

Huh?

Also, I have PM65422 for WMQ v7.0.1 on already if that helps and PM60589 has been Applied to the v7.1 Target files.

So at this point, I am a bit confused. When I upgraded from v6.0 to v7.0.1 I ran 1) CSQ45ATB, 2)CSQ45BPL and then 3) CSQ45GEX and had no issues.

Since I did that on the last upgrade, I am thinking that I need to run 1) CSQ457TB, 2) CSQ45BPL and 3) CSQ45GEX. If that’s true, then where does CSQ45BPK come into the picture?


So do I?
A: Run 1) CSQ457TB, 2) CSQ45BPL , 3) CSQ45GEX
B: Run 1) CSQ457TB, 2) CSQ45BPL, 3) CSQ45GEX, 4) CSQ45BPK
C: Run 1) CSQ45BPK
D: None of the above.

Phil Miller | Software Systems Engineer
IT Technical Support Services
Aflac Worldwide Headquarters



________________________________

Confidentiality Notice:
This e-mail and any attachments may contain confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, any distribution, copying, or use of this e-mail or its attachments is prohibited. If you received this message in error, please notify the sender immediately by e-mail and delete this message and any copies. Thank you.
________________________________
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>

________________________________

Confidentiality Notice:
This e-mail and any attachments may contain confidential information intended solely for the use of the addressee. If the reader of this message is not the intended recipient, any distribution, copying, or use of this e-mail or its attachments is prohibited. If you received this message in error, please notify the sender immediately by e-mail and delete this message and any copies. Thank you.

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...