DSXchange

The solution was : Unix and Zos are not the same OS ... So cp in Unix and cp in Zos are differents ... cp in Zos ask for explicit information about delimiter ONLY for binary ! So "cp -F lf filesource filedest" in Zos => copy file source to filedest and not copy delimiter "lf" lin...

The solution :

In the shell script :

I added a :
sed 's/\x0D$//' file

So the file before being transfered have no '\r' or CR or 'x0D'

Only have a delimiter of end of line : '\n'.

I have the same problem :

I suppose somebody else created a dataset in the same directory, but not from the same environnement.

So For solution in TEST environnement :

I created a dataset with a different name.

Because my datasets can have diffrents name suffixs.

AND IT works ! fine !

It is probably a problem of transfert from Unix to ZOS in mode text .

Because in mode binary it will be ok.

The issue seems to be like that : " Even though the message is not currently viewable in it's entirety, the portion that is visible gives you the clue on how to solve your problem. Basically, a "\n" (UNIX), or <CR><LF> (Windows) is just another string that can be manipulated with norm...

How many nodes do you have ?

How many lignes in your treatment ?

Cordially, Gabriel Georgin.

The wanted format was : PIC 9(4) COMP-3 But decimal[4,0] {packed} is PIC S9(4) COMP-3 SO i tried with decimal[4,0] {packed} type format = binary My real problems is : I have 5 columns : 1st column : char(1) (no problem but type format = text) 2nd column : decimal[4,0] (type format = binary) wanted 3...

The format in output for second column wanted was PIC 9(4) COMP-3
=> format 3 hexadecimal
in datastage it is : decimal [4,0] {packed} ("type format binary")

sequential file text binary (unix to ZOS) ZOS file has lag problems (add of blanks). I created a file in datastage text + binary first column : char(1) text (values '1';'2';'9') second column : decimal [4,0] binary (take 3 in binary not 4) third column : char (10) In datastage, I see only first colu...