Transfer CFT messages: CFTH

This topic lists the CFTHxx (CFT xnnx) messages and provides the type, a description, consequence, and corrective actions when applicable.

Message format

Earlier versions of Transfer CFT used a different message format than the current version 3.1.3. The error messages displayed in this document use the former, or earlier version, format. If your system uses the CFTLOG parameter Format = V24, the log display is as shown below:

CFTXXX: fixed text message <variables>

Example

CFTLOG FORMAT=[V23,V24]

For V23: CFTT57I PART=&part IDF=&idf IDT=&idt &str transfer started

For V24: CFTT57I &str transfer started <IDTU=&idtu PART=&part IDF=&idf IDT=&idt>

Error

CFTH01E: PART=&part Context area allocation failure CS=&scs

Explanation

Cannot allocate the working area necessary for the transfer.

Consequence

In REQUESTER mode, the transfer is refused with a Transfer CFT 122 diagnostic code and a MALLOC protocol diagnostic message.

In SERVER mode, the incoming call is rejected. In this case, as the partner's name is not known, the value UNKNOWN is displayed.

 

Error

CFTH02E: PART=&part TFIL Exchange buffer allocation failure CS=&scs

Explanation

Cannot allocate the working area required to exchange information between the PROTOCOL task and the FILE task.

Consequence

In REQUESTER mode, the transfer is refused with a Transfer CFT 122 code and a MALLOC protocol diagnostic message.

In SERVER mode, the incoming call is rejected. In this case, as the partner's name is not known, the value UNKNOWN is displayed.

 

Error

CFTH03E PART=&part Error sending data on network NCR=&ncr NCS=&ncs NET=&net

Explanation

Cannot send a message on the network.

Consequence

The transfer is interrupted with a Transfer CFT 302 code and a protocol diagnostic message indicating the specific error code of the error that occurred during the send request. This code is expressed in hexadecimal.

 

Error

CFTH04E PART=&part Mismatch between header and FPDU size

Explanation

The transfer is aborted. A 318 protocol code, transported by an ABORT FPDU, is reported to the remote partner.

 

Error

CFTH05E: PART=&part ,&message

Explanation

Inconsistent FPDU received.

The end of the message is then set to one of the following values:

  • Unknown FPDU type=n:

Reception of an FPDU, for which the type byte in the header is unknown

  • Missing PI number n into FPDU fpdu:

Reception of an FPDU with missing mandatory PI

  • PGI n in PGI into FPDU fpdu:

Reception of an FPDU embedding a PGI in a PGI

  • Invalid length n for PI n into FPDU fpdu:

Reception of an FPDU with a PI of invalid length

  • Unknown PI number n into FPDU fpdu:

Reception of an FDPU with an unwanted PI

Consequence

The transfer is aborted. A 318 protocol code, transported by an ABORT FPDU, is reported to the remote partner.

 

Error

CFTH06E: PART=&part Error &cr while formatting FPDU

Explanation

Problem encountered while formatting an FPDU.

  • -1  PGI embedded in a PGI
  • -2  Output buffer overflow
  • -3  End of PGI without PGI
  • -4  External/internal type error
  • -5  End of FPDU with PGI not closed
  • -8  Invalid PI length
  • -11  FPDU description pointer null

Consequence

The transfer is aborted. A 220 protocol code, transported by an ABORT FPDU, is reported to the remote partner.

 

Error

CFTH07E PART=&part TFIL task Synchronization error CR=&cr CS=&scs

Explanation

Problem encountered when sending a Transfer CFT internal message to the FILE task.

Consequence

The transfer is aborted by the protocol task (network disconnection). However, as the FILE task is not protected by a time-out, the request remains in the C status in the catalog.

 

Error

CFTH08E: PART=&part Network release response error NCR=&ncr NCS=&ncs

Explanation

Cannot respond to a network connection failure indication.

Consequence

This incident has no impact on the previous transfer (whether terminated or interrupted).

 

Error

CFTH09E PART=&part Network connect request local error NCR=&ncr NCS=&ncs

