DSXchange

Not really. Your RTRIM/LTRIM syntax is database syntax, you could replace it with just Trim() in the derivation and accomplish the same thing. If you are good with something like Perl or Awk (or perhaps a good editor), you may be able to export your job to .dsx or .xml format and make the substituti...

As have I...

Welcome!

I don't believe so, at least not the "HTTP the output stream to an URL" part. There have been other posts on this subject here, you may be able to turn them up with a search.

BACKUP.BAT? Is that something that comes with the Windows version of DataStage?

ray.wurlod wrote:That is, AND and OR have the same precedence.

Are you sure about that, Ray? I was under the impression that it followed more 'standard' precedence rules in that AND had precedence over OR. Maybe I've been fooling myself all these years...

No, you don't. Didn't you get my reply to your Yahoo email regarding your example job? If not... you are only mentioning one field in your where clause - the first field or :1 which is fine. However, the first two fields are marked as keys. Try setting the second field to a key value of 'No' and onl...

I think that was already mentioned... along with the 'unlimited budget' comment.

Best Practice would have you create, in a "preprocessing" step or job, a hash file with all of the current business keys and their corresponding surrogate keys. Ideally, you would constrain that build to whatever records are currently staged for processing. Then your lookup can be done against the h...

How are you actually doing this "search"?

So, in other words you are emulating a BI tool with DataStage? :D Yerk. Do your users have a methodology whereby they could insert records into a database table? I'd probably create a set of jobs that periodically polled that table for unprocessed records that indicate specific requests and then run...

Probably a locking conflict where someone else has a record locked that your job is trying to update. DataStage will wait for it to become available before it moves on. Check with your DBA...

Simple - we don't have any "user scheduled" jobs. Actually, I've never had a need to do this, so I would be curious what kind of jobs these people would be scheduling. Now, we do have "loosely scheduled" jobs that are waiting for files from various people... but they run over a specific window and p...

Yes, it is possible - but you do have to create a VOC record to do so. Search the forum if you need it, the syntax has been posted here many times. I use a routine I found here that creates the VOC record 'on the fly', does the count on the hash and then removes the VOC record. Simple enough to setu...

Ok, let's try our luck with this one. First thought would be to ditch the stored procedure and replicate whatever work it is doing in DataStage. I think you'll find this easier to maintain going forward. That being said, if you only want to run this once you either need to run this 'after job' or on...

Maybe... however, I do use the syntax that I posted quite a bit, so I know that using the quotes inside the sql (around the parameter marker) works just fine.