| Author |
Message
|
| yshakraj |
 Posted: Sat Jul 28, 2012 8:20 am Post subject: facing an error whilst parsing against cobol copy messageset |
 |
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
Hi,
I've created two message sets , output is a cobol copy,few of the fields are ebcidic values and rest are packed decimal fields .While parsing against output message set i'm getting error
'CPI InputData Too Long'
Insert Type:INTEGER:5
Text:CHARACTER:decimal
Insert Type:INTEGER:5
Text:CHARACTER:packed decimal
Insert Type:INTEGER:2
Text:CHARACTER:5
Insert Type:INTEGER:5
Text:CHARACTER:4413
 
so pls help me fix this one |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat Jul 28, 2012 8:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
This means that the model represented by the message set had parsed everything it needed to in order to be complete, but there was still more data.
Or it means something else entirely.
It depends on what the documentation says that BIP 4413 means.
You are also looking at the wrong messages. You should be looking at the messages in the system log, that come with a BIP number. There should be a number of them that provide a more complete understanding of what's wrong.
You should also be using a User Trace instead of the debugger to debug this. You will see information about where in the message tree the data has failed to parse. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sat Jul 28, 2012 2:39 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| mqjeff wrote: |
| It depends on what the documentation says that BIP 4413 means. |
It looks like 4413 is a data value, not a BIP error number; the OP did not provide the actual BIP error number, (for example BIP 5507).
| mqjeff wrote: |
| You should also be using a User Trace instead of the debugger to debug this. |
 |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jul 28, 2012 3:15 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| rekarm01 wrote: |
| mqjeff wrote: |
| It depends on what the documentation says that BIP 4413 means. |
It looks like 4413 is a data value, not a BIP error number; the OP did not provide the actual BIP error number, (for example BIP 5507). |
Mmmm.... good point, not likely to be storing data persistently for subsequent processing. |
|
| Back to top |
|
|
| yshakraj |
| Posted: Sun Jul 29, 2012 2:46 am Post subject: |
|
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
In field properties,it has decimal(packed decimal) but in the esql i'm mapping it to character data.I think this is the problem I guess.Could please tell me whether i've to cast it to decimal or any other.
and some other fields are 'xsd:short-' but under physical properties it's physical type is 'external decimal' and could pls tell me how to cast that field, which is currently mapped to charater data. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jul 29, 2012 3:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yshakraj wrote: |
| I think this is the problem I guess.Could please tell me whether i've to cast it to decimal or any other. |
Why guess? Why not follow the advice given to know what the problem is?
But yes, moving character data to numeric fields typically doesn't work out that well unless you cast it. You're reliant on WMB doing an implicit cast, which may or may not be what you want.
Of course, if you'd taken a user trace you'd know what was happening.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| yshakraj |
| Posted: Sun Jul 29, 2012 5:09 am Post subject: |
|
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
The flow i'm working on is unwritable so i'm unable to put a trace node to that flow.I put a trace node in a local flow and tried,but then it is neither giving error nor giving expected result.
my actual error is this
| Code: |
Text:CHARACTER:CWF Writing error
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:CMessage::write
Insert
Type:INTEGER:5
Text:CHARACTER:msg_PBMSPAYFILELAYOUT
Insert
Type:INTEGER:5
Text:CHARACTER:/msg_PBMSPAYFILELAYOUT/SAP_TO_JDE_EMP_FILE/PAID_RATE
ConversionException
File:CHARACTER:F:\build\S000_P\src\cpi\bsutils\datacnv.cpp
Line:INTEGER:3769
Function:CHARACTER:DataCnv::PckdDecFromDec
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPv610
Severity:INTEGER:3
Number:INTEGER:5507
Text:CHARACTER:CPI InputData Too Long
Insert Type:INTEGER:5
Text:CHARACTER:decimal
Insert
Type:INTEGER:5
Text:CHARACTER:packed decimal
Insert
Type:INTEGER:2
Text:CHARACTER:5
Insert
Type:INTEGER:5
Text:CHARACTER:4413 |
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jul 29, 2012 6:29 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
looks like you are supplying a value for field
| Code: |
| Text:CHARACTER:/msg_PBMSPAYFILELAYOUT/SAP_TO_JDE_EMP_FILE/PAID_RATE |
that is too big for the space defined for that value...?
You really need to take a user trace... this will give you the definite answer 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jul 29, 2012 7:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yshakraj wrote: |
| The flow i'm working on is unwritable so i'm unable to put a trace node to that flow. |
What does that mean? How can you be working on a flow (especially as you claim to be adding ESQL to it) when it's "unwritable".
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sun Jul 29, 2012 1:31 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| yshakraj wrote: |
my actual error is this
| Code: |
<useful information missing>
Text:CHARACTER:CWF Writing error
Insert
Type:INTEGER:2
Text:CHARACTER:0
Insert
Type:INTEGER:5
Text:CHARACTER:CMessage::write
Insert
Type:INTEGER:5
Text:CHARACTER:msg_PBMSPAYFILELAYOUT
Insert
Type:INTEGER:5
Text:CHARACTER:/msg_PBMSPAYFILELAYOUT/SAP_TO_JDE_EMP_FILE/PAID_RATE
... |
|
Above the portion of the error shown, there should be a "Number:INTEGER:####", which indicates the BIP Error number. In the absence of a usertrace, the InfoCenter can provide additional information about the error. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sun Jul 29, 2012 1:32 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Also, a User Trace does not require a Trace Node. |
|
| Back to top |
|
|
| yshakraj |
| Posted: Mon Jul 30, 2012 7:19 am Post subject: |
|
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
| pls suggest me how to take a user trace. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jul 30, 2012 7:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| By following the instructions on IBM's website and in the Info Center for taking a User Trace. |
|
| Back to top |
|
|
| yshakraj |
| Posted: Tue Jul 31, 2012 12:53 am Post subject: |
|
|
Voyager
Joined: 14 Sep 2011
Posts: 91
|
I took the user trace, it' showing the similar error BIP5507.The conversion from character to packed decimal is causing the problem.
SET target.MRM.SAP_TO_JDE_EMP_FILE[I].OT_1_HOURS = CAST(source.MRM.JDE_Emp_PayFile[I].Emp_P2.OT_1_Hrs AS INT);
I'm mapping OT_1_HOURS,a packed decimal field, to source field which is a string and i'm casting that to INT inorder to make it a packed decimal.Could plesae tell whether i'm doing the correct casting or whether i've to do any encoding. |
|
| Back to top |
|
|
| kimbert |
| Posted: Tue Jul 31, 2012 1:45 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I took the user trace, it' showing the similar error BIP5507 |
Please
a) post the full text of the error message
b) post any relevant details about the target field's physical format. We know that it is a packed decimal, but that's all we know at this point. The error message is complaining about the input data being too long, so the length of the output field would be useful. |
|
| Back to top |
|
|
|
|
