Comments on: SSIS – Working with cobol zoned (signed) decimals

By: Cliff

Cliff — Wed, 16 Sep 2009 18:47:12 +0000

Jim (or anyone else having this issue),
Create a view with the SQL statement and it should work in 2008.

By: Jim

Jim — Tue, 23 Dec 2008 08:26:18 +0000

Doesn’t seem to work in SSIS in 2008. When I try to use the select statement for the lookup table, it complains “The lookup transformation reference metadata contains too few columns.”

Any ideas? Has anyone tried this approach on SQL 2008?

thanks

By: Mike Coffey

Mike Coffey — Mon, 28 Jul 2008 22:23:35 +0000

Know what, I think I found the answer here:

http://www.simotime.com/datazd01.htm

By: Mike Coffey

Mike Coffey — Mon, 28 Jul 2008 22:18:52 +0000

Phil:

Figured I’d ask here rather than on the forum.

In the data file I’m dealing with, the last character isn’t showing up as a brace or anything in your decode table. I’m seeing a lower-case q or lower-case w or something similar. Is there a way to break that last character out into its hex components so I can see what I’m dealing with?

By: Phil Brammer

Phil Brammer — Tue, 27 Nov 2007 21:20:28 +0000

Javier,
You are talking about packed decimals, which this article does not touch on. For packed decimals, look at the UnpackDecimal component from Microsoft: http://www.microsoft.com/downloads/details.aspx?familyid=0e4bba52-cc52-4d89-8590-cda297ff7fbd&displaylang=en

By: Javier

Javier — Mon, 26 Nov 2007 11:39:42 +0000

Hi
Regarding the comment of Phil Brammer (4) about signed decimals in comp-3.
Is there a way to manage these bytes with a data flow transformation?
How can I extract a number if it is with the sign?, like
01 2C -> 12
Many Thanks

By: Andrey

Andrey — Fri, 29 Jun 2007 08:00:36 +0000

Thanks for this article.
I have a data file with copybook…
The Data File(ASCII format) has records with different length…
How can I parse my datafile?( records have fields with COMP-3 type). If records have same length, than I set USEBINARYFORMAT to True (Flat File Source) and use UnPackDecimal component…
Thanks

By: Phil Brammer

Phil Brammer — Thu, 28 Jun 2007 20:02:07 +0000

Comp-3 numbers, I believe are always “signed.” That is, and you’ll have to test on your own, the last byte of data in hex will either end in “C” or “F”, I believe, if the number is “unsigned.”

Regardless, the challenge here is that the data is in hex, but not really. So you’ll have to convert each byte into an appropriate number. That is, if you have a value of +800 stored in a COMP-3, it will be shown as 80 0C in hex. In decimal, that 80 converted to ASCII is some goofy control character. So some work is needed, for sure.

By: William Cikanek

William Cikanek — Thu, 28 Jun 2007 17:40:52 +0000

This works for the zoned decimal, but what about comp-3. I have a rec type PIC S(9)5 comp-3. The values coming through are like 1C, 5C, 6C, 0C. In files like these are the negatives 1D, 5D, 6D, 0D? Also for an unsigned PIC 9(5) comp-3, what will the incoming data look like? Is there a value in the last nibble?

By: Oron

Oron — Wed, 09 May 2007 13:47:07 +0000

Can you plz put the project that transfer the txt to sql with the rules (converting cobol to sql)