There is a field in a table definition record (table definition records are in the DS_METADATA table) containing "CMetaColumn/n" where n is the number of column definitions in the table definition. This introduces the collection of column definitions. Let us assume that this is found in field number...
Check the permissions on the project directory and on any directory associated with a processing node. If the executing user does not have write permission, and script files can not be created and you might get this message. It's not really the message I'd expect in that case, however. I think an "i...
Expanding slightly on what Kim said. You can set the "missing columns" rules in the Sequential File stage (Columns grid - scroll right to find them) to have DataStage ignore the fact that there are missing columns, pad with null, etc. Then you constrain the output so that these rows are not output, ...
Take a look in the supplied Routines, in the SDK branch. There are some associated with translating data types. They are written for reading, rather than writing, these data types and converting to "regular" numeric formats. It will be straightforward to create the inverses of these functions. It is...
Maybe, maybe not. For a start, both jobs would have to run on exactly the same set of processing nodes. It may also be necessary to specify those in the same order (for example use the same configuration file for each job), so that the partitioning algorithm works the same way. I don't imagine you w...
From past experience I know that the DB2 API is quite similar to the ODBC API. The SQLAllocEnv function (which SQLAllocHandle probably calls when needing an environment handle) does little more than set up a small amount of memory for managing the environment in which connection information will be ...
Thanks for posting the solution. It's one of those simple things that we just assume have been done correctly, and don't bother to ask. The support folks are more professional, and always remember to ask!
Take a look at the stage properties (Write Method of Load property) and/or the script file that is produced.
Details are in the Parallel Job Developer's Guide in Chapter 12.
There is an upper limit to the complexity of nested If..Then..Else statements. The limit is not documented, but IS hard-wired. You can't change it. There is an also an upper limit to the overall length of an expression. This used to be documented, but I can't find it now. From memory it is about 8KB...