Preparing the IBM Communications Server › Generate SMF Records for FTP Event Flow

Generate SMF Records for FTP Event Flow

Note: Perform this task only if you want to monitor FTP events.

The Communications Server must be set up to generate the SMF records required for FTP events.

The SMF records are intercepted by the NMFTP Monitor region and are used by the product region to enable the following:

• File Transfer events monitoring
• Event history reporting

To ensure SMF records are generated

1. Add the following line to the PROFILE.TCPIP configuration member to enable the SMF API:

   NETMONITOR SMFSERVICE
   

2. Restart the TCP/IP started task.

Note: Alternatively, you can issue this change in an OBEYFILE.

Generate FTP Post-Processing Transfer Failures Event Flow

Note: Perform this task only if you want to monitor FTP events.

You can use this procedure to monitor all FTP failures.

To generate transfer failures without existing user exit

1. Receive and apply the dsnpref.NMC1.CC2DSAMP(FTPOSTPR) SMP/E USERMOD.

   The FTPOSTPR exit is created.

2. Do one of the following:
   • APF-authorize the dsnpref.NMC1.CC2DLOAD library, and include it as a STEPLIB for your FTP server started task (typically named FTPD).
   • Copy FTPOSTPR from the dsnpref.NMC1.CC2DLOAD library into an existing APF-authorized library that also is included as a STEPLIB to your FTP server job.
   • Copy to a link library known to the linklist.
3. If you are using RACF and program control is active, use the following commands to add FTPOSTPR to program control:

   RDEFINE PROGRAM FTPOSTPR ADDMEM('library'//NOPADCHK) UACC(READ) 
   SETROPTS WHEN(PROGRAM) REFRESH
   

   library

   Identifies the library that contains FTPOSTPR.

To generate transfer failures with existing user exit

1. Modify your existing FTP post-transfer processing user exit (FTPOSTPR) by inserting the following code fragment immediately before exiting:

   *------------(NetMaster For File Transfer Management )----------------- 
   *                                                                       
   *        .------------------------------------------------------------. 
   *        | Call the CA NMFT FTP Post-Transfer Processing module       | 
   *        '------------------------------------------------------------' 
            L     R15,=V(NM000FPX)                                         
            O     R15,=X'80000000'                                         
            BASSM R14,R15                  Call NM000FPX                   
            L     R14,=A(NEXT0000+X'80000000')                             
            BSM   0,R14                    Ensure in 31-BIT if required    
            SPACE 2                                                        
   NEXT0000 DS    0H
   

   These lines are added in the module entry section, and register 1 must point to the parameter list passed to FTPOSTPR.

2. Modify your existing FTP post-transfer processing user exit (FTPOSTPR) link-edit deck by inserting the following:

   //AC2DLOAD DD DISP=SHR,DSN=dsnpref.NMC1.AC2DLOAD
   //SYSLIN   DD    *
      …
      INCLUDE AC2DLOAD (NM000FPX)
      INCLUDE AC2DLOAD (NM000Y51)
      ORDER             NM000FPX
      ORDER             FPXDATA
      ORDER             NM000Y51
      ENTRY    FTPOSTPR
      MODE     AMODE(31)
      MODE     RMODE(ANY)
      NAME     FTPOSTPR(R)
   

3. Submit the modified job to assemble and link edit the exit.
4. Ensure that the user exit load module is in a cataloged data set and placed in an APF authorized library that the FTP server accesses using STEPLIB, linklist, or LPA.

Note: The existing FTP Control Customizer parameter group option Enable FTP Event Receiver (for non-TCPaccess FTP server), also controls the FTP Post Processing User Exit event delivery.