DSXchange

DRS = the Dynamic Relational Stage, one which alleges to support access to multiple databases with the flip of a switch.

Which Ken has already done.

Pretty much all objects include a place for 'Logging Text'... including Sequencers. No need for a routine.

Right, take only what you need from ETLStats. Or use it as a template or just as something to prime the pump, get your creative juices flowing.

And it will continue to run the 'Reset' job on next schedule. If this means 'start the sequence from the point of failure', you won't have that until you upgrade to at least the 7.5.x release. Or you write something yourself. I used to code in multiple entry points in the job stream, with a job par...

(channelling Ken) Time Dimension!

Give it an appropriate name and that will go a long way towards the 'self explanatory' part.

Your error is still "Unknown client library - #SRCDBTYPE#" - without it translating the job parameter? Then perhaps that field doesn't support parameters. I don't use it so can't say. Suggest you contact your official support provider and ask them.

No, I remember them as being all lumped together under the "lastest DataStage patches" from what I recall. Could be wrong, however, it's been awhile.

Yes, mixed case to match the value in the stage if you pick it manually.

Known bug.

I believe that if you can connect to whatever the latest "eSupport" website is, they are there available for immediate download.

Well, unless you are running something like the 7.0.1 version, you are going to get push-back on your "aren't restartable" comment. They are, we leverage that all functionality over the place. If you are on an older version, you can code in restart points (messy but doable) or you can... upgrade. Of...

You have #SRCDBTYPE# set to "ORACLE" where? In the DRS stage? Doesn't it need to be "Oracle" instead - assuming it takes a parameter at all?

Hey, one I know!

Touch a file called 'errorlog' into existence in $DSHOME.