TCP/IP REXEC Interface

Installation Options › TCP/IP REXEC Interface

TCP/IP REXEC Interface

The CA ACF2 for z/VM interface with TCP/IP REXEC is implemented by using the ESM feature of REXEC. CA ACF2 for z/VM uses our SAF interface to process calls from CA‑ESM (release 1.1 or above) to provide the ESM functions to REXEC.

Follow the steps below to implement the TCP/IP REXEC Interface:

From a security administrator's user ID, provide the following logonid attributes to REXECD:
```
VMESM
```
```
VMSAF
```
Copy the following file from the CAIMAINT 291 to the TCPMAINT 198 minidisk to make it accessible to REXECD and other TCP/IP service machines, replacing any existing version:
```
ACFSAFAO MODULE
```
If not already there, copy the following file from the CAIMAINT 291 to the TCPMAINT 198 minidisk to make it accessible to REXECD and other TCP/IP service machines:
```
CAIRPI PARMS
```
Modify the CAIRPI PARMS file on the TCPMAINT 198 minidisk to make sure that the APPLNAME is OTHER (not the default SFS):
```
ESMID *RPI     APPLNAME OTHER
```
In the SYSTEM DTCPARMS file, change the following lines in the :nick.rexec section. If you don't have a section with the :nick.rexec tag, you can copy the section from the IBM DTCPARMS file. The SYSTEM DTCPARMS file should be located on the TCPMAINT 198 disk, and it overides the IBM DTCPARMS file.
From:
```
:ESM_Enable.NO
```
```
:ESM_Validate.RPIVAL
```
```
:ESM_Racroute.RPIUCMS
```
To:
```
:ESM_Enable.Yes
```
```
:ESM_Validate.ACFSAFA0
```
```
:ESM_Racroute.RPIUCMS
```
```
:VMLink.CAIMAINT 391
```
Note: If you are upgrading from CA ACF2 for z/VM release 4.1 or earlier, change the ESM_Racroute.RPIDUMY back to the original IBM value of ESM_Racroute.RPIUCMS and add the new :VMLink. tag as listed above.
The use of CA‑ESM requires that your REXEC service machine (normally REXECD) directory entry must include the following statement:
```
IUCV *RPI
```