ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MRM TO XML DEPLOYMENT ERROR

Post new topic  Reply to topic
 MRM TO XML DEPLOYMENT ERROR « View previous topic :: View next topic » 
Author Message
bhavika
PostPosted: Tue Dec 06, 2005 7:50 pm    Post subject: MRM TO XML DEPLOYMENT ERROR Reply with quote

Newbie

Joined: 06 Dec 2005
Posts: 2
i m a newbie in this field. i want to transform my MRM to XML . i have created a mess set PHXLG_ACTIVATECHK and message named ACT_CHK_REPLY. I have set Identifier as ACT_CHK_REPLY andcompleted rest of the steps. when i deploy i get message saying "correlation name not valid". my code in the compute name is as follows.

DECLARE C INTEGER;
SET C = CARDINALITY(InputRoot.*[]);
DECLARE I INTEGER;
SET I = 1;
WHILE I < C DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I=I+1;
END WHILE;

-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.
SET OutputRoot.Properties.MessageSet = 'E70LLCS07C001';
SET OutputRoot.Properties.MessageType = 'ACT_CHK_REPLY';
-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.

-- Setting Header Properties

SET OutputRoot.Properties.MessageDomain = 'XML' ;
--SET OutputRoot.Properties.MessageFormat = 'CWF' ;

-- Convert from ASCII to EBCDIC

SET OutputRoot.Properties.CodedCharSetId = 819 ;
SET OutputRoot.MQMD.CodedCharSetId = 819 ;
SET OutputRoot.MQMD.Encoding = 273;
SET OutputRoot.MQMD.Format = 'MQFMT_STRING' ;

SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."EncodingTypeCd"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."CharacterSetCd"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MessageId"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."CorrelationId"= "";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."OriginatorNm"="CAS";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."ServiceNm"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."SrvcMajVersionNbr"="1";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."SrvcMinVersionNbr"="0";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgPatternTypeCd"="RR";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgTypeCd"="O";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgSrvcDomainNm"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgSetId"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgNm"="ACT_CHK_REPLY";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgFormatCd"="XML";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgMajVersionNbr"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgMinVersionNbr"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgPersistenceTypeCd"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgPriorityNbr"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgExpireTimeQty"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgPutDt"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgPutTime"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgSLATimeQty"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."SrvcResponseTimeQty"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."ProcessControlId"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."SLAMode"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."ReportOptionCd"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MQMsgTypeCd"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."ReplyToQNm"="";
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."ReplyToQMgrNm"="";


SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."DomainId"="1";
SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."RealmId"="1";

SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."SessionId"="1";

SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."GUID"="1";
SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."TokenCreationTs"="1";
SET "OutputRoot"."XML"."Envelope"."Header"."SecurityBlk"."HTTPInfoBlk"."TokenExpirationTs"="1";




-- Map Output Fields
SET "OutputRoot"."XML"."Envelope"."Body"."Response"."CASChkActRespInfo"."CustCardCustCardAcctNbr" = "InputBody"."ACT_CHK_PLST_NUM_D";
SET "OutputRoot"."XML"."Envelope"."Body"."Response"."CASChkActRespInfo"."ChkActTransRespCd" = "InputBody"."ACT_CHK_RESPONSE_CODE"="00";


can someone help me out.....
Back to top
View user's profile Send private message
wooda
PostPosted: Wed Dec 07, 2005 4:38 am    Post subject: Reply with quote

Master

Joined: 21 Nov 2003
Posts: 265
Location: UK
Here are some of the issues with your ESQL.

When entering string literals in ESQL use single quotes. Double quotes are used for correlation names. This is probably the source of your error.

eg.

Code:
SET OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgNm"="ACT_CHK_REPLY";


should be

Code:
SET "OutputRoot"."XML"."Envelope"."Header"."TransactionBlk"."MsgNm"='ACT_CHK_REPLY';


You appear to be confused between whether you are using the MRM domain or XML domain.

You set OutputRoot.Properties.MessageSet and MessageType (suggesting you want to use the MRM domain.)
Then you try to set OutputRoot.Properties.MessageDomain = 'XML';
which is invalid as OutputRoot.Properties.MessageDomain is not a valid correlation name (another cause of your error)
And then your ESQL is using the XML domain (OutputRoot.XML etc.)

You also have the following which is clearly wrong. Not sure what you are trying to acheive here with the ="00" on the end.


Code:
SET "OutputRoot"."XML"."Envelope"."Body"."Response"."CASChkActRespInfo"."ChkActTransRespCd" = "InputBody"."ACT_CHK_RESPONSE_CODE"="00";


[/b][/code]
Back to top
View user's profile Send private message
wooda
PostPosted: Wed Dec 07, 2005 4:46 am    Post subject: Reply with quote

Master

Joined: 21 Nov 2003
Posts: 265
Location: UK
I suggest you go back to basics and first understand the difference between MRM domain and XML domain and decide which you want to use for your output XML.
Back to top
View user's profile Send private message
JT
PostPosted: Wed Dec 07, 2005 6:50 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
.......also, where you may have multiple lines of code in error, as wooda pointed out, the error messages that are produced as a reult of the deployment, will point you in the general direction of the error by identifying a line & column number in the ESQL code.

Quote:
BIP2432E: (.REDEFINE_LOGIC.Main, 8.21) : The correlation name 'JT' is not valid. Those in scope are: , Environment, InputLocalEnvironment, OutputLocalEnvironment, InputRoot, InputBody, InputProperties, OutputRoot, InputExceptionList, OutputExceptionList, InputDestinationList, OutputDestinationList, MyOutput.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » MRM TO XML DEPLOYMENT ERROR
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.