Preparing CA TCPaccess CS › Generate SMF Records for FTP Event Flow

Generate SMF Records for FTP Event Flow

You must implement the software for the product region to generate SMF Records for the FTP event flow.

To generate SMF Records for the FTP event flow

1. Check the IJTCFGxx configuration member to ensure that all of the subtypes that you require will be generated.

   The SMF TYPE parameter identifies whether or not SMF records are created.

   Note: If your SMF statement does not specify SUBTYPE or has SUBTYPE(ALL), you can skip this step.

   The SMF statement includes a SUBTYPE parameter. This allows specific subtypes to be selected or suppressed. Do the following:

   • If the parameter is set to ALL, leave it as it is.
   • If the parameter is set to NONE, set it to ALL or a list of the subtypes that you require.
   • If the parameter is set to a list of subtypes, set it to ALL or a list of the subtypes that you require.

   This product uses SUBTYPE 20, FTP data set transfer completion (RETR, STOR, and APPE).

2. Copy the NMDSPAXS load module supplied in dsnpref.NMC1.CC2DLOAD to a library accessible to CA TCPaccess CS, for example a library in the CA TCPaccess CS started task STEPLIB.
3. Define NMDSPAXS as a CA TCPaccess CS exit by adding the following statement to IJTCFGxx member:

   EXIT PROGRAM (NMDSPAXS)
   

   Note: Insert the NMDSPAXS definition in the first position of the exit list. This ensures that the exit is always called.