On 27 October 2015 at 09:52, Charles Mills <[email protected]> wrote: An old one, but...
> Summarizing, there are three possible reasons: > 1. The hardware clock is set to local time and it is necessary to stop for an > hour to avoid duplicate timestamps. > 2. There are one or more applications that use civil time, are difficult to > restart without an IPL, and have a potential duplicate or incorrect time > problem. > 3. Neither of the above, but operations management is in the habit of > behaving as though one or both were true. > With regard to 1, this is less than a best practice, and should be relatively > easy to correct, as UTC is ahead of their local time and no duplicate times > eould result. > 2 is more difficult. We are all familiar with unmaintainable applications. > Further, they are a service bureau and for all I know the application belongs > to their largest customer who has said "deal with it or we will find a > service bureau that can." So your service bureau runs your work on the same z/OS image as the work of (some of?) their other customers? How 1970s... Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
