DSXchange

One of the job aborted when I ran the Controller job because it could not open the file in one of the foler. Actually, no such file exists in that folder.

DSD.SEQOpen Failed to open 68159.csv in directory d:\Indata_Arch
STATUS = 2.

I had reset the job many times in Director, but status remained as Aborted only. Finally I compiled the job, hence status changed to Compiled from Aborted.

Please let me know, why is this occuring.

Thanks,

Is the error repeatable, i.e. if the job aborts now will a reset put it back into a runnable state? When you did a reset of the job, did it put any messages into the job's log file?

Generally, when we reset a job, which is in aborted status, status will change to reset. For me, I have a contoller job, within that I am calling two controller jobs. When the sub job aborts, automatically all the parent jobs are becoming to aborted status. But when I had reset, none of the jobs' status is changing to Reset. And neither its logging any message in the job log when reset is done.

The reset will only change the status of one job at a time, not the parent or dependant jobs. Or perhaps I misunderstood your explanation. I can't recall a reset not doing -something- to a job in a project where everything else is working. If you don't have a busy machine you can clear out the contents of the project's &PH& directory and try your reset to see if a log file gets created.

I am not able to understand whats happening here. When I am trying to run the controller job (which is in Finished Status), nothing is happening. It's not showing the status as Running, but its running and after sometime the "Started" and "Last Ran" times are getting updated.

Please advise me.

Will the refresh interval affect this?

One more thing is Controller job's "Started" and "Last Ran" times are showing less than that of sub job. When is this possible? Controller job is calling these sub-jobs, so when the sub-jobs are complete, bassed on that time, last ran time for Controller job should be updated.

Error code 2 means "file not found".
Either d:\Indata_Arch\68159.csv does not exist when the job runs, or you do not have sufficient access privilege to the directory to determine whether it exists.

But why the last ran time of Controller job is less than that of sub job last ran time. Sometimes, when I start running the job, its not running and status is still showing as Finished. Whi is it so?

Because if the job sequence aborted it may not have had opportunity to update its runtime information (status, date/time, etc.).

I am running the main controller job. This job contains, two controller jobs within. Though the main controllre job's last ran time is 10:32 PM, the sub jobs are running and have the start/last ran time varying from 10:32PM to 10:40PM. How come this is possible. Atleast the last ran time of the Main controller job should be updated to 10:40PM.

I am unable to figure out this issue. Sometimes, sub jobs will be reset, when job aborts.

Please advise me on this.

Thanks,

I am facing this issue again. Though controller job is running the other jobs, status of controller job is showing as "Finished" and sub jobs status is changing correctly, when they are running/completed such as either Running or Finished respectively.

Why is this variation of status for Controller job and sub-jobs?

Seems like it is time to call Support and ask them.