DSXchange

Hi, I have an error, but the log doesn't point out what the error is. Actually I don't get a fatal message at all, the job simply aborts. The job is a sequence job. I'm wondering if the phantom dir will provide more info. I can get drill down to the PH directory, but don't know what to do or how to access once I'm there.

If you reset the job (not recompile, reset), any diagnostic information in &PH& should be transferred to the job log, in an event called "From previous run...".

Otherwise, &PH& is a directory within the project on the server. The file will have a name made up of the program name (DSD.RUN or DSD.StageRun for server jobs) followed by the pid, date and time in DataStage internal format.

Files that are only two lines long don't contain any useful information (the events are "started" and "finished" - while that's reassuring to know, it's not that helpful in diagnosis). So look for larger files.

Stone
Did you check the logs for the individual jobs . The fatal error may be in there. Sort the jobs by start time and look for the first aborted job.
Thanks

Do a "ls -altr" to order the file listing, listing the most recent edited file last. That way, you can pinpoint the potential files that was created by your job. Look at the timestamp for the file and the timestamp of the job's run.

"Otherwise, &PH& is a directory within the project on the server. The file will have a name made up of the program name (DSD.RUN or DSD.StageRun for server jobs) followed by the pid, date and time in DataStage internal format.
"
How about parallel jobs?

Yes, parallel jobs too.

DSD.RUN is a generic "job starting" routine that also appears for parallel jobs.

Beware that ampersand is a special character for the shell. You need to escape or hard quote. For example: