FTP Server Setup and Configuration

A) Activate the FTP server Component:

To activate the FTP server component, please review and code the following global configuration statements. They are discussed in greater detail in APPENDIX A.

NOTE:

The FTP Server Component shares a great deal of code with the APPC-TCP/IP file transfer server. Therefore, you must activate both components even if you never use the APPC-TCP/IP server. And, this means that you must code the TCP_LISTEN_PORT and at least one TCP_HOST statement. The TCP_HOST must be syntactically correct but the IP address need not be a real one (if you do not wish to use the APPC-TCP/IP server, that is).

1. Review and include the flollowing global statements. They apply to the
    TCP/IP interface as a whole:

   SWITCH_IP_INTERFACE        = YES              ( defalt is NO).
    IP_ID                                         = two digits      (default 00)
    IP_TIMEOUT (IN MINUTES)   = nn                 (default is 10 minutes).

2. The following statements are required by the APPC-TCP/IP file
     transfer server.

   TCP_LISTEN_PORT     = 255
    TCP_HOST                    = 100.100.10.10,PORT=256,NAME=XYZ,TYPE=XFER
    HOST                            = ABCDEFG    (PARTNER VTAM NETNAME)

3. The following statements are required by the FTP server:

   SWITCH_FTP_SERVER_SUPPORT              = YES
    SWITCH_FTP_SERVER_UID_PWD_FOLD = YES | NO
    SWITCH_FTP_SERVERPORT                      = port (default is 259)
    FTP_32K_Buffers                                           = nn (default is 8 buffers).
    FTP_LIBR_MEM_TYPE                                = mem_TYPE,RECF=STRING | FIXED

4 The following statements are required by the application. You
   should review each one and change it if the default is not suitable:

   USER
    ADMIN
    TAPE_DRIVE
    NOTIFY

    VTAM_ACB                                      do not forget this one!!!!!

    NUM_USER_SESSIONS
    NUM_HOST_SESSIONS
    NUM_XFER_SESSIONS
    NUM_WORK_BUFFERS
    NUM_EOR_BUFFERS
    NUM_SCREEN_DEPTH
    NUM_LINE_PER_SCREEN
    NUM_REPORT_PAGE_LEN

    E2A
    A2E

B) Create All Necessary Control files:

Control files are LIBR members. They must be created and saved in the start-up sublibrary. For more info about the start-up sublibrary, please refer to APPENDIX A.

There are two types of control files:

      These control files are referred to in this document as FTPC (FTP
      Client) files. The name of the meber is up to you; however, the type
      of this member is fixed and must be FTPC. Member names will
      eventually show up as subdirectories in the User's home directory.


      These control files are referred to in this document as PROF (profile)
      files. The name of the member must be the same as the USERID the
      PROF belongs to. The type of the member is fixed and must be prof

      Here is what the server does if you do not create a profile for a user:

       a.   grants access to all FTPC members it finds, and
       b.   sets a default mask to * ,   and
       c.   sets properties for each view to ALL, and.
       d.    Enables Delete and Rename properties.

FTP Server Setup and Customization:

Introduction:

The server's Admin must configure the server before general users can use it. To configure the server, the Admin must do two things:

A) Activate the server component itself, and
B) Create all necessary control files.

1. File Views (Required):

2. User Profiles (optional, but!)

HeeeHaaaa..HeeeeHaaaa.. HeeeHaaa

Be mighty careful. Leaving out User Profs is a baaaad idea.