|
Barbara Morris wrote:
The problem is proportional to the size of the return value. Calling a procedure that returns 50 bytes should not be a problem unless you call it a zillion times in the same procedure.This seems like a pretty serious issue since it would most likely only occur during periods of heavy load, so I put together a little test, albeit pretty unscientific. Basically I just created an ILE RPG program that invokes a subprocedure that returns a 65K varying field (after stuffing the current time into the field). I ran it for an hour and a half, 14 million calls, and it seemed to run just fine.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.