DSXchange

vijayindukuri wrote:After renaming the file i tried to view the file by double cliking that,I was able to see that data in csv format.

Just for one last note - no, you didn't. Double-clicking on the renamed csv file simply launched Excel and you were looking at the spreadsheet. Again.

I for one feel that would be a Very Bad Idea and should not be the kind of advice we hand out here willy-nilly. More than likely, all that will result of it would be a corrupted repository.

say UPDATE EMPLOYEE SET DEPT=30 WHERE ENAME LIKE 'Diana' AND DEPT = 10 A 'like' with no wildcards is the same as saying 'equals', which turns this into a plain old ordinary update statement. If you really mean to use the 'like' you'll need custom sql and to wrap your field value in the appropriate ...

Instead of using routine activity use uservariable activity and call your routine there.It works fine. Maybe so, but it also 'works fine' calling the routine using a... wait for it... Routine Activity stage! It someone is going to be building anything other than basic level Sequence jobs, it is cri...

sb_akarmarkar wrote:Routine_Activity.$Jobstatus and Routine_Activity.$Returnvalue both are different

Yes, of course... but Routines do not have a $JobStatus - jobs do.

'Executed Ok' means 'returned a zero'. For jobs it is returned as their status, for routines as their answer.

Perhaps it depends on what the 'among other things' things are?

For anyone wanting to help: To put this into perspective, please go through this exchange so you understand how the XML is being generated. I really don't think this is a bug but more likely a problem in the job design, specific to the need to use a Sequential File stage as your final output. But t...

There is no command line mechanism to delete jobs. Curiousity forces me to ask - why do you think you need to do something like this?

A job the Sequence runs aborted, had a fatal error - simple as that. You need to back to the other job's log to find out why: the multi-instance job FTP7InsightCSVFile.FTPFIN specifically.

Routine Activity fails unless untill the Ans = 0. When ever we use routine activity in Sequence jobs we use 'Unconditional' trigger. As Kris noted, you need to understand the behaviour of routines, how triggers decide if they 'failed' or not and use them accordingly based on each case. If you enabl...

Search the forums for 'DSX Cutter', it is freely available and does exactly what you want.

Or just stick with an 'Unconditional' trigger.

Have you thought about putting them in a Hashed file?

For what it's worth, Dancing with Support right now. I'm told that the thick drivers should have worked and respected the override of the environment variables, however they did not. Or perhaps something else is going on.

Hasn't anyone else had to worry about something like this before?

Any luck getting a newer Client installed?