|
Joel Cochran wrote: > ... > But what does that static storage entail? I would think that other than > global variables and procedure pointers it should be precious little. > That being said I am hardly a compiler/operating system level guy, so > maybe my understanding is faulty. In either case it seems that Joep is > more correct than I am. > The static storage is the global variables declared in the module plus any compiler-internal storage like file-information-blocks and other control structures. Initializing it takes time; the amount of time depends on the amount and nature of the static storage. It should be pretty easy to see if the extra time for unused srvpgms is worth worrying about. - Create two modules, MOD1 and MOD2 where MOD1 just has a RETURN, and NOMAIN-MOD2 has bound calls or %PADDRs that would cause several service programs to be bound in. - Create two *NEW programs: PGM1 with MOD1 and PGM2 with MOD1 and MOD2. - Call PGM1 and PGM2 in a couple of timed loops. I think any extra time for the PGM2 loop can be chalked up to srvpgm-activation time.
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.