T4 V4,0 MONITOR.EXE imcompatible to VMS MONITOR.EXE

[Karl Rohwedder]

Just to give you a hint to avoid needless error searching:

The T4 V4.0 supplied MONITOR_ALPHA.EXE (id X-22) is not compatible with the latest MONITOR.EXE for VMS/Alpha V8.2 (id X-24).
When making reports using the standard MONITOR.EXE using binary data collected with the T4-image, ACCVIO's may occur (not always but reproducable in some cases).

Fix: copy the newer MONITOR to the T4$SYS directory under the name MONITOR_ALPHA.EXE.

regards Kalle

[Karl Rohwedder]

Since it was just a hint I closed it.

[John Abbott_2]

Thanks Karl, actually hit this problem yesterday! Another point is that if you have T4 installed and you upgrade from VMS 7.3-2 to 8.2 (what I did) T4 monitor part fails - subprocess fails to find T4$SYS:MONITOR_ALPHA.EXE (under 7.3-2 it has another name - *NODRIFT*.EXE). I suspect you can simply copy the missing image out of the T4 kit, but I elected to re-install T4, as it's so easy to do !

J.

[Ian Miller.]

you could report this by email to
T4 at hp

[Karl Rohwedder]

That's what I did i parallel :-)

Kalle

[Martin Vorlaender]

Kalle,

does the 8.2 MONITOR.EXE time drift?

IIRC, that was the cause for the T4 provided EXE files, and I think I heard the time drift suppress code didn't make it into the 8.2 image.

cu,
Martin

[Jess Goodman]

What is T4?

[Ian Miller.]

What is T4
from
http://h71000.www7.hp.com/OpenVMS/products/t4/

"T4 stands for Total Timeline Tracking Tool. It runs on HP OpenVMS systems with the purpose of capturing and consolidating important OpenVMS performance statistics. Pulling from several (currently seven) independent yet cooperating sources, T4 lets you create a relatively compact composite timeline view of the day-to-day performance of each important OpenVMS node."

[Karl Rohwedder]

Had a mail from Steve Liemann (responsible for T4). Fix for the problem is to comment out the definition of a MONITOR logical name in T4$COLLECT.COM, i.e. use the system default monitor image.

regards Kalle

[Karl Rohwedder]

And again an update:
The image T4$MON:EXTRACT.EXE cannot read monitor datafile created with VMS standard MONITOR.EXE (neither from V8.2 or V8.3) (gets an 'bad header format' error)

Steve Liemann may send you an updated version of the T4$mon_extract images that seem to work.

regards Kalle

[GUINAUDEAU_1]

hello,

The T4$MON_EXTRACT.EXE image of latest T4 kit i found (V4.3) will not extract under my Alpha VMS V8.3 the data, exact error message

...
Program name : T4$MON_EXTRACT, Image file id : X-5 , Link date/time : 1-OCT-2003 21:19:37.90.
T4EXTR-F-UNRECFMT, Unrecognized record format
%SYSTEM-W-BADFILEHDR, bad file header

i dont find a newest image version

=> where could i download it ?

Louis Guinaudeau

[Volker Halle]

Louis,

you seem to be using an older T4$MON_EXTRACT.EXE image. The one from the T4 V4.3 kit has:

Image Identification Information
image name: "T4$MON_EXTRACT"
image file identification: "X-15"
image file build identification: ""
link date/time: 26-JUN-2006 09:06:41.02
linker identification: "A13-03"

Volker.

[GUINAUDEAU_1]

Hi Volker,

that was it !

The installed kit under that machine was not V4.3 but V4.2 !

I installed now the V4.3 kit.

Using
SYS$SYSTEM:MONITOR.EXE VMS V8.3
(X-26, 18-JUN-2008 08:55:26.82)
T4$MON_EXTRACT.EXE of T4 kit V4.3
(X-15, 26-JUN-2006 09:06:41.02)

The data collection created by this MONITOR image could be extracted by this extractor image without error and examined further with T4 tools (e.g., TLViz)

Thanks for your help

Louis