Author |
Message
|
malachid |
Posted: Tue Dec 02, 2003 12:47 pm Post subject: C#, PCF, etc. |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 3 Location: Oregon
|
We currently are talking to Websphere via C (not C++) and Java. I have been testing the C# interface, and am having a few issues.
First, I was curious if there are plans to finish the interface? I saw references to it being provided as-is, and sent PartnerWorld an email asking what the plans were for the product. Unfortunately, they just stated that they couldn't talk to me unless I paid for tech support. Does anyone know if this interface will ever be finished? As of right now, there are many constants missing (CMQCFC.MQIA_*), methods not implemented (PCFMessage.ToString), etc.
Second, has anyone determined the best method of multi-threading the use of this library? It appears that the only was we have been able to provide multi-threaded access was to have it maintain its own thread (with Suspend and Resume) and not call any of the functionality directly, but to go through an Event dispatcher.
Third, has anyone been able to get any PCF commands (other than Neil's ListQueues) to work? I can't even seem to find out the current message depth (ie: number of messages in a queue) without it throwing errors about invalid parameters.
Fourth, I understood Neil to say that he designed it around the Java interface... I didn't see any sort of event-based notification of incoming messages (which Java is really good for). Is there plans to add this functionality?
Thanks for any assistance or information you might be able to provide.
Malachi |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Dec 02, 2003 1:31 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Neil's .Net framework has been included in an updated form in CSD5/FixPack 5 of Websphere MQ 5.3 for Windows.
But there are still, apparently, some issues with PCF support.
I'd suggest you download CSD05 and look at the included documentation. Although keep in mind that the documentation is wrong in at least one point, the version included with CSD05 requires the .Net Framework 1.1 even though the documentation says it only needs 1.03something.
There has been much discussion here about the capabilities and limitations of the .Net interface. It would probably be worth your time to use the Search button for '.Net' and see what else has been said. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
JasonE |
Posted: Tue Dec 02, 2003 3:54 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Just to reiterate, that the PCF support in csd05 is better, but still broken. Its not documented either yet, so its support state is 'interesting', but the intention is never to supply a partially working interface.
There is also a testfix available (not sure if its an apar yet, but as far as I know it'll be in the next fixpack, but dont quote me) which should fix the functionality. However as far as I know, none of the pcf constants were missing (I havent looked so dont shoot me) - Any obvious ones spring to mind so I can check? [Have you checked the csd05 version though as it might be better anyway]. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Tue Dec 02, 2003 4:20 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Jason, what are the plans over there to fix all these little quirks in the CSD05 MQ code for .NET? Will it be fixed in CSD06? If yes, do you have a date for that? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
JasonE |
Posted: Wed Dec 03, 2003 2:11 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Depends on the 'quirks' you mean. Its business as usual wrt to the .net code - Someone reports a bug and we fix it, take an apar and add the apar to the list of things requiring shipping. Depending on cut off dates depends on whether it goes into the next immediate fixpack or not.
Fixpacks are shipping about once every 3 or 4 months, so you can guess when the next one might be out but any date i said would probably be missed! Remember we will delay a fixpack if we find regressions in it, which is one reason we dont publish and stick to dates.
Aside from the PCF issue, what ones spring to mind?
FYI The 4mb one: http://www-1.ibm.com/support/docview.wss?rs=0&q=IC38370&uid=swg1IC38370&loc=en_GB&cs=utf-8&lang= |
|
Back to top |
|
 |
PeterPotkay |
Posted: Wed Dec 03, 2003 5:31 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
|
Back to top |
|
 |
JasonE |
Posted: Wed Dec 03, 2003 6:12 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Yes - I did raise this with the developer and we had some discussions about it, but we have not had a pmr in so there is no formal problem report as such (I have to keep emphasizing that participation in forums is effectively in my 'own time', and we cannot provide formal support this way). I'll ask again... |
|
Back to top |
|
 |
malachid |
Posted: Wed Dec 03, 2003 7:59 am Post subject: missing constants |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 3 Location: Oregon
|
JasonE wrote: |
Just to reiterate, that the PCF support in csd05 is better, but still broken. Its not documented either yet, so its support state is 'interesting', but the intention is never to supply a partially working interface.
There is also a testfix available (not sure if its an apar yet, but as far as I know it'll be in the next fixpack, but dont quote me) which should fix the functionality. However as far as I know, none of the pcf constants were missing (I havent looked so dont shoot me) - Any obvious ones spring to mind so I can check? [Have you checked the csd05 version though as it might be better anyway]. |
It appears that we are using the csd05... One of the missing constants is CMQCFC.MQIA_CURRENT_Q_DEPTH -- I am trying to modify the ListQueues example to show me queue depth, but that parameter doesn't exist. In fact, MQIA_* are all missing.
Malachi |
|
Back to top |
|
 |
JasonE |
Posted: Wed Dec 03, 2003 8:42 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Its MQC.MQIA_*
(And you might need using IBM.WMQ.PCF;) |
|
Back to top |
|
 |
malachid |
Posted: Wed Dec 03, 2003 8:48 am Post subject: Queue Depth |
|
|
Newbie
Joined: 02 Dec 2003 Posts: 3 Location: Oregon
|
JasonE wrote: |
Its MQC.MQIA_*
(And you might need using IBM.WMQ.PCF;) |
That definitely explains why I didn't find it. I was doing the 'using', but I was trying to replace CMQCFC.MQCACF_Q_NAMES from the example with CMQCFC.MQIA_CURRENT_Q_DEPTH. Now that I switched it to MQC.MQIA_CURRENT_Q_DEPTH, I can at least compile with the constant -- thought it still reports the parameter invalid:
Exception: CompCode: 2, Reason: 3033
from doing:
string [] depths = responses[0].GetStringListParameterValue(MQC.MQIA_CURRENT_Q_DEPTH);
Malachi |
|
Back to top |
|
 |
JasonE |
Posted: Wed Dec 03, 2003 9:13 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003 Posts: 1220 Location: Hursley
|
Please see the info I just 'PM'ed you - its an example of what you are trying to do but (unhelpfully ) may not work at the code level you are running. |
|
Back to top |
|
 |
|