External Stored Proc Limitations?
in [Cobol]
|
From: Pete Dashwood on 10 Jan 2008 06:10 "pompeyoc" <pompeyocatindig(a)gmail.com> wrote in message news:460ccd8d-7078-4b2a-82aa-5a3eab0dc423(a)s12g2000prg.googlegroups.com... > On Jan 8, 2:22 pm, Robert <n...(a)e.mail> wrote: >> On Mon, 7 Jan 2008 18:58:05 -0800 (PST), pompeyocatin...(a)gmail.com wrote: >> >Hi. I was wondering if anyone out here knows if there is a limit to >> >the size of an external stored procedure? I am currently using VB >> >programs in Windows to call small COBOL stored procs residing in AIX >> >without any problems. This time, however, I am planning to have >> >another VB program call a COBOL stored proc that, in turn, calls other >> >COBOL programs via ordinary COBOL CALLs. >> >> >Any ideas? >> >> If you're tallking about Oracle, the external procedure runs as a child >> of the listener. >> Unless a system administrator put limits on that user, which is unlikely, >> you should be >> good. >> >> If you want to find out for sure, write a quickie external procedure that >> does a malloc >> for, say, 100 meg. Or run svmon -P (listener pid) Or, if you can get to >> it, look at the >> /etc/security/limits file. > > Thanks for answering so quickly, guys. Our connection at the office > has been down for the last couple of days so I'm actually doing this > from my home. > > Pete, I guess my next question is, resources from which server? Since > the database resides in the AIX server, does this mean the stored > procedure will be using its resources? Absolutely... unless the procedure contains RPC (Remote Procedure Calls) to components and applications distributed around the Network, in which case the resources of the server(s) where each component resides will be used. Pete. -- "I used to write COBOL...now I can do anything."
From: Simon Tobias on 11 Jan 2008 06:02
> Hi. I was wondering if anyone out here knows if there is a limit to > the size of an external stored procedure? I am currently using VB > programs in Windows to call small COBOL stored procs residing in AIX > without any problems. This time, however, I am planning to have > another VB program call a COBOL stored proc that, in turn, calls other > COBOL programs via ordinary COBOL CALLs. > > Any ideas? > > Simon? I'm hoping you're still around to help since you were the one > who managed to solved my first problem. > > Thanks in advance. > DB2 stored procedures run under the auspices of the server, rather than client-side. By default, they're executed as setuid apps under the 'fenced' ID specified at instance creation time. IBM DB2 doc covers limits on the number of parameters you can use, stored procedure name, number of nested levels. Search for "SQL Limits" within the Information Center for DB2. As for the maximum application size permissible, I guess that this *may* be limited by the ulimit settings on the machine, memory available. This isn't an area of DB2 which I'm totally familiar with, however, so you may be best of talking to IBM. I see that you also posted on comp.databases.ibm-db2 , and that Serge has responded (he really knows his stuff from what I've seen from his posts!), so you may now need to check the AIX configuration (ulimit etc.). SimonT. |