DSXchange

can you try saving the access to a csv format file?

they ran successfully after i restarted the server. i guess the issue was with some hung jobs.

use the iconv and oconv functions to convert. check datastage help for usage

a job can hang due to numerous reasons. If datastage shows job as running, there is a very minimal chance that the job has aborted. meanwhile to check if the job is running or not see the following: 1. If any any file is being written. check if the file size is still increasing 2. goto director and ...

Use "nvarchar"

SQL server does not support longnvarchar

as sam said. try and see if the job run through the director or not

what is "MANAGEMENT" here?

did you get this type of error ? can you please paste the error message.

From what i know, the routines can be invoked multiply.

edited as per ray's suggestion: <CODE> $INCLUDE DSINCLUDE DSD_STAGE.H $INCLUDE DSINCLUDE JOBCONTROL.H $INCLUDE DSINCLUDE DSD.H $INCLUDE DSINCLUDE DSD_RTSTATUS.H Deffun DSRMessage(A1, A2, A3) Calling "*DataStage*DSR_MESSAGE" Equate RoutineName To "JobLogMail" * Passing JobName for...

cool.

ya my mistake.

You probably need to clear all your archive. there is nothing else hidden in datastage that can increase your project size.

Are your exception handler and the jobs connected?

Just ensuring.

Delete all the datasets. You can get the path where the datasets are stored from your config file.If a job aborts, datasets dont get deleted and stay there.

Apart from that there can be some irrelevant project archives which you can look to delete.

its more of mastering unix than mastering datastage.

Datastage has only few commands to be invoked to run, stop or reset a job.

however you can find the datastage commands in installation docs.

yeah i know. will check and update

If something was a bottleneck then how come we were able to run 17 jobs simultaneously at some point of time. anyways i will try and run all of them in night ensuring no other user is connected.

will update this post. thanx