>From my experience over the past few decades on the customer side there is no full proof means to inform the customer of an expiring license.
Highlighted console messages work if you have live operators who actually look at a console. They also work for the Sysprogs who look at system action messages assuming that they actually read the messages and don't assume that someone else is doing something about it. Messages in a batch job can be useful, again only if the application owner looks at the generated messages and then reports them. Messages in reports are useful as the report user may report that information - then again they may assume that someone is already working the license issue. Lastly just because the messages are there and someone has alerted the appropriate parties does not mean that the product won't expire as I have rarely found any of the places I've worked where the licenses get renewed on time - my experience is that 99% (perhaps higher) do expire and fall into either a grace period or the Sysprog scrambles to get a temporary extension from the vendor. My $0.01 on the topic Lionel B. Dyck <sdg>< Website: http://www.lbdsoftware.com "Worry more about your character than your reputation. Character is what you are, reputation merely what others think you are." - John Wooden ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
