Originally posted by: jvanboga

I received an EBCDIC file from a TP that needs to be converted to ASCII. Along with the file, they sent a version of their mainframe copybook. Once I delt with the redefines (removed) the copybook imported fine. I then went thru the tree converting western/ascii to western/ebcdic.

I created a valitation map using their sample file and it fails with an invalid on first field. That particular field/element is defined as...

number/binary/packed/sign-trailing(+)/

Anyone have any input that might help?

v6.7
windows xp
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: repanzer

We recieve EBCDIC in the MQ header over a message queue and CONVERT it;

CONVERT(CorrelId MQBYTE Field:.:InputMessage,etoatabl)

Where etoatabl is the one that installed with WTX for the EBCDIC/ASCII conversion sample under;

C:\Program Files\ibm\WTX_8.1\examples\general\portdata
We don't define our input type as EBCDIC and our output type ASCII and let the map convert it.

Can you post the trace file?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: jvanboga

Yes, I've used that map set too. Actually before converting the type tree to EDCDI I used both versions of the 'ebcdic to ascii' maps. They both produced the same results but the default/ascii type tree failed to validate those results also. I suspect the issue is the comp3 fields.

Here is an excerpt from the ebcdic validation....

(Level 2: Offset 0, len 2, comp 1 of 45, #1, DI 00000001:)
Data at offset 0 ('00...') failed item presentation test for TYPE
X'0007' (PLAN Field CopyBook).

(Level 2: Offset 0, len 2, comp 1 of 45, #1, DI 00000001:)
Data at offset 0 ('00') is INVALID data of TYPE
X'0007' (PLAN Field CopyBook).

(Level 2: Offset 2, len 7, comp 2 of 45, #1, DI 00000002:)
Data at offset 2 ('000000h...') failed item presentation test for TYPE
X'0008' (CLAIM_NO Field CopyBook).

.
.
.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: repanzer

Where you able to figure this out?

If the question is, I have an ascii value of 1000 and it's failing against a type that is defined;

number/binary/packed/sign-trailing(+)/

I might be able to help.

When you throw in the EBCIDIC to ACSII, I'm not sure exactly what's happening in the map.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

To some degree I have it resolved.

The generic ascii conversion didn't seem to work. I worked with the EBCDIC t-tree and have gotten the first 2000 bytes converted.

Also, the first two files given to me were bad files.

My problem now is that the records are variable length, no terminators (or deliminators) and uses occurs as part of the record format.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange