about F$GETSYI("TEMPERATURE_VECTOR")

[Davor_7]

Hi lexical expert,

after i do this
$ a = f$getsyi("Temperature_Vector")
$ write sys$output a
$ FFFFFFFFFFFFFFFFFFFF18161B1D1C1E

who know's the last 12 letters(18161B1D1C1E) meaning for?
i know that '1E' means 30 degrees, and '1C' means 28 degrees,
but where does it stand for? which physical location in the rack?

thanks !

[Bojan Nemec]

Davor,

The value is hardware dependent. Each byte means the temperature in Celsius degrees (as you already know). The value FF means not present, FE unknown , 01 ok and 00 failed.

I think that you should search the hardware manuals abbout the physical location of the sensors.

Bojan

[Davor_7]

btw, how to know where the sensor may be ?
i cannot search any result in lots of OVMS manuals.
i lost my way..

[Volker Halle]

Davor,

you do not need to read any OpenVMS manual to find out about the location of the temperature sensors. This information could only be in the hardware manuals of your specific type of Alpha system, if it's publicly available at all.

Please note that this GETSYI item code is undocumented.

Volker.

[Ian Miller. · Accepted solution]

See this
http://h71000.www7.hp.com/wizard/swdev/thermal.html

[Martin Vorlaender]

Please find attached a small DCL program (renamed to .TXT for Internet Exploder) which - besides decoding the vector - also has strings on the location of the respective sensors.

I think Paul Jacobi posted this to comp.os.vms (or was that the C program?).

HTH,
Martin

[Larry De Clay]

Davor,
It depends of the hardware.
In some models reports temperature of diferents places in the box also the CPU temperature.
Could you tell us in what model of Alpha are you running the command ?

Thanks,
Mauricio

[Davor_7]

Thanks all, i have got a method to make the conclusion.

very appreciate
============================================

Hi all, i reopen this thread for that
who knows the error log number about the temperature problem or fan problem?
i wanna search it in the errlog.sys, but there are lots of records there, do you know the keywords to search?
thanks!

[Volker Halle]

Davor,

as you didn't provide the type of system nor the OpenVMS version, it's kind of hard to suggest an errlog analysis command.

ANAL/ERR does not work anymore since V7.1-2 on OpenVMS Alpha and has finally been replaced by ANAL/ERR/ELV as of V7.3-2. An alternative may be DIAGNOSE (DECevent), but this needs to be installed separately.

You would want to start with the equivalent of:

$ ANAL/ERR /SUMM/NOFULL

to find the different classes of errlog entries in your ERRLOG.SYS. Then you could use /INCL=... to include a specific class most likely to show the fan and/or power events. I would guess it's ENVIRONMENTAL_ENTRIES

Volker.

[Davor_7]

thanks Halle,
do you mean $analyze /err /elv translate /summ errlog.sys ?
this is the output and i cannot see ENVIRONMENT_ENTRIES at the list, does it mean that no error about environment ?

Output for ERRLOG.SYS;1

ERROR_LOG_SUMMARY______________________________________________________

Total number of events: 408
Number of the first event: 1
Number of the last event: 408
Earliest event occurred: 22-AUG-2005 09:04:14.86
Latest event occurred: 28-NOV-2005 15:06:35.24
Number of events by event class:
ATTENTIONS 6
BUGCHECKS 1
CONFIGURATION 2
CONTROL_ENTRIES 24
DEVICE_ERRORS 146
MACHINE_CHECKS 7
TIMEOUTS 3
VOLUME_CHANGES 219

[Volker Halle]

Davor,

that was the right command to use for ELV.

I would stop guessing here and use ANAL/ERR/ELV TRA/out=x.x and then search the output file for 'FAN' or 'TEMP'

Volker.

[Volker Halle]

Davor,

ELV may not be able to fully translate all those different errlog entries. Again - depening on the type of system - you would need DECevent for the older Alpha systems or WEBES (SEA = System Event Analyzer) for DS10, GS80 or higher to translate errlog entries for OpenVMS systems.

Both tools are downloadable from the hp OpenVMS Analysis Service Tools page:

http://h18023.www1.hp.com/support/svctools/

Volker.

[Davor_7]

here is ES40, so i think WEBES is a better tool to analyze the errlog.

hi Halle, is it easy to use? can i use a simple command like $analyze/err/elv... to extract error log via WEBES? (i heard that this is a web-based tool, how to use it?)
thanks....

[Volker Halle]

Davor,

using SEA (=System Event Analyzer, a component of WEBES) to translate or analyze an OpenVMS error log file, is not as 'easy' as ANAL/ERR/ELV, but you'll get used to it.

I could point you to my DECUS presentation on OpenVMS Errlog Analysis, but it's in german...

http://www.decus.de/slides/sy2004/20_04/1l04.pdf

There is documentation available on the analysis tool website, but it's a lot of reading. You can also invoke WEBES on your ES40 (after you've installed and started it) via the WEB as http://hostname:7902 and use the WEB interface to decode and analyze error logs.

The SEA (WSEA) DCL interface is used like this:

$ wsea v /tra/sin="31-Jan-2005â /out=x.x

will translate SYS$ERRORLOG:ERRLOG.SYS entries created since 31-JAN-2005 and put the results in file x.x

Volker.