DSXchange

I disagree. There is no mention of given year in the requirement. Just the fact that there's a date. The requirement for a two digit year is in the output. My point was that one digit for the "century" may not be enough, or that the restriction on dates properly handled needs to be documented among ...

You can see this most easily in the job log. Look for where the "active stage finishing" messages appear. They tend to bunch just ahead of the "job finishing" message.

It is VERY different. For a start it generates C++ rather than BASIC. Try it; you will see different operands in the expression editor. And you will see "data type" as an extra grid in stage variable declaration (one of the more common traps for those converting from server jobs).

Never assume.
The requirement may also need to exclude public holidays. Now we're necessarily talking about a table-driven solution.
And we're still talking about an incompletely specified requirement.
That said, I must plead guilty to overlooking the word "business" in the OP.

Thanks for that clarification. I guess they concentrated more on the east Asian languages for NLS.

You find the packages on the DataStage CD in a folder called Packages. Select the I386 subfolder of any particular package to install on Windows.

On UNIX, the command is dspackinst

The answer is definitely no.

The primary reason is that the project name is also a schema name, and there is no way available to change a schema name in "UniVerse" SQL.

How does complexity of business relate to projects? One example is where there is sensitive information (privacy, confidentiality or sensitivity concerns) where you don't want too many developers to have access to the data. So you might have a separate project (set of projects - dev, test, QA, prod...

Disagree. There are utilities for migrating Table Definitions as other DataStage components, including Version Control and export/import.

A hashed file is just a mechanism for implementing a database table in which the location of a record is determined by applying a function to its key value. No index, no scan. Very quick to do key-based access. To get to TCL (terminal control language) establish a telnet session to your UNIX server ...

Lots of folks use Control-M, SeeBeyond and other enterprise schedulers. You need the command line interface dsjob to start and query your jobs; search the forum or the manuals for more information on this command.

Don't do it in the Transformer stage, which is still running when you execute the function calls. Do it in an after-job subroutine or in a routine executed after the job finishes completely (probably invoked from a job sequence).

Your requirement will cause problems if you have dates ten years apart crossing a millenium boundary (for example 1005-07-29 and 2005-07-29). The "century" will be 1 in each case (11th and 21st). Your result will be identical in each case. Sit a man by a fire and he's warm just for a while. Set him ...

You have missed the vital point. There is NO index on the key. That's where the speed comes from; the key value is processed by a function (the "hashing algorithm") that returns the exact address of the page on which the record resides. Exactly one logical I/O is required to retrieve the record (unl...

In terms of the ETL logic, no. Unless you need to implement different rules in the new system. Physical architecture obviously. PX can run on one or more UNIX (or Windows) machines, or on USS (UNIX support services) on a mainframe (I think that options costs more). The UNIX architecture needs to hav...