FTP exits - syncsort_cobol_migration_manager - syncsort_clone_center - syncsort_space_recovery_system - syncsort_scc_monitor - syncsort_simulate_2000 - syncsort_allocation_control_center - Latest

Enforce Rule-Based Policies for File Transfer

EASY/Exit can receive control and enforce standards and policies from standard exit points within the z/OS FTP Server. These exit points can be used to validate and enforce standards for file transfers, allow or deny FTP access or individual FTP commands, change command arguments, perform logging, and more. The rules and variables provide the means to control FTP use in great detail.

EASY/Exit receives control at each of the FTP Server exit points:

• FTCHKCMD — The FTCHKCMD exit receives control when any FTP command is executed.

• FTPOSTPR — The FTPOSTPR exit receives control upon completion of a file transfer (RETR, STOR, STOU, APPE, DELE, RNTO).

• FTCHKIP — The FTCHKIP exit receives control during FTP login or OPEN commands.

• FTCHKPWD — The FTCHKPWD exit receives control during userid and password authentication.

• FTCHKJES — The FTCHKJES exit receives control when an FTP client submits a job.

By examining and setting the appropriate EASY/Exit variables at each of these exit points, EASY/Exit can enforce standards for FTP processing, issue warnings, alter FTP command parameters and options, write log or SMF records for later analysis, and control many aspects of server-side FTP operation.

When EASY/Exit receives control at any of these exit points, the environment name (the &ENV variable) is the name of the exit point (FTCHKCMD, FTPOSTPR, FTCHKIP, FTCHKPWD, or FTCHKJES). The subenvironment name (the &ENVS variable) is either blank or, for the FTCHKCMD environment, the name of the FTP command being executed.

Some FTP environments may be entered multiple times during an FTP session. For example, the FTCHKCMD environment is entered whenever an FTP command is executed (CWD, RETR, SITE, etc.). The exit is entered anew each time a command is issued. For FTPOSTPR, the exit is entered each time a file is transferred, deleted, or renamed. During a single FTP session, each of the EASY/Exit environments may receive control many times, and the rules may therefore be executed many times.

EASY/Exit communicates with the FTP server via interface modules (FTPs "stubs") that are defined as ordinary exits. These stubs (one per exit point such as FTCHKCMD, FTPOSTPR, FTCHKIP, FTCHKPWD, FTCHKJES) communicate with the DIF started task to run the EASY/Exit policy rules. This design keeps the main DIF and EASY/Exit modules independent of FTP and allows policy rules to be changed without requiring an IPL, relink, or restart of the FTP server.

Before using the FTP environments, the interface module (the "stub") for FTP must be linked into a load library accessible to the FTP server (usually a system linklist library). Once the stub modules are in the linklist library, they will be called whenever an FTP client communicates with the server. Only the modules for the desired environments need be placed in the linklist. If an exit is not to be called, place a dummy module that returns RC=0 in the linklist for security so calls use the dummy module rather than an exposed implementation.

