DSXchange

Demoting the message to informational is not going to help you, since the warning is most likely occurring in the sequential file write stage and any rows with one or more nulls will not get written to the output unless you handle nulls. You will need to handle nulls for all nullable columns when wr...

Are you certain that the sequential file exists and is not empty at the time when you are trying to do a "view data"?

##I IIS-DSEE-TOIX-00163 13:53:01(000) <Seq_PS_Vendor,0> Import complete; 0 records imported successfully, 0 rejected.

Two commonly used options are:

1. NFS mount the remote drive
2. Use "rsh" (or "ssh")

No, not using the API calls to get the log entries and it is better to modify your current return string to remove the invocation id column than to access the log files directly. I don't have access to DS right now, but if you post your output with invocation id included then I'm sure that I or some...

knoblaub - I'm curious as to how that is different from the answer that I gave you, since that is exactly what I posted?

Regardless, please do mark the thread as "resolved".

It would seem that you are in a single-byte mode, i.e. no UTF-8 or extended latin character set, which makes things easier. The sequential file stage allows you to specify a filter, so you could indeed use the follow sed command in the sequential file stage filter condition: sed "s/[^space-~]//...

Would the following work for you:

/opt/IBM/InformationServer/Clients/istools/cli/istool export -dom SERVER:9080 -u ***** -p ***** -ar arc.isx -ds ''-incdep "SERVER/Tutorial/Tutorial/Jobs/Copy*.*"' -v

There is no DataStage command to perform this cleanup, so you should use a UNIX command.

I would not exit out of datastage and use sed unless there were no simple way to do this within the tool. This would depend upon your definition of "special". The base function used for this kind of work is CONVERT()

The path information for the components is contained in the .ds file, which is a binary file and shouldn't be edited with a text editor. Can you simulate a logical link to that path using a symbolic link?

The answer depends heavily on what you consider to be special characters.

You have different metadata and data. adding a carriage-return line-feed to your file is the simplest method to get rid of this warning.

The following function takes the string as the input parameter and returns the string parsed into distinct fields. EQUATE Delimiter TO ',' EQUATE DoubleQuote TO '"' Ans = '' FieldCount = DCOUNT(InString,Delimiter) QuoteCount = 0 FOR i = 1 TO FieldCount WorkField = FIELD(InString,Delimiter,i) IF...

If you add $OSH_PRINT_SCHEMAS = true to your job parameters you can see the actual schema used between your stages. You are converting HOSP_NUM to a datatype with less possible value and thus you are getting the warning message. The best solution is to explicitly convert the data to the same types i...

CONVERT(@FM,CHAR(10),FIELD(Execute_Command.$CommandOutput,@FM,1,DCOUNT(Execute_Command.$CommandOutput,@FM)-1))

This removes the last field then converts all field marks into char(10)