Author |
Message
|
Vitor |
Posted: Tue Sep 21, 2010 8:36 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqtablet wrote: |
And as far as I know, IBM will not support PCFs in .net. Currently, PCFs are supported only in Java by IBM. |
That's something I didn't know. Bit of a blow to those of us producing PCF messages with C & C++, not to mention all the non-Java monitoring tools that rely on PCF messages for discovery & data gathering......  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Sep 21, 2010 10:03 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
PCF structures are provided for C, COBOL, PL/I, S/390® assembler, Visual Basic.
This from the PCF manual - which actually has references to .NET. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
Back to top |
|
 |
mqtablet |
Posted: Thu Sep 23, 2010 10:31 am Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009 Posts: 71
|
Vitor wrote: |
mqtablet wrote: |
And as far as I know, IBM will not support PCFs in .net. Currently, PCFs are supported only in Java by IBM. |
That's something I didn't know. Bit of a blow to those of us producing PCF messages with C & C++, not to mention all the non-Java monitoring tools that rely on PCF messages for discovery & data gathering......  |
Yes, its true. One of my friend was getting the same issue. He raised a PMR and got response from IBM, stating that, there is no support available for using PCF in WebSphere MQ classes for .net. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Sep 23, 2010 10:44 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqtablet wrote: |
Vitor wrote: |
mqtablet wrote: |
And as far as I know, IBM will not support PCFs in .net. Currently, PCFs are supported only in Java by IBM. |
That's something I didn't know. Bit of a blow to those of us producing PCF messages with C & C++, not to mention all the non-Java monitoring tools that rely on PCF messages for discovery & data gathering......  |
Yes, its true. One of my friend was getting the same issue. He raised a PMR and got response from IBM, stating that, there is no support available for using PCF in WebSphere MQ classes for .net. |
But those of us using C or C++ are still ok? Phew!
Any chance of posting the PMR number for the benefit of other .NET sufferers? The more people who request this be fixed / enhanced / changed the sooner IBM will act. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqtablet |
Posted: Fri Sep 24, 2010 10:30 am Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009 Posts: 71
|
I asked my friend, he works as a contractor for his client. The MQ architect from his client company had raised a PMR. He said he will try to get the PMR number from him.
Will post it here once I get it from him.
Thank you. |
|
Back to top |
|
 |
mvic |
Posted: Fri Sep 24, 2010 11:20 am Post subject: |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
Vitor wrote: |
Any chance of posting the PMR number |
mqtablet wrote: |
Will post it here once I get it from him. |
There is not much point posting a PMR number - they are not published to the internet so cannot be found in a search.
If you need this, talk with your IBM sales team, tell them the business reasons you need it. |
|
Back to top |
|
 |
vinay_s_s |
Posted: Thu Nov 11, 2010 3:32 am Post subject: |
|
|
 Apprentice
Joined: 17 Nov 2008 Posts: 39
|
Yes, even I'm facing a similar issue and found out where exactly the issue is occuring.
In amqmdnet.dll -> In the class PCFParameter and in the Method NextParameter. Below is the code where the issue is occuring.
Code: |
public static PCFParameter NextParameter(MQMessage message)
{
int num = message.ReadInt4();
message.DataOffset -= 4;
switch (num)
{
case 3:
return new MQCFIN(message);
case 4:
return new MQCFST(message);
case 5:
return new MQCFIL(message);
case 6:
return new MQCFSL(message);
}
throw new Exception("Unknown type");
}
|
when this switch case tries to matches 'num', num will have a value of 9 but cases are provided only 3,4,5 and 6. Also this happens only for subscriptions and not for any other MQ object.
I've raised a request with IBM and waitng for response.
Thanks,
Vinay |
|
Back to top |
|
 |
vinay_s_s |
Posted: Mon Nov 15, 2010 8:45 am Post subject: |
|
|
 Apprentice
Joined: 17 Nov 2008 Posts: 39
|
IBM response
Quote: |
Thank you for submitting an MQSeries Requirement.
We have reviewed your requirement and have the following
response:
Recognised- IBM agrees with the request and a solution appears to be a
desirable
objective. A solution, however, may not presently appear feasible or
implementable. No IBM commitment is made or implied as to the
eventual delivery of an acceptable solution.
Thank you for raising this requirement. Currently PCF interface in
WebSphere MQ .NET Client is undocumented and not supported. Hence we are
recognising the need to document and support the PCF interface. But it
should be noted that this "recognise" is not for the one fix our customer
requires but is for the whole of PCF support in WebSphere MQ .NET Clients.
Another attempt could probably be made in the service stream to analyse and
see if it can be fixed under an APAR.
|
|
|
Back to top |
|
 |
mqtablet |
Posted: Thu Apr 05, 2012 2:02 pm Post subject: |
|
|
Acolyte
Joined: 09 Jun 2009 Posts: 71
|
Tried with MQ 7.1 amqmdnet.dll now.
Same issue. 'Unknown Type' (MQCFBS) not handled.  |
|
Back to top |
|
 |
Vitor |
Posted: Fri Apr 06, 2012 4:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqtablet wrote: |
Tried with MQ 7.1 amqmdnet.dll now.
Same issue. 'Unknown Type' (MQCFBS) not handled.  |
Time to add this information to your PMR and / or your enhancement request.
Or the new RFE thing. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|