Manually create internal data files

The CFTFILE command is used to create, replace, or delete Transfer CFT files. These initial files define the most basic parameters for the Transfer CFT. You can further define the Transfer CFT settings after the initial startup, but the Transfer CFT must at least have this CFTFILE as a minimum configuration.

You can only create the initial environment in the CFTUTIL command line interface. You must create all files that are handled by the Transfer CFT. After creating a basic CFTFILE, you can execute the profile file, and continue either in command line.

About the CFTFILE command

The CFTFILE command affects the following files:

  • PARAMETER - containing the Transfer CFT general parameters where TYPE = PARM
  • PARTNER - containing the descriptions of the characteristics of partners where TYPE = PART
  • CATALOG - containing the control information associated with transfers where TYPE = CAT
  • STATISTICS - containing the information relative to terminated transfers where TYPE = ACCNT
  • LOG - used to record messages associated with the execution of transfers and CFT operations where TYPE = LOG
  • COMMUNICATION - used to enter transfer requests and Transfer CFT management comm, ands where TYPE = COM

To delete a Transfer CFT file, MODE = DELETE, you must declare the parameters FNAME, the name of the file to be deleted, and TYPE, the type of the file to be deleted.

OS Description

IBM i

The CFTFILE command is incorporated in Transfer CFT IBM i Manager. It can, however, be activated directly in the log file switching procedures. See the example supplied in the B_EXECLOG member.

You can use the CFTCATAL utility to resize the catalog. In a multi-node environment, this action resizes all nodes.

Use the CFTFILE command to create (MODE = CREATE) empty or delete (MODE = DELETE) Transfer CFT files.

Syntax

CFTFILE { PARM | PART }

TYPE = { PARM | PART }

FNAME = filename  

[ HABFNAME = filename ]

[ CIPHER = { NO | YES } ]

[ FBLKSIZE = { 0 |n } ]

[ FSPACE = n ]

[ FSPACEX = n ]

[ MAC = { NO | YES } ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE } ]

 

CFTFILE { CAT | COM }

TYPE = {  CAT | COM }

FNAME = filename

[ RECNB = n ]

[ CIPHER = { NO | YES } ]

[ FBLKSIZE = { 0 |n } ]

[ FSPACE = { 0 | n } ]

[ FSPACEX =  { 0 | n } ]

[ HABFNAME = filename ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE} ]

 

CFTFILE { ACCNT | LOG }

TYPE = { ACCNT | LOG }

FNAME = filename

[ FBLKSIZE = 0 | n ]

[ FSPACE = 0 |n ]

[ FSPACEX = 0 |n ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE } ]

Parameter Description

CIPHER 

File cipher request.

FBLKSIZE see table

Defines the block size of the file to be created (in bytes).

According to TYPE/OS

FNAME 

Name of the file the command applies to.

FSPACE see table

According to TYPE/OS

Primary allocation of the file to be created, expressed in K bytes (1024).

FSPACEX see table

Secondary allocation of the file to be created, expressed in K bytes (1024).

 

HABFNAME

Name of the security system initialization file.

LOCK

TYPE = COM

Name of the lock file created in parallel with the communication file and used to manage file access conflicts.

MAC

File authentication request.

 

MODE

Action requested on the file.

RECNB 

TYPE = {COM | CAT}

Number of records in the file.

TYPE = {ACCNT | CAT | COM | LOG | PARM | PART}

Type of file concerned by the command.

When TYPE = CAT, COM, PARM or PART, you can use the HABFNAME parameter for security.

Example

The following command creates a parameter file.

CFTFILE    TYPE = PARM,
MODE = CREATE,
FNAME = filename

Related Links