DSXchange

Here is one such example of the kind of Vincent's blog that I was thinking of. These test objectives might also help. None of them contain a discrete set of questions, but should give you plenty of ideas on things you could be asked about.

If you look, you'll notice the jobs are not producing 'excel' files but rather simple 'csv' or comma separated value files. They can then be opened by Excel and (if desired) saved back as an xls file. Take all the defaults in the Sequential File stage and you'll get a csv file, but you'll probably w...

Do you have a partitioned table? If you do, then it would be a matter of ensuring your loads were partitioned in the same manner as the target table, on the same 'keys' or fields. Unless you've made special arrangements, I'd be surprised if your files are arriving that way, so you need to take the t...

Multiple Instances not necessarily equal faster or that they are able to break the laws of Database Loads. The first load is locking the table until complete, at which time the second can run. Multiple simultaneous loads generally require a partitioned table with each load stream handling a unique p...

Look into all of the 'Link Variables' available. Put them all in a reject link and see which ones the DB2 stage actually populates under various conditions as not all stages are created equal. Depending on what you see there, you may very well find that to know the full 'reason' for the problem you'...

"Error variable unassigned on return from BEFORE routine" Your problem in a nutshell. A Before/After Subroutine is not equivalent to a Transform Function like you would use in a Transformer derivation. And which you seem to be trying to write. A Transform Function can have multiple Arg values and re...

Actually guys, if you read the post again, you'll see that Kauchy hasn't asked for any answers but is apparently just looking for some sample questions that may be asked. I personally don't see any problem with that. I seem to recall that Vincent posted some sample certification questions over at I...

Two posts in December 2004 and then gone, it seems.

Ok... I AGREE if what the op means by 'DS Job Control' is hand coded job control code. Silly assumption on my part that we were discussing Sequence jobs as we don't run into all that many hand-coders around here.

Still, they'll need to find a way to differentiate between the two 'aborts'.

pradkumar wrote:Moreover in loop activity stage, we can give only numeric values

That's not correct.

Add in a UserVariables Activity stage to capture the filenames and it can be used to feed them to the Start Loop stage one at a time.

But of course!

And this is different from the precision specified by the EXACTNUMERIC uvconfig parameter?

"Specifies the number of digits of precision before rounding occurs. The maximum is 57 digits and the minimum and the default is 15 digits."

Are we actually discussing scale?

All of the DSGet* functions have an equivalent option in 'dsjob' from the command line. For example, DSGetLogSummary is the -logsum option from what I recall. So it is perfectly feasible to script something rather than code up a routine to do this. Bone up on it by reading the Server Job Developer's...

Not sure that's possible. An abort is an abort so you wouldn't be able to differentiate solely based on that criteria. You'll need to find some other way to handle stoppages based on rejected counts. Perhaps just logging a warning and then a specific Warnings trigger to a Terminator stage? Hmm....

You can create an 'after job' routine to check the job's INTERIM status and send an email if it says it will be aborting.