DSXchange

The user's environment for DataStage jobs is set in dsenv (on UNIX systems) and may also be set up in .profile, /etc/profile and similar login scripts. Environment variables may also be set in scripts that invoke dsjob.
This must occur before the run request for the DataStage job is made.

That doesn't achieve much. Is there any way that the email address can be barred?

You're misled/confused. When the job starts the values of job parameters are read, and can not be changed subsequently. When you request a job run (via Director or any other means), you can supply a replacement value for the job parameter. If you change the value of the environment variable subseque...

Can you please ask your lead why this is required? And post the response here?

A perfectly effective command line interface for DataStage is supplied - why re-invent the wheel?

Logically the next thing they'll want is that you re-program all your DataStage logic in Java. Resist now.

It may even be that you lack x permission for the script when executing from DataStage.

$ENV picks up the default value from the user's environment.

$PROJDEF picks up the default value from the project; that is, the values set in the Administrator client and stored in the DSParams file.

And some of us like our weekends. That's why the facetious response. I don't appreciate being hassled (on any channel); I will post if I have anything to add; my silence either means that I have nothing to add or that I don't have the answer. Sometimes I am working at server-only sites, so I can not...

pump307

That the link in your sig leads to a gambling web site is not, in my opinion, within the bounds of good taste or the intent of this forum. Indeed, had you posted it in my country you would be guilty of an offence. Please remove it.

I'll play. Anybody there WHO?

You can append even if the old version is in the DSX file. Do one, and note that the point where appending begins is marked by a comment in the DSX file. When you import, it's last in last out, so that the version closest to the end of the DSX file ends up being imported.

There is an excellent book out there called The Elements of Programming Style - although it concentrates on language-based coding there is a lot of good advice, most of which can be generalized to graphical programming. Modularity is one of the main principles espoused, primarily for ease of underst...

I'm fairly certain this has been answered in the past, probably in a post with a more precise subject line. What does searching the forum reveal?

Widening the lock tables, which is what Stan suggests, reduces the probability of a clash of two record IDs hashing to the same lock-controlling semaphore. It will not work in this case, because the lock ID ("RT_CONFIG2660") is identical (and will always therefore hash to the same lock-controlling s...

Probably your system is overloaded. DB2 needed to start a process but failed to do so within some timeout limit. Try again when the system is not so busy.

csrazdan, you get this information in the training classes, and in the Orchestrate manuals. kumar_s, it's one conductor process per job, one section leader process per job per processing node, and one player process per stage per job per processing node. Review my earlier posts and do the arithmetic.