DSXchange

NVarChar is Unicode. Use Unicode consitently throughout, and always specify a string length. You may need to make the sizes a multiple of the number of characters.

I would like to have password structure rules, password expiry and enforcement of password change available when one chooses not to map Information Server user IDs onto LDAP user IDs.

Give VarChar(50) - that is, data type VarChar and precision 50.

Standardize whether you have Unicode or don't have Unicode.

No, it revolves around the total size of the query string.

Check with your DBA or Sybase manuals about the maximum length of a query string that can be sent from a client.

Try executing the same query from a different client than DataStage.

Depends. What do you mean by "it"?

There is no replace command. There is, however, a Convert() function. Convert all non-required characters to "".

Tip: initialize a stage variable to contain a full list of non-required characters.

Is there a message in the log that the peek operator consumed nnn rows?
(The key word here is "consumed".)

To summarize what Andy contributed extremely briefly:
Entire guarantees that every lookup will work on any partition.

Dates do not have formats. Dates are stored in binary format.

How can you believe that "The name supplied is aliased to another user" relates to UNION operator?

What has your testing revealed?

What's in the job log for the sequence?

What is your operating system limit (for example kernel parameter NPROC) on the number of sub-processes that any one process may start?

The Repository tier must be installed first, then the services tier before the engine tier.

I have found that following the version 8.1 installation manual, particularly planning (Chapter 2) and installation (Chapter 3) to be very accurate.

A hash file is used for shaping a block of hash.

A DataStage hashed file, if created as Type 30, is "dynamic" (automatic table space management) whereas, if created as Types 2-18, is "static" (manual table space management).

Types 1, 19, 25, 27 and 41 are not hashed files at all.

Your string type, wherever it is, is unbounded. You will therefore always get these alert messages.