Author |
Message
|
Lisa |
Posted: Thu Jul 25, 2002 5:57 pm Post subject: Casting Error |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
All,
I'm getting the following error.
BIP2521E (&1, &2) : Error casting a value from &3
to &4.
Explanation: An error occurred when casting a value
of data type &3 to a value of data type &4.
User Response: Subsequent messages will indicate the
context of the error.
How can I find the problem statement in my compute node?
Do you need more information? I can post additional information if needed.
The EXCEPTIONLIST shows the following RecoverableException:
Function: IbmComputeNode::evaluate
Type: ComIbmComputeNode
Function: SqlTypeCast::evaluate
Insert
Type: 2
Text: 96
Insert
Type: 2
Text: 14
Insert
Type: 5
Text: BLOB
Insert
Type: 5
Text: CHARACTER
RecoverableException:
Text: Unconvertable character
Serverity: 3
Number: 2135
Insert
Type: 5
Text: a0
Insert
Type: 5
Text: c3e2d840d4d8c4f1404040 (etc..)
Insert
Type: 2
Text: 1051
Thanks, Lisa |
|
Back to top |
|
 |
kirani |
Posted: Thu Jul 25, 2002 6:31 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
There is a casting error in your compute node at line number 96 and column number 14.
Hope this helps. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
Lisa |
Posted: Mon Jul 29, 2002 6:32 am Post subject: Casting Error - MQMD Mqsgid |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
All,
The error occurs on the following statement within my Compute Node:
This message flow is running on HP-Unix 11.0 and the data is coming from the mainframe.
Once the MQMD messageid is casted, it's moved into our standard copybook header.
DECLARE MSG_ID CHAR;
SET MSG_ID = CAST(InputRoot.MQMD.MsgId AS CHAR CCSID InputRoot.MQMD.CodedCharSetId);
SET "OutputRoot"."MRM"."e_LOGCHeader"."LOGC_MQMD_MSGID_I" = MSG_ID; |
|
Back to top |
|
 |
kirani |
Posted: Mon Jul 29, 2002 7:53 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
what is the Logical and Physical type defined for field "e_LOGCHeader"."LOGC_MQMD_MSGID_I" into MRM? Is it BINARY or STRING? _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
Lisa |
Posted: Mon Jul 29, 2002 8:02 am Post subject: Casting Error |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
Kirani,
Question:
What is the Logical and Physical type defined for field "e_LOGCHeader"."LOGC_MQMD_MSGID_I" into MRM? Is it BINARY or STRING?
Response:
"e_LOGCHeader"."LOGC_MQMD_MSGID_I
Physical Type = Fixed Length String
Length Count = 24 |
|
Back to top |
|
 |
kirani |
Posted: Mon Jul 29, 2002 8:40 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
The error you are getting has something to do with a particular character (X'A0') not being supported in codepage 1051.
I wouldn't use CAST function to convert MQMD.MsgId TO CHAR because it is a BINARY field. I would define MRM field as BINARY of length 48 to store Msg-id. After I modify MRM field, I will be able to use simple ESQL to assign value to it:
SET "OutputRoot"."MRM"."e_LOGCHeader"."LOGC_MQMD_MSGID_I" = InputRoot.MQMD.MsgId; _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
Lisa |
Posted: Mon Jul 29, 2002 10:14 am Post subject: Casting Error |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
Kirani,
The copybook cannot be changed. It's part of our firm wide logging application on the mainframe.
Thanks, Lisa |
|
Back to top |
|
 |
kirani |
Posted: Mon Jul 29, 2002 10:32 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
Which application is consuming the output message generated by the above message flow? Is it only for logging or is there any process that operates on this data? How difficult it will be to change the field to X(4 ?
Occasionally, you will hit this error If the MQMD.Msgid is auto generated by the queue manager. You could think of generating MQMD.MsgId, which will guarantee the uniqueness of the MsgId and it will not contain any "special character". _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
Lisa |
Posted: Mon Jul 29, 2002 10:42 am Post subject: Casting Error |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
Kirani,
At this point in time, changing the msgid field to PIC X(4 is not an option.
The messages are coming from our mainframe application, transformed into S.W.I.F.T. format, logged and sent to our trading partner.
By the way, if the msgId contains 'CSQ or AMQ, queue mgr. name and timestamp', where are these odd characters coming from?
Thanks, Lisa |
|
Back to top |
|
 |
kirani |
Posted: Mon Jul 29, 2002 12:15 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
Probably the timestamp is formatted/converted into "odd" characters before it becomes a part of generated MsgId. _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
Lisa |
Posted: Mon Jul 29, 2002 3:59 pm Post subject: Casting Error |
|
|
Master
Joined: 07 Jun 2002 Posts: 287 Location: NJ
|
Thanks for your help.
I will try generating my own msgid or change the MRM physical format to Binary with a length of 24.
Lisa |
|
Back to top |
|
 |
kirani |
Posted: Mon Jul 29, 2002 4:42 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Lisa,
The length should be 48 not 24! _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
|