Re: Handling Database down period in WMQI
Title: RE: Handling Database down period in WMQI MQ 5.3 on Os/390 Current problem The QMGR has 12 online logs defined. When many become full, only 1 online log is archived to tape at a time, even though many tape drives are available. Is this the way MQ works, or do we have some parameter set wrong? We have duplex archive logs. MQ is using 2 tapes drives at a time. If 11 online logs are full, it requires 11 cycles of offloading each online log to get back to the state where no online logs are full. Utilising ZPARM is there an option or parm that controls how many tape drives MQ can use ? I would appreciate any input Stewart Herd Senior Software Engineer Systems Engineering Services ACS NSC Campus Loughmahon Technology Park Cork Ireland Office +353 21 2309331 Mobile +353 86 1713777
Re: Handling Database down period in WMQI
We had this same condition at a client. We caught the exception and parsed the exception for certain database errors. What you have to watch out for is when the DB comes back online. The first message gets a different error that still implies the DB is unavailable. (WIERD) But WMQI throws an error. So you have messages of type: 1 - Database unavailable 2 - Connection unavailable 3 - All other Database errors When we got 1 & 2 we wrote a message to a queue that triggered a script to GET DISABLE the queue. (Here I'm a little fuzzy). We had another script which reset the GET to EABLE. THis can be started by the Database Backup process. bobbee From: Jas Singh <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Handling Database down period in WMQI Date: Fri, 10 Oct 2003 11:58:04 -0500 We are developing message flows in IBM Websphere MQ Integrator (WMQI), Message flows are using Databases for Lookup and Write operations extensively . The database is shutdown for backup every night for 2 hrs and we need to build a functionality that the messages remain in the INPUT queue until the database is up and running . Option such as backout count or try catch do not suite our purpose as this a normal process we do not want to treat this as an error . Is there any good way of achieving this in Message flow Thanks -Jas *Internet Email Confidentiality* This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Thank you. 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 _ Surf and talk on the phone at the same time with broadband Internet access. Get high-speed for as low as $29.95/month (depending on the local service providers in your area). https://broadband.msn.com 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
Re: Handling Database down period in WMQI
But you'll have to do this for every single queue.
-Original Message-
From: Kulbir S. Thind [mailto:[EMAIL PROTECTED]
Sent: Monday, October 13, 2003 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: Handling Database down period in WMQI
Another alternative is to GET(disable) the message flow input queue before and then
GET(enable) the input queue after.
"Hashir, Mehedi" <[EMAIL PROTECTED]>
Sent by: "MQSeries List" <[EMAIL PROTECTED]>
13-Oct-2003 14:27
Please respond to "MQSeries List" <[EMAIL PROTECTED]>
To:MQSERIES
cc:
Subject:Re: Handling Database down period in WMQI
If this is on a UNIX schedule a cron job
(1) to stop the broker before the database is unavailable and
(2) restart it when it is available.
-Original Message-
From: Jas Singh [mailto:[EMAIL PROTECTED]
Sent: Friday, October 10, 2003 12:58 PM
To: [EMAIL PROTECTED]
Subject: Handling Database down period in WMQI
We are developing message flows in IBM Websphere MQ Integrator (WMQI),
Message flows are using Databases for Lookup and Write operations
extensively .
The database is shutdown for backup every night for 2 hrs and we need to
build a functionality
that the messages remain in the INPUT queue until the database is up and
running .
Option such as backout count or try catch do not suite our purpose as this a
normal process we do not want to treat this as an error .
Is there any good way of achieving this in Message flow
Thanks
-Jas
*Internet Email Confidentiality*
This communication may contain privileged or other confidential
information. If you are not the intended recipient, or believe that you
may have received this communication in error, please reply to the sender
indicating that fact and delete the copy you received. In addition, you
should not print, copy, retransmit, disseminate, or otherwise use the
information contained in this communication. Thank you.
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
CONFIDENTIALITY NOTICE: This E-Mail is intended only
for the use of the individual or entity to which it is addressed and may contain
information that is privileged, confidential and exempt from disclosure under
applicable law. If you have received this communication in error, please do not
distribute and delete the original message. Please notify the sender by E-Mail at the
address shown. Thank you for your compliance.
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
CONFIDENTIALITY NOTICE: This E-Mail is intended only
for the use of the individual or entity to which it is addressed and may contain
information that is privileged, confidential and exempt from disclosure under
applicable law. If you have received this communication in error, please do not
distribute and delete the original message. Please notify the sender by E-Mail at the
address shown. Thank you for your compliance.
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
Re: Handling Database down period in WMQI
Another alternative is to GET(disable) the message flow input queue before and then GET(enable) the input queue after. "Hashir, Mehedi" <[EMAIL PROTECTED]> Sent by: "MQSeries List" <[EMAIL PROTECTED]> 13-Oct-2003 14:27 Please respond to "MQSeries List" <[EMAIL PROTECTED]> To: MQSERIES cc: Subject: Re: Handling Database down period in WMQI If this is on a UNIX schedule a cron job (1) to stop the broker before the database is unavailable and (2) restart it when it is available. -Original Message- From: Jas Singh [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2003 12:58 PM To: [EMAIL PROTECTED] Subject: Handling Database down period in WMQI We are developing message flows in IBM Websphere MQ Integrator (WMQI), Message flows are using Databases for Lookup and Write operations extensively . The database is shutdown for backup every night for 2 hrs and we need to build a functionality that the messages remain in the INPUT queue until the database is up and running . Option such as backout count or try catch do not suite our purpose as this a normal process we do not want to treat this as an error . Is there any good way of achieving this in Message flow Thanks -Jas *Internet Email Confidentiality* This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Thank you. 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 CONFIDENTIALITY NOTICE: This E-Mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this communication in error, please do not distribute and delete the original message. Please notify the sender by E-Mail at the address shown. Thank you for your compliance. 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
Re: Handling Database down period in WMQI
If this is on a UNIX schedule a cron job (1) to stop the broker before the database is unavailable and (2) restart it when it is available. -Original Message- From: Jas Singh [mailto:[EMAIL PROTECTED] Sent: Friday, October 10, 2003 12:58 PM To: [EMAIL PROTECTED] Subject: Handling Database down period in WMQI We are developing message flows in IBM Websphere MQ Integrator (WMQI), Message flows are using Databases for Lookup and Write operations extensively . The database is shutdown for backup every night for 2 hrs and we need to build a functionality that the messages remain in the INPUT queue until the database is up and running . Option such as backout count or try catch do not suite our purpose as this a normal process we do not want to treat this as an error . Is there any good way of achieving this in Message flow Thanks -Jas *Internet Email Confidentiality* This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Thank you. 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 CONFIDENTIALITY NOTICE: This E-Mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you have received this communication in error, please do not distribute and delete the original message. Please notify the sender by E-Mail at the address shown. Thank you for your compliance. 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
Handling Database down period in WMQI
We are developing message flows in IBM Websphere MQ Integrator (WMQI), Message flows are using Databases for Lookup and Write operations extensively . The database is shutdown for backup every night for 2 hrs and we need to build a functionality that the messages remain in the INPUT queue until the database is up and running . Option such as backout count or try catch do not suite our purpose as this a normal process we do not want to treat this as an error . Is there any good way of achieving this in Message flow Thanks -Jas *Internet Email Confidentiality* This communication may contain privileged or other confidential information. If you are not the intended recipient, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received. In addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Thank you. 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
