Antony,

there does not appear to exist any patch for MONITOR (i.e.
MONITOR.EXE, MONTORSHR.EXE or SPISHR.EXE) for OpenVMS Alpha V7.3-2.

As OpenVMS Alpha V7.3-2 is out of support, no fixes can be expected.

You could try a SET PROC/DUMP and have a look at the process dump to
find out, which instruction causes this floating point divide error.

Are those 2 nodes, you're trying to monitor, Alpha or VAX nodes ?

Volker.

Antony,

MONITOR on V7.3-2 is still a VAX translated image (MONITOR_TV.EXE).

This seems to be the instruction stream taking the FLTDIV_F fault:

MONITOR_TV+5BBC4: LDT F5,#X0018(FP) < load F5
MONITOR_TV+5BBC8: CVTQF F5,F5 < convert F5
MONITOR_TV+5BBCC: LDAH R17,#X000B(R15)
MONITOR_TV+5BBD0: LDF F17,#XA5F4(R17)
MONITOR_TV+5BBD4: DIVF/U F5,F17,F18
MONITOR_TV+5BBD8: TRAPB
MONITOR_TV+5BBDC: CPYS F18,F18,F5 < copy F18
into F5
MONITOR_TV+5BBE0: S4ADDL R1,R2,R18
MONITOR_TV+5BBE4: DIVF/U F4,F5,F19 < divide by
R5 (r5=0)
MONITOR_TV+5BBE8: TRAPB < report
fault here

Don't expect anyone willing to dig into that translated image.

You've found a workaround. Use it...

Volker.

Volker Halle wrote:

> there does not appear to exist any patch for MONITOR (i.e.
> MONITOR.EXE, MONTORSHR.EXE or SPISHR.EXE) for OpenVMS Alpha V7.3-2.
>
> As OpenVMS Alpha V7.3-2 is out of support, no fixes can be expected.

Current Version Support did end earlier this year.

V7.3-2 Prior Version Support is expected through through 2011, and
thereafter only with advanced notice of 24 months. This on both of the
posted PVS policies; in both the European Geography and the US & AP
Geography policies.

Which means that there can still be fixes seen for OpenVMS Alpha V7.3-2,
for customer folks with PVS contracts.

kiwi-red: If you have a prior version support (PVS) contract, call up HP
and report the bug. And Volker is correct; I'd certainly also expect to
use the workaround for a while.

I'd also look at loading mandatory ECOs for the core OpenVMS Alpha
V7.3-2 components, on the off chance that this error is arising from an
underlying library or operating system component and not from within the
images of the translated MONITOR itself.

MONITOR was re-written for the next release after this version; the use
of the translator and the existing MONITOR code was eliminated. The
updated version of MONITOR can be found in the V8.* range of OpenVMS
releases.

--
www.HoffmanLabs.com
Services for OpenVMS

Steve,

I maybe should have said:

As OpenVMS Alpha V7.3-2 is out of support, no PUBLIC fixes can be
expected.

Volker.

In article <1185463804.696925.99420@k79g2000hse.googlegroups.c om>, Volker Halle writes:
>Steve,
>
>I maybe should have said:
>
>As OpenVMS Alpha V7.3-2 is out of support, no PUBLIC fixes can be
>expected.

Maybe. But I expect, that fixes for a PVS paying customer will get
PUBLIC afterwards also...

--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail peter@langstoeger.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

Thanks guys,

I have asked my local support guy, Sek, in oz and he is looking at it.
I assume we are supported, as we keep paying the bills ;-)

FWIW, it is two Alpha's. Looking at rolling out Update 12 in the next
month or so on Non prod and then see if we can get it in to
production.


Cheers

kiwi





On Jul 27, 5:39 am, pe...@langstoeger.at (Peter 'EPLAN' LANGSTOeGER)
wrote:
> In article <1185463804.696925.99...@k79g2000hse.googlegroups.c om>, Volker Halle writes:
>
> >Steve,
>
> >I maybe should have said:
>
> >As OpenVMS Alpha V7.3-2 is out of support, no PUBLIC fixes can be
> >expected.
>
> Maybe. But I expect, that fixes for a PVS paying customer will get
> PUBLIC afterwards also...
>
> --
> Peter "EPLAN" LANGSTOEGER
> Network and OpenVMS system specialist
> E-mail pe...@langstoeger.at
> A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

David J Dachtera wrote:
> kiwi-red wrote:
>>I have asked my local support guy, Sek, in oz and he is looking at it.
>>I assume we are supported, as we keep paying the bills ;-)
>
> yeah - that's what we thought, also - until we called for phone support and
> couldn't understand the person on the other end.

Ironically, folks had the same complaints when the Customer Support
Center in Atlanta first opened up -- folks said they couldn't understand
the Southern accent. Some folks even hung up the phone if they were
connected to a person with a Southern accent. But people learned, over
time, to understand and appreciate each other.

I grew up in a college town with students from all over the world, and
grew to understand (and even enjoy) the variety of English accents.

I taught a seminar for the DECUS user group in Budapest in 2004. They
were only 10 years or so out of Communist rule and most adults (who
already knew Hungarian and Russian) had already learned English as well.
They said if I could have spoken English with a German or French accent
they could have understood me better, but my American accent was too
different and hard to understand. They had my respect and my sympathy,
and we did the best we could together.

Keith Parris wrote:
>
> David J Dachtera wrote:
> > kiwi-red wrote:
> >>I have asked my local support guy, Sek, in oz and he is looking at it.
> >>I assume we are supported, as we keep paying the bills ;-)
> >
> > yeah - that's what we thought, also - until we called for phone support and
> > couldn't understand the person on the other end.
>
> Ironically, folks had the same complaints when the Customer Support
> Center in Atlanta first opened up -- folks said they couldn't understand
> the Southern accent. Some folks even hung up the phone if they were
> connected to a person with a Southern accent. But people learned, over
> time, to understand and appreciate each other.
> [snip]

Um, Keith?

There's rather a difference between vernacular and culture, and people knowing
the product lines, and so on. The language issue is merely a symptom of far
deeper issue.

HP needs to take a lesson from Dell and start pulling support back on-shore.

> I grew up in a college town with students from all over the world, and
> grew to understand (and even enjoy) the variety of English accents.

Likewise, I find it a welcome challenge at such events as the VMS Bootcamp and
"DECUS" Symposia where we talk to/with folks from darn near everywhere. At least
we all know the products. Culture issues are not major, and the language issue
merely a challenge.

> I taught a seminar for the DECUS user group in Budapest in 2004. They
> were only 10 years or so out of Communist rule and most adults (who
> already knew Hungarian and Russian) had already learned English as well.
> They said if I could have spoken English with a German or French accent
> they could have understood me better, but my American accent was too
> different and hard to understand. They had my respect and my sympathy,
> and we did the best we could together.

I spent two weeks at a time in England three times between Jan and Jun of 1984
for work. I came home sounding like a cross between and Yank and a Brit. Lasted
for couple weeks at home, until I re-adjusted myself to talking to everyone in
the local vernacular with a non-British manner.

--
David J Dachtera
dba DJE Systems
http://www.djesys.com/

Unofficial OpenVMS Marketing Home Page
http://www.djesys.com/vms/market/

Unofficial Affordable OpenVMS Home Page:
http://www.djesys.com/vms/soho/

Unofficial OpenVMS-IA32 Home Page:
http://www.djesys.com/vms/ia32/

Unofficial OpenVMS Hobbyist Support Page:
http://www.djesys.com/vms/support/