DSXchange

Create a reject link on your Sequential File stage that reads the file and specify Date as the data type for this column.

Process the reject stream to generate null to replace this field, and funnel it back into mainstream processing.

What's special about them? Can you find out what the underlying codes for them are, perhaps by inspecting your source with a hex editor of some kind?

There being no output from the final record is not actually a problem in this particular scenario. This is why I made no mention of it in my solution.

I'd be wary of using "#" as a delimiter character, as it can have another meaning (parameter reference). I'd prefer one of the dynamic array delimiter characters, such as field mark (@FM), since these are unlikely ever to occur in data.

Where do the 3490 figures come from in target row 1000|01|12|24|2000.00|3490.00|2000.00|3490.00 ? There is no 3490 beside key 1000 in your source data. At a guess you're simply searching for a way to compare a row with the previous row. This is done with sorted source data (which you appear to have,...

1. You can not reindex a job. You can only reindex repository tables. If users have developer's privileges you can not easily restrict their ability to index the tables in which their metadata are stored. The only way of which I can think is the "fourth line of remote" security mechanism f...

Warning: Latin content

In the singular:
nausea (nominative)
nausea (vocative)
nauseam (accusative)
nauseae (genitive)
nauseae (dative)
nausea (ablative)

Being first declension there's no way you could get a "um" suffix.

"From the command line" was my intention for "this context".

What's special about them? Can you find out what the underlying codes for them are, perhaps by inspecting your source with a hex editor of some kind? Do you have NLS enabled?

Get your DBA to monitor the session. In my experience DELETE does take a very long time, particularly when there are referential integrity constraints involved.

Are these actually job parameters or are you intending to use the -user and -password options to the dsjob command itself?

I never claimed it was slower. I asserted that it needs more resources (mainly memory but also CPU). This is because each sort group must be kept sorted in memory. If you have sufficient spare resources, then overall processing speed may be unaffected. But best practice in all computing is never to ...

In a routine open VOC then use the STATUS statement to fetch it's file information. In the dynamic array returned by STATUS you will be able to find the date and time created. This perforce is the project date/time created.

Try either creating a new job (to pick up your new default that you set in Administrator) or changing the existing job's job properties to set the new format there.

PX as a name no longer exists. It was a marketing fantasy based on an incorrect premise, and very short-lived. Use EE (Enterprise Edition). It requires not "a" C++ compiler - it requires the approved C++ compiler. And this needs to be installed before DataStage is installed. But it remains...