Automatically Starting the REXEC Server
The AUTOSTARTsetting in the REXEC configuration affects the operation of the
STRTCP command. It has no effect on the STRTCPSVR command.The
STRTCPSVR command ignores the AUTOSTARTparameter value. If you run the
STRTCPSVR SERVER (*REXEC) command when the REXEC server is running,
the system starts one additional REXEC server.
Ending the REXEC Server
Specify the
End TCP/IP Server
(ENDTCPSVR) command with the server attribute
set to *REXEC, as follows:
ENDTCPSVR SERVER(*REXEC)
Changing Attributes
The

Change REXEC Attributes

(CHGRXCA) command changes the REXEC server
attributes. The following are two ways to get to this command prompt:
vSpecify the

Change REXEC Attributes

(CHGRXCA) command.
vSelect Option 17 on the
Configure TCP/IP Applications
(CFGTCPAPP) display.
Note: Youmust have *IOSYSCFG special authority to make changes to the
REXEC attributes with the CHGRXCA command.
Change REXEC Attributes (CHGRXCA)
Type choices, press Enter.
Autostart server........ *YES *YES, *NO, *SAME
Number of initial servers . . . 2 1-20, *SAME, *DFT
Inactivity timeout....... 300 1-2147483647, *SAME, *DFT
Coded character set identifier 00437 1-65533, *SAME, *DFT
REXEC Command Considerations
The REXEC server is restricted to running commands that are allowed in batch
jobs. The command must have *BATCH as one of the

Where allowed to run

values.
The maximum length of a command that the REXEC server can process is 4000
bytes. Some REXEC clients limit the command to a smaller length.
For spawned paths, the program that runs in the child process must be either a
program object in the QSYS.LIB file system (*PGM object) or a shell script. You
must specify the path with the proper syntax for the file system in which the file
resides.
For Qshell commands, you can put the same commands that you would enter at an
interactive command line into a non-interactive shell script.
Figure 240. Change REXECAttributes (CHGRXCA)
400 OS/400 TCP/IPConfiguration and Reference V4R4
|
|
|
|
|
|
|
|
|
|
|