MQSeries.net :: View topic

wilsonho3 · Posted: Tue Sep 14, 2010 6:39 am Post subject:

Platform window XP

Error when message try to send on publication node. pls help

ESQL on compute node:

CREATE COMPUTE MODULE PUB_SUB_Compute
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
CAll CopyMessageHeaders();
-- CAll CopyEntireMessage()

SET OutputRoot = InputRoot;

CREATE NEXTSIBLING OF OutputRoot.MQMD NAME 'MQRFH2';
SET OutputRoot.MQMD.CodedCharSetId = '1208';
SET OutputRoot.MQMD.Format = 'MQHRF2';

SET OutputRoot.MQRFH2.Version = '2';
SET OutputRoot.MQRFH2.Format = InputRoot.MQMD.Format;
SET OutputRoot.MQRFH2.Encoding= InputRoot.MQMD.Encoding;
SET OutputRoot.MQRFH2.CodedCharSetId = InputRoot.MQMD.CodedCharSet
SET OutputRoot.MQRFH2.Flags = '0';
SET OutputRoot.MQRFH2.NameValueCCSID = '1208';

SET OutputRoot.MQRFH2.psc.Command = 'Publish';
SET OutputRoot.MQRFH2.psc.Topic = 'TiTleName';

END;

CREATE PROCEDURE CopyMessageHeaders() BEGIN
DECLARE I INTEGER 1;
DECLARE J INTEGER;
SET J = CARDINALITY(InputRoot.*[]);
WHILE I < J DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I = I + 1;
END WHILE;
END;

CREATE PROCEDURE CopyEntireMessage() BEGIN
SET OutputRoot = InputRoot;
END;
END MODULE;

trace error :

Timestamps are formatted in local time, 480 minutes past GMT.
Trace written by version ; formatter version 6103
2010-09-13 14:21:01.652292 3476 Information BIP7407I: Publish/Subscribe subscriptions recovery started. Found ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 14:21:01.664271 3476 Information BIP7410I: Publish/Subscribe subscriptions recovery. Recovered ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 14:21:01.666358 3476 Information BIP7033I: Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
2010-09-13 17:14:06.098159 3096 Information BIP7407I: Publish/Subscribe subscriptions recovery started. Found ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:14:06.110117 3096 Information BIP7410I: Publish/Subscribe subscriptions recovery. Recovered ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:14:06.251795 3096 Information BIP7033I: Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
2010-09-13 17:38:21.612266 2080 Information BIP7407I: Publish/Subscribe subscriptions recovery started. Found ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:38:21.696340 2080 Information BIP7410I: Publish/Subscribe subscriptions recovery. Recovered ''5'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:38:21.696733 2080 Information BIP7033I: Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
2010-09-13 17:51:01.841150 4840 Information BIP7407I: Publish/Subscribe subscriptions recovery started. Found ''17'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:51:01.855651 4840 Information BIP7410I: Publish/Subscribe subscriptions recovery. Recovered ''17'' subscriptions.
The Publish/Subscribe broker is recovering subscriptions from the broker's database.
This message is for information only. There should be a matching message to indicate that recovery is complete; if such a message is not produced, then an error has occurred and it may be necessary to restart the broker.
2010-09-13 17:51:01.855865 4840 Information BIP7033I: Publish/Subscribe state recovery completed.
Recovery of the Publish/Subscribe state from the broker's database is complete.
This message is for information only. No action is required.
2010-09-13 17:53:12.559458 4636 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'PUB.MQInput'.
2010-09-13 17:53:12.560007 4636 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'PUB.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2010-09-13 17:53:12.560157 4636 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'PUB.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2010-09-13 17:53:12.560309 4636 UserTrace BIP6061I: Parser type ''MRM'' created on behalf of node 'PUB.MQInput' to handle portion of incoming message of length '232' bytes beginning at offset '364'. Parser type selected based on value ''MRM'' from previous parser.
2010-09-13 17:53:35.029922 4636 UserTrace BIP4007I: Message propagated to 'out' terminal of node 'PUB.Compute'.
2010-09-13 17:53:38.389366 4636 UserTrace BIP7086I: Node 'PUB.Publication.ComIbmPSService': The Publication Node with Subscription Point '''' has received an error code 3008.
The Publication Node with Subscription Point '''' has received an error with code 3008. No response message has been sent as one was not requested.
No user action required.
2010-09-13 17:53:39.996746 4636 Error BIP2628E: Exception condition detected on input node 'PUB.MQInput'.
The input node 'PUB.MQInput' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2010-09-13 17:53:39.996788 4636 RecoverableException BIP2230E: Error detected whilst processing a message in node 'PUB.Publication.ComIbmPSService'.
The message broker detected an error whilst processing a message in node 'PUB.Publication.ComIbmPSService'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2010-09-13 17:53:39.996795 4636 ImbPubSubEngineNode::evaluate , 'caught exception'
2010-09-13 17:53:39.996803 4636 RecoverableException BIP2328E: A value of SQL datatype ''CHARACTER'' encountered when datatype ''INTEGER'' expected.
The value of SQL datatype 'CHARACTER' was encountered, but a value of SQL datatype 'INTEGER' was expected.
This message will be accompanied with others which will give the higher level context for this error. Look at these other messages to determine the root source of the problem.
2010-09-13 17:53:40.997817 4636 Error BIP2648E: Message backed out to a queue; node 'PUB.MQInput'.
Node 'PUB.MQInput' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2010-09-13 17:53:40.999549 4636 UserTrace BIP2638I: The MQ output node 'PUB.MQInput' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2010-09-13 17:53:40.999629 4636 UserTrace BIP2615I: The WebSphere MQ input node 'PUB.MQInput' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.
Threads encountered in this trace:
2080 3096 3476 4636 4840

Ths for help.

w