开发者

Generating a flat file with SSIS to be read by IBM z/OS program

I am creating a fixe开发者_StackOverflowd width text file using SSIS. The format of the flat file connection is Ragged Right. The file is generated correctly and passes all local unit tests on my Windows machine. The SSIS package then transmits the file using SFTP to a partner. The mainframe programmer at our partner claims he only can read one record. I checked what I was using for line breaks and I had chosen {CR}{LF}.

I did some research and found a couple of articles that stated that non-Windows systems would not be able to recognize CRLF as a row delimiter, but {LF} would be valid. I tried that and the programmer there still says he only detects one record even if the file has over 100 records.

Is there any additional SSIS configuration I am missing in my Flat File Connection? Could it be an encoding issue?


In cases like this I find it useful to request a small sample file so that you can match your output to it, using a hex editor to verify all the special characters. If a sample file is not possible then narrow down your results to 2 or 3 and work with your counterpart to get the format correct even if it means you are manually altering the file with the hex editor until you get it correct, then you can tackle the programmatic file creation.

Your mileage may vary, but right now it would seem you are programming without a complete spec, and that's going to make your job a huge headache if not totally impossible.

Good Luck!

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