Transfer CFT messages: CFTG

This topic lists the CFTGxx (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

CFTG01E: 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

CFTB02E: 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

CFTG03E: 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

CFTG04E: PART=&part Mismatch between header and FPDU size

Explanation

The FPDU size does not match the information in the header (the first two bytes indicate the FPDU size).

Consequence

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

 

Error

CFTG05E: message&part ,&PART=

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

CFTG06E: 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

CFTG07E: 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 message

CFTG08E: PART=&part Network release response error NCR=&ncr NCS=&ncs NET=&net

Explanation

Cannot respond to a network release indication.

Consequence

This incident has no effect on the previous transfer (whether completed or interrupted).

 

Error

CFTG09E: PART=&part Network connect reqt local err NCR=&ncr NCS=&ncs NET=&net

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, the minimum time-out equal to the WSCAN parameter of the CFTCAT command, without incrementing the retry counter.

 

Error

CFTG10E: PART=&part RECOV=&recov L= &local R=&reason D=&ncs NET=&net

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

CFTG11E: 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

CFTG12E: PART=&part SAPPL=&sappl Invalid application type relation

Explanation

The SIT profile imposes a correlation between the sending and receiving applications. This correlation is not respected.

Consequence

The transfer is aborted.

 

Error

CFTG13E: 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

CFTG14E: str&part Invalid AckCONNECT FPDU &PART=

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

CFTG15E: 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:

  • SDU 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

CFTG16E: str&part Invalid AckWRITE FPDU &PART=

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 message

CFTG17E: PART=&part Invalid Check Point acknowledge n

Explanation

Reception of an invalid synchronization point acknowledgment. This message is to be analyzed in association with the protocol diagnostic message ASY_inn.

Consequence

The transfer is aborted.

 

Error

CFTG18E : Incoming call reject error NCR=&ncr NCS=&ncs

Explanation

Cannot refuse an incoming call.

Consequence

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

 

Error

CFTG19E: Incoming call accept error NCR=&ncr NCS=&ncs

Explanation

Cannot accept an incoming call.

Consequence

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

 

Error

CFTG20E: Invalid CONNECT FPDU %s

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 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

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

Explanation

Transfer CFT internal synchronization error.

 

Error

CFTG22E: 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

CFTG23E: PART=&part rejected EVENT=%s

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

CFTG24E: 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.

 

Error

CFTG25E: PART=&part Multi-record FPDU not authorized

Explanation

A data FPDU containing several records (MULTART option) is not supported in the SIT profile.

Consequence

The transfer is aborted.

 

Error

CFTG26E : PART=&part Too many data without synchronization

Explanation

Detection of a synchronization error.

Consequence

The transfer is aborted.

 

Error

CFTG27E: 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 (protocol violation).

 

Error

CFTG28E: part Invalid Checkpoint n&PART=

Explanation

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

Consequence

The transfer is aborted.

 

Error

CFTG29E: 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.

Related Links