DSXchange

Try setting the 'default padding' character in the Sequential File Stage to a "*".

You're probably going to need to get into DS.TOOLS from the command line and check the integrity of your repository. If you've never done it before or don't know what it is, it can be a little intimidating. Do you have a support provider you can call? Someone who can walk you through this or help di...

why does log says 50 records read and 50 records written ?? To address this question, this is simply the number of records read from your flat file that were sent (ie, written) to the OCI stage. Each record contains a set of key columns that you are using to delete rows in the target table. Note th...

when ever I change the variable value in Administrator That should effect in Datastage jobs And it will, provided you are running a recent enough version. I think it is in 7.0.1 that Environment Variables work as you would expect. Before that, you would need to recompile the job before it would rec...

marc_brown98 wrote:Would the two lookups be in the same transform?

Yes, it would. Doesn't absolutely need to be, but it is the simplest way to do it.

From the online help for System Variables:

Help wrote:@FALSE The compiler replaces the value with 0.
@TRUE The compiler replaces the value with 1.

There are others well worth your time to check out.

Datastage is INDEED receiving the parameters I'm passing - but it is NOT recognizing the "then" statement following a "true" IF statement. It's the "IF-THEN-ELSE" - NOT the parameters that are the problem. Any suggestions for that??? That's cool. Must be an O/S thing 'cuz it don't for me on HP/UX t...

Thanks as well. Interesting to me is the fact that it is chosen from the (...) in the editor from the list of Link Variables, not System Variables and doesn't have the leading @ you would expect. Oh, well... live and learn.

I didn't know Oracle 8 supported the "left outer" syntax, I thought they were still using the (+). I also thought that Oracle 8 didn't support the extended ANSI standard where the join statement and join criteria could be included on the same line, instead you had to use the basic ANSI standard whe...

You've got it right, Vincent. The plus sign syntax is the older Original Recipe way of doing this in Oracle and goes on the 'outer' side. The new 'left outer join' syntax is the Extra Crispy version.

You can also do 'right outer' and 'full outer' joins.

It actually looks like Neo is trying to call the routine only on the first record in an effort to avoid exactly what you said. However, there do seem to be a couple of issue with what was posted, unless they are 'typos'. I would think that this: ProcDateValue=Arg1 PreviousPath="/home/login/xyz/...

Thanks Ray. I was on my way home when I came to the same realization and smacked myself upside the head - why not not check the generated code? [thump] The interesting thing to me is it only seems to handle 'logical' rejects. Actual 'physical' rejects, bounced back from a passive stage like OCI, don...

Like I said, I know about the rejects specifically tied to a linkname and I know it will work with all the goofy stuff that happens when you first start getting 'real' data that doesn't come close to looking like all of the test data you've seen before that. Duplicate Keys, Required Fields, Invalid ...

I've found a number of jobs where a Reject Link (not with the Reject Row checkbox marked) has a contraint of either "REJECTED" or "(REJECTED)". Does anyone use these and know how in the heck they are supposed to work? They don't seem to trap OCI rejects, hence my question. Note that this is not Link...

I couldnt figure out how to set the stage variable information into a user status area and then pull it out from the next job. Create a custom routine that simply calls DSSetUserStatus with Arg1 and then passes Arg1 back out as Ans. This allows data (like your Stage Variable) to pass thru something...