Well we have a table that is read by a Pro C job and it looks at certain columns (i.e. file name, file type, parameters, priority). The filename would be my SQL script, file type is PL/SQL, parameters would be the actual parameters I pass in, and the priority in the job queue. This Pro C* job then knows to call SQL+ and execute said script with parameters if any. At that point that's where it chokes.

But I have come up with a work-around since there really is no solution. Instead of trying to pass the parameter from inside the oracle environment of forms out to unix than back into the server-side of oracle, I just call the procedure directly from within a forms-trigger within the FORM. The only downside is, is that the user's form screen is temporarily locked while this procedure is executed whereas if I could submit it as a separate job, then another SQL+ session would be opened while the user can still work. But this solution is the one that works perfectly without any limitations from a calling the procedure aspect.

Configuring and using Oracle Database Gateway for ODBC
Introduction
First, a brief summary of what a Database Gateway is. A Gateway is a set of driver agents and configurations that allow an Oracle database to communicate with other platforms…