DSXchange

I'm afraid there's absolutely nothing we can do to help you unless you provide more tangible information. What does your job do? What are its sources/targets. Are you performing joins? The context of your migration activity? Just because you 'NEED' a solution doesn't mean you'll 'GET' a solution if ...

Thanks Ray. That worked. I queried the DS_JOBS table to get a list of jobs in a specific folder.

Hi,
Is there a way to list the names all the DataStage jobs in UNIX or otherwise?
Thank You

So you are not sure if those columns from Teradata are actually nulls. First fire a query with a 'where colname is null' in teradata and check if they are really nulls. If they aren't, try extracting the ascii values using the ASCII function in your db. If the values aren't nulls, then they are most...

This might help you.

And like you can see in the above diagram, the link on which you define the type of lookup is a reference link!

The sparse lookup option will be available to you in the Oracle connector stage only if the connector is directly used as a reference link to the lookup stage. There SHOULD NOT be any intermediate stages between the two else you will not find the sparse lookup option.

Are you sure you are linking the Oracle connector directly to the lookup and there is no copy stage between the connector and the lookup?

it won't and it shouldn't. The Quote=double/single merely tells datastage to ignore the character 'IF' present and read from the character after the leading quote character up to and not including the trailing quote. If not present, it just reads all the data. if the quotes are present, then it igno...

I don't see the trim applied to the NUM function's parameter in the code you've posted. Kindly post the updated code.

Since it's char(19) and you have numbers stored in the column, you may have spaces padded after the number.
Spaces, or whatever your PADCHAR is, are not valid numeric values. Either change the datatype to varchar or trim the spaces before performing the numeric check.

So my question was not childish after all

This might sound childish but when you say \N, you mean the newline character '\n' right?

See if This helps. You can probably get a custom SQL at your source. This is under the assumption that your database is Oracle. Not too ure whether the SQLs mentioned will work with other DBs

Try

This might sound childish but when you say \N, you mean the newline character '\n' right? In my opinion the \n is where it should be. It's a new-line/record delimiter. Your logic might be failing because the new-line character is not a part of the column's data!