DSXchange

roy wrote:But,you can always SET.FILE pathed hash files to COUNT them

I know. Just picking on Arnd.

ArndW wrote:You can also execute a command line COUNT <hashfilename> or SELECT COUNT(*) FORM <hashfilename>; from the Administrator.

As long as they're not 'pathed'.

Joshi - that's an... interesting... solution. Not something I would have thought of, mostly because our Production jobs are read only and can't be horked with like that. Suggest you build checkpoints into the process, much like Roy mentions. I've taken more of an approach in the past of assinging a ...

That was my understanding.

Out of curiousity, are you importing an export made in XML format? Those have to first be converted from xml to dsx and that happens under the covers with no indication of anything going on other than your CPU being pegged by something called 'xml2dsx.exe', from what I recall. Large ones can take qu...

If you use capital letters for the sort criteria - A, ASC, D, DESC, etc - you get a case insensitive sort. To make it case sensitive use lower case letters - a, asc, d, desc, etc.

This is all spelled out in the .pdf documentation for the stage.

*claps*

Yah... it was so extra special and exception-full that we are always at the end of the port list. "It won't be ready for our platform until when?"

1. During selection of the job to import there are 4 jobs of the same name. How do I know which is the latest batch job...? Import? If you mean 'Initialize' into VC then there can't be 4 jobs with the same name. Same thing when you 'Promote' from VC to a project, you'll find the jobs all have diffe...

I could have sworn - back in the day - when I was running on a Tru64 cluster and 6.0 came in the door, it went from 32bit to 64bit as part of that upgrade. There was a need to upgrade to a specific compiler release and I thought mention was made of large speed increases directly as a result of every...

You really should read the What's New documentation that comes along with the product. It's built into the Manager, under the 'Tools' menu.

You may need to filter out the records with the nulls in an upstream constraint so they don't even get to the Aggregator... it's not real fond of nulls anyway. Is that a possibility?

The 14 is a resource error, from what I recall. You have overloaded your machine. You either need to throttle back on how many you run at any given time, or look into upping some of the internal configuration parameters for the DataStage server. Not something for the faint of heart... or the subject...

Very true! Two links into one stage doesn't mean that they write to the same hash. All it guarantees is they live in the same account or are pathed in the same directory.

Comparison against @NULL is meaningless; the result is necessarily "unknown". That is, you can't legitimately say Col = @NULL and expect it to behave in a Boolean fashion (in fact, there are rules in DataStage that govern the behaviour under these circumstances, but won't yield the results you expe...