DSXchange

I recall reading a tech note about needing to do that, but I can't immediately recall where.

Don't worry about the spaces, that's just how DataStage displays raw data (non-printing characters are displayed as two-digit hex values, such as 09). The third field in your pipe-delimited data has the value "False", yet the metadata specifies a nullable int32 for this field. That will be...

Schema file extension should conventionally be ".osh" though it really shouldn't matter. I agree that you are reading the schema file, since DataStage would otherwise not have been able to detect a size mismatch. Take a very close look at your file and the metadata that describe it. Add a ...

Assuming you're using a Sequential File stage you could use a Filter command to drop or edit the # signs out of the data.

For example to bypass those records, use the grep command, while to alter them use the sed or awk command.

Perhaps RT_CONFIGnnn has become corrupted. Try using either of the hashed file repair utilities to verify its state. Or even just try to count the records in it. If it has become corrupted, you could attempt a repair, but a better approach would be to make a copy of the job and compile that, then de...

There's no other way to unit test DataStage jobs than by running them. Or running a copy, in which things like database targets are replaced with, for example, text files (not always possible, but usually feasible in the early phases of testing).

To use RCP with the Sequential File stage, you must provide a schema file that describes the file's structure.

DSGetLinkInfo() is part of the DataStage BASIC language. You can use it in a BASIC Transformer stage in a parallel job, but not in a parallel Transformer job.

I was about to suggest exactly that solution!

Well done for solving it yourself!

This is the database transaction log for the XMETA database, not DataStage job logs. In an ideal world a DBA monitors how full the transaction log is getting and truncates older entries before it becomes a problem.

You could always upgrade. After all, version 8.0 is no longer supported by IBM.

Welcome aboard.

Excel is doing this, not DataStage.

Change the cell formatting so that leading zeroes are displayed.

"quite similar" <> "identical"

In particular:

• RepositoryAdmin.sh -listRepositories
  
  RepositoryAdmin.sh -listDatabasePlatforms
  
  RepositoryAdmin.sh -listDatabaseServers -dt DB2 -dv 10.2
  
  RepositoryAdmin.sh -displayRepository -rn dsodb

Not cd but su - you have to "become" db2inst1 to determine environment variable settings.

If you don't have access to the su command, login as db2inst1.