DSXchange

Have you, or has anyone else at your site, modified the ''dssendmail_template.txt" file?

File system permissions is the only way I can think of. A protected project is protected against change, rather than against running.

Parameter defaults are stored in RT_CONFIGnnn for job number nnn, so RT_CONFIGnnn may be the best candidate for tight security.

Everything you do in DataStage is internal to one project. Projects are independent of each other. The dsjob command sits outside of DataStage, which is why you must provide project and job name to most of its sub-commands.

I doubt, in that case, that you're reading directly from the .XLS file.

No. Twenty five stage variables is not a lot. Go for it.

This is a stupid requirement. What if the job aborts and you can not write to the sequential file because the disk has filled? There is no way that you can avoid "data loss in the sequential file" in this case.

Resist stupid requirements.

It depends where you've set the pertinent environment variables; it may be in the dsenv script, or you may have specific-to-project environment variables set in the Administrator client (and stored in the DSParams file in the project directory). Then again, your jobs may set these as job parameters ...

Not until version 8.1.

Why should the job abort? Kill anyone who stops it manually; we find that this prevents a second offence.

What do you mean by "performance" in this scenario?

Transformer stage to accumulate fields with non-empty values followed by a Remove Duplicates stage to pass only the last record in each group.

What do YOU mean by "extended"?

How many times do you propose to ask this question?

You need to specify the name of an SMTP server in your Notification Activity.

How did you invoke NextSurrogateKey() function?