On 04/02/12 17:19, Oleg Safiullin wrote:
UAF> ADD/PROXY SLAVE::allin1 A1$XFER_OUT
Is this proxy command appropriate in this case? I thought maybe it should be A1$XFER_IN?
Any help gratefully appreciated.
Thanks, Mark.
Not sure, but ADD/PROXY SLAVE::allin1 A1$XFER_OUT/DEF may help.
Hi Oleg,
Unfortunately that didn't help. Proxy access is all completely new to me unfortunately!
Mark.
UAF> ADD/PROXY SLAVE::allin1 A1$XFER_OUT
Is this proxy command appropriate in this case? I thought maybe it should be A1$XFER_IN?
Any help gratefully appreciated.
Thanks, Mark.
Not sure, but ADD/PROXY SLAVE::allin1 A1$XFER_OUT/DEF may help.
Hi guys,
Could someone help me with a file transfer issue. I'm trying to get ALLIN1 to transfer all my documents from my VAX to my ALPHA. This happens via a management menu and a submitted batch job, but that job fails.
I've narrowed it down to a copy operation:
$ COPY oa$transfer:[MSW]pat_MSW.dat -
SLAVE"A1$XFER_IN"::oa$loaduser:[000000]pat_MSW.dat
%COPY-E-OPENOUT, error opening SLAVE"A1$XFER_IN"::OA$LOADUSER:[000000]PAT_MSW.DAT; as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-INVLOGIN, login information invalid at remote node
The account A1$XFER_IN exists on SLAVE, as does the target directory.
The instructions before transfer include setting up a proxy between the two accounts:
UAF> ADD/PROXY SLAVE::allin1 A1$XFER_OUT
Is this proxy command appropriate in this case? I thought maybe it should be A1$XFER_IN?
Any help gratefully appreciated.
Thanks, Mark.
On 1/24/2012 8:37 PM, Steve Davidson wrote:
Mark,
Look at the file MIM::DU4:[DECNET]LATGROUPS.TXT, then configure your
DECserver to use the LAT groups assigned to your network.
-Steve
HE LIVES! :-D
-brian
Mark,
Look at the file MIM::DU4:[DECNET]LATGROUPS.TXT, then configure your
DECserver to use the LAT groups assigned to your network.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens
Sent: Tuesday, January 24, 2012 18:09
To: hecnet at Update.UU.SE
Subject: [HECnet] Access to SLAVE via LAT from local
DECserver - permission denied...
Hi guys,
My node SLAVE is configured for LAT as follows:
Node Name: SLAVE LAT Protocol
Version: 5.3
Node State: On
Node Ident: AlphaServer 1000A 5/300 VMS Alpha V8.3 MSW,
Windermere, UK
Incoming Connections: Enabled Incoming Session
Limit: None
Outgoing Connections: Enabled Outgoing Session
Limit: None
Service Responder: Disabled Announcements:
Enabled
Circuit Timer (msec): 80 Keepalive Timer
(sec): 20
Retransmit Limit (msg): 8 Node Limit
(nodes): None
Multicast Timer (sec): 60 CPU Rating:
0
Maximum Unit Number: 9999 Extra Datalink
Buffers: 9
Queue Limit: 24 Forward Session
Limit: 16
User Groups: 20, 23
Service Groups: 20, 23
Service Classes: 1
Service Name Status Rating Identification
SLAVE Available 81 D AlphaServer 1000A 5/300
VMS Alpha
V8.3 M
SW, Windermere, UK
I have a DECserver 90M connected locally, but I get a
connection refused when I attempt a CONNECT SLAVE.
Is this a permissions issue I need to sort via configuration
on SLAVE, or is this something to do with the DECserver configuration.
Thanks, Mark.
Hi guys,
My node SLAVE is configured for LAT as follows:
Node Name: SLAVE LAT Protocol Version: 5.3
Node State: On
Node Ident: AlphaServer 1000A 5/300 VMS Alpha V8.3 MSW, Windermere, UK
Incoming Connections: Enabled Incoming Session Limit: None
Outgoing Connections: Enabled Outgoing Session Limit: None
Service Responder: Disabled Announcements: Enabled
Circuit Timer (msec): 80 Keepalive Timer (sec): 20
Retransmit Limit (msg): 8 Node Limit (nodes): None
Multicast Timer (sec): 60 CPU Rating: 0
Maximum Unit Number: 9999 Extra Datalink Buffers: 9
Queue Limit: 24 Forward Session Limit: 16
User Groups: 20, 23
Service Groups: 20, 23
Service Classes: 1
Service Name Status Rating Identification
SLAVE Available 81 D AlphaServer 1000A 5/300 VMS Alpha V8.3 M
SW, Windermere, UK
I have a DECserver 90M connected locally, but I get a connection refused when I attempt
a CONNECT SLAVE.
Is this a permissions issue I need to sort via configuration on SLAVE, or is this something
to do with the DECserver configuration.
Thanks, Mark.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Kari Uusimaki
Sent: Tuesday, January 17, 2012 9:13 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Is Pathworks32 server CTerm part exists?
Pinocchio,
It takes a while for me to find the Pathworks CD's. I have an unsorted
collection of hundreds of DEC software CD's and I have to dig into the
boxes and go through them to pick the right ones.
Please have patience.
When I have the CD's available, I prefer to upload them to my own VMS
machine for your pick up. I'll tell you about the locations when
everything is ready.
Kari
Wonderful!
Waiting impatiently!
Thank you!
On 17.1.2012 20:16, Pinocchio wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Kari Uusimaki
Sent: Tuesday, January 17, 2012 9:56 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Is Pathworks32 server CTerm part exists?
On 16.1.2012 20:43, Pinocchio wrote:
P.S. Do anyone have DOS version of Pathworks in archives?
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one
do you prefer?
Kari
What a luck! Please, upload both!
Thank you!
P.S. I am not part of HECnet yet, so please upload it on some free hosting
like http://www.mediafire.com/
P.P.S. It's my secondary reply to your message. For unknown to me reason
first post seems is lost in eternity :-) (I did not receive it via mail list
for about half hour). So I performing repost now. And to be on the safe side
I am sorry for double posting in case first reply finally would find it
destination sometime.
.
Pinocchio,
It takes a while for me to find the Pathworks CD's. I have an unsorted collection of hundreds of DEC software CD's and I have to dig into the boxes and go through them to pick the right ones.
Please have patience.
When I have the CD's available, I prefer to upload them to my own VMS machine for your pick up. I'll tell you about the locations when everything is ready.
Kari
2012/1/17 Kari Uusim ki <uusimaki at exdecfinland.org>:
On 16.1.2012 20:43, Pinocchio wrote:
Thank you all, for useful information on CTERM subject!
While playing with Pathworks32 v7.4 I did found and fixed one bug, which
can
in some cases prevent successful installation of Pathworks32 at least on
W2K/W2K3 platforms. If network card service registry path (mine is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\e1yexpress) last
component (e1yexpress) longer than 8 characters - network card would never
be listed on last installation step. So you would be unable to bind DECnet
to network interface. Of course there is always way to manually bind them
via editing registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DECNDIS\Linkage\Bind,
but this way is not very convenient. Buggy component responsible for this
activity is w2k\pwbind.exe executable on installation CD. If anyone would
interested in - I can post patched binary (24k) or binary diff description
here.
P.S. Do anyone have DOS version of Pathworks in archives?
.
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one do you
prefer?
Kari
Hello!
I don't know, you pick. Now as for accessing the location, that'll be
a problem because I only have normal (What's that?) Internet access
here.
Basically either version will work for me. If you want to make both
ones available, then that's okay as well.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On 16.1.2012 20:43, Pinocchio wrote:
Thank you all, for useful information on CTERM subject!
While playing with Pathworks32 v7.4 I did found and fixed one bug, which can
in some cases prevent successful installation of Pathworks32 at least on
W2K/W2K3 platforms. If network card service registry path (mine is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\e1yexpress) last
component (e1yexpress) longer than 8 characters - network card would never
be listed on last installation step. So you would be unable to bind DECnet
to network interface. Of course there is always way to manually bind them
via editing registry at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DECNDIS\Linkage\Bind,
but this way is not very convenient. Buggy component responsible for this
activity is w2k\pwbind.exe executable on installation CD. If anyone would
interested in - I can post patched binary (24k) or binary diff description
here.
P.S. Do anyone have DOS version of Pathworks in archives?
.
I might have PW for DOS V5 or V6 (or maybe both) someplace. Which one do you prefer?
Kari