Explanation

Cannot make an outgoing connection request on the network. For a general -6 code (maximum number of connections reached on the resource), the transfer is refused with a Transfer CFT 416 diagnostic code and a MAXCNX protocol diagnostic message.

The transfer will be retried (minimum time-out equal to the WSCAN parameter of the CFTCAT command), without incrementing the retry counter.

 

Error

CFTH10E: PART=&part Network connect reject RECOV=&recov L= &local R=&reason D=&ncs

Explanation

The physical connection has been refused.

Consequence

Depending on the origin of the refusal and the RECOV code, the transfer is set to the K state (diagnostics code 303) or remains set to the D state (diagnostics code 302) and will be retried.

 

Error

CFTH11E PART=&part Error Opening session EV=&pevent ST=&pstate

Explanation

Problem opening a PeSIT session with a remote partner after establishing the network session.

Consequence

The transfer is aborted with a Transfer CFT 451 diagnostic code.

 

Error

CFTH12E PART=&part Logon reject logon

Explanation

The PESIT pre-connection phase, logon, is refused by the SERVER partner (the correct response is ACK0 in EBCDIC). The string received is included in the message.

Consequence

The transfer is aborted with one of the following possible diagnostic codes:

  • 903: invalid password
  • 970: password expired, or
  • 963: unknown acknowledgment of a pre-connection request

 

Error

CFTH13E PART=&part FPDU Remote reject DIAGI=&diagi DIAGP=&diagp

Explanation

FPDU including a diagnostic code has been received. The DIAGP field is of the XXX NNN type.

Consequence

The transfer is aborted.

 

Error

CFTH14E PART=&part Invalid AckCONNECT FPDU &str

Explanation

The AckCONNECT FPDU sent by the SERVER partner is invalid.

The field "&str" is an explicit character string:

  • Version = n:

The protocol version negotiated by the SERVER partner is invalid Window without Pacing: A synchronization window is specified even though the interval is null,

  • Window = n too large:

The synchronization window negotiated by the SERVER partner is too large The SIT profile does not allow a value greater than 16

  • Pacing = n not authorized:

The synchronization interval negotiated by the SERVER partner does not comply with the specifications of the SIT profile The values 1, 2 and 3 are not allowed

  • Pacing = n greater than initial value = n:

The synchronization interval negotiated by the SERVER partner is larger than that proposed

  • Window = n greater than initial value = n:

The synchronization window negotiated by the SERVER partner is larger than that proposed

  • Resynchronization = n:

The value of the resynchronization option negotiated by the SERVER partner does not comply with the specifications of the protocol

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

The transfer is aborted with DIAGI=220, DIAGP=ACO + PeSIT code.

 

Error

CFTH15E: PART=&part Invalid AckCREATE FPDU &str

Explanation

The AckCREATE FPDU sent by the SERVER partner does not conform.

The "&str" string is an explicit character string:

  • NSDU size = n greater than initial value = n:

The maximum NSDU size negotiated by the partner is greater than that proposed

  • NSDU size = n too lower for LRECL = n:

In the SIT profile, as segmentation is not authorized, a record must fit in an FPDU. The negotiated NSDU size (RUSIZE) must therefore be greater than the record length of the file (plus 6 for the FPDU header)

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ACR + PeSIT code.

 

Error

CFTH16E: PART=&part Invalid AckWRITE FPDU &str

Explanation

The AckWRITE FPDU sent by the SERVER partner does not conform.

The field "&str" is an explicit character string:

  • Restart point without restart option:

The remote partner proposes a restart point for the transfer, even though it is a new transfer

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=AWR + PeSIT code.

 

Error

CFTH17E: PART=&part Invalid Check Point acknowledge &n

Explanation

The synchronization check point number is not correct.

 

Error

CFTH18E: Incoming call reject error NCR=&ncr NCS=&ncs NET=&net

Explanation

Cannot refuse an incoming call.

Consequence

The transfer is aborted by the protocol task (it is not registered in the catalog)

 

Error

