Programmers?
Thread Starter
I Love To Post!
Joined: Jan 2003
Posts: 6,753
From: Miami, FL
Programmers?
We have some scheduled processes in my job that were written in VB6.
We use MS SQL and built DTS processes to handl ethese executables.
We use the SQL Scheduler to kick these off...
A few weeks ago we installed SP1 for Windows Server 2003.
Ever since then, most of our FTP Batch jobs wont run. No errors at all, they just wont execute.
For example:
Process A has 5 steps:
Step 1 - Create FTP BATCH file and FTP TXT (instruction)FILE in xx directory. Overwrite files if they exist.
Step 2 - Execute FTP BATCH to copy file from mainframe system and place in xx directory.
Step 3 - Populate xx table with data in file.
Step 4 - Compare new data in table with old data in yesterdays table.
Step 5 - Make changes to files that are different in step 4 and send email to xyz user with changes.
The problem is that the executable will complete with no errors, but since the FTP Batch file never executes, Step 3 just assumes there were no changes for that day and there for make Step 4 and 5 null. So it completed successfully but in reality it did not.
Has anyone got an idea why the FTP BATCH file is not executing? Does it have to do with SP1?
Removing SP1 is not an option at this point.
We use MS SQL and built DTS processes to handl ethese executables.
We use the SQL Scheduler to kick these off...
A few weeks ago we installed SP1 for Windows Server 2003.
Ever since then, most of our FTP Batch jobs wont run. No errors at all, they just wont execute.
For example:
Process A has 5 steps:
Step 1 - Create FTP BATCH file and FTP TXT (instruction)FILE in xx directory. Overwrite files if they exist.
Step 2 - Execute FTP BATCH to copy file from mainframe system and place in xx directory.
Step 3 - Populate xx table with data in file.
Step 4 - Compare new data in table with old data in yesterdays table.
Step 5 - Make changes to files that are different in step 4 and send email to xyz user with changes.
The problem is that the executable will complete with no errors, but since the FTP Batch file never executes, Step 3 just assumes there were no changes for that day and there for make Step 4 and 5 null. So it completed successfully but in reality it did not.
Has anyone got an idea why the FTP BATCH file is not executing? Does it have to do with SP1?
Removing SP1 is not an option at this point.
Registered User
Joined: Aug 2006
Posts: 154
From: Stone throw from Canada, next Miami!!!!
Re: Programmers?
Is that it? That's an easy fix. Here it is
The FTP batch file is not executing because when you populated xx table with data in step 3 you did not make changes to file 34 before setting the batch to self destruct as mentioned in step 8. Take step 4, switch it with step 3 than put step 5 before it. Move step 6 between 4 and 3, populate the batch xx with three buffers of SP1 than delete said executables and list yesterdays data as todays but still list it as new but old while still being yesterdays. Make sense. No thanks needed
The FTP batch file is not executing because when you populated xx table with data in step 3 you did not make changes to file 34 before setting the batch to self destruct as mentioned in step 8. Take step 4, switch it with step 3 than put step 5 before it. Move step 6 between 4 and 3, populate the batch xx with three buffers of SP1 than delete said executables and list yesterdays data as todays but still list it as new but old while still being yesterdays. Make sense. No thanks needed
Scrapes Elbow
Joined: May 2004
Posts: 8,833
From: Phoenix, AZ.
Re: Programmers?
that was good. haha..
ima a macintosh person n only front end programming. VB & SQL is to deep but my g/f's dad is a honeywell engineer/programmer and hes allways writing software (back end applications).. i'll run this by him an see what he says
ima a macintosh person n only front end programming. VB & SQL is to deep but my g/f's dad is a honeywell engineer/programmer and hes allways writing software (back end applications).. i'll run this by him an see what he says
Thread Starter
I Love To Post!
Joined: Jan 2003
Posts: 6,753
From: Miami, FL
Re: Programmers?
Is that it? That's an easy fix. Here it is
The FTP batch file is not executing because when you populated xx table with data in step 3 you did not make changes to file 34 before setting the batch to self destruct as mentioned in step 8. Take step 4, switch it with step 3 than put step 5 before it. Move step 6 between 4 and 3, populate the batch xx with three buffers of SP1 than delete said executables and list yesterdays data as todays but still list it as new but old while still being yesterdays. Make sense. No thanks needed
The FTP batch file is not executing because when you populated xx table with data in step 3 you did not make changes to file 34 before setting the batch to self destruct as mentioned in step 8. Take step 4, switch it with step 3 than put step 5 before it. Move step 6 between 4 and 3, populate the batch xx with three buffers of SP1 than delete said executables and list yesterdays data as todays but still list it as new but old while still being yesterdays. Make sense. No thanks needed
Registered User
Joined: Apr 2003
Posts: 5,046
From: stuntbums hq
Re: Programmers?
We have some scheduled processes in my job that were written in VB6.
We use MS SQL and built DTS processes to handl ethese executables.
We use the SQL Scheduler to kick these off...
A few weeks ago we installed SP1 for Windows Server 2003.
Ever since then, most of our FTP Batch jobs wont run. No errors at all, they just wont execute.
For example:
Process A has 5 steps:
Step 1 - Create FTP BATCH file and FTP TXT (instruction)FILE in xx directory. Overwrite files if they exist.
Step 2 - Execute FTP BATCH to copy file from mainframe system and place in xx directory.
Step 3 - Populate xx table with data in file.
Step 4 - Compare new data in table with old data in yesterdays table.
Step 5 - Make changes to files that are different in step 4 and send email to xyz user with changes.
The problem is that the executable will complete with no errors, but since the FTP Batch file never executes, Step 3 just assumes there were no changes for that day and there for make Step 4 and 5 null. So it completed successfully but in reality it did not.
Has anyone got an idea why the FTP BATCH file is not executing? Does it have to do with SP1?
Removing SP1 is not an option at this point.
We use MS SQL and built DTS processes to handl ethese executables.
We use the SQL Scheduler to kick these off...
A few weeks ago we installed SP1 for Windows Server 2003.
Ever since then, most of our FTP Batch jobs wont run. No errors at all, they just wont execute.
For example:
Process A has 5 steps:
Step 1 - Create FTP BATCH file and FTP TXT (instruction)FILE in xx directory. Overwrite files if they exist.
Step 2 - Execute FTP BATCH to copy file from mainframe system and place in xx directory.
Step 3 - Populate xx table with data in file.
Step 4 - Compare new data in table with old data in yesterdays table.
Step 5 - Make changes to files that are different in step 4 and send email to xyz user with changes.
The problem is that the executable will complete with no errors, but since the FTP Batch file never executes, Step 3 just assumes there were no changes for that day and there for make Step 4 and 5 null. So it completed successfully but in reality it did not.
Has anyone got an idea why the FTP BATCH file is not executing? Does it have to do with SP1?
Removing SP1 is not an option at this point.
Thread
Thread Starter
Forum
Replies
Last Post
