DSXchange

Welcome aboard. Any standard number beginning with ISO is issued by the International Standards Organization; you can consult their website for more information. ISO8859 (parts 1 through 12) covers ways of encoding characters encountered in commercial business data processing in "European" language ...

It's not actually relevant. Your disk was full, and that's why DataStage could not create a new file/table.

You are getting intermittent network errors. Check for faulty network card and/or check with your network administrator whether any strange things are occurring on your network.

Use Monitor to determine what the status of each stage is. Also, is the row count continuing to increase? (Yes would indicate that the job is still running.)

U has not logged in for some time.

The second person personal pronoun in English is spelled "you".

Switch back temporarily to a hard-coded pathname as the value of $APT_CONFIG_FILE. When you're done testing reinstate $PROJDEF as the default value.

Try using double-quote characters instead of single-quote. The target field must be of type VarChar (that is, string[max=N]).

sreddy wrote:There is generally a player for each operator on each node.

There is ALWAYS a player for each operator (each operator mentioned in the score) on each node.

Try to stay with the convention of ".fs" suffix for File Sets and Lookup File Sets (even though the latter is not a true file set) so that you don't confuse your support provider.

They are stored in DSParams. But you may need to re-open the client to have it re-read the file.

Or the disk where your project is installed has become full.

Just leave out (omit) the -type option to get all types.

ODBC driver for text files can do this. It's a great solution if you're being paid by the hour!

It suggests to me that you're trying to read a sequential file with a hashed file stage. The ds_uvopen() function relates only to a Hashed File stage. If you had been using a Sequential File stage the function would have been DSD.SeqOpen().

Define "not used". This may be trickier than you imagine. For example you may have one or two hashed files used only in end of year processing. Once you have identified them, deleting them is straightforward, but you must use the correct method depending on how they were created. If they were create...