DSXchange

Hmmm. I didn't see the problem in 7.5 when we tested it. We did have other problems with 7.5 and didn't move to it. I am testing 7.5.1A now, in my spare time. We'll see...

Tony

I finally found that the problem was caused by using inter-process row buffering on the job. If you disable row buffering it will fix it (Ascential says v7.5 is fixed, but I haven't tested it). Oddly enough there's another bug in disabling row buffering, so it doesn't actually disable it. What I've ...

Hmmm. Perhaps I was thrown by the Active Stage Finishing message . Sorry if I misled you.

Tony

You might want to check the &PH& directory in your project directory. When there are a lot of files in this directory it can take a job a loooonnnng time to finish. If no DataStage jobs are running (ps -ef |grep -i dsd) you can delete all the files in this directory. Also, you may have an af...

I believe with the newer versions of DataStage that you can use a RowSplitter stage to take the single column in and split it out into individual columns.

It is supposed to support parameters on 7.5, but I haven't been able to test it yet.

tony

Thanks, Kim. I thought I was on the right track, but I was in a hurry when I wrote it and didn't have time to do it on the computer. Thanks for looking this over.

Tony

pongal If you filled out the information correctly in your first message, I think you have a problem. It says that you're running DataStage on Windows. If that's the case, you can't run a UNIX shell script in Windows unless you load some kind of other layer like SIGWIN or something similar. Other th...

1) Pass the Job Parameter in an argument to the routine. In the routine build the command in a variable something like: Cmd = "ExecFTP.sh" : ipadress : "," : username : "," : pwd : "," : remotedir : "," : JobParameterArg : "," : Arg6 where ...

You may need to add an index on the column(s) in the universe table/hash file on which you're doing the range lookup.

Try something like

dscmdexport .... < !EOF
Y
!EOF

This will simulate a 'Y' entry as an user-response and move beyond the prompt.

Will that work on Windows?

Tony

No, not if it's like what I was seeing. Previous runs would be complete and error free and then suddenly... nothing. The next day it would run fine.

Yes, Craig. This is exactly what I'm seeing.

Tony

I've noticed (7.1 on AIX) that the job entries are to be found in atjobs rather than in cronjobs. But this really addresses the "can't schedule" problem rather than the "won't start" problem. Ray, the only time I've dealt with 'at' was when I scheduled a non-recurring job. The s...

No. This is a job sequencer job that is scheduled to start at 5:00am. At 7:30am someone called to my attention that they hadn't receive an email report from this job as they usually did. I checked and what I saw in the Job Log for this Job Sequencer job was the DS.SCHED entry at 5:00am. There was li...

Craig, Yes, this is exactly what I'm seeing. Thanks, Ketfos, if it comes to that we will do that, but I would hate to have to go that route. Sainath, Yes, this is a multi-processor system. An HP UNIX system with 8 processors. My problem, right now, is that I don't know what to look for to troublesho...