Ashok Agarwala/DTC is out of the office.
I will be out of the office from 12/02/2002 until 12/23/2002. I will respond to your message when I return. 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: LOG ABEND
MQ should automatically attempt to offload the log again when the next one fills up. Mark Steely cc: Sent by: MQSeriesSubject: LOG ABEND List 03/12/2002 03:13 Please respond to MQSeries List We are OS/390 V2.8 and MQ v2.1. During the ARCHIVE offload process one of the tapes received an IO/ERROR, a swap was performed 3 times and was unable to bypass the tape error, the reply to the WTO to swap was no. The MQ region took a SVC dump, but continue to process. How can I restart the offload process or will MQ restart the process on it own? Any help would be appreciated. Thank You Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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: Triggering when CKTI comes up
I should have said that the transaction is getting triggered but sees that certain resources aren't available yet so doesn't even try to open the queue and process the messages - it just ends. Everything is working as designed ... it's just not a good design. Lowering the TRIGINT fixes this, though I still think the application should code an EXEC CICS START with some interval when it finds the application resources are not up yet. TRIGINT is good for recovering from unexpected situations like the program abending before it gets the queue open, but it doesn't seem like a good idea to rely upon it as part of your program design. Thanks for everyone's input. -Original Message- From: Ronald Weinger [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 2:10 PM To: [EMAIL PROTECTED] Subject:Re: Triggering when CKTI comes up Usually those symptoms indicate a mismatched or mispelled definition between what is in the application and the MQ objects. "MCSHEFFREY, MICHELLE (AIT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc: Sent by: Subject: Re: Triggering when CKTI comes up "MQSeries List" 12/02/2002 02:53 PM Please respond to "MQSeries List" The solution actually isn't very interesting. I looked at the use count of the program after the CICS region comes up (and messages are sitting on the queue), and it is non-zero, indicating that the transaction is getting triggered but not opening the queue and processing the messages (I don't have a tool to see when the transaction ran and was relying on the programmer's report). Also, the TRIGINT was 99, not 60 seconds - I'd looked at the wrong queue manager. Fortunately I figured this all out before gathering a trace and sending it to IBM. -Original Message- From: MCSHEFFREY, MICHELLE (AIT) Sent: Tuesday, November 26, 2002 10:05 AM To: 'MQSeries List' Subject:RE: Triggering when CKTI comes up Thanks for everyone's replies. In our case, we are not getting a trigger when CICS and CKTI come up, nor are we getting a trigger after the TRIGINT of 60 seconds have passed when new messages arrive on the trigger queue. If I flip the trigger to N then back to Y, it does generate a trigger, though, so it seems triggering is working in general. I will continue to work with IBM on this and post the solution if turns out to be something interesting. _ Michelle McSheffrey - MQSeries/Tuxedo Support Phone: (312) 669-2059 Pager: (312) 760-2059 _ For emergency support, use WebNotify at http://ebiz.sbc.com/webnotify/ to page the on-call support person. For MQSeries, send the page to the MQSERIES group. For Tuxedo, send the page to the TUXEDO group. Team WEB site: http://mvsha00.sbc.com/appl/cics/index.htm -Original Message- From: Raabe, Stefan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 3:54 AM To: [EMAIL PROTECTED] Subject:AW: Triggering when CKTI comes up No :-) After CKTI startup there is an immediate trigger as explained by others some messages before trigger interval works different. its not a time interval after that queues are scanned if they should be triggered again, its a time interval that has to be expirered after the last trigger message was generated and a new message that is put to the queue. read system application programmers guide for details. regards stefan -Ursprüngliche Nachricht- Von: Chan, Ian M [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. November 2002 01:45 An: [EMAIL PROTECTED] Betreff: Re: Triggering when CKTI comes up I think it also depends on the trigger interval. Once the CKTI is up and running, the trigger message will be generated within the trigger interval period. Ian -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 8:02 AM To: [EMAIL PROTECTED] Subject: Re: Triggering when CKTI comes up One of the times that the QM checks to see if a trigger message should be generated is when the INIT queue IPROCS count goes from 0 to 1. I would think that when CKT1 is brought up, it opens the INIT queue, and if no other app had the init queue open, the IPROCS would then go from 0 to 1. The queue manager would check to see if any queues meet trigger criteria, and would see that your triggered on first queue had more than zero messages on it, and would thus trigger. I tested this behaviour on distributed and it does exactly that. Don't know if CICS would be different. The triggering manual doesn't say so. http://publibfp.boulder.ibm.com/epubs/html/csqzal
Re: WMQI V2.1 vs. MQSI V2.0.2
Thanks for the info. That makes sense since many users don't use the NEON rules. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com Jason Cornell <[EMAIL PROTECTED]> wrote: Date Recieved: 12/02/2002 01:45:58 PM To: [EMAIL PROTECTED] cc: Bcc Subject: Re: WMQI V2.1 vs. MQSI V2.0.2 The Integrator broker is cheaper. The price difference, according to IBM, is due to the fact it does not contain the NEON functionality. >>> [EMAIL PROTECTED] 12/02/02 03:13PM >>> And to add to this, what is with the new name? Now I see both WebSphere MQ Integrator and WebSphere MQ Integrator Broker. Does the term "broker" make it different? I can see versions with and without "broker" in the name, both version 2.1, but if you click on the link to either download it takes you to the same site for WebSphere MQ Integrator Broker. Are these different products? Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com [EMAIL PROTECTED] wrote: Date Recieved: 12/02/2002 10:46:19 AM To: [EMAIL PROTECTED] cc: Bcc Subject: WMQI V2.1 vs. MQSI V2.0.2 I've searched the IBM website for documents comparing these two version, but have found none which directly address the differences. Have I missed something ? Does anyone know of any document which summarizes the differences ? Thanks ! Phil This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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: Removal of Messages
Michael, If you don't get any other reply, send me an email and I can send you VB source for a dll (that you can change to be an executable). It deletes messages older than a certain time period (seconds, minutes, hours or days) and writes a report. Peter From: Administrator <[EMAIL PROTECTED]> on 12/02/2002 01:20 PM Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Removal of Messages I have a message problem that I need to deal with. I have messages that can sit on my queue and get stuck there. I need to write a script that will clear messages that have been sitting on the queue over a period of time, say 100 hours. Unfortunatly my client will not set expiry on the message, so this has to be a script that I write to handle this process. I am a straight Windows NT shop. If anybody has a script that I can use to clear messages meeting this criteria I would greatly appreciate it. Thank you. Michael 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: Keep Alive vs Heartbeat - What's the diff?
Thanks Paul. Very clear now. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 3:11 PM To: [EMAIL PROTECTED] Subject: Re: Keep Alive vs Heartbeat - What's the diff? >Paul, >Keep Alive is configured at the machine level, correct? So all TCP >applications on a machine have to agree to a common value? Most platforms allow you to only set a machine wide keep alive interval, zOS is an exception, there may be others. Each socket application can merely choose to switch keepalive on or off. >You said HB doesn't apply on SVRCONN channels, but the below paragraph from >the Intercommunication handbook says it does? No I didn't. I said a SVRCONN channel can not heartbeat to a client *between* MQI calls. > >This attribute is valid for sender, cluster-sender, server, receiver, >cluster-receiver, and requester channels. Other than on OS/390 and OS/400, >it also applies to server-connection and client-connection channels. On >these channels, heartbeats flow when a server MCA has issued an MQGET >command with the WAIT option on behalf of a client application. > Thanks for the book quote but there's a fair chance I wrote this. >So for Blocking Gets, the HB comes into play, but for all other times that >an MQClient might be connected, the Keep Alive pulse is what will catch the >MQClient dissappearing without disconnecting? Yes. >The manual says if 2 sides of a channel have different values, the larger is >used. Unless one side is ZERO, which means no HB? In that case ZERO trumps >the other side? Yes, if you like ZERO is treated as an infinite heartbeat value. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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: WMQI V2.1 vs. MQSI V2.0.2
The Integrator broker is cheaper. The price difference, according to IBM, is due to the fact it does not contain the NEON functionality.>>> [EMAIL PROTECTED] 12/02/02 03:13PM >>>And to add to this, what is with the new name? Now I see both WebSphere MQ Integrator and WebSphere MQ Integrator Broker. Does the term "broker" make it different? I can see versions with and without "broker" in the name, both version 2.1, but if you click on the link to either download it takes you to the same site for WebSphere MQ Integrator Broker. Are these different products? Mike MurphySr. Middleware ConsultantMQ Solutions, LLChttp://www.mqsolutions.com[EMAIL PROTECTED] wrote: Date Recieved: 12/02/2002 10:46:19 AM To: [EMAIL PROTECTED] cc: Bcc Subject: WMQI V2.1 vs. MQSI V2.0.2I've searched the IBM website for documents comparing these two version,but have found none which directly address the differences. Have I missedsomething ?Does anyone know of any document which summarizes the differences ?Thanks !PhilThis communication is for informational purposes only. It is not intended asan offer or solicitation for the purchase or sale of any financial instrumentor as an official confirmation of any transaction. All market prices, dataand other information are not warranted as to completeness or accuracy andare subject to change without notice. Any comments or statements made hereindo not necessarily reflect those of J.P. Morgan Chase & Co., itssubsidiaries and affiliates.Instructions 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: New MQ numbering confusing to a point of frustration
I understand the 5.2.1 thing. But 5.3.1 is for all platforms so that wipes that explanation. I opened a PMR for this but they haven't called me back yet. I want to get something from them because I am telling my client to not upgrade to 5.3 because of this issue. I won't be responsible for something getting screwed up because we can't tell what version we really have. I am attaching my memo.ptf from Windows. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com Luc-Michel Demey <[EMAIL PROTECTED]> wrote: Date Recieved: 12/02/2002 10:09:49 AM To: [EMAIL PROTECTED] cc: Bcc Subject: Re: New MQ numbering confusing to a point of frustration Date sent: Mon, 2 Dec 2002 16:45:23 - Send reply to: MQSeries List <[EMAIL PROTECTED]> From: "David C. Partridge" <[EMAIL PROTECTED]> Subject: Re: New MQ numbering confusing to a point of frustration To: [EMAIL PROTECTED] > Mike, > > Are you absolutely sure that MQ5.3.1 does include CSD1. I don't think it > does based on some discussions the other week at Hursley. > > Please could IBM clarify this yes ! AFAK, for windows flavor, 5.3 is the same story than 5.2, ie : - a 5.2 version not certified on Win2000 - a 5.2.1 certified, with CSD 1 included just replace "5.2" by "5.3" and "Win2000" by "WinXP" ;-) ... I will try to double check this with IBM localy. LMD. PS : have you noticed that MQ clients are listed "5.3.1" ?-- Luc-Michel Demey - Consultant indipendant Architecte EAI - Expert MQSeries - +33 6 08 755 655 http://consulting.demey.org/ - [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 memo.ptf Description: Binary data
Re: Keep Alive vs Heartbeat - What's the diff?
> What is the difference between these two, if any? Seems to me they both > accomplish the same thing (allowing one side of a channel to see that the > network is down and thus being able to go Inactive). The only thing I can > guess is that Keep Alive applies only to TCP while Heartbeat will work for > other transmission protocols as well as TCP. Keepalive and channel Heartbeats do tend to serve similar functions (and actually work in a similar way), but there are some differences between them. Both work by periodically sending data over an otherwise inactive channel. The difference is that Keepalive is performed by TCP/IP 'under the covers' as out-of-band data which MQ is never aware of, and Heartbeats are sent as actual data flows. As you pointed out, this does mean that Keepalive is only available for TCP/IP based channels. Of the two, Keepalive is usually more reliable at detecting network problems since it is always active, even if a channel is in a state where Heartbeats may not normally be sent, such as at the end of a batch of messages when a sender is waiting for confirmation of receipt from the partner. Heartbeats, however, offer some advantages which Keepalive cannot. They will allow the receiver MCA to periodically wake up and see if it has been told to stop mode(quiesce). It also gives an otherwise inactive receiver the opportunity to free any resources it's not used in some time (close target queues, free buffers, etc.). One problem with Keepalive, is that on most platforms, it's only possible to configure one Keepalive interval for ALL TCP/IP connections on the system. This means that if you wanted, say, a 5 minute timeout for your channels, you will inherit the same timeout for every TCP/IP connection one that system which uses Keepalive (e.g. telnet, ftp, etc.). The lower timeout causes extra network traffic as it needs to send additional keepalive packets for each connection which has not seen any activity for the duration of the keepalive timer. The default Keepalive timer on most systems is two hours. In recent times, it's become possible to specify Keepalive times for individual connections on z/OS. On this platform, we now have (in V5.3.0) the KAINT channel attribute, which allows you to specify an individual keepalive timer for any given channel. If you opt to use both Heartbeats and Keepalive, then it's most logical to ensure your Keepalive timer is longer than the HBINT for a channel, otherwise an inactive channel will be sending both Heartbeats and Keepalive packets. Neil Johnston. WebSphere MQ for z/OS Development. 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: Triggering when CKTI comes up
Usually those symptoms indicate a mismatched or mispelled definition between what is in the application and the MQ objects. "MCSHEFFREY, MICHELLE (AIT)" To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> cc: Sent by: Subject: Re: Triggering when CKTI comes up "MQSeries List" 12/02/2002 02:53 PM Please respond to "MQSeries List" The solution actually isn't very interesting. I looked at the use count of the program after the CICS region comes up (and messages are sitting on the queue), and it is non-zero, indicating that the transaction is getting triggered but not opening the queue and processing the messages (I don't have a tool to see when the transaction ran and was relying on the programmer's report). Also, the TRIGINT was 99, not 60 seconds - I'd looked at the wrong queue manager. Fortunately I figured this all out before gathering a trace and sending it to IBM. -Original Message- From: MCSHEFFREY, MICHELLE (AIT) Sent: Tuesday, November 26, 2002 10:05 AM To: 'MQSeries List' Subject:RE: Triggering when CKTI comes up Thanks for everyone's replies. In our case, we are not getting a trigger when CICS and CKTI come up, nor are we getting a trigger after the TRIGINT of 60 seconds have passed when new messages arrive on the trigger queue. If I flip the trigger to N then back to Y, it does generate a trigger, though, so it seems triggering is working in general. I will continue to work with IBM on this and post the solution if turns out to be something interesting. _ Michelle McSheffrey - MQSeries/Tuxedo Support Phone: (312) 669-2059 Pager: (312) 760-2059 _ For emergency support, use WebNotify at http://ebiz.sbc.com/webnotify/ to page the on-call support person. For MQSeries, send the page to the MQSERIES group. For Tuxedo, send the page to the TUXEDO group. Team WEB site: http://mvsha00.sbc.com/appl/cics/index.htm -Original Message- From: Raabe, Stefan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 3:54 AM To: [EMAIL PROTECTED] Subject:AW: Triggering when CKTI comes up No :-) After CKTI startup there is an immediate trigger as explained by others some messages before trigger interval works different. its not a time interval after that queues are scanned if they should be triggered again, its a time interval that has to be expirered after the last trigger message was generated and a new message that is put to the queue. read system application programmers guide for details. regards stefan -Ursprüngliche Nachricht- Von: Chan, Ian M [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. November 2002 01:45 An: [EMAIL PROTECTED] Betreff: Re: Triggering when CKTI comes up I think it also depends on the trigger interval. Once the CKTI is up and running, the trigger message will be generated within the trigger interval period. Ian -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 8:02 AM To: [EMAIL PROTECTED] Subject: Re: Triggering when CKTI comes up One of the ti
Re: Keep Alive vs Heartbeat - What's the diff?
>Paul, >Keep Alive is configured at the machine level, correct? So all TCP >applications on a machine have to agree to a common value? Most platforms allow you to only set a machine wide keep alive interval, zOS is an exception, there may be others. Each socket application can merely choose to switch keepalive on or off. >You said HB doesn't apply on SVRCONN channels, but the below paragraph from >the Intercommunication handbook says it does? No I didn't. I said a SVRCONN channel can not heartbeat to a client *between* MQI calls. > >This attribute is valid for sender, cluster-sender, server, receiver, >cluster-receiver, and requester channels. Other than on OS/390 and OS/400, >it also applies to server-connection and client-connection channels. On >these channels, heartbeats flow when a server MCA has issued an MQGET >command with the WAIT option on behalf of a client application. > Thanks for the book quote but there's a fair chance I wrote this. >So for Blocking Gets, the HB comes into play, but for all other times that >an MQClient might be connected, the Keep Alive pulse is what will catch the >MQClient dissappearing without disconnecting? Yes. >The manual says if 2 sides of a channel have different values, the larger is >used. Unless one side is ZERO, which means no HB? In that case ZERO trumps >the other side? Yes, if you like ZERO is treated as an infinite heartbeat value. Cheers, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: WMQI V2.1 vs. MQSI V2.0.2
And to add to this, what is with the new name? Now I see both WebSphere MQ Integrator and WebSphere MQ Integrator Broker. Does the term "broker" make it different? I can see versions with and without "broker" in the name, both version 2.1, but if you click on the link to either download it takes you to the same site for WebSphere MQ Integrator Broker. Are these different products? Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com [EMAIL PROTECTED] wrote: Date Recieved: 12/02/2002 10:46:19 AM To: [EMAIL PROTECTED] cc: Bcc Subject: WMQI V2.1 vs. MQSI V2.0.2 I've searched the IBM website for documents comparing these two version, but have found none which directly address the differences. Have I missed something ? Does anyone know of any document which summarizes the differences ? Thanks ! Phil This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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: Triggering when CKTI comes up
The solution actually isn't very interesting. I looked at the use count of the program after the CICS region comes up (and messages are sitting on the queue), and it is non-zero, indicating that the transaction is getting triggered but not opening the queue and processing the messages (I don't have a tool to see when the transaction ran and was relying on the programmer's report). Also, the TRIGINT was 99, not 60 seconds - I'd looked at the wrong queue manager. Fortunately I figured this all out before gathering a trace and sending it to IBM. -Original Message- From: MCSHEFFREY, MICHELLE (AIT) Sent: Tuesday, November 26, 2002 10:05 AM To: 'MQSeries List' Subject:RE: Triggering when CKTI comes up Thanks for everyone's replies. In our case, we are not getting a trigger when CICS and CKTI come up, nor are we getting a trigger after the TRIGINT of 60 seconds have passed when new messages arrive on the trigger queue. If I flip the trigger to N then back to Y, it does generate a trigger, though, so it seems triggering is working in general. I will continue to work with IBM on this and post the solution if turns out to be something interesting. _ Michelle McSheffrey - MQSeries/Tuxedo Support Phone: (312) 669-2059 Pager: (312) 760-2059 _ For emergency support, use WebNotify at http://ebiz.sbc.com/webnotify/ to page the on-call support person. For MQSeries, send the page to the MQSERIES group. For Tuxedo, send the page to the TUXEDO group. Team WEB site: http://mvsha00.sbc.com/appl/cics/index.htm -Original Message- From: Raabe, Stefan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 3:54 AM To: [EMAIL PROTECTED] Subject:AW: Triggering when CKTI comes up No :-) After CKTI startup there is an immediate trigger as explained by others some messages before trigger interval works different. its not a time interval after that queues are scanned if they should be triggered again, its a time interval that has to be expirered after the last trigger message was generated and a new message that is put to the queue. read system application programmers guide for details. regards stefan -Ursprüngliche Nachricht- Von: Chan, Ian M [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 26. November 2002 01:45 An: [EMAIL PROTECTED] Betreff: Re: Triggering when CKTI comes up I think it also depends on the trigger interval. Once the CKTI is up and running, the trigger message will be generated within the trigger interval period. Ian -Original Message- From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 26 November 2002 8:02 AM To: [EMAIL PROTECTED] Subject: Re: Triggering when CKTI comes up One of the times that the QM checks to see if a trigger message should be generated is when the INIT queue IPROCS count goes from 0 to 1. I would think that when CKT1 is brought up, it opens the INIT queue, and if no other app had the init queue open, the IPROCS would then go from 0 to 1. The queue manager would check to see if any queues meet trigger criteria, and would see that your triggered on first queue had more than zero messages on it, and would thus trigger. I tested this behaviour on distributed and it does exactly that. Don't know if CICS would be different. The triggering manual doesn't say so. http://publibfp.boulder.ibm.com/epubs/html/csqzal06/csqzal06tfrm.htm Chapter 14, Section 13.D Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: MCSHEFFREY, MICHELLE (AIT) [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 3:38 PM To: [EMAIL PROTECTED] Subject: Triggering when CKTI comes up If there are messages on a queue that is set to trigger a CICS transaction on FIRST, and the CICS region is down, will a trigger message be generated when the CICS region and CKTI trigger monitor first come up? I thought yes, but IBM support just told me no. I don't want to spend a lot of time looking at the wrong problem (we're getting a trigger when CICS comes up in production but not in test), so please someone tell me which is correct. Thanks. 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:/
Re: Keep Alive vs Heartbeat - What's the diff?
Paul, Keep Alive is configured at the machine level, correct? So all TCP applications on a machine have to agree to a common value? You said HB doesn't apply on SVRCONN channels, but the below paragraph from the Intercommunication handbook says it does? This attribute is valid for sender, cluster-sender, server, receiver, cluster-receiver, and requester channels. Other than on OS/390 and OS/400, it also applies to server-connection and client-connection channels. On these channels, heartbeats flow when a server MCA has issued an MQGET command with the WAIT option on behalf of a client application. So for Blocking Gets, the HB comes into play, but for all other times that an MQClient might be connected, the Keep Alive pulse is what will catch the MQClient dissappearing without disconnecting? The manual says if 2 sides of a channel have different values, the larger is used. Unless one side is ZERO, which means no HB? In that case ZERO trumps the other side? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Paul Clarke [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 12:45 PM To: [EMAIL PROTECTED] Subject: Re: Keep Alive vs Heartbeat - What's the diff? >What is the difference between these two, if any? Seems to me they both >accomplish the same thing (allowing one side of a channel to see that the >network is down and thus being able to go Inactive). The only thing I can >guess is that Keep Alive applies only to TCP while Heartbeat will work for >other transmission protocols as well as TCP. >Was Keep Alive the only thing available at one time, and now is kind of >useless if you have HeartBeat available to you? Peter, There is certainly considerable overlap between the benefits of using Heartbeat and KeepAlive but they are not mutually exclusive. I would always recommend that a customer uses both unless he/she has a good reason not to. A good reason might be that you pay for network packets and you don't want keepalive flows. Having said that both keepalive packets and heartbeat packets will only flow when the channels not doing anything so there is no cost of either if the channel remains active. Heartbeats are useful for all channel types except SVRCONN channels. A SVRCONN channel can not 'heartbeat' to the client between MQI calls because there will be no code at the client ready to respond to the 'heartbeat'. To detect client applications ending without MQDISC it is therefore imperative to use KEEPALIVE on your server machine. Generally speaking Heartbeats are more reliable than KEEPALIVE since they are proactive. In other words they require that a process on the other end of the socket actually responds to the request. KEEPALIVE can give false positives because the sockets may be still alive but the process itself is hung (say in a channel exit). Heartbeat is also more configurable (ie. settable on a channel basis), only zOS allows the KEEPALIVE interval to be set per channel. Heartbeating is negotiable between the two ends of the channel. So if the administrator on the other end has configured no heartbeating the value in your channel definition will be ignored. For this reason I would always use KEEPALIVE as well as a 'last resort' type thing. Generally speaking Heartbeats will detect failures because they are more reliable and more configurable but in some instances we have to fall back and use good old KEEPALIVE. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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
Removal of Messages
I have a message problem that I need to deal with. I have messages that can sit on my queue and get stuck there. I need to write a script that will clear messages that have been sitting on the queue over a period of time, say 100 hours. Unfortunatly my client will not set expiry on the message, so this has to be a script that I write to handle this process. I am a straight Windows NT shop. If anybody has a script that I can use to clear messages meeting this criteria I would greatly appreciate it. Thank you. Michael 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: Win 2000 to AS400
No problem. I have a desktop running Win/2000 and MQ V5.2.1 CSD5, connecting to an AS/400 running MQ V5.2. You'll probably have to reset the message sequence number for sender channel. "Anderson, Lizette T. (RyTull)" To: [EMAIL PROTECTED] Subject: Win 2000 to AS400 Sent by: MQSeries List <[EMAIL PROTECTED] T> 12/02/2002 01:52 PM Please respond to MQSeries List The AS400 group has just upgraded to version 5.2 of MQ. The ip address and possibly the port number has changed. I connect to the AS400 from a Windows 2000 server running version 5.2. Do you know of any problems with version 5.2 for AS/400? I think I only need to change my sending channel definition to the new IP address. Am I correct? Will I need to change the port number as well? I am completely unfamiliar with the AS/400. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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
Win 2000 to AS400
The AS400 group has just upgraded to version 5.2 of MQ. The ip address and possibly the port number has changed. I connect to the AS400 from a Windows 2000 server running version 5.2. Do you know of any problems with version 5.2 for AS/400? I think I only need to change my sending channel definition to the new IP address. Am I correct? Will I need to change the port number as well? I am completely unfamiliar with the AS/400. --- Legal Disclaimer: The information contained in this communication may be confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message and any copy of it from your computer system. Thank you. --- Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
WMQI V2.1 vs. MQSI V2.0.2
I've searched the IBM website for documents comparing these two version, but have found none which directly address the differences. Have I missed something ? Does anyone know of any document which summarizes the differences ? Thanks ! Phil This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of J.P. Morgan Chase & Co., its subsidiaries and affiliates. 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: Keep Alive vs Heartbeat - What's the diff?
>What is the difference between these two, if any? Seems to me they both >accomplish the same thing (allowing one side of a channel to see that the >network is down and thus being able to go Inactive). The only thing I can >guess is that Keep Alive applies only to TCP while Heartbeat will work for >other transmission protocols as well as TCP. >Was Keep Alive the only thing available at one time, and now is kind of >useless if you have HeartBeat available to you? Peter, There is certainly considerable overlap between the benefits of using Heartbeat and KeepAlive but they are not mutually exclusive. I would always recommend that a customer uses both unless he/she has a good reason not to. A good reason might be that you pay for network packets and you don't want keepalive flows. Having said that both keepalive packets and heartbeat packets will only flow when the channels not doing anything so there is no cost of either if the channel remains active. Heartbeats are useful for all channel types except SVRCONN channels. A SVRCONN channel can not 'heartbeat' to the client between MQI calls because there will be no code at the client ready to respond to the 'heartbeat'. To detect client applications ending without MQDISC it is therefore imperative to use KEEPALIVE on your server machine. Generally speaking Heartbeats are more reliable than KEEPALIVE since they are proactive. In other words they require that a process on the other end of the socket actually responds to the request. KEEPALIVE can give false positives because the sockets may be still alive but the process itself is hung (say in a channel exit). Heartbeat is also more configurable (ie. settable on a channel basis), only zOS allows the KEEPALIVE interval to be set per channel. Heartbeating is negotiable between the two ends of the channel. So if the administrator on the other end has configured no heartbeating the value in your channel definition will be ignored. For this reason I would always use KEEPALIVE as well as a 'last resort' type thing. Generally speaking Heartbeats will detect failures because they are more reliable and more configurable but in some instances we have to fall back and use good old KEEPALIVE. Hope this helps, P. Paul G Clarke WebSphere MQ Development IBM Rochester,MN Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Keep Alive vs Heartbeat - What's the diff?
Heartbeat is valid for recievers. The below is from the Intercommunication Handbook. HeartBeat This attribute is valid for sender, cluster-sender, server, receiver, cluster-receiver, and requester channels. Other than on OS/390 and OS/400, it also applies to server-connection and client-connection channels. On these channels, heartbeats flow when a server MCA has issued an MQGET command with the WAIT option on behalf of a client application. Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 -Original Message- From: Paul Meekin [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 11:34 AM To: [EMAIL PROTECTED] Subject: Re: Keep Alive vs Heartbeat - What's the diff? If I remember correctly, Heartbeat only works for Sender channels, keepalive only works for receivers. Fuzzy on the details though. "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> on 02/12/2002 14:59:17 Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Paul Meekin) Subject: Keep Alive vs Heartbeat - What's the diff? What is the difference between these two, if any? Seems to me they both accomplish the same thing (allowing one side of a channel to see that the network is down and thus being able to go Inactive). The only thing I can guess is that Keep Alive applies only to TCP while Heartbeat will work for other transmission protocols as well as TCP. Was Keep Alive the only thing available at one time, and now is kind of useless if you have HeartBeat available to you? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This e-mail is from Energis Communications Ltd, 185 Park Street, London, SE1 9DY, United Kingdom, No: 2630471. This e-mail is confidential to the addressee and may be privileged. The views expressed are personal and do not necessarily reflect those of Energis. If you are not the intended recipient please notify the sender immediately by calling our switchboard on +44 (0) 20 7206 and do not disclose to another person or use, copy or forward all or any of it in any form. 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: New MQ numbering confusing to a point of frustration
Date sent: Mon, 2 Dec 2002 16:45:23 - Send reply to: MQSeries List <[EMAIL PROTECTED]> From: "David C. Partridge" <[EMAIL PROTECTED]> Subject:Re: New MQ numbering confusing to a point of frustration To: [EMAIL PROTECTED] > Mike, > > Are you absolutely sure that MQ5.3.1 does include CSD1. I don't think it > does based on some discussions the other week at Hursley. > > Please could IBM clarify this yes ! AFAK, for windows flavor, 5.3 is the same story than 5.2, ie : - a 5.2 version not certified on Win2000 - a 5.2.1 certified, with CSD 1 included just replace "5.2" by "5.3" and "Win2000" by "WinXP" ;-) ... I will try to double check this with IBM localy. LMD. PS : have you noticed that MQ clients are listed "5.3.1" ?-- Luc-Michel Demey - Consultant indipendant Architecte EAI - Expert MQSeries - +33 6 08 755 655 http://consulting.demey.org/ - [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: New MQ numbering confusing to a point of frustration
The installation of MQ5.3.1 (or whatever IBM is calling it) for Windows/NT indicated that it included CSD01. It also installed a memo.ptf for CSD01. I would certainly agree that the numbering is very confusing. - Bruce Giordano "David C. Partridge" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Sent by: MQSeries List Subject: Re: New MQ numbering confusing to a point of frustration <[EMAIL PROTECTED]> Monday December 2, 2002 11:45 AM Please respond to MQSeries List Mike, Are you absolutely sure that MQ5.3.1 does include CSD1. I don't think it does based on some discussions the other week at Hursley. Please could IBM clarify this Dave 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: LOG ABEND
Mark, I believe you can manually restart the archive offload process. You'll have to identify the archived data sets involved in the offload process that failed. Then, whatever job you used to run the offload process should be updated to point to the archived data sets. Rerun the job. The BSDS should contain the newly created data set name and volser of the tape(s) created. Mark Steely cc: Sent by: Subject: LOG ABEND MQSeries List 12/02/2002 11:13 AM Please respond to MQSeries List We are OS/390 V2.8 and MQ v2.1. During the ARCHIVE offload process one of the tapes received an IO/ERROR, a swap was performed 3 times and was unable to bypass the tape error, the reply to the WTO to swap was no. The MQ region took a SVC dump, but continue to process. How can I restart the offload process or will MQ restart the process on it own? Any help would be appreciated. Thank You Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive 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: AMI and performance
Your loss in performance is about 10%. I was told by an instructor from Hursley at the MQ conference in 2001. I don't know if MQ5.3 can do better. -Original Message- From: Francois van der Merwe [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 7:32 AM To: [EMAIL PROTECTED] Subject: AMI and performance What is the performance hit when you use the AMI? Very small, some, really bad? Francois van der Merwe 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: New MQ numbering confusing to a point of frustration
Mike, Are you absolutely sure that MQ5.3.1 does include CSD1. I don't think it does based on some discussions the other week at Hursley. Please could IBM clarify this Dave 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: Keep Alive vs Heartbeat - What's the diff?
If I remember correctly, Heartbeat only works for Sender channels, keepalive only works for receivers. Fuzzy on the details though. "Potkay, Peter M (PLC, IT)" <[EMAIL PROTECTED]> on 02/12/2002 14:59:17 Please respond to MQSeries List <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Paul Meekin) Subject: Keep Alive vs Heartbeat - What's the diff? What is the difference between these two, if any? Seems to me they both accomplish the same thing (allowing one side of a channel to see that the network is down and thus being able to go Inactive). The only thing I can guess is that Keep Alive applies only to TCP while Heartbeat will work for other transmission protocols as well as TCP. Was Keep Alive the only thing available at one time, and now is kind of useless if you have HeartBeat available to you? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 This e-mail is from Energis Communications Ltd, 185 Park Street, London, SE1 9DY, United Kingdom, No: 2630471. This e-mail is confidential to the addressee and may be privileged. The views expressed are personal and do not necessarily reflect those of Energis. If you are not the intended recipient please notify the sender immediately by calling our switchboard on +44 (0) 20 7206 and do not disclose to another person or use, copy or forward all or any of it in any form. 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: New MQ numbering confusing to a point of frustration
As you can see, they changed the output in 5.3 so it is no longer readable. It doesn't make sense. CSD is applied in this case but you can't tell that from the output because the numbers are nonsense. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com "MCSHEFFREY, MICHELLE (AIT)" <[EMAIL PROTECTED]> wrote: Date Recieved: 12/02/2002 08:08:04 AM To: [EMAIL PROTECTED] cc: Bcc Subject: Re: New MQ numbering confusing to a point of frustration I think that's indicating no CSD has been applied. When a CSD has been applied, the CSD is given in the CMVC level: MQSeries Version: 520 CMVC level: p520-CSD03G BuildType: IKAP - (Production) -Original Message- From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 30, 2002 11:07 AM To: [EMAIL PROTECTED] Subject: New MQ numbering confusing to a point of frustration The output of mqver is disturbing and I think IBM is really doing a poor job at managing this. I installed 5.3.1 on Windows 2000 and Linux and got the same results with mqver. Here's what I get with mqver: Name: WebSphere MQ Version: 530 CMVC level: p000-L021011 BuildType: IKAP - (Production) So like, where does it tell me the CSD level? This command is now documented in the quick beginnings but it does not say what the output means. The other disturbing part is the Windows ptf says it is at CSD01 but the Linux ptf says there are no CSDs applied. Both are 5.3.1. So this indicates the dot 1 means nothing. What is IBM trying to do? If anyone has been able to get an answer on this yet please tell me. I am putting off upgrading to 5.3 because of this glitch with the numbering. How am I to manage what version I am installing if I can't even tell what version it is? My client's IBM sales rep has no idea what this means either. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com
LOG ABEND
We are OS/390 V2.8 and MQ v2.1. During the ARCHIVE offload process one of the tapes received an IO/ERROR, a swap was performed 3 times and was unable to bypass the tape error, the reply to the WTO to swap was no. The MQ region took a SVC dump, but continue to process. How can I restart the offload process or will MQ restart the process on it own? Any help would be appreciated. Thank You Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Re: Keep Alive vs Heartbeat - What's the diff?
As I understand it, heartbeat was not originally available (I think it was available from V5.0 onwards on the distributed platforms). We had less popular platforms (Unixware) where we had older queue managers and the only option available to us was keepalive. Not that it was much use out of the box, the default system-wide keepalive interval seems to be 2 hours on several platforms. We generally reduced this to the 5 minutes default for the HBINT value for MQ5.0+ Regards John Scott Senior Middleware Technical Specialist Argos Ltd > -Original Message- > From: Potkay, Peter M (PLC, IT) [mailto:[EMAIL PROTECTED]] > Sent: 02 December 2002 14:59 > To: [EMAIL PROTECTED] > Subject: Keep Alive vs Heartbeat - What's the diff? > > > What is the difference between these two, if any? Seems to me > they both accomplish the same thing (allowing one side of a > channel to see that the network is down and thus being able > to go Inactive). The only thing I can guess is that Keep > Alive applies only to TCP while Heartbeat will work for other > transmission protocols as well as TCP. > > Was Keep Alive the only thing available at one time, and now > is kind of useless if you have HeartBeat available to you? > > Peter Potkay > IBM MQSeries Certified Specialist, Developer > [EMAIL PROTECTED] X 77906 > > > > 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 ** 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 confidential, and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you are not the intended addressee, any disclosure, reproduction, distribution, dissemination or use of this communication is not authorised. If you have received this message in error, please advise the sender by using your reply facility in youe e-mail software. All messages sent and received by Argos Ltd are monitored for virus, high risk file extensions, and inappropriate content. As a result users should be aware that mail maybe accessed. ** 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: MQSeries CICS Bridge Problem
We've had the same problem with the bridge...you can look up our PMR in
IBMLINK (48401, 487) and request the same patch IBM just gave us.
Scott
- Original Message -
From: "Miller, Dennis" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, November 30, 2002 4:34 PM
Subject: Re: MQSeries CICS Bridge Problem
Can't imagine the bridge would understand a message populated with
WriteUTF. Use MQFMT_STRING and writeString. You might be able to get away
with MQFMT_NONE if you have an EBCDIC client, but I'm not entirely sure. The
better approach is to use MQFMT_STRING after specifying
hello_world.characterSet=mq.cmqccsi_q_mgr.
> -Original Message-
> From: Gary P. Klos [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 27, 2002 11:58 AM
> To: [EMAIL PROTECTED]
> Subject: MQSeries CICS Bridge Problem
>
> I am trying to start a CICS DPL program via the CICS MQSERIES bridge. I
am
> able to do this from a batch cobol program on the mainframe running
> mqseries 5.2. We are running Z/os. However when I do it from a java
> program running as an MQClient I get the following error in the REPLYTO
> queue. CSQC710E MQGET failed,MQCC=1, MQRC=2110. I took the sample java
> program in Websphere MQ Using Java, which does a put and get to a queue.
> It works fine normally. I modified the program to put in a replyto queue
> and the other necessary MQMD fields for the cics bridge. The following is
a
> code snipet.
>
> qMgr.accessQueue("UST2.CICS.BRIDGE.REQUESTQ",openOptions);
> // Define a simple MQSeries message, and write some text in UTF
> format..
> MQMessage hello_world = new MQMessage();
> hello_world.correlationId = MQCI_NEW_SESSION;
> hello_world.replyToQueueManagerName = "UST2";
> hello_world.replyToQueueName = "UST2.CICS.BRIDGE.REPLYQ";
> hello_world.messageId = MQC.MQMI_NONE;
>hello_world.format = MQC.MQFMT_NONE; //also tried
MQFMT_STRING
> // hello_world.writeString(MQDPLTSThi gary);
> hello_world.writeUTF("MQDPLTSThi gary");
> NOTE:MQDPLTST is the CICS DPL program to run.
> I've tried it with writeUTF and writeString and with the format =
> MQFMT_STRING OR NONE. (I'm not using the MQCIH header so I can use NONE or
> String from what I've read).
>
>
> Once I send this message. The DEAD letter queue has the original message I
> sent while the REPLYTO queue has the MQRC=2110.
> What am I missing? Is there some translation I'm missing or conversion?
> I'm running the client on a windows 2000 box.
>
> Once this error occurs anytime I try to put another message to the request
> queue I get the CSQC746E error - Invalid ccsid; 500 excepted 819 received.
> The only way I can stop this is by bouncing the cics adapter. Any help
> with these problems would really be appreciated.
>
> Thanks,
> Gary
>
> 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: MQ and Weblogic
My understanding is that MQ must be used in "bindings mode" to support XA 2PC. That means it MUST be on the same machine as Weblogic (at least for 6.1 and MQ 5.2). If XA 2PC is not necessary, "client mode" can be used without the need to have them both on the same machine. This should be a consideration before moving MQ to a separate machine. There are also a number of restrictions on the Weblogic side to get 2PC to work properly with MQ JMS. Regards, Chris James Kingdon cc: Sent by: Subject: Re: MQ and Weblogic MQSeries List 12/02/02 08:50 AM Please respond to MQSeries List Hi Rob, Just wanted to pick up on: Quigley, Robert wrote: >It may be a more solid solution where such a 2PC >is a true requirement - as MQ doesn't support. > MQ most certainly supports 2PC. Perhaps there's some problem with the integration into Weblogic that you are referring to? Regards, James. 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: New MQ numbering confusing to a point of frustration
I think that's indicating no CSD has been applied. When a CSD has been applied, the CSD is given in the CMVC level: MQSeries Version: 520 CMVC level: p520-CSD03G BuildType: IKAP - (Production) -Original Message- From: Michael F Murphy/AZ/US/MQSolutions [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 30, 2002 11:07 AM To: [EMAIL PROTECTED] Subject: New MQ numbering confusing to a point of frustration The output of mqver is disturbing and I think IBM is really doing a poor job at managing this. I installed 5.3.1 on Windows 2000 and Linux and got the same results with mqver. Here's what I get with mqver: Name: WebSphere MQ Version: 530 CMVC level: p000-L021011 BuildType: IKAP - (Production) So like, where does it tell me the CSD level? This command is now documented in the quick beginnings but it does not say what the output means. The other disturbing part is the Windows ptf says it is at CSD01 but the Linux ptf says there are no CSDs applied. Both are 5.3.1. So this indicates the dot 1 means nothing. What is IBM trying to do? If anyone has been able to get an answer on this yet please tell me. I am putting off upgrading to 5.3 because of this glitch with the numbering. How am I to manage what version I am installing if I can't even tell what version it is? My client's IBM sales rep has no idea what this means either. Mike Murphy Sr. Middleware Consultant MQ Solutions, LLC http://www.mqsolutions.com
Keep Alive vs Heartbeat - What's the diff?
What is the difference between these two, if any? Seems to me they both accomplish the same thing (allowing one side of a channel to see that the network is down and thus being able to go Inactive). The only thing I can guess is that Keep Alive applies only to TCP while Heartbeat will work for other transmission protocols as well as TCP. Was Keep Alive the only thing available at one time, and now is kind of useless if you have HeartBeat available to you? Peter Potkay IBM MQSeries Certified Specialist, Developer [EMAIL PROTECTED] X 77906 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: MVS Page Set Usage
Hi, Please see : http://www.mqseries.net/phpBB2/viewtopic.php? t=5143&highlight=csqi018i Cheers, Jan. > I am trying to size a page set and am puzzled by this: > > I have an application that put approximately 1,000,000+320 byte > persistent messages on an MVS queue. > > When I display page set usage, the page set display shows this: > > CSQI018I (MQSF CSQIDUSE PAGE SET 2 HAS 1002286 DATA PAGES. 987 ARE > UNUSED, 1001299 HOLD PERSISTENT DATA AND 0 HOLD NONPERSISTENT DATA > > Why are so many data pages required to hold 320 bytes (+control > information) messages? > The manual states that MQ tries to put multiple "short" messages into a > data page.. > Any thoughts. > And yes, > only this queue is defined to this storage class and hence this page set... > The message length was set to 320 as verified by browsing messages and > message header > We checked the definitions for this test.. > Any help would be appreciated.. > Thanks > Milt > > > > The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. > > 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 > > -/ /&Jan van Kemenade \&www.cressida.info -\ 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: Difference between MQSeries 5.1 and 5.2???
Please disregard my original post, I did not notice that our API was changed to automatically create the queue if it didn’t already exist. My mistake. --- Robert Martin ([EMAIL PROTECTED]) Design Engineer SISCO Inc, 6605 19 1/2 Mile Road Sterling Heights, MI 48314-1408 Phone : 586-254-0020 (ext 125) Fax : 586-254-0053 -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Srivathsa T.V. Sent: Thursday, November 28, 2002 1:08 AM To: [EMAIL PROTECTED] Subject: Re: Difference between MQSeries 5.1 and 5.2??? Are you saying that the queue did not exist and returned a 2085 error on 5.1. And when you upgraded to 5.2 you were able to put/get messages from the queue ? If you are talking about dynamic queues, then yes you can create a queue during the MQOPEN call. The queue created can be made temporary OR dynamic. I have tested this feature on 5.0(CSD 07) & 5.2 and it works fine. So this should be applicable to 5.1 too. Can you please elaborate on the problem. Are you using dynamic queue creation OR trying to put to a local queue. Regards, Srivathsa -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Martin Sent: Thursday, November 28, 2002 1:27 AM To: [EMAIL PROTECTED] Subject: Difference between MQSeries 5.1 and 5.2??? We upgraded our NT MQSeries server from 5.1 to version 5.2 a few months ago. In the past, if you tried to open a queue that did not exist, you would get an error. Now it appears that the queue is created automatically. We are not sure if we want this type of functionality or not, but I cannot seem to find some configuration parameter to turn it off. Does anyone have any suggestions?
Re: MQ and Weblogic
Hi Rob, Just wanted to pick up on: Quigley, Robert wrote: It may be a more solid solution where such a 2PC is a true requirement - as MQ doesn't support. MQ most certainly supports 2PC. Perhaps there's some problem with the integration into Weblogic that you are referring to? Regards, James. 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: MVS Page Set Usage
Milt, There's a formula in the Admin's Guide that you can use to size the page sets. Based on what your message size is, the MQMD is about the same size as your message. I used Excel to formulate page sizes. If you want, I'll send you a copy. Milton Weinberger To: [EMAIL PROTECTED] Subject: MVS Page Set Usage Sent by: MQSeries List 12/02/2002 09:25 AM Please respond to MQSeries List I am trying to size a page set and am puzzled by this: I have an application that put approximately 1,000,000+320 byte persistent messages on an MVS queue. When I display page set usage, the page set display shows this: CSQI018I (MQSF CSQIDUSE PAGE SET 2 HAS 1002286 DATA PAGES. 987 ARE UNUSED, 1001299 HOLD PERSISTENT DATA AND 0 HOLD NONPERSISTENT DATA Why are so many data pages required to hold 320 bytes (+control information) messages? The manual states that MQ tries to put multiple "short" messages into a data page.. Any thoughts. And yes, only this queue is defined to this storage class and hence this page set... The message length was set to 320 as verified by browsing messages and message header We checked the definitions for this test.. Any help would be appreciated.. Thanks Milt The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. 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: MQ and Weblogic
There is no problem that I've seen running WMQ and Weblogic together. We have MQ 5.2 and WL6.1 running in an weblogic cluster. Weblogic supports services which use JMS, and MQ as the underlying provider. Everything is vanilla JMS, no MQ implementation of anything, just straight spec. We've had no problems w/ this. BEA has a product called "JAM" which basically supports a distributed 2 phase commit between unix and mainframe. Plus, it's bidirectional. We're doing a proof of concept. It may be a more solid solution where such a 2PC is a true requirement - as MQ doesn't support. We're keeping MQ for the truly async stuff, however. The BEA product runs an agent on the mainframe which can connect to or receive connections from distributed systems and manages mainframe resources which participate in the whole resource coordination game. Rob Quigley -Original Message- From: Wesley Shaw [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 9:12 AM To: [EMAIL PROTECTED] Subject: MQ and Weblogic Does anyone have any problems running MQ and Weblogic on the same server using the MQ deployed jar files ? We are running on a Solaris server running MQ 5.2 / CSD02G. We have been running this way for a couple of years. With MQ 5.1, we did have a problem where we had to bounce Weblogic if MQ needed bouncing, but that issue went away with 5.2. Our Weblogic team is saying they do not want to run MQ on their Weblogic server and that BEA has a solution that could replace the MQ need. ( this need is getting DB2 data from MVS) Are there issues or problems anyone knows about ? 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
MVS Page Set Usage
I am trying to size a page set and am puzzled by this: I have an application that put approximately 1,000,000+320 byte persistent messages on an MVS queue. When I display page set usage, the page set display shows this: CSQI018I (MQSF CSQIDUSE PAGE SET 2 HAS 1002286 DATA PAGES. 987 ARE UNUSED, 1001299 HOLD PERSISTENT DATA AND 0 HOLD NONPERSISTENT DATA Why are so many data pages required to hold 320 bytes (+control information) messages? The manual states that MQ tries to put multiple "short" messages into a data page.. Any thoughts. And yes, only this queue is defined to this storage class and hence this page set... The message length was set to 320 as verified by browsing messages and message header We checked the definitions for this test.. Any help would be appreciated.. Thanks Milt The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. 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
MQ and Weblogic
Does anyone have any problems running MQ and Weblogic on the same server using the MQ deployed jar files ? We are running on a Solaris server running MQ 5.2 / CSD02G. We have been running this way for a couple of years. With MQ 5.1, we did have a problem where we had to bounce Weblogic if MQ needed bouncing, but that issue went away with 5.2. Our Weblogic team is saying they do not want to run MQ on their Weblogic server and that BEA has a solution that could replace the MQ need. ( this need is getting DB2 data from MVS) Are there issues or problems anyone knows about ? 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
AMI and performance
What is the performance hit when you use the AMI? Very small, some, really bad? Francois van der Merwe 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: MQSeries and MQSI process names
Title: Message Q, Nice, but I think that Mr. Gurney was looking for the WMQI process names. Regards, John Dawson -Original Message- From: MQSeries [mailto:[EMAIL PROTECTED]] Sent: Thursday, November 28, 2002 8:59 AM To: [EMAIL PROTECTED] Subject: Re: MQSeries and MQSI process names Attached is a list I have had for some time now. HTH Cheers, Q -Original Message- From: MQSeries List [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Gurney Sent: Thursday, November 28, 2002 4:27 AM To: [EMAIL PROTECTED] Subject: MQSeries and MQSI process names In the past a document has been posted on the list describing all of the various MQSeries process names, for all platforms, and a description of what they do. Can someone please repost that document. From memory, I believe that document did not include MQSI processes, if anyone has something similar for MQSI, that would be great too. I tried looking in the listserver archive, but couldn't locate what I am after. Thanks in advance, Matt Gurney
Conclusion of the IBM WebSphere MQ V5.3 Open Beta
With the General Availability of WebSphere MQ V5.3 for iSeries, Linux on Intel, Linux on zSeries and Windows XP on 29 November 2002, the WebSphere MQ V5.3 Open Beta program has now completed. Many thanks to the 2,000+ participants who downloaded the Beta code and provided valuable feedback. The Beta newsgroup ( ibm.software.websphere.mq.beta) will remain in place for future Beta programs but should no longer be used for discussion of the V5.3 products. Instead, please use the normal IBM Service Channel for defect reporting or the WebSphere MQ News Groups (ibm.software.websphere.mq, ibm.software.websphere.mq.programming and ibm.software.websphere.mq.administration) for general discussion. Please remember that the code ceased to function on 30 November 2002 so if you wish to continue using the product you need to purchase a copy! 90-Day Free Trial code of WebSphere MQ for Windows V5.3, WebSphere MQ for Linux on Intel V5.3 and WebSphere MQ for Linux on zSeries V5.3 will be available shortly at www14.software.ibm.com/webapp/download/home.jsp cordiali saluti / mit freundlichen Grüßen / met vriendelijke groet / with best regards / avec mes meilleures salutations / venlig hilsen / cordialmente / atenciosamente The WebSphere MQ Beta Team [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: WMQI Switch node?
Use the RouteToLabel and Label nodes. There is an example in the Using the Control Center manual. You can also check the latest WMQI redbook. Cheers, Manuel Carlosr Rodriguez IBM Certified Specialist - WebSphere MQ > -Mensaje original- > De: Francois van der Merwe [SMTP:[EMAIL PROTECTED]] > Enviado el: Monday, December 02, 2002 11:37 AM > Para: [EMAIL PROTECTED] > Asunto: WMQI Switch node? > > Is there a "switch node" available for WMQI where you would switch on a > value and then take different paths depending on the value? > Thanks > > Francois van der Merwe > > 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
WMQI Switch node?
Is there a "switch node" available for WMQI where you would switch on a value and then take different paths depending on the value? Thanks Francois van der Merwe 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: Problem building C++ application on AIX
And now the explanation of the ins and outs of this problem.
The developer building the application was using IBM VA C++ Version 6. The
MQSeries C++ libraries were built with IBM VA C++ Version 5.
This was reported to IBM, and their response paraphrased from the PMR was:
=== RESPONSE ===
VisualAge C++ V5 uses a different name mangling scheme from that used by V6.
VAC++ V5 mangles each const as a part of type specification, whereas V6 does
not do the same. This may affect the binary compatibility of your objects
unless you use the same scheme with both compilers. In order to enforce
the VAC++ V5 name mangling scheme with V6, you can compile your object with
option -qnamemangling=v5.
The logic behind this design can be found in the C++ standard. According
to the standard (13.1:3), the const type-specifiers for function parameters
at the outermost level (e.g. void f(const ...)), are ignored in the context
of function declaration, definition, and calling. Expression const-ness is
enforced at the compilation level (e.g. the compiler will always detect if
your program attempts to overwrite a const expression, which results in a
compile-time error). Also, const is a type access specifier, and there is
really no need to mangle it into function names when used in the context
described above.
=== END RESPONSE ===
So the moral of this story is: If you want to use V6 of the compiler to
build applications that use the MQSeries C++ libraries, you must use the
option
-qnamemangling=v5
Heaven help anyone who needs to build an application using libraries built
with both V5 and V6 of the compiler.
Dave
-Original Message-
From: David C. Partridge [mailto:[EMAIL PROTECTED]]
Sent: 22 November 2002 15:53
To: MQSeries List
Subject: RE: Problem building C++ application on AIX
The plot thickens ...
The prototype for ImqObj::setOpenOptions in imqobj.h looks like:
ImqBoolean setOpenOptions ( const MQLONG );
and that for ImqCac::read in imqcac.h looks like:
ImqBoolean read ( const size_t, char * & );
and the functions exported by the library match these signatures.
Note that the undefined externs don't include the const modifier.
What's more:
A simple test case with two functions like:
void TestMethod( const long param ) {}
void TestMethod( long param ) {}
Compiles just fine on MS VisualStudio but on AIX using IBM VA C++ 5 this
error is generated:
"impconf.cpp", line 81.6: 1540-0403 (S) "TestMethod(long)" is already
defined.
"impconf.cpp", line 77.6: 1540-0425 (I) "TestMethod" is defined on line 77
of "impconf.cpp".
This looks awfully like the compiler has developed serious "const"
blindness!
Anyone seen or heard of a problem like this with the compiler.
Dave
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: BITSTREAM changes between MQSI version 2.0.2 and 2.1
Hi Kevin, Does the ASBITREAM (is that spelled correctly) provide exactly the same functionality? Is there an efix available to get the BITSREAM functionality working again? Thanks, Kulbir. "Kevin Tobin" <[EMAIL PROTECTED]> Sent by: "MQSeries List" <[EMAIL PROTECTED]> 30-Nov-2002 04:29 Please respond to "MQSeries List" <[EMAIL PROTECTED]> To: MQSERIES cc: Subject: Re: BITSTREAM changes between MQSI version 2.0.2 and 2.1 In WMQI CSD3 the BITSTREAM functionality was broken. I believe this has been addressed and will be corrected in the next release. The ASBITREAM function though not documented yet - does work. If you need further assistance please contact me. Cheers Kevin Kevin Tobin Senior IT Specialist IBM WebSphere Services Asia Pacific Level 9, 601 Pacific Hwy, St Leonards, Sydney NSW 2000 Phone: +61 2 947-88249 Fax: +61 2 947-88467 Mobile 0421-052-812 - International : +61 421-052-812 e-Mail: [EMAIL PROTECTED]
MQSeries and VC7
Hi all, Does anybody know if there is a version of MQSeries (and MQSeries AMI) available that was built in VC7 rather than VC6 for Windows ? I am currently developing an application using VC7. The application is an MQ client. The problem is that since VC7 runtime has a separate environment than the VC6 one, I cannot set any environment variables to MQSeries during runtime (MQENV, MQCCSID, MQ_USER_ID etc). Is there a solution to this ?What about MQSeries support for VC7 which is the current standard development platform for WinXP ? Thanks for your help Guy _ Protect your PC - get McAfee.com VirusScan Online 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: BITSTREAM changes between MQSI version 2.0.2 and 2.1
Look this topic: http://www.mqseries.net/phpBB2/viewtopic.php?t=6536&highlight=pq%2A "There is a regression in WMQIv2.1 CSD03 with the BITSTREAM function. The symptoms match what you have described here in that BITSTREAM(Root) and BITSTREAM(InputRoot) evaluate to X''. There is an efix avaliable for WMQIv2.1 CSD03 on all platforms under the defect (APAR) number PQ66348. Suggest you contact your IBM support team for this." HTH, Tibor > In WMQI CSD3 the BITSTREAM functionality was broken. I believe this has > been addressed and will be corrected in the next release. > The ASBITREAM function though not documented yet - does work. If you need > further assistance please contact me. > Cheers > Kevin > Kevin Tobin > Senior IT Specialist > IBM WebSphere Services Asia Pacific > Level 9, 601 Pacific Hwy, St Leonards, > Sydney NSW 2000 > Phone: +61 2 947-88249 > Fax: +61 2 947-88467 > Mobile0421-052-812 - International : +61 421-052-812 > e-Mail:[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