CFTH19E: Incoming call accept error NCR=&ncr NCS=&ncs NET=&net

Explanation

Cannot accept an incoming call.

Consequence

The transfer is aborted by the protocol task (it is not registered in the catalog).

 

Error

CFTH20E: Invalid CONNECT FPDU &str

Explanation

The CONNECT FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • CRC option = n:

The remote partner proposes a value for the CRC option which does not comply with protocol specifications.

  • This value is displayed:

Only the values 0 (no CRC) and 1 (application of a CRC) are correct

  • Version = n:

The protocol version proposed by the remote partner does not comply with the specifications of the PeSIT protocol.

Only the values 1 (version D) and 2 (version E) are allowed. The incorrect value is displayed in the message

  • Window without Pacing:

A synchronization window is specified even though the interval is null

  • Window = n too large:

The synchronization window negotiated by the REQUESTER partner is too large. The SIT profile does not allow a value greater than 16

  • Access = n:

The correct access types are 0 for write mode, 1 for read mode and 2 for read/write mode. The other values represent a violation of the protocol. The incorrect value received is displayed in the message.

  • Resynchronization = n:

The functional resynchronization unit is negotiated by the value 0 (no) or 1 (yes). Any other value is not allowed

  • Pacing = n not authorized:

The synchronization interval negotiated by the SERVER partner does not comply with the specifications of the SIT profile. The values 1, 2 and 3 are not allowed

  • Application type relation R=sapp S=rapp:

The SIT profile imposes a correlation between the sender and receiver applications. This correlation is not respected. The message displays the first byte of PI 3 and 4 of the CONNECT FPDU in numeric form

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

The transfer is aborted without trace in the catalog.

 

Error

CFTH21E: PART=&part MAIN task Synchronization error CR=&cr CS=&scs

Explanation

Transfer CFT internal synchronization error.

 

Error

CFTH22E: PART=&part rejected DIAGI=&diagi

Explanation

The Transfer CFT refuses to open a protocol session following a request to do so from a partner. The message displays the Transfer CFT diagnostic code.

Consequence

The transfer is aborted. No trace of this attempt appears in the catalog.

 

Error

CFTH23E: PART=&part rejected EVENT=&pevent

Explanation

Transfer CFT refuses to open a protocol session for internal reasons, following a request to do so from a partner. The event which caused this rejection is displayed in the message.

Consequence

The transfer is aborted. No trace of this attempt appears in the catalog.

 

Error

CFTH24E: PART=&part Invalid CREATE FPDU &str

Explanation

The CREATE FPDU sent by the REQUESTER partner does not conform. The field "&str" is an explicit character string:

  • IDT is null:

Reception of a CREATE FPDU with a null Transfer Identifier (PI 13)

  • Restart = n:

Invalid value for the restart option of a transfer

  • Data Code = n:

Unknown code for the data to be transported

  • Priority = n:

Invalid priority assigned to the transfer

  • Record Format = n:

Unknown record format

  • Record size = n greater than Pacing:

The record size is greater than the synchronization interval

  • NSDU size = n too lower for LRECL = n:

In the SIT profile, as segmentation is not authorized, a record must fit in the FPDU. The negotiated NSDU size (RUSIZE) must therefore be greater than the record length of the file (plus 6 for the FPDU header).

  • File Organization = n:

Unknown file organization

  • Key length without indexed organization:

A key length is specified for a file that is not indexed

  • Key Position without indexed organization:

A key position is specified for a file that is not indexed

  • Space Unit in record without fixed format:

A file must be in fixed format for its size to be expressed as a number of records

  • Space Unit = n:

Space reservation unit unknown

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=CRE + PeSIT code.

 

Information

CFTH25I: PART=&part Concatenation area allocation failure CS=&scs

Explanation

Cannot allocate a working area to execute the concatenation option.

Consequence

The transfer continues but the concatenation option remains inhibited for the rest of the session.

 

Error

CFTH26E: PART=&part Too many data without synchronization

Explanation

Detection of a synchronization error.

