[FNAME = filename ]   string 64

Name of the statistical file. This name can be a:

  • physical name
  • logical name


[FNAME = filename ]    string 512

The name of the file where authorized or prohibited users are defined.

Enter the name of the file, up to 512 characters, in which you defined the list of model file identifiers.

The number of identifiers in this list is not limited. Build the file using the following rules:

  • a record of this file can only contain one idf
  • the size of the record is limited to 80 characters
  • an idf must start in the first column and only the first 8 characters of the record are taken into accound
  • characters after the 8th column are ignored
  • the identifier can be entered in upper or lower case
  • the file can contain records of zero length

You cannot complete this field if you have selected the idf button.


[FNAME = filename ]   string 64

Catalog file name. Service files, such as Catalog and Log. This name can be:

  • a physical filename
  • a logical name


[FNAME = filename ]   {string 64}


[FNAME = filename ]   {string 64}


[FNAME = filename ]   {string 64}


[FNAME = filename ]   {string 512}


[FNAME = filename]  {512 characters }

Name of the file in which the list of the identifiers of the various partners, each corresponding to one value of the ID parameter of a CFTPART object, is defined.

The number of identifiers in this list is not limited.

The existence of each partner is checked at the time of the transfer. If a partner is not defined, this does not prevent files being broadcast to or collected from the partners defined; only the partners not described are not served.

To build this file, the following rules must be followed:

  • A record of this file can only contain one partner identifier
  • The size of a record is limited to 80 characters
  • A partner identifier must begin in the first column and only the first 32 characters of the record are taken into account
  • Any characters after column 32 are ignored and considered to be a comment
  • An identifier may be entered in either upper case or lower case letters (it is converted into upper case letters)
  • The file may contain records of zero length

File example:

Example file names for distribution list

Transfer CFT does not check the transfer requester access rights for this file.

If FOR=COMMUT (broadcasting by a intermediate site):

The symbolic variable &SPART, network identifier of the sender partner, may be used in forming the name of the file (FNAME parameter value). This makes it possible to make a distinction between the lists defined for the various originating sites.

The following symbolic variables can be used:

  • &IDF, &PARM, &IDA
  • &NIDF


[FNAME = filename]    {1...512}

Name of the physical receiver file, filename or complete path name, of the directory.

When the parameter value is between quotes, it becomes case-sensitive.

In the receiver server configuration, the use of this parameter is mandatory.

In the receiver requester configuration, the filename may be defined in the RECV reception command or in the CFTRECV object. With the exception of the case of improvised transfers, the user should preferably opt for the second solution.

You can define the filename either in:

  • the receive command
  • or in the CFTRECV object (recommended method)

To receive...


a file

a complete physical file name

a version of a file

a file name with a root and a version number

a group of concatenated files

a directory name

Specific case using the complete filename

The complete path name includes the names of directories, or any other organization specific to the environment concerned, used to group files: library, catalog, PDSE, etc.

Depending on the environment concerned, the use of a complete "pathname" may lead to the implicit creation of all or part of a path structure.

A specific character, OS dependent, delimits the path to be created (intermediate directories). Only the names of the sub-directories appearing to the right of the delimiting character are created.

The filename may:

  • Be assigned dynamically using symbolic variables
  • Correspond to the name of a file with versions (GDG for instance)

Using symbolic variables

The following variables may be used to form the FNAME character string:

  • &IDF, &PARM, &IDA
  • &NIDF, &IDTU, &IDT
  • &NFVER

The ‘&’ character here replaces the char_symb character specific to each operating system. Refer to the Transfer CFT Operations Guide corresponding to your OS.


The &FUNIT, &FUNITC, &FPATH, &FROOT and &FSUF variables are used so that the FNAME parameter gives the full "path" pointing to the file to be written.

Specific case using &NFNAME symbolic variable    


The use of &NFNAME is only valid if the Transfer CFT is a receiver server.

This variable is only used in the open mode.

Receiving a file with versions          


This name includes a root and a version number.

The file is received as the temporary file defined in the WFNAME parameter and must concern the receiver file version + 1 (mandatory operation with RENAME).

The relative filename is converted into an absolute filename on completion of the transfer. The temporary file is then renamed with the name defined by FNAME.

Note When a temporary file is used, the WFNAME parameter, there may be restrictions related to the operating system. On IBM systems, for example, the type of unit must not appear in the name of the FNAME file.

PeSIT E CFT/CFT profile

Receiving a group of copied/concatenated files. This name must correspond to a directory name if a copy/concatenation operation is performed when the files are sent (transfer of a group of files between systems of the same type).

The data received is stored in the temporary file specified in the WFNAME  parameter. The files are then deconcatenated in the directory specified by FNAME.


[FNAME = {filename | mask | dirname | #filename | #mask | #dirname}]    {string 512}

Name of the local file, directory, indirection file, selection mask or selection directory to be sent. The maximum length of a filename value-type is 512 characters. This is only applicable for the name of transferred file, for example, FNAME parameter of SEND command.

This file name length is not applicable for service files.

When the parameter value is between quotes, it becomes case-sensitive.

The indirection file, selection mask or selection directory name is preceded by the <file-symb> character specific to each system. In most environments, the ’#’ character is used. Refer to the table of specific values in the Transfer CFT Operations Guide that corresponds to your OS.

In the sender server with implicit send operating mode, the use of the FNAME parameter is mandatory in CFTSEND.

In sender requester or sender server mode with a hold for sending request, the filename may be defined in the send transfer request (SEND command or CFTAPI call) rather than in the CFTSEND command.


[FNAME = filename]    {string 64}

Name of the log file.

Check that the file < filename> exists and is accessible; if not, information will be truncated on the CFTOUT standard output and will not be able to be used. This also applies when the current log file is the file defined by AFNAME.

Do not use logical names.


[FNAME = filename]   {string 512}

Name of the file containing the description of the translation table (1 record of 256 characters).

This file must have a sequential organization. Examples of such files are given with the various products. Refer to the Operations Guide specific to the system.

Return to Command index

Related Links