CFTPROT - Transfer protocols

The following table lists the parameters which are common to all protocols.The CFTPROT TYPE = xxx commands are explained in the tables following the general parameters.

For network resources of the asynchronous type (not SAP), there cannot be more than one CFTPROT object per CFTNET object.

Related topics

Description

CFTPROT: Use this command to define network parameter settings.

Parameters

DISCTD

Wait time-out (in seconds) before disconnection, in the absence of a new transfer request to the partner, in requester mode.

The session established for a transfer remains active for DISCTD seconds after the completion of this transfer.

If the value is 0, the wait time-out is infinite.

DISCTS

see table

Wait time-out (in seconds) before disconnection, in the absence of a new transfer request from the partner, in server mode.

The session established for a transfer remains active for DISCTS seconds after the completion of this transfer. If at the end of this time-out, no new transfer has been received, the connection is freed by the ABORT FPDU.

DYNAM

Dynamic partner identifier (8 characters) in server mode.

EXIT 

Identifier describing the directory EXIT.

The value of this identifier corresponds to the CFTEXIT ID parameter.

The identifier may contain the &NPART symbolic variable.

EXITA 

Identifier describing the directory EXIT.

The value of this identifier corresponds to the value of the CFTEXIT ID parameter.

The identifier may contain the &NPART symbolic variable.

ID 

CFTPROT command identifier.

This name must be referenced in the values taken by the CFTPARM PROT parameter.

IDF 

Used to assign an IDF to a file on receiving an NIDF.

This parameter can be used in:

  • server mode (sender or receiver)
  • receiver requester following the activation of a RECV IDF=<mask> command
NACK

PeSIT

Enables or disables the negative acknowledgement feature.

NET

Identifier referring to a CFTNET command associated with this protocol.

RCOMP

Maximum compression authorized on receiving a file.

This compression is negotiated between the sender and the receiver.

A zero value corresponds to no compression.

For further information such as usable values etc., refer to Compression.

RESTART

Maximum number of transfer restart attempts.

An attempt is taken into account as soon as the physical connection with the remote site is correctly established.

RTO 

Network monitoring time-out (expressed in seconds) excluding the protocol connection/disconnection/break phase.

Corresponds to the wait time-out of a reply to an FPDU before disconnection (READ TIME OUT).

If the value is 0, the wait time-out is infinite.

SAP 

Name of the local SAP, Service Access Point, associated with this protocol.

Used to identify the "access point" at which incoming connection requests for this communication protocol are placed.

The SAP supplied by a requester partner when making its connection request is retrieved by the local Transfer CFT which uses it to deduce the protocol to be used. Each CFTPROT object in a given resource class must include its specific SAP.

The value of this parameter may be expressed in hexadecimal form. In this case, the first character must be "#" (number sign) (for example: #31 is understood as the ASCII character ‘1’).

SCOMP 

Maximum authorized compression for sending a file.

This compression is negotiated between the sender and the receiver.

A zero value corresponds to no compression.

SRIN 

Controls the direction of transfers authorized for the Transfer CFT when it is server, accepter of the protocol connection.

SROUT

Controls the direction of transfers authorized for the Transfer CFT when it is requester (initiator of the protocol connection).

TYPE 

Type of file transfer protocol.

Defining ODETTE (OFTP)

The CFTPROT TYPE = ODETTE command is used to describe the OFTP (ODETTE) transfer protocol.

This command is used to specify the values on which the Transfer CFT is based during protocol negotiations concerning:

  • Credit
  • Data compression
  • Special logic

The "Credit" value designates the maximum number of data packets which the sender can send, before the server needs to acknowledge their receipt by assigning a new "Credit". Transfer CFT simulates the taking of a synchronization point at each credit message sent or received.

If a transfer is interrupted, the restart point proposed by a sender Transfer CFT corresponds to the point the send transfer was interrupted, as detected by the sender. The restart point negotiated by a receiver Transfer CFT always corresponds to a credit message it previously sent (except when restarting from the beginning of the file).

The OFTP (ODETTE) section of the Protocols book contains a detailed explanation of the constraints and specifics regarding the use of this particular protocol.

Description

Use this command to describe the ODETTE transfer protocol.

Parameters

EERP

Used to interpret the value of the ORIGINATOR and DESTINATOR fields contained in the EERP message, according to the protocol version.

The End to End ResPonse service generates a message called EERP. This message informs the file sender that the data sent arrived correctly.

The first version of the protocol (1986) specifies that:

  • the ORIGINATOR protocol field corresponds to the file sender
  • the DESTINATOR protocol field corresponds to the file receiver

The second version (1991) specifies that:

  • the ORIGINATOR protocol field corresponds to the EERP sender (i.e. the file receiver)
  • the DESTINATOR protocol field corresponds to the EERP receiver (i.e. the file sender)

Note: heck the consistency of the customized values from one end to another. If the sender and receiver have different versions, it is not possible to acknowledge the transfer.

PAD 

Option applying "SPECIAL LOGIC" to the data exchange buffers.

This option is negotiated with the partner when the protocol session is established (in the SSID FPDU). Iif the option is set to NO for one of the partners, the "special logic" is not applied.

RCREDIT 

Value of the "credit" (expressed as a number of "DATA" messages) proposed by Transfer CFT when it is server.

This value is negotiated with the value proposed by the requester (see the SCREDIT parameter) when the protocol session is established.

RESYNC 

Option for restarting a transfer following an interruption.

This option is negotiated with the partner when the connection is established: if the option is set to NO for one of the partners, transfer restarts are not managed.

RRUSIZE

Maximum size of NSDUs (Network Service Data Unit) being received.

This parameter is negotiated with the partner (SRUSIZE parameter if Transfer CFT), the smallest value is selected as the size of NSDUs sent.

Refer to the Transfer CFT Protocol topics to optimize the definition of the value of this parameter.

SCREDIT

Value of the "credit" (expressed as a number of "DATA" messages) proposed by Transfer CFT when it is the requester.

Transfer CFT is authorized to send a number of "DATA" protocol messages equal to the result of the negotiation (performed when the protocol session is established), before waiting for a new "credit" to be sent by the server.

SRUSIZE

Maximum size of NSDUs (Network Service Data Unit) being sent.

This parameter is negotiated with the partner (RRUSIZE parameter if Transfer CFT), the smallest value being selected as the size of NSDUs sent.

Refer to the   Protocol topics to optimize the definition of the value of this parameter.

MVS connection, the maximum value of SRUSIZE is equal to the value configured in the NCP (or the equivalent) less (-) 6 bytes.

TCP 

Processing method used for protocol messages:

  • Transfer CFT: activation of the method specific to Transfer CFT
  • OFTP: activation of the standard method (RFC 2204)

This parameter applies in both initiator and responder modes. 

Defining PeSIT

The CFTPROT TYPE = PESIT command is used to describe the PeSIT transfer protocol.

In PeSIT, the user can specify parameters controlling the:

  • mechanisms associated with the synchronization points
  • format of messages
  • compression algorithms
  • CRC calculation
Note In certain environments, the mechanisms for repositioning in the transferred files are not operational with all the files supported: after a transfer interruption, transfers then begin again from the start of files (see the Transfer CFT Operations Guide specific to your OS).

The four PeSIT variants supported correspond to the four values of the PROF parameter (CFT, SIT, EXTERN, ANY). Some parameters are only meaningful for one or more of these variants. For clarity, these specific parameters are grouped below according to the corresponding value(s) of the PROF parameter.

For a detailed explanation of the constraints and specifics regarding the use of each of these variants, refer to the Transfer CFT Protocols.

Description

Use this command to describe the PeSIT transfer protocol.

Parameters

CONCAT

Only in sender mode

Option to concatenate FPDUs (File Protocol Data Units) in a given NSDU.

This option is not negotiated.

CTO 

Minimum duration (in minutes) of the session, Cycle Time Out.

At the end of a transfer, the wait time-out for a nfew transfer is recalculated depending on:

  • the time (hour) for opening the session
  • the current time
  • the wait delay before disconnection (DISCTS for the protocol)
  • the duration of the session (CTO)

The session is liberated if no transfer was initiated by the remote partner during the indicated duration.

CYCLE 

Periodicity (in minutes) for creation of a protocol session:

  • 0: PeSIT session open on startup
  • n: periodicity

DISCTC 

Wait time-out (in seconds) for the reply FPDU (ACONNECT), after the sending of a CONNECT FPDU.

If the value is 0, the wait time-out is infinite.

DISCTR 

Network disconnection wait time-out. Wait time-out (in seconds) for the partner site to cut the connection, after sending an "abort" request (ABORT FPDU).

If the value is 0, the wait time-out is infinite.

HIDE99

Optional parameter available only to PESIT protocol definition (TYPE=PESIT) using the ANY profile (PROFIL=ANY/CFT).

  • NO (Default value): no information inside PI99 (free message PI Code) is hidden
  • YES: hide private information carried by the protocol (physical local path of the file)

LOGON

Only in requester mode PeSIT E

Implementation of the pre-connection phase.

According to the value of this parameter:

  • YES: this phase is implemented. The requester sends a 24-byte EBCDIC message as follows:
    • byte 1 to 8: ‘PESIT ’ (PeSIT followed by 3 blank characters) (corresponding to the protocol used)
    • byte 9 to 16: requester identifier (NSPART of CFTPART)
    • byte 17 to 24: requester password (NSPASSW of CFTPART)
  • NO: this phase is not implemented: the requester does not send a message

Note: The Transfer CFT server automatically adapts itself to the choice of the requesting partner to send a Logon message or not.

MULTART

Only in sender mode

Option to group several records of the file sent in a given FPDU (multi-record FPDUs).

  • in sender mode, MULTART = YES is recommended if the partner supports multi-record FPDUs

The value MULTART = YES is PROHIBITED in this profile

  • in receiver mode, the Transfer CFT accepts multi-record FPDUs, regardless of the value of this parameter

PAD 

Only in requester mode CFT profile

Use of the CRC (Cyclic Redundancy Checksum).

This option is not negotiated: in server mode, Transfer CFT always adapts itself to the choice of the requesting partner.

The PAD = YES option is mandatory for an access through a PAD.

PART 

List of the partners (maximum of four) for which a PeSIT session, where the transactional turn is cyclically opened..

Inactive partners (result of the command INACT) are not taken into account.

PROF 

PeSIT D or E protocol profile.

The profile options are:

  • SIT profile: the PeSIT is then used in the SIT network context.
    It is the same in PeSIT version D and version E.
    It provides synchronization point management but does not manage:
    • segmentation: the value of the SEGMENT parameter must be set to
      NO (SEGMENT = NO)
    • or multi-records: the value of the MULTART parameter must be set to
      NO (MULTART = NO)

Note: A sender in the PeSIT SIT profile cannot segment a record sent in several data FPDUs or group several records sent in the same data FPDU

  • or compression: the RCOMP and SCOMP parameters are not applicable
  • or receive transfer requests
  • EXTERN profile: corresponds to the "non-SIT" (external to SIT network) standardized definition of the PeSIT version D protocol
  • CFT profile: the PeSIT version D protocol is used outside the context of the SIT network, the partner also having a Transfer CFT

Its functionality level is greater than the PeSIT D EXTERN profile specifications,

  • ANY profile: corresponds to the "non-SIT" (external to SIT network) standardized definition of the PeSIT version E protocol

This profile includes the facilities of the CFT profile, as standard.

Additional facilities are provided between two Transfer CFTs, while remaining in conformity with the PeSIT E standard. These facilities are based on the use of the PI 99 (free PI).

  • the DMZ profile (DeMilitarized Zone): corresponds to the normalized "hors SIT" definition for the PeSIT protocol, version E E (refer to Managing the Turn)

Note: In server mode, the PROF parameter can take either the EXTERN, CFT or ANY values (corresponding to the "non-SIT" profiles): indeed, in server mode, the Transfer CFT automatically adapts itself to the non-SIT profile proposed by the requesting partner.

RCHKW

Size of the receive mode synchronization point acknowledgement anticipation window, expressed as a number of synchronization points.

Negotiated with the sender partner.

RCHKW=0 means that synchronization points are not acknowledged.

RCHKW=1 is equivalent to operation in half-duplex mode.

On LU6.2 networks all non-null values will be forced to 1 during protocol negotiation.

RESYNC

PeSIT D CFT profile, PeSIT D EXTERN profile, PeSIT E

Dynamic resynchronization of exchanges during transfer (without interrupting the data exchange phase).

This option is negotiated with the partner at the time the connection is established: if this option is set to NO for one of the partners, dynamic resynchronization is not managed.

Note: The only dynamic resynchronization possible between two Transfer CFTs is performed when a CRC error is detected (PAD=YES).

REVERSE

Only in requester mode  PeSIT D CFT profile, PeSIT E

Option to reuse a connection to perform two transfers in different directions one after the other.

RPACING

Value of the interval between synchronization points for receive transfers (in Kbytes) (1 Kbyte = 1024 bytes) (see explanations of the SPACING parameter).

This parameter is negotiated with the partner (SPACING parameter if Transfer CFT); the smallest value is selected as the interval between synchronization points.

A null value (RPACING = 0) means that synchronization points are not set.

RRUSIZE 

Maximum size of NSDUs being received and sent.

This parameter is negotiated with the partner (SRUSIZE parameter if Transfer CFT); the smallest value is selected as the size of NSDUs sent.

Refer to the Transfer CFT Protocol for more information on this parameter.

SCHKW

Size of the send mode acknowledgement anticipation window for synchronization points, expressed as a number of synchronization points.

SEGMENT

Only in sender mode  Profile

Option to segment file records in several FPDUs.

SPACING 

Interval between synchronization points being sent (in Kbytes)
(1 Kbyte = 1 024 bytes).

SRUSIZE

Maximum size of NSDUs being received and sent.

SSERV

see details

Identifies the service (protocol variant) required for the incoming partner.

Example [FOR DETAILS: PeSIT examples ]

SSL parameter

The CFTPROT object accepts the optional SSL parameter. For the declared protocol, it sets the:

  • Default security profile in requester mode
  • Security profile in server mode

If the SSL parameter is set in a CFTPROT object, transport security must be implemented in both the server and requester modes.

The security profile is mandatory in server mode. The default security profile for the requester mode is optional: if it does not exist, it must then be declared for each CFTPART object, which provides the transfer partner definition.

The new SSL parameter is used to associate a security profile with a protocol definition.

For a security profile related to incoming calls (server mode), the SSL parameter value must correspond to the identifier of a DIRECT=SERVER SSL command.

For a default security profile related to outgoing calls (client mode), the SSL parameter value must correspond to the identifier of a DIRECT=CLIENT SSL command.

If you do not define the CFTPROT SAP parameter when using the SSL protocol, then the server mode for CFTSSL is not mandatory.

Syntax:  

CFTPROT

[SSL =     identifier,]

Description

Use the CFTPROT object to set:

  • Default security profile in requester mode
  • Security profile in server mode

Parameter

SSL

SSL commands Identifier  used for security profiles.

PeSIT examples

PeSIT profile

PeSIT protocol, SIT profile, associated with the data exchange protocol and network resources defined by the CFTNET ID=ACCEPTOR command.

The time-outs are the default values [ Compression]. Each FPDU contains a single file record (MULTART=NO). There is no on-line compression.

CFTPROT     ID     = PSITIN,          /* PSITIN protocol               */
     TYPE     = PESIT, PROF=SIT,     /* PeSIT SIT                      */
     NET     = ACCEPTOR,
     SCOMP     = 0,                /* No compression                    */
     RCOMP     = 0,                /* in SIT profile                    */
     CONCAT     = YES

PeSIT D EXTERN profile

CFTPROT     ID     = PSITEXT,
     TYPE     = PESIT,
     NET     = xx,
     PROF     = EXTERN,
     CONCAT     = YES,
     MULTART     = YES,
     SEGMENT     = NO

PeSIT D CFT profile

PeSIT D CFT profile

CFTPROT     ID     = PSITCFT,
     TYPE     = PESIT,
     NET     = yy,
     PROF     = CFT,
     CONCAT     = YES,
     MULTART     = YES,
     SEGMENT     = YES

PeSIT E

CFTPROT     ID     = PSITE,
     TYPE     = PESIT,
     NET     = zz,
     PROF     = ANY,
     CONCAT     = YES,
     MULTART     = YES,
     SEGMENT     = YES

Related Links