DSXchange

You can have a log if you like, by changing the startup characteristics of dsrpcd. But this process VERY rarely has issues. Log is used primarily for troubleshooting - otherwise it is just another way to fill your disk.

Wherever you ask it to be created. Typically, and by default, it's not created.

I think I know what the rule is, but will await the original poster's response.

A meaningful subject line would have been good, too.

Are you giving this expression as the file name or as the filter command?

DataStage has a far richer range of connectivity options and transformation capabilities than does ODI. Its graphical user interface is, to my mind, easier to use, understand and maintain than the ODI one. Finally, in DataStage one does not need to become an expert in the use of PL/SQL scripting (or...

What other diagnostic information was generated? What's in the install log, for example?

Wrong on so many counts. JobLinkStatistics is something written at your site, therefore we can't comment on it other than by surmise. The same is true of the other parameter ResurrectLogFile. The dsjob command with -jobstatus option returns the return status of the job, which you can find documented...

A client connecting to a DataStage engine engages the DataStage RPC mechanism requesting a process running the dscs (DataStage common service). This is looked up in the dsrpcservices file and the relevant executable (dsapi_server) started as the agent process of that particular client connection. Am...

The Merge stage in server jobs reads two files, the pathnames of which are given in the stage properties itself. The stage type does not support inputs.

So, what are you trying to accomplish?

Use the DataStage resource estimation tool.

Welcome aboard. You don't want to select in your target. You need a design like ODBC | V SeqFile ---> Transformer ---> whatever Let DataStage generate the SQL in the ODBC stage. Mark the column that has to be in the WHERE clause as "Key".

Are you using a static user name for executing DataStage jobs in ANALYZERPROJECT project? If so, ensure that a valid user name and password are provided in this frame. Also check that the DataStage credentials are correct for the engine tier on which this project resides.

Correct forum. This message comes up when you attempt to validate the analysis engine settings in Information Analyzer either the global ones in the Home pillar menu or in the Project Properties workspace for a particular project. It's usually caused by the user ID being incorrect. Are you using a s...

For the date portion use a format string of "%yy%ddd". You're on the right track.

Do you have $, # or _ character in your password?