DSXchange

Tried that. Didn't help.

Specifically, from DS.TOOLS, I first ran "Check integrity of job files" and then "Rebuild Repository indices".

Ray - don't know if you'll classify this as a 'respectable reference' as I can't site a webpage or anything, but one of my 'onshore' cohorts tells me that your first representation is correct:

10,00,00,00,00,00,000

Three places for the first comma and always two after that.

For the initialization I can grab all dependent components of a server job (a.e. routines); but I am missing the possibility to grab all the dependent components of a sequence that means all the called jobs. Or is there a way to configure this? Not that I am aware of. This seems like a good candida...

Thanks to a run-away job with an improperly pathed 10GB flat file, our DataStage install partition just filled up. Now, as expected, I've got horked up jobs. In addition to the error mentioned above, I have two jobs that in the Director show "!!Error getting job status!!" as their description. Job #...

At worst case, just wrap a 'select count(*) from' around the whole darn thing.

If you search the forum, you'll find that there have been several recent conversations regarding Row Buffering and the strange problems it can cause.

Still a little fuzzy, but let's see... There must be someway to join these four tables together or you are not going to get very far. If they can't all be joined together at the same time using some kind of complex SQL statement, then it sounds like you may need to do it in two steps: first join A t...

Well, seeing as how you can 'select' pretty much anything using a DB stage you can select a simple count. Depends on exactly what you are trying to accomplish. If you are joining tables and want to process the detailed output plus know how many records were involved, you've got a few options: * Make...

Only with a Windows server and the 7.1 version, from what I understand. UNIX server side exports are rumored to be part of the upcoming Trinity release.

As Ogmios pointed out, that's pretty darn vague. Depending on exactly what you meant, I could see two ways to approach this... 1. Do your joins in the driving query or at worst case in a reference lookup inline. Use the Aggregator stage after that to do your 'sum result and record count' work. Check...

I have all the columns defined for all the fields being returned by queries and prog_id and agmt_prg_id are keys Then that's the problem - the 'are keys' bit. It didn't find anywhere to 'bind' the key column(s) in your custom sql. Assuming both are keys and they are column 1 and column 2 respective...

Make sure you've got columns defined for all of the fields being returned by these queries...

How are you 'joining' the two results? There doesn't seem to be a 'key' field in your lookup.

Thanks Ken.

7.1 only!

Otherwise you get to roll your own checkpoints.

Write Cache will not overwrite a hash record so the first record in is the final record only on duplicate keys. Going back in time a little, but this came up in conversation this morning... This statement concerned me, so I wrote a little test case to see if it was really the case that overwrites d...