[Info-vax] OpenVMS IA64 V8.2 - Failing to reboot automatically

[Jim Mehlhop]

Jim Mehlhop wrote:
> jim wrote:
>> On Jan 21, 1:56 pm, koeh... at spock.koehler.athome.net wrote:
>>> In article 
>>> <2534768e-55eb-4531-9ca7-08ef9b394... at v18g2000pro.googlegroups.com>, 
>>> Ivan Lowe <ivanlow... at googlemail.com> writes:
>>>
>>>> We have a number of Itaniums running ovms 8.2.  A new "bug" seems to
>>>> have materialised since the start of this year whereby these systems
>>>> won't reboot automatically.  The system starts booting up VMS but then
>>>> requires the date to be re-entered.
>>>> At first I thought this was an issue with the battery on the
>>>> motherboard but have found that if the date is say 1-JAN-2004 the
>>>> system will reboot fine - but when put back to 2009 the problem
>>>> reoccurs.
>>>> Is this a hardware or software issue - anyone?  If a software issue -
>>>> is there an easily administered s/w patch for it.
>>>    Are you running sys$system:shutdown.com?  If not, then the commands
>>>    to update the hardware clock may not be happening.
>>
>> I have another site with EXACTLY the same problem.  It is an rx1600
>> the  CM> date command shows the correct time. to be safe I had them go
>> into the system configuration menu and do the set time and set date.
>> then go back to MC> and  RS.  Then check the data again.  Looks good.
>> If he sets settime=0 (which is was) and TIMEPROMPTWAIT = 0 it will
>> boot and set the time to-------  Are you ready for this     1-jan-2004
>> at midnight!!
>> I had him do
>> $ set time <cr> also so that has been covered.  Will check his
>> patches.
>>
> 
> It appears to be a system patch.  The following patches were installed 
> on a system that DID work!
> 
> 
> 
> BFIELD::SYSTEM$ prod sho hist
> 
> ----------------------------------- ----------- ----------- 
> --------------------
> 
> PRODUCT                             KIT TYPE    OPERATION   DATE AND TIME
> 
> ----------------------------------- ----------- ----------- 
> --------------------
> 
> 
> HP I64VMS VMS82I_TZ V2.0            Patch       Install     31-OCT-2007 
> 01:18:40
> 
> HP I64VMS VMS82I_TDF V3.0           Patch       Install     31-OCT-2007 
> 01:17:12
> 
> HP I64VMS VMS82I_UPDATE V6.0        Patch       Install     31-OCT-2007 
> 01:11:13
> 
> HP I64VMS VMS82I_PCSI V1.0          Patch       Install     31-OCT-2007 
> 01:07:45

To verify  Installing the latest set of 8.2I patches DID indeed fix the 
problem