SUBMIT - Submitting a processing procedure

This topic describes the SUBMIT command, which is used to submit a processing procedure for a selected transfer.

The procedure inherits the transfer context symbolic variables.

You can start, or restart, this procedure when the file or message transfer is in the T phasestep.

This command has no effect on the transfers belonging to a broadcasting list even if these transfers are in the T phasestep. Alternatively, it can be applied to a generic transfer, whose PART parameter equals the broadcasting list identifier, when it is in the T phasestep.

Description

Use this command to submit a processing procedure for each selected transfer.

Parameters

BLKNUM 

Catalog block number. If the values '*' or ' ' are used then all transfers are selected regardless of the block that they belong to.

DIRECT

Transfer direction for the requests in question.

Possible values are:

  • BOTH: (default) takes both send transfers and receive transfers into account
  • RECV: limits the action to receive transfers
  • SEND: limits the action to send transfers

EXEC 

Name of the file containing the procedure to be executed.

By default, this name is the one defined by the parameters:

  • EXEC of the SEND/RECV command (according to the transfer direction),
  • or (if this parameter is not defined) EXECSF or EXECRF of CFTPARM (according to the transfer direction).

The symbolic variables inherit the values of the context of each transfer selected.

These variables may consequently used, as in the case of the previously indicated EXEC* parameters:

  • to form the name of the file containing the procedure to be executed.
    The list of symbolic variables which can be used is the same as the one indicated for the corresponding EXEC* parameter.
  • in the processing of the procedure to be executed.
    The list of symbolic variables is indicated in Symbolic variables .

IDA 

Local identifier of the transfer assigned by the user or user application.

Several catalog entries may be associated with a given IDA. There is no default value.

IDF 

Model file identifier.

Several catalog entries may be associated with a given IDF. There is no default value.

IDT 

Transfer identifier.

This identifies a transfer for a given partner. The value ‘ *’ means that no selection is required using the IDT parameter (default value).

IDTU 

Transfer local counter identifier.

PART 

(Mandatory)

Partner identifier.

The value of this parameter can be:

  • Identifier: the command only concerns the transfers with this partner
  • Mask: the command concerns the transfers with the partners, whose identifiers correspond to this mask

Example 1 - Single Transfer

SUBMIT

IDT = A1020301,

 

 

IDF = file1,

 

 

IDA = appli1,

 

 

DIRECT = SEND,

 

 

EXEC = myprog

 

The procedure defined in the file "myprog" is submitted.

This procedure inherits the values of the parameters of the transfer selected by the SUBMIT command. This provides the possibility of substituting the symbolic variables which may have been used in the procedure submitted.

Example 2 - Broadcast list

CFTDEST

IDT = list,

 

 

PART = (part1, part2, part3)

 

CFTPART

ID = part1, .....

 

CFTPART

ID = part2, .....

 

CFTPART

ID = part3, .....

 

CFTSEND

PART = list,

 

 

IDF = myfile,

 

 

EXEC = myprog

 

The procedure myprog is executed ONCE when all the transfers are completed.

Before the post-processing procedure is executed, the catalog looks like this.

STATE 

PART 

IDF 

SFT 

LIST 

MYFILE (generic transfer) 

SFT 

PART1 

MYFILE 

SFT 

PART2 

MYFILE 

SFT 

PART3 

MYFILE 

The post-processing procedure can be submitted again as follows:

SUBMIT

PART = list,

 

 

IDF = myfile,

 

This relates to the generic transfer. A SUBMIT command applied to a transfer in the list (SUBMIT PART = PART1 for example) has no effect.

Related Links