DSXchange

I have created a file where one of the fields is a CDU Number which we have formatted to a PIC COMP field. Within some of these values will be the EBCDIC value of 10 (<LF>). I have handled this within DS by changing the "Contains terminators" value within the file to YES for the relevant f...

For further information, we are sending this file via Connect Direct which appears to be corrupting the file with regards to the line terminators.

Does anyone have any ideas what we can do with regards to Connect Direct to remove this issue ?

JezT

Arnd Unfortunately the file is required in Binary format so is there any way round this problem of the line terminating ? Why did the "Contains Terminators = YES" work before we made the field EBCDIC but after it had already been converted by your routine ? Is it likely that the problem is...

Arnd

So does that mean that within my DS Job, I need to import a specific file definition for my output file that will accept line terminators as a character and not actually action the line termination ?

Any suggestions ?

JezT

Arnd Another issue that has come to light is that when we run the job and the output file of the converted Customer Numbers is created, one of the lines has the following error: UKWHCustSegtIntCDUXtct3Job..CDURefreshFile.DSLink335:read_fixedwidth() - row 55, column CDU_CIN, column unexpectedly ended...

Found the problem but on't have the answer. Your routine works perfectly.. the problem we have is: List of Numbers: 40 44 74 When your routine converts them we get: ( , J Which have the following hex values: 28 2C 4A When we transfer this to mainfrme via NDM (either bin or text) we get the following...

So will the trim I have put on Arg1 within the routine be sufficient then ?

Arnd

Should this be sufficent then within the routine ?
With Arg1 being the Customer Number

Or should I also trim ANS ?

Cheers
Jez

Arnd I have put the following into the transformer that calls the routine COMPConversion(trim(DSLink338.CDU_CIN)) Where "COMPConversion" is the name of the routine and "DSLink338.CDU_CIN" is the Customer Number I am passing into the routine. Should that be sufficient to remove th...

Arnd We have a Customer Number: 0123456789 0122222222 0999999999 We need to convert these within DS to be in the format: PIC S9(9) COMP. (I understand these will be gibberish, but want to then re-run this file through the inbuilt conversion to check before we send the file off). Any ideas Welcome, l...

Arnd We have a Customer Number: 0123456789 0122222222 0999999999 We need to convert these within DS to be in the format: PIC S9(9) COMP. (I understand these will be gibberish, but want to then re-run this file through the inbuilt conversion to check before we send the file off). Any ideas Welcome, l...

Arnd I have removed that Print line - thanks for letting me know. However, I am a bit confused. I have run my DS Job with your routine added to convert the values. On my ooutput file I am getting the following figures in my first few lines: ( , J f h If I then test the built in routine "DataTyp...

I have been getting the following warnings when running a DS Job. It involves the conversion of CHAR vakues to a COMP PIC value.

Any ideas what this warning may mean ?

Arnd

Thanks for your reply. Once our system is back up and running again (as we are currently having system problems !!) I will try it out and let you know how I get on.

Cheers
Jez

I think you may have forgotten to add the code (unless that is really the quick and dirty way to do it !!!!!!!!) :D