DSXchange

Can you post the generated SELECT statement? This may offer some insight into what is happening. Can you try using user-defined SQL, specifying the column as CHAR or VARCHAR, and using a TO_CHAR function to effect conversion, using the date picture of your choice (for example 'YYYY-MM-DD HH24:MI:SS')?

For large volumes of data, a hashed file containing 601 rows and two columns, would perform best. Assuming your hashed file is to be called RANGES, create it as a Type 2 with modulus 20 and separation 4. (Just trust me on this.) CREATE.FILE RANGES 2 20 4 Populate the file with the following code (or...

See http://www.dsxchange.com/viewtopic.php?t=86781

See http://www.dsxchange.com/viewtopic.php?t=86781

To answer the original question, the length limit on column names is imposed by the ODBC driver, not by DataStage. It's typically 255, but may be less for some drivers. The limit on the number of columns may be imposed by the database server; if not it is constrained by the MAXFETCHCOLS parameter in...

You can use the functions Craig mentioned in a BASIC Transformer stage.

You could always use the Ereplace function in a Transformer stage, or in a Routine called from a Transformer stage. For example Ereplace(inlink.column, "<", "&LT;", -1, 0) Unfortunately, this approach requires one Ereplace per special character. But, if there aren't m...

The Reporting Assistant is used in two phases. In phase 1 you export whatever components you need to report on. The metadata are written in a first normal form destination, by default an MS Access file called doc_tool.mdb. In phase 2 you use either the standard reports in doc_tool.mdb or create your...

Covered this off line with Tom.

Welcome aboard! :D

So that you can justify the search, the answer is yes.

Create job parameters, click on "use environment variable" when defining them.

Now, search on... :D

Why not ask Ascential for a copy of the 7.x manuals? They contain much that will answer all of these questions. I am sure they would have no problem with this request. A very short answer is that the Hash algorithm uses a hashing algorithm based on the supplied key value (which can be any data type)...

At the "bleedingly obvious" level it indicates that your transaction could not write to the transaction cache file. What's going on here is that you're performing some kind of write to a UniVerse table. All writes to UV tables are auto-commit transactions, and are therefore cached until the commit i...

DSObjects is the control that delivers objects to DataStage clients that allow them to open and maintain connections, invoke code on the server and, in general, do all the things they do that require a connection. Definitely sounds like an incomplete installation. Try uninstalling. When this is unsu...

No.

DataStage mainframe jobs generate COBOL code and the JCL to compile and run same.
No provision is made for reading COBOL (apart from DATA DIVISION) and translating same into DataStage objects.

I've seen something like that before.
It's documented at http://www.dilbert.com/comics/dilbert/a ... 522841.jpg