DSXchange

The Sort stage previously had its preserve partitioning flag set to the default, namely Preserve. This instructs the downstream stage to try to preserve the partitioning of the data that entered the Sort stage. Since the downstream stage is perforce required to operate in sequential mode, it is unab...

They are text files so you can use any file comparison tool. If you have a UNIX emulator, like MKS Toolkit or CygWin, you could use the diff command. Some editors, like UltraEdit, also have comparison tools available.

If a before-job subroutine fails, nothing else in the job happens.

What precisely do you mean by external datasource in this context (for there's no such terminology in the product as far as I am aware), and where is this record size limit documented?

THe file is designated as fixed width. Therefore your null field value must have the correct number of characters to fill its field. In this case that number of characters is 19. You have provided a one-character null field value, which is unacceptable.

The hashed file may be being used to remove duplicates - though a DISTINCT keyword in the column derivation in the ODBC stage would have done just as well in this particular job design.

In the NLS.ADMIN menu choose Mappings then Tables then Create. This creates an entry in NLS.MAP.TABLES table. Enter the name of the table (for example UTF-16). It then prompts You may copy an exsting record to form the basis of the new one whereupon you can enter the name of a compatible map (or non...

There is a manual called DataStage NLS in the standard manual set. This takes you through the process of creating a map. Make sure that every mapping you create is round-trip-capable.

I think it has to be at the client end. There's nothing findable in DSINCLUDE with either value.

1) It's a bug.
2) It ought not to bring down the instance.

Do 'they" stop DataStage - for example for backups - in the middle of the night?

...and make very sure that $APT_ORCHHOME/lib appears in the shared library search path ahead of ANY database client library.

Not enough information. What stage types are involved?

Check that you have privileges to create the table in the temporary workspace (or wherever else you may have specified).

Not sure where these messages are originating, which doesn't help diagnosis. They aren't in SYS.MESSAGE, so I don't think they're part of DataStage server. I think you'll need to involve your "official" support provider on this one.