How to code CTL_FTPC statements...

You may code none, some or all of the following statements:

CTL_FTPC_TIME = HHMM-nnnnnnnn

   This statement assigns a history, or log, key to this view. If you do not code it, the server assigns a special key,
   2400-00000000. This key tells the server NOT to log events associated with this file view. This may be desirable if you
   up/down-load thousands of LIBR members and you wish to skip logging.

   code values for HHMM-nnnnnnnn as follows:

      HH            choose any value between 00 and 23
      MM           choose any value between 00 and 59.
       -               Dash, or minus sign. Code exactly as is.
      nnnnnnnn   choose a string of eight hex-decimal digits. The lowest must be 00000001 and NOT 00000000.


    Examples:

      CTL_FTPC_TIME = 0001-00000001 .
      CTL_FTPC_TIME = 2359-FFFFFFFF

    Default: 2400-00000001 (i.e., do not log events (GET and PUT) associated with this file view.


CTL_FTPC_STRIP = YES or NO

   This statement tells the server what to do with trailing blank characters:

     Yes: Strip them (do not send to client)
     No:   Pass trailing blanks to client.

    Default: NO (i.e., Pass trailing blanks to cient).

CTL_FTPC_PAD = nn where dd is any one of the 256 EBCDIC bytes.

   This statement tells to add, or PAD, incoming logical records with the nn character. Paddind applies only to Fixed
   logical records.

    The default padding character is 40 (i.e., pad records with blanks, if necessary).

   Example::

       CTL_FTPC_PAD = 5C     * Pad with Asterisks.

CTL_FTPC_STREAM = stream_type

   This statement locks the stream to ASCII, EBCDIC or BINARY. Client commands, such as TYPE = IMMAGE, are
   IGNORED by the server (i.e., do not actually change stream type). There is a way, however, to force the server to
   change stream type.

   Please notice that LIBR member TYPES listed in FTP_LIBR_MEM_TYPE are ALWAYS transferred in BINARY mode.

Examples:

       CTL_FTPC_STREAM = ASCII
       CTL_FTPC_STREAM = EBCDIC
       CTL_FTPC_STREAM = BINARY

   Default:

       CTL_FTPC_STREAM = ASCII

CTL_FTPC_EOLINE = value

   This statement impact downloads, i.e., GETs. It has no bearing on uploads. The server, blindly, adds end-of-logical-record
    sequence as follows:

   CTL_FTPC_EOLINE = BOTH:      Adds ASCII carriage return and line feed codes.
   CTL_FTPC_EOLINE = LF            Adds ASCII Line Feed code.
   CTL_FTPC_EOLINE = CR           Adds ASCII Carriage return code.
   CTL_FTPC_EOLINE = NL           Adds EBCDIC NewLine code.

   Default:

       If the statement is not coded at all or if the value coded is not valid, the server�s action is based on the
       STREAM type (FTPC_STREAM_TYPE) as follows:

      FTPC_STREAM_TYPE                                       CTL_FTPC_EOLINE

       ASCII:                                                                BOTH
       EBCDIC:                                                             NL
       BINARY:                                                             nothing is added.

CTL_FTPC_PUT_USER = NOTIFY_THIS_ID
CTL_FTPC_PUT_GOOD = 12340000000A
CTL_FTPC_PUT_BAD = 12340000000B

CTL_FTPC_GET_USER = NOTIFY_THIS_ID
CTL_FTPC_GET_GOOD = 000000000002
CTL_FTPC_GET_BAD = 11340000000D

The first set of statements tells the server what to do at the end of a client�s PUT command. You may code none, some, or all statements.

The second set of statements tells the server what to do at the end of a client�s GET command. You may code none, some or all statements.

CTL_FTPC_XXX_USER:       Notify this user at the end of operation via POWER�s Broadcast command.
CTL_FTPC_XXX_GOOD:     12 hexadecimal digits �Dbase object ID� to execute if the operation succeeds.
CTL_FTPC_XXX_BAD:        12 hexadecimal digits �Dbase object ID� to execute if the operation fails.

�So how do I get this Dbase Object ID?�, One might ask. Well, the application assigns it when you create the object. For example, if you want the server to submit a job at the end of a put, then you must first create a job object. Once created, come back to the file view and plug in the assigned Dbase object ID. Please see chapter 5 for more info about creating job objects.

CTL_FTPC_NAME = meaningful_entry_name

This statement might be useful with shell and Specific views. The entry name appears as a data file entry if the client issues DIR command.