DSXchange

All,

I have create a job which will extract the data from a table and store it in a text file.

say for example,

Table Name: Emp

I want to add current date at the end of file. i.e if i run the job now, the file should be created as e_details20090701.txt

suppose if i run the job tomorrow,then the file name should be
e_details20090702.txt.

How to add the current date at the end of file ?

The date portion of the filename should be passed into the job as a job parameter. It is not quite clear to me whether this date is part of the data or computed elsewhere, though.

This has been asked and answered a jillion times here. Another way - create it with a fixed name and then rename it to include the date 'after job' using your O/S.

Jillion+1. That method too complicated and too Old School. Get Hip Daddy-O. Use a DSMacro as part of the filename in the sequential stage. <filename>#DSJobStartDate#. Use DSJobStartTimestamp if running more then once in a day. Nah, never happen.

That's cool, Daddy-o as long as you don't mind the delimiters the macros use.

Maynard G Krebs lives!

Wasn't that Gilligan before he was Gilligan... <google,google>... why yes, yes it was.

throbinson wrote:Jillion+1. That method too complicated and too Old School. Get Hip Daddy-O. Use a DSMacro as part of the filename in the sequential stage. <filename>#DSJobStartDate#. Use DSJobStartTimestamp if running more then once in a day. Nah, never happen.

I gave like

#FileName##DSJobStartDate# but the date didn't added with the file name.

I declared one variable in the parameter

ProcessDate

with default value

1000-01-01


In the JobControl section,

I wrote one subroutine

If ProcessDate = "1000-01-01" Then ProcessDate = Oconv(Date(),"D-YMD[4,2,2]")

then i used this variable like

#FileName##ProcessDate#

But no use.

Timestamps has colon (:) symbol which is generally interpretted for remote hostname or ip address.

Parameter must not be computed within the job.

Use an afterjob rountine for now.

Sainath.Srinivasan wrote:Timestamps has colon (:) symbol which is generally interpretted for remote hostname or ip address.

Parameter must not be computed within the job.

Use an afterjob rountine for now. ...

What i have to choose from the afterjob routine combo box ?

execSH

From a Windows server it would be ExecDOS. And code in 'Job Control' is not visible to anything inside your job proper.

chulett wrote:From a Windows server it would be ExecDOS. And code in 'Job Control' is not visible to anything inside your job proper. ...

It is throwing 'No command to execute' error message.

After selecting ExecDOS you need to pass the command to execute in the text box in-front of it. so that the routine ExecDOS can execute it.

Try something like
where pCurrentDate is the date parameter formatted in required manner.