On 2012-07-11 23:27, Bob Armstrong wrote:
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Hmmmm, PONDUS thinks that 1.250 is unreachable too. You guys will have to
work that one out.
And 1.250 came online 23:36, about 10 minutes after this was posted... I suspect the "guilty" person is the owner of that node... :-)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2012-07-11 23:15, Steve Davidson wrote:
This one is easy :-)
LEGATO:: does not know about TARDIS::.
-Steve
A fairly up-to-date nodename list can be copied from PONDUS:: for the time being, as MIM:: is down.
Johnny
------------------------------------------------------------------------
*From:* owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
*On Behalf Of *Tony Blews
*Sent:* Wednesday, July 11, 2012 17:12
*To:* hecnet at update.uu.se
*Subject:* Re: [HECnet] SMTP <-> MAIL11 Gateway
Hi, I've just tried this and got this error mailed back to me:
Bad address -- <"tardis::tony">
Error --
%MAIL-E-LOGLINK, error creating network link to node TARDIS
-SYSTEM-F-NOSUCHNODE, remote node is unknown
And mailing from the VMS box gives me this:
MAIL> mail
To: legato::smtp%tonyblews at gmail.com
<mailto:legato%3A%3Asmtp%25tonyblews at gmail.com>
%JBC-E-JOBQUEDIS, system job queue manager is not running
This is probably my fault, so what am I doin wrong?
On Wed, Jul 11, 2012 at 8:55 PM, Bob Armstrong <bob at jfcl.com
<mailto:bob at jfcl.com>> wrote:
I ve set up an Internet SMTP to HECnet MAIL11 gateway. To
send mail from the Internet to a HECnet node, address it to____
____
user at node.decnet.org <mailto:user at node.decnet.org>____
____
where user is the VMS (or RSX or RSTS or whatever) user name
and node is the HECnet node name. If you re logged into a
HECnet machine you can send Internet mail by addressing it to____
____
LEGATO::SMTP%user at whereever.com <mailto:user at whereever.com>____
____
Note that LEGATO will store mail sent in either direction for up
two days if the target node is down at the time that means
your HECnet machine doesn t have to be online 24x7 in order to
receive mail.____
____
IMPORTANT - There is absolutely no SPAM filtering, so please be
very careful about where or how you publish these addresses
unless you want your VMS mailbox filled up with thousands of
SPAMs ____
____
Bob____
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
On 2012-07-11 17:16, Bob Armstrong wrote:
You can't take the default on *all* questions, since some don't have ny
defaults.
The CSR and vector for the terminal lines, for example... :-)
You're right - I did have to enter the address for that one.
:-)
Simh is rather simple minded about the terminal muxes - it considers the
DZ11/DZV11/DZQ11/CYX08/CXY16 all to be the same. Although the hardware is
different as far as I know they all have the same programmer model so this
is not unreasonable. The only thing that differs is the number of lines per
board, and simh allows you to set that.
I thought the CXY muxes had a different interface than the DZ, but if I remember that one wrong, then I guess you should be ok.
And the only floating vector in this configuration, AFAIK, is the DZ/CXY
and 300 is the first one, right?
Yes. But vectors should be less of an issue. However, the floating CSR address is the more important one.
FWIW I did a VMS SYSGEN (which, among other things allows you to enter a
list of devices and will calculate for you the correct CSR/vector
assignments) and it agrees with simh in that regard. It particular, it says
160100 and vector 300 for the DZ11. As far as I know the PDP-11 and VAX
rules for address and vector assignments are the same, but it's possible RSX
does something different. It's suspicious that the default answer for the
first DZ11 in the RSX SYSGEN is not the same as the default floating address
assignment.
No. For autoconfigure, the architecture does not matter. It's a set of rules for the bus, not the CPU.
The RSX SYSGEN is not clever enough to calculate a reasonable default value for CSR addresses of devices. So it just gives a fixed value as the default, if it gives a default at all.
The other devices (MSCP disk, MSCP tape, NI) are all their default
addresses for the first such device.
Yes. Actually, the first device of those types have a fixed address.
You really need to make sure your hardware is correctly configured before
you can expect ACF to work.
Sure, but that's the whole question. I think this is the correct
configuration unless you can see what's wrong.
I thought the CXY looked different from a DZ, which is why I thought things were wrong. Since it would appear I was wrong on that, I can't see any problems. And in the next post, you even note yourself that it works fine, if you just select another CPU, so it would definitely appear that your config here is ok.
The other possibility that there's some hardware in there that this
version of ACF doesn't know about.
Don't appear to be, and I would have been surprised if there had been.
I guess I could do another SYSGEN and just take out the DZ/CXY from the
simh configuration. That's easy enough to do.
I guess at this point, we're beyond that.
However, the fact that ACD fails if you select an 11/53 in simh, but works if you select an 11/73 makes me wonder if there is something funny in the 11/53 CPU type in simh.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Yeah, I forgot the quotes... but so did you in your original post :)
Ah it takes me back to the days when we had to bounce mail through 2 different relays to get it out of our local network at the university.
Tony.
On Wed, Jul 11, 2012 at 9:24 PM, Bob Armstrong <bob at jfcl.com> wrote:
>$start/queue/manager (in SYS$STARTUP:SYSTARTUP_VMS.COM)
FWIW, you don t actually need the queue manager running in order to send
mail. This is just a bogus error because Tony got the syntax of the address
wrong.
Bob
On 2012-07-11 18:14, Jordi Guillaumes i Pons wrote:
Hi,
After reading the real experts discussing about the difficulties one has to expect generating a 11M (no plus) system I wanted to test it first hand and I've (almost) successfully sysgene'd from scratch a RSX11M 4.6 system from its tape distribution. I said "almost" because I've run into 2 little problems, one of those probably coming from my lack of knowledge about RSX itself...
Heh... Isn't it fun...? :-)
1) I get no "REMove" task built. I've tried a SYSGEN3 and it doesn't get built either. I wonder if that task is absent from the "standard function" system and I will have to do a fully customized SYSGEN.
REMove is not a task. It's a built-in command in MCR.
2) Even being logged on a privileged account I can't write anything under [1,54] unless I SET /UIC first. I get a privilege violation error when I try to PIP something if I have any other default directory. That causes installation scripts to fail (I've tried to install F77 and it aborts when it tries to copy the OTS and the compiler task. My SYSUID is set to [1,54]. I guess I'm missing something but have no clue about what is it.
That is because when you do a SET /UIC in 11M on a privileged terminal, it always changes both your protection uic and default uic.
Privileges are somewhat different in concept and implementation in RSX to what you would think and expect in other OSes.
This is a slightly longer story than I feel like writing here on the spot. Suffice to say that your above description is correct, and that is the expected behavior.
I'll try and write something up later, and post here if people really want to know...
If I can overcome these problems I plan to publish the installation log to help anyone wanting to do the same...
Excellent!
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Hmmmm, PONDUS thinks that 1.250 is unreachable too. You guys will have to
work that one out.
Bob
%MAIL-E-LOGLINK, error creating network link to node LEGATO
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
Which would make sense since I can't see 1.250 either... I think PONDUS
is the router for area 1 now that MIM is gone - have to kick this question
up to Johnny.
Bob
$start/queue/manager (in SYS$STARTUP:SYSTARTUP_VMS.COM)
FWIW, you don t actually need the queue manager running in order to send
mail. This is just a bogus error because Tony got the syntax of the address
wrong.
Bob
Which now gives me the slightly more logical error:
MAIL> mail
To: legato::smtp%"tonyblews at gmail.com"
%MAIL-E-LOGLINK, error creating network link to node LEGATO
-SYSTEM-F-UNREACHABLE, remote node is not currently reachable
On Wed, Jul 11, 2012 at 9:17 PM, Steve Davidson <jeep at scshome.net> wrote:
LEGATO::SMTP%user at whereever.com
Should read:
LEGATO::SMTP%"user at whereever.com"
-Steve
You're end.
$start/queue/manager (in SYS$STARTUP:SYSTARTUP_VMS.COM)
You could use autostart if you wish. I do not because my startup depends on queues starting up in a particular order.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Tony Blews
Sent: Wednesday, July 11, 2012 17:17
To: hecnet at update.uu.se
Subject: Re: [HECnet] SMTP <-> MAIL11 Gateway
D'oh!
As for the second part, does it mean that the queue manager isn't running on my machine, or the distant one, as local mail seem to work fine.
On Wed, Jul 11, 2012 at 9:15 PM, Steve Davidson <jeep at scshome.net> wrote:
This one is easy :-)
LEGATO:: does not know about TARDIS::.
-Steve
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Tony Blews
Sent: Wednesday, July 11, 2012 17:12
To: hecnet at update.uu.se
Subject: Re: [HECnet] SMTP <-> MAIL11 Gateway
Hi, I've just tried this and got this error mailed back to me:
Bad address -- <"tardis::tony">
Error --
%MAIL-E-LOGLINK, error creating network link to node TARDIS
-SYSTEM-F-NOSUCHNODE, remote node is unknown
And mailing from the VMS box gives me this:
MAIL> mail
To: legato::smtp%tonyblews at gmail.com
%JBC-E-JOBQUEDIS, system job queue manager is not running
This is probably my fault, so what am I doin wrong?
On Wed, Jul 11, 2012 at 8:55 PM, Bob Armstrong <bob at jfcl.com> wrote:
I ve set up an Internet SMTP to HECnet MAIL11 gateway. To send mail from the Internet to a HECnet node, address it to
user at node.decnet.org
where user is the VMS (or RSX or RSTS or whatever) user name and node is the HECnet node name. If you re logged into a HECnet machine you can send Internet mail by addressing it to
LEGATO::SMTP%user at whereever.com
Note that LEGATO will store mail sent in either direction for up two days if the target node is down at the time that means your HECnet machine doesn t have to be online 24x7 in order to receive mail.
IMPORTANT - There is absolutely no SPAM filtering, so please be very careful about where or how you publish these addresses unless you want your VMS mailbox filled up with thousands of SPAMs
Bob
