Beware: Don't use such "strange" time-offsets when your VM system is part of an NJE (RSCS) network that crosses several timezones, spread over more than 1 CPU. My customer did without asking me first, and the result was a mess. One reason is that SENDFILEd files have their timestamp in GMT time. RECEIVE at the other side will use its local GMT offset to calculate the timestamp for the file. If the offsets are in whole hours (or half hours as we have to live with) you can still trust that the last digits of a file's timestamp will not change when sent from one VM to another. W ith "strange" offsets, every digit can change.
Furthermore, EXECs might exist that are interested to see a GMT time. Maybe these EXEC cannot cope with "strange" offsets. We had to fix some code when we installed a VM with 05.30.00 as offset. Kris, IBM Belgium, VM customer support VM/ESA and z/VM Discussions <[email protected]> wrote on 11/03/2005 12:05:11 AM: > Just define a new timezone with the minutes adjusted as well as the > hours offset from GMT and then the SET TIMZONE command. > > This can be done on the fly and the timezone name can be anything > (e.g. XXX).
