[p4] P4 Verify issue consolidating servers - across time zones

[Craig A]

I am consolidating a remote server in PST time zone (SERVER_A) to an
existing Perforce server (SERVER_B) in CST time zone. I am going to bring
the server up as a second service instance on a different port. I am copying
all the depotfiles across the WAN and will be restoring the checkpoint file
to rebuild db.*

I have noticed in the past migrating and moving P4 servers around that when
I run a 'p4 verify -q //...' against a newly moved P4 server and the OS time
zones aren't the same, I get many !BAD errors showing mismatched MD5
checksums. When I diff the errored depot files I see that the only
difference is a $DateTime value that the server expands. I am guessing
Perforce is storing the time field ($DateTime) in its database as GMT and
then when it renders the file it adjusts $DateTime for the server's time
zone.

So here is my problem:
I want to avoid getting these timezone-related BAD! Errors when I run a 'p4
verify -q //...' immediately after the checkpoint restore on SERVER_B.
However I cannot adjust the time zone on SERVER_B to match SERVER_A since it
already has a running P4 instance and would cause verify errors on that
instance. So it seems I am stuck with these !BAD errors on the second server
instance when running 'p4 verify -q //..'. This prevents me from using 'p4
verify -q' to validate that all the files came across the WAN intact.

I don't want to just run 'p4 verify -v //...' (regenerate MD5 checksums)
immediately after I bring the second server instance online, since that does
not give me a good comfort level that I have migrated the server with all
depotfiles intact.

The best solution I can think of is to run a 'p4 verify -q //...' on the
existing P4 server instance at SERVER_B (the migration target). If I see no
errors then stop the P4 server, change the time zone (to match SERVER_A) and
then run 'p4 verify -v //...' on the original P4 server instance to reset
the MD5 for every file to the new time zone. 

Now when I bring up the newly migrated p4 server instance the time zones
will match. I can run 'p4 verify -q //...' on the newly migrated server
instance and I will not get the extra BAD! errors.

Is there a way to tell the Perforce server to use a time zone different from
the OS?

Thanks
Craig