DSXchange

1. On the Tracing tab select all options except "report row data".

2. Have your DBA monitor what's executed.

DataStage uses "prepared SQL".

Not sure that it's indexes - there are no indexes on the log tables. It may - particularly since you describe the problem as intermittent - that your system is simply too busy for its capacity at those times. Another possibility is that you're running out of slots in the T30FILE table; what is the v...

Have you really got two left parentheses and only one right parenthesis?

Note that User Variables activity is not available until version 7.5.

If that's the case, then cat $filename near the end of the script would push the contents of that file onto stdout, ne c'est pas?

There's not a lot more we can suggest by mind reading. Are you able to post the code of the shell script? Then we can see whether it's trying to do something that would result in 0 rows appearing on stdout.

Most stages' input links also allow you to specify sorting and removal of duplicates, so you can get by without either of the Remove Duplicates stage or the Sort stage. So the choice is really about using the lowest impact tool; if your data are already sorted, then the Remove Duplicates stage is pr...

It's always a good plan to check, and not just for DataStage software.

Yes. The .*.adm files are where the groups associated with each role are stored.

Thanks for the Inputs. Please let me know what this error means... DSD.SEQOpen GCI $DS.SEQOPEN error 11. Thanks This error means that the sequential file cannot be opened. Check again. "Looks good" = insufficiently thorough. Do you have execute permission to every directory in the sequemntial file'...

Your strategy is OK. But... Only the production staff is allowed (authorized) to promote to the Production server. How are you going to restrict access to the Production server? You basically have two choices; to use the role-based mechanism with different groups for Production, or to make Productio...

There's nothing within DataStage itself, but you can have a continuously-running process checking email (send SMS through email gateway) and generating an appropriate dsjob command.

If you have version 7.5 you can also have the Director client on a PDA device, and start jobs that way.

When you uninstalled the clients, did you check that it had been removed from the Registry?

The same job runs correctly in test environment which is also DS7.5 but it aborts in production.

You must tell us what's different between the two environments (which may be DB2 client configuration).

"Nothing" is not the correct answer.

Did you mean or does your dsadm script execute dsenv?