DSXchange

Are you looking at the correct log?

The example record schema given above is correct for CSV files (provided that these are well-formed).

Take a look at the available Transforms, particularly MONTH.TAG, MONTH.FIRST and MONTH.LAST. Since the latter two return internal format dates, if you subtract 1 from the result of MONTH.FIRST you have the date of the last day of the previous month. If you insist on working with Iconv() and Oconv() ...

Which NULLTOZERO is this?

The supplied Transform is called NullToZero (and it's case sensitive).

If you have your own NULLTOZERO routine/transform, I'd suggest you test it more thoroughly.

That's what I intended - the "telnet before command". Of course your mainframe security probably doesn't allow telnet so you may need to set up a more secure (ssh) approach. But it has to be in the same session.

@OUTROWNUM is the record's sequence number in the output file.

@INROWNUM is the record's sequence number in the input (source) file.

No, you're not right. Persistent Data Sets (the non-virtual kind) are not cleared. However, the original question relates to scratch disk, which might be used for any kind of temporary file, including "paging space" for virtual Data Sets. Scratch space *should* be cleared automatically but may not b...

Virtual data sets are created in memory and their control files (xyz.v) are created in the project directory, being automatically deleted when the job ends.

decimal_from_decimal[trunc_zero](inputcol)

As you get to each of these properties, read the property help that displays when it is selected. This should inform you about any default value applicable to each property. The same information should be in the relevant manual.

That's probably because you never changed the supplied configuration file, which puts both disk and scratchdisk resource into the DataStage Engine file system.

The tool is in $PXENGINE/bin.

Read about it in the Orchestrate User Guide - one of the "OEM manuals" you can get from IBM through your support provider.

Type in the command with no options to get a usage (syntax) summary.

80 characters is a common limit, dating back to the days of punched cards. You have to find out what FTP option (it could be a "before" command) you need to use (on your system) to override this, so that your GTG has the desired line length.

Yes, because your descendants will be waiting for that transaction to complete. Red Brick does not support transactions at all - this is one of its strengths. DataStage version 8.1 has a Distributed Transaction Stage that might come close but, since version 8.1 isn't out yet, I can tell you much abo...

Then try it. Under the conditions that I specified.