DSXchange

How about just encapsulating this command as the filter command in your Sequential File stage?

Director has a Print to File option.
You can create a "dump log to file" routine.
You can use dsjob to dump the log contents and redirect its output into a file of your choice.
There's three possibilities.

The DataStage job log is a database table in the Repository - it is not a file. The best you can do is to dump the log into a file - you can not "maintain" the log in any sense.

The Double has 31 significant digits.
Decimal has 26.
The message tells you that you can't shoehorn the one into the other.
Can you investigate reducing the size of the Double?

Of course you can. You will also need a specification, and therefore some logic, to define what happens with any out-of-range values.

Use the Configurations editor to test your configurations file. If that tests out OK, we've eliminated one possible cause of the compilation problem.

Not in version 7.
Create them separately and combine them afterwards.

The first is an alert, about which you can search for information on the forum. The second is a message apparently from a Transformer stage. You will need to provide a lot more information about what this stage is doing - and some job context information as well - in order for us to have any chance ...

DSJE.BADPARAM means that you have tried to use a parameter name that is not defined in the job. Step back and simplify. Don't try to use environment variables' values as default values. That doesn't work. Use environment variables as job parameters. Click the Add Environment Variable... button in th...

The dsjob executable is in .../DSEngine/bin, not in .../DSEngine.

Why not just have the job sequence read the file into User Variables and use those downstream? There are a couple of techniques. One is to read the entire file as a string, parsing out the param=value pairs. This is easily done in a Routine activity. Field() functions can then be used as the derivat...

Do you REALLY have an "=" character in a pathname? What is the value of APT_CONFIG_FILE environment variable?

Why not let Windows Explorer search for it?

Where do you get your metadata? Ask the mainframe folks for the COBOL file definition, and import the table definition from that. At the very least it ought to match the data you are receiving. Then you might contemplate using either a Sequential File stage with fixed-width format, or perhaps a Comp...

Nah. Just parse each row into columns then use a Pivot stage. Too easy: it's an exact fit. Where are the data sourced?