Consequence

The transfer is aborted.

 

Error

CFTH27E: PART=&part SYNC FPDU without synchronization

Explanation

A synchronization FPDU was received unexpectedly as the Functional Synchronization Unit was not negotiated at the beginning of the session.

Consequence

The transfer is aborted with a Transfer CFT 730 diagnostic code, a protocol violation.

 

Error

CFTH28E: PART=&part Invalid Checkpoint n

Explanation

Reception of an invalid synchronization point, which does not follow the sequence.

Consequence

The transfer is aborted.

 

Error

CFTH29E: PART=&part Invalid FPDU RC=&n

Explanation

An inconsistent FPDU has been received. The RC code enables the error found to be defined more specifically: this code is identical to the one included in the PDU_iNN protocol diagnostic message.

Consequence

The transfer is aborted.

 

Error

CFTH30E: PART=&part Invalid AckORF FPDU &str

Explanation

The AckORF FPDU sent by the SERVER partner does not conform.

The field "&str" is an explicit character string:

  • Compression Indicator = n:

The compression indicator has a value which does not comply with the specifications of the PeSIT protocol (0 no compression, 1 compression)

  • Compression Value without Indicator:

A compression value is negotiated even though the indicator inhibits the compression option

  • Compression Indicator without Value:

The compression indicator is set even though the negotiated value is null

  • Compression Value = n:

The negotiated compression value does not comply with to the specifications of the PeSIT protocol

  • Compression Negotiation: n for n:

The negotiated compression is greater than the proposed compression

  • Extended LRECL greater than PACING: n for n:

Compression may cause a record to be extended. This risk, which is measurable (1 byte for 32 bytes), means that the record size becomes greater than the synchronization interval

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=AOF + PeSIT code.

 

Error

CFTH31E: PART=&part Invalid AckTRANS.END FPDU &str

Explanation

The AckTRANSFER.END FPDU sent by the SERVER partner does not conform.

The field "&str" is an explicit character string:

  • Byte count mismatch n for n:

The number of bytes transferred does not correspond to the Transfer CFT-maintained counter

  • Record count mismatch n for n:

The number of records transferred does not correspond to the Transfer CFT-maintained counter

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ATE + PeSIT code.

 

Error

CFTH32E: PART=&part Invalid AckMESSAGE FPDU &str

Explanation

This message is only displayed in security-enabled mode and corresponds to a security problem.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

 The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=AMG + PeSIT code.

 

Error

CFTH33E: PART=&part Invalid AckSELECT FPDU &str

Explanation

The AckSELECT FPDU sent by the SERVER partner does not conform.

The field "&str" is an explicit character string:

  • File type value not authorized:

Reception of an AckSELECT FPDU with an invalid file type (PI 11) The values between 0xFFFC and 0xFFFF are invalid

  • IDT is null:

Reception of an AckSELECT FPDU with a null Transfer Identifier (PI 13)

  • Data Code = n:

Unknown code for the data to be transported

  • Priority = n:

Invalid priority assigned to the transfer

  • Record Format = n:

Unknown record format

  • Record size = n greater than Pacing:

The record size is greater then the synchronization interval

  • NSDU size negotiation n for n:

The negotiated NSDU size is greater than that proposed

  • NSDU too small n:

The negotiated NSDU size is smaller than the minimum authorized value (128)

  • File Organization = n:

Unknown file organization

  • Key length without indexed organization:

A key length is specified for a file that is not indexed

  • Key Position without indexed organization:

A key position is specified for a file that is not indexed

  • Space Unit in record without fixed format:

A file must be in fixed format for its size to be expressed as a number of records

  • Space Unit = n:

Space reservation unit unknown

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ASE + PeSIT code.

 

Error

CFTH34E: PART=&part Invalid ORF FPDU &str

Explanation

The ORF FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • Compression Indicator = n:

The compression indicator has a value that does not comply with the specifications of the PeSIT protocol (0 no compression, 1 compression)

  • Compression Value without Indicator:

