|
View previous topic :: View next topic
|
| Author |
Message |
Amit Banerjee
New User
Joined: 12 Jan 2008
Posts: 14
Location: india
|
|
|
|
Hi all,
I've a job where there are 2 consecutive steps FTPing data to 2 different servers.Now recently the second server goes down for maintainance during this FTP time itself.Considering that this jobflow has been running for a long time and there are many complicacies in breaking down the job.
Is there a way that after the first FTP we can wait and check the connection and only when the 2nd server is up do we send the data? |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Not really. This has come up before and as i recall, none of the alternatives were attractive - they lead to other problems.
Is there some reason the "second server" has to come down at this new time?
Might the sequence of the ftp steps be reversed and get the transmission done before the second server drops?
Might the second server "pull" the data after it is re-cycled (rather than the mainframe "pushing" the data? |
|
| Back to top |
|
|
Amit Banerjee
New User
Joined: 12 Jan 2008
Posts: 14
Location: india
|
|
|
|
| Actually this second server goes through some maintenance for a few hours during that time.What we're currently doing is let the job fail at the second step once.Then again when the second server is up we restart from that step but this is not a healthy way.Thanks for your advise,maybe we'll have to think of some other way.. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
|
|
| Forget about FTP and use Connect:Direct. It automatically handles restarts when a link is down or unavailable. |
|
| Back to top |
|
|
|
|
