TELL.COM seems simpler :)
Sampsa
On 15 Aug 2012, at 15:01, Steve Davidson wrote:
Sampsa,
For VMS specific you can us SYSMAN. It does NOT require a cluster. It
does require that you specify the username and password of the remote
however.
$ MCR SYSMAN
SYSMAN> set environment/node=<nodename>/user=<username>
Remote Password: <remote accounts password>
SYSMAN> do @foo.com
SYSMAN>
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine
Sent: Wednesday, August 15, 2012 05:20
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] 'rexec' or 'ssh <command>' over DECNET
Well, the logs are transferred over DECNET to the main host
that runs SSH (the others are too slow to run SSH).
But they are generated by a DCL script on the node from which
they are extracted (basically, DCL scripts are run on KUHAVX
and LABVAX which copy the exported logs to SOLAR5).
So I execute the log generation process (which tells KUHAVX +
LABVAX to export their logs to SOLAR5) and then fetch them
from SOLAR5.
Sampsa
On 15 Aug 2012, at 12:15, Johnny Billquist wrote:
On 2012-08-15 11:09, Sampsa Laine wrote:
I am aware of this - I am using this to pull some logs
from a couple of boxes to another, all VMS.
Eh... Are the logs not accessible over DECnet? Seems like
you might be going over the river to get the water...?
Johnny
Sampsa
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to
do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now
is not really generally usable in DECnet, but is rather
VMS-specific. But on the other hand, more or less any
solution will be rather specific...
Not sure that a batch submission is that much different
from your network connection though. Neither is really
similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling
another node to run a DCL script for me, but have totally
forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell
node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use
network communication to a named task.
Another is to submit a batch job on another node. A
third is (I seem to remember) the ability to just request a
program to be run on a remote node, but that might some RSX
specific thing. I can check in manuals if you want to know
more, as my memory is fuzzy on the specifics.
Johnny
Sampsa,
For VMS specific you can us SYSMAN. It does NOT require a cluster. It
does require that you specify the username and password of the remote
however.
$ MCR SYSMAN
SYSMAN> set environment/node=<nodename>/user=<username>
Remote Password: <remote accounts password>
SYSMAN> do @foo.com
SYSMAN>
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine
Sent: Wednesday, August 15, 2012 05:20
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] 'rexec' or 'ssh <command>' over DECNET
Well, the logs are transferred over DECNET to the main host
that runs SSH (the others are too slow to run SSH).
But they are generated by a DCL script on the node from which
they are extracted (basically, DCL scripts are run on KUHAVX
and LABVAX which copy the exported logs to SOLAR5).
So I execute the log generation process (which tells KUHAVX +
LABVAX to export their logs to SOLAR5) and then fetch them
from SOLAR5.
Sampsa
On 15 Aug 2012, at 12:15, Johnny Billquist wrote:
On 2012-08-15 11:09, Sampsa Laine wrote:
I am aware of this - I am using this to pull some logs
from a couple of boxes to another, all VMS.
Eh... Are the logs not accessible over DECnet? Seems like
you might be going over the river to get the water...?
Johnny
Sampsa
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to
do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now
is not really generally usable in DECnet, but is rather
VMS-specific. But on the other hand, more or less any
solution will be rather specific...
Not sure that a batch submission is that much different
from your network connection though. Neither is really
similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling
another node to run a DCL script for me, but have totally
forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell
node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use
network communication to a named task.
Another is to submit a batch job on another node. A
third is (I seem to remember) the ability to just request a
program to be run on a remote node, but that might some RSX
specific thing. I can check in manuals if you want to know
more, as my memory is fuzzy on the specifics.
Johnny
Well, the logs are transferred over DECNET to the main host that runs SSH (the others are too slow to run SSH).
But they are generated by a DCL script on the node from which they are extracted (basically, DCL scripts are run on KUHAVX and LABVAX which copy the exported logs to SOLAR5).
So I execute the log generation process (which tells KUHAVX + LABVAX to export their logs to SOLAR5) and then fetch them from SOLAR5.
Sampsa
On 15 Aug 2012, at 12:15, Johnny Billquist wrote:
On 2012-08-15 11:09, Sampsa Laine wrote:
I am aware of this - I am using this to pull some logs from a couple of boxes to another, all VMS.
Eh... Are the logs not accessible over DECnet? Seems like you might be going over the river to get the water...?
Johnny
Sampsa
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now is not really generally usable in DECnet, but is rather VMS-specific. But on the other hand, more or less any solution will be rather specific...
Not sure that a batch submission is that much different from your network connection though. Neither is really similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
On 2012-08-15 11:09, Sampsa Laine wrote:
I am aware of this - I am using this to pull some logs from a couple of boxes to another, all VMS.
Eh... Are the logs not accessible over DECnet? Seems like you might be going over the river to get the water...?
Johnny
Sampsa
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now is not really generally usable in DECnet, but is rather VMS-specific. But on the other hand, more or less any solution will be rather specific...
Not sure that a batch submission is that much different from your network connection though. Neither is really similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
Not sure that a batch submission is that much different from your network connection though. Neither is really similar to an ssh session, unless I'm missing something.
Long story short, the log pulling is initiated from a Unix box over SSH to a VMS box, which asks the nodes to export the logs and then copy them over.
Once this is complete, the Unix box SCPs the exported logs over.
This way I am sure the log export has finished before initiating the SCP.
Sampsa
I am aware of this - I am using this to pull some logs from a couple of boxes to another, all VMS.
Sampsa
On 15 Aug 2012, at 12:05, Johnny Billquist wrote:
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now is not really generally usable in DECnet, but is rather VMS-specific. But on the other hand, more or less any solution will be rather specific...
Not sure that a batch submission is that much different from your network connection though. Neither is really similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
On 2012-08-15 10:57, Sampsa Laine wrote:
Yes, I was aware of the batch submission, but wanted to do it the "ssh way" for a particular reason..
Ok. Note, however, that the solution you came up with now is not really generally usable in DECnet, but is rather VMS-specific. But on the other hand, more or less any solution will be rather specific...
Not sure that a batch submission is that much different from your network connection though. Neither is really similar to an ssh session, unless I'm missing something.
Johnny
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
Yes, I was aware of the batch submission, but wanted to do it the "ssh way" for a particular reason..
Sampsa
On 15 Aug 2012, at 11:55, Johnny Billquist wrote:
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
On 2012-08-15 08:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
I notice that you figured out one way, which is to use network communication to a named task.
Another is to submit a batch job on another node. A third is (I seem to remember) the ability to just request a program to be run on a remote node, but that might some RSX specific thing. I can check in manuals if you want to know more, as my memory is fuzzy on the specifics.
Johnny
And just answered my own question: The permissions on KUHAVX::SYS$MANAGER:TELL.COM were wrong, it needed W:RE.
Sampsa
On 15 Aug 2012, at 10:38, Sampsa Laine wrote:
So I installed TELL.COM from Freeware on both SOLAR5 and KUHAVX in SYS$MANAGER and followed the NCP instructions, but still get this:
SOLAR5$ tell kuhavx dir
Establishing link to remote node KUHAVX::
%DCL-E-OPENIN, error opening KUHAVX::"task=tell" as input
-RMS-E-ACC, ACP file access failed
-SYSTEM-F-NOSUCHOBJ, network object is unknown at remote node
Any ideas gents?
--
Sampsa
On 15 Aug 2012, at 09:36, Sampsa Laine wrote:
Guys,
I remember there's a clean / elegant way of telling another node to run a DCL script for me, but have totally forgotten how to do it.
Basically, I have three nodes, A, B and C.
I've set up proxies for user FOO across all of them.
Now I want node A (as user FOO) to be able to tell node B and C to run a script on them, as user FOO.
How do I do this?
Sampsa
