Thanks Johnny,
Yes, I got it sorted in the end, pretty much down to me not following instructions, but then the options weren't always obvious.
The information is still very informative.
Mark
Hi Steve,
Yes, thanks. In the end once I'd got the proxy configuration set at both ends (the transfer involves an index file push and then a data file pull) I had to work out that I needed to use Gold-Menu to pull up the option to actually perform the transfer.
Took me four hours to transfer a set of files from one box to another mind - hardly and efficient process!
Regards, Mark.
On Sun, 5 Feb 2012, Steve Davidson wrote:
> -----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens
Sent: Saturday, February 04, 2012 12:44
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Help requested with issue regarding
file transfer...
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.
Bizarrely (and I'm sure Steve Davidson will have something to
say about
this) the instructions are telling you to set up the proxy
the wrong way round.
When I added the proxy on the target system back to the
system doing the copying it worked fine.
... onto the next step...
Regards, Mark.
Mark,
Are you all set with this?
-Steve
On 2012-02-04 18:35, Mark Wickens wrote:
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!
I think you're working now, but I figured I could add some comments on proxy access, which might help you and others.
Proxy access is essentially a way for you to specify that a specific user, from a specific machine, should get access rights as a specific other user on the local machine if they do not specify any user information.
As a good example, here is the proxy definitions on MIM::
PROXY>list
Remote User Local Account
----------- -------------
*::* DECNET (DEFAULT)
ERNIE::BILLQUIST BILLQUIST
MAGICA::* * (DEFAULT)
MIM::* * (DEFAULT)
PONDUS::BILLQUIST BILLQUIST
STARS2::DAVIDSON DAVIDSON
PROXY>
So, anyone on HECnet, with any username, will by default access MIM:: as the user DECNET. (This is because under RSX, there is no default DECnet account, so I implemented the same through proxy, which works if both sides have enabled proxy)
Next line is that BILLQUIST (me) on node ERNIE:: will have access on MIM as user BILLQUIST (well, ok, that is also me). This means I don't have to enter username and passwords on ERNIE when I want to access my stuff on MIM.
Next. Anyone from MAGICA:: will have access on MIM:: with the same username. Since the username databases are (supposedly) synced between MIM and MAGICA, this is a nice thing to do, so people don't have to enter passwords all over the place. They expect to be able to access their files on MIM without hassle, if they are logged in to MAGICA.
Next, anyone on MIM:: can connect to MIM::, getting access with the name he have. Essentially, you can access your own stuff on MIM, even if you go over DECnet, with the correct rights.
Then I also have an entry for me from PONDUS:: to MIM::. Same deal as from ERNIE.
Last is an entry I have for DAVIDSON. I don't remember exactly why I set that one up, but it just allows him to access files on MIM from STARS2, without having to pass credentials.
I hope this will make people understand a little better what proxy is, and how it can be used.
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
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens
Sent: Saturday, February 04, 2012 12:44
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Help requested with issue regarding
file transfer...
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.
Bizarrely (and I'm sure Steve Davidson will have something to
say about
this) the instructions are telling you to set up the proxy
the wrong way round.
When I added the proxy on the target system back to the
system doing the copying it worked fine.
... onto the next step...
Regards, Mark.
Mark,
Are you all set with this?
-Steve
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.
No, I'm wrong, it's in the manual, it's just in a subsequent section which doesn't really help when you're following the instructions step-by-step.
Mark.
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.
Bizarrely (and I'm sure Steve Davidson will have something to say about this) the instructions are telling you to set up the proxy the wrong way round.
When I added the proxy on the target system back to the system doing the copying it worked fine.
... onto the next step...
Regards, Mark.
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.
