The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Scribe Error
Posted: 15 May 08 3:16 PM
|
I'm using the Scribe Console to schedule an import. Basically every morning I want to set off an FTP script to download a file and then run an import using Scribe after the file appears. The problem is that sometimes the file will take a few seconds to download the file and when that happens the job fails because it doesn't see the file. Right now I have a dummy job running first on a schedule that runs the Pre-job command to download the file (and then ends with WScript.Quit 901, so the dts doesn't run) and then another job running based on a file appearing in the folder to run the scribe job.
This doesn't feel like the best way to do this, does anyone else have any insight?
Thank you! |
|
|
|
Re: Scribe Error
Posted: 16 May 08 6:19 PM
|
G'day Ian,
I do a lot of VB6 development.
In my apps, I set a shared memory variable (clsMemoryMap) and the calling app waits for the FTP app to say "Downloads/Uploads Completed!" - (Well it sets a value anyway  )
Because I have not done any SLX scripting for 7 years or so (apart from ASP) I don't know if this might help you at all, but I hope it does.
Cheers,
Kevin
|
|
|
|
Re: Scribe Error
Posted: 28 Jul 08 10:10 AM
|
In the past we processed lots of files from FTP using scribe. We no longer have any in place. Below is how we managed it for a long time and it work very well.
Write a vb script and schedule it using the windows scheduler to check the FTP server several times a day for the file we needed.
Once the file was detected, the script would transfer it to our scribe server. After the file transfer was complete, the script would create a blank txt file (something like trigger_for_account_load.txt) that a scribe integration process (Event type File Runs a DTS when a file in a folder is detected) would monitor for.
The scribe event would detect the trigger file and run the event to process the FTP transferred file. We used a post process vbs script to clean up the processed file and trigger file. Also created a copy of the processed file in an “archive” directory named with the current date and time. We would keep 15 days worth incase we needed to go back and trouble shoot the source file.
|
|
|
| |
|