DSXchange

Create an additional set of "columns" upstream, containing the column names, and pivot these columns also.

Your specification also needs to define the expected format of the file. Sure it contains parameter=value pairs but may it contain anything else such as comments (what do these look like) or blank lines? Are comments permitted following a parameter=value pair. Are spaces allowed around the "=" chara...

It is highly unusual to have decimal numbers in the exponent for "scientific notation".

That said, the calculation is mantissa * (10 ** exponent) - in your case, 7 * (10 ** -0.002)

In particular the job sequence's parameters are available to all activities in the job sequence. They do not have to be re-declared in a User Variables activity.

Variables declared in a User Variables activity are only accessible to activities downstream of the User Variables activity.

If you have MKS Toolkit or some other UNIX emulator installed you can also use an mv command to rename the file in an after-job subroutine ExecSH, using backquotes to capture the result of the date command.

Is this the same question as this one?

Posting the same question in multiple fora does not get you any better answers, and annoys those who have perforce to re-read the same question.

Please describe job2 more fully - in particular all stage types used, and any processing done.

This can be caused if entries have been purged (manually or automatically) between the call to DSGetNewestLogId() or DSGetLogSummary() and the call to DSGetLogEntry().

That is, we're more likely talking data "corruption" here than physical corruption.

Hire somebody who CAN produce the DataStage jobs quickly.

Watch them and learn. Have them then mentor you in the techniques used.

There is no restricton - the query Engine is obeying the field widths specified in the metadata (file dictionary). This is How It Works. If you want something different, YOU have to take control. Try this. SELECT EVAL "CONVERT(@FM:@VM,'~|',@RECORD)" FMT "132L#132" FROM ha...

Urgh. Given that your server is UNIX, you are in for a messy path. You need to remotely execute a dssh command with in which you can execute the SQL.

Check also in the global .odbc.ini file to see whether tracing is enabled there.

I suspect an Intel chip is required also, but am not 100% certain on this. But the message is definitely coming because 7.5.0 does not have support for compiling or running parallel jobs on a Windows platform. As was suggested, you need either version 7.5x2 (the "x" is part of the version number) or...

So instead of using the date command, you use the cat command and tr any newline characters from it. Something like

Spend some time verifying whether Trim("____") returns " " or "". You may need slightly different logic, perhaps testing against " ", or perhaps using Convert() rather than Trim().