DSXchange

3600000008 is too big to be a signed Integer. You'll need to make it a BigInt. The largest signed integer is 2147483647, the largest unsigned integer is 4294967295. So even uint32 can not cope with all 10-digit numbers.

Do you know, reliably, which format your source dates are in? For example is 08/08/08 a YY/MM/DD or a MM/DD/YY format?

If not, you're doomed.

InLink.Value >= 0 on output link constraint.
InLink.Value < 0 on reject link. You could also employ Otherwise/Log for this link.

Terminology: it's hashed file, not hash file.

It is not possible to delete rows from a hashed file from a parallel job.

There is no support for hashed files in parallel jobs (other than by including a server Shared Container).

The routine is already written, and posted on DSXchange. It is PxEreplace().

What is the NAME of the aberrant job?

VarChar data type does not need to be padded at all. The value of APT_STRING_PADCHAR will be ignored when writing to VarChar columns unless, perhaps, you explicitly specify a padding function.

What are your criteria for "best"? At one level, anything that achieves the correct result is "best", is that not so?

Is there any easy and straightforward way to obtain a list of all common metadata assets in the Repository, ideally using a command line tool (but I'll tolerate a GUI if absolutely necessary, provided the results can be written to a file)?

Did you once have a default node pool ("") which has since been removed from the configuration file? The Sequential File stage (import operator) would have used that.

Oracle is ...
_________________ ... different

Because, in server jobs, the representation of the Date data type is "internal format". Most Connectors (and their predecessors) perform the conversion automatically where the metadata are consistent.

You can not pad with "" because a zero-length string doesn't pad. That is, string : "" does not increase the length of string. NULL (unknown value) is even worse, because concatenating NULL causes the result to be NULL and you lose the original value. Pad with 0x00 (which your vi...

In a word, "automatically". Date management is part of regular Type 2 SCD processing using this stage. You can also set a "current" indicator.

Your edit has removed the example, leaving us even more in the dark.

At a guess, I'd say what you need to do is subtract the number of days in the previous month from the current date.