DSXchange

This can also occur if the job is open in Director in log or monitor view.

Are you talking about the XMETA database here, or a local DataStage project repository, or something else? What is meant in your question by "new environment"? Basically, the answer is going to be "export project, import into new environment". A fresh install of the database or of DataStage server (...

In version 7.x you click on "Usage Analysis" in Manager, having selected the job about which you are enquiring.

What's changed?

Is that the entire error message?

Have you tried recompiling the job?

Apparently it was from IBM (short for IBMDS).

Sort the data by Column 1 and Column 2 and have the Sort stage generate a key change column into Column 3.

They implement DataStage Repository tables. The vendor has not provided complete metadata; what there is can be obtained by executing a LIST.DICT command against each from the Administrator client command window. You do not clean them up. Ever. There is no need to. Individual job logs are cleaned up...

The name of the file is DSParams (no suffix), not DSParams.txt. So the ones you are seeing in Administrator are probably in DSParams but not in DSParams.txt. DSParams.txt is nothing; you may safely delete it.

In the job log you can see that DataStage submitted the Open command to the database server. Whether or not it got executed there is outside of DataStage's control, if the command to execute the stored procedure was correct.

Because you can edit it, you can also damage it. Be careful, and take a backup copy first.

Then you have to treat it as not fixed width. Read it as a single VarChar column, and parse it within a Transformer stage. Or pre-process the file to insert delimiter characters, using either a shell script or a BASIC routine.

Execute the following commands. Edit your SQL query to suit your requirements. The first command establishes a "print channel", while the LPTR keyword in the query directs output to that channel. I have used channel #4 in the example; you can use any number between 0 and 255. SETPTR 4,132,200000,0,0...

This is not a DataStage question. You can call any command (a BAT file is just one kind of command) from Autosys using Autosys scripting.

The obvious first question to ask is whether the directory /opt/IBM/InformationServer/Server/Datasets exists and, if so, whether the executing user had rwx permission to it and/or the /opt file system was full and/or whether a quota in or above that directory had been exceeded.