What I want is to be able to call the export utility from within a stored procedure. As a last resort, I could define a program with dbms_scheduler, then a job that executes that program just once and call that job that actually execute the export from the procedure. But I was hoping to avoid it by calling the export directly in the procedure, eventually within a wrapper(like shell function in VB)
There is a tool called winbatch. Use it to write a program that looks for batch files in a particular directory. When it finds a bat file it should run the file, delete it and then go to sleep for a period of time.
Then write your procedure to create a file ending in bat with all of the commands that you want run. You can also dynamically create the parameter file.