I had to try too, under VAX/VMS 5.5-2:
$ monitor
MONITOR> monitor ethernet
%MONITOR-E-NOCLASSES, no classes specified
MONITOR> monitor notthere
%MONITOR-E-INVCLSNM, class-name "NOTTHERE" is invalid or not uniquely identified
MONITOR>
Erik
On Mon, Jan 14, 2013 at 04:51:47PM +0000, lee.gleason at comcast.net wrote:
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
----- Original Message -----
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
On 14 Jan 2013, at 11:51, lee.gleason at comcast.net wrote:
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
MISSY::SYSTEM$ monitor ethernet
MONITOR> exit
MISSY::SYSTEM$ monitor notthere
%MONITOR-E-INVCLSNM, class-name "NOTTHERE" is invalid or not uniquely identified
This is on VMS 8.4.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
--
Cory Smelosky
http://gewt.net/ Personal stuff!
http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.
Correction:
On VAX/VMS 6.1 monitor ethernet results in the Monitor> prompt.
Retyping monitor ethernet gives:
Monitor-E-Noclasses, no classes specified
Monitor blabla (in monitor) gives class name BLABLA is iinvalid or not uniquely identified.
On AXP/VMS 8.3
Mon ethernet gets the Monitor> prompt and retyping it gives nothing, just Monitor> again. Monitor blabla gives the same error as on VAX.
Hans
From: lee.gleason at comcast.net
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 14 Jan 2013 16:51:47 +0000 (UTC)
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Cc: <hecnet at Update.UU.SE>
Subject: Re: [HECnet] SCSISE adapter -> listings
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
I recall, that that indicates at least some support is still there. See what happens when you do MONITOR BADCLASS or any other nonexistent class - it should be different.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Monday, January 14, 2013 10:58:19 AM
Subject: Re: [HECnet] SCSISE adapter -> listings
Curious that I am I did try
MONITOR ETHERNET on a VAX/VMS 6.1 system and on an AXP/VMS 8.3 system and all I saw was the command prompt.
No other output.
From: lee.gleason at comcast.net
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 14 Jan 2013 16:51:47 +0000 (UTC)
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Cc: <hecnet at Update.UU.SE>
Subject: Re: [HECnet] SCSISE adapter -> listings
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
VMS, VAX 7.3:
LABVAX::SAMPSA$ monitor ethernet
MONITOR> exit
LABVAX::SAMPSA$ monitor foobar
%MONITOR-E-INVCLSNM, class-name "FOOBAR" is invalid or not uniquely identified
LABVAX::SAMPSA$
VMS, AXP, 8.3:
CHIMPY$ monitor ethernet
MONITOR> exit
CHIMPY$ monitor foobar
%MONITOR-E-INVCLSNM, class-name "FOOBAR" is invalid or not uniquely identified
CHIMPY$
VMS, I64, 8.4:
{RHESUS$} monitor ethernet
MONITOR> exit
{RHESUS$} monitor foobar
%MONITOR-E-INVCLSNM, class-name "FOOBAR" is invalid or not uniquely identified
{RHESUS$}
So looks like the hidden classes are in there, anyone know how to write a patch for this? :)
sampsa
On 14 Jan 2013, at 18:51, lee.gleason at comcast.net wrote:
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
Curious that I am I did try
MONITOR ETHERNET on a VAX/VMS 6.1 system and on an AXP/VMS 8.3 system and all I saw was the command prompt.
No other output.
From: lee.gleason at comcast.net
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 14 Jan 2013 16:51:47 +0000 (UTC)
To: <hecnet at Update.UU.SE>
ReplyTo: hecnet at Update.UU.SE
Cc: <hecnet at Update.UU.SE>
Subject: Re: [HECnet] SCSISE adapter -> listings
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
I wrote the original patches for Monitor that enabled those hidden classes, and the Pagewapper article that detailed how to apply them
I haven't had an opportunity to check on newer versions of VMS, but it's trivial to see if at least some support is still there for them.
On a VMS system, try
$ MON ETHERNET
or any of the other undocumented monitor classes. Then try a command that definitely isn't going to be there
$ MON NOTTHERE
If the error messages are different - then at least some of the support for the undocumented classes is still there.
--
Lee K. Gleason N5ZMR
Control-G Consultants
lee.gleason at comcast.net
From: "H Vlems" <hvlems at zonnet.nl>
To: hecnet at Update.UU.SE
Sent: Sunday, January 13, 2013 2:21:30 PM
Subject: RE: [HECnet] SCSISE adapter -> listings
Brian,
Speaking of source listings, VMS V4.<mumble> had a "secret" patch for
MONITOR.EXE. It enabled the monitor class Ethernet. Is that code still
hidden in MONITOR?
The MONITOR utility was written in PL/I at the time. Probably rewritten,
right?
Hans
Larry is an old friend he and I left dec after to compaq-tion. He recently retired althought i think is still doing some consulting as needed. CJ Coppersmith was the vms technical director at that time and the architect of galaxy
On Jan 14, 2013, at 10:13 AM, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote:
Clem Cole <clemc at ccc.com> writes:
On Jan 13, 2013, at 3:25 PM, "Brian Schenkenberger, VAXman-"
<system at TMESIS.= COM> wrote >=20 > There were only 3 or 4 modules
written in PL/I. Those were rewritten in C= . > Why not Bliss? Dunno.
I'd have to ask Larry or CJ but if Culter had anything to do with it
Larry Kenah? Long gone from VMS horizon... CJ isn't lighting any bulb
at the moment.
that wo= uld explain it. He disdained Bliss (and of course led both C
& PL/1 compil= ers).
Perhaps that's why he was absent after the early VMS development days. ;)
The rest of the code was Macro or Bliss. The pieces rewitten in C have
poor code to comment ratio (as too much of the code being rewritten into
C has had) and still rely on calling the $GETSPI written in Bliss. It's
not an issue of likes/dislikes. It was a question of why go out of ones
way to recode in C. It doesn't fit in well with VMS either. Too many
escape to VMS support routines to fill in the holes. There's no macro
capability for one and scant pre-initialized data support (strings and
some struct and arrays).
if you look at NT source while its C/C++ some of us think he tried to
morp= h it into PL/1=
I don't look at things Micro$oft. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Clem Cole <clemc at ccc.com> writes:
On Jan 13, 2013, at 3:25 PM, "Brian Schenkenberger, VAXman-"
<system at TMESIS.= COM> wrote >=20 > There were only 3 or 4 modules
written in PL/I. Those were rewritten in C= . > Why not Bliss? Dunno.
I'd have to ask Larry or CJ but if Culter had anything to do with it
Larry Kenah? Long gone from VMS horizon... CJ isn't lighting any bulb
at the moment.
that wo= uld explain it. He disdained Bliss (and of course led both C
& PL/1 compil= ers).
Perhaps that's why he was absent after the early VMS development days. ;)
The rest of the code was Macro or Bliss. The pieces rewitten in C have
poor code to comment ratio (as too much of the code being rewritten into
C has had) and still rely on calling the $GETSPI written in Bliss. It's
not an issue of likes/dislikes. It was a question of why go out of ones
way to recode in C. It doesn't fit in well with VMS either. Too many
escape to VMS support routines to fill in the holes. There's no macro
capability for one and scant pre-initialized data support (strings and
some struct and arrays).
if you look at NT source while its C/C++ some of us think he tried to
morp= h it into PL/1=
I don't look at things Micro$oft. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
It's ADSL with an uplink speed of just 500 kb/s. So be patient...
From: Saku Set l <setala at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Mon, 14 Jan 2013 16:44:17 +0200
To: <hecnet at update.uu.se>
ReplyTo: hecnet at Update.UU.SE
Subject: Re: [HECnet] AXP/VMS 8.4
3rd try... it was not a good idea to try to copy all the files at the same time.
--Saku
On Mon, Jan 14, 2013 at 12:19 AM, Dave McGuire <mcguire at neurotica.com> wrote:
On 01/13/2013 05:17 PM, hvlems at zonnet.nl wrote:
Yes, when you see them they're done.
The zip file is called Znnnnnnnn. while the utility is running.
Perfect, thanks!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
