DSXchange

I've seen the message before when trying to read nulls into an numeric column. Specifying the "Null field value" should fix the problem.

If it's something else, then let us know the format properties of the file, and the format properties of the "SYR" field.

Note that it has been a problem for both Server jobs and Parallel jobs. From Administrator, the command: SELECT "DESC" FROM DS_RESENU WHERE ERRNO = 2046; returns Finished waiting for job\n I did notice one other code returned without text: Missing StringID[2114] so put this through Adminis...

We occasionally receive a "Missing StringID[2046]" error when running datastage v7.x jobs from Unix. - It happens for both PX jobs and for Server jobs. - It usually happens when the job aborts, but there have been cases where the job finishes okay, but the message is still written to Unix ...

My thanks to asadi for this one:
Map the decimal[10] field to BigInt

Much nicer!

Sorry. I missed some vital information about your environment.
I'm using v7.x. I do not know if v6 has a "Remove Duplicates" stage.

Someone else will have to help you on this one.

Have you tried the derivation options of the Aggregator stage?

Newkid now, but perhaps not for long :D
Have you looked at using the "Remove Duplicates" and "Sort" stages?

Scenario: ColumnA is a varchar field (eg. value=A). ColumnB is a decimal[10,0] field (eg. value=76543210). ColumnC is a varchar field (eg. value=X). Requirement: Write to a comma-delimited sequential file. ColumnB is not to have a leading space or decimal point. eg. the record should be: A,76543210,...

That issue of null_values for fixed-length fields (eg. a timestamp field) was a real problem for us. We had a pipe-delimited file with a timestamp field, where || signified a null. Ascential provided a patch that basically provides a new setting (a project environment variable: "APT_IMPEXP_ALLO...

Sorry for the confusion. "null field" is how it appears on the internal record definition, but in the Stages it's called "Null field value". 1. Here are the steps to get to the "Null field value" property: In the "Sequential File" stage, on the "Columns&q...

We got that message too, but chose to look the other way and ignore it (standard coding practice ). The job output showed no adverse effects from this strange warning message.

Our experiences with XML in Datastage 7.0: Trouble with using XML in PX. We resorted to using a Server job. No "parallelism" under PX, so using a Server job was no great loss. Big crash (core dump) when parsing large files (~30MB+). This was resolved by applying a patch from Ascential. Cou...

If I understand you right, this is done by specifying "null_field" value for each column, in the initial Sequential File stage. eg. If ColumnA is a fixed-length Integer(10) field, then you specify null_field=' ' When reading the file, if ColumnA contains a string of ten spaces, then Datast...

I have a PX job that reads in an entire record as a single binary column. The binary column is later passed to a Column Export, that converts the binary column into a Varchar(4000) field, which is then output to a delimited Sequential File, with variable-width records. The problem is that the text f...