The following sample JCL can be used to link the interface stubs. A copy of this JCL can be found in DTS.R61.SLyyddd.SAMPLIB(EXFTSRVI):

 //JOBCARD JOB ...
 //L       EXEC PGM=IEWL,PARM='XREF,LIST,LET,RENT'
 //SYSPRINT DD SYSOUT=*
 //SYSLMOD  DD DISP=SHR,DSN=<apf.library>
 //SYSLIB   DD DISP=SHR,DSN=<dts.load.library>
 //SYSUT1   DD UNIT=SYSALLDA,SPACE=(CYL,(1,1))
 //SYSLIN   DD *
  INCLUDE SYSLIB(EXCHKCMD) SETCODE AC(1)
  NAME FTCHKCMD(R) INCLUDE SYSLIB(EXCHKPWD) SETCODE AC(1)
  NAME FTCHKPWD(R) INCLUDE SYSLIB(EXCHKJES) SETCODE AC(1)
  NAME FTCHKJES(R) INCLUDE SYSLIB(EXPOSTPR) SETCODE AC(1)
  NAME FTPOSTPR(R) INCLUDE SYSLIB(EXCHKIP) SETCODE AC(1)
  NAME FTCHKIP(R)
 /* (end SYSLIN)
        

Program Control

The FTP exits must reside in an APF-authorized library (usually a linklist library) and must be program-controlled by RACF. To ensure program control, define the exit program names and load library to RACF. For example:

 RDEF PROGRAM FTCHKCMD   ADDMEM('load.library.name') UACC(READ)
 RDEF PROGRAM FTPOSTPR   ADDMEM('load.library.name') UACC(READ)
 RDEF PROGRAM FTCHKIP    ADDMEM('load.library.name') UACC(READ)
 RDEF PROGRAM FTCHKPWD   ADDMEM('load.library.name') UACC(READ)
 RDEF PROGRAM FTCHKJES   ADDMEM('load.library.name') UACC(READ)
 SETROPTS WHEN(PROGRAM) REFRESH
        

Each environment supported by the EASY/Exit FTP Server functions represents a different exit point in FTP processing. During processing, the environment name (&ENV) is the exit point name and the subenvironment name (&ENVS) is the FTP command name, if any. The environment name may therefore be any of the following:

• FTCHKCMD — The command checking exit. Receives control for any FTP command (most commonly used). It can accept or reject a command, and can examine or modify command arguments. If rejected, a customized message can be returned to the client. Use FTCHKCMD to implement security, standardize processing, provide abbreviations/substitutions, etc.

• FTPOSTPR — The post-transfer-processing exit. Gets control when a command causes a file to be transferred, renamed, or deleted. Use it to act on filename, CLOSE return code, FTP reply messages, write SMF/log messages, or take actions based on dataset names or types.

• FTCHKIP — The login exit. Called when a connection is initiated or an OPEN command is issued. It can examine local/remote host addresses and ports and cancel the connection if desired. With EASY/Exit, changing rules does not require restarting the FTP server (a DIF REFRESH is sufficient).

• FTCHKPWD — The password checking exit. Called after the userid and password have been sent but before authentication. Can validate password/userid or anonymous email address, issue messages, write records, or allow/reject the login.

• FTCHKJES — The job submission exit. Called when the client submits a job with FILETYPE=JES. Each control statement is passed to the exit, which can allow or prevent submission based on job/EXEC content.

FTCHKCMD — The FTP Server Command Check Exit

FTCHKCMD is called whenever the server receives an FTP command (RETR, STOR, USER, SITE, etc.). Both the command and its arguments are available to the exit, as well as current directory, file type, session id, and client/server IP addresses and ports. All parameter list values are available as EASY/Exit variables. Although the command itself cannot be changed, command arguments can be modified and the command may be accepted or rejected. If rejected, a customized message can be returned to the client.

Modifying command arguments supports actions such as removing invalid arguments or replacing abbreviations with full parameters.

Environment

The following variables are available specifically in the FTCHKCMD environment. Many usual DIF variables (for example, &SYSID, &CURDATE, &CURTIME) are also available.

Table 13-1. Variables for the FTCHKCMD Server Exit

Table 13-1. Variables for the FTCHKCMD Server Exit (continued)

Examples for the FTCHKCMD Environment

Example 1 — Scan / Replace to Abbreviate Arguments for the SITE Command

The following rule changes the SITE parameter 'ATTR=F80' to 'LRECL=80 BLKSIZE=800 RECFM=FB' and 'ATTR=F133' to 'LRECL=133 BLKSIZE=0 RECFM=FBA' for specified users. Other users receive a syntax error. A copy of this rule is in DTS.R61.SLyyddd.SAMPLIB(EXFTCHK1).

 DEFENV FTCHKCMD MODE(ACTIVE)
 DEFRULE ABBREVIATE
 IF &FTPUSER = (USER1,USER2,TEST*) &FTPCMD = 'SITE' THEN DO
  SET &FTPARGFIND = 'ATTR=F80'
  SET &FTPARGREP  = 'LRECL=80 BLKSIZE=800 RECFM=FB'
  SET &FTPARGCHG  = YES
  SET &FTPARGFIND = 'ATTR=F133'
  SET &FTPARGREP  = 'LRECL=133 BLKSIZE=0 RECFM=FBA'
  SET &FTPARGCHG  = YES
 END /* DO */
      