A compression value is negotiated even though the indicator inhibits the compression option

  • Compression Indicator without Value:

The compression indicator is set even though the negotiated value is null

  • Compression Value = n:

The negotiated compression value does not comply with the specifications of the PeSIT protocol

  • Extended Record size greater than pacing: n for n:

Compression may cause a record to be extended. This risk, which is measurable (1 byte for 32 bytes), means that the record size becomes greater than the synchronization interval

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ORF + PeSIT code.

 

Error

CFTH35E: PART=&part Invalid TRANS.END FPDU &str

Explanation

This message is only displayed in security-enabled mode and corresponds to a security problem.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=TFE + PeSIT code.

 

Error

CFTH36E: PART=&part Invalid MESSAGE FPDU &str

Explanation

The MESSAGE FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • IDT is null:

Reception of a MESSAGE FPDU with a null Transfer Identifier (PI 13)

  • Attribute = n:

PI 14 in the MESSAGE FPDU is set to an invalid value (attribute request)

  • Data Code = n:

Unknown code for the data to be transported

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=MSG + PeSIT code.

 

Error

CFTH37E: PART=&part Invalid D.MESSAGE FPDU &str

Explanation

The START of MESSAGE FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • IDT is null:

Reception of a D.MESSAGE FPDU with a null Transfer Identifier (PI 13)

  • Attribute = n:

PI 14 of the D.MESSAGE FPDU is set to an invalid value (attribute request)

  • Data Code = n:

Unknown code for the data to be transported

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=DMG + PeSIT code.

 

Error

CFTH38E: PART=&part Invalid READ FPDU &str

Explanation

The READ FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • Restart point must be null for new transfer:

Reception of a READ FPDU with a restart point other than 0 for a new transfer

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=RDF + PeSIT code.

 

Error

CFTH39E: PART=&part Invalid SELECT FPDU &str

Explanation

The SELECT FPDU sent by the REQUESTER partner does not conform.

The field "&str" is an explicit character string:

  • IDT not null:

Reception of a SELECT FPDU with a non-null Transfer Identifier (PI 13) for a new transfer

  • IDT null with restart:

Reception of a SELECT FPDU with a null Transfer Identifier (PI 13) for a transfer to be restarted

  • Attribute = n:

PI 15 of the SELECT FPDU is set to an invalid value (file attribute request)

  • Restart = n:

PI 15 of the SELECT FPDU is set to an invalid value (restart or new transfer)

  • Priority = n:

PI 17 of the SELECT FPDU is set to an invalid value (transfer priority)

  • NSDU too small n:

The negotiated NSDU size is smaller than the minimum allowed value (128)

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=SEL + PeSIT code.

 

Error

CFTH40E: PART=&part Invalid DTF FPDU (MULTART)

Explanation

The DTF FPDU received is multi-record but it is not valid (the sum of the record lengths is not equal to the total length of the received FPDU).

Consequence

The transfer is aborted. The protocol code transported to the remote partner is 220.

 

Error

CFTH41E: PART=&part Invalid DTF.END FPDU &str

Explanation

The DTF END (end of data) FPDU sent by the sender partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=DTE + PeSIT code.

 

Error

CFTH42E: PART=&part Invalid SYNC

FPDU &str

Explanation

The SYNC (set synchronization point) FPDU sent by the sender partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=SYN + PeSIT code.

 

Error

CFTH43E: PART=&part Invalid AckSYNC      FPDU &str

Explanation

The AckSYNC (acknowledge synchronization point) FPDU sent by the receiver partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ASY + PeSIT code.

 

Error

CFTH44E: PART=&part Invalid IDT FPDU &str

Explanation

The IDT (transfer interrupt) FPDU sent by the partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received,

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=IDT + PeSIT code.

 

Error

CFTH45E: PART=&part Invalid AckIDT FPDU &str

Explanation

The AckIDT (acknowledge transfer interrupt) FPDU sent by the partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

 The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=AID + PeSIT code.

 

Error

CFTH46E: PART=&part Invalid RESYNC FPDU &str

Explanation

The RESYNC (dynamic transfer resynchronization) FPDU sent by the sender partner does not conform.

The field "&str" is an explicit character string:

  • Resynchronization is not authorized:

Dynamic resynchronization is not authorized (CFTPROT RESYNC parameter) or the maximum number of resynchronizations is exceeded (CFTPROT RESTART parameter),

  • Mismatch between header and FPDU size:

The FPDU length indicated in the header is not equal to the length of the FPDU received

  • Unknown FPDU:

The number identifying the received FPDU is not referenced

  • Missing PI number n into FPDU:

The PI is mandatory for this type of FPDU

  • Unknown PI number n into FPDU:

The PI is unknown for this type of FPDU

  • PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid

  • Invalid length n for PI n into FPDU:

The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=RST + PeSIT code.

 

Error

CFTH47E: PART=&part Invalid DESELECT FPDU &str

Explanation

The DESELECT FPDU sent by the requester partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=DSE + PeSIT code.

 

Error

CFTH48E: PART=&part Invalid DESELECT FPDU &str

Explanation

The AckRead FPDU sent by the receiver/sender partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ARD + PeSIT code.

 

Error

CFTH49E: PART=&part Invalid WRITE FPDU &str

Explanation

The WRITE FPDU sent by the requester/sender partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=WRI + PeSIT code.

 

Error

CFTH50E: PART=&part Invalid M.MESSAGE FPDU &str

Explanation

The Middle of Message FPDU sent by the requester partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=MMG + PeSIT code.

 

Error

CFTH51E: PART=&part Invalid F.MESSAGE FPDU &str

Explanation

The End of Message FPDU sent by the requester partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU:The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU:The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU:The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU:The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=FMG + PeSIT code.

 

Error

CFTH52E: PART=&part Invalid AckCLOSE FPDU &str

Explanation

The AckCLOSE FPDU sent by the server partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=ACF + PeSIT code.

 

Error

CFTH53E: PART=&part Invalid AckDESELECT  FPDU &str

Explanation

The AckDESELECT FPDU sent by the server partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum le

Consequence

Transfer aborted with DIAGI=220, DIAGP=ADS + PeSIT code.

 

Error

CFTH54E: PART=&part Invalid CLOSE FPDU &str

Explanation

The CLOSE (file close) FPDU sent by the requester partner does not conform.

The field "&str" is an explicit character string:

  • Mismatch between header and FPDU size: The FPDU length indicated in the header is not equal to the length of the FPDU received
  • Unknown FPDU: The number identifying the received FPDU is not referenced
  • Missing PI number n in FPDU: The PI is mandatory for this type of FPDU
  • Unknown PI number n in FPDU: The PI is unknown for this type of FPDU
  • PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is invalid
  • Invalid length n for PI n into FPDU: The length of the PI is invalid (less than minimum length or greater than maximum length)

Consequence

Transfer aborted with DIAGI=220, DIAGP=CRF + PeSIT code.

 

Error

CFTH55E: PART=&part Invalid DTF FPDU &str

Explanation

The DTF (data send) FPDU sent by the sender partner does not conform.

The field "&str" is an explicit character string:

  • Too much data without synchro

A synchronization interval, CFTPROT SPACING or RPACING parameter, has been negotiated and the amount of data received since the start of the transfer (or since the last synchronization FPDU) is greater than this interval.

Consequence

Transfer aborted with DIAGI=220, DIAGP=DTF + PeSIT code.

 

Information

CFTH56I ODETTE &str session opened <PART=&part IDS=&ids pi2=&n pi24=&n HOST=&addr>

CFTH56I PESIT &str session opened <PART=&part IDS=&ids pi7=&n:&n HOST=&addr>

Explanation

An ODETTE session in either Requester or Server mode was opened.

Where:

  • PART: partner
  • PROT: local protocol definition (CFTPROT)
  • IDS: reference for this session
  • pi2 and pi24: the window and the interval of the negotiated synchronization
  • HOST:
    • Requester side: the host address configured through CFTTCP for the related partner (either an IP or a logical hostname).

    • Server side: the IP address of the incoming connection.

 

A PeSIT session in either Requester or Server mode was opened.

Where:

  • PART: partner
  • PROT: local protocol definition (CFTPROT)
  • IDS: reference for this session
  • pi7: the window and the interval of the negotiated synchronization
  • HOST:
    • Requester side: the host address configured through CFTTCP for the related partner (either an IP or a logical hostname).

    • Server side: the IP address of the incoming connection.

 

Information

CFTH57I transfer selected PART=&part IDS=&ids IDF=&idf IDT=&idt pi25=&n /

Explanation

A transfer passed the selection phase in the PeSIT session that was referenced by the IDS field.

The field pi25 indicate the maximum size of the negotiated message. The displayed reference in the second message is the public transfer reference.

 

Information

CFTH58I transfer deselected <PART=&part IDS=&ids IDF=&idf NIDT=&idt T=&n>

Explanation

A transfer passed the deselection phase in the PeSIT session referred to by the IDS. The IDS is the reference for this particular session context.

The T field indicates the armed time-out for the CFTPROT parameter:

  • disctd – requester mode, or
  • discts – server mode

 

Information

CFTH59I message transferred PART=&part IDS=&ids IDM=&idm NIDT=&idt

Explanation

A message transfer was carried out in the PeSIT as referenced by the IDS field, where the IDS refers to this specific session context.

The displayed reference in the second message is the public transfer reference.

 

Information

CFTH60I reply transferred PART=&part IDS=&ids IDM=&idm NIDT=&idt

Explanation

An acknowledgement type transfer message was carried out in the PeSIT session, where the IDS references the session context.

The reference in the second message is the public transfer reference.

 

Information

CFTH61I ODETTE &s session closed PART=&part IDS=&ids

Explanation

A ODETTE session in Requester or Server mode was closed.

Where:

  • PROT: the local definition of the protocol (CFTPROT)
  • IDS: the reference for this session context

 

Information

CFTH62I REF=&ref

Explanation

A message transfer has been performed in the PeSIT session referenced by the IDS field.

The reference displayed in the second message is the public reference of the transfer (pi13.pi3.pi4.pi11.pi12.pi61.pi62).

Information

CFTH62I REF=&PublicReference

Explanation

The transfer has passed the selection phase in the PeSIT session referenced by the IDS field.  

The pi25 field indicates the maximum size of the negotiated message.

The reference displayed in the second message is the public reference of the transfer (pi13.pi3.pi4.pi11.pi12.pi61.pi62).

Information

CFTH62I REF=&ref

Explanation

An acknowledgement-type message was performed in the PeSIT session referenced by the IDS, the session reference.

The reference displayed in the second message is the public reference of the transfer (pi13.pi3.pi4.pi11.pi12.pi61.pi62).

 

Information message

CFTH63I PESIT DMZ session for messages only PART=&part IDS=&ids

Explanation

A PeSIT DMZ session was open but only for mailing messages. This message follows message CFTH56I, where the IDS is the session call id.

 

Information

CFTH64I PESIT session rejected L=&reason R=&diag

Explanation

Protocol connection refused at network level.

  • &reason: Network reason
  • &diag: Network diagnostic

 

Information

CFTH65I: PESIT DMZ permanent session control call=&call PART=&part IDS=&ids

Explanation

Support for permanent links in DMZ.

Transfer CFT in DMZ does not give the TURN when there are no more files to send, but sends an FPDU Control Call to the initiator Transfer CFT at regular negotiated intervals to prevent the temporization from expiring.

  • &ids = Session call id
  • &call = interval for the DMZ control call

 

Error

CFTH66E Incoming calls (&count) rejected, ERROR=&error (&info1|&info2), PROTOCOL=&protocol

Explanation

Incoming calls are rejected:

  • &count = Number of rejected calls
  • &error = Error message
  • &info1 = Additional information
  • &info2 = Additional information
  • &protocol = Protocol type when available

Related Links