DSXchange

Sainath.Srinivasan wrote:If you want to retain the zeros in Excel, prefix each with a single quote mark.

That's a manual solution that doesn't work in a csv file.

If your whole question is you are trying to create something to be opened in Excel that contains a numeric field with leading zeroes and you want to retain the leading zeroes - you can't. At least not easily and not without macros and the manual cooperation of your Excel users. This doesn't have any...

the .csv extension is already associated with Excel, so it will already open it. And no, you can't simply rename a csv to an xls.

Time to mark this as Resolved then? If so, there's a button for that at the top of the page.

It *has* converted it to a number, use something else to view your file - NotePad, for instance, something that won't change the values.

So... is this a problem for everyone or just you?

Again - check the log for your Sequence job, is it being reset by your job control before it restarts it? If you are unsure, post your job control code.

Suggest you provide more information. We have no idea what database you are using or what action there is causing this. Details, man, details!

If you want to keep the (non-significant) leading zeroes for some reason, you need to make the output field a varchar.

No, it means after the job aborts you press the 'Reset' button in the Director. Looks like a 'rewind' icon, two arrow-heads pointing left.

From where you run the Sequence shouldn't make any difference. However... "The Problem i am facing is when i run the Job sequence from job control, the checkpoint does not work." I have no idea what this means. What exactly does "does not work" mean here? I'm specifically wonderi...

OE: Truncate is truncate. The word 'clear' is used for the transactional 'delete from table' operation.

DB2: no clue.

Those options are part of the job Properties page, you'll see an entry for both 'before' and 'after' job actions there. Change the after property to ExecSH and then put the full path to the script in the box next to it.

If you're trying to set enviroment variables, that needs to happen before you start the job. 'Before SQL' needs to be valid sql / session statements... are these?

Trim off the last comma, that should be the simplest fix.