<------ snip ------> Different local offsets in the CLOCKxx member. Or somebody does a weird T CLOCK= command. The TOD clocks must be in sync. But the local times may differ. <------ snip ------>
Well, I know that. We don't use it, but I think I have no problems understanding it. <------ snip ------> For the truly strange (like me): Imagine a sysplex where there is a different z/OS image for every possible "time zone" in which the company does business. The users in that time zone are directed to their z/OS image. This "solves" the local time issue! <------ snip ------> Shouldn't "local time" be just a representation (like in FTP or mail clients - you sent your mail at 10:59:58 -0600, it arrived at 18:00:49 +0100); now let's look at resources shared in a sysplex: - what time should be written in the operlog? - what time should be written in the sysplex coupling datasets, logger coupling datasets? - what time use HSM or equivalent product for migration/restore/backup? - what time is used in DB2 logs, CICS logs, assuming DB2 and/or CICS instances run in images in different timezones? Zaromil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
