DSXchange

This is one for your support provider. If JobMonApp is shutting down as soon as its start request is issued either you have a permissions problem with one or more of the places it needs to write, or you have a buggy version of JobMonApp.

No, the default is 15 for EXACTNUMERIC. This is not the same thing as PRECISION. The default value for PRECISION is 4.

You can not give $PROJDEF. Because it's your own code, you need to interrogate the value of the environment variable and provide that value in DSSetParam().

Yes. Further, it's a DB2 installation/configuration error, not a DataStage installation error.

A Search of DSXchange would have saved you the trouble of waiting for this reply. Assuming that you have executed the dsenv script, your command search list (PATH environment variable) includes the DataStage parallel engine bin directory and have correctly set APT_CONFIG_FILE and APT_ORCHHOME, then ...

Table X already exists in the SEBI_EDW schema.

There's nothing more to say.

No database will permit CREATE TABLE if the table named already exists.

You can use the orchadmin command in a script or even with wildcard characters.

Ancient UniVerse knowledge.

Using an ODBC driver for Excel, the DSN refers to the workbook and each worksheet in the workbook - subject to certain requirements - presents as a system table from that data source.

Read the DataStage BASIC manual on the topic of PRECISION. Hopefully it will make things clearer.

You need to transform whatever format is coming in into the format expected by the default Oracle timestamp picture (or supply a non-default picture).

It *should* return null, provided your target field is nullable. Otherwise it will expect that the target field has a default value and should return that.

OK, then try one of the simple ASCII maps.

The file name is actually errlog. If you create it it exists and logs engine errors. Don't forget to make it writable.

Blocking on exact name is an unusual approach - what if there are misspellings? However, that is not the cause of this problem. As noted, check lines 3, 4 and 5 of your source data.