Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

RSH between OpenVMS machines without password

 
SOLVED
Go to solution
Volker Halle
Honored Contributor

Re: RSH between OpenVMS machines without password

smsc_1,

 

what is the error message ? Please add a $ DEF SYS$PRINT NLA0: into the script, run it again and then check the MAINSCRIPT.LOG file in the login directory of the user on the remote node, under which this script runs.

 

Volker.

EdgarZamora_1
Respected Contributor

Re: RSH between OpenVMS machines without password

You asked a simple question "How do you do rsh without using passwords?" and the simple answer is use tcpip communications proxies (as Steven S. already told you in an earlier response but you may have not noticed because he had it in an attachment).   TCPIP HELP ADD PROXY

 

 

RBrown_1
Trusted Contributor

Re: RSH between OpenVMS machines without password


@smsc_1 wrote:

 

mainscript.com (on remote machine)

copy dka100:[log]test.log dka101:[000000]

 Then execute it on local machine with:

SUBMIT /REMOTE ABCD::DKA101:[SCRIPTS]mainscript.com

 This works fine, but if I add the following line on mainscript.com:

 

copy dka100:[log]test.log dka101:[000000]
@DKA101:[SCRIPTS]test.com

 

 

Where are the dollar signs? Each command line in a DCL command file must start with a dollar sign ($). If you leave them out, the first line might be executed, but the rest are not.

 

As mentioned by another, you should tell us the error message.

 

 

John Gillings
Honored Contributor
Solution

Re: RSH between OpenVMS machines without password

As others have suggested, use a TCPIP proxy that's what they're for! Perhaps a full example will help?

 

Two nodes NODEA and NODEB one user MYSELF has an account on each machine. You want MYSELF to be able to execute RSH commands from each node to the other without a password.

 

NODEA> TCPIP ADD PROXY MYSELF /HOST=NODEB/REMOTE_USER=MYSELF
NODEA> TCPIP SHOW PROXY

VMS User_name     Type      User_ID    Group_ID   Host_name

MYSELF            CD     MYSELF                   NODEB


NODEB> TCPIP ADD PROXY MYSELF /HOST=NODEA/REMOTE_USER=MYSELF
NODEB> TCPIP SHOW PROXY

VMS User_name     Type      User_ID    Group_ID   Host_name

MYSELF            CD     MYSELF                   NODEA


NODEA> RSH NODEB SHOW SYSTEM/NOPROCESS
OpenVMS V8.4  on node NODEB   24-AUG-2011 07:20:19.15   Uptime  150 21:12:53


NODEA> RSH NODEB RSH NODEA SHOW SYSTEM/NOPROCESS
OpenVMS V8.4  on node NODEA   24-AUG-2011 07:21:03.45   Uptime  164 14:19:24

 

 


One trick, sometimes the proxy doesn't appear as "CD" immediately, especially in a cluster with a shared proxy data base. In those cases, you need the magic, undocumented incantation executed on all cluster nodes:

 

$ TCPIP SET TCP/SIGNAL

 

(I've never fully understood what it actually means, or why it's necessary, but the upshot is it refreshes the proxy data base).

A crucible of informative mistakes
John Gillings
Honored Contributor

Re: RSH between OpenVMS machines without password

Steven,

   I'm sure you already know this... Since going to the new system, your responses appear only as text attachments. The interface is bad enough without having to jump out of the thread to open an attachment to read a few lines of text. Can't you find a way to post responses so they appear in line?

A crucible of informative mistakes
Steven Schweda
Honored Contributor

Re: RSH between OpenVMS machines without password

 
smsc_1
Regular Advisor

Re: RSH between OpenVMS machines without password

      

People, I would like to thanks all for helping me expecially John Gillings that show me the proxy example.

 

Just one more question. It's not important because I need to execute commnad from NODEB, but just to know in case I need it in the future.

 

I setup both proxy but I can execute the command only from "NODEB" to "NODEA".

If I start the command from NODEA I receive the following:

 

NODEA:USER> RSH NODEB SHOW SYSTEM/NOPROCESS
%RSH-E-FAILED, TCPIP$RSH - Permission denied - host IP addr
 (from remote)

 

This is the proxy configuration from NODEA

NODEA:USER> TCPIP SHOW PROXY
 VMS User_name     Type      User_ID    Group_ID   Host_name
USER              CD     USER                     NODEB

 

 This is the proxy configuration from NODEB

NODEB:USER> tcpip show proxy
 VMS User_name     Type      User_ID    Group_ID   Host_name
USER              CD     USER                     NODEA

 

 

As advice by John I used the following command without success :(

 

NODEA:USER> TCPIP SET TCP/SIGNAL
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 1 proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records
-TCPIP-I-SERVTOTAL, total of 1 proxy records read

 

Users are the same on both machines.

 

 

./ Lucas
Hoff
Honored Contributor

Re: RSH between OpenVMS machines without password

Ensure that the rsh server is configured and enabled on the target VMS server.  Via TCPIP$CONFIG or related.

 

And FWIW, I would discourage use of rsh for application-level operations.  It's intended for interactive use.  Given VMS's lack of an "expect" command or related, processing errors or untoward results from the target rsh-triggered script/procedure is comparatively hairy.  

 

While DECnet DCL is (also) a hack, that provides a bi-directional communications path you can use to detect and report remote activity and particularly remote failures.  (While IP task-to-task communications would be a useful enhancement to DCL, I don't see that happening.)