DSXchange

I've not seen that particular error before. What precise version of DataStage/QualityStage are you using?

The itag is a unique identifier used as part of the shared memory keys used by the engine. For example, the shared memory in which the locks are stored has an identifier of 0xadec7521, the itag is "ade". Installing with a different itag, such as "adc", would mean that the shared ...

You can not do it with a Hashed File stage. You can, however, do it with a UniVerse stage that references the hashed file through a VOC pointer.

Not quite. On any UNIX system it's /etc/hosts

(On UNIX, \etc\hosts would become etchosts.)

antonyraj.deva wrote:What exactly is the "X" in 7.5.X?

Just a placeholder. 7.5.X might represent 7.5.1, 7.5.2 or 7.5.3.

Did the error message include SQLSTATE and DBMS Code? If so, you might search for these on the internet. It seems to me that there is a finite limit imposed on the mainframe application server on the number of concurrent connections, and your connection attempt was thwarted by that limit already hav...

Only the obvious one - in the Before and After commands.

Schema file can use

It is highly annoying to get the "You must select a value in the server list." message because one forgets to select the only item in a list of one. Can the list dialogs be made cognizant of the fact that there's only one item in the list so that, when an item is selected from the Tasks li...

This thread and this companion thread seem to be arguing for a "storage search list" - something akin to PATH and LD_LIBRARY_PATH, but for storage. I discussed this off line with the OP, who agrees with that assessment - that storage could only be allocated in directories in the search pat...

Probably that the job HAS finished but for whatever reason has not updated the status table that is read by Director. Or maybe you have a really long-running after-job subroutine, or your after-job subroutine set its ErrorCode argument to a non-zero value. This is an occasion for the Clear Status Fi...

Yeah, that's a good plan. Other time zones don't have whole hour differences from GMT (Nepal, for example, or India).

... and absolute power corrupts absolutely.

Still verify that the correct values have been passed, in the "job starting" event for the job itself.

Like any batch process, a DataStage job will consume as much CPU as it can to get the job done as quickly as possible. Since streaming I/O is used wherever possible, there are no waits on I/O to preclude use of the CPU. That you aren't using much memory means exactly that you aren't using much memor...