DSXchange

It does not.

It's only possible via a query (or several) against DS_JOBOBJECTS. There's nothing in the version 7 UI that can help you, and not even the Advanced Find facility in version 8 will help. You might begin with something like: SELECT OBJNAME, OLETYPE, NAME FROM DS_JOBOBJECTS WHERE EVAL "@RECORD&quo...

I have a master sequencer No you don't. You have a sequence. A Sequencer only makes an Any/All decision about whether its inputs have fired. It's a component you use in a sequence. Assuming you got that right, the issue is almost certainly how you are handling errors and warnings. You have told us ...

The commands will work OK on Windows assuming that the user ID executing the script has relevant authority. db2Start and db2Stop are in %SQLLIB%\BIN (for example C:\IBM\SQLLIB\BIN). WebSphere Application Server commands such as startServer and stopServer are in C:\IBM\WebSphere\AppServer\bin folder....

Only if you can edit the generated DDL. I prefer to copy the generated DDL from DataStage, paste it into a suitable tool (like DB2 Control Center or TOAD for DB2), and amend it there for any requirements I have - tablespaces, indexes, named constraints, and so on).

You resist stupid requirements.

Of course you can use SQL, but you still need some convenient table from which to select.

There are no "out of the box" functions, though DateFromDaysSince() will come fairly close.

There are scripts in ASBNode/bin and ASBServer/bin but I can't remember off the top of my head what they are. Hopefully the locations will trigger someone who does know to respond. If not, I'll get back to it at a convenient opportunity.

Any wait can cause it. Even waiting for DB2 to generate all the warnings it needs to before rolling back a transaction, if the timeout interval is set short enough or the server is busy enough. Saw one of those today.

OK, that rules out the possibility that UV.ACCOUNT is corrupted. I presume that you have full permission to UV.ACCOUNT ? If so, it's time to involve the vendor, because "internal error" is not something someone "outside" can easily diagnose.

The dot is correct. This indicates that it's a decimal. If you don't want the dot, explicitly trim it off. What do you want to do with the additional eight character positions? Whatever it is, you have to specify it.

As with any metadata mismatch warning, the only way to suppress them is to "get it right" - specify mapping the correctly handles all of the characters in your source data. In extreme cases, build a map (or hire an expert to do so).

Always put Sort stages on each input of the Join stage. This gives you the flexibility to control things like the memory allocated to sorting, and to be able to specify "already sorted". If you don't, DataStage will insert a tsort operator anyway (under default environment variable setting...

There are ways of getting "hi___" to work without code tags, if you really want to.

So you have three key columns and two parameter markers in the WHERE clause? That won't work. Your keys should be ID and TheDate (where you want to return rows where TheDate is between eff_date and term_date).

This is a perfect example of where a time dimension table is the ideal solution.