DSXchange

You get that after you launch the application or after you give your credentials and click OK?

That's a Microsoft / client side error. First thing I'd try is reinstalling the VC software. You may need to completely uninstall, reboot and reinstall to get it working right.

Can you not simply check and see if you have a dsadm user on that box? Does the following command return anything? grep dsadm /etc/passwd We'll know where to go after that depending on the outcome. Also, do you have access to whomever installed the Server software for you? You may need to... interro...

Somewhat - it's not about UNIX admin rights. It's about having DataStage admin rights and that is granted automatically to the dsadm user. Have you had to make any changes using the Administrator tool? For example, setting the client timeout to 'Do not timeout'? That required either dsadm or root to...

You have to have created an Administrator userid on the DataStage server machine before the product can be installed. It is assumed to be 'dsadm' but can be overriden nowadays if you want. I doubt that happened for yours. That userid - dsadm - is the one that needs to be used for this. That or 'root...

The person who installed it originally installed it as root, but then changed all of the file ownerships to user dstage. Ignoring that little nugget - you need to use either 'dsadm' or 'root' to start or stop the DataStage server. Or more properly, use your 'Adminstrator' account which is no longer...

666? The devil you say!

No one is suggesting you can import from the DTD, we've already established you can't. Ernie suggested using something like XML Spy to convert your DTD to an xsd - with the caveats he noted.

No. Sorry, but the MCM *is* your only answer here - other than having two PCs that is. What is your issue with it?

videsh77 wrote:Modifying jobs in Sys Test is BIG NO.

No time for a proper answer, but wanted to point out that no 'job modifications' would be involved in this. You simply need to use the 'Set Defaults' option from the 'Job' menu in Director to override the default value of the parameter.

You mean concatenate, not add - yes? If so, generate the number and use the colon (:) concatenation operator to stick them together. Perhaps you need a surrogate key generated, perhaps it just needs to be the @INROWNUM. You'd have to tell us.

You can't. Rewrite it as 'INSERT INTO SELECT FROM' style DML and you should be fine.

Or... just build a job to do that.

Well now... that's a little different - they are addressing the problem with an acknowledged 'significant change' to How Things Work in this patch it would seem.

All the 'patch' could do is increase the timeout, I would think - is that what you mean here? It won't address the fundamental problem.

It's an environment variable, so would not say you couldn't "use" it - but you certainly couldn't for the purpose that it was intended.

Don't worry about the 'Direct Path Context' part - this is your issue:

ORA-00942: table or view does not exist

Verify your table and schema names in the stage.