Regarding frequent updates:

I suppose I was wondering why you would be changing code in a production 
library even as frequently as several times a day. I would have guessed 
that your application would reach stability and not require updates aside 
from functional enhancements (which most would not roll out several times 
a day, I think) and bug fixes.

And wouldn't most try out their code in a test environment and not choose 
to inject potential instability several times a day, thus grouping their 
updates to production?

So I'm curious....

Updating data upon which the code operates is a different matter, but 
that's perhaps not frequently within production code libraries.

Peter Relson
z/OS Core Technology Design

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to