DSXchange

ArndW wrote:But, if there are only 2 updates per 100 records then doing it via the reject method might be more efficient; it depends upon the ratios.

True.

I am not near the product at the moment, but I am pretty sure there is a transform function in px transformer to get the enviornment variable. Use that, instead of going down the job parameter path.

Its the classic Insert/Update logic. Do a join, get the updates, transform the value and do Insert Updates via two links.

You can use PROJDEF as the values and specify all your job parameters as environment variables. This way you only have to change th values in the administrator, one place, instead of a zillion places.
The other way is using DSSetParam() function. Thats used with job control.

You can provide the constraint in the transformer itself and avoid the use of Filter stage.

You can also use Before Job ExecDos, OS command to invoke the sql utility to connect to your database and execute your script. That is another way too.

Email the Webmaster. Email address is under Contact

First of all go and check if the server is actually running. You can either do a command line ping or go to control panel and check if the services are running. A re-install will not help if your server is not running in the first place.

Stick to the standards. Use a job sequence.

.....I said so, the energizer bunny

Depends upon in house standards. Almost all the places I have worked in, use Version Control to elevate the jobs. While doing so, they get compiled. At one client, our admin was doing the moveup using the manager and did a multi-job compile. I like to get the executables built. But no harm in gettin...

Go for it then. As I said before, I wouldnt go for something thats a trial, or might break someday. If it does, you cannot even go back to IBM, as they will point out to the same line that Craig quoted, that it is not supported.

Not from unix. Deploy your jobs with the executables and you will not need to re-compile them.

Can you post the link to Micheal's post?
The manual says pretty clearly that it wont work, or atleast not supported. I wouldnt go for something that might break some day.

How are you running the job? Via dsjob or through director/designer?
What is the type of job parameter, is it encrypted or string, when you pass the encrypted password?
WHat happens when you pass the string 'pwd123'? Does the job succeed?