Default send template - CFTSEND

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

Related topics

Access the CFTSEND window

  1. Click to expand the Initial configuration folder in the left pane object manager.
  2. Right click the Default send template file object.
  3. Click Edit the Object . The CFTSEND window is displayed in the right pane.
  4. The fields and components displayed in the CFTSEND tabs are schematically illustrated in the following tables. Complete the fields according to your system requirements, and click OK to close the window.

Completing the CFTSEND General tab

The default CFTSEND id is displayed when Implicit is set to No. When the default id is grayed, you cannot modify it.

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

Field Description

comment

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

  • is not analyzed or used during transfers
  • can be queried locally using the command LISTCAT CONTENT=FULL
  • is restored using the symbolic variable &COMMENT

delete

Automatically deletes catalog entries that are completed (in the T state).

exec

Enter the name of the file that describes the end-of-transfer procedure to execute on completion of the transfer.

If you do not enter a value in this field, the execsf field of the CFTPARM object is taken into account.

 

execsub

Submits end of procedure when sending a group of files.

exit

Enter the identifier of the CFTEXIT object used to activate a file type EXIT user task.

This identifier can include the symbolic variable &IDF.

force

Specify the priority for the parameters defined in the CFTSEND object.

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.

fspace

Enter the size of the file (in K-bytes).

You do not usually need to complete this field since Transfer CFT automatically retrieves the size of the file before each transfer. Check in the "Operations Guide" that the operating system supports this feature.

impl

Responder mode only

Use this field to send any authorized file without requiring a send command with hold.

From the drop-down list, select one of the following values:

  • NO (default value which is always set to NO for Default CFTSEND)
  • YES

If you set this field to YES and are in sender mode, CFT automatically generates a send request on condition that no SEND command ( STATE= HOLD) is specified in the catalog. The file becomes permanently available.

Note: Set this parameter to NO in the description of the default model file.

netband

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

notify

Destination of messages associated with the send transfer selected from the log file message.

opermsg

Categories of transfer information messages.

parm

PeSIT D CFT profile, PeSIT E CFT/CFT, PeSIT E

Enter a user free-text (80 characters) that is sent to the receiver.

The value of this parameter can be accessed through the symbolic variable &PARM in the end-of-transfer procedure.

pri

Use this field to set the selection priority.

state

From the drop-down list, select one of the following transfer states:

  • D (default value): The request is saved in the “D” state (at disposal) in the catalog. This state corresponds to an immediate transfer. That is, a transfer which is executed as soon as possible, depending on the time slot, parallel transfer constraints, and so on.
  • H: The request is saved in the “H” state in the catalog. This state corresponds to a deferred transfer. The transfer is executed later:
  • K: The request is saved in the “K” state in the catalog. This state corresponds to a deferred transfer: the transfer can only be executed later after a local START command changes this transfer to the available state ("D").

trk

Use this field to specify how much detail Transfer CFT provides 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 identifier of the translation table defined by the CFTXLATE object.

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

Completing the Local file tab

Complete the fields in the Local File tab starting with the physical location of the file.

Field Description

faction

From the drop-down list, select the action to perform on the file after a send transfer:

  • ERASE
  • DELETE
  • NONE (default value)

Caution: This parameter is ignored if set to DELETE for a directory or file group send. No directories or files are deleted after a generic transfer.

fcode

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

  • ASCII
  • BINARY
  • EBCDIC

The default value is determined by the characteristics of each transfer and depends on the type of the file sent ( ftype in the OS-specific tabs).

The sender’s automatic detection of the ftype partly takes the place of automatic code detection.

fdisp

From the drop-down list, select the file sharing option:

  • SHARE: shared access
  • OLD: exclusive access

fkeylen

PeSIT E only

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

The monitor sends this information in the PI 38, but does not use it. The indexed file is processed as if it were a sequential file.

fkeypos

PeSIT E only

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

The monitor sends this information in the PI 39, but does not use it. The indexed file is processed as if it were a sequential file.

flrecl

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

By default, NRECFM= FRECFM . 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 to be sent

Make sure that your system supports this facility by checking the specific Operations Guide.

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

fname

Use this field to identify the type of file transfer. Specify whether you are sending:

  • a file
  • a version of a file
  • a list a local directory
  • a group of files from a list defined in a file
  • a group of files selected just before sending
  • all the files in a directory

In sender responder mode with implicit send operating mode ( IMPL= YES), the fname parameter is mandatory.

In sender initiator or sender responder mode with a hold for sending request, you can specify the filename in the send transfer request (SEND object or CFTAPI call) rather than in the CFTSEND object.

To send... Enter...

a file

a complete physical file name

a version of a file

a file name with a root and a version number

a list of all the files in a local directory

a directory name

a list of files selected in a local directory

a generic file name

a group of files from a list defined in a file

the file name

a group of files selected just before sending

a generic file name

all the files in a directory

enter the directory name

forg

Specify the file organization. Enter 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.

fspace

Enter the size of the file (in K-bytes).

You do not usually need to complete this field since Transfer CFT automatically retrieves the size of the file before each transfer. Check in the "Operations Guide" that the operating system supports this feature.

selfname

Name of the file that contains the list of files selected for sending.

wfname

Homogeneous systems and PeSIT protocol only

Use this field when sending a group of files. The files are copied and concatenated into this temporary file and sent. [FOR DETAILS: fname] Once sent as a sequential file, it is deleted.

Enter a unique name for the temporary file.

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

For additional information on the file and its structure:

Completing the Protocol file tab

Complete the fields pertaining to the Protocol file characteristics.

Field Description

nblksize

Use this field to define the block size of the file. Make sure that the partner supports the block size concept.

Enter one of the following values:

  • the value of fblksize (see the MVS-specific tab)
  • any other value from 0 to 65535

ncomp

All protocols except PESIT SIT

Use this field if the sender requires online compression.

Authorized values and default values are the same as for the scomp field. Complete this field in ODETTE, to inhibit compression when, after negotiation, the scomp field set to 1.

 

ncode

All PeSIT profiles except SIT

Use this field to specify the network data code to use for send transfers.

From the drop-down list, select one of the following values:

  • ASCII
  • BINARY
  • EBCDIC

Although there is no default value for this field, for each transfer it can implicitly take one of the following values:

  • BINARY if FCODE= BINARY
  • ASCII or EBCDIC, depending on the partner computer code deduced from the syst field

About translation during a send transfer

The fields ncode, fcode, and xlate specify the type of translation performed during a send transfer and whether the values are determined explicitly or implicitly:

  • If FCODE= BINARY or NCODE= BINARY, no translation is performed.
  • If FCODE and NCODE are assumed to be coded in ASCII or EBCDIC:
  • if NCODE= FCODE, ASCII/ASCII or EBCDIC/EBCDIC translation can only be performed with an external translation table (see the use of the xlate field).
  • if not, ASCII/EBCDIC or EBCDIC/ASCII translation is always performed, either via an external translation table or via the Transfer CFT internal translation table.

nfname

PeSIT D CFT profile, PeSIT E CFT/CFT profile

Use this field when sending:

  • a file
  • a version of a file

Specify the name of the physical file sent to the receiver partner. It can be a:

  • complete physical filename
  • filename preceded by an asterisk ( *filename) - The receiver can choose whether or not to use the name of the transmitted file.
  • filename with a version number ( filename(+1)) MVS only)

The file is transferred on condition that:

  • The receiver partner authorizes the sender site (initiator or responder) to set the physical name of the file to be received (this name is defined from parameter settings such as FNAME= &NFNAME)
  • The file designated by nfname exists, or can be created at the receiver end
  • The version number of the GDG file corresponds to the version number of the receiver file + 1

MVS

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
  • &BDATE, &BTIME, &BYEAR, &BMONTH, &BDAY

nkeylen

PeSIT E only

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

By default, NKEYLEN= FKEYLEN.

The monitor sends this information in the PI 38, but does not use it. The indexed file is processed as if it were a sequential file.

nkeypos

Available in PeSIT E only

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

By default, NKEYPOS= FKEYPOS.

The monitor sends this information in the PI 39, but does not use it. The indexed file is processed as if it were a sequential file.

nlrecl

Use this field to enter the network record length in bytes.

Enter one of the following values:

  • If FRECFM= F, enter the length of the records of the receiver file
  • If FREFM= V, enter the maximum length of the records
  • By default, NLRECL= FLRECL

Make sure that your system supports this facility by checking the specific Operations Guide.

When a file is sent, if a record is:

  • larger than the length defined, it is truncated.
  • 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

nrecfm

Enter the file record format to use on the network:

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

By default, NRECFM= FRECFM.

PeSIT

In PeSIT SIT and PeSIT EXTERN, if an undefined length ( U ) is entered, the monitor changes it to a variable length ( V )

nspace

ODETTE and PeSIT only

Use this field to define the size of the file to send on the network.

Enter:

  • the value entered for fspace (default value)
  • any other value in K-bytes

ntype

ODETTE, PeSIT D CFT, PeSIT E CFT/CFT only

Use this field to define the type of the network file. In some client/server configurations, the local file can be physically located on a different computer from the one on which Transfer CFT is run. The value that you enter depends on the operating system.

PeSIT D CFT profile, PeSIT E CFT/CFT If you do not complete this field, the Transfer CFT monitor assigns a default value depending on the local file type (see ftype field in the OS-specific tabs) and the operating system of the partner.

ODETTE Set this field to T to request the sending of a file in text format. If you set this value to T, the nrecfm and nlrecl parameters are ignored.

  • The format of a file (corresponding to nrecfm) is imposed for Odette text files.
  • The maximum length of records (corresponding to nlrecl), is set to 2048 bytes.

Completing the Scheduling tab

Select times in the time frame fields displayed in the Scheduling tab.

Field Description

cycdate

Specify the last day you can activate the cycle of delayed transfers in a cyclic transfer request.

cycle

Use this field to define the transfer activation cycle. Enter the period of time to wait before activating the next transfer. This period can be expressed in minutes, days or months as defined in the tcycle field.

cyctime

Use this field with cycdate to specify the validity period of a cyclic transfer request. In cyctime, you specify the first time of activation for the cycle of delayed transfers.

maxdate

Initiator mode only

You can define a time slot for activating delayed transfers. Use the maxdate, maxtime, mindate and mintime (described next) to specify the validity period. In maxdate, you specify the last day of the partner time slot.

maxtime

Initiator mode only

Use this field with maxdate (described above), mindate and mintime (described next) to specify the validity period for activating delayed transfers. In maxtime, you specify the maximum time for the last day ( maxdate field) of the partner time slot.

mindate

Initiator mode only

Use this field with maxdate, maxtime (described above) and mintime (described next) to specify the validity period for activating delayed transfers. In mindate, you specify the first day of the partner time slot.

mintime

Initiator mode only

Use this field with maxdate, maxtime, mintime (described above) to specify the validity period for activating delayed transfers. In mintime, you specify the minimum time for the first day ( mindate field) of the partner time slot.

tcycle

From the drop-down list, select how to express the transfer activation cycle.

  • DAY (default value): day
  • MIN: minute
  • MONTH: month

Completing the Identification tab

Complete the Identification tab as follows.

Field Contents

userid

Sender/responder mode only

Use this field to define the transfer owner associated with an implicit send ( IMPL= YES).

Enter a transfer owner identifier of up to 15 characters.

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
  • &SUSER: value substituted by the suser parameter sent between two Transfer CFT monitors (PeSIT D CFT profile and PeSIT E protocols)
  • &RUSER: value substituted by the ruser parameter sent between two Transfer CFT monitors (PeSIT D CFT profile and PeSIT E protocols)

Windows only

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. The value you enter depends on the operating system.

rappl

PeSIT only

Enter the identifier of the file receiver application.

ruser

PeSIT only

Enter the user identifier of the file receiver.

sappl

PeSIT only

Enter the identifier of the file sender application.

suser

PeSIT only

Enter the user identifier of the file sender.

spart

Enter an eight-character string to specify the network designation by which the local Transfer CFT monitor identifies itself to its partner.

If the login field  associated with SEND is not defined, the spart value is taken into account.

Related Links