Example 2 — prevent specified users from issuing SITE command (returns custom message and rejects command). A copy in DTS.R61.SLyyddd.SAMPLIB(EXFTCHK2).

 DEFENV FTCHKCMD MODE(ACTIVE)
 DEFRULE NOSITECMD
 IF &FTPUSER = (USER1,USER2,TEST*) &FTPCMD = 'SITE' THEN
  SET &FTPREPLY = '&FTPUSER MAY NOT ISSUE SITE COMMAND'
  SET &EXIT_RC  = 8
      

FTPOSTPR — The FTP Server Post-File-Processing Exit

FTPOSTPR is called whenever the server completes an FTP file transfer or file processing command (RETR, STOR, STOU, APPE, DELE, RNTO). The CLOSE return code is in &FTPCLOSR and indicates success or failure. The exit can examine file name, file type, directory, FTP reply messages, client/server IPs, etc., and take actions such as issuing messages or writing log/SMF records. At entry, the transfer has already completed (successfully or unsuccessfully).

Environment

These variables are available specifically in the FTPOSTPR environment. Usual DIF variables (&JOBNAME, &SYSID, &CURDATE, &CURTIME, etc.) are also available.

Table 13-2. Variables for the FTPOSTPR Server Exit

Table 13-2. Variables for the FTPOSTPR Server Exit (continued)

Examples for the FTPOSTPR Environment

Example 1 — Write Log/SMF Records for Unsuccessful File Transfers

If an MVS file transfer did not complete successfully (&FTPCLOSR nonzero), write a log record to the DIF log (include dataset name, error message, GB/bytes transferred). For files beginning with 'SYS', write a message to the system console including FTP server (&JOBNAME) and system id (&SYSID). Rule available in DTS.R61.SLyyddd.SAMPLIB(EXFTPOS1).

 DEFENV FTPOSTPR MODE(ACTIVE)
 DEFRULE LOGFAILURES
 IF &ENV = FTPOSTPR &FTPDIRTP = MVS &FTPCLOSR GT 0 THEN DO
  ISSUE WRITEREC(LFAILREC)
  IF &FTPDSNAM = SYS* THEN ISSUE WRITEMSG(CONM1)
 END
 DEFREC LFAILREC
  INIT(BLANKS) DDNAME(DIFLOG) LENGTH(500) FIELD &FTPDSNAM
  FIELD &FTPCMD FIELD &FTPCLOSR FIELD &FTPGBXFR FIELD &FTPBYXFR FIELD &FTPRMSG
 DEFMSG CONM1 WTORC(2)
  'FILE &DSNAME(1,44) FAILED TRANSFER SERVER=&JOBNAME SYSTEM=&SYSID RC=&FTPCLOSR'
      

Example 2— log successful DELETE commands from certain users. Includes filename, date, and time. Copy in DTS.R61.SLyyddd.SAMPLIB(EXFTPOS2).

 DEFENV FTPOSTPR MODE(ACTIVE)
 DEFRULE LOGDELS
 IF &FTPUSER = (USER1,USER2,TEST*) &FTPCMD = 'DELE' &FTPCLOSR = 0
  THEN ISSUE WRITEREC(DELLOG)
 DEFREC DELLOG
  INIT(BLANKS) DDNAME(DIFLOG2) LENGTH(500) FIELD &FTPDSNAM
  FIELD &FTPUSER
  FIELD &CURDATE FIELD &CURTIME
      

