DSXchange

Welcome aboard. We are not talking about the Command stage here; we're talking about the Execute Command activity in a job sequence.

Check the "delete file before create" check box.

To get everything back in sync if necessary, execute a command such as

You can not do this. DataStage has its own set of exit (status) codes. 1 = finshed OK, 2 = finished with warnings, 3 = failed, 21 = has been reset, and so on. You will need to write your result, if you want something else, to some kind of persistent storage. If the -jobstatus option is used, then th...

No matter what you do, the same volume of data needs to be transmitted across your network. Perhaps you could consider compressing your flat files prior to transmission, and uncompressing them afterwards.

CASS is US-only. Others are available, for example SERP for Canada.
These databases are refreshed. I don't currently have information about the interval; your vendor could provide that.

Create a "time" table with daily granularity. You'll appreciate having it.

Could it be, perhaps, that the string returned by the ls command is too long?

What do you mean by "standalone"?

DataStage routines execute only in the DataStage environment. Ultimately they must be invoked from a DataStage job. Even the Test grid writes a small job "on the fly" to invoke the routine under test.

Do you want to use a job, a command or a routine to dump the log table contents into a text file? Search the forum for techniques. There are many. You can even count the warnings in a specific time range without dumping the contents to a text file, using the DataStage API function DSGetLogSummary (o...

Press F1 when you're in the Designer or Manager client, and use the index to find DSGetJobInfo().

Or why not download EtlStats from Kim Duke's web site which will do all this data gathering, and put the results into a table, for you?

It IS the right one.

The -u option for the sort command means "unique" - it returns unique values of the sort keys.

Therefore, if it is not giving you the answer you require, then you are not specifying the sort command appropriately.

Don't you believe in Search?

It's not like you're a newbie here - you have more than 100 posts.

That very question has been answered twice in the last two days.

Don't push! It's the middle of the night in the USA. If someone knows an answer they'll post something. When they're awake.

No. of rows processed is captured automatically, and is logged in the "active stage finishing" event in the job log, is viewable using the monitor, and can be captured with DataStage API functions (which includes the dsjob command line interface). No. of rows affected is something you'll need to ask...

Please post the exact error message. More to the point, read all of the information contained in the error message. Then check thoroughly the properties of this link, particularly the file name property, and check that you have all the requisite permissions and the like for that particular file. Wit...