DSXchange

Here is the official verdict from IBM for all products: m For DataStage, it's all about the Java components. So, if you are using the Web Services PACK or RTI / SOA, you'll need to upgrade the embedded JVM to be compliant. No mention of XML, which kind of surprised me. My understanding is it is bas...

Since this seems to have become a popular topic lately and I had something 'official' on the subject stashed away, I thought I would post it for the community so people would stop asking me to email it to them.

Please check the FAQ Forum for a posting with the same title.

but My question is that why at all datastage makers decided to provide this functionality in a transformer stage and did not allow look up stage in a server job. Because they are different products and different paradigms. Ascential built the Server product from the ground up, and later acquired th...

when I rerun job it is not doing "loading ( updating)" as per expectation. You've said neither what it actually does when you rerun the job, nor what your expectation is. Need more details on the nature of your problem, like how you differentiate inserts from updates for one. Can't help you with th...

If your job parameter truly is a String type and you're still getting the -4 errors, that would be because of @FM (Field Marks) in your command output.

You either need to pull $CommandOuput<1> or use something like Convert or EReplace to strip them.

Yah, kinda figured. Thing is I've used it in the past for DOS and early Windows when it was truly just a toolkit. My, how she has grown in all these years I've been away.

So, the MKS Toolkit in essence creates something like a 'virtual' UNIX environment and everything actually runs in that environment? Interesting... I guess 'toolkit' is a little bit of a misnomer.

My response was based on a faulty recollection of having done that just recently. I had to relicense an expired server and thought I had changed serial numbers in the process. Now that I recollect, it wasn't a serial number issue like we thought it was at first but actually just a need to replace th...

A Protected project will only allow 'dsadm' type users to delete jobs, a 'normal' user will not be able to. That's how it is in 7.5.x but perhaps that functionality is not in the early releases. You'd need to verify that with Support, I would think.

All that is good. Now you just need a constraint to keep the unmatched records from being output. Typically, that would be:


Change the ReferenceLinkName noted above to your real link name.

Ok, good. However, other statements you've made are a little confusing as well. Setting a constraint on an outbound link will not effect an inbound's link ability to do a reference lookup. And a typical lookup check would be using the Link Variable LinkName.NOTFOUND instead of checking the two value...

ghostraider wrote:The key expression is Sample.FlatFile=Sample.HashFile.

That's not literally what's in your Key Expression, is it?

It should just be something like InputLink.Sample_Number as best as I can tell from your posting.

I don't really understand your "from within an MKS Tools environment" statement. You might want to expand on that a wee bit. DataStage for Windows ships with the MKS Toolkit nowadays, so that you can leverage it and do 'UNIX things' on your Windows Server. If that's what you mean by 'running from wi...

Where did you read it's not possible? Older version required a 're-install' to do that, but recent ones allow it via the Administrator.

Do an exact search on your error message: 'Consumed more than 100,000 bytes looking for record delimiter; aborting'. There are several other conversations where this has already been discussed.