Title: Message
Peter
 
The representative from WebSphere MQ SupportPac (TM) Systems is out of the office the rest of this week since she is just part time.  Maybe someone else from that organization who monitors this LISTSERV can provide the time frames.
 
Possible REXX Alternatives I can think of are:
 
IBM Netview or Tivoli
BMC Mainview with AutoOperator
Candle's AFOPER

Thanks
    Frank

-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bright, Frank
Sent: Tuesday, November 11, 2003 11:38 AM
To: [EMAIL PROTECTED]
Subject: Re: Supportpac MA19:Rexx Interface to Issue Commands to MQSeries for MVS/ESA V2.0

Peter
 
I will try to find out the time frames.  As soon as I know, I will post it.
 
Thanks
    Frank
-----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Moir, Peter
Sent: Tuesday, November 11, 2003 8:43 AM
To: [EMAIL PROTECTED]
Subject: Re: Supportpac MA19:Rexx Interface to Issue Commands to MQSeries for MVS/ESA V2.0

 
This is a bit of a disaster for us.....do you know when ?......is there a IBM announcement anywhere ?
 
When it goes, is there any alternative to enable you to use MQSeries in REXX on the mainframe ?
 
 
 -----Original Message-----
From: Bright, Frank [mailto:[EMAIL PROTECTED]
Sent: 11 November 2003 12:22
To: [EMAIL PROTECTED]
Subject: Re: Supportpac MA19:Rexx Interface to Issue Commands to MQSeries for MVS/ESA V2.0

I have just learned that MA19 SupportPac will be with drawn as an offering by IBM.  I believe the same goes for MA18.  If you put any reliance on these SupportPac, you should start making plans for their replacement.

Thanks
    Frank

 -----Original Message-----
From: MQSeries List [mailto:[EMAIL PROTECTED] On Behalf Of Bright, Frank
Sent: Monday, November 10, 2003 2:53 PM
To: [EMAIL PROTECTED]
Subject: Supportpac MA19:Rexx Interface to Issue Commands to MQSeries for MVS/ESA V2.0

I have been using the MA19 support with some good results, however, after a recent test, I have been getting a 2033 for the command responses.  The responses wind up in the DEAD.LETTER for dynamic queue RXMQVC.* for reason code 2085.  I don't understand what may be wrong since I am passing in the timeout value of 15 seconds.  The time it takes to get a 2033 is around 2 seconds.  The trace for CMD shows using this interface using  the .TO variable is set to 15 with a length of 2.  Can anyone offer a suggestion on how to debug this?
 

Thanks
    Frank


This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.


This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.


This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.


This e-mail message and any attachments contain confidential information from Medco Health Solutions, Inc. If you are not the intended recipient, you are hereby notified that disclosure, printing, copying, distribution, or the taking of any action in reliance on the contents of this electronic information is strictly prohibited. If you have received this e-mail message in error, please immediately notify the sender by reply message and then delete the electronic message and any attachments.

Reply via email to