FTCHKIP — The FTP Server Login Exit

FTCHKIP is called during initial login or when the user issues an OPEN command. Called early in FTP processing, it can examine IP addresses and ports and accept or reject the connection. If FTCHKIP rejects the login by setting &EXIT_RC nonzero, the message '421 User Exit rejects open for connection' is sent and the connection is broken.

For an ordinary assembler-language FTCHKIP exit, the server must be stopped and restarted to reload the exit after changes. With EASY/Exit, a DIF REFRESH of the rules is sufficient — no server restart is required.

Environment

Variables available specifically in FTCHKIP are listed below. Usual DIF variables (&JOBNAME, &SYSID, &CURDATE, &CURTIME, etc.) are also available.

Table 13-3. Variables for the FTCHKIP Server Exit

Examples for the FTCHKIP Environment

Example — reject logins from IP addresses not in local network (192.168.*.*), and write client IP/port plus date/time to a DIF log. Copy in DTS.R61.SLyyddd.SAMPLIB(EXCHKIP1).

 DEFENV FTCHKIP MODE(ACTIVE)
 DEFRULE ONLYLOCAL
 IF &ENV = FTCHKIP &FTPCLIENTIP NE 192.168.*
 THEN
  SET &EXIT_RC = 8
  ISSUE WRITEREC(ERRREC)
 DEFREC ERRREC
  INIT(BLANKS) DDNAME(DIFLOG) LENGTH(500) FIELD &FTPCLIENTIP
  FIELD &FTPCLIENTPORT FIELD &FTPSERVERIP FIELD &FTPSERVERPORT FIELD &JOBNAME
  FIELD &CURTIME FIELD &CURDATE
      

FTCHKPWD — The FTP Server Password Exit

FTCHKPWD is called after the server has received the userid and password but before authentication. The exit may examine userid, password, client IP/port, user data (if any), make RACF calls, or perform other validation. The number of failed attempts and anonymous email (when applicable) are available. If FTCHKPWD returns a nonzero code, the login attempt is rejected.

For anonymous logins (userid = ANONYMO), when ANONYMOUSLEVEL 3 is specified, the server prompts for an email address and FTCHKPWD is called twice (after USER and after PASS).

Environment

Variables available specifically in FTCHKPWD are listed below. Usual DIF variables are also available.

Table 13-4. Variables for the FTCHKPWD Server Exit

Table 13-4. Variables for the FTCHKPWD Server Exit (continued)

Examples for the FTCHKPWD Environment

Example 1 — Issue Security Checks for FTP Logins

Allow login only if the userid has READ authority to the FTPIN resource in the USRCLAS class. If not authorized, fail the login. Copy in DTS.R61.SLyyddd.SAMPLIB(EXFTPW1).

 DEFENV FTCHKPWD MODE(ACTIVE)
 DEFVAR SAFRC "USRCLAS FTPIN READ"
 EXTER(DIFRACF) NUMERIC
 DEFRULE TESTAUTH
 IF &ENV = FTCHKPWD &FTPDIRTP = MVS &FTPUSER = (STEVE,FRED,TOM*)
  THEN DO
   IF &SAFRC NE 0 THEN SET &EXIT_RC = YES
  END
      

Example 2 — limit all users to a maximum of 3 invalid passwords before failing login and writing a DIF log record (date/time, userid, password specified, bad password count). Copy in DTS.R61.SLyyddd.SAMPLIB(EXFTPW2).

 DEFENV FTCHKPWD MODE(ACTIVE)
 DEFRULE LOGBADPWS
 IF &ENV = FTCHKPWD &FTPBADPW GT 3
  THEN
   SET &EXIT_RC = 8
   ISSUE WRITEREC(BADPWREC)
 DEFREC BADPWREC
  INIT(BLANKS) DDNAME(DIFLOG) LENGTH(500) FIELD &FTPUSER
  FIELD &FTPPASS FIELD &FTPBADPW FIELD &CURDATE FIELD &CURTIME
      

