Author |
Message
|
JimmyJ |
Posted: Thu Apr 17, 2003 2:18 pm Post subject: |
|
|
Newbie
Joined: 17 Apr 2003 Posts: 2
|
Hi
Is this statement (from another thread) also true for the MQ.NET classes?
"Java is a bit special. When you create a connection, a thread is created, dedicated to serializing all MQ Series calls for this connection. This means that you can use the same connection handle in multiple threads, but all the calls to MQ will be serialized (even the MQGET with wait)."
Thanks.
Jimmy |
|
Back to top |
|
 |
smeyer1 |
Posted: Mon Apr 21, 2003 12:24 pm Post subject: Dynamic Connect option |
|
|
 Newbie
Joined: 20 Nov 2002 Posts: 4 Location: Dallas, Texas
|
According to thier documnetation:
public MQQueueManager(MQConnectOptions mqcno)
However, i get an error trying to reference the MQCOnnectOptions
Does anyone know if IBM is monitoring this, or where we can get help on this pak. |
|
Back to top |
|
 |
Gallagher |
Posted: Mon Apr 21, 2003 12:44 pm Post subject: |
|
|
 Newbie
Joined: 15 Apr 2003 Posts: 5 Location: Seattle
|
I don't think IBM is following this thread...when I've contacted their support people (and Neil, the original developer), they've told me all support packs are "as-is" (see below). I've tried to get a hold of Mike Bailey (who is mentioned on the support pack but haven't heard from him)
Unfortunately, our agency has decided to abandon using these classes until they are fully supported by IBM.
Neil's Reply:
---------
Since the technology that I originated as the MQSeries .NET classes were picked up by IBM's development lab and then made available through the Support Pacs, I am afraid I have no involvement anymore. I suggest that you work with your local IBM reps to research the information. Please be aware that the support pac is currently available on an "as-is" basis which means no fromal technical support through IBM.
IBM Support's Reply:
------------------------
The change team reviewed your PMR and made the following update...MA7P, is a Category 2 SupportPac, and is provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels. I would suggest the customer to follow up the same with a email request to the below email address. _________________ -Gallagher |
|
Back to top |
|
 |
Leigh Kendall |
Posted: Mon Apr 21, 2003 4:03 pm Post subject: |
|
|
 Acolyte
Joined: 10 Apr 2003 Posts: 66 Location: Hartford, CT
|
So what's the alternative from a .NET environment if you "need" the support? Use the ActiveX/COM library?
Anyone successfully using the MQ Classes for .NET in a production environment? Anyone using them WITH a transaction coordinator like COM+? _________________ Leigh Kendall |
|
Back to top |
|
 |
Gallagher |
Posted: Mon Apr 21, 2003 4:28 pm Post subject: MA7B Activex support pack withdrawn |
|
|
 Newbie
Joined: 15 Apr 2003 Posts: 5 Location: Seattle
|
Unfortunately, IBM has withdrawn the Activex support pack, so we're building our own COM object in house (see below).
Support Reply:
-----------------
We have a support pac MQSeries Automation Classes for ActiveX that was withdrawn. Another customer was asking when the above support pac will be supported on XP. This support pac was used to create an interface between MQ and Active X Com components. . I will get back to you as soon as I get a reply from L3. . .
For this particular query about MA7B : MQSeries Automation Classes for Active X, the customer has to post a question to the below mentioned
email address: aimpacs@uk.ibm.com _________________ -Gallagher |
|
Back to top |
|
 |
smeyer1 |
Posted: Wed Apr 23, 2003 5:57 am Post subject: MQ Client 5.3 required for .Net Package |
|
|
 Newbie
Joined: 20 Nov 2002 Posts: 4 Location: Dallas, Texas
|
For those unexplained errors on connect (2173 and 2139's), here is what i got back:
The problem your customer is encountering is the default MQCNO used in the WebSphere MQ classes for .Net was MQCNO_CURRENT_VERSION (MQ_VERSION_4).
If your customer is uning a client connection on a MQ Client < v5.3 then the SSL attributes are not supported.
Last edited by smeyer1 on Wed Apr 23, 2003 12:44 pm; edited 2 times in total |
|
Back to top |
|
 |
ping master |
Posted: Wed Apr 23, 2003 12:17 pm Post subject: |
|
|
 Centurion
Joined: 20 Sep 2002 Posts: 116 Location: USA
|
Quote: |
Unfortunately, IBM has withdrawn the Activex support pack, so we're building our own COM object in house (see below).
Support Reply:
-----------------
We have a support pac MQSeries Automation Classes for ActiveX that was withdrawn. Another customer was asking when the above support pac will be supported on XP. This support pac was used to create an interface between MQ and Active X Com components. . I will get back to you as soon as I get a reply from L3. . .
For this particular query about MA7B : MQSeries Automation Classes for Active X, the customer has to post a question to the below mentioned |
Gallaher, I am using the MQSeries Automation Classes for ActiveX and it works great with XP. I was the customer who found the bug in the original dll and IBM has fixed it. I actually have a PRE-production version that works great until IBM sends out the global efix. let me know if you want it.
$PM |
|
Back to top |
|
 |
simon.starkie |
Posted: Sun Apr 27, 2003 8:12 am Post subject: Maybe use the MSMQ-MQ Bridge? |
|
|
Disciple
Joined: 24 Mar 2002 Posts: 180
|
It is indeed unfortunate to see good work, such as the MQSeries .NET Support Pack, fail because of the apparent support policies IBM has. But having provided vendor support for many years, I do understand the underlying reasons.
I have always made sure to appraise my employer of the "as is" nature regarding the support policy for "Support Pac's", particularly when the production environment is involved. My concerns even extended to the MA88 support pack for Java and I am pleased to see this functionality is finally included in the base MQSeries product as of MQSeries MQ 5.3.
Because of these support concerns, I decided not to use the MQSeries .NET support pack, even though it worked well enough to facilitate the "Integration of J2EE and .NET via Message Oriented Middleware" proof of concept I am working on (this is part of an SOA I'm implementing for the Enterprise).
Instead, I decided to use the MSMQ-Bridge, formerly provided by Level 8, now available from Microsoft as part of the Host Integration Server 2000 (HIS). This approach is consistent with my companies current "buy versus build" directive, which requires us to buy COTS rather than develop proprietery solutions in-house.
I am pleased to report that, so far, the MSMQ-Bridge poc looks very promising and it appears that it will achieve my objective - integrating J2EE and .NET via MOM using MQSeries and MSMQ.
The good news about this approach, for me, is the fact that I don't have to get into lengthy debates with either the .NET folks or the J2EE folks to achieve any particular integration. If they can get or put a message from or to either an MSMQ or MQSeries queue, then I can accomplish my integration goal.
Perhaps the best news is fact that the MSMQ Bridge is fully supported by Microsoft.
Hope that helps.  |
|
Back to top |
|
 |
rosireddyr |
Posted: Wed Apr 30, 2003 5:54 am Post subject: How to create queue programatically in C# |
|
|
Newbie
Joined: 30 Apr 2003 Posts: 2
|
Hi Kolban
I am using Dotnet Component to access MQSeries. Its very easy to access MQSEries now.
Now I need some help.
Please tell how to create queue, channel and connection programatically.
If you have any tutorial please send it to me at rosireddyr@yahoo.com.
Thanks
Rosi |
|
Back to top |
|
 |
bduncan |
Posted: Wed Apr 30, 2003 9:01 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
Rosi you'll need to use the PCF interface to achieve this... _________________ Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
Back to top |
|
 |
Gallagher |
Posted: Wed Apr 30, 2003 11:04 am Post subject: Open Source |
|
|
 Newbie
Joined: 15 Apr 2003 Posts: 5 Location: Seattle
|
Ping Master...thanks offering, yes I'd like to see your patch and source (see messages in your inbox).
BTW, is MA7P open source? If so, where can we download it (I only get the compiled binaries off the support pack page). _________________ -Gallagher |
|
Back to top |
|
 |
rosireddyr |
Posted: Fri May 02, 2003 1:39 am Post subject: Create queue by using Kolban.net dll |
|
|
Newbie
Joined: 30 Apr 2003 Posts: 2
|
Hi bduncan
Thanks for your reply.
Can you send me one example to create queue and queuemanager by using Koban.net dll. I am unable to create. I am eagerly waiting for your reply.
Thanks in advance
Rosi |
|
Back to top |
|
 |
bduncan |
Posted: Fri May 02, 2003 9:51 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001 Posts: 1554 Location: Silicon Valley
|
|
Back to top |
|
 |
LovenDOTNET |
Posted: Mon May 05, 2003 9:14 am Post subject: When to use QMgr_Handle.Close() or QMgr_Handle.Disconnect()? |
|
|
Newbie
Joined: 26 Mar 2003 Posts: 2 Location: Raleigh NC - USA
|
Some code....... for put....
But which do I used in the 2nd to the last Finally...??
QMgr_Handle.Close()
' or
QMgr_Handle.Disconnect()
.......Thanks for any comments....
'======================
Public Function PutMessage(ByVal TheNameofTheQueue As String, ByVal TheNameofTheQueueMgr As String, ByVal TheMessage As String) As Boolean
' ...Declarations
Dim QMgr_Handle As MQQueueManager '* MQQueueManager instance
Dim Queue_Handle As MQQueue '* MQQueue instance
Dim Message_Handle As MQMessage '* MQMessage instance
Dim PutMessageOptions_Handle As MQPutMessageOptions '* MQPutMessageOptions instance
Dim queueName As String '* Name of queue to use
Dim msgLen As Integer '* Message length
Dim message As String '* Message buffer
Dim PlaceHolderForText As String
Try
If (Not TheNameofTheQueue = "") And (Not TheNameofTheQueueMgr = "") Then
' ...Queue name, Queue Manager name provided.......
queueName = TheNameofTheQueue
' ...InitializeComponent with the New
QMgr_Handle = New MQQueueManager(TheNameofTheQueueMgr)
Else
' ...Return a false to the Boolen
Return False
Exit Function
End If
Catch mqe As IBM.WMQ.MQException
' ...stop if failed
' ...create of MQQueueManager ended with mqe.Message
Windows_Event_Log.WriteEntry(mqe.Source.ToString & " " & mqe.TargetSite.Name & " " & mqe.Message, EventLogEntryType.Error, 15009)
Return False
Catch EE As System.Exception
Windows_Event_Log.WriteEntry(EE.Source.ToString & " " & EE.TargetSite.Name & " " & EE.Message, EventLogEntryType.Error, 15009)
End Try
' ...Try to open the queue
Try
' ...open queue for output but not if MQM stopping
Queue_Handle = QMgr_Handle.AccessQueue(queueName, MQC.MQOO_OUTPUT + MQC.MQOO_FAIL_IF_QUIESCING)
PlaceHolderForText = QMgr_Handle.ConnectionStatus()
Windows_Event_Log.WriteEntry("The current QMgr_Handle.ConnectionStatus is " & PlaceHolderForText, EventLogEntryType.Information, 15010)
Catch mqe As IBM.WMQ.MQException
' ...stop if failed
' ...MQQueueManager::AccessQueue ended with mqe.Message
Windows_Event_Log.WriteEntry(mqe.Source.ToString & " " & mqe.TargetSite.Name & " " & mqe.Message, EventLogEntryType.Error, 15009)
Return False
End Try
message = ""
message = TheMessage
msgLen = 0
msgLen = message.Length
If (msgLen > 0) Then
Try
' ...Initialize Component with the New
Message_Handle = New MQMessage()
Message_Handle.WriteString(message)
Message_Handle.Format = MQC.MQFMT_STRING
' ...InitializeComponent with the New
PutMessageOptions_Handle = New MQPutMessageOptions()
' ...put message to the message queue
Queue_Handle.Put(Message_Handle, PutMessageOptions_Handle)
' ...Closed the Initialize Component of Queue_Handle
Queue_Handle.Close()
' ... Return True to the Boolen
Return True
Catch mqe As MQException
' ...report the error
' ...MQQueue::Put ended with mqe.Message
Windows_Event_Log.WriteEntry(mqe.Source.ToString & " " & mqe.TargetSite.Name & " " & mqe.Message, EventLogEntryType.Error, 15009)
Return False
Finally
End Try
Else
Try
message = "No Message Details Provided"
' ...Initialize Component with the New
Message_Handle = New MQMessage()
Message_Handle.WriteString(message)
Message_Handle.Format = MQC.MQFMT_STRING
' ...InitializeComponent with the New
PutMessageOptions_Handle = New MQPutMessageOptions()
' ...put message to the message queue
Queue_Handle.Put(Message_Handle, PutMessageOptions_Handle)
' ...Closed the Initialize Component of Queue_Handle
Queue_Handle.Close()
' ... Return True to the Boolen
Return True
Catch mqe As IBM.WMQ.MQException
' ...report the error
' ...MQQueue::Put ended with mqe.Message
Windows_Event_Log.WriteEntry(mqe.Source.ToString & " " & mqe.TargetSite.Name & " " & mqe.Message, EventLogEntryType.Error, 15009)
Return False
Finally
'==========================================================
'==========================================================
QMgr_Handle.Close()
'or
QMgr_Handle.Disconnect()
'==========================================================
'==========================================================
End Try
End If
QMgr_Handle = Nothing
Queue_Handle = Nothing
Message_Handle = Nothing
PutMessageOptions_Handle = Nothing
queueName = Nothing
msgLen = Nothing
message = Nothing
Catch mqe As IBM.WMQ.MQException
' ...report the error
' ...MQQueue::Put ended with mqe.Message
Windows_Event_Log.WriteEntry(mqe.Source.ToString & " " & mqe.TargetSite.Name & " " & mqe.Message, EventLogEntryType.Error, 15009)
'Return (mqe.Reason)
Return False
Catch EE As System.Exception
Windows_Event_Log.WriteEntry(EE.Source.ToString & " " & EE.TargetSite.Name & " " & EE.Message, EventLogEntryType.Error, 15009)
Finally
'Windows_Event_Log.WriteEntry("Ending the PutMessage Function", EventLogEntryType.SuccessAudit, 15010)
GC.WaitForPendingFinalizers()
GC.Collect()
End Try
End Function _________________ Brent Morris
MQ Series Admin
Raleigh NC - USA |
|
Back to top |
|
 |
Leigh Kendall |
Posted: Sat May 10, 2003 7:20 pm Post subject: |
|
|
 Acolyte
Joined: 10 Apr 2003 Posts: 66 Location: Hartford, CT
|
Is it stated anywhere in the MA7P doc or samples that amqmdnet.dll is the assembly that needs to be referenced for the MQ classes?
Took me a little while to find it. Did I miss it mentioned somewhere? If so, it's not to explicit as to what the assembly and namespace is.
TIA, _________________ Leigh Kendall |
|
Back to top |
|
 |
|