DSXchange

I don't know. Email membershipdirector@dsxchange.com

Keith has it. Your data are not partitioned correctly or not sorted correctly or both.

The "A" stands for "attribute". "Attribute mark" is a synonym for "field mark". Therefore storage really is a dynamic array in a DataStage hashed file. The key is separated from the rest of the record by a "segment mark" (Char(255)). On that basis th...

Keys and non-key columns are stored adjacent in the DataStage (UniVerse) hashed file structure. Each page consists of a contiguous set of records. The key value is used to determine the physical location of the page on which the record is stored (using a hashing algorithm, from which the name HASHED...

It's the name of the document that is the manual.

It's an environment variable. It should, if it exists, contain the pathname of the parallel engine directory.

ODBC uses ODBC protocols, Sybase stages use Sybase OC client software.

Why not ask the original authors of the article at that site? Basically the point made is that the two are completely separate products, sharing only a name. The original DataStage (now server edition) was created by VMark Software, while the parallel execution engine was developed by a company call...

No.

You may be able to convince your IBM sales rep/reseller to let you have an evaluation copy, but one of the requirements for that is that there must exist a reasonable likelihood of a sale.

Have you installed the SAP pack on your production system? This message indicates that the cataloged routine could not be loaded. Since this routine exists in the global catalog ($DSHOME/catdir) that either means that it's not there, or that you don't have permission to read that particular file (*D...

Orchestrate operators are the small pieces of C++ executable code - the classes, if you will, from which objects are instantiated. For example, when you design a job that has a Sequential File stage that reads a file, the runtime executable will include an import operator whose task is to read the f...

a) It's not a file it's a database. That's why it's called the repository database. b) Yes, it's a database. c) It's a database that is installed in a location you specify when installing IBM InfoSphere Information Server. d) Yes you can query it. Like with any other undocumented database, you need ...

1) Faster than you could do it with pen and paper. 2) Depends which version you're asking about. In version 8 there are four tiers - the common metadata repository for Information Server, the services tier (also known as the "domain"), the DataStage engine tier and the DataStage client tier.

So? Even though that may be a stupid requirement, it does not prevent you providing a lookup mechanism. Use a lookup stage.

I've learned something today. Does the "old way" - having the job check for the existence of a file or of a value in a file - not work any more?