FTCHKJES — The FTP Server Job Submission Exit

FTCHKJES is called after the server is in FILETYPE=JES mode and the client submits a job. Called before submission to the internal reader, it can examine each JCL statement and allow or prevent submission. The exit cannot modify JCL being submitted (other environments such as JES or SMF can). If FTCHKJES returns nonzero, the job is not submitted and the client receives '550 User Exit refuses this job to be submitted by <userid>'.

Environment

Variables available specifically in FTCHKJES are listed below. Usual DIF variables are also available.

Table 13-5. Variables for the FTCHKJES Server Exit

Table 13-5. Variables for the FTCHKJES Server Exit (continued)

Examples for the FTCHKJES Environment

Example 1 — Prevent Job Submission for Specified Users/Systems

Disallow certain userids from submitting jobs to JES. On system 'SYSD', only specific users may submit. Rule copy in DTS.R61.SLyyddd.SAMPLIB(EXFTJES1).

 DEFENV FTCHKJES MODE(ACTIVE)
 DEFRULE CHKJOBS
 IF &ENV = FTCHKJES &FTPUSER = (USER1,USER2,TEST*) THEN
  SET &EXIT_RC = 8
 IF &ENV = FTCHKJES &FTPUSER = (USER9,USER10,XYZ*) &SYSID = 'SYSD'
  THEN EXIT
 ELSE SET &EXIT_RC = 8
      

Example 2 — scan each control statement for fields JOB and MSG. If both found, allow job; if JOB found but not MSG, fail submission. Copy in DTS.R61.SLyyddd.SAMPLIB(EXFTJES2).

 DEFENV FTCHKJES MODE(ACTIVE)
 DEFRULE CHKJCL
 IF &ENV = FTCHKJES THEN DO
  IF &FTPCARD(1,2) = '//' &FTPCARD CONTAINS 'JOB' THEN DO
   IF &FTPCARD CONTAINS 'MSG' THEN SET &EXIT_RC = 0
   ELSE SET &EXIT_RC = 8
  END
 END
      

Debugging Hints for the FTP Server Exits

Tracing DIF rule execution or displaying variable values at the time an environment gets control can help debugging. Two sample rule sets are shown: one displays variable values to the console (WTOR route codes) and the other enables DIF rule tracing by setting trace variables. Consider using a separate FTP server/port for testing.

 DEFENV FTCHKCMD MODE(ACTIVE)
 DEFENV FTCHKJES MODE(ACTIVE) WTORC(2,11)

 *******************************************************
 * DISPLAY VARIOUS VARIABLES
 *******************************************************
 DEFRULE DSPYVARS
 IF &ENV = FTCHKCMD &FTPUSER = STEVE THEN
  ISSUE WRITEMSG(M1,M2,M3,M4,M5,M6,M7,M8,M9,MA)

 *******************************************************
 * TRACE SUBSEQUENT RULE EXECUTION
 *******************************************************
 DEFRULE TRACERUL CONTINUE(NEXTIF) /* CONT AFTER THIS RULE */
 IF &ENV = FTCHKJES &FTPUSER = FRED THEN
  SET &RULE_TRACEACT = YES /* TURN ON TRACE */
  SET &RULE_PALLACT  = YES /* TURN ON TRACE */

 * ... subsequent rules are traced ...
 *******************************************************
 * DISPLAY MESSAGES TO CONSOLE
 *******************************************************
 DEFMSG M1  '******* ENV=&ENV &ENVS &JOBNAME ' WTORC(2,11)
 DEFMSG M2  '** FTPNUMP=&FTPNUMP FTPUSER=&FTPUSER ' WTORC(2,11)
 DEFMSG M3  '** FTPCMD=&FTPCMD' WTORC(2,11)
 DEFMSG M4  '** FTPDIRTP=&FTPDIRTP' WTORC(2,11)
 DEFMSG M5  '** FTPFTYPE=&FTPFTYPE' WTORC(2,11)
 DEFMSG M6  '** FTPCWD=&FTPCWD' WTORC(2,11)
 DEFMSG M7  '** FTPARG=&FTPARG' WTORC(2,11)
 DEFMSG M8  '** FTPREPLY=&FTPREPLY' WTORC(2,11)
 DEFMSG M9  '** FTPSCRCH=&FTPSCRCH' WTORC(2,11)
 DEFMSG MA  '** FTPSESID=&FTPSESID' WTORC(2,11)
      

Enforce Rule-Based Policies for File Transfer (Client-Side)

With z/OS version 2.1 introducing standard client-side exits, EASY/Exit can now enforce standards and policies on the client side as well. The client exits can validate/enforce standards for file transfers, allow or deny FTP access or commands, change command arguments, perform logging, and more. One use case is preventing outbound transfer of certain datasets by z/OS FTP clients. The rules and variables provide detailed control. EASY/Exit receives control at each of the FTP Client exit points:

• EZAFCCMD — Receives control when an FTP client executes a command.
• EZAFCREP — Receives control when an FTP client receives a reply (single-line or multi-line) from a server; called once per line of a multi-line reply.

By examining and setting the appropriate variables at these exit points, EASY/Exit can enforce client-side standards, issue warnings, alter command parameters, write logs/SMF records, and even terminate the FTP client/connection. When EASY/Exit receives control at these points, &ENV is the exit point name (EZAFCCMD or EZAFCREP) and &ENVS is either blank (for EZAFCREP) or, for EZAFCCMD, the FTP command being executed.

Client exits are entered multiple times during a session; the connection id (FTPCONID) remains constant for the session.

EASY/Exit automatically loads necessary modules and invokes z/OS Dynamic Exits to allow rules to get control. Server-side exits require a stub module, but client-side exits (EZAFCCMD and EZAFCREP) do not require stubs. Simply include the DEFENV statements for each environment in the rules, for example:

 DEFENV EZAFCCMD MODE(ACTIVE)
 DEFENV EZAFCREP MODE(ACTIVE)
        

When these statements are present, the z/OS Dynamic Exits facility will add the EASY/Exit routines for the client exits when EASY/Exit starts and remove them when it terminates.

Program Control (Client Exits)

Client exit modules must reside in an APF-authorized library and be program-controlled by RACF. Define program names and load library to RACF. For example:

 RDEF PROGRAM EZAFCCMD ADDMEM('load.library.name') UACC(READ)
 RDEF PROGRAM EZAFCREP ADDMEM('load.library.name') UACC(READ)
 SETROPTS WHEN(PROGRAM) REFRESH
        

To use client exits successfully, add the FTP program name to the TSO Authorized Program Table (IKJTSOxx member of SYS1.PARMLIB concat). 'FTP' must be listed in AUTHCMD and AUTHPGM. If missing, the FTP client start will fail with an error like:

 CSVDYNEX DEFINE failed for user exit EZAFCCMD / EZAFCREP RETURN CODE x'08' REASON CODE x'00000804'
        

The FTP Client Environments

For client exits, the environment name (&ENV) is the exit point and the subenvironment (&ENVS) is the FTP command, if any. For client exits the environment name may be:

EZAFCCMD — Command checking exit on the client. Receives control for any FTP command before it is sent to the server. It can accept, reject, examine, or modify the command arguments, or terminate the client before sending. If rejected or terminated, a customized message can explain the reason. Use it to implement client-side security, standardize processing, provide abbreviations/substitutions, and logging.

EZAFCREP — The Client Reply Exit

EZAFCREP is called when the client receives a reply over the control connection. For multi-line replies, it is called once per line. It can examine replies and take actions (write logs/SMF records, notify TSO users, terminate the connection). If terminating the connection, additional lines not yet passed to the client are flushed.

EZAFCCMD receives control whenever the client issues a command (before sending), with command, arguments, current directory, dataset/filename, file type, connection id, and client/server IPs/ports available as variables. Although the command cannot be changed, arguments can be modified or replaced, and the client or command can be rejected or terminated with customized messages.

Variables in the EZAFCCMD Environment

Environment

Variables available specifically in EZAFCCMD are listed below. Usual DIF variables (&SYSID, &CURDATE, &CURTIME, etc.) are also available.

Table 13-6. Variables for the EZAFCCMD Server Exit

Table 13-6. Variables for the EZAFCCMD Server Exit (continued)

Examples for the EZAFCCMD Environment

Example 1 — prevent outbound transfer (PUT) of datasets beginning with 'PROD' or 'SYS*'; terminate FTP client with an error message. Rule in DTS.R61.SLyyddd.SAMPLIB(EZEXCMD1).

 DEFENV EZAFCCMD MODE(ACTIVE)
 DEFRULE NOOUTBND
 IF &FTPCMD = 'PUT' &FTPDSN = (PROD.*, SYS*) THEN
  SET &EXIT_RC = 12      /* kill the client */
  SET &FTPREPLY = 'YOU MAY NOT TRANSFER PROD FILES!'
      

Example 2 — Scan / Replace to Remove Arguments in FTP Commands

Remove the 'ALL' parameter on the DUMP command to prevent excessive output, and change any PROTECT CLEAR to PROTECT SAFE. Copy in DTS.R61.SLyyddd.SAMPLIB(EZEXCMD2).

 DEFENV EZAFCCMD MODE(ACTIVE)
 DEFRULE NODUMPALL
 IF &FTPCMD = 'DUMP' THEN
  SET &FTPARGFIND = 'ALL'
  SET &FTPARGREP  = 'BLANK'
  SET &FTPARGCHG  = YES
 IF &FTPCMD = 'PROT' THEN
  SET &FTPARGFIND = 'CLEAR'
  SET &FTPARGREP  = 'SAFE'
  SET &FTPARGCHG  = YES
      

Example 3 — log DELETE, RENAME, RMDIR commands (successful or not) issued by certain users; include filename, date, and time. Copy in DTS.R61.SLyyddd.SAMPLIB(EZEXCMD3).

 DEFENV EZAFCCMD MODE(ACTIVE)
 DEFRULE LOGDELS
 IF &FTPUSER = (USER1,USER2,TEST*) &FTPCMD = (DELETE, RENAME, RMDIR) THEN
  ISSUE WRITEREC(DELLOG)
 DEFREC DELLOG
  INIT(BLANKS) DDNAME(DIFLOG2) LENGTH(500) FIELD &FTPCMD
  FIELD &FTPDSNAM FIELD &FTPUSER FIELD &CURDATE FIELD &CURTIME
      

EZAFCREP — The FTP Client Reply Exit

EZAFCREP is called whenever the client receives a single-line reply or a line of a multi-line reply from the server. It can examine replies and take actions (write messages, log records, terminate the client). Use EZAFCREP together with EZAFCCMD to act based on commands and replies.

Environment

Variables available specifically in EZAFCREP are listed below. Usual DIF variables are also available.

Table 13-7. Variables for the EZAFCREP Server Exit

Configuration Variables for the FTP Client Exits

Local FTP client configuration options are available as read-only variables in EASY/Exit. Values may change between invocations (e.g., after a SITE command). The table below lists names of local client configuration options; each EASY/Exit variable name should be prefixed with FT_.

Table 13-8. Configuration Variables for the FTP Client Exits

Table 13-8. Configuration Variables for the FTP Client Exits (continued)