DSXchange

The dsjob command is well-formed and returns 0 for success and non-zero for non-success. One that basis IBM don't have a case to answer. It's by using the -jobstatus option that you cause dsjob to exit with the DataStage job's exit status. If you don't do that, then dsjob behaves "properly"...

DataStage originally, and up to version 5.2, used UniVerse as the engine for its Repository. So the appropriate place to go is the UniVerse manuals on IBM's web site. For TCL commands the best manuals are: UniVerse System Description UniVerse SQL Reference UniVerse User Reference Any damage you caus...

There is no way to suppress return code checking in the way about which you ask.

You can, of course, change the script itself so that it always exits with zero status.

"Not nice" is not a business case. IBM's response would be that the product works as documented.

"seemed", eh? Get in touch with your support provider, who can guide you through the use of supplied scripts for cleaning up the XMETA repository.

A Search would have garnered your answer faster. Your data type is Char(40), therefore ANY value, whether or not that value represents NULL, must contain forty characters. The Null Field Value property contains a value that will be interpreted as NULL on reading or be written if NULL is received int...

This will only ever be an approximate result. To get the precise result you require a rule about how partial months are to be handled.

And let us know, purely out of curiosity, whether it's still urgent a week later.

Windows 95, Windows 98, Windows XP, Windows Server 2003 or Windows RG?

Again, it's not that simple. It's probably going to be a small multiple of (82 * 10000) or thereabouts*. This is the Char(1) sort key, a separator and the 80 bits that identify the row in the virtual Data Set. If you don't have enough memory, the Sort stage will use other disk space, starting with t...

The overhead is 80 bits (10 bytes) per row, so the total requirement for a reference input to a Lookup stage would be 1010 * 10000. The partitioning algorithm does not affect total demand, but can influence per-node demand.

Yes you can, and would be in this case. Specify space as the delimiter character in your StartLoop activity.

What if you specify -domain, -server, -user and -password options?

1) It does resolve them in version 8.1. There are some 8.1 sites where you are working.

2) The new tool (Information Server Manager) does most of what you are asking for.

3) The main "problem" is that Version Control was dropped from the product set in version 8.0.

4) See above.

Was it working before you moved things? If so move them back. There are lots of Registry entries pointing to the locations of things.