DSXchange

Those errors mean the Oracle instance you attempted to connect to was down. So either it was available earlier but not now or, as Arnd mentions, you connected to a different (and still unavailable) instance. Check the Server job's log, the first record will show the parameter values it used. Or doub...

Go ahead. Use whatever command line interface exists for your database - for example, 'sqlplus' for Oracle.

You may not know how many delimiters there will be on any given run, but do you know what the maximum value of 'n' would be?

Going that route, you'd need both IConv and OConv. First convert the data to internal format and then back to external format using the desired mask. If your date is consistent, meaning always 8 digits, you can also go the substring route: Link.AC_COMPLETED[7,2] : '/' : Link.AC_COMPLETED[5,2] : '/' ...

No clue as I don't have access to the 8.x version, someone else is going to have to answer that one.

Hmmm... not sure if there's an easier way, but the DSJobController macro (or DSGetJobInfo with the DSJ.JOBCONTROLLER InfoType) will give you the name of the controlling job. You could then take that job name to the repository and query for the job type.

Trap what errors? And what exactly do you mean by "trap" in this context?

Of course. You need to ensure that each Sequence has defined in them all of the parameters that each Job Activity they will be running, needs.

Same way, basically. Include a job parameter for the string and put it in your where clause surrounded by hash marks.

OK, that all looks fine. So, your ODBC Action is set to "Call stored procedure"? If that actually runs the proc during a reset, I'd report that as a bug to your official support provider.

How exactly is your script doing the "reset"? Post your script or at least that relevant portion.

No - if one of them works for you, simply wrap the whole constraint in a Not() to get the "opposite" of it.

The Nested Condition stage is what you need. Check the job parameter value in the triggers to the child Job Activity stages, make sure they are mutually exclusive.

Your logic is faulty. One good field makes it goes down the good link, while one bad field makes it go down the reject, so both are perfectly valid unless all fields are good/bad.