DSXchange

We have some sql that contains the clause: WHERE CODE IN ('123','456','789') We'd like to replace the hard-coded list with a parameter, something like: WHERE CODE IN (#pCodeList#) We'd rather not have separate paramaters for each code, because the list may expand. So we wish to avoid something like:...

That'll do nicely. Better than hard-coding, and much better than modifying the Job Control code.

Thanks Kryt0n, and everyone for their help.

Yes, it is the name of the invoking Sequence job that I want. Thanks for that - I couldn't think of the term to use. I've tried a few things, but cannot seem to get the syntax right. I've tried the following: 1. #BATCHID##DSJobName# = 1234DSJobName (literally, with no substitution). 2. #BATCHID#DsJo...

Thanks for your patient explanation Ray, but I still think we're not quite on the same page. Building from Ray's example: - What we want is for JS to run the multi-instance job JA, and give it the instance-name JA.1234JS (where 1234 is the Batchid (a parameter of JS), and JS is the name of the calli...

I'd have thought that DSJobName is set during the initialisation of the master sequence (eg. EMP_DATA), before it runs any Job Activities (eg. calls CHKAVAIL). If I understand Ray's explanation correctly, it means that the "Invocation Id's" are established during initialisation, before DSJ...

Sorry, that's not quite what I meant. What we want is to see items in the log like: CHKAVAIL.1234LOAD_EMP CHKAVAIL.1234LOAD_ITEM CHKAVAIL.1234LOAD_ORDER and so on. In the calling sequence (eg. LOAD_EMP) we have a job activity that runs CHKAVAIL. The job activity has a text box labelled "Invocat...

We have some sequences that all call another sequence, potentially at the same time. So the common sequence was made multi-instance. For ease of identification, we'd like the invocation-id to include the name of the calling sequence. Is there a way to include DSJobName in the Invocation-Id? I've tri...

Ah, thanks Craig. Yes, I fell for the trap, and thought it meant it'd wait for all jobs to start and finish. Something I forgot to mention: the sequence also has an Exception Handler that links into the error-handling Sequencer, to trap any unexpected problems (such as a job in the wrong state). I'l...

The current design: We have a "master" sequence that calls a dozen other sequences (After an initialisation job that sets the batchid, there are 6 independent "paths" through the sequence, with each path calling an "extract" and a "load" sequence). Each job a...