Transfer CFT temporary files

Depending on the processing involved, Transfer CFT creates various temporary files in the /tmp directory. This topic describes temporary files, how to delete them, and provides an example.

Temporary files

Transfer CFT temporary files

There are four types of temporary files corresponding to different types of actions:

  • /tmp/cftlo* files are produced during the log switching procedure
  • /tmp/cftcn* files are produced when the accounting feature is enabled
  • /tmp/cftsu* files are produced when end of transfer procedures are run
  • /tmp/cftsu*.err files correspond to the results of commands in the cftsu* files

Deleting temporary files

Transfer CFT cannot delete temporary files automatically. It does not know exactly when the end of the user script is reached.

To avoid saturating the /tmp directory, you should end any shell procedure with the rm $0 command.

Note If this command is omitted, the /tmp partition rapidly becomes full and the end of transfer procedures will fail.

This command deletes the procedure that runs it and is applicable to cftlo*, cftfcn* and cftsu* files.

Additionally, the cftsu*.err files associated with cftsu* files should be deleted. However, to avoid losing any errors that may be logged in this file, it is best to check that the file is empty before deleting it.

For example, write:

if test -s $0.err
then
echo $0.err contains data to be consulted
else
rm $0.err
fi

TMPDIR environment variable

You can use the environment variable TMPDIR=<path> to define a temporary directory in Unix and POSIX. If you define TMPDIR, the temporary file goes in this directory. If you do not define TMPDIR, Transfer CFT uses the default directory (/tmp).

Example

export TMPDIR=/home/Desktop/tmpdir/

Sample procedure

The contents of the recvm.cmd file stored in <installdir>/runtime/conf/ are shown below. The recvm.cmd file is a sample procedure executed after receiving a message.

This procedure must first be declared in the CFTPARM section of your configuration file, in the EXECRM field, so that it can be executed.

Example:

 

     EXECRM = '/home/transfer/cft/<installdir>/runtime/conf//recvm.cmd'

The contents of the recv.cmd file are as follows:

echo "MESSAGE RECEIVED"     /* display of the message received */

echo "** &msg **"      /* by CFT using the &msg symbolic */

     /* variable that contains the */

     /* message text */

 

rm $0      /* deleting the /tmp/cftsu* */

     /* temporary file */

if test -s $0.err
then
echo $0.err contains data to be consulted
else
rm $0.err
fi

 

Transfer CFT identification

Some clients package Transfer CFT/UNIX to meet the special requirements of their company. This specific package can apply to both the product in its ready-to-install state, as delivered by Axway, and the product specifically preconfigured for the company.

To make it easier to identify this type of product, a specific directory is available on the delivery medium and product following installation. This directory is called .info (the dot must be included before the name).

This .info directory is located:

  • For the installable product, on the same level as the other product files to install
  • For the installed product, in the subdirectory in which Transfer CFT/V2/UNIX was generated, in the examples provided in this guide, this is the cft directory

This directory comprises a series of subdirectories ending with an empty file. These various levels provide the information below in the following order:

  • Transfer CFT release, cft240 for example
  • Product generation date, 20060307 for example
  • Operating system, AIX for example
  • Operating system release, for example, for AIX: 43
  • If necessary, the hardware manufacturer, for example, for AIX: IBM

Taking the examples above, the complete directory structure is as follows:

     .info/cft240/20060307/AIX/43/IBM

Note This directory and the information it contains are also used by Transfer CFT. As some utilities are very similar from one product release to another, the release information is retrieved to fine-tune the way in which the utilities behave.

Related Links