Transaction Names
I have already posted this question on mqseries.net, but I wondered if I would get some more responses on the list server... I am not looking for ideas on general MQSeries naming standards, I already have those and there are enough examples in the archives to keep anybody happy. Our queue naming standard is basically APP_NAME.TRANSACTION_NAME. Where APP_NAME is the name of the application that is allowed access to the queue. We use alias/remote queue definitions to wire up MYAPP.TRANSACTION_NAME - YOURAPP.TRANSACTION_NAME I am now looking in detail at the TRANSACTION_NAME. When I look at the queues we have I see a mixture of TRANSACTION_NAME styles - some of them are named after what the message content is (i.e. ORDER_AMENDMENT) and others are named after what the applications (typically the receiving application) does with the data (i.e. UPDATE_ORDER). Thus we would have a queue called: MYAPP.ORDER_AMENDMENT or MYAPP.UPDATE_ORDER I wanted to canvas whether people preferred the what it is over what it does or vica-versa. Which style do you use and why? Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd. ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and/or confidential, and is intended exclusively for the addressee. Unauthorised disclosure, copying or distribution of the contents is strictly prohibited. The views expressed may not be official policy, but the personal views of the originator. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for viruses, high-risk file extensions, and inappropriate content. 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
runmqlsr - 5 instances running ?
Hi, I'm replacing amqcrsta with runmqlsr. According to the insight I got from the Vegas conference, and a FAQ from IBM: ..., a SINGLE listener can now handle an unbounded number of connections... However, whenever I start runmqlsr, a ps -aef | grep runmqlsr shows five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist MessagingIntegration Supp. Mercedes-Benz USA x.2474 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: runmqlsr - 5 instances running ?
Depending on the platform what you may be seeing is all the active threads in the one listener process (with I think three active connections in this case). Do the PPID values all go back to the same runmqlsr process? If so then that would suggest that this is the case. What release of MQ is this and how are you starting the listener? If its 5.3 I'd expect one runmqlsr per QM, and on (or more) amqrmppa processes with multiple threads. David -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Benjamin F. Zhou Sent: 22 June 2004 12:49 To: [EMAIL PROTECTED] Subject: runmqlsr - 5 instances running ? Hi, I'm replacing amqcrsta with runmqlsr. According to the insight I got from the Vegas conference, and a FAQ from IBM: ..., a SINGLE listener can now handle an unbounded number of connections... However, whenever I start runmqlsr, a ps -aef | grep runmqlsr shows five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist MessagingIntegration Supp. Mercedes-Benz USA x.2474 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
Still on ssl troubles between z/os and sun solaris...
Title: Message Hi again Either my mail from yesterday got lost or notbody could help me on ma ssl problems... As a -18 doesnt provide much information, I would be interested on what ressources where touched on the failing call (cert name, label name ?) Therefor I tried to use the component trace with a trace writer. Setup the stuff as written in the manuals, but didnt got any data on ma trace dataset, and no error message from either trace writer or server stc. Well, next question: For this type off trace, I have to specify the job name who has to be traced. Is it now a problem as the ssl stuff gets executed under seperat tcb's and not the job step tcbof the channel initiator address space? Please help, I'm a poor CICS guy... :-( Regards Guido The content of this e-mail is intended only for the confidential use of the person addressed. If you have received this message in error, please notify us immediately by electronic mail, by telephone or by fax at the above num- bers. E-mail communications are not secure and therefore we do not accept any res- ponsibility for the confidentiality or altered contents of this message. Please be aware that SIS Group and its subsidiary companies cannot accept any orders or other legally binding correspondence with a participant as part of an E-mail. The views expressed above are not necessarily those held by SIS Group and its subsidiary companies and not binding for them. ***hexfe
Peter Gersak/Slovenia/IBM is out of the office.
I will be out of the office starting June 22, 2004 and will not return until July 4, 2004. I'm on the business trip. I'm reading mail on request only. In case of urgency, please call me on my mobile: +386 40 456 639. If you cannot reach me, please leave a voice mail or try to call me later. 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
OS/390 GET WAIT Troubles
Hi, We recently upgraded from WebSphere MQ 5.2 to 5.3.1 on an OS/390 2.10 system. We run a homegrown trigger monitor which does a GET WAIT on the batch initiation queue, it runs as a batch job...not a started task. The JWT on this system is set at 15 minutes. For some reason, it seems that under MQ 5.2 the batch job did NOT abend with a S522 (JWT Timeout), but when we implemented MQ 5.3.1 it started to timeout. Was there some architecture change between releases that would account for this? I assumed the GET WAIT caused the program to wait on an ECB, but I can't figure out why it would not time out under MQ 5.2was there some sort of keepalive handshake going on under the covers? Thanks for any response, George [EMAIL PROTECTED] ** This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: OS/390 GET WAIT Troubles
have TIME=1440 on the EXEC card? Bill -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Sproull, George Sent: Tuesday, June 22, 2004 11:16 AM To: [EMAIL PROTECTED] Subject: OS/390 GET WAIT Troubles Hi, We recently upgraded from WebSphere MQ 5.2 to 5.3.1 on an OS/390 2.10 system. We run a homegrown trigger monitor which does a GET WAIT on the batch initiation queue, it runs as a batch job...not a started task. The JWT on this system is set at 15 minutes. For some reason, it seems that under MQ 5.2 the batch job did NOT abend with a S522 (JWT Timeout), but when we implemented MQ 5.3.1 it started to timeout. Was there some architecture change between releases that would account for this? I assumed the GET WAIT caused the program to wait on an ECB, but I can't figure out why it would not time out under MQ 5.2was there some sort of keepalive handshake going on under the covers? Thanks for any response, George [EMAIL PROTECTED] 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: OS/390 GET WAIT Troubles
Aside from the JWT parameter in SYS1.PARMLIB(SMFPRMxx), I believe you can have an SMF exit that gains control when jobs/users fail due to a wait timeout. It's possible that the exit in your shop doesn't recognize the STC names used for MQ 5.3.1. Or, you could simply code TIME=1440 as someone else suggested. Sproull, George [EMAIL PROTECTED] SO-MECH.DISA.MIL To Sent by: MQSeries [EMAIL PROTECTED] List cc [EMAIL PROTECTED] n.AC.AT Subject OS/390 GET WAIT Troubles 06/22/2004 11:15 AM Please respond to MQSeries List [EMAIL PROTECTED] n.AC.AT Hi, We recently upgraded from WebSphere MQ 5.2 to 5.3.1 on an OS/390 2.10 system. We run a homegrown trigger monitor which does a GET WAIT on the batch initiation queue, it runs as a batch job...not a started task. The JWT on this system is set at 15 minutes. For some reason, it seems that under MQ 5.2 the batch job did NOT abend with a S522 (JWT Timeout), but when we implemented MQ 5.3.1 it started to timeout. Was there some architecture change between releases that would account for this? I assumed the GET WAIT caused the program to wait on an ECB, but I can't figure out why it would not time out under MQ 5.2was there some sort of keepalive handshake going on under the covers? Thanks for any response, George [EMAIL PROTECTED] ** This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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: OS/390 GET WAIT Troubles
George, I had opened a service request with MQ support a while back over the changed behaviour of CSQOREXX at 5.3.The change is that CSQOREXX now reacts to JWT where prior to 5.3 is seemed to not be affected by JWT. Here is part of the reply I got: The different behaviour of CSQOREXX is due to changes to the batch stub. In the past the batch stub has employed a STIMER exit to check for Queue Manager termination which if detected would post all get waiters. In V5.3 this function is only used for Get with Signal, Get with wait now employes a ECB/WAIT mechanism. So provided Get With Signal is NOT used time-outs can occur. I think this explains what you are seeing as well. -Tom -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Tom Schneider / IBM Global Services - MQSeries ASC (513) 274-4034 [EMAIL PROTECTED] -=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Sproull, George [EMAIL PROTECTED] Sent by: MQSeries List [EMAIL PROTECTED] 06/22/2004 11:15 AM Please respond to MQSeries List To [EMAIL PROTECTED] cc Subject OS/390 GET WAIT Troubles Hi, We recently upgraded from WebSphere MQ 5.2 to 5.3.1 on an OS/390 2.10 system. We run a homegrown trigger monitor which does a GET WAIT on the batch initiation queue, it runs as a batch job...not a started task. The JWT on this system is set at 15 minutes. For some reason, it seems that under MQ 5.2 the batch job did NOT abend with a S522 (JWT Timeout), but when we implemented MQ 5.3.1 it started to timeout. Was there some architecture change between releases that would account for this? I assumed the GET WAIT caused the program to wait on an ECB, but I can't figure out why it would not time out under MQ 5.2was there some sort of keepalive handshake going on under the covers? Thanks for any response, George [EMAIL PROTECTED] ** This email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ** Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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: Transaction Names
Our queues are named after what it is - we describe the contents of the queue... because a queue does not do anything. John Scott [EMAIL PROTECTED]To: [EMAIL PROTECTED] .CO.UK cc: Sent by: MQSeriesSubject: Transaction Names List [EMAIL PROTECTED] N.AC.AT 06/22/2004 01:29 AM Please respond to MQSeries List I have already posted this question on mqseries.net, but I wondered if I would get some more responses on the list server... I am not looking for ideas on general MQSeries naming standards, I already have those and there are enough examples in the archives to keep anybody happy. Our queue naming standard is basically APP_NAME.TRANSACTION_NAME. Where APP_NAME is the name of the application that is allowed access to the queue. We use alias/remote queue definitions to wire up MYAPP.TRANSACTION_NAME - YOURAPP.TRANSACTION_NAME I am now looking in detail at the TRANSACTION_NAME. When I look at the queues we have I see a mixture of TRANSACTION_NAME styles - some of them are named after what the message content is (i.e. ORDER_AMENDMENT) and others are named after what the applications (typically the receiving application) does with the data (i.e. UPDATE_ORDER). Thus we would have a queue called: MYAPP.ORDER_AMENDMENT or MYAPP.UPDATE_ORDER I wanted to canvas whether people preferred the what it is over what it does or vica-versa. Which style do you use and why? Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd. ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and/or confidential, and is intended exclusively for the addressee. Unauthorised disclosure, copying or distribution of the contents is strictly prohibited. The views expressed may not be official policy, but the personal views of the originator. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for viruses, high-risk file extensions, and inappropriate content. 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: Transaction Names
I always preferred SendingApp.ReceivingApp.BusinessReason where the third parameter looks like your transaction portion of the name. Business name could be defined as the business process_Interface so a message going from SAP to ARIBA for warehousing of the GL arbitrage accounts would look like the following: SAP.ARIBA.WAREHOUSE_GL-ARBITRAGE Obviously the naming portion after the sending and receivng portion has a certain amount of artistic license build into the actual naming but it allows a certain amount of traceability. I would think that this is the idea that would need to be promoted. Obviously there could probably be many examples where this design may not work but it could be used as a start. bobbee From: John Scott [EMAIL PROTECTED] Reply-To: MQSeries List [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Transaction Names Date: Tue, 22 Jun 2004 09:29:10 +0100 I have already posted this question on mqseries.net, but I wondered if I would get some more responses on the list server... I am not looking for ideas on general MQSeries naming standards, I already have those and there are enough examples in the archives to keep anybody happy. Our queue naming standard is basically APP_NAME.TRANSACTION_NAME. Where APP_NAME is the name of the application that is allowed access to the queue. We use alias/remote queue definitions to wire up MYAPP.TRANSACTION_NAME - YOURAPP.TRANSACTION_NAME I am now looking in detail at the TRANSACTION_NAME. When I look at the queues we have I see a mixture of TRANSACTION_NAME styles - some of them are named after what the message content is (i.e. ORDER_AMENDMENT) and others are named after what the applications (typically the receiving application) does with the data (i.e. UPDATE_ORDER). Thus we would have a queue called: MYAPP.ORDER_AMENDMENT or MYAPP.UPDATE_ORDER I wanted to canvas whether people preferred the what it is over what it does or vica-versa. Which style do you use and why? Regards John Scott IBM Certified Specialist - MQSeries Argos Ltd. ** Click here to visit the Argos home page http://www.argos.co.uk The information contained in this message or any of its attachments may be privileged and/or confidential, and is intended exclusively for the addressee. Unauthorised disclosure, copying or distribution of the contents is strictly prohibited. The views expressed may not be official policy, but the personal views of the originator. If you have received this message in error, please advise the sender by using the reply facility in your e-mail software. All messages sent and received by Argos Ltd are monitored for viruses, high-risk file extensions, and inappropriate content. 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 _ Watch the online reality show Mixed Messages with a friend and enter to win a trip to NY http://www.msnmessenger-download.click-url.com/go/onm00200497ave/direct/01/ 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
Windows 2000 Server and CSD07 problem
Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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: Windows 2000 Server and CSD07 problem
Roger, I am gonna guess this is just more typical MQ locked files, and nothing specific to CSD07. Try the following, I wrote this up for my team because we constantly deal with this: When applying a CSD, no MQSeries dlls can be held by any programs. This step will insure that all MQSeries dlls are released. a. Go to Services and stop the IBM MQSeries Service. Wait a minute or so, and if still present after 1 minute, right click on the MQServices Icon in the Task bar to stop WebSphere MQ and again to hide the icon. Give it (amqsvc.exe) a minute to drop out of the Task Manager after hiding it. b. The services listed in Appendix A should also be stopped when trying to install the CSD. They have all been known to hold onto MQ dlls. Appendix A Windows Services That Use MQSeries Files The following is a list of services that typically run on Windows Servers at The Hartford. All have been know to interfere with MQSeries Installs / Upgrades due to the fact that they use MQSeries dlls. If MQSeries dlls are in use, MQ will not allow you to upgrade MQ. Use this as a checklist to know which Services you shut off, so that you can restore them all back to their prior state upon completion of your MQSeries work on this server. 1. BGS_SDService Manual or Automatic 2. BMC SoftwareManual or Automatic 3. CPQHostsManual or Automatic 4. Compaq EcoTools Manual or Automatic 5. Compaq Versioning Control Manual or Automatic 6. IBM MQSeriesManual or Automatic 7. IBM MQSI Broker Manual or Automatic 8. IBM MQSI Configuration Manager Manual or Automatic 9. Norton Anti Virus Manual or Automatic 10. Performance Data Log ServiceManual or Automatic 11. QPASA (all three components)Manual or Automatic 12. SMV Collector Manual or Automatic 13. Tivoli Manual or Automatic 14. Windows Management Instrumentation Manual or Automatic 15. BMC is also known to hang onto to MQ Files, but it is not a service. You may need to manually kill it using procexp.exe. BMC is not always present, so you may not want to bother looking for this unless the CSD install cries about locked files even after stopping all of the above. Use listdlls.exe to see what is holding an MQSeries file; use procexp.exe to kill it if you can't find it in Task Manager or Services. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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 exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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: runmqlsr - 5 instances running ?
Please ignore last posting, It seems to be specific to this platform( Linux/zOS). On AIX, it shows only one. Benjamin F. ZhouTo: [EMAIL PROTECTED] [EMAIL PROTECTED] cc: BUSA.COMSubject: runmqlsr - 5 instances running ? Sent by: MQSeries List [EMAIL PROTECTED] en.AC.AT 06/22/2004 07:48 AM Please respond to MQSeries List Hi, I'm replacing amqcrsta with runmqlsr. According to the insight I got from the Vegas conference, and a FAQ from IBM: ..., a SINGLE listener can now handle an unbounded number of connections... However, whenever I start runmqlsr, a ps -aef | grep runmqlsr shows five instances of it running. Is this the default behavior? Can anyone explain why? thanks, Benjamin F. Zhou Technical Specialist MessagingIntegration Supp. Mercedes-Benz USA x.2474 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: Windows 2000 Server and CSD07 problem
We had a problem just like that and we even were using the MQPINUSEOK=1 flag. We tried stopping most of the services, but still got the error. Eventually we just rebooted. Now mqver say it is at 530.7 CSD07, but I wonder how good the install is. The queue manager is running and seems to be problem free so far. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 2:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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: Windows 2000 Server and CSD07 problem
Check the listserv archive (date around May 7,2004). There were some excellent responses to a similar problem, not with W2K and Terminal Services, but with applying CSDs in general. 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: Windows 2000 Server and CSD07 problem
From the IBM docs: - All MQ activity must be stopped before CSD install - Check for processes with prefixes - amq,runmq, strmq - Stop tools used to monitor MQ or any performance monitor tasks - http://www.sysinternals.com (Process Explorer, etc.) - CSD install log %TEMP%amqicsdn.txt shows the files in use - Reboot if process locking the files cannot be identified - Before reboot disable IBM MQ Series service - NET STOP IBM MQSeries --- Sudheer -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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: Windows 2000 Server and CSD07 problem
Roger, I had a similar problem with Win/2000 SP3 and CSD5. I rebooted several times and it finally worked. I never did pin-down the cause of the problem, you might want to look at the install log (see Quick Beginnings). It should name the files it's choking on. Roger Lacroix [EMAIL PROTECTED] PITALWARE.BIZ To Sent by: MQSeries [EMAIL PROTECTED] List cc [EMAIL PROTECTED] n.AC.AT Subject Windows 2000 Server and CSD07 problem 06/22/2004 03:57 PM Please respond to MQSeries List [EMAIL PROTECTED] n.AC.AT Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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
WBIMB Mapping DB input source question
In WBIMB when you are using a mapping node and configure the node to accept the input from a RDB (database) source and have the output to a message set. It look as if the mapping is going to generate a seperate SELECT call for each mapping. In the database node you can combine mapping statements after you do the mapping so individual calls are not made. Can this be done in the mapping node or will this puppy make multiple select calls?? bobbee _ Is your PC infected? Get a FREE online computer virus scan from McAfee. Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 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: Windows 2000 Server and CSD07 problem
Hi, Of your list of files, besides IBM MQSeries, we have Windows Management Instrumentation and stopping it did not help. Regards, Roger Lacroix Quoting Potkay, Peter M (PLC, IT) [EMAIL PROTECTED]: Roger, I am gonna guess this is just more typical MQ locked files, and nothing specific to CSD07. Try the following, I wrote this up for my team because we constantly deal with this: When applying a CSD, no MQSeries dlls can be held by any programs. This step will insure that all MQSeries dlls are released. a. Go to Services and stop the IBM MQSeries Service. Wait a minute or so, and if still present after 1 minute, right click on the MQServices Icon in the Task bar to stop WebSphere MQ and again to hide the icon. Give it (amqsvc.exe) a minute to drop out of the Task Manager after hiding it. b. The services listed in Appendix A should also be stopped when trying to install the CSD. They have all been known to hold onto MQ dlls. Appendix A Windows Services That Use MQSeries Files The following is a list of services that typically run on Windows Servers at The Hartford. All have been know to interfere with MQSeries Installs / Upgrades due to the fact that they use MQSeries dlls. If MQSeries dlls are in use, MQ will not allow you to upgrade MQ. Use this as a checklist to know which Services you shut off, so that you can restore them all back to their prior state upon completion of your MQSeries work on this server. 1. BGS_SDService Manual or Automatic 2. BMC SoftwareManual or Automatic 3. CPQHostsManual or Automatic 4. Compaq EcoTools Manual or Automatic 5. Compaq Versioning Control Manual or Automatic 6. IBM MQSeriesManual or Automatic 7. IBM MQSI Broker Manual or Automatic 8. IBM MQSI Configuration Manager Manual or Automatic 9. Norton Anti Virus Manual or Automatic 10. Performance Data Log ServiceManual or Automatic 11. QPASA (all three components)Manual or Automatic 12. SMV Collector Manual or Automatic 13. Tivoli Manual or Automatic 14. Windows Management Instrumentation Manual or Automatic 15. BMC is also known to hang onto to MQ Files, but it is not a service. You may need to manually kill it using procexp.exe. BMC is not always present, so you may not want to bother looking for this unless the CSD install cries about locked files even after stopping all of the above. Use listdlls.exe to see what is holding an MQSeries file; use procexp.exe to kill it if you can't find it in Task Manager or Services. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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 exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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: Windows 2000 Server and CSD07 problem
Yes, that was Peter's checklist email plus some other comments. Regards, Roger Lacroix 416-566-7307 Capitalware Inc. http://www.capitalware.biz Quoting Lawrence Coombs [EMAIL PROTECTED]: Check the listserv archive (date around May 7,2004). There were some excellent responses to a similar problem, not with W2K and Terminal Services, but with applying CSDs in general. 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: Windows 2000 Server and CSD07 problem
Fun is, huh? Go to sysinternal.com, and download listdlls.exe. It is a lifesaver. Then follow the below steps. Process Explorer is also found at sysinternals. This has always worked, and I have dealt with CSD upgrades on 5.3 about 50 times. Ya know, this was never such an issue at 5.2.1.why did 5.3 make it so bad. 1.Put the listdlls.exe into a folder on the server, like maybe E:\Programs\IBM\MQSeries\MQSupportTools. 2.CD into that directory from the dos prompt. 3.Run the executable, and pipe the output into a text file. Here is a sample of what you would type assuming you placed the executable file as in step 1: E:\Programs\IBM\MQSeries\MQSupportTools\listdlls.exe DLLOutput.txt 4.Open DLLOutput.txt and do a search on MQ. Scroll up to see what .exe is using this MQ dll. 5.Stop the application that is using the MQ dll and you should be all set. If you do not recognize what this .exe is, use Process Explorer (procexp.exe). You can find the exe in there, and it will tell you what app it is. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 5:05 PM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 Server and CSD07 problem Hi, Of your list of files, besides IBM MQSeries, we have Windows Management Instrumentation and stopping it did not help. Regards, Roger Lacroix Quoting Potkay, Peter M (PLC, IT) [EMAIL PROTECTED]: Roger, I am gonna guess this is just more typical MQ locked files, and nothing specific to CSD07. Try the following, I wrote this up for my team because we constantly deal with this: When applying a CSD, no MQSeries dlls can be held by any programs. This step will insure that all MQSeries dlls are released. a. Go to Services and stop the IBM MQSeries Service. Wait a minute or so, and if still present after 1 minute, right click on the MQServices Icon in the Task bar to stop WebSphere MQ and again to hide the icon. Give it (amqsvc.exe) a minute to drop out of the Task Manager after hiding it. b. The services listed in Appendix A should also be stopped when trying to install the CSD. They have all been known to hold onto MQ dlls. Appendix A Windows Services That Use MQSeries Files The following is a list of services that typically run on Windows Servers at The Hartford. All have been know to interfere with MQSeries Installs / Upgrades due to the fact that they use MQSeries dlls. If MQSeries dlls are in use, MQ will not allow you to upgrade MQ. Use this as a checklist to know which Services you shut off, so that you can restore them all back to their prior state upon completion of your MQSeries work on this server. 1. BGS_SDService Manual or Automatic 2. BMC SoftwareManual or Automatic 3. CPQHostsManual or Automatic 4. Compaq EcoTools Manual or Automatic 5. Compaq Versioning Control Manual or Automatic 6. IBM MQSeriesManual or Automatic 7. IBM MQSI Broker Manual or Automatic 8. IBM MQSI Configuration Manager Manual or Automatic 9. Norton Anti Virus Manual or Automatic 10. Performance Data Log ServiceManual or Automatic 11. QPASA (all three components)Manual or Automatic 12. SMV Collector Manual or Automatic 13. Tivoli Manual or Automatic 14. Windows Management Instrumentation Manual or Automatic 15. BMC is also known to hang onto to MQ Files, but it is not a service. You may need to manually kill it using procexp.exe. BMC is not always present, so you may not want to bother looking for this unless the CSD install cries about locked files even after stopping all of the above. Use listdlls.exe to see what is holding an MQSeries file; use procexp.exe to kill it if you can't find it in Task Manager or Services. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I
Re: Windows 2000 Server and CSD07 problem
Yes, did that but it not help - the files remained locked. Regards, Roger Lacroix 416-566-7307 Capitalware Inc. http://www.capitalware.biz Quoting Kumar, Sudheer [EMAIL PROTECTED]: From the IBM docs: - All MQ activity must be stopped before CSD install - Check for processes with prefixes - amq,runmq, strmq - Stop tools used to monitor MQ or any performance monitor tasks - http://www.sysinternals.com (Process Explorer, etc.) - CSD install log %TEMP%amqicsdn.txt shows the files in use - Reboot if process locking the files cannot be identified - Before reboot disable IBM MQ Series service - NET STOP IBM MQSeries --- Sudheer -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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
Not directly MQ - Time Syncing your servers
What do people out there use for syncing up all their clocks on all their servers? We are using Transaction Vision to correlate our transactions. TV reports the time from its sensors down to the millisecond (microsecond on z/OS and UNIX). But if the servers are off in time by tenths or even hundredths of a second, the result are skewed for transactions that zip thru 3 servers in half a second. I get results showing that events on server 3 happened before server 2. And I am not confident on how long the message took to get from 1 to 2, even if the order happens to be correct. Is it realistic to expect better than one second accuracy between servers if you are using time sync software? To the naked eye all the servers look pretty well synced up, but at the millisecond level, they are all over the place. Peter Potkay MQSeries Specialist The Hartford Financial Services [EMAIL PROTECTED] x77906 IBM MQSeries Certified This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies. 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
Resolved: Windows 2000 Server and CSD07 problem
All, Thanks for your comments. No matter how many things I stopped and how many times I rebooted the server, I had the problem with locked files. Besides what mentioned below, here is what I did to resolve the problem: - Removed the MQ Taskbar icon from the Startup folder - Set the IBM MQ Series service to 'Manual' then REBOOTED. - Tried the CSD07 install again and of course it failed - Checked the CSD install log by doing the following command: notepad %TEMP%\amqicsdn.txt - Search for the string 'Target file is in use' - For each entry found (I had 5), renamed it to 'roger_amq*' - REBOOTED again. - After the the reboot, deleted the 'roger_amq*' files - Tried the CSD07 install again and this time it worked. - REBOOT again. - Put back the Task Bar icon in the startup folder - Set the IBM MQ Series service to 'Automatic' and started the service. - REBOOTED one last time to make sure everything worked and it did. Now mqver gives 530.7 CSD07. Yeah!!! Regards, Roger Lacroix Capitalware Inc. http://www.capitalware.biz Quoting Roger Lacroix [EMAIL PROTECTED]: Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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: Windows 2000 Server and CSD07 problem
Did you hide the MQSeries task bar icon? On the task bar, right click on the Websphere MQ icon and select Hide from the menu. That stops amqmtbrn.exe, and that has been enough to get me over the hump. Roger Lacroix [EMAIL PROTECTED]To: [EMAIL PROTECTED] ALWARE.BIZ cc: Sent by: MQSeries Subject: Re: Windows 2000 Server and CSD07 problem List [EMAIL PROTECTED] c.at 06/22/2004 04:15 PM Please respond to MQSeries List Yes, did that but it not help - the files remained locked. Regards, Roger Lacroix 416-566-7307 Capitalware Inc. http://www.capitalware.biz Quoting Kumar, Sudheer [EMAIL PROTECTED]: From the IBM docs: - All MQ activity must be stopped before CSD install - Check for processes with prefixes - amq,runmq, strmq - Stop tools used to monitor MQ or any performance monitor tasks - http://www.sysinternals.com (Process Explorer, etc.) - CSD install log %TEMP%amqicsdn.txt shows the files in use - Reboot if process locking the files cannot be identified - Before reboot disable IBM MQ Series service - NET STOP IBM MQSeries --- Sudheer -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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 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: Windows 2000 Server and CSD07 problem
See if a process has any of the MQSeries DLL's open. http://www.sysinternals.com has a utility called process explorer which can help. If you run it up choose the find option then find dll - enter mq and it should find all the processes with MQSeries dll's open. You can also try the find handle option and enter say ibm(if you installed MQ into \program files\ibm\websphere mq otherwise enter some other directory name in the MQSeries path) and all processes having any MQ related files open should be listed. Hope this is of some assistance. +++ -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Roger Lacroix Sent: Tuesday, June 22, 2004 13:58 To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I stopped the MQ Services and clicked 'Hide the icon'. Check Task Manager for any AMQ*** or RUNMQ*** tasks and there were none. Under Terminal Services launched the CSD07 (U200212A.exe) and goes fine until it gets to'Checking files; please wait' (the 2nd time). Then I get the following error: 'IBM WebSphere MQ files are in use. Stop activity and retry. (AMQ4757)' I have rebooted the server 2 twice now, stopped services, checked the Task Manager and I don't see anything MQ related running. I have NOT even defined a queue manager yet on this server!! Could it be a problem with Terminal Services?? Or is CSD07 like CSD06 where it wasn't fully baked by IBM? Anyone have an idea or comment? Regards, Roger lacroix Capitalware Inc. 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: Windows 2000 Server and CSD07 problem
Roger, And do you see patrolpsf.exe running? I had experience that this locked amqmperf and amqxcs2 dll. Listdll is able to display that. Cheers, Ian -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Potkay, Peter M (PLC, IT) Sent: Wednesday, 23 June 2004 7:12 AM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 Server and CSD07 problem Fun is, huh? Go to sysinternal.com, and download listdlls.exe. It is a lifesaver. Then follow the below steps. Process Explorer is also found at sysinternals. This has always worked, and I have dealt with CSD upgrades on 5.3 about 50 times. Ya know, this was never such an issue at 5.2.1.why did 5.3 make it so bad. 1.Put the listdlls.exe into a folder on the server, like maybe E:\Programs\IBM\MQSeries\MQSupportTools. 2.CD into that directory from the dos prompt. 3.Run the executable, and pipe the output into a text file. Here is a sample of what you would type assuming you placed the executable file as in step 1: E:\Programs\IBM\MQSeries\MQSupportTools\listdlls.exe DLLOutput.txt 4.Open DLLOutput.txt and do a search on MQ. Scroll up to see what .exe is using this MQ dll. 5.Stop the application that is using the MQ dll and you should be all set. If you do not recognize what this .exe is, use Process Explorer (procexp.exe). You can find the exe in there, and it will tell you what app it is. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 5:05 PM To: [EMAIL PROTECTED] Subject: Re: Windows 2000 Server and CSD07 problem Hi, Of your list of files, besides IBM MQSeries, we have Windows Management Instrumentation and stopping it did not help. Regards, Roger Lacroix Quoting Potkay, Peter M (PLC, IT) [EMAIL PROTECTED]: Roger, I am gonna guess this is just more typical MQ locked files, and nothing specific to CSD07. Try the following, I wrote this up for my team because we constantly deal with this: When applying a CSD, no MQSeries dlls can be held by any programs. This step will insure that all MQSeries dlls are released. a. Go to Services and stop the IBM MQSeries Service. Wait a minute or so, and if still present after 1 minute, right click on the MQServices Icon in the Task bar to stop WebSphere MQ and again to hide the icon. Give it (amqsvc.exe) a minute to drop out of the Task Manager after hiding it. b. The services listed in Appendix A should also be stopped when trying to install the CSD. They have all been known to hold onto MQ dlls. Appendix A Windows Services That Use MQSeries Files The following is a list of services that typically run on Windows Servers at The Hartford. All have been know to interfere with MQSeries Installs / Upgrades due to the fact that they use MQSeries dlls. If MQSeries dlls are in use, MQ will not allow you to upgrade MQ. Use this as a checklist to know which Services you shut off, so that you can restore them all back to their prior state upon completion of your MQSeries work on this server. 1. BGS_SDService Manual or Automatic 2. BMC SoftwareManual or Automatic 3. CPQHostsManual or Automatic 4. Compaq EcoTools Manual or Automatic 5. Compaq Versioning Control Manual or Automatic 6. IBM MQSeriesManual or Automatic 7. IBM MQSI Broker Manual or Automatic 8. IBM MQSI Configuration Manager Manual or Automatic 9. Norton Anti Virus Manual or Automatic 10. Performance Data Log ServiceManual or Automatic 11. QPASA (all three components)Manual or Automatic 12. SMV Collector Manual or Automatic 13. Tivoli Manual or Automatic 14. Windows Management Instrumentation Manual or Automatic 15. BMC is also known to hang onto to MQ Files, but it is not a service. You may need to manually kill it using procexp.exe. BMC is not always present, so you may not want to bother looking for this unless the CSD install cries about locked files even after stopping all of the above. Use listdlls.exe to see what is holding an MQSeries file; use procexp.exe to kill it if you can't find it in Task Manager or Services. -Original Message- From: Roger Lacroix [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 22, 2004 3:58 PM To: [EMAIL PROTECTED] Subject: Windows 2000 Server and CSD07 problem Help please, Box: Windows 2000 Server SP4 (dual CPU) Today I installed WMQ v5.3 with CSD01 using Terminal Services (to D: drive of server) and the install went fine (I copied the CD to a local drive then did the install from it). As I said, everything went fine and I reboot the server. After the reboot, I downloaded CSD07. First I
Help about MQSeries on AS400
Hi, I am working on MQSeries with AS400. I have 2 queue managers speaking to each other using Remote queue definition and transmission queue, sender channel and receiver channel. What I want to do is track the message where all it flows through. For this we need a channel exit program. I have generated a service program for the same. Now what I want to do is call this service program when the message moves across the channel. That is this service program should get activated when the message moves across a channel. This will be analogous to dll in windows. So it will load library in windows. If this has to be AS400 not sure as to what is to be done. I want to know how to call the service program when the message moves across the channel. Any pointers to this will be really helpful. Regards, Shuba 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
