DSXchange

Luk, did you remember that a constraint gets evaluated to TRUE and then sends the column out that stream. Meaning that if the constraint reads "ISNULL(In.Column)" then only nulls columns are passed, and the REJECT merely takes any rows that haven't gone down any previous links. Looking at your logic...

Amos, the home directory (UV) doesn't contain any indexed files, so somewhere during your new project creation phase a CREATE.INDEX has probably failed. This could be due to UNIX or DataStage privileges. Did you do a "VERIFY.SQL {ALL}" as Ray suggested? If you create a dummy directory in /tmp and is...

<slap><slap><slap> You shouldn't go around indiscriminately killing jobs

Go to the Director and, for the job in question, click on Job -> Clear Status File. This will work since you know the job is no longer actually running (as you bounced the DS server this is a given).

We have a 10-cpu AIX box and are running a DataStage 16-cpu license on this system. The operators have turned on SMT (Simultaneous Multithreading) which makes the system look like it has 20 CPUs. DataStage gives warning messages that the number of licensed CPUs has been exceeded in every job run but...

TheBird, <sigh>. Please read my original response. There is no easy "just click somewhere" option to fix this, unless you can make the person giving you this data change their method. 1. You now know what the problem is. 2. You now know what the rules are to fix this problem. 3. You are a DataStage ...

nolane,

when you right click do you get the 3 greyed-out selections and the 2nd not-greyed-out selection is "delete"? I do.

If you have embedded quotes in a string they are doubled (the following is a correctly formatted CSV string:

I do it from the Manager or Director, click on the top job, shift-click on the bottom and then do a delete.

This is not an uncommon problem. The easiest way to fix this is to make sure that the program creating the sequential file does it correctly - either through use of another quote character or doubling up the quotes as per csv specs. If you cannot do this then you need to modify the sequential file t...

How about IF NUM(In.CheckNumber) THEN IF (In.CheckNumber<0) THEN '-' ELSE '+' ELSE '*'

There are whole packages (costing big $$$) that do this kind of thing; so you know any answer you get here will be incomplete.

I would do a derivation LastName = FIELD(In.Name,' ',DCOUNT(In.Name,' ')), that will make the last name everything after the last space in the string.

Yes, even if the file is being created in the same job it will work, provided the stage that creates the file is in the stream before the stage that reads from it.

mcolen,

yes, you can write to and read from a hash file in the same job, just make sure that you have buffering on both writes and reads turned off.

Madhukar,

the easiest way to create an empty dataset and also to clear the contents of one is to write a job that doesn't write any rows to the dataset.

It turns out that we the environment variable $APT_ORACLE_LOAD_DELIMITED set (using ";"), which messes the handling of embedded quotes up. I added $APT_ORACLE_LOAD_DELIMITED to the parameters of the job in question and specified "$UNSET" as the value and it ran through flawlessly. (got the solution ...