Integrating Database Functionality with Workload Schedulers

A computer system comprising:

• a processor;
• a data bus coupled to the processor;
• a memory coupled to the data bus;
• and
• a computer-usable medium embodying computer program code, the computer program code comprising instructions executable by the processor and configured for executing a software job that comprises a first set of instructions and a second set of instructions by performing the steps of:
• creating a relational database trigger that accesses a distributed database table;
• inserting the relational database trigger into the first set of instructions, wherein the first set of instructions are designed to be executed by a local first computer;
• initiating execution of the first set of instructions in the local first computer;
• in response to the local first computer executing the relational database trigger, accessing the distributed database table, wherein the distributed database table comprises table information that comprises a trigger name for the relational database trigger, a name of a dummy file that contains no data, a name of a server to which the dummy file is to be sent, an identifier required to access a remote second computer, a password needed to access the remote second computer, and a specific file location on the remote second computer to which the dummy file will be stored by the remote second computer;
• using the table information to transmit the dummy file to the remote second computer;
• in response to the remote second computer receiving the dummy file, directing a scheduler to search the specific file location on the remote second computer for the dummy file;
• and
• in response to the scheduler detecting the dummy file at the specific file location, initiating execution of the second set of instructions on the remote second computer.

A computer storage medium encoded with a computer program that, when executed, performs the steps of:

• creating a relational database trigger that accesses a distributed database table;
• inserting the relational database trigger into the first set of instructions, wherein the first set of instructions are designed to be executed by a local first computer;
• initiating execution of the first set of instructions in the local first computer;
• in response to the local first computer executing the relational database trigger, accessing the distributed database table, wherein the distributed database table comprises table information that comprises a trigger name for the relational database trigger, a name of a dummy file that contains no data, a name of a server to which the dummy file is to be sent, an identifier required to access a remote second computer, a password needed to access the remote second computer, and a specific file location on the remote second computer to which the dummy file will be stored by the remote second computer;
• using the table information to transmit the dummy file to the remote second computer;
• in response to the remote second computer receiving the dummy file, directing a scheduler to search the specific file location on the remote second computer for the dummy file;
• and
• in response to the scheduler detecting the dummy file at the specific file location, initiating execution of the second set of instructions on the remote second computer.