DSXchange

Hi,

Few of the web service enabled quality jobs which were running fine earlier aborted.
And the compilation failed with below error We will try to reimport the dsx or make copy of the jobs and try to recompile.
1. Would like to understand why the job status file got corrupted?
2. How to check administrator, there are no RT_LOGS number
3. The webservice jobs are using Isd stages. After server restart do these jobs try to run automatically, I could see multiple invocation id in abort status until any instance is in running state.

Thanks

I would guess your log file logged a HUGE number of warnings or possibly multi-instance aborts, probably exceeding 2 GB of job log details. I've run into that exact case and error before. Enable auto-purge settings.

RT_STATUS1 tells you the job ID is 1. You could try command COUNT RT_LOG1 to see how many detailed job log entries you've got.

To avoid crashed job status with ISD related jobs when stopping or bouncing the server, make sure to stop each ISD application first. This can be done from the command line and scripted. Do the opposite after startup.

Do clear the log. It's just good practice to do so. However, the hashed file that has become corrupted is RT_STATUS1, not RT_LOG1.

If you have administrative tools enabled in Director client, you can clear the job's status information from there. If you do not have these tools enabled, then execute CLEAR.FILE RT_STATUS1 (for example from the Administrator client's Command window for the project).

Then you will need to recompile the job before it can be executed again.

And before you do that, you may need to change its status to stopped via the Information Server console, if it's exposed as a web service.

thanks for the replies.

After trying to view the RT Log files which caused the issue, icould only find the below error in all the jobs.
1) Is this error is related to server down? we are just trying to identify what caused the huge logs.

2) What happens actually when the server restarts?

Before Server restart- To stop the jobs dsjob commands or do we need to undeploy them

After restart- Do we need re-deploy or just start commands would suffice?

Thanks

As Ray pointed out, it wasn't your job log that got filled up, rather its status file overflowed. I'm not sure what would cause that.

If you were to reach out and stop the DataStage job, ISD would notice and immediately spawn a new instance.

To script stops and starts, you need to undeploy and deploy. Here is a UNIX example of the syntax you can use within shell scripts.

ISDAdmin.sh -authfile <AUTH_FILE> -action undeploy -application <ISD_application_name>

ISDAdmin.sh -authfile <AUTH_FILE> -action deploy -project <ISD_project_name> -application <ISD_application_name>

Thanks for the details.

In addition to the status file overflowed, for the ISD jobs we could also see the /tmp folder getting full.

What are these files? Are there any harm in removing these files and why do they go to tmp?

Are there any settings we could change the directory

ad1.proj.ISD_jobname.input
ad1.proj.ISD_jobname.output

Thanks

The TMPDIR environment variable may be set to any path you like. You can change it using DataStage Administrator, per project. After you set a new one and run the ISD jobs, or redeploy, then remove the old tmp files.

we are working with PMR team to figure out why ther server went down.

After clearing up the tmp and logs files, imported the dsx again and the jobs got compiled.

Thanks.