|
> From: Joel Cochran > > Service programs, by contrast are always created with > *CALLER unless there is a specific feature or performance need to use a > 'named' activation group. This brings up an interesting issue. Service programs, reinitialization and the joys thereof. For my tools, I LOVE to have ACTGRP(*NEW) on the command processing program, and *CALLER On everything else. This allows me to use *INZSR to do initialization even in called programs, and basically not set on *INLR anywhere. I leave files open, expect variables to retain state between program calls, and all kinds of goodies. So, do I have problems when I do that with a service program? When two jobs call the same service program, I assume they have their own storage for variables, right? If I declare a bunch of variables in the global section of a procedure, they're not shared between jobs, are they? I'm just asking - haven't gotten around to doing a lot with them yet. Joe
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.