DSXchange

Or tab-delimited. Tabs in data are fairly rare, since tab in Windows applications moves one to the next field.

A simple check for existence (no timeout) can be effected with an Execute Command activity. Windows: DIR /B pathname UNIX: ls -1 pathname where pathname is the pathname of the file whose existence is to be checked for. Create an OK trigger and an Otherwise trigger on the Execute Command activity, an...

Less effort once.
Then you'd probably complain about the relative "performance".

The secret of the Modify stage's speed is its simplicity. By getting you to do the work (fairly low-level specification), it needs no particular overheads.

To reiterate, you must design whatever restart capability is desired.

In a job sequence you can certainly design to run a job over and over till its exit status is "Success" but there's a danger of that being an infinite loop.

You're on version 8. My current client isn't. You research it and post your findings.

Yes. If you right click on the job name you will get a menu from which you can choose a Compare tool and compare against another job.

This is new functionality in version 8.

What will happen is whatever you designed to happen. If you want restart from a particular point you have to design that in. If you want to keep records of how far the job got, you have to design that in. If you want to check the target to see how many rows were committed by the previous run, you ha...

string_from_date() function

No. That's what "defunct" means. They are not connected to anything any more.

You could browse through your job logs and status detail views trying to match the process IDs but the benefit would not be worth the cost.

Check that the APT_ORCHHOME environment variable is set to the pathname of the PXEngine directory in DataStage.

In particular what stage type are you using?

In particular what stage type are you using?

The query given by DSGuru2B can be run from the Administrator client Command window. Note that all the identifiers are upper case and the terminating ";" character is required. Job name is case sensitive.

Locate is a statement in DataStage BASIC, not a function that can be used in a parallel Transformer stage. Modify stage has a useful lookup_int16_from_string() function if the list of values is fixed, which yours appears to be. It can be constructed to set a default value if the lookup fails. Otherw...

Why did you not clear the lock in Director?