iX 6.0)

Chapter 6 81

REMSH Service

Using remsh

The remsh service is accessed by running the REMSH.NET.SYS

program. You may do so under the MPE/iX CI or under the POSIX

shell. While the format of the commands will differ depending on how

you run the program, the parameter list remains the same.

For the purposes of explaining the parameters, look at a sample

invocation from the POSIX shell. Detailed examples of both the POSIX

shell and MPE/iX invocations will follow later.

From the POSIX shell, invoke the remsh by typing:

/SYS/NET/REMSH remotehost -1 remoteuser remotecommand

In all cases you must provide a remotehost and a remotecommand.

The remsh program will fail and generate an error message otherwise.

Unless the remote system has MPE/iX type userids, you will also need

to provide a -l remoteuser parameter as well. Otherwise the remote

system will not allow the connection.

The name of the remote host you are attempting to connect to is

remotehost. The host name can be either the ofﬁcial name or an alias

as understood by gethostbyname().

The userid is remoteuser on the remote system.

NOTE The traditional UNIX implementation of remsh makes the -l

remoteuser parameter optional. If you do not provide a -l

remoteuser parameter, remsh takes your current userID and assumes

that you wish to connect to the same userID on the remote system.

Since the MPE version of the userID is USER.ACCOUNT, and the UNIX

equivalent is user, it is unlikely that you will ﬁnd a user on the remote

system to match your id. We recommend that you always provide the -l

remoteuser argument to remsh.

The remotecommand is the command the user wishes to execute on the

remote machine. This command may be a CI command, a program (that

meets certain criteria) or a shell script. If remotecommand is not

speciﬁed, remsh will terminate and provide a usage message.

NOTE remsh cannot be used to run commands that require a terminal

interface (such as vi) or commands that read their standard error (such

as more).