On Wed, Feb 20, 2013 at 5:20 PM, Dave McGuire <mcguire at neurotica.com> wrote:
On 02/20/2013 05:19 PM, Gregg Levine wrote:
Right! He wasn't talking about the audience of hungry big cats
surrounding your place that are eating things we don't want to know
about.
You really should write. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
Well your next door neighbors are completely out of their pets and
even their cars.
This does not explain why your network connection is now belonging to them.....
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 02/20/2013 05:19 PM, Gregg Levine wrote:
Right! He wasn't talking about the audience of hungry big cats
surrounding your place that are eating things we don't want to know
about.
You really should write. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Wed, Feb 20, 2013 at 5:00 PM, Dave McGuire <mcguire at neurotica.com> wrote:
I think he was talking about the typo, end_fo_file vs. end_of_file..
-Dave
On 02/20/2013 07:18 AM, Steve Davidson wrote:
That is just a simple check for end of file on read. When it reaches
the EOF it closes the open file(s). The early close statements include
error checking as well. That allows debugging and ensures that the file
is closed before the attempted open.
BTW - This procedure gets around all the issues that Johnny's procedure
may be running into. It does the right thing for all VMS systems. It
also skips the current area so that local databases that are
cluster-based will not get clobbered. This can be a problem if DECnet
is used for cluster communications. It does not have to be regenerated
each time a database update occurs. The data file it uses is
regenerated automatically by Johnny's procedures. That's the reason for
the file in the first place.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Dennis Boone
Sent: Tuesday, February 19, 2013 10:41
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet Area Request
Grab the file SG1::[DECNET]NU2.COM. Ignore the errors.
It does depend > on MIM being defined as 1.13. This
procedure makes use of the file >
MIM::DU4:[DECNET]NODENAMES.DAT. Johnny creates this file for
this > procedure. I will not update your area nodes - that
is your > responsibility. It can be run interactively or
via batch. It must be > run from a priv'd account.
Steve,
Edumacation question. There are a number of places in
NU2.COM where it uses the switch /end_fo_file= [sic]
Unless I'm missing something "meta" about how this thing
works, and assuming it _does_ work, that succeeds in spite of
the typo because...
...DCL only looks at the first 4?
De
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
Right! He wasn't talking about the audience of hungry big cats
surrounding your place that are eating things we don't want to know
about.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
I think he was talking about the typo, end_fo_file vs. end_of_file..
-Dave
On 02/20/2013 07:18 AM, Steve Davidson wrote:
That is just a simple check for end of file on read. When it reaches
the EOF it closes the open file(s). The early close statements include
error checking as well. That allows debugging and ensures that the file
is closed before the attempted open.
BTW - This procedure gets around all the issues that Johnny's procedure
may be running into. It does the right thing for all VMS systems. It
also skips the current area so that local databases that are
cluster-based will not get clobbered. This can be a problem if DECnet
is used for cluster communications. It does not have to be regenerated
each time a database update occurs. The data file it uses is
regenerated automatically by Johnny's procedures. That's the reason for
the file in the first place.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Dennis Boone
Sent: Tuesday, February 19, 2013 10:41
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet Area Request
Grab the file SG1::[DECNET]NU2.COM. Ignore the errors.
It does depend > on MIM being defined as 1.13. This
procedure makes use of the file >
MIM::DU4:[DECNET]NODENAMES.DAT. Johnny creates this file for
this > procedure. I will not update your area nodes - that
is your > responsibility. It can be run interactively or
via batch. It must be > run from a priv'd account.
Steve,
Edumacation question. There are a number of places in
NU2.COM where it uses the switch /end_fo_file= [sic]
Unless I'm missing something "meta" about how this thing
works, and assuming it _does_ work, that succeeds in spite of
the typo because...
...DCL only looks at the first 4?
De
--
Dave McGuire, AK4HZ
New Kensington, PA
Some day, some day
On Wed, Feb 20, 2013 at 3:15 PM, G. <gerry77 at mail.com> wrote:
On Wed, 20 Feb 2013 13:00:13 +0200, you wrote:
> Maisa is still there, but I had to move it to another location, so you have
> to telnet using ip address 212.226.161.98.
Thanks! I missed it :)
Last interactive login on Saturday, 3-NOV-2012 22:53
BTW, will it be clustered again as it was in the good ol' times? :)
G.
On Wed, 20 Feb 2013 13:00:13 +0200, you wrote:
Maisa is still there, but I had to move it to another location, so you have
to telnet using ip address 212.226.161.98.
Thanks! I missed it :)
Last interactive login on Saturday, 3-NOV-2012 22:53
BTW, will it be clustered again as it was in the good ol' times? :)
G.
CHIMPY offers accounts, but no guest account per se.
telnet://chimpy.sampsa.com/
sampsa
On 19 Feb 2013, at 13:22, G. <gerry77 at mail.com> wrote:
Once upon a time, when I wanted to play with HECnet or check something, I used
to telnet and login into a VMS node called MAISA, and from there I was able to
access the whole HECnet. Now MAISA seems long gone and today I remembered that
I can directly telnet to MIM, and so I did. But now I'm wondering wether is
somewhere available a publicly accessible list of telnetable HECnet nodes
offering guest access to the network... Is there something of that sort? :)
Thanks!
G.
That is just a simple check for end of file on read. When it reaches
the EOF it closes the open file(s). The early close statements include
error checking as well. That allows debugging and ensures that the file
is closed before the attempted open.
BTW - This procedure gets around all the issues that Johnny's procedure
may be running into. It does the right thing for all VMS systems. It
also skips the current area so that local databases that are
cluster-based will not get clobbered. This can be a problem if DECnet
is used for cluster communications. It does not have to be regenerated
each time a database update occurs. The data file it uses is
regenerated automatically by Johnny's procedures. That's the reason for
the file in the first place.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Dennis Boone
Sent: Tuesday, February 19, 2013 10:41
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet Area Request
Grab the file SG1::[DECNET]NU2.COM. Ignore the errors.
It does depend > on MIM being defined as 1.13. This
procedure makes use of the file >
MIM::DU4:[DECNET]NODENAMES.DAT. Johnny creates this file for
this > procedure. I will not update your area nodes - that
is your > responsibility. It can be run interactively or
via batch. It must be > run from a priv'd account.
Steve,
Edumacation question. There are a number of places in
NU2.COM where it uses the switch /end_fo_file= [sic]
Unless I'm missing something "meta" about how this thing
works, and assuming it _does_ work, that succeeds in spite of
the typo because...
...DCL only looks at the first 4?
De
Gerry,
Maisa is still there, but I had to move it to another location, so you have to telnet using ip address 212.226.161.98.
--Saku
On Tue, Feb 19, 2013 at 1:22 PM, G. <gerry77 at mail.com> wrote:
Once upon a time, when I wanted to play with HECnet or check something, I used
to telnet and login into a VMS node called MAISA, and from there I was able to
access the whole HECnet. Now MAISA seems long gone and today I remembered that
I can directly telnet to MIM, and so I did. But now I'm wondering wether is
somewhere available a publicly accessible list of telnetable HECnet nodes
offering guest access to the network... Is there something of that sort? :)
Thanks!
G.
