| Author |
Message
|
| kimbert |
 Posted: Wed Jan 11, 2012 5:40 am Post subject: |
 |
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
We just made a bit of history there - that's the first DFDL modelling problem to be solved on this forum.
From my point of view, we've started out in the right direction. The DFDL trace gave enough information to enable an accurate diagnosis at the first attempt. In most cases that would not have been possible with the MRM parser. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Jan 11, 2012 6:05 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Congrats on solving the problem.
Can't help wondering if this was some cunning plan cooked up by mqjeff & kimbert to promote the new functionality. 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 11, 2012 6:26 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| smdavies99 wrote: |
Congrats on solving the problem.
Can't help wondering if this was some cunning plan cooked up by mqjeff & kimbert to promote the new functionality. |
I'm not that clever. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 11, 2012 6:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Okay.
So I removed the separator, and now it "works" in that it starts parsing the comment line as a comment.
But it ends parsing the comment line at the first space. So I try to add %NL; as the terminator of the comment element, and it then fails parsing the define again. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jan 11, 2012 8:21 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
Okay.
So I removed the separator, and now it "works" in that it starts parsing the comment line as a comment.
But it ends parsing the comment line at the first space. So I try to add %NL; as the terminator of the comment element, and it then fails parsing the define again. |
Have you allowed for an undefined number of spaces between words and arguments??
| Code: |
DEFINE QL (qname) bothresh (x) +
cluster(xyz) +
replace |
Poses the challenges of a continuation char (' +') plus attribute values that are separated by spaces from the attribute...
Note that you also want to allow for a number of blank lines with or without spaces/tabs in front of LF / CRLF before the next command...
Don't remember though if it is legal for a command to be preceded by one or more spaces / tabs
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 11, 2012 8:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
the model doesn't deal with continuation characters yet.
mqsc continuation characters are much uglier than they need to be in the first place.
AND, there are no continuation characters in the sample data.
there is some allowance for spaces between words, and it's possible that's a related cause. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jan 11, 2012 3:54 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| it ends parsing the comment line at the first space. So I try to add %NL; as the terminator of the comment element, and it then fails parsing the define again. |
OK - here's why.
a) your DFDL xsd has a 'global format block' at the top. That's another way of saying that it defines some defaults for some DFDL properties. Those defaults apply to *everything* in that particular xsd because the format block is anonymous.
b) the global format block contains defaults for lengthKind and separator. They are set to 'delimited' and "%SP;" respectively.
c) your definition for the comment element does not override those default values. So COMMENT is currently defined as a space-delimited string.
d) adding a terminator was a cunning move, but doomed to fail because the separator occurs first in the data. The DFDL parser is not at liberty to ignore a separator just because a terminator has been defined ( otherwise a CSV message with separator=comma and terminator=LF wouldn't work ).
Hope that's clear enough - good luck with refining the model.
ps: probably best to start a new thread for the next problem. This one's getting long. And another DFDL thread can't hurt  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jan 11, 2012 11:41 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
How about starting a FAQ for the DFDL Parser somewhere?
This way all the common problem that we will face when trying to use it can be captured in one place.
OR
An article like the one that is a sticky at the top of this forum for TDS but on the subject of DFDL?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jan 12, 2012 1:39 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Good idea. It's probably a little early to write it now- I'll wait until I've seen a few more questions from real-world users.
btw, there are some DFDL tutorials here: http://www.ogf.org/dfdl/
Some are not complete yet, but there's useful information there already. |
|
| Back to top |
|
|
| RNAWorld |
| Posted: Wed Sep 05, 2012 10:54 am Post subject: CTDP3041E error sounds like new APAR IC85248 |
|
|
Newbie
Joined: 19 Jul 2010
Posts: 2
|
For the CTDP304E error up above, please see APAR IC85248 at http://www-01.ibm.com/support/docview.wss?uid=swg1IC85248 for a possible fix.
-- Craig
2012-09-14 -- update -- upon further testing, I observed an additional alternative cause for a CTDP304E message: We got a file with Unicode when we expected ANSI. -- Craig
Last edited by RNAWorld on Fri Sep 14, 2012 3:45 pm; edited 1 time in total |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Sep 05, 2012 11:07 am Post subject: Re: CTDP3041E error sounds like new APAR IC85248 |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
|
|
