DSXchange

I think it uses the table name to validate the columns in your design when the connection to the database is established but before the request to prepare the SQL is issued.

You can not control access at the individual job level, other than by having the jobs in separate projects. You can manage access to projects with better effect than you imagine by well-planned and systematic use of operating system groups in conjunction with DataStage roles. Have a separate group f...

Can't you just pass the value along a link to the ODBC stage that invokes the second Stored Procedure?

UniVerse does not have a TimeStamp data type. Hashed files store all data as string, but DataStage allows the Hashed File stage to pretend that there really are data types out there. Ross is pretty close, but you won't need an index on the primary key, since the hashing algorithm will find keys fast...

On the Format tab there's a property in which you can specify how null is represented in the text file. By default this field is empty, which means that "" (a zero-length string) is treated as null. Change it to anything else (such as <NULL>) and you will read "" as "".

Best practice is to have dedicated network segments with different IP addresses from the rest of the LAN between machines. That way you do not experience saturation problems with the rest of the LAN. NICs are not that expensive - maybe a couple of hundred dollars.

Welcome aboard! :D

The ports really depend on what products you are using. The DataStage RPC daemon listens on port number 31538 by default. Other products, such as ProfileStage and QualityStage, use their own port numbers.

There's a button in the Container properties that allows you to reconcile the names of links within the shared container with the names of the links connecting to the shared container.

Set up parameters in the job sequence's job properties just the same way you would for a regular job.
In a Job Activity these become available via the Add Job Parameter button.

If you can find a UNIX-based ODBC driver for Excel you can go that route. If you also have a Windows-based DataStage you can use the Microsoft ODBC driver for Excel. Beware that worksheets are treated by the ODBC driver as system tables, so you have to check "include system tables" when importing. E...

You are going to need a properly configured Oracle client on the DataStage server machine no matter what you want to do. Whether you use a DataStage job (the preferred approach) or not, what you're creating is a client application as far as Oracle is concerned. So do think about using the tool prope...

If you want to force left-justified (string) or right-justified (numeric) comparisons, you can use the Compare() function.

It's not totally clear what you want to do. Can you please clarify? What I think you want to do is to assemble something on the output that is derived from multiple lookups. If that's it, you note that every input column reference is unambiguous, because it is qualified by its input link name. So yo...

It depends. How many rows? How big are the rows? For small values of each, an all-in-one-hashed-file is appropriate. But if they get too big then separate hashed files (note: hashed, not hash) would be appropriate.

Can't open UV.ACCOUNT indicates a wider problem, which you may have introduced or may have just happened. Get into the UV project via telnet, in dssh, and try a query against UV.ACCOUNT, such as SELECT * FROM UV.ACCOUNT; Let us know what error messages appear (if any). Then try naming columns in the...