Transfer CFT procedures

When batch procedures (end of transfer, log switching, and so on) are triggered, a temporary command file and its execution report file are created. These procedures are submitted in batch mode in the batch queue defined by the CFT_QUEUE logical name.

These submits cause a temporary file to be created in the directory in which the CTMAIN JOB is running:

CFT_XXXXXX_HHMMSS.COM

Where:

  • XXXXXX = submitter's process ID in hexadecimal
  • HHMMSS = timestamp

This file is deleted following normal procedure execution. An execution report is created in the SYS$LOGIN directory, with a default name of CFT_XXXXXX_HHMMSS.LOG.

Defining the CFT_PRINT logical name with the required print queue value can print these reports.

You can also specify that VMS must delete the reports of correctly executed procedures by setting the CFT_LOGDEL logical name to YES.

The end of transfer procedures, CFTPARM command EXEC* parameters, and CFTSEND and CFTRECV commands EXEC parameter, are submitted from the transfer owner account and not Transfer CFT. Users can therefore submit their own end of transfer procedures.

The Transfer CFT must have the CMKRNL privilege to submit a JOB from the account of another user. The installation procedure provides the option of implementing this mechanism.

A logical name value is used to define Transfer CFT behavior. Therefore when Transfer CFT is installed or subsequently during processing, the product operations manager must modify the CFTLOGIN.COM file so that the CFT_SUBMIT logical name can be set.

The authorized values are as follows:

  • USER: The ends of transfer procedures are submitted from the transfer owner's account (command submitter in requester mode or USERID parameter value in server mode). Note that Transfer CFT must be able to obtain the CMKRNL privilege
  • CFT: the end of transfer procedures are submitted from Transfer CFT owner's account
  • Any other value is equivalent to CFT

Related Links