Re: SYSTEM.CHANNEL.SYNCQ
Thanks Rebecca, Paul and Morag. I just found that all the new additions to the SYNCQ belong to the channels that are no longer in use. I am planning to remove those channel defintions from our MQ. That should keep the SYNCQ from growing. Thanks again. Morag Hughson <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 11/04/2002 02:32:28 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Thanks Paul - I would echo the need to make sure you are up-to-date on maintenance, especially make sure you have PQ26840 applied. It was a very early APAR on V2.1 so you may well have it already, but it could be the cause of your problem if your queue depth really is growing out of proportion to the number of channel instances and the number of records each channel instance could have. Cheers Morag (now back from conference and also back from a trip to windy Shetland where she got stuck when all planes were cancelled due to high wind - normal service will be resumed shortly) Morag Hughson WebSphere MQ for z/OS Development Internet: [EMAIL PROTECTED] Bahman wrote: >Thanks Rebecca, I'll go through your suggested path and delete the messages >that belong to non-existing channels. But, while I am not adding any new >channel, >I see this queue is growing. Any idea why? Rebecca wrote: >Sorry, no. Perhaps Morag H. would care to comment. -- Rebecca Morag is away as a UK User conference for a day or two so let me answer in her place. The SYSTEM.CHANNEL.SYNCQ contains essentially two types of messages, both to do with storing channel status. 1/ There is a message (possibly two) for each instance of channel that has run and transferred a persistent message to a remote partner. These messages maintain the synchronisation state between the two ends of the channels. If you delete these messages your channel will forget where it got to. This will almost certainly lead to sequence number problems since the channel will start at 1 again and you will have to issue RESET CHANNEL. In the worst case, if the channel was indoubt, you may may also cause messages to be duplicated. 2/ There may also be a message recording the status of the channel. In other words, whether the channel is STOPPED, RETRYING etc etc. If you delete these messages the worsed that will happen is that when you recycle your Queue Manager a channel will come up inactive rather than STOPPED or RETRYING. Now there were a few problems with the initial implementation of the type 2 messages. You could find that even a channel retrying would add a few more of these messages. I would ensure that you are on the latest service level for whatever release you are running. In the general case though don't be fooled into thinking that you've got a problem with the queue just because you have more messages on there that you have channels. Since you have a Type 1 message for each *partner* you must consider how many locations you are talking to. So a single RCVR channel which receives connections from 100 other Queue Managers will, quite rightly, be responsible for 100 messages on this queue. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN 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 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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
Re: SYSTEM.CHANNEL.SYNCQ
Thanks Paul - I would echo the need to make sure you are up-to-date on maintenance, especially make sure you have PQ26840 applied. It was a very early APAR on V2.1 so you may well have it already, but it could be the cause of your problem if your queue depth really is growing out of proportion to the number of channel instances and the number of records each channel instance could have. Cheers Morag (now back from conference and also back from a trip to windy Shetland where she got stuck when all planes were cancelled due to high wind - normal service will be resumed shortly) Morag Hughson WebSphere MQ for z/OS Development Internet: [EMAIL PROTECTED] Bahman wrote: >Thanks Rebecca, I'll go through your suggested path and delete the messages >that belong to non-existing channels. But, while I am not adding any new >channel, >I see this queue is growing. Any idea why? Rebecca wrote: >Sorry, no. Perhaps Morag H. would care to comment. -- Rebecca Morag is away as a UK User conference for a day or two so let me answer in her place. The SYSTEM.CHANNEL.SYNCQ contains essentially two types of messages, both to do with storing channel status. 1/ There is a message (possibly two) for each instance of channel that has run and transferred a persistent message to a remote partner. These messages maintain the synchronisation state between the two ends of the channels. If you delete these messages your channel will forget where it got to. This will almost certainly lead to sequence number problems since the channel will start at 1 again and you will have to issue RESET CHANNEL. In the worst case, if the channel was indoubt, you may may also cause messages to be duplicated. 2/ There may also be a message recording the status of the channel. In other words, whether the channel is STOPPED, RETRYING etc etc. If you delete these messages the worsed that will happen is that when you recycle your Queue Manager a channel will come up inactive rather than STOPPED or RETRYING. Now there were a few problems with the initial implementation of the type 2 messages. You could find that even a channel retrying would add a few more of these messages. I would ensure that you are on the latest service level for whatever release you are running. In the general case though don't be fooled into thinking that you've got a problem with the queue just because you have more messages on there that you have channels. Since you have a Type 1 message for each *partner* you must consider how many locations you are talking to. So a single RCVR channel which receives connections from 100 other Queue Managers will, quite rightly, be responsible for 100 messages on this queue. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN 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 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: SYSTEM.CHANNEL.SYNCQ
Bahman wrote: >Thanks Rebecca, I'll go through your suggested path and delete the messages >that belong to non-existing channels. But, while I am not adding any new >channel, >I see this queue is growing. Any idea why? Rebecca wrote: >Sorry, no. Perhaps Morag H. would care to comment. -- Rebecca Morag is away as a UK User conference for a day or two so let me answer in her place. The SYSTEM.CHANNEL.SYNCQ contains essentially two types of messages, both to do with storing channel status. 1/ There is a message (possibly two) for each instance of channel that has run and transferred a persistent message to a remote partner. These messages maintain the synchronisation state between the two ends of the channels. If you delete these messages your channel will forget where it got to. This will almost certainly lead to sequence number problems since the channel will start at 1 again and you will have to issue RESET CHANNEL. In the worst case, if the channel was indoubt, you may may also cause messages to be duplicated. 2/ There may also be a message recording the status of the channel. In other words, whether the channel is STOPPED, RETRYING etc etc. If you delete these messages the worsed that will happen is that when you recycle your Queue Manager a channel will come up inactive rather than STOPPED or RETRYING. Now there were a few problems with the initial implementation of the type 2 messages. You could find that even a channel retrying would add a few more of these messages. I would ensure that you are on the latest service level for whatever release you are running. In the general case though don't be fooled into thinking that you've got a problem with the queue just because you have more messages on there that you have channels. Since you have a Type 1 message for each *partner* you must consider how many locations you are talking to. So a single RCVR channel which receives connections from 100 other Queue Managers will, quite rightly, be responsible for 100 messages on this queue. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN 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: SYSTEM.CHANNEL.SYNCQ
Sorry, no. Perhaps Morag H. would care to comment. -- Rebecca -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Tuesday, October 29, 2002 4:30 PM To: [EMAIL PROTECTED] Subject: Re: SYSTEM.CHANNEL.SYNCQ Thanks Rebecca, I'll go through your suggested path and delete the messages that belong to non-existing channels. But, while I am not adding any new channel, I see this queue is growing. Any idea why? "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 02:32:24 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Ok, here's an idea. You need to keep these messages if they pertain to an existing channel. And you can get a list of channels easily enough using CSQUTIL. So -- write something that does the following: 1) Print the SYNCQ messages using the sample browse program (the Cobol program with the impossible to remember name CSQ4). Put the output into a dataset (generally, the DDname is SYSOUT, but it will depend upon your Cobol customization parms; for example, we write to SYSOUX here). Note: I'd suggest modifying the program slightly to print out the msgid, too; you can use this below to delete the messages. This is file A 2) Run CSQUTIL to get a list of the current channels, again writing the output to a dataset. This is file B 3) Now write a quick&dirty to pick up the columns from file A where the channel names resides and the columns from file B where the channel names reside. Now do a match/merge and write out the channel names in file A that don't reside in file B. Sounds like the perfect opportunity for a simple SAS program to me. Depending on the version of SAS you are using, you can use it to delete the unnecessary messages (V6 included a SAS/MQ interface as part of the base product; it wasn't pretty, but it did work). Or delete them manually once you have the list of which channels you don't need. For testing -- Dump the queue to a flat file and reload it to a new queue where it won't matter if you wipe the wrong messages! -- Rebecca -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ***
Re: SYSTEM.CHANNEL.SYNCQ
Thanks Rebecca, I'll go through your suggested path and delete the messages that belong to non-existing channels. But, while I am not adding any new channel, I see this queue is growing. Any idea why? "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 02:32:24 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Ok, here's an idea. You need to keep these messages if they pertain to an existing channel. And you can get a list of channels easily enough using CSQUTIL. So -- write something that does the following: 1) Print the SYNCQ messages using the sample browse program (the Cobol program with the impossible to remember name CSQ4). Put the output into a dataset (generally, the DDname is SYSOUT, but it will depend upon your Cobol customization parms; for example, we write to SYSOUX here). Note: I'd suggest modifying the program slightly to print out the msgid, too; you can use this below to delete the messages. This is file A 2) Run CSQUTIL to get a list of the current channels, again writing the output to a dataset. This is file B 3) Now write a quick&dirty to pick up the columns from file A where the channel names resides and the columns from file B where the channel names reside. Now do a match/merge and write out the channel names in file A that don't reside in file B. Sounds like the perfect opportunity for a simple SAS program to me. Depending on the version of SAS you are using, you can use it to delete the unnecessary messages (V6 included a SAS/MQ interface as part of the base product; it wasn't pretty, but it did work). Or delete them manually once you have the list of which channels you don't need. For testing -- Dump the queue to a flat file and reload it to a new queue where it won't matter if you wipe the wrong messages! -- Rebecca -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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
Re: SYSTEM.CHANNEL.SYNCQ
Ok, here's an idea. You need to keep these messages if they pertain to an existing channel. And you can get a list of channels easily enough using CSQUTIL. So -- write something that does the following: 1) Print the SYNCQ messages using the sample browse program (the Cobol program with the impossible to remember name CSQ4). Put the output into a dataset (generally, the DDname is SYSOUT, but it will depend upon your Cobol customization parms; for example, we write to SYSOUX here). Note: I'd suggest modifying the program slightly to print out the msgid, too; you can use this below to delete the messages. This is file A 2) Run CSQUTIL to get a list of the current channels, again writing the output to a dataset. This is file B 3) Now write a quick&dirty to pick up the columns from file A where the channel names resides and the columns from file B where the channel names reside. Now do a match/merge and write out the channel names in file A that don't reside in file B. Sounds like the perfect opportunity for a simple SAS program to me. Depending on the version of SAS you are using, you can use it to delete the unnecessary messages (V6 included a SAS/MQ interface as part of the base product; it wasn't pretty, but it did work). Or delete them manually once you have the list of which channels you don't need. For testing -- Dump the queue to a flat file and reload it to a new queue where it won't matter if you wipe the wrong messages! -- Rebecca -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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: SYSTEM.CHANNEL.SYNCQ
Thanks Frank, We have used that program to purge the duplicate messages. It cannot be used to purge the unwanted messages. "Bright, Frank" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 01:37:30 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ There is one other option. You can request from IBM a program, CSQ4SYNC, that examines the Channel SYNCQ and either reports on or removes the duplicates. -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 4:28 PM To: [EMAIL PROTECTED] Subject: Re: SYSTEM.CHANNEL.SYNCQ Thanks Rebecca for sharing your experience. The problem I see here in purging all the messages in this queue is having to reset the sequence numbers in our side and in all other Q managers we talk to. This last piece, resetting other Q managers, which takes a lot of coordination and causes outage, is something that we cannot afford. This is the reason why I am trying to find which messages should be kept and which ones can be purged. "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 12:45:09 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Bahman, I haven't done this since we moved off V1.2 (actually, not all that long ago), so this information is current as of that level. But I don't think this info has changed... You can safely delete any message from the SYNCQ, BUT... If you do, you will need to do a message number Reset for any existing channels whose information you delete. This queue is where that kind of information is stored. I once deleted every message from this queue when we had a pretty off the wall problem with the queue caused by a power failure combined with a UPS failure, and we survived (although all those resets were a pain). I'd suggest (strongly) you do this at a time when your CHIN is down; actually, I'm not sure you can do it otherwise. What I would do is shutdown the CHIN, dump the queue to a flat file using CSQUTIL, then delete what you want, then restart the CHIN and see what happens. If you find it's royally messed up, you should be able to reload the old SYNCQ from your backup. Good luck ... Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and
Re: SYSTEM.CHANNEL.SYNCQ
There is one other option. You can request from IBM a program, CSQ4SYNC, that examines the Channel SYNCQ and either reports on or removes the duplicates. -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 4:28 PM To: [EMAIL PROTECTED] Subject: Re: SYSTEM.CHANNEL.SYNCQ Thanks Rebecca for sharing your experience. The problem I see here in purging all the messages in this queue is having to reset the sequence numbers in our side and in all other Q managers we talk to. This last piece, resetting other Q managers, which takes a lot of coordination and causes outage, is something that we cannot afford. This is the reason why I am trying to find which messages should be kept and which ones can be purged. "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 12:45:09 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Bahman, I haven't done this since we moved off V1.2 (actually, not all that long ago), so this information is current as of that level. But I don't think this info has changed... You can safely delete any message from the SYNCQ, BUT... If you do, you will need to do a message number Reset for any existing channels whose information you delete. This queue is where that kind of information is stored. I once deleted every message from this queue when we had a pretty off the wall problem with the queue caused by a power failure combined with a UPS failure, and we survived (although all those resets were a pain). I'd suggest (strongly) you do this at a time when your CHIN is down; actually, I'm not sure you can do it otherwise. What I would do is shutdown the CHIN, dump the queue to a flat file using CSQUTIL, then delete what you want, then restart the CHIN and see what happens. If you find it's royally messed up, you should be able to reload the old SYNCQ from your backup. Good luck ... Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 Inst
Re: SYSTEM.CHANNEL.SYNCQ
Thanks Rebecca for sharing your experience. The problem I see here in purging all the messages in this queue is having to reset the sequence numbers in our side and in all other Q managers we talk to. This last piece, resetting other Q managers, which takes a lot of coordination and causes outage, is something that we cannot afford. This is the reason why I am trying to find which messages should be kept and which ones can be purged. "Bullock, Rebecca (CSC)" <[EMAIL PROTECTED]>@AKH-Wien.AC.AT> on 10/28/2002 12:45:09 PM Please respond to MQSeries List <[EMAIL PROTECTED]> Sent by:MQSeries List <[EMAIL PROTECTED]> To:[EMAIL PROTECTED] cc: Subject:Re: SYSTEM.CHANNEL.SYNCQ Bahman, I haven't done this since we moved off V1.2 (actually, not all that long ago), so this information is current as of that level. But I don't think this info has changed... You can safely delete any message from the SYNCQ, BUT... If you do, you will need to do a message number Reset for any existing channels whose information you delete. This queue is where that kind of information is stored. I once deleted every message from this queue when we had a pretty off the wall problem with the queue caused by a power failure combined with a UPS failure, and we survived (although all those resets were a pain). I'd suggest (strongly) you do this at a time when your CHIN is down; actually, I'm not sure you can do it otherwise. What I would do is shutdown the CHIN, dump the queue to a flat file using CSQUTIL, then delete what you want, then restart the CHIN and see what happens. If you find it's royally messed up, you should be able to reload the old SYNCQ from your backup. Good luck ... Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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 ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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
Re: SYSTEM.CHANNEL.SYNCQ
Bahman, I haven't done this since we moved off V1.2 (actually, not all that long ago), so this information is current as of that level. But I don't think this info has changed... You can safely delete any message from the SYNCQ, BUT... If you do, you will need to do a message number Reset for any existing channels whose information you delete. This queue is where that kind of information is stored. I once deleted every message from this queue when we had a pretty off the wall problem with the queue caused by a power failure combined with a UPS failure, and we survived (although all those resets were a pain). I'd suggest (strongly) you do this at a time when your CHIN is down; actually, I'm not sure you can do it otherwise. What I would do is shutdown the CHIN, dump the queue to a flat file using CSQUTIL, then delete what you want, then restart the CHIN and see what happens. If you find it's royally messed up, you should be able to reload the old SYNCQ from your backup. Good luck ... Rebecca Rebecca Bullock Computer Sciences Corporation Educational Testing Service Account Princeton, NJ 08541 e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] -Original Message- From: Bahman Nejad [mailto:Bahman.Nejad@;UBOC.COM] Sent: Monday, October 28, 2002 11:16 AM To: [EMAIL PROTECTED] Subject: SYSTEM.CHANNEL.SYNCQ The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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 ** This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. 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
SYSTEM.CHANNEL.SYNCQ
The number of messages in our SYSTEM.CHANNEL.SYNCQ is growing and I need to purge its un-needed messages before it causes any problem for us. I have been unable to find a way to determine which messages are needed which messages are not. Does anyone out there have any experience with this issue? We are running MQ for OS/390 V2.1. Thanks ** This communication (including any attachments) may contain privileged or confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this communication and/or shred the materials and any attachments and are hereby notified that any disclosure, copying, or distribution of this communication, or the taking of any action based on it, is strictly prohibited. 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
