Again: the application is very simple and quite old, it is only capable of issuing MQGET. It is coded by our in-house programmers and I know it inside-out. And it works on another Queue Manager and host, where it reads messages from Local Queues as they come sent from Broker.
We have only subscriptions created by MQSC using DEF SUB command - I know that for sure because I'm the only one who knows how to do that here.
Publication, on the other hand, is done by my simple script:
while [ $rc -ne 0 ]
do
/var/mqm/bin/q -I $queue -Ts:"STREAM."$string"/"$string -p20
rc=$?
if [ $rc -ne 0 ]
then
sleep 10
fi
done
It is meant to be started by a Trigger Monitor only.
As you can see the name of receiving queue identifies the TOPICSTR.
I'm 100% sure no application can create subscription here. No application runs on the same host where our Broker QM is running and there are no Client connections configured (our applications do not use Client connection at all actually, and are only able to run on the same host where QM is started - we have lot's of Queue Managers...)
Here is sample SUB definiton - to show the way I define them:
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum