Comment 7 for bug 730162

Thanks! Will check those APARS. I'm on 7.0.1.3. Will also make sure I checked in all the code as soon as I am home.

>I did an interesting experiment - right before calling MQSUBRQ in pymqe_MQSUBRQ, I added /yet another/ hardcoded >subscription for the topic string, that is I discarded the previous subscription, made another one and all of a sudden the call to >MQSUBRQ would start working.

What? That's strange. But why only in python then. I do exactly in "c" what I do in python but get different results. I will once again check and double check the VSPtr fields at all levels and I will check the subscription handle.

The thing about using topicString, topicName and subName heavily depends on the subscription options you sepcify. If your subscription is unmanaged you always have to supply a subName. The use of topicName and/or topicString is as documented in the MQ manual.

Thanks for your help. I'm going to look at this with new eyes after your experiment.