DSXchange

You could use the "uv" program to kill. Just note down the process id in your unix server.

That's interesting! Care to elaborate?

The Abort statement in your routine is getting executed because you are taking the Else clause of OpenSeq. You can take the Else clause of OpenSeq even though you open the file successfully. Search for the OpenSequentialFile routine for documentation. You have not coded for this possibility. Avoid u...

The routine itself has to return the file handle. But you could use the system variable @USER.RETURN.CODE, or one of the system variables @USER0 through @USER4, or the invoking job's user status area, as ways in which to return the flag you require. You could also return the flag through one of the ...

Try View > Refresh. It may or may not work. Otherwise, open a new Manager, which will force the tnsnames.ora file to be re-read.

If your UNIX admin doesn't understand what those two redirects are doing - you may need a new admin or to demand to see your admin's certification!

It does do a lot of logical opens but, as you say, you would hope that many of those would be handled by the rotating file pool. This is the nature of the beast; they need to guarantee that the file is open, even though coming from what is essentially a stateless client. How do you propose to index ...

You've mismatched the service names and descriptions. The DataStage resource service manages DataStage's shared memory and processes logins, allocating unique user numbers. If this is not running, then DataStage is not running. The DataStage telnet service exists because Windows does not have its ow...

The warning indicates that there may be longer values in your string than can be accommodated in a decimal of the indicated precision. For example, if the data types are string[16] and decimal[10,0] then you would get this warning. Solution is to get the metadata right, or to pre-empt the possibilit...

It's better in version 7.5.

It doesn't look like a DataStage error to me either. What database are you using?

u009/etl/Ascential/DataStage/Projects/Eclipse/dsr_sched.sh /u009/etl/Ascential/DataStage/Projects/Eclipse project name /u009/etl/Ascential/DataStage/DSEngine location of $DSHOME ImportRejects job name 0/0/1/0/0 control values for wave, logging 1 run mode (1 = normal, 2 = validate, 3 = reset) >/dev/n...

Of course, 3 months can be anywhere between 90 and 92 days. Other variations are possible if you're dealing with the years when "they" fiddled with the calendar. A more robust solution would manipulate the month number and, as a possible consequence, the year and day numbers.

What is the volume of data? In particular, do your Data Sets begin to be segmented at the 2 million row mark? (You can view segments in the Data Set Management GUI after the event.)

Welcome aboard! :D

Sparse lookup is documented only to work with DB2 and Oracle stage types (at least in version 7.1).

Bhavna, it sounds like your attempt at removal has been interpreted as "replace with 0". Try re-loading the metadata from your Repository.