Using the delimiter character (Ã½) in sequential

srimitta · Post by **srimitta** » Mon Apr 16, 2007 11:41 am

Can you forward (Paste) some sample records?

mouthou · Post by **mouthou** » Mon Apr 16, 2007 12:03 pm

[quote="srimitta"]Can you forward (Paste) some sample records?[/quote]

Please see how the records were created though I gave a different delimiter.. Copied 4 records from my output file.

A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002388**IN_TRANSIT******WAREHOUSE**2002-10-15*******************
A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002389**IN_TRANSIT******WAREHOUSE**2002-10-15*******************
A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002599**IN_TRANSIT******WAREHOUSE**2004-10-15*******************
A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002600**IN_TRANSIT******WAREHOUSE**2004-10-29*******************

ray.wurlod · Post by **ray.wurlod** » Mon Apr 16, 2007 2:58 pm

Char(248) through Char(255) are reserved characters in DataStage; they are the dynamic array delimiter characters.

You are wise not to use them for any other purpose in server jobs.

Pre-process your source file to replace any character in this range with a suitable equivalent, perhaps from Control Set 0 (Char(1) through Char(31)).

mouthou · Post by **mouthou** » Tue Apr 17, 2007 9:25 am

[quote="ray.wurlod"]Char(248) through Char(255) are reserved characters in DataStage; they are the dynamic array delimiter characters.

You are wise not to use them for any other purpose in server jobs.

Pre-process ...[/quote]

Ray,

I am wondering how another datastage user (srinitta) was able to use the character as the delimiter without any problems. If you see the post above, she mentioned it. Is there any reason why it doesnt work for my version?

Thanks,

bharathappriyan · Post by **bharathappriyan** » Tue Apr 17, 2007 2:40 pm

Try with &Hfd as delimiter in the target sequential file stage

mouthou · Post by **mouthou** » Tue Apr 17, 2007 3:06 pm

[quote="bharathappriyan"]Try with &Hfd as delimiter in the target sequential file stage[/quote]

It is really a surprise for me why it doesnt work in my case.

I am still getting the same compilation warning and the same output..

A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002388**IN_TRANSIT******WAREHOUSE**2002-10-15*****12345**************
A*INV_DOC*RECEIVING*WHSE_TO_STORE*1*00002389**IN_TRANSIT******WAREHOUSE**2002-10-15*******************

Thanks everybody for trying. I really appreciate it. I may have report this to IBM.

ray.wurlod · Post by **ray.wurlod** » Tue Apr 17, 2007 3:33 pm

I did not say impossible, I said unwise.

Use a hex editor (for example UltraEdit or filepeek) to convince us that the delimiter characters are indeed 253.

Please advise whether you have DataStage NLS enabled. If you do, then the "true" ASCII codes 248 through 255 may be being remapped to the Unicode private use area.

mouthou · Post by **mouthou** » Wed Apr 18, 2007 7:50 am

[quote="ray.wurlod"]I did not say impossible, I said unwise.

Use a hex editor (for example UltraEdit or filepeek) to convince us that the delimiter characters are indeed 253.

Please advise whether you have DataStag ...[/quote]

Ray,

I dont quite understand when you said confirming the characters as 253 only. I am setting 253 as the delimiter. Datastage itself is resisting to have that character as the delimiter and converting the 253 to *. Hence the benefit of checking the file using an hex editor is very minimal.

Thanks,

ray.wurlod · Post by **ray.wurlod** » Wed Apr 18, 2007 3:25 pm

Use a hex editor on your source data. Or you only trying to create a target file with 253 as the delimiter?

Please advise whether you have DataStage NLS enabled and, if so, what map is being specified for the Sequential File stage.

mouthou · Post by **mouthou** » Thu Apr 19, 2007 8:07 am

[quote="ray.wurlod"]Use a hex editor on your source data. Or you only trying to create a target file with 253 as the delimiter?

Please advise whether you have DataStage NLS enabled and, if so, what map is being speci ...[/quote]

Yes, the source data is from the table. I am using the delimiter only when I am creating the files. NLS may help in our case. But as I checked, NLS was not enabled during our installation. I am contacting the admin to work upon it.

Thanks,

ray.wurlod · Post by **ray.wurlod** » Thu Apr 19, 2007 2:48 pm

You have misunderstood my intent. If you don't have NLS enabled, that's one less possible cause for the problem. Leave it disabled until you can solve the handling of 253 without it.

Can you please list ALL of the values from the Format tab of the Sequential File stage that writes this file?