Executing a Job on a Client Computer

Previous Next

To execute a job on a client computer, outside USoft Binder, use this command line:

runbatch.exe -<database_type> -database <database_name> [-ddfile]

-app <application_name> -u <user_name> -pw <password> -exe "job(<job_name>[,<parameter>=<value>,..])"

For a complete list of all command line options and their meaning, refer to "Batch Runner Command Line Options".


Here is a typical example of a Batch Runner command line within a production environment:

runbatch.exe –oracle –database PROD –ddfile –app MYAPP –u JOHN

–pw secrid –exe "job(EXP_PERSON,INS_AFTER=01-APR-2001)"

In this example:

· The application tables are stored in an Oracle database with name PROD.


· The code in the command line that reads:

-ddfile –app MYAPP

specifies that the application definitions for the MYAPP application are read from the MYAPP.con and MYAPP.ext flat files, instead of from repository.

This is because in a production environment, no repository is available.

· The EXP_PERSON job is executed, with the job input parameter with name INS_AFTER set to 01-APR-2001.

Once you have distributed the job definition file for the application, you must provide a mechanism for your end users to be able to run a given job, or tell them how to set up such a mechanism.

If the job is to run on the client, then the simplest way is to place the above code into an MS-DOS batch (.BAT) file, supply it to your end users, and tell them to make a shortcut to it on the Windows desktop. After this, they can just double-click the shortcut to run the job.

If the job is to run on the server, the best thing to do is to create a batch file in the same way, such that it starts the appropriate remote connection, and then runs the job. How you do this depends on your remote server, and the login you use.

In order to run a job at a given time, you need to use an operating system command, or third-party tool that is designed to use the system clock for scheduling purposes.