DSXchange

I just noticed a typographical error on my part, the format should be
"%dd-%mmm-%yyyy"

I vaguely recall someone posting either source code or comments about a user-written function to emulate the REPLACE function in server jobs, perhaps you could search for it.
This might be a case where a server job might be useful.

Your data string error message shows a leading space, which, as ajith_infy has already seen, needs to be removed in order for the format to match.

Your date format is incorrect, it should read "%dd-%mmm%-%yyyy"

There is no builtin function in PX to do this.

Are you applying your schema to the one-column record in a column import stage? If so, you can use the reject mechanism there.

There is just one repository system, but at Version 8 and above you have both hashed files and the XMETA repository contents to keep in synch. Since you have used an undocumented method to force delete a job, you might have caused damage to your project which cannot be easily fixed. Can you try to f...

If you get incorrect values with multiple nodes then you have partitioned incorrectly. You need to partition on DEPTNO.

What happens when you put a reject link on your input file? (That was not really a question, but an answer...)

Yes, there are. If you want to get the current project name in BASIC or a job sequence, try

Colin - All I can think of is increased sunspot activity influencing your compile times.

(for those of us who weren't around when the Dead Sea was just sick, google "BOFH" or "Bastard Operator from Hell" )

This is somewhat confusing, since the error you posted is for a job that calls the "ParsenExtract" instead of the cpp program you mentioned. The error message refers to an inability for finding the object code - which is set in your repository definition of the "ParsenExtract" ro...

Yes, you won't be able to set the value using an embedded BASIC transform stage for this reason.

There is no "not null" in schema files, if "nullable" is not present in the schema description then the field is not nullable.

a SQL Char is converted to whatever datatype you declare that column to be in the DB stage. The table shows what implicit conversions can be done.