DSXchange

kaps - when fuser doesn't return anything it means that no process has the file open. Check your job parameters again to see what the output file should be. If you are certain that you are looking at the correct file then you should check to see if the job is actually still running by using "ps -ef ...

You need to create your own after-job subroutine; and then use a function such as DSGetJobInfo() from inside that subroutine.

Please enclose your program in "code" tags to make it legible.

You code issues a call to DSWaitForJob(), this is why it executes in sequence.

if the job is still running then your data might be buffered and not flushed to disk. You won't know the actual file contents until the job completes.
Try doing a 'fuser -fux {filename}' to see if your DataStage job actually has this file open for write; you might be looking at the wrong file.

Dang - just as an aside, you can mix quote characters in DataStage, so your command could read:



If you use that, does your error remain the same?

Have you tried replace the "BINARY" with "CHARACTER" in your .dsx file and then importing the table definitions?

Nitin, this question and your other post in the Server forum are not the type of queries that DSXChange expects. There is nothing wrong with being a beginner, all of us were absolutely 'green' at some point in time. But it is expected that participants read the documentation and experiment with prob...

Delete your empty file. Re-run the job with the correct parameter setting (confirm the setting in the director log entry for the job). Is the empty file created again? Do you have an after-job subroutine that might touch the file?

If the SetNull() and reject set are your only problems then it still doesn't explain why one user can compile and another cannot. I would check your environment settings and permissions (particularly group permissions).

Can we get a return values in routines or not? Yes, routines can return values How can I run a routines in windows & unix enviornment? Yes, DataStage server routines will work across all supported platforms How will I create a before & after sub routines? Follow the instructions in the docum...

There are various types of errors, and not all of them can be detected or discovered the same way.

Recompilation usually does a good job of either detecting or eradicating errors.

You could set your default umask to create the file with the appropriate permissions in the first place. In order to do a chmod you will need to shell out, there is no other builtin method to change permissions of file system objects.

I would re-check your hex editor output. What happens if you output char(32)? That should show up as a space.
Perhaps you could try a very simple job, writing just that one character value to a file and make 100% sure that you are getting what you expect.

Does the following Command work?

Ok, that message means that your DSParams file is actually in the project directory. Can you explicitly set the permissions on the file to allow all access to everyone and see if your error message goes away?