DSXchange

Yah... too bad 'View Data' works for something that won't actually run in your job. Much like if you add a semi-colon to the end of an Oracle query.

try this dsjob -logdetail ProjectName JobName 'dsjob -logsum ProjectName JobName|head -1|awk '{print $1}'` `dsjob -logsum ProjectName JobName|grep '^[0-9]'|tail -1|awk '{print $1}'` >> FileName.log You missed a back tick. Sorta. Kumar - also search for the equivalent commands in the DataStage onlin...

Don't select them in the first place?

Just mean BASIC job control code that you write. You can do that under the Job Control tab of the Job Properties in a Server job and not put any stages (other than annotations) on the actual job canvas. Or go old school and create a "Batch::" from the Director, which is kind of like the job control ...

Now, that doesn't mean a DataStage job can't run the script. A Sequence job with an Execute Command stage comes to mind. Or 'after job' in the job that creates whatever needs to be zipped using ExecSH. Or via hand-crafted job control. Or...

You can't use the Filter option to zip a file because it's all about reading 'standard out' of the filter command into the stage as a file. You can't use the FTP stage to send a zipped file because it is metadata driven. Separately. Outside. ps. 'Reply with quote' work better than hand-typing and co...

AIX?

parvathi wrote:can i use a seqentail stage to zip the file and then use ftp stage to pass it to the remote server.

Nope. Script it.

Jeez, doesn't anyone search the forum?

This is like the fourth time this question has been asked in the last two days... do an Exact search of the forums for your error phrase "Timed out while waiting for an event". Many discussions on this topic will be forthcoming.

That error is one of the ones that are a pain to diagnose. I could see none of your jobs working, but 20 out of 35 failed? And you don't see anything different about those 20 I assume. Only suggestion I'd have is to try not passing any of these parameter values in question to the child jobs - leave ...

I am pretty sure that the Oracle clients ARE backwards compatible. They are not, however, necessarily forwards compatible. Think about it - how can you write a client to access a database using features that weren't conceived at the time the client was written. I know what you are saying and agree ...

... and extremely simple to check for yourself - try to create one.

From what I observe, I think it is only the year 2000 is being read as 3000. Well... this is different than the problem as originally stated: It is reading 26-APR-02 as 0002-04-26 00:00:00 instead of reading it as 2002-04-26 00:00:00. This new set of data makes a little more sense... as Ray notes, ...

The problem persists only for certain date values, from what I recall. At this point all I can suggest is opening a case with Support and see what they have to say. You're not doing anything wrong or out of the ordinary from what I can tell. It sure as heck should work fine that way.

Google for something like 'here document ftp script' and you should find lots of examples of what is meant by that.

One such example.