REXEC

The Remote Execution (REXEC) server is a Transmission Control Protocol/Internet Protocol (TCP/IP) application that allows a client user to submit system commands to a remote system. The Remote Execution Protocol (REXEC) allows processing of these commands or programs on any host in the network. The local host then receives the results of the command processing.

The user's client program sends the user identifier, password, and command to run to the server. The server validates the user, runs the requested command, and returns the results of the command to the client.

Commands submitted to the System i™ host fall into the following categories:

i5/OS^® command processor

You run i5/OS command processor commands by specifying QCAPCMD as the target of the client REXEC.

Qshell command interpreter (i5/OS option 30)

You can use the Qshell interpreter by specifying qsh as the target of client REXEC.

"Spawned paths"

You can run any i5/OS program in a "child" (spawned) job by specifying the complete path to the program or shell script as the target of the REXEC command.

• Printable PDF
  Use this to view and print a PDF of this information.

• Changing REXEC server attributes
  The Change REXEC Attributes (CHGRXCA) command and Configure TCP/IP REXEC (CFGTCPRXC) command change the REXEC server attributes.

• REXEC command considerations
  You should be aware of some restrictions when you use the REXEC command.

• Selecting a command processor
  You can select different command processors for the REXEC server by using exit programs.

• REXEC connection usage
  The REXEC protocol allows an REXEC client to specify whether to use one or two connections for returning data.

• Spooled output considerations
  The REXEC server overrides the default printer file (*PRTF) to capture spooled output. Any resulting spooled files are tagged with the user data field set to REXECSVR.

• REXEC client considerations
  Different clients might use a single connection or two connections for returned data.

• REXEC server jobs and job names
  To monitor and process requests from REXEC client users, start REXEC server jobs.

• Creating REXEC server spooled job logs
  To find the errors occurred in the REXEC session, you can create REXEC server spooled job logs.

• Exit points for controlling REXEC server
  The experienced programmer can use exit programs to create customized processing while an application is running.

• Determining problems with REXEC
  If you detect a problem when using the REXEC server, you can use the REXEC flow chart and cause lists to identify potential problems.