Default receive template - CFTRECV

This topic describes how to create and manage transfer templates for the CFTRECV object.

Related topics

Access the CFTRECV window

  1. Click to expand the Initial configuration folder in the left pane object manager.
  2. Right-click the Default receive template file object.
  3. Click List all Objects . The CFTRECV window is displayed in the right pane.
  4. The fields and components displayed in the CFTRECV window are schematically illustrated below. Complete the fields according to your system requirements. By default, certain fields may be set to Null.

Completing the General tab

The default CFTRECV object id is grayed and is not enabled for this object.

Complete the fields in the General tab as follows. When you have completed all of the CFTRECV tabs, click OK to confirm.

Field Description

comment

Enter a local free-text description for the receive transfer. You can enter up to 160 alphanumeric characters. The content of this field:

  • is not analyzed or used during transfers
  • is restored using the symbolic variable &COMMENT

delete

Specify the action to perform on the catalog entries in the "T" state (terminated). From the drop-down list, select one of the following:

  • NO (default value)
  • YES (automatic deletion)

If you select YES and you specify end-of-transfer procedures, catalog entries are only deleted after these procedures are executed.

If file store-and-forward is requested (via the Transfer CFT parameter setting), none of the catalog entries associated with terminated transfers is deleted.

exec

Specify the name of the file that describes the end-of-transfer procedure.

exit

Specify the CFTEXIT object used to activate a file type EXIT user task.

Enter the identifier of the CFTEXIT object. This identifier can include the symbolic variable &IDF.

fcheck

This parameter enables you to reject an incoming transfer if local file attributes don't match the virtual file attributes. Select one of the following:

  • NO (default value): Transfer CFT behavior is unchanged
  • YES: FLRECL and FRECFM attributes are compared with the virtual file record length and format. If they do not match, the transfer is rejected.

force

Specify the priority you want to set on the parameters defined in the CFTRECV object.

Select one of the following:

  • NO (default value):The parameters specified in the RECV command override the parameters in the corresponding CFTRECV object.
  • YES: The parameters specified in the CFTRECV object override the parameters in the corresponding RECV command.

ncomp

All protocols except PeSIT SIT

Use this field if the receiver requires online compression for the model file.

Authorized values and default values are the same as for the scomp field.

netband

The outgoing port range is controlled by the CFTNET object SRCPORTS parameter.

pri

Use this field to set the transfer request priority.

rkerror

Server mode only

From the drop-down list, select the action to be taken when a transfer fails during the selection phase:

  • “ ” (default value)
  • KEEP: the transfer remains in the catalog.
  • DELETE: the transfer is removed from the catalog.

If the parameter is omitted, the rkerror field in the CFTCAT object is used.

state

Specify the transfer state.

trk

Use this field to specify how much detail Transfer CFT provides Axway Sentinel about transfers. Transfer CFT sends detail about the transfers in the form of Tracked Instances.

From the drop-down list, select:

  • ALL: for each step of each transfer process, the monitor sends a tracked instance to Sentinel.
  • NO: the monitor never sends tracked instances to Sentinel.
  • SUMMARY: for both the initial step and the final step of each transfer process, the monitor sends a tracked instance to Sentinel.
  • UNDEFINED (default value): the tracking options are defined in the trk field.

xlate

Enter the translation table identifier that you define in the Name field of the CFTXLATE object.

To use a translation table other than the one attached to the model file, specify it in the RECV command ( xlate parameter).

Completing the Local file tab

Complete the fields in the Local file tab as follows.

Field Description

fname

Use this field when receiving a:

  • file or a version of a file
  • group of files

In receiver/responder mode, the fname parameter is mandatory.

In receiver/initiator mode, you can define the filename either in:

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

To receive...

Enter...

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

fcode

From the drop-down list, select the file data code to use:

  • ASCII
  • BINARY
  • EBCDIC

The default value does not depend on the file type received from the network. For all PeSIT profiles (except PeSIT SIT), if the code of the data received from the network is BINARY, FCODE= BINARY. Otherwise, the data code used is the native code of the receiver system.

About translation on reception

The translation performed on reception depends on the:

  • local code (explicit or implicit value of this field)
  • network code (code of the data received from the network)
  • presence of an external translation table if needed. This translation table is taken into account if:
  • it corresponds to the local data code (fcode of the CFTXLATE object) and the network data code
  • the xlate field of the CFTRECV references an existing CFTXLATE object or the default id of the CFTPARM object

The code of the data received is not detected by examining the data. This code is:

  • either explicitly communicated by the sender (see the ncode field of the CFTSEND object, for PeSIT CFT to CFT)
  • or deduced from the protocol rules.

On each receive transfer:

  • If the data received and/or the local data code are BINARY, no translation is performed.
  • If the data received and the local data are assumed to be encoded in ASCII or EBCDIC:
  • if the data received and the local data have the same code (ASCII/ASCII or EBCDIC/EBCDIC), translation can only be performed via an external translation table.
  • if not, translation is always performed either via an external translation table or via the Transfer CFT internal translation table.

fkeylen

PeSIT E only

Enter the key length (in bytes) of the indexed file.

The default value is:

  • the value received in PI 38 if defined by the initiator
  • 0 otherwise

The monitor receives sequential records. You can create a file type EXIT or an end-of-transfer procedure to use this information which can be recovered by the symbolic variable &FKEYLEN.

fkeypos

PeSIT E only

Enter the key position (in bytes) of the indexed file.

The default value is:

  • the value received in PI 39 if defined by the initiator
  • 0 otherwise

The monitor receives sequential records. You can use the key position in a file type EXIT or an end-of-transfer procedure. Use the symbolic variable &FKEYPOS to retrieve the key position.

frecl

Enter the file record length in bytes (up to 32 characters). If:

  • FRECFM = F , enter the length of the records of the receiver file.
  • FRECFM= V or FRECFM= U, enter the maximum length of the records.

Some operating systems generate implicit record lengths when they are not supplied by the sender or by the local parameters:

  • Windows: 512
  • UNIX text files: 512
  • UNIX binary files: 4096

When a file is received, if a record is in fixed format and the size of the record to be sent is less than the length defined, it is padded with:

  • binary zeros (X'00') if FCODE= BINARY
  • spaces (X'20 or X'40') if FCODE= ASCII or FCODE= EBCDIC

forg

Specify the file organization. Select one of the following:

  • SEQ (default value): sequential
  • INDEXED: indexed
  • DIRECT: relative (direct access)

On some operating systems, you can send indexed and relative files as sequential files. Depending on the operating system, you may have to complete the fields ftype, fkeylen, fkeypos.

frecfm

Enter the file record format:

  • F: fixed length
  • V: variable length
  • U: undefined length

The value that you enter depends on the operating system.

UNIX: You can receive a variable format file. But since it contains control information, an application cannot directly interpret the file. Unless otherwise specified, for the store-and-forward for example, FRECFM=V is not used.

fspace

Enter the size of the file (in Kbytes).

This size usually corresponds to the primary allocation. Transfer CFT automatically retrieves the size of the file before each transfer.

UNIX: This field is not supported.

wfname

Use this field when additional processing is required, that is, when receiving:

  • a version of a file (MVS only)
  • a group of concatenated files (PESIT E CFT/CFT only)

Enter a unique name for the temporary file. This temporary file is used to ensure the integrity of the received file. It is renamed at the end of the transfer using the name defined by the fname field. It then becomes available to the user application.

This name can include the following symbolic variables:

  • &FDATE, &FTIME, &FYEAR, &FMONTH, &FDAY
  • &SPART, &RPART, &PART, &NPART, &GROUP
  • &SUSER, &RUSER
  • &SAPPL, &RAPPL
  • &IDF, &PARM, &IDA
  • &NIDF, &NFNAME, &IDT
  • &BDATE, &BTIME, &BYEAR, &BMONTH, &BDAY

You can also use this field for store-and-forward purposes (see ID= COMMUT field).

This field is mandatory:

  • when a copy/concatenation operation is performed during the send (transfer of a group of files in PeSIT CFT/CFT mode).
  • in MVS, if the receiver file is a version file, in particular for operation in open mode and when the sender sends an nfname that corresponds to a GDG name.

dirnb

MVS only

Enter the number of directory blocks used to create a directory.

faction

From the drop-down list, select the action to perform on the file before a receive transfer.

If a receiver file of the same name already exists, the monitor performs one of the following actions:

  • ERASE: it resets the file
  • DELETE: it deletes the file
  • VERIFY (default value): it checks that the file is empty

MVS: For VSAM files, only ERASE is accepted.

VMF: CONCAT is also an option, allowing concatenation of files.

fdisp

From the drop-down list, select the action of the monitor on the file:

  • NEW: if the file already exists, the transfer is refused.
  • OLD: the file must already exist.
  • BOTH (default value): if the file does not exist, it is created.

maction

From the drop-down list, select the action of the monitor on the files transferred by COPY:

  • “ ”: if the files already exist in the reception directory, the copy of these files is ignored.
  • REPLACE: if the files already exist in the directory, they are replaced.

Completing the Scheduling tab

Complete the fields in the Scheduling tab as follows.

Field Description

cycdate

Use the cycdate parameter to define a cyclic transfer request. Specify the last day to activate the cycle of delayed transfers.

If the interval is expressed in:

  • days or months (TCYCLE = DAY or TCYCLE = MONTH), the default value is: CYCDATE = MINDATE + TCYCLE * CYCLE
  • minutes (TCYCLE = MIN), the default value is: CYCDATE = MINDATE

cyctime

Use the cyctime parameter to define  a cyclic transfer request.

The period between two transfer activations is defined by the cycle and tcycle parameters in the CFTSEND object. This period can be expressed in minutes, days or months.

The validity time slot for this request is defined by the mindate / mintime and maxdate / maxtime parameters and corresponds to the global time during which the transfers are periodically repeated.

Enter the initial activation time for the cycle of delayed transfers.

If the interval is expressed in:

  • days or months ( tcycle = day or tycycle = month), the default value is cyctime = mintime.
  • minutes (tycycle = min), the default value is cyctime = mintime + tcycle * cycle.

maxdate

Initiator mode only

To define a time slot for activating delayed transfers, specify the last day of the partner time slot. See also Delayed transfers .

You can specify the date:

  • explicitly (absolute date)
  • relative to the date the command is taken into account. This value is then expressed as a number of days.

The default value is assigned by the monitor depending on the transfer context. If MAXTIME is:

  • greater than MINTIME, MAXDATE = MINDATE
  • less than MINTIME, MAXDATE = MINDATE+1
  • omitted, MAXDATE = 99991231

maxtime

Initiator mode only

Use this field to define a time slot for activating delayed transfers. Enter the maximum time for the last day (maxdate field) of the partner time slot.

You can specify the time:

  • explicitly (absolute time): default value is 23595999
  • relative to the time the command is taken into account: the corresponding absolute time must be less than 24 hours. The value is expressed in minutes.

The maxtime must not be equal to mintime except if maxdate is defined and is not the current date.

mindate

Initiator mode only

Use this field to define a time slot for activating delayed transfers. Enter the first day of the partner time slot.

You can specify the date:

  • explicitly (absolute date): the default value is the current date
  • relative to the time the command is taken into account: the corresponding absolute time must be less than 24 hours. The value is expressed in minutes.

mintime

Initiator mode only

Use this field to define a time slot for activating delayed transfers. Enter the minimum time for the first day (mindate field) of the partner time slot.

You can specify the time:

  • explicitly (absolute time): the default value is 0000000
  • relative to the time the command is taken into account: the corresponding absolute time must be less than 24 hours. The value is expressed in minutes.

The mintime must not be equal to maxtime unless maxdate is defined and is not the current date.

Completing the Identification tab

This topic describes the Identification tab. Complete the fields in the Identification tab as follows.

Field Description

userid

Responder/receiver only

Enter the identifier of the transfer owner (up to 15 characters) associated with the CFTRECV object.

If you do not enter a value in this field, the default value is the system userid of the responder Transfer CFT.

This field can include one or more of the following symbolic variables:

  • &PART: value substituted by the local identifier of the transfer partner (CFTPART ID)
  • &SUSER: value substituted by the SUSER parameter sent between two Transfer CFTs (PeSIT D CFT profile and PeSIT E protocols)
  • &RUSER: value substituted by the ruser parameter sent between two Transfer CFTs (PeSIT D CFT profile and PeSIT E protocols)

Transfer CFT can use domain\user accounts instead of USER, except when using PassPort AM or internal security. To do so, set the USERID value to the format DOMAIN\USER.

groupid

Enter a group identifier for the user of up to 15 alphanumeric characters. The value you enter depends on the operating system.

ruser

PeSIT only

Enter the user identifier of the file receiver.

Enter one of the following:

  • an eight-character string for PeSIT D CFT, PeSIT E
  • a 28-character string for PeSIT E CFT/CFT

Otherwise, the same rules apply as for the parameter rappl.

suser

PeSIT only

Enter the user identifier of the file sender. Enter one of the following:

  • an eight-character string for PeSIT D CFT, PeSIT E
  • a 28-character string for PeSIT E CFT/CFT

Otherwise, the same rules apply as for the parameter rappl , except that in PeSIT E, this value is transported in the PI 03.

Related Links