Posted: Wed Nov 12, 2008 7:30 am Post subject: More fun with ApplicationID
Acolyte
Joined: 17 Oct 2007 Posts: 67
Following on from my last post , but not related ( I don't think ). This is not a question, just passing on my findings.
The Timer Controls effect the MQMD content of the message on the target queue.
To see for yourself create a flow
MQInput --> Compute --> MQOutput
in the compute node include the following code
CALL CopyEntireMessage;
SET OutputRoot.MQMD.ApplIdentityData = 'abcdefghijklmnop';
Run a message through the flow and you get the correct ApplId in the output.
modify the same flow by introducing timer controls
MQInput --> TimeoutControl
TimeoutNotification --> Compute --> MQOutput
Post a timer message
Do you get the ApplId in the output I'm afraid not
I was in a rush so I've worked around the problem, but just in case someone else is tearing their hair out. If I remember rightly it effects more than just the ApplId of the MQMD.
Looks like this is addressed in 6.1.0.3 ( but I haven't tried it yet). It appears that any input node apart from MQInput effected the content of the output MQMD
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