Re: amqiclen question
Peter,
If the server crashes, it doesn't matter. If MQ crashes, then I suppose it
could prove useful to run amqiclen or mqipcrm it at the head of the startup
script. Unless there's some exposure/problem with residual shared memory
segments and semaphores, running the cleanup before starting MQ might be
better. But, if your script doesn't detect and abort the startup, raise an
alert, if either amqiclen or mqipcrm returns a bad return code, you could
see your queue manager fail. I guess the question is when you want to
notified of a problem with amqiclen/mqipcrm.
"Potkay, Peter M
(PLC, IT)" To: [EMAIL PROTECTED]
<[EMAIL PROTECTED] cc:
RTFORD.COM> Subject: Re: amqiclen question
Sent by: MQSeries
List
<[EMAIL PROTECTED]
AC.AT>
04/21/2004 09:50 AM
Please respond to
MQSeries List
Where do you guys put amqiclen or mqipcrm.sh?
I was thinking of putting it at the head of my startup scripts as well as
the end of the shutdown scripts. If the server / QM crashes and the
shutdown
script never runs, there is a chance that there will be leftover shared
memory and segments that may interfere with the QM coming back up. Or is
this overkill?
-Original Message-
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: amqiclen question
Bill,
It's been around for awhile, but never seemed to made to the admin manual:
Here is item RTA000170159 concerning your inquiry:
Source..: PDDBR PDDBR
Last updated....: 20010724
Abstract: AMQICLEN HANG HUNG CLEANUP SHMEM SEMAPHORES CHKMQIPC
USERS: ALL USERS with MQSeries HPUX HP
PROBLEM SUMMARY:
Cust wants to discuss methods for cleaning up shared memory
and semaphores particularly in their shutdown scripts where they
have to bring down a queue manager manually by killing off processes.
In
5.1 they have been using a script developed by Hursley called
chkmqipc because they could use it to clean up ipc resources from one
queue manager on a machine where another queue manager was still
running (without having to end that other queue manager). In 5.2 we
had suggested they used the utility supplied with the product called
amqiclen. Cust is having problems trying to use it.
SOLUTION:
If there is no documentation, then the utility is probably in the
'unsupported' category, i.e. it is intended for use by MQ support and
has been issued so it is already installed should support require it
for any purpose. It is not really intended for customer use. There
are other 5.2 utilities like this, for authorizations, cluster and
channel debugging.
It is not necessary to clear IPC resources if MQ is ended normally,
nor at 5.2 should it be necessary if MQ is ended abnormally or
abruptly. CHKMQIPC should indeed continue to work at 5.2. However
either 5.2 or PB may be cleaning up IPC stuff so chkmqipc has no work
to do.
The command line for amqiclen is:
amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini
.
-v => verbose
-c => check only (does not ipcrm anything)
-m => only to clean up named queue manager
.
returns:
0 => OK
2 => One or more connected process(es)
>2 => unexpected error
Note: if the input redirection is omitted, the
< /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input.
Once cust used the correct syntax for the amqiclen command it did
work as desired.
Bill Anderson
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
ITA.AERO>cc:
Sent by: Subject: Re: amqiclen
question
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
04/15/2004 09:16
AM
Please respond
to MQSeries List
We are an AIX shop, but I use mqipcrm, which is a fairly simple "K shell"
script. I run it every time I bring a qmgr down with out bouncing the
machine. I believe It was written by an IBM support person, and the are the
ones that gave it to me a year ago or so. It takes no flags at all, and
seems to work fine.
I have never heard of amqiclen, perhaps I should consider taking a look at
it?
Cheers
Rick Tsujimoto
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
.CANON.CO
Re: amqiclen question
Where do you guys put amqiclen or mqipcrm.sh?
I was thinking of putting it at the head of my startup scripts as well as
the end of the shutdown scripts. If the server / QM crashes and the shutdown
script never runs, there is a chance that there will be leftover shared
memory and segments that may interfere with the QM coming back up. Or is
this overkill?
-Original Message-
From: Rick Tsujimoto [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 15, 2004 10:53 AM
To: [EMAIL PROTECTED]
Subject: Re: amqiclen question
Bill,
It's been around for awhile, but never seemed to made to the admin manual:
Here is item RTA000170159 concerning your inquiry:
Source..: PDDBR PDDBR
Last updated: 20010724
Abstract....: AMQICLEN HANG HUNG CLEANUP SHMEM SEMAPHORES CHKMQIPC
USERS: ALL USERS with MQSeries HPUX HP
PROBLEM SUMMARY:
Cust wants to discuss methods for cleaning up shared memory
and semaphores particularly in their shutdown scripts where they
have to bring down a queue manager manually by killing off processes.
In
5.1 they have been using a script developed by Hursley called
chkmqipc because they could use it to clean up ipc resources from one
queue manager on a machine where another queue manager was still
running (without having to end that other queue manager). In 5.2 we
had suggested they used the utility supplied with the product called
amqiclen. Cust is having problems trying to use it.
SOLUTION:
If there is no documentation, then the utility is probably in the
'unsupported' category, i.e. it is intended for use by MQ support and
has been issued so it is already installed should support require it
for any purpose. It is not really intended for customer use. There
are other 5.2 utilities like this, for authorizations, cluster and
channel debugging.
It is not necessary to clear IPC resources if MQ is ended normally,
nor at 5.2 should it be necessary if MQ is ended abnormally or
abruptly. CHKMQIPC should indeed continue to work at 5.2. However
either 5.2 or PB may be cleaning up IPC stuff so chkmqipc has no work
to do.
The command line for amqiclen is:
amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini
.
-v => verbose
-c => check only (does not ipcrm anything)
-m => only to clean up named queue manager
.
returns:
0 => OK
2 => One or more connected process(es)
>2 => unexpected error
Note: if the input redirection is omitted, the
< /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input.
Once cust used the correct syntax for the amqiclen command it did
work as desired.
Bill Anderson
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
ITA.AERO>cc:
Sent by: Subject: Re: amqiclen
question
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
04/15/2004 09:16
AM
Please respond
to MQSeries List
We are an AIX shop, but I use mqipcrm, which is a fairly simple "K shell"
script. I run it every time I bring a qmgr down with out bouncing the
machine. I believe It was written by an IBM support person, and the are the
ones that gave it to me a year ago or so. It takes no flags at all, and
seems to work fine.
I have never heard of amqiclen, perhaps I should consider taking a look at
it?
Cheers
Rick Tsujimoto
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
.CANON.COM> cc:
Sent by: MQSeries List Subject: amqiclen
question
<[EMAIL PROTECTED]>
04/14/2004 02:59 PM
Please respond to MQSeries
List
I've used amqiclen for HP-UX, but on AIX there seems to be a different set
of switches. What switches should be set to routinely get rid of any
shared memory segments and semaphores when MQ is brought down?
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
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 attachments, is for the exc
Re: amqiclen
amqiclen [-v] -x|-c -m . I am not sure if it is safe on Prod. boxes, but what I have seen is, it doesn't clean the stuff all the time. It cleans most of the times and does nothing sometimes. I use Justin Fries' script to clear up all the S's and M's. And there are others like MQKill and MQClean, that would do the needful. -Sudheer. -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of W Samuel Sent: Monday, April 19, 2004 12:44 PM To: [EMAIL PROTECTED] Subject: amqiclen Hello, Is amqiclen a safe command to use on Production or is this still an unsupported feature ? What are the parameters for this ? Thanks, WS Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html 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
amqiclen
Hello, Is amqiclen a safe command to use on Production or is this still an unsupported feature ? What are the parameters for this ? Thanks, WS Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html 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: amqiclen question
Bill,
It's been around for awhile, but never seemed to made to the admin manual:
Here is item RTA000170159 concerning your inquiry:
Source..: PDDBR PDDBR
Last updated: 20010724
Abstract....: AMQICLEN HANG HUNG CLEANUP SHMEM SEMAPHORES CHKMQIPC
USERS: ALL USERS with MQSeries HPUX HP
PROBLEM SUMMARY:
Cust wants to discuss methods for cleaning up shared memory
and semaphores particularly in their shutdown scripts where they
have to bring down a queue manager manually by killing off processes.
In
5.1 they have been using a script developed by Hursley called
chkmqipc because they could use it to clean up ipc resources from one
queue manager on a machine where another queue manager was still
running (without having to end that other queue manager). In 5.2 we
had suggested they used the utility supplied with the product called
amqiclen. Cust is having problems trying to use it.
SOLUTION:
If there is no documentation, then the utility is probably in the
'unsupported' category, i.e. it is intended for use by MQ support and
has been issued so it is already installed should support require it
for any purpose. It is not really intended for customer use. There
are other 5.2 utilities like this, for authorizations, cluster and
channel debugging.
It is not necessary to clear IPC resources if MQ is ended normally,
nor at 5.2 should it be necessary if MQ is ended abnormally or
abruptly. CHKMQIPC should indeed continue to work at 5.2. However
either 5.2 or PB may be cleaning up IPC stuff so chkmqipc has no work
to do.
The command line for amqiclen is:
amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini
.
-v => verbose
-c => check only (does not ipcrm anything)
-m => only to clean up named queue manager
.
returns:
0 => OK
2 => One or more connected process(es)
>2 => unexpected error
Note: if the input redirection is omitted, the
< /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input.
Once cust used the correct syntax for the amqiclen command it did
work as desired.
Bill Anderson
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
ITA.AERO>cc:
Sent by: Subject: Re: amqiclen question
MQSeries List
<[EMAIL PROTECTED]
en.AC.AT>
04/15/2004 09:16
AM
Please respond
to MQSeries List
We are an AIX shop, but I use mqipcrm, which is a fairly simple "K shell"
script. I run it every time I bring a qmgr down with out bouncing the
machine. I believe It was written by an IBM support person, and the are the
ones that gave it to me a year ago or so. It takes no flags at all, and
seems to work fine.
I have never heard of amqiclen, perhaps I should consider taking a look at
it?
Cheers
Rick Tsujimoto
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
.CANON.COM> cc:
Sent by: MQSeries List Subject: amqiclen
question
<[EMAIL PROTECTED]>
04/14/2004 02:59 PM
Please respond to MQSeries
List
I've used amqiclen for HP-UX, but on AIX there seems to be a different set
of switches. What switches should be set to routinely get rid of any
shared memory segments and semaphores when MQ is brought down?
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
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: amqiclen question
We are an AIX shop, but I use mqipcrm, which is a fairly simple "K shell" script. I run it every time I bring a qmgr down with out bouncing the machine. I believe It was written by an IBM support person, and the are the ones that gave it to me a year ago or so. It takes no flags at all, and seems to work fine. I have never heard of amqiclen, perhaps I should consider taking a look at it? Cheers Rick Tsujimoto <[EMAIL PROTECTED]To: [EMAIL PROTECTED] .CANON.COM>cc: Sent by: MQSeries List Subject: amqiclen question <[EMAIL PROTECTED]> 04/14/2004 02:59 PM Please respond to MQSeries List I've used amqiclen for HP-UX, but on AIX there seems to be a different set of switches. What switches should be set to routinely get rid of any shared memory segments and semaphores when MQ is brought down? 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
amqiclen question
I've used amqiclen for HP-UX, but on AIX there seems to be a different set of switches. What switches should be set to routinely get rid of any shared memory segments and semaphores when MQ is brought down? 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
amqiclen question - never mind
Just realized I was looking at a V5.2 version, when I needed V5.3. 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: amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING)
Found this on the IBM Link site: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>> The command line for amqiclen is: amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini . -v => verbose -c => check only (does not ipcrm anything) -m => only to clean up named queue manager . returns: 0 => OK 2 => One or more connected process(es) >2 => unexpected error Note: if the input redirection is omitted, the < /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input. If there is no documentation, then the utility is probably in the 'unsupported' category, i.e. it is intended for use by MQ support and has been issued so it is already installed should support require it for any purpose. It is not really intended for customer use. There are other 5.2 utilities like this, for authorizations, cluster and channel debugging. >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>> Looks like CSD07 for 5.3 will have some more switches added to this command. -Original Message- From: Potkay, Peter M (PLC, IT) Sent: Tuesday, January 20, 2004 3:56 PM To: 'MQSeries List' Subject: RE: amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING) There is a -m switch allowing you to specify the QM. IBM sent me this: amqiclen -v -c -m mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 3:50 PM To: [EMAIL PROTECTED] Subject: amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING) Does the amqiclen just cleanup unused semaphores and shared memory? Can I use it if I shutdown one queue manager, but there is another running? -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING On a Unix system, when a queue manager starts it acquires shared memory and semaphore resources. It uses these during normal operation. If you then end the queue manager with "endmqm QMGRNAME" then all of these resources will get cleaned up and there will be no MQ artifacts left in memory (semaphores and shared memory segments). On the other hand if you issue endmqm with the -i parameter (as I did during our test) or the -p parameter then these shared memory and semaphore resources will NOT get cleaned up. That means that the queue manager will end but the resources it used in memory will not get cleaned up. This will happen whether my MDBs are connected or not, which is why it doesn't have anything to do really with MDBs specifically. The problem with this is that when you restart the queue manager it will attempt to acquire new shared memory and semaphore resources, as it normally does. However, if OLD resources are still resident in memory (because they weren't cleaned up during the last MQ shutdown) then it is possible that the current instance of the queue manager (that is starting) might interpret these resources as belonging to processes that are still running. This is why we got the error messages we saw. In most cases the queue manager will start OK even if it finds old resources in memory, but it can encounter the error we saw. The -i switch on the endmqm command means shut down immediately. Do not wait for connected programs to end when they want to (like MDBs). Without that -i switch, we run the risk of our QM shutdown waiting forever for the MDBs to end. This is why I always use the -i switch when ending a QM. At 5.3, there is the undocumented amqiclen command that cleans up these resources. We are testing this command at the end of our shutdown scripts and at the beginning of our startup scripts. It cleans up old memory resources if they are present after a QM has come down, eliminating the problem we saw on subsequent startups. Back to MDBs: I still think we will research the polling interval setting to help MDBs ralize that the QM is gone, as that can only help prevent problems. -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 1:22 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING I don't know. I am asking the customer to help me test this. (or maybe someone out there knows) Hopefully it will not write to the log every time it simply checks to see if the connectio
Re: amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING)
There is a -m switch allowing you to specify the QM. IBM sent me this: amqiclen -v -c -m mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 3:50 PM To: [EMAIL PROTECTED] Subject: amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING) Does the amqiclen just cleanup unused semaphores and shared memory? Can I use it if I shutdown one queue manager, but there is another running? -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING On a Unix system, when a queue manager starts it acquires shared memory and semaphore resources. It uses these during normal operation. If you then end the queue manager with "endmqm QMGRNAME" then all of these resources will get cleaned up and there will be no MQ artifacts left in memory (semaphores and shared memory segments). On the other hand if you issue endmqm with the -i parameter (as I did during our test) or the -p parameter then these shared memory and semaphore resources will NOT get cleaned up. That means that the queue manager will end but the resources it used in memory will not get cleaned up. This will happen whether my MDBs are connected or not, which is why it doesn't have anything to do really with MDBs specifically. The problem with this is that when you restart the queue manager it will attempt to acquire new shared memory and semaphore resources, as it normally does. However, if OLD resources are still resident in memory (because they weren't cleaned up during the last MQ shutdown) then it is possible that the current instance of the queue manager (that is starting) might interpret these resources as belonging to processes that are still running. This is why we got the error messages we saw. In most cases the queue manager will start OK even if it finds old resources in memory, but it can encounter the error we saw. The -i switch on the endmqm command means shut down immediately. Do not wait for connected programs to end when they want to (like MDBs). Without that -i switch, we run the risk of our QM shutdown waiting forever for the MDBs to end. This is why I always use the -i switch when ending a QM. At 5.3, there is the undocumented amqiclen command that cleans up these resources. We are testing this command at the end of our shutdown scripts and at the beginning of our startup scripts. It cleans up old memory resources if they are present after a QM has come down, eliminating the problem we saw on subsequent startups. Back to MDBs: I still think we will research the polling interval setting to help MDBs ralize that the QM is gone, as that can only help prevent problems. -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 1:22 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING I don't know. I am asking the customer to help me test this. (or maybe someone out there knows) Hopefully it will not write to the log every time it simply checks to see if the connection is still valid (meaning the QM is up). -Original Message- From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 1:15 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING Peter, Do unsatisfied GETs really get logged? I thought the log was driven only by message movement and rcdmqimg. -- T.Rob -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 12:03 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING WL MDBs are pure JMS implementations of MDBs, and do not have IBM specific capabilities, like WAS MDBs do. If a JMS object has an IBM specific property (like FAIL_IF_QUIESCING), it will just be ignored by the WL MDB. A WL MDB can check to see if its cached connection to the QM is still valid every X seconds, and if it is not, it can end, throwing an exception to be handling by the container. The restart of that MDB can then be handled in whatever manner is suitable. Meanwhile the QM should be able to end cleanly with no MDB connections that would prevent a clean start up. If I understand it correctly, jms-polling-interval-seconds is what we need to set. This is an optional element that can be declared in the weblogic-ejb-jar.xml deployment descriptor. Typically this is not set, so my thought is that if we actually do set it, it will reach out to the QM every interval and if the Connection is lost, kill the connection and kill the MDB. The issue, if this does work as I am hoping, and kills the connection, is that the Container will then continually poll the QM every interval consuming resources and writing the log. If this occurs over an extended period of time, the log file has the potential to grow to rather large proportions.
amqiclen (was RE: Message Driven Beans and FAIL_IF_QUIESCING)
Does the amqiclen just cleanup unused semaphores and shared memory? Can I use it if I shutdown one queue manager, but there is another running? -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 2:38 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING On a Unix system, when a queue manager starts it acquires shared memory and semaphore resources. It uses these during normal operation. If you then end the queue manager with "endmqm QMGRNAME" then all of these resources will get cleaned up and there will be no MQ artifacts left in memory (semaphores and shared memory segments). On the other hand if you issue endmqm with the -i parameter (as I did during our test) or the -p parameter then these shared memory and semaphore resources will NOT get cleaned up. That means that the queue manager will end but the resources it used in memory will not get cleaned up. This will happen whether my MDBs are connected or not, which is why it doesn't have anything to do really with MDBs specifically. The problem with this is that when you restart the queue manager it will attempt to acquire new shared memory and semaphore resources, as it normally does. However, if OLD resources are still resident in memory (because they weren't cleaned up during the last MQ shutdown) then it is possible that the current instance of the queue manager (that is starting) might interpret these resources as belonging to processes that are still running. This is why we got the error messages we saw. In most cases the queue manager will start OK even if it finds old resources in memory, but it can encounter the error we saw. The -i switch on the endmqm command means shut down immediately. Do not wait for connected programs to end when they want to (like MDBs). Without that -i switch, we run the risk of our QM shutdown waiting forever for the MDBs to end. This is why I always use the -i switch when ending a QM. At 5.3, there is the undocumented amqiclen command that cleans up these resources. We are testing this command at the end of our shutdown scripts and at the beginning of our startup scripts. It cleans up old memory resources if they are present after a QM has come down, eliminating the problem we saw on subsequent startups. Back to MDBs: I still think we will research the polling interval setting to help MDBs ralize that the QM is gone, as that can only help prevent problems. -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 1:22 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING I don't know. I am asking the customer to help me test this. (or maybe someone out there knows) Hopefully it will not write to the log every time it simply checks to see if the connection is still valid (meaning the QM is up). -Original Message- From: Wyatt, T. Rob [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 1:15 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING Peter, Do unsatisfied GETs really get logged? I thought the log was driven only by message movement and rcdmqimg. -- T.Rob -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 07, 2004 12:03 PM To: [EMAIL PROTECTED] Subject: Re: Message Driven Beans and FAIL_IF_QUIESCING WL MDBs are pure JMS implementations of MDBs, and do not have IBM specific capabilities, like WAS MDBs do. If a JMS object has an IBM specific property (like FAIL_IF_QUIESCING), it will just be ignored by the WL MDB. A WL MDB can check to see if its cached connection to the QM is still valid every X seconds, and if it is not, it can end, throwing an exception to be handling by the container. The restart of that MDB can then be handled in whatever manner is suitable. Meanwhile the QM should be able to end cleanly with no MDB connections that would prevent a clean start up. If I understand it correctly, jms-polling-interval-seconds is what we need to set. This is an optional element that can be declared in the weblogic-ejb-jar.xml deployment descriptor. Typically this is not set, so my thought is that if we actually do set it, it will reach out to the QM every interval and if the Connection is lost, kill the connection and kill the MDB. The issue, if this does work as I am hoping, and kills the connection, is that the Container will then continually poll the QM every interval consuming resources and writing the log. If this occurs over an extended period of time, the log file has the potential to grow to rather large proportions. Not being a JMS expert, I am not 100% sure of this solution, and would like to see it tested, but it seems to make sense, no? -Original Message- From: Christopher Frank [mailto:[EMAIL PROTECTED] Sent: Monday, January 05, 2004 2:44 PM To: [EMA
Re: amqiclen
The command line for amqiclen is: amqiclen .-v. .-c. .-m qmgr_name. < /var/mqm/mqs.ini . -v => verbose -c => check only (does not ipcrm anything) -m => only to clean up named queue manager . returns: 0 => OK 2 => One or more connected process(es) >2 => unexpected error Note: if the input redirection is omitted, the < /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input. -Original Message- From: Kearns, Emile E [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2003 8:48 AM To: [EMAIL PROTECTED] Subject: amqiclen Importance: High Hi all, Is this the correct usage of amqiclen? MQSERIES 5.2 on solaris 7 amqiclen -v -c -m QMNAME For some reason , when I issue this command, it just hangs. Any ideas? For information about he Standard Bank group visit our web site www.standardbank.co.za Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of the Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group.The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. I 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
amqiclen
Hi all, Is this the correct usage of amqiclen? MQSERIES 5.2 on solaris 7 amqiclen -v -c -m QMNAME For some reason , when I issue this command, it just hangs. Any ideas? For information about he Standard Bank group visit our web site www.standardbank.co.za Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of the Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group.The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. I 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: amqiclen question
I got a copy of a script that Justin Fries wrote from the Support Center which does what I want. Thanks to all that replied. "KANE, TOM M (SBCSI)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc: Sent by: Subject: Re: amqiclen question MQSeries List <[EMAIL PROTECTED] en.AC.AT> 02/26/2003 04:39 PM Please respond to MQSeries List Were you able to clean those semaphores manually using ipcrm? I frequently have semaphores that I can't get rid of. Not that we have to do this often, and we have our own version of something I think was on the list once that basically does the ipcs and pipes to grep and awk to build ipcrm commands. Tom -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:19 PM To: [EMAIL PROTECTED] Subject: amqiclen question I tried running amqiclen and it didn't remove any memory and/or semaphore segments on AIX. The format of the command I used was: amqiclen -v -m MyQmgr < /var/mqm/mqs.ini It returned with rc=0. I did a ipcs -a|grep mqm before and after issuing amqiclen and 3 semaphore segments were there before and after. Any ideas? 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 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: amqiclen question
Try this script. But I agree with Tom. There is usually at least one memory piece that does not go away. Actually I ran my MQKill command (removes a QMGR manually) and the my MQClean script (cleans s& M's). I was very surprised that there was NO S or M left around owned by 'mqm'! Go figure? bobbee From: "KANE, TOM M (SBCSI)" <[EMAIL PROTECTED]> Reply-To: MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: amqiclen question Date: Wed, 26 Feb 2003 16:39:26 -0500 Were you able to clean those semaphores manually using ipcrm? I frequently have semaphores that I can't get rid of. Not that we have to do this often, and we have our own version of something I think was on the list once that basically does the ipcs and pipes to grep and awk to build ipcrm commands. Tom -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:19 PM To: [EMAIL PROTECTED] Subject: amqiclen question I tried running amqiclen and it didn't remove any memory and/or semaphore segments on AIX. The format of the command I used was: amqiclen -v -m MyQmgr < /var/mqm/mqs.ini It returned with rc=0. I did a ipcs -a|grep mqm before and after issuing amqiclen and 3 semaphore segments were there before and after. Any ideas? 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 _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus MQClean Description: Binary data
Re: amqiclen question
Were you able to clean those semaphores manually using ipcrm? I frequently have semaphores that I can't get rid of. Not that we have to do this often, and we have our own version of something I think was on the list once that basically does the ipcs and pipes to grep and awk to build ipcrm commands. Tom -Original Message- From: Rick Tsujimoto [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 26, 2003 2:19 PM To: [EMAIL PROTECTED] Subject: amqiclen question I tried running amqiclen and it didn't remove any memory and/or semaphore segments on AIX. The format of the command I used was: amqiclen -v -m MyQmgr < /var/mqm/mqs.ini It returned with rc=0. I did a ipcs -a|grep mqm before and after issuing amqiclen and 3 semaphore segments were there before and after. Any ideas? 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
amqiclen question
I tried running amqiclen and it didn't remove any memory and/or semaphore segments on AIX. The format of the command I used was: amqiclen -v -m MyQmgr < /var/mqm/mqs.ini It returned with rc=0. I did a ipcs -a|grep mqm before and after issuing amqiclen and 3 semaphore segments were there before and after. Any ideas? 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: amqiclen
amqiclen is the IPCS clean up. If you have this problem, it is usually caused by applications refusing to let go of the queue manager and that don't recognize when a queue manager is stopped. It can just happen too, but if you close the applications first before stopping the queue manager, you will probably see better results. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com "Chan, Ian M" <[EMAIL PROTECTED]> wrote: Date Recieved: 11/25/2002 10:45:45 PM To: [EMAIL PROTECTED] cc: Bcc Subject: Re: amqiclen We have a similar arrangement except we stop at -i step. Actually in the case happened this time, all the processes are ended and the shutdown took 1min 6 sec to complete. The queue manager was then brought up 15 minutes later by the script but failed with amq6004. When I got paged, I grep the mq process but there was none. Then I strmqm but failed with same error again so I just did the amqiclen without doing any ipcs command. I think I have to check the details of CSD5. Thanks for reminding me. Cheers, Ian -Original Message- From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 3:38 PM To: [EMAIL PROTECTED] Subject: Re: amqiclen The first thing that comes to mind is your queue manager is not completely shutdown and then you try to start a half shut down queue manager. This can happen if your script is not smart enough to deal with a slow or failed shutdown. Misbehaving apps or apps not designed to properly recognize the queue manager is shutting down and aggravate this situation. If you are just issuing "endmqm QmgrName" than you are quiescing it. This can take from 1 minute to 100 years or so to shut down the queue manager. It depends on how good the apps are, but I usually use endmqm -i to make sure it shuts down. Even then, you can have problems. A good process for a shutdown and restart includes these steps: 1. Shut down the apps first if they are not designed to deal with a quiescing queue manager. Most are not 2. endmqm -i (run in background) then wait a few minutes 3. Check the queue manager processes to see if they have ended. 4. If not ended, endmqm -p (in the background) then wait a few minutes 5. Check the queue manager processes again. 6. If the queue manager still hasn't shut down start killing processes. This is detailed in the system admin manual. Read this because you should kill the processes in the correct order. 7. Clean up IPCS if needed. Only do this if all queue managers are shut down though. Carefully. If you use this as a guideline before performing your other steps and restarting, you'll probably eliminate your problem. Just an observation, you should upgrade to CSD 5 because 4 has a nasty bug that can prevent your log pointer from moving forward on linear logs. Since you mention cleaning the logs I am assuming you are using linear logs. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com "Chan, Ian M" <[EMAIL PROTECTED]> wrote: Date Recieved: 11/25/2002 05:31:29 PM To: [EMAIL PROTECTED] cc: Bcc Subject: amqiclen Hi Listers, I got the amq6004 problem in the SUN box this morning which caused the queue manager cannot be brought up. This is the second time it happened on that box this year and thanks for those who showed me the amqiclen command recently on the list. This time I don't have to issue ipcs and ipcrm commands to fix it. The amqiclen is great with just one command to do all the things and on a particular queue manager. On the other hand, I still don't have any idea why this happen. At midnight, there is a script running to do a cleanlog/shutdown/backup and then restart. Everything looks alright except when executing the strmqm. Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 with CSD4. There is no FDC or other errors at all. Cheers, Ian 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: amqiclen
We have a similar arrangement except we stop at -i step. Actually in the case happened this time, all the processes are ended and the shutdown took 1min 6 sec to complete. The queue manager was then brought up 15 minutes later by the script but failed with amq6004. When I got paged, I grep the mq process but there was none. Then I strmqm but failed with same error again so I just did the amqiclen without doing any ipcs command. I think I have to check the details of CSD5. Thanks for reminding me. Cheers, Ian -Original Message-From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]]Sent: Tuesday, 26 November 2002 3:38 PMTo: [EMAIL PROTECTED]Subject: Re: amqiclenThe first thing that comes to mind is your queue manager is not completely shutdown and then you try to start a half shut down queue manager. This can happen if your script is not smart enough to deal with a slow or failed shutdown. Misbehaving apps or apps not designed to properly recognize the queue manager is shutting down and aggravate this situation. If you are just issuing "endmqm QmgrName" than you are quiescing it. This can take from 1 minute to 100 years or so to shut down the queue manager. It depends on how good the apps are, but I usually use endmqm -i to make sure it shuts down. Even then, you can have problems. A good process for a shutdown and restart includes these steps: 1. Shut down the apps first if they are not designed to deal with a quiescing queue manager. Most are not 2. endmqm -i (run in background) then wait a few minutes 3. Check the queue manager processes to see if they have ended. 4. If not ended, endmqm -p (in the background) then wait a few minutes 5. Check the queue manager processes again. 6. If the queue manager still hasn't shut down start killing processes. This is detailed in the system admin manual. Read this because you should kill the processes in the correct order. 7. Clean up IPCS if needed. Only do this if all queue managers are shut down though. Carefully. If you use this as a guideline before performing your other steps and restarting, you'll probably eliminate your problem. Just an observation, you should upgrade to CSD 5 because 4 has a nasty bug that can prevent your log pointer from moving forward on linear logs. Since you mention cleaning the logs I am assuming you are using linear logs.Mike MurphySr. Middleware ConsultantMQ Solutions, LLChttp://www.mqsolutions.com"Chan, Ian M" <[EMAIL PROTECTED]> wrote: Date Recieved: 11/25/2002 05:31:29 PM To: [EMAIL PROTECTED] cc: Bcc Subject: amqiclenHi Listers,I got the amq6004 problem in the SUN box this morning which caused the queuemanager cannot be brought up. This is the second time it happened on thatbox this year and thanks for those who showed me the amqiclen commandrecently on the list. This time I don't have to issue ipcs and ipcrmcommands to fix it. The amqiclen is great with just one command to do allthe things and on a particular queue manager.On the other hand, I still don't have any idea why this happen. Atmidnight, there is a script running to do a cleanlog/shutdown/backup andthen restart. Everything looks alright except when executing the strmqm.Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 withCSD4. There is no FDC or other errors at all.Cheers,IanInstructions for managing your mailing list subscription are provided inthe Listserv General Users Guide available at http://www.lsoft.comArchive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: amqiclen
The first thing that comes to mind is your queue manager is not completely shutdown and then you try to start a half shut down queue manager. This can happen if your script is not smart enough to deal with a slow or failed shutdown. Misbehaving apps or apps not designed to properly recognize the queue manager is shutting down and aggravate this situation. If you are just issuing "endmqm QmgrName" than you are quiescing it. This can take from 1 minute to 100 years or so to shut down the queue manager. It depends on how good the apps are, but I usually use endmqm -i to make sure it shuts down. Even then, you can have problems. A good process for a shutdown and restart includes these steps: 1. Shut down the apps first if they are not designed to deal with a quiescing queue manager. Most are not 2. endmqm -i (run in background) then wait a few minutes 3. Check the queue manager processes to see if they have ended. 4. If not ended, endmqm -p (in the background) then wait a few minutes 5. Check the queue manager processes again. 6. If the queue manager still hasn't shut down start killing processes. This is detailed in the system admin manual. Read this because you should kill the processes in the correct order. 7. Clean up IPCS if needed. Only do this if all queue managers are shut down though. Carefully. If you use this as a guideline before performing your other steps and restarting, you'll probably eliminate your problem. Just an observation, you should upgrade to CSD 5 because 4 has a nasty bug that can prevent your log pointer from moving forward on linear logs. Since you mention cleaning the logs I am assuming you are using linear logs. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com "Chan, Ian M" <[EMAIL PROTECTED]> wrote: Date Recieved: 11/25/2002 05:31:29 PM To: [EMAIL PROTECTED] cc: Bcc Subject: amqiclen Hi Listers, I got the amq6004 problem in the SUN box this morning which caused the queue manager cannot be brought up. This is the second time it happened on that box this year and thanks for those who showed me the amqiclen command recently on the list. This time I don't have to issue ipcs and ipcrm commands to fix it. The amqiclen is great with just one command to do all the things and on a particular queue manager. On the other hand, I still don't have any idea why this happen. At midnight, there is a script running to do a cleanlog/shutdown/backup and then restart. Everything looks alright except when executing the strmqm. Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 with CSD4. There is no FDC or other errors at all. Cheers, Ian 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: amqiclen
It's a normal shutdown (i.e. the default control shutdown). Actually the shutdown worked without problem. I can see the queue manager ended messsage in the message log. Ian -Original Message- From: Malamud, Mikhail [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 1:12 PM To: 'Chan, Ian M '; '[EMAIL PROTECTED] ' Subject: RE: amqiclen What options do you use for endmqm command? -Original Message- From: Chan, Ian M To: [EMAIL PROTECTED] Sent: 11/25/2002 7:31 PM Subject: amqiclen Hi Listers, I got the amq6004 problem in the SUN box this morning which caused the queue manager cannot be brought up. This is the second time it happened on that box this year and thanks for those who showed me the amqiclen command recently on the list. This time I don't have to issue ipcs and ipcrm commands to fix it. The amqiclen is great with just one command to do all the things and on a particular queue manager. On the other hand, I still don't have any idea why this happen. At midnight, there is a script running to do a cleanlog/shutdown/backup and then restart. Everything looks alright except when executing the strmqm. Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 with CSD4. There is no FDC or other errors at all. Cheers, Ian 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: amqiclen
What options do you use for endmqm command? -Original Message- From: Chan, Ian M To: [EMAIL PROTECTED] Sent: 11/25/2002 7:31 PM Subject: amqiclen Hi Listers, I got the amq6004 problem in the SUN box this morning which caused the queue manager cannot be brought up. This is the second time it happened on that box this year and thanks for those who showed me the amqiclen command recently on the list. This time I don't have to issue ipcs and ipcrm commands to fix it. The amqiclen is great with just one command to do all the things and on a particular queue manager. On the other hand, I still don't have any idea why this happen. At midnight, there is a script running to do a cleanlog/shutdown/backup and then restart. Everything looks alright except when executing the strmqm. Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 with CSD4. There is no FDC or other errors at all. Cheers, Ian 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
amqiclen
Hi Listers, I got the amq6004 problem in the SUN box this morning which caused the queue manager cannot be brought up. This is the second time it happened on that box this year and thanks for those who showed me the amqiclen command recently on the list. This time I don't have to issue ipcs and ipcrm commands to fix it. The amqiclen is great with just one command to do all the things and on a particular queue manager. On the other hand, I still don't have any idea why this happen. At midnight, there is a script running to do a cleanlog/shutdown/backup and then restart. Everything looks alright except when executing the strmqm. Anyone got any idea what causes this? The OS is SUN 5.6 and MQ 5.2 with CSD4. There is no FDC or other errors at all. Cheers, Ian 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: amqiclen
Here is item RTA000170159 concerning your inquiry:
Source..: PDDBR PDDBR
Last updated: 20010724
Abstract: AMQICLEN HANG HUNG CLEANUP SHMEM SEMAPHORES CHKMQIPC
USERS: ALL USERS with MQSeries HPUX HP
PROBLEM SUMMARY:
Cust wants to discuss methods for cleaning up shared memory
and semaphores particularly in their shutdown scripts where they
have
to bring down a queue manager manually by killing off processes. In
5.1 they have been using a script developed by Hursley called
chkmqipc because they could use it to clean up ipc resources from
one
queue manager on a machine where another queue manager was still
running (without having to end that other queue manager). In 5.2 we
had suggested they used the utility supplied with the product
called
amqiclen. Cust is having problems trying to use it.
SOLUTION:
If there is no documentation, then the utility is probably in the
'unsupported' category, i.e. it is intended for use by MQ support
and
has been issued so it is already installed should support require
it
for any purpose. It is not really intended for customer use. There
are other 5.2 utilities like this, for authorizations, cluster and
channel debugging.
It is not necessary to clear IPC resources if MQ is ended normally,
nor at 5.2 should it be necessary if MQ is ended abnormally or
abruptly. CHKMQIPC should indeed continue to work at 5.2. However
either 5.2 or PB may be cleaning up IPC stuff so chkmqipc has no
work
to do.
The command line for amqiclen is:
amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini
.
-v => verbose
-c => check only (does not ipcrm anything)
-m => only to clean up named queue manager
.
returns:
0 => OK
2 => One or more connected process(es)
>2 => unexpected error
Note: if the input redirection is omitted, the
< /var/mqm/mqs.ini, then amqiclen will 'hang' waiting for input.
Once cust used the correct syntax for the amqiclen command it did
work as desired.
-Original Message-
From: MQSeries List [mailto:[EMAIL PROTECTED]] On Behalf Of Li,
Grant
Sent: Friday, October 04, 2002 10:47 AM
To: [EMAIL PROTECTED]
Subject: Re: amqiclen
I don't know if there is a documentation. The usage of the program was
given by IBM 2nd level support. We only run it in the case when a strmqm
fails and returns AMQ6004. We ran several times on Solaris 2.7/MQ5.2
boxes, and never had a problem.
-Original Message-
From: Robert Sloper [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 04, 2002 7:36 AM
To: [EMAIL PROTECTED]
Subject:
We are trying to use amqiclen but are finding that it just hangs when we
run it.
Is there any documentation available for this 'undocumented' program?
.. A program, amqiclen, comes with MQ can clean up the IPC
resources owned by the troubling queue manager. Here is the syntax:
/opt/mqm/bin/amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini
-v => verbose
-c => check only (does not ipcrm anything)
-m => only to clean up named queue manager
returns:
0 => OK
2 => One or more connected process(es)
>2 => unexpected error
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
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: amqiclen
I don't know if there is a documentation. The usage of the program was given by IBM 2nd level support. We only run it in the case when a strmqm fails and returns AMQ6004. We ran several times on Solaris 2.7/MQ5.2 boxes, and never had a problem. -Original Message- From: Robert Sloper [mailto:[EMAIL PROTECTED]] Sent: Friday, October 04, 2002 7:36 AM To: [EMAIL PROTECTED] Subject: We are trying to use amqiclen but are finding that it just hangs when we run it. Is there any documentation available for this 'undocumented' program? ...... A program, amqiclen, comes with MQ can clean up the IPC resources owned by the troubling queue manager. Here is the syntax: /opt/mqm/bin/amqiclen -v -c -m qmgr_name < /var/mqm/mqs.ini -v => verbose -c => check only (does not ipcrm anything) -m => only to clean up named queue manager returns: 0 => OK 2 => One or more connected process(es) >2 => unexpected error 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
