| Re: .0
Robin, has your Customer heard the phrase "Doctor, it hurts when I do
this ..." ? What excuse does your Customer have for trying to start
LAT that little bit sooner than normal during StartUp ? ( is it just
for a "MIN" startup, perhaps? ) Also, from which file is LAT$STARTUP
called when this happens ?
Anyhow, to address your questions..
| Has anyone seen error message "LAT rating image has not been initialized".
| before? If so, do you know where this is coming from? What is the
| fix for it?
The message comes from the LATACP process when it discovers that the
loadable image which (in partnership with LTDRIVER) produces the node's
Load Rating has not yet been initialized by LTDRIVER's controller init.
routine.. as to why this happens, I don't know for sure, but I'd have to
ask whether this node is a Multiprocessor (SMP) with 2 or more CPUs
active (?) The 'fix' is probably to return to a tested (supported)
configuration and start LAT at the same point that everyone else
does.. :) ..otherwise, I suppose you could try a $WAIT 0:0:5 just
prior to @SYS$STARTUP:LAT$STARTUP..
Hope this is of some help..
John.
|
| Re: .1
Robin, I'm very sorry.. I misinterpreted .0 as implying that
LAT$STARTUP.COM was called earlier and from a place other than
SYSTARTUP_VMS.COM.. so ignore the first paragraph of .1 please..
The SMP question remains, though.
Btw, another person has just asked the same question over in Noted::LAT
topic 4957.0
Thanks,
John.
|