tags:

views:

13

answers:

0

I'm basically writing a ksh script that wraps over the dsjobs command to give my command-line-wary colleagues a simple interface from where they can view job logs, start/stop a job etc in case the clients at the Windows end crash (they often do).

I've pretty much finished the script except a snag: the stageinfo option in dsjob doesn't give detailed information; and my colleagues would love to get a list of all the input/output/reject files etc that get used in a job. I can get all the stages/links for the job with lstages/llinks, but stageinfo/linkinfo for each of them won't do it since I won't get the file names.

So, in sum: is there a way to get the filenames for PS stages, as well as more fine-grained details all over? Is there a project-level setting that I have to change (almost impossible since at our end of the chain nobody has admin privileges)?

I've been searching the net for a bit, and I found the dssh command, which apparently is a shell for datastage where you can select from tables like DS_JOBS etc. Anybody know anything about this? Some documentation would be really helpful, so that I can figure out if this will be a better solution.

I'm not a DS dev myself, so sorry if I was unclear/wrong/stupid about anything... nobody would be happier than me if a simple solution exists!