|
Hi Joel - >*NEW is a named activation group. The system just picks >the name for you. Well, excuse me for not using the full term "user-named activation group"! <G> >I do use it for exactly the circumstances we're talking >about because it pretty much guarantees a unique identifier. >I would use a name if I was sure that the job would never, >never, never have more than one instance at a time, The job will never have more than one instance of a user-named activation group at a time. Once the activation group is created, anything that specifies that activation group will run in that same activation group until it is destroyed. >just because I like human readable names. I'd have to be >real sure, though. <g> If you use a user-named activation group, it will not be automatically destroyed when no longer in use; a system-named activation group will be. To me that is a significant difference and automatic cleanup is much more important than having a meaningful name. (The system-named activation groups have human readable names, they just aren't particularly meaningful. <G>) Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.
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.