From PORTMAP to RPCBIND

This task describes how to move safely from the PORTMAP to the RPCBIND service.

About this task

The following steps can help you to move safely from PORTMAP to RPCBIND service:

Procedure

Create a PROCLIB member RPCBIND similar to PORTMAP

//**************************************************************
//RPCBIND  PROC
//*
//*   TCP/IP FOR MVS
//*   SMP/E DISTRIBUTION NAME: EZARBBND
//*   FUNCTION: UNIX SYSTEM SERVICES RPCBIND SERVER MAIN PROCESS
//*
//RPCBIND  EXEC PGM=RPCBIND,REGION=4096K,TIME=1440
//*
//STDOUT   DD SYSOUT=*
//STDERR   DD SYSOUT=*
//SYSOUT   DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//         PEND

(Optional) Change TCP/IP profile to autolog RPCBIND instead of PORTMAP
Note: Skip this step in case you want to manage RPCBIND as a SA z/OS® resource.
```
;AUTOLOG
   RPCBIND    ; RPCBIND is required for NFS
;ENDAUTOLOG                                   
```
(Optional) Change TCP/IP profile to reserve port 111 tcp and udp for RPCBIND instead of PORTMAP
Note: This step is required if you have port reservation for portmapper. Edit the TCP/IP profile and change from PORTMAP to RPCBIND. Skip this step if you do not have port reservation for portmapper and if you do not intend to have port reservation for RPCBIND.
```
PORT
   111  TCP RPCBIND             ; RPCBIND SERVER
   111  UDP RPCBIND             ; RPCBIND SERVER
```
Update RACF® For the definition of the started task user and further security settings for RPCBIND see the sample jobs that are provided in <hlq>.SEZAINST(EZARACF). Do a FIND on RPCBIND.
SA z/OS 3.3 update policy
1. Modify application RPCBIND:
  - Add a HasParent relationship to TCPIP/APL/=
  - Add a ForceDown relationship to TCPIP:
    - Relationship: ForceDown
    - Supporting resource: TCPIP/APL/=
    - Condition: WhenObservedHardDown
2. Modify application OMPROUTE:
  - Modify the ForceDown relationship to TCPIP:
    - Relationship: ForceDown
    - Supporting resource: TCPIP/APL/=
    - Condition: WhenObservedAssumedDownOrStopping