DSXchange

Have you asked your DBA to check the database logs to see if the cause came from within DB2? Also, monitor your disk space during the load, I always feel uncomfortable when I see "/tmp" and huge files since that is often mounted on the system partition which has very little space.

If both systems were identical, they would produce identical results with identical programs & data, but there is a difference so, ipso-facto, they must be different. Finding and fixing the error isn't always easy. You first need to identify one simple (to test) aspect which is different and the...

Go to the stage, double-click the number next to the column name and see if any of those settings are set, that is what I meant by the "extended attributes"

FranklinE - if they don't even have a chance of adding a column to the table, what are the chances of them implementing partitioning?

Do you have any extended attributes set by mistake for this field?

How about:
1. copy the table contents to a dataset.
2. clear the table
3. load the new data

if the load aborts, the clear the table and re-load the dataset from (1).

An awful lot of overhead, but at least you won't blow up your database.

Since the host is EBCDIC and the vm isn't, it would be the settings on the vm host side where the DS server is running which would apply. I do know that there are many EBCDIC host character sets in use and one would need to "choose wisely" to use an Indiana Jones analogy if one wanted legi...

This is more of an Outlook question than a DataStage one. If you know how to get embedded objects out of an Outlook server then the DataStage part is relatively easy. A Google search of "ODBC" and "Outlook" gives a number of hits. As does "Web Service" with "Outloo...

Are you certain that the data type is "string" for this column; I've never seen this stage not create double quotes when set to do so, but this option only applies to non-numeric fields.

I think that we are talking past each other. Even with RCP, your columns will need to be "created" somewhere before they can be part of the RCP schema. This can happen in several different ways, none of which seem to be happening here. Add the following Job Parameters then compile and run ...

An empty derivation in the transformer tells DataStage that the columns are coming from the input. You need to give a column derivation in the transformer in order for the columns to be created.

The routines you need to use are: DSGetProjectInfo(). With "DSJ.JOBLIST" you will get a list of all jobs. Loop for each job DSAttachJob() DSGetJobInfo() - will get you the job name, last run DSGetLogEventIds - will get you a list of log entries Loop for each logentry DSGetLogEntry() - get ...

In the sequence that starts the 2 invocations, were you using those long fixed strings or a variable? If a variable, then ensure that this variable isn't empty (a length 0 string) at runtime since that would cause the sequence to run as if it had no invocation id.

ponzio wrote:...Why Job B and Job C don't have log entry with the invocation id as suffix and have only the main log ?
Andrea

They don't have an invocation id specified in the place where they are started.

Is the birthdate in the column "BIRTH_DTTM"? If yes, what is the data type and if it is a string, what is the format?

What data type should the output column "AGE" be?