Previous Topic: TCP/IP FTP InterfaceNext Topic: TCP/IP REXEC Interface


TCP/IP NFS Interface

The CA ACF2 for z/VM interface with TCP/IP NFS is implemented by using the ESM feature of NFS. 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 NFS.

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

  1. If your site has installed CMS security, add the VMNFS ID to the MAINT VMO record and use the ACFSERVE RELOAD CONTROL VMO MAINT command to reload the maint vmo record. This prevents NON CNCL logging records from being created when CMS files are validated.
  2. From a security administrator's user ID, provide the following logonid attributes to VMNFS:
    VMESM
    
    VMSAF
    
    VMD4AUTH
    
    VMD4TARG
    
    VMD4RSET
    
    NON CNCL (only if CMS security is installed)
    
  3. Copy the following files to the TCPMAINT 198 minidisk to make them accessible to VMNFS and other TCP/IP service machines, if not already there:
    ACFSAFA0 MODULE
    

    If not already there, copy the following file from the CAIMAINT 291 to the TCPMAINT 198 minidisk to make it accessible to VMNFS 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
    
  4. In the SYSTEM DTCPARMS file, change the following lines in the :nick.nfs section. If you don't have a section with the :nick.nfs 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.

  5. The use of CA‑ESM requires that your NFS service machine (normally VMNFS) directory entry must include the following statement:
    IUCV *RPI