TROUBLESHOOTING GUIDE

Transfer CFT
Version 3.1.3

02 February, 2017
Copyright © 2015 Axway Software S.A.

All rights reserved.

This documentation describes the following Axway software: Transfer CFT

No part of this publication may be reproduced, transmitted, stored in a retrieval system, or translated into any human or
computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise,
without the prior written permission of the copyright owner, Axway Software S.A.

This document, provided for informational purposes only, may be subject to significant modification. The descriptions and
information in this document may not necessarily accurately represent or reflect the current or planned functions of this
product. Axway Software S.A. may change this publication, the pro­d uct described herein, or both. These changes will be
incorporated in new versions of this document. Axway Software S.A. does not warrant that this document is error free.

Axway Software S.A. recognizes the rights of the holders of all trademarks used in its publications.

The documentation may provide hyperlinks to third­party web sites or access to third­party content. Links and access to these
sites are provided for your convenience only. Axway Software S.A. does not control, endorse or guarantee content found in
such sites. Axway Software S.A. is not responsible for any content, associated links, resources or services associated with a
third­party site.

Axway Software S.A. shall not be liable for any loss or damage of any sort associated with your use of third­party content.
Contents

Preface 4
About Transfer CFT 4
Troubleshooting guide outline 4
Who should read this guide 4
Transfer CFT documentation set 6
Support services 6

Accessibility 7
Accessibility features of the documentation 7
Screen reader support 7
Support for high contrast and accessible use of colors 7

1 Troubleshoot 8
Getting information when an error occurs 8
Performing checks 8
Documentation 9
Axway forum 9
Support tools and contacting Support 10
Accessing the Axway Support site 10
Using CFT_support 10

2 Troubleshoot the server 12

Corrective actions 12
Troubleshoot installation and registration 13
Connect to a different Central Governance system 14
UCONF: Central Governance options 17
Install a certificate on the server 20
Troubleshoot the runtime 23
Reactivate an object 26
Deactivate objects 26
Query internal Transfer CFT components 28
Display product information 30
Extract data 32
Rebuild the runtime 34
Delete a command in the COM file 35
Suspend a transfer when offline 40
Manually create Transfer CFT internal datafile files 41
44
How to use ATM traces 44

Transfer CFT 3.1.3 Troubleshooting Guide i

 About Transfer CFT traces 45
Trace management concepts 45
Managing trace information collection 47
Trace commands 48
Defining a trace 50
Initializing the trace 51
Configuring the trace communication medium 52
Defining a trace file externally 53
Defining the internal trace file 54
Using the start trace command 58
Using the stop trace command 61

3 Messages and error codes 62

Message format 62
Format in the documentation 62
Format in the product 62
Writing conventions 63
Message description 63
Message source 63
Sequence number 64
Severity 64
Symbolic variables used in message text 64
Transfer CFT messages: CFTB 67
Transfer CFT messages: CFTC 70
Transfer CFT messages: CFTE 76
Transfer CFT messages: CFTG 76
Transfer CFT messages: CFTH 89
Transfer CFT messages: CFTI 125
Transfer CFT messages: CFTN 136
Transfer CFT messages: CFTP 137
Transfer CFT messages: CFTR 142
Transfer CFT messages: CFTS 148
Transfer CFT messages: CFTT 163
Transfer CFT messages: CFTW 187
Transfer CFT messages: CFTY 189
CFTUTIL utility output messages: CFTunnx 197
DIAGI: Diagnostic codes 206
Transfer CFT internal diagnostic codes 206
Diagnostic code values 206
Event column in diagnostic codes 206
Consequence column in diagnostic codes 207
DIAGP: Event codes 233
RECOV: General network error recovery codes 240
General Transfer CFT protocol diagnostics 241

Transfer CFT 3.1.3 Troubleshooting Guide ii

 Diagnostics format 241
"Mnemonic"­Type DIAGP Codes 241
"L HH HHH"­Type DIAGP Codes 246
"R HH HHH"­Type DIAGP Codes 246
"HHHHHHHH"­Type DIAGP Codes 247
"eNNsNN"­Type PeSIT DIAGP Codes 247
"PDU iNN"­Type PeSIT DIAGP Codes 247
"XXX NNN"­Type PeSIT DIAGP Codes 247
"NNN HHHH"­Type ODETTE DIAGP Codes 248
"XXX HHHH"­Type ODETTE DIAGP Codes 248
Miscellaneous codes 249
Network codes 256
NCR Common return code ­ Network interface 256
NCS System return code ­ Network interface 256
PKIUTIL error codes 272
Protocol diagnostic codes 274
PeSIT protocol diagnostic codes 274
ODETTE Protocol Diagnostic Codes 283
Reason and diagnostic network codes 285
TCP/IP network codes 285
PeSIT protocol diagnostic codes 286
Diagnostic protocol field format 286
PeSIT E PI codes 293
PeSIT E CFT/CFT extensions 293
PeSIT­extension PI code descriptions 295
Synchronous communication return codes 300
How to find the return code 300
Send and receive related errors 301
SWAITCAT related errors 302

Transfer CFT 3.1.3 Troubleshooting Guide iii

Preface

This documentation provides information to help you get started in troubleshooting Transfer CFT. It
describes checks to perform, lists messages and codes along with corrective actions when
necessary, and describes how to collect information if you still need to contact Axway support.

About Transfer CFT

Transfer CFT is the file transfer component in the Axway 5 Suite platform, and provides a multi­
platform, high­volume, file and message transfer service.

As of version 3.1, you can configure Transfer CFT to manage flows using Axway Central
Governance. Central Governance simplifies Transfer CFT usage, and provides services such as
identity and access management, certificate management, monitoring, alerting, and a web
dashboard.

For more information on Axway products, visit www.axway.com.

Troubleshooting guide outline

Introduction - This chapter provides guidelines for identifying a problem, next steps, available
resources, and how to contact Axway support if required.

Corrective actions – This chapter describes procedures that can help you to troubleshoot and
resolve problems relating to Transfer CFT or Copilot server administration. Additionally it offers
corrective actions for issues that could occur during installation, an upgrade, or post­installation
procedures.

Messages and error codes- This chapter starts with an introduction to error messages, message
formats, severity, and additional conventions used in this chapter. It then lists the messages that
Transfer CFT generates, and corrective actions when applicable.

Who should read this guide

This guide is intended for enterprise personnel involved in installing or operating the Transfer
CFT software, and Axway Professional Services personnel. Familiarity with Axway products is
recommended.

This guide presumes you have knowledge of:

l Your company’s business processes and practices
l Your company’s hardware, software, and IT policies

Transfer CFT 3.1.3 Troubleshooting Guide 4

Preface

l The Internet, including use of a browser

Others who may find parts of this guide useful include network or systems administrators and other
technical or business users.

Transfer CFT 3.1.3 Troubleshooting Guide 5

Preface

Transfer CFT documentation set

Transfer CFT provides a complete set of documentation, covering all aspects of using the product.
These documents include the following:

l Transfer CFT 3.1.3 Release Notes

l Transfer CFT 3.1.3 Note de diffusion
l Transfer CFT 3.1.3 User Guide (HTML)
l Axway 5 Suite Supported Platforms Guide
l Axway 5 Suite Interoperability Matrix

Support services
The Axway Global Support team provides worldwide 24 x 7 support, subject to validation of your
license agreement. Email [email protected] or, for your local support telephone number, visit
Axway Sphere at support.axway.com and click Contact Axway Support.

You can post comments and question to the Axway user forum at: forums.axway.com/index.php

Transfer CFT 3.1.3 Troubleshooting Guide 6

Accessibility

At Axway, we strive to create accessible products and documentation for all our users.

This section describes the accessibility features of the documentation.

Accessibility features of the documentation

The product documentation provides the following accessibility features:
l Screen reader support

l Support for high contrast and accessible use of colors

Screen reader support

l Alternative text is provided for images whenever necessary.
l The PDF documents are tagged to provide a logical reading order.

Support for high contrast and accessible use

of colors
l The documentation can be used in high­contrast mode.
l There is sufficient contrast between the text and the background color.

Transfer CFT 3.1.3 Troubleshooting Guide 7

Troubleshoot
1
The Transfer CFT Troubleshooting Guide contains information to help you locate the cause of an
error, solve or define the problem, and additionally list corrective actions when applicable. The
Transfer CFT logs and catalogs provide useful information as to the state of the process, and may be
a good starting point when troubleshooting.

Transfer CFT generates messages that provide information about the processes and events that
occur on the Transfer CFT. These messages are collected and stored in a log file. If you are using
Central Governance, in the Products List page select the Transfer CFT in question. In the Transfer
CFT page, select Logs in the right pane to view the Transfer CFT logs.

Transfer CFT also generates messages that provide information about the state of a transfer. These
messages are collected and stored in a catalog file. From the Central Governance main menu, select
Flow > Monitoring > and then the type of View, for example View all flows in error for a
given application.

Getting information when an error occurs

All Transfer CFT error messages and diagnostics are listed in the section Messages and error codes. If
an error occurs in Transfer CFT that you cannot correct using the diagnostic information provided
there, see Performing checks below.

As you go through the questions in Performing checks, note your responses. If you need to
submit a Support request this information can help you to save time.

Documentation on page 9 lists related documentation that you may want to consult.

Performing checks
To better help you resolve an incident, you can print and use the following table. It can serve as a
guideline for gathering information, which can help you if you need to file an incident report.

Step Your remarks

1. Identify the symptoms

Did the system crash?

Is the error message due to a transfer

request, a transfer in server mode, or other?

Transfer CFT 3.1.3 Troubleshooting Guide 8

1 Troubleshoot

Step Your remarks

Is Transfer CFT functioning abnormally?

Is the symptom persistent?

Can you reproduce the symptom?

2. Locate the problem

Which component and function are

concerned?

Can you identify the source of the problem?

Can you bypass the problem?

3. Find the cause

Has your system or Transfer CFT recently

been re­configured?

Have you installed a new component, either

hardware or software?

Has the problem only recently occurred, or

has it existed for some time?

Documentation
If an error occurred while running Transfer CFT in Central Governance, you may also want to consult
the Central Governance documentation.

Some corrective actions may be operating system specific, so you may also want to refer to:

l Windows operations in the Transfer CFT 3.1.3 User Guide

l UNIX operations in the Transfer CFT 3.1.3 User Guide
l Transfer CFT 3.1.3 z/OS Installation and Operation Guide
l Transfer CFT 3.1.3 IBM i Installation and Operation Guide

Axway forum
Post comments and question to the user forum: http://forums.axway.com/index.php

Transfer CFT 3.1.3 Troubleshooting Guide 9

1 Troubleshoot

Support tools and contacting Support

Accessing the Axway Support site

In the Axway Support web site, Sphere, click to select Contact us for the email address and phone
number of your nearest Axway support site.

Opening a Support case

Before contacting Customer Support, we suggest that you start by using the Axway online patch
library to see if there is a patch available for your problem, or by searching for a solution in the
Knowledge Database. If you still need to contact Support, have the following information available
if possible:

l Product version
l Operating system
l Cft_support

To submit a Support request, you can do the following:

l Submit and track your request through the Axway Support Web site support.axway.com.
l Each time you submit a support request, that request is assigned a unique number. Use this
specific number when you contact Customer Support concerning that case.
l You must have a user account to submit a Support request.

Using CFT_support
The cft_support tool collects all of the needed information from the customer's Transfer CFT
installation environment, including the static configuration (PARM/PART), Unified Configuration
parameters (UCONF), catalog information, communication media file status (CFTCOM), log files,
execution environment (variables), disk space, and so on. This information is then packaged into a
archive file called cft-support-<date>(.tar.gz|.zip).

Note When using the cft_support tool on other Operating Systems, refer to the OS­specific
guide for the correct syntax.

Using Copilot
From the UI, click the debug icon. The report is saved in the Transfer CFT runtime directory, after
which you are prompted to download the report to your desktop.

Transfer CFT 3.1.3 Troubleshooting Guide 10

1 Troubleshoot

Using command line

UNIX/Windows
In command line enter: cft_support collect

IBM i
The CFTSUPPORT command executes the CFTSUPPORT program by submitting the script
CFTPGMn/CFTSRC MBR(B_SUPPORTn), which retrieves information about the Transfer CFT. In the
script name, the 'n' value represents the Transfer CFT environment number (from 1 to 5).

z/OS
Run the JCL XSUPPORA. You can transfer the resulting file to a Windows system, zip, and attach to
an email request.

Note ATM traces are available only when using Transfer CFT Local Administration. However
Central Governance managed Transfer CFT is the recommended version.

Transfer CFT 3.1.3 Troubleshooting Guide 11

Troubleshoot the server
2
Corrective actions
This section describes some procedures that can help you to troubleshoot and resolve problems
relating to Transfer CFT installation, runtime, or Copilot server administration. For example querying
the server, and using the collected information to help remedy the issue.

A complete listing of the Transfer CFT error messages and diagnostics, as well as message
conventions and formats, are available in the Messages and error codes section of the Messages and
error codes section of the User Guide.

Administrative issues are classified in the following general categories:

l Post installation and Central Governance registration

l Configuration and production issues

Possible corrective actions include:

l Collect system information ­ you can use either the Central Governance interface, or from
Transfer CFT use cft_support
l Check for updates and updating the system
l Regenerate the internal datafile or rebuild the runtime

Transfer CFT 3.1.3 Troubleshooting Guide 12

 Troubleshoot installation and registration

About start-up and registration

This section lists some possible post­installation issues along with corresponding corrective actions
when applicable. If corrective actions do not remedy the issue, check the Support tools section for
more information, or contact support at Axway Sphere.

Copilot server issues

Copilot doesn't start

l Check that the port is not already used by another application.
l Close all active sessions, use the syntax: copstop ­f
l Check that there are no orphan "cop*" processes. If there are, manually kill these processes.

Central Governance

Troubleshoot the registration

If Copilot starts, but the Transfer CFT either does not display in the Central Governance Product
List or registers in error:

l Verify the Central Governance IP address (or FQDN) used in the Transfer CFT configuration.
l On the computer running Transfer CFT, check that you can reach Central Governance at the IP
address used in the Transfer CFT configuration.
l Check that the Transfer CFT appears in the Central Governance logs. If not, typically this is
because the Transfer CFT is unable contact Central Governance.
l In Central Governance check Administration > Services to ensure that Central Governance is
correctly started.
l Verify the shared secret for Central Governance used in the Transfer CFT configuration.

Note See the Central Governance documentation for additional information and details.

Re-register with Central Governance

When Central Governance sends the SSL certificates to Transfer CFT, the uconf:cg.registration_id
parameter is set to a positive integer. If an error occurs, the registration process ends in error. To
repeat the registration, perform the following steps:

Transfer CFT 3.1.3 Troubleshooting Guide 13

2 Troubleshoot the server

1. Stop Transfer CFT.

2. Stop Copilot.
3. Set the uconf:cg.registration_id to its default value (­1) using the command:

CFTUTIL uconfunset id=cg.registration_id

4. Start the Transfer CFT Copilot. Copilot starts the registration process.

More information

For more information on Central Governance, refer to the Central Governance1.0.3 documentation.

Transfer CFT server

Cannot start my Transfer CFT

l Check my Transfer CFT's log in Central Governance
l From the local Transfer CFT runtime, try to manually start the server
o If you cannot manually start the server, refer to Support tools Support tools in the Transfer
CFT User Guide.

Connect to a different Central Governance

system
If Transfer CFTwas previously registered on a Central Governance system but you now want to
register it on a different one, perform the following steps.

All OS

This section describes how to manually modify the Transfer CFT configuration to enable Central
Governance connectivity in command line.

Prerequisites
1. Stop Transfer CFT and Copilot if running.
2. Enabling Central Governance connectivity after an upgrade implies replacing any standalone
connectors. Therefor, prior to connecting to Central Governance deactivate all previously
activated connectors, for example PassPort AM, PassPort PS, and Sentinel.

CFTUTIL uconfunset id=am.type

CFTUTIL uconfunset id=sentinel.xfb.enable
CFTUTIL uconfset id=pki.type, value=cft

Transfer CFT 3.1.3 Troubleshooting Guide 14

2 Troubleshoot the server

Note When running in a z/OS environment you must additionally set the am.passport.superuser
with the user that will start the Copilot server.

3. Ensure that all UCONF values used to identify a Transfer CFT instance are defined. These
parameters include:
l cft.full_hostname
l cft.instance_id
l cft.instance_group

Use the format:

CFTUTIL uconfset id=cft.instance_id, value=<cft_id>

Procedure
The manual procedure consists of the following steps, which are detailed below:

1. Include certificates in the PKI database.

2. Set the UCONF parameter values for Central Governance.
3. Enable Central Governance.
4. Start Copilot.

Include certificates
You must include the certificate authority that is used to validate communication with Central
Governance in the PKI database. You can personalize this certificate on the Central Governance side,
so be sure to use the correct iname in the pkicer command.

You can use any ID for this certificate. Transfer CFT uses the certificate ID defined in UCONF to
communicate with Central Governance.

Note Modify the filename syntax to accommodate your specific platform.

PKIUTIL pkicer id = 'CG_CA',

iform = 'PEM',
iname = '$CFTPKIDIR/passportCA.pem',
itype = 'ROOT',
pkifname = '$CFTPKU',
pkipassw = 'CFT',
state = 'ACT',
mode = 'CREATE'

After inserting the correct certificate in the PKI database, define the UCONF variable cg.ca_cert_id.
This value is required so that Transfer CFT knows which certificate to use when communicating with
Central Governance.

Transfer CFT 3.1.3 Troubleshooting Guide 15

2 Troubleshoot the server

CFTUTIL uconfset id=cg.ca_cert_id, value='CG_CA'

Set UCONF values

Use the Central Governance installation values for the following UCONF settings. Transfer CFT uses
these values to identify Central Governance.

l cg.host
l cg.port
l cg.mutual_auth_port
l cg.shared_secret

Use the format:

CFTUTIL uconfset id=cg.host, value=<host_value>

Enable Central Governance

CFTUTIL uconfset id=cg.enable, value=yes

As a final step, prior to starting Copilot, reset the Central Governance registration id.

CFTUTIL uconfunset id=cg.registration_id

Register
Start the Transfer CFT Copilot to trigger an automatic registration with Central Governance.

You can check in the Central GovernanceProduct List to confirm that the registration was
successful.

Transfer CFT 3.1.3 Troubleshooting Guide 16

2 Troubleshoot the server

UCONF: Central Governance options

This topic describes the Transfer CFT unified configuration parameters necessary to register with
Central Governance.

To enable Transfer CFT to self­register with Central Governance set the parameters listed in the
following table, either during the Transfer CFT installation or manually post installation.

Parameter Description Type Default Flags

value

cg.enable Enables exchanges with the Central bool No ­

Governance server (registration, Yes No
heartbeat).

cg.host Central Governance server host string cg­server­ RECONFIG

address, either the IP address or FQDN. hostname

cg.port Central Governance server simple int 12553 RECONFIG

authentication port.

cg.ca_cert_id CA certificate identifier (stored in the string ­ ­

internal PKI base) used to authenticate
the Central Governance server.

cg.shared_ The shared secret needed to register to passwd ­1 RECONFIG

secret the Central Governance server.

cg.registration_ Registration identifier provided by int ­1 EXPERT

id Central Governance server. If set to ­1,
Transfer CFT tries to register with the
Central Governance server.

Registration completes with Transfer CFT appearing in the Central Governance product list.

Additional parameters
The following table lists additional Transfer CFT parameters related to Central Governance
connector.

Transfer CFT 3.1.3 Troubleshooting Guide 17

2 Troubleshoot the server

Parameter Description Type Default Flags

value

cg.mutual_auth_port Central Governance server int 12554 RECONFIG

mutual authentication port.
Automatically set during the
registration process.

cg.csr.business.id Internal identifier given by int ­1 EXPERT

the Central Governance MUTABLE
server when sending a READ_ONLY
Certificate Signing Request
for business exchanges.

cg.csr.governance.id Internal identifier given by int ­1 EXPERT

the Central Governance MUTABLE
server when sending a READ_ONLY
Certificate Signing Request
for governance exchanges.

cg.key_label Label used for license key string ­ EXPERIMENTAL

management.

cg.periodicity Notification interval in int 600 RECONFIG

seconds.

cg.proxy.in.host Proxy host used by Central string ­ RECONFIG

Governance to connect to
Transfer CFT.

cg.proxy.in.port Proxy port used by Central int ­ RECONFIG

Governance to connect to
Transfer CFT.

cg.proxy.in.login Proxy login used by Central string ­ RECONFIG

Governance to connect to
Transfer CFT.

cg.proxy.in.password Proxy password used by passwd ­ RECONFIG

Central Governance to
connect to Transfer CFT.

Transfer CFT 3.1.3 Troubleshooting Guide 18

2 Troubleshoot the server

Parameter Description Type Default Flags

value

cg.renewal_period Number of days prior to int 60 RECONFIG

expiration that the certificate
renewal procedure should
execute.

cg.timeout TCP connection timeout, in int 5 RECONFIG

seconds.

For more information on Central Governance, refer to the Central Governance 1.0.3 documentation.

Transfer CFT 3.1.3 Troubleshooting Guide 19

2 Troubleshoot the server

Install a certificate on the server

Note This procedure is only available when using the Local Administration version of Transfer
CFT.

The certificates used by the Copilot server to authenticate itself are defined in UCONF using the
parameters described in the following tables.

The examples provided in this section use sample certificates that are supplied in product. Do not
use these certificates in production; you should instead use your own certificates.

Example 1

This example uses a single PKCS#12 certificate.

Parameter Value

copilot.ssl.SslCertFile conf/pki/MFT_Demonstration_User_Certificate.p12

copilot.ssl.SslCertPassword Certificate password (“user” for the sample above)

copilot.ssl.SslKeyFile Not used

copilot.ssl.SslKeyPassword Not used

Example 2

This example uses a DER certificate with the private key in a separate DER file.

Parameter Value

copilot.ssl.SslCertFile conf/pki /MFT_Demonstration_User_Certificate.der

copilot.ssl.SslCertPassword Not used

copilot.ssl.SslKeyFile conf/pki /MFT_Demonstration_User_Certificatek.der

copilot.ssl.SslKeyPassword Key file password (no password with sample file above)

Transfer CFT 3.1.3 Troubleshooting Guide 20

2 Troubleshoot the server

Additional https parameters

There are two additional UCONF parameters to use for https connections:

Parameter Value

copilot.http.onlyssl l No: Default value.

l Yes: Restricts access to the Copilot server to HTTPS
secured connections only.

copilot.ssl.SslCipherSuites A comma separated list of cipher suites accepted by the

Copilot server.
l “47, 10, 9, 2”: Default value.

List of supported cipher suites:

l 1 = RSA_WITH_NULL_MD5
l 2 = RSA_WITH_NULL_SHA
l 4 = RSA_WITH_RC4_MD5
l 5 = RSA_WITH_RC4_SHA
l 9 = RSA_WITH_DES_CBC_SHA1
l 10 = RSA_WITH_3DES_EDE_CBC_SHA

l 47 = RSA_WITH_AES_128_CBC_SHA
l 53 = RSA_WITH_AES_256_CBC_SHA
l 59 = RSA_WITH_NULL_SHA256
l 60 = RSA_WITH_AES_128_CBC_SHA256
l 61 = RSA_WITH_AES_256_CBC_SHA256

Installing a certificate on the client side

Windows

On Windows, there are two ways to install a certificate on the client side: use the Windows
certificate, or the Java keystore.

UNIX

On Linux, the Java keystore is the only option.

Example

Transfer CFT 3.1.3 Troubleshooting Guide 21

2 Troubleshoot the server

In this section and the example below, we use the sample certificate delivered with Transfer CFT and
located at:

<CFTDIRRUNTIME>/conf/pki/Axway_MFT_Demonstration_Root_Certificate.der

Installing a certificate in the Windows keystore

1. In Windows Explorer, navigate to the certificate Axway_MFT_Demonstration_Root_
Certificate.der and right­click.
2. Select the “Install certificate” option.
3. Follow the screen instructions. Windows automatically imports the certificate into its keystore,
in the Intermediate certificate authorities folder.

Alternative method

1. In Internet Explorer, select Tools > Internet Options.

2. In the Content tab select the Certificate button.
3. Select Import, which starts the Certificate Import Wizard.
4. Click Next, and Browse to the Axway_MFT_Demonstration_Root_Certificate.der.
5. Follow the screen instructions. Windows imports the certificate into its keystore.

Installing a certificate in the Java keystore

The Java keystore is a file located at <installation directory>/jre/lib/security/cacerts. The default
password for this keystore is “changeit”.

Use the keytool command as follows to import the Axway_MFT_Demonstration_Root_Certificate.der

certificate into the Java keystore:

keytool –importcert
-trustcacerts
-alias AXWMFTCA
-file Axway_MFT_Demonstration_Root_Certificate.der
-storepass changeit-keystore <keystore>

Specify the keystore to use on the client side by customizing html files
The html files used by the Copilot server to be accessed by a browser are:

l runtime/wwwroot/admin.html
l runtime/wwwroot/index.html

These files contain a parameter SSL_KEYSTORE, which are modifiable. The default value for this
parameter is “Windows”, and the only other possible value is “” (empty string).

Transfer CFT 3.1.3 Troubleshooting Guide 22

2 Troubleshoot the server

The following table shows used keystore depending on the SSL_KEYSTORE value and operating
system.

SSL_KEYSTORE value Windows Linux

“Windows” Windows keystore Java keystore

“” (empty string) Java keystore Java keystore

Connect to Copilot through an SSL connection

Restart the Copilot server and your browser, and connect to the following URL:

https://<copilot_server_hostaddr>:<uconf:copilot.general.serverport>

Troubleshoot the runtime

Runtime issues can include the following for the server, Copilot, CFTUTIL and other system services:

l Abend
l Performance
l Start disk space, multi­node issues, restart
l Unexpected shut down, such as when the catalog is full

l System freezes or infinite looping

l Service pack issues (applying or removing), also for migrating issues, updates

Common causes
Issue Typical causes

Hard disk Catalog Network Memory or Corrupt

bottleneck full bottleneck processor file or
bottleneck* DB **

Performance Disk check Network Check

checks application

Start issue Disk check Catalog Network Time­out Check

check checks Transfer
CFT
files

Transfer CFT 3.1.3 Troubleshooting Guide 23

2 Troubleshoot the server

Issue Typical causes

Unexpected stop Disk check Catalog Network Check

check checks Transfer
CFT
files

Transfer freeze or Disk check Network Check Check

infinite looping checks application Transfer
CFT
files

SP and updates Disk check

Crash Disk check Network Check

checks Transfer
CFT
files

* Axway or third party software.

** Transfer CFT internal database.

Initial checks and actions

Disk check

l No space left on the device

o Free space
o Check Sentinel connectivity and verify the size of the runtime/data/trkapi.buf file, which may
be voluminous
l Check for problematic file transfers and output, and clean
l Check to see if traces are set, which may lead to multiple large files in the "run" directory
l Check to see if you have enabled dynamic catalog resizing

Catalog check
When the catalog is full Transfer CFT stops and you cannot restart it without a correction action to
reduce the size of the catalog. Note that this does not necessarily mean that the disk is full.

l See the Catalog houskeeping topic in the Transfer CFT 3.1.3 User Guide
l Backup your catalog and export the existing catalog

Export the full catalog

Transfer CFT 3.1.3 Troubleshooting Guide 24

2 Troubleshoot the server

Create a new catalog file configured for a greater number of records, and re­import the original
catalog file.

Use the command: cftmi

1. Export the full catalog as shown in the following example.

CFTMI migr type=cat,ifname=<catalog_file>,ofname=<export_catalog_

file>,direct=fromcat

2. Check that the exported file is not empty.

3. Create new catalog:

CFTUTIL Cftfile type=cat,fname=<new_catalog_file>,recnb=<number of

records>

4. Import the exported catalog file into the new catalog.

CFTMI migr type=cat,ifname=data/catasv,ofname=data/ cftcata-

new,direct=tocat

5. Move (rename) depending on your operating system:

Move cftcata cftcata-old (archive or erase the old, exported catalog)

Move cftcata-new cftcata (rename the new catalog)

Network checks
These corrective measures are often system dependent.

l Perform basic tests such as pinging the address, telnet (to check the port)

Check additional products

l Check if another product is consuming all of the CPU/memory
l Check Central Governance interoperability, such as the Sentinel database
l Scripts or end­of­transfer procedures may indirectly

Check Transfer CFT files

For each of the types of files, you can perform checks to see if the file is corrupted and, if necessary
contact Axway support for corrective actions.

Transfer CFT 3.1.3 Troubleshooting Guide 25

2 Troubleshoot the server

Reactivate an object
This topic describes the ACT command and its parameters. You can use the ACT command to
reactivate:

l Sentinel tracking objects

l CRON objects

The ACT command cannot be applied to a partners if its definition was provided or modified by a
directory EXIT.

You can choose to reactivate a single mode (requester or server) or both modes.

When the partner is reactivated, transfer requests that were suspended by the INACT command:

l Are restarted automatically in requester mode (diagnostics code 430)

l Must be restarted with the START command in all other cases

See the ACT command in the Transfer CFT 3.1.3 User Guide

Parameters

Parameter Description

ID Identifier for the object to be reactivated.

To reactivate several partners/jobs with a single command,
use wildcard characters or meta characters.

MODE Mode to be reactivated:

l BOTH
l REQUESTER
l SERVER

TYPE Object to reactivate:

l TRK
l CRON

Deactivate objects
This topic describes the INACT command and its parameters. The INACT command is used to
deactivate:

l Sentinel tracking object

l CRON object

Transfer CFT 3.1.3 Troubleshooting Guide 26

2 Troubleshoot the server

Note This command cannot be applied to partners whose definition was provided or modified by
a directory EXIT.

A partner that has been deactivated by the INACT command can only be reactivated using the ACT
command.

The INACT command also can:

l Interrupt transfers in progress

l Deactivate modes (requester or server)

When a partner is deactivated, transfers awaiting processing are:

l suspended in requester mode

l refused in server mode

The state of a transfer request awaiting execution in requester mode for a deactivated partner
remains D, with a diagnostic code 430 and a protocol diagnostic INACT.

The state of a transfer request awaiting execution in server mode for a deactivated partner remains
D, with a diagnostic code 930 and a protocol diagnostic RCO 312, or ABO 312 if the session is
already open.

The state of transfers that are interrupted by an INACT command when FORCE=YES is H, with a
diagnostic code 121 and a protocol diagnostic OPER.

See the INACT command in the Transfer CFT 3.1.3 User Guide

Parameters TYPE Object to be deactivated:

l TRK
l CRON

ID Identifier for the partners or jobs to be deactivated.

To deactivate several partners/jobs with a single command, use
wildcard characters or meta characters.

MODE Mode to be deactivated:

l BOTH
l REQUESTER
l SERVER
You can use the shortcuts B, R and S in place of the keywords.
The MODE parameter is absolute.

FORCE Stops any transfers in progress involving the deactivated partners.

Transfer CFT 3.1.3 Troubleshooting Guide 27

2 Troubleshoot the server

Query internal Transfer CFT components

This topic describes how to use the MQUERY command to query the various Transfer CFT
components.

You might use this command to check transfers that should have started but are blocked, check a
scheduled job that has not started, or to provide information when troubleshooting performance
issues as shown in the examples below.

The MQUERY command sends the requested internal information to display in the log.

Syntax
OBJECT = CACHE or SYSTEM

[ OBJECT = { CACHE | SYSTEM | STATS | PROBE } ]

[ CMD = { string }]

[ CONTENT = { BRIEF | FULL | STAT } ]

[ NAME = { CAT | COMMAND | CRON | STAT } ]

OBJECT = STATS or PROBE

[ OBJECT = { CACHE | SYSTEM | STATS | PROBE } ]

[ CMD = { string }]

[ CONTENT = { XMLBRIEF | XMLFULL | RAW } ]

[ NAME = { CAT | COMMAND | CRON | STAT } ]

Parameter Description

OBJECT Options: CACHE | SYSTEM | STATS |

PROBE

NAME The options available for the NAME depend on the type of OBJECT to be
queried.
If the object = cache (default) then the name can be set to:
l CAT: Query of the catalog cache
l COMMAND: Query of the command cache
l CRON: Query the Transfer CFT CRON cache

CONTENT If OBJECT=CACHE then you can select from the following values:
BRIEF| FULL | STAT ­ or ­ XMLBRIEF| XMLFULL | RAW

Transfer CFT 3.1.3 Troubleshooting Guide 28

2 Troubleshoot the server

Examples

Querying the catalog cache

Use this command to check that transfers are not blocked by, for example, a time_locked or
partner_locked issues.

MQUERY NAME=CAT,CONTENT=FULL
listlog
=========================== TRANSFERS
======================================
pri minTime minDate reqTime reqDate cat_blk part
=======================================================================
=====
Transfers_Non_Ready : 0
Transfers_Ready : 0 ( 0 Partners )
Transfers_Time__Locked : 2 ( 1 Partners )
128 11:49:12 TODAY 11:49:12 TODAY 1780 PART1
128 11:49:14 TODAY 11:49:31 TODAY 1781 PART1
Transfers_State_Locked : 0 ( 0 Partners )
======================== PARTNERS =====================================
name count state locked diag diagp minTime minDate
=======================================================================
Partners : 1
PART1 2 TLCK 2 302 L 02 045 11:55:38 TODAY
Partners_Ready : 0
Partners_Time__Locked : 1
PART1 2 TLCK 2 302 L 02 045 11:55:38 TODAY
Partners_State_Locked : 0
MQUERY Treated for USER AXWAY\ls

Querying the command cache

Check scheduled internal commands, more specifically the switch and purge commands such as
checking the time that the activity occurs.

MQUERY NAME=COMMAND,CONTENT=FULL
listlog
CFTI24I *** 3 COMMAND(S) INTO CACHE
CFTI24I *** DATE=28/01/2013 TIME= 18:48:00.00 SWITCH LOG
CFTI24I *** DATE=29/01/2013 TIME= 00:05:00.00 PURGE
CFTI24I *** DATE=29/01/2013 TIME= 10:57:00.00 SWITCH ACCNT -

Transfer CFT 3.1.3 Troubleshooting Guide 29

2 Troubleshoot the server

CFTR12I MQUERY Treated for USER userid

Displaying internal technical statistics for advanced diagnostic

purposes
You can use this command when troubleshooting issues, and provide this output when contacting
Axway support. One example is if you encounter an issue with memory usage.

MQUERY OBJECT=STATS

Output raw data to troubleshoot performance

This command provides statistical information, for example to troubleshoot performance issues,
when contacting Axway support.

MQUERY OBJECT=PROBE, CONTENT=RAW

Display product information

Use the ABOUT command

Use the ABOUT command to display the Transfer CFT product, host, and key information. This
command displays the characteristics of the platform on which Transfer CFT is installed.

Syntax

[ COMMENT = string ]

[ TYPE = { ALL | HOST | CFT } ]

Parameters

Parameter Description

COMMENT Free comment.

This comment is displayed and can be used to indicate a specific
item of information, such as the customer name.
This information is then used to determine a software license
key.

Example

This command displays the following type of information:

Transfer CFT 3.1.3 Troubleshooting Guide 30

2 Troubleshoot the server

CFTU20I
CFTU20I CFT Windows
CFTU20I Version 3.1.2 20140423
CFTU20I (C) Copyright AXWAY 1989-2014
CFTU20I ====> Starting Session on 28/04/2014 Time is 18:54:31
CFTU20I Parameters file :C:\AxwayCFT312\Transfer_
CFT\runtime\data\cftparm
CFTU20I Partners file :C:\AxwayCFT312\Transfer_CFT\runtime\data\cftpart
CFTU20I Catalog file :C:\AxwayCFT312\Transfer_CFT\runtime\data\cftcata
CFTU20I
CFT information :
* product = CFT Windows
* version = 3.1.2
* level = SP1
* upgrade = 7595
* target = win-x86-64
Host information :
* model =
* hostname = MACH-A10229
* sysname = Windows
* machine = AMT_X8664
* version = 6.1.7601
* release = Seven Service Pack 1
* distrib =
Axway information :
* product = Axway Transfer CFT
* version = 3.1.2_SP1.0
* applied-patches =
* forbidden-patches =
Key information :
* idparm = IDPARM0
* key = Lxxxxxxxxxxxxxxxxxxxxxxxxxx588S
* CI97S
* type = DATE
* expire = 2015/04/14
* sysname = win-x86-64
* Nb Transfers = 999
* Nb CPU = 2
* Nb Partners = Max
* Nb EBICS partners = Not authorized
* In/Out Bandwidth = Unlimited

Transfer CFT 3.1.3 Troubleshooting Guide 31

2 Troubleshoot the server

* In/Out Transfer activation = Unlimited

* Edition =
* Options = BWP CLU FIP ACC ODT CLP CLP XSR SSL SSL
* XTF WBS
CFTU00I ABOUT _ Correct ()

C:\projects>cfttell target
win-x86-32

C:\projects>cfttell version
3000

Extract data
You can use the CFTEXT object to extract Parameter and Partner file data. CFTEXT generates, as
output, a configuration command text used to reconstitute the data of these files.

The resulting configuration file is then submitted to CFTUTIL to:

l Rebuild a lost or damaged configuration

l Facilitate the exporting of a Transfer CFT configuration to another computer

l Upgrade the Transfer CFT software when such an upgrade incorporates a file structure
modification

The configuration command text generated is written to the CFTUTIL output medium. To recover a
CFTUTIL output, you can either redirect the standard output or else redefine the output medium via
the command CONFIG TYPE = OUTPUT.

All parameter values are in UPPER CASE letters.

See the INACT command in the Transfer CFT3.1.3User Guide

Description Use this command to extract all or part of the data from the parameter
and partner files.

Transfer CFT 3.1.3 Troubleshooting Guide 32

2 Troubleshoot the server

Parameters ID Identifier of the parameter to be extracted.

The value of this identifier is the value of the
ID of the command CFTxxxx corresponding
to the TYPE parameter; this allows the
extraction to be limited:
l To an explicitly indicated value (identifier)
l Or to a group of values designated through
the use of a mask using "wildcard"
characters
When this parameter is not defined, all the
occurrences of the parameter type (defined
by TYPE) are extracted.

FOUT Name of the file to which the command’s

standard output will be redirected.
This generated file can then be interpreted
directly by CFTUTIL.
When this parameter is not filled, all
occurrences of the type parameter (defined in
the TYPE parameter) are extracted.

FPARM Name of the Parameter input file.

{see the comment | Default value: default name of the Parameter
filename} file defined for CFTUTIL for the system
Except for TYPE = concerned. Refer to the Transfer CFT
PART Operations Guide that corresponds with your
OS.

FPART Name of the Partner input file.

{see the comment | Default value: default name of the Partner file
filename}] defined for CFTUTIL for the system
For TYPE = {ALL | concerned. Refer to the Transfer CFT
PART} Operations Guide that corresponds with your
OS.

TYPE This parameter defines the parameter type to

be extracted.

Transfer CFT 3.1.3 Troubleshooting Guide 33

2 Troubleshoot the server

Example 1

CFTEXT

Extraction of all data from the CFTPARM parameter and CFTPART partner files.
Example 2

CFTEXT TYPE = SEND,

ID = FACT,
FPARM = mycftparm

Extraction of data concerning the model file to be sent (CFTSEND command) with an IDF =
FACT, from the file mycftparm.
Example 3

CFTEXT TYPE = RECV,

ID = FACT*

Extraction of the data concerning the model files to be received (CFTRECV command) whose
IDF value begins with the four letters "FACT". The name of the Parameter file is the default
name indicated. Refer to the Transfer CFT Operations Guide that corresponds with your OS.
Example 4

CFTEXT TYPE = PART,

ID = MAGA*

Extraction of the partner data corresponding to the CFTPART commands, the identifier of
which begins with the four letters "MAGA". The Partner file name is the default name
indicated. Refer to the Transfer CFT Operations Guide that corresponds with your OS.
Example 5
Transfer CFT application definitions

CFTEXT TYPE = APPL,

Rebuild the runtime

This section describes how to rebuild the unified configuration environment.

You may need to use this process, after accidentally erasing critical files, to deal with corrupted files,
or after a disk failure.

Transfer CFT 3.1.3 Troubleshooting Guide 34

2 Troubleshoot the server

Create or regenerate runtime uconf environment

UNIX and Windows only

Syntax

cftruntime <cft­install­dir> <cft­runtime­dir> [­profile|­n <name>|­uconf|­inst]

Where:

l cft­install­dir: Is the full Transfer CFT install path and must exist.
l cft­runtime­dir: Is the full Transfer CFT runtime path and does not exist.

Usage:

l ­profile: Creates a new profile.bat/sh and backs up the old one.

l ­name: Creates a new profile with the <name> of your choice.
l ­uconf: Regenerate the uconf file.
l ­inst: Creates the initial runtime environment, which is used exclusively by the Installer.

Note You must use double quotes when indicating a path that contains spaces.

Example 1

In a Windows environment, regenerate the cftuconf.dat uconf file as follows:

cftruntime c:\AxwayCFT31X \Transfer_CFT\home c:\AxwayCFT31X

\Transfer_CFT\runtime –uconf

Example 2

In a Windows environment, create a new runtime called runtime2:

cftruntime c:\AxwayCFT31X \Transfer_CFT\home c:\AxwayCFT31X

\Transfer_CFT\runtime2

Delete a command in the COM file

This topic describes the CLEARCMD. Use this command to delete a transfer request from the
communication file. It generates a WLOG command that reports the event in the LOG file.

Description Deletes a transfer request from the communication file.

Transfer CFT 3.1.3 Troubleshooting Guide 35

2 Troubleshoot the server

Parameters COMMAND Request keyword.

INDEX Request number as displayed by the LISTCOM

command.

JOBNAME Jobname (string 15).

USERID Identifier of the request owner.

Delete a single command

To use CLEARCMD to delete a single command, the USERID, INDEX, and COMMAND parameters are
mandatory.

Example

Begin by running the LISTCOM command.

cftutil listcom
RECORDS
RECORD N 1 ACTIVE : YES
COMMAND-TYPE : SEND USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=bclpm,idf=un,fname=cc,mintime=+1

Enter the CLEARCMD command.

cftutil clearcmd userid=AXWAY\Manager,command=send,index=1

Repeat the LISTCOM command, and the example below displays the results (note the record is now
set to CLEARED).

cftutil listcom
RECORD N 1 ACTIVE : CLEARED
COMMAND-TYPE : SEND USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=bclpm,idf=un,fname=cc,mintime=+1
RECORD N 6 ACTIVE : YES
COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :

Transfer CFT 3.1.3 Troubleshooting Guide 36

2 Troubleshoot the server

JOBNAME : 10204
COMMANDE :
MSG='CLEARCMD Command=SEND, Userid=AXWAY\Manager, Index=1 _ Command O
K'

Delete a group of commands

To delete a group of commands use the following syntax.

To delete all commands=cmd for this userid:

INDEX=*,COMMAND= cmd,USERID=userid

To delete all commands for this jobname and this userid:

INDEX=*,JOBNAME= job,USERID=userid

To delete all commands=cmd for this jobname and this userid:

INDEX=*,JOBNAME= job,COMMAND=cmd ,USERID=userid

Example

To delete all RECV commands that have the JOBNAME 9168 for the Axway/Manager account user
begin by executing the LISTCOM command.

cftutil listcom
RECORD N 3 ACTIVE : YES
COMMAND-TYPE : RECV USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=loop,idf=*
RECORD N 4 ACTIVE : YES
COMMAND-TYPE : RECV USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=pesit1,idf=*

Enter the CLEARCMD command.

cftutil clearcmd userid=AXWAY\Manager,command=recv,index=*,jobname=9168

Transfer CFT 3.1.3 Troubleshooting Guide 37

2 Troubleshoot the server

Run LISTCOM; the selected records now display as CLEARED.

cftutil listcom
RECORD N 3 ACTIVE : CLEARED
COMMAND-TYPE : RECV USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=loop,idf=*

RECORD N 4 ACTIVE : CLEARED

COMMAND-TYPE : RECV USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9168
COMMANDE :
part=pesit1,idf=*

The following screen shows the WLOGs that correspond to the 2 deleted RECV commands.

RECORD N 7 ACTIVE : YES

COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9088
COMMANDE :
MSG='CLEARCMD Command=RECV,Jobname=9168, Userid=AXWAY\Manager, Index=
3 _ Command OK'

RECORD N 8 ACTIVE : YES

COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :
JOBNAME : 9088
COMMANDE :
MSG='CLEARCMD Command=RECV,Jobname=9168, Userid=AXWAY\Manager, Index=
4 _ Command OK'

Syntax error
The following is a list of error and information messages that display if there are no WLOG transfers
in CFTCOM.

Error 1

CFTU26E CLEARCMD _ Error (Index value not authorized_ Bad command)

Transfer CFT 3.1.3 Troubleshooting Guide 38

2 Troubleshoot the server

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,index=4*,command=recv)

Error 2

CFTU26E CLEARCMD _ Error (COMMAND Keyword missing)

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,index=4,jobname=1234)

Error 3

CFTU26E CLEARCMD _ Error (COMMAND or JOBNAME Keyword missing)

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,index=*)

Error 4

CFTU26E CLEARCMD _ Error (WLOG not authorized_ Bad command)

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,index=*,command=wlog)

Error 5

CFTU26E CLEARCMD _ Error (COMMAND or JOBNAME Keyword missing)

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,index=*)

Execution errors
The following is a list of error and information messages that display if there is an error when
executing the WLOG transfers in CFTCOM.

Error 1

CFTU26E CLEARCMD _ Error ( Bad userid)

CFTU00I CLEARCMD _ Failed (userid=XXXXY\Manager,command=send,index=2)

Error 2

CFTU26E CLEARCMD _ Error ( Communication media record not found)

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,command=send,index=99)

Error 3

CFTU26E CLEARCMD _ Error ( Bad command)

Transfer CFT 3.1.3 Troubleshooting Guide 39

2 Troubleshoot the server

CFTU00I CLEARCMD _ Failed (userid=AXWAY\Manager,command=halt,index=2)

Example

The following examples show the LISTCOM messages after three erroneous CLEARCMD commands.

RECORD N 10 ACTIVE : YES

COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :
JOBNAME : 10188
COMMANDE :
MSG='CLEARCMD Command=SEND, Userid=XXXXY\Manager, Index=2 _ Bad userid'

RECORD N 11 ACTIVE : YES

COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :
JOBNAME : 11780
COMMANDE :
MSG='CLEARCMD Command=SEND, Userid=AXWAY\Manager, Index=99 _
Communication media record not found'

RECORD N 12 ACTIVE : YES

COMMAND-TYPE : WLOG USERID : AXWAY\Manager
GROUPID :
JOBNAME : 4196
COMMANDE :
MSG='CLEARCMD Command=HALT, Userid=AXWAY\Manager, Index=2 _ Bad
command'

Suspend a transfer when offline

This topic describes the KSTATE command. The KSTATE command is used to suspend a transfer in
the catalog when the Transfer CFT is offline. Transfer CFT must be shut down before the command
is run and then restarted. The transfer must exist in the catalog and be in one of the following
phasesteps: in process C, available D, or hold H. After execution of the command, the phasestep is
set to K.

The command generates a WLOG command which reports the event in the LOG file.

Description Suspends a transfer in the catalog.

Transfer CFT 3.1.3 Troubleshooting Guide 40

2 Troubleshoot the server

Parameters IDF Model file identifier.

IDTU Local transfer counter identifier.

PART Identifier of the partner.

(Mandatory)

Manually create Transfer CFT internal

datafile files
The CFTFILE command is used to create, replace, or delete Transfer CFT files. These initial files
define the most basic parameters for the Transfer CFT. You can further define the Transfer CFT
settings after the initial startup, but the Transfer CFT must at least have this CFTFILE as a minimum
configuration.

You can only create the initial environment in the CFTUTIL command line interface. You must create
all files that are handled by the Transfer CFT. After creating a basic CFTFILE, you can execute the
profile file, and continue either in command line or use the GUI Configuration Wizard.

About the CFTFILE command

The CFTFILE command affects the following files:

l PARAMETER ­ containing the Transfer CFT general parameters where TYPE = PARM
l PARTNER ­ containing the descriptions of the characteristics of partners where TYPE = PART
l CATALOG ­ containing the control information associated with transfers where TYPE = CAT
l STATISTICS ­ containing the information relative to terminated transfers where TYPE = ACCNT
l LOG ­ used to record messages associated with the execution of transfers and CFT operations
where TYPE = LOG
l COMMUNICATION ­ used to enter transfer requests and Transfer CFT management comm, ands
where TYPE = COM

To delete a Transfer CFT file, MODE = DELETE, you must declare the parameters FNAME, the name
of the file to be deleted, and TYPE, the type of the file to be deleted.

OS Description

OS400 The CFTFILE command is incorporated in Transfer CFT OS/400 Manager. It can,
however, be activated directly in the log file switching procedures. See the example
supplied in the B_EXECLOG member.

You can use the CFTCATAL utility to resize the catalog. In a multi­node environment, this action
resizes all nodes.

Transfer CFT 3.1.3 Troubleshooting Guide 41

2 Troubleshoot the server

Use the CFTFILE command to create (MODE = CREATE) empty or delete (MODE = DELETE) Transfer
CFT files.

Syntax

CFTFILE { PARM | PART }

TYPE = { PARM | PART }

FNAME = filename

[ HABFNAME = filename ]

[ CIPHER = { NO | YES } ]

[ FBLKSIZE = { 0 |n } ]

[ FSPACE = n ]

[ FSPACEX = n ]

[ MAC = { NO | YES } ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE } ]

CFTFILE { CAT | COM }

TYPE = { CAT | COM }

FNAME = filename

[ RECNB = n ]

[ CIPHER = { NO | YES } ]

[ FBLKSIZE = { 0 |n } ]

[ FSPACE = { 0 | n } ]

[ FSPACEX = { 0 | n } ]

[ HABFNAME = filename ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE} ]

CFTFILE { ACCNT | LOG }

TYPE = { ACCNT | LOG }

FNAME = filename

[ FBLKSIZE = 0 | n ]

[ FSPACE = 0 |n ]

Transfer CFT 3.1.3 Troubleshooting Guide 42

2 Troubleshoot the server

[ FSPACEX = 0 |n ]

[ MODE = { CREATE | REPLACE | DELETE | ERASE } ]

Parameter Description

CIPHER File cipher request.

FBLKSIZE Defines the block size of the file to be created (in bytes).
According to TYPE/OS

FNAME Name of the file the command applies to.

FSPACE Primary allocation of the file to be created, expressed in K bytes

According to TYPE/OS (1024).

FSPACEX Secondary allocation of the file to be created, expressed in K

bytes (1024).

HABFNAME Name of the security system initialization file.

LOCK Name of the lock file created in parallel with the

TYPE communication file and used to manage file access conflicts.

MAC File authentication request.

MODE Action requested on the file.

RECNB Number of records in the file.

TYPE = {COM | CAT}

TYPE = {ACCNT | CAT | COM Type of file concerned by the command.

| LOG | PARM | PART} When TYPE = CAT, COM, PARM or PART, you can use the
HABFNAME parameter for security.

Example

The following command creates a parameter file.

CFTFILE TYPE = PARM,

MODE = CREATE,
FNAME = filename

Transfer CFT 3.1.3 Troubleshooting Guide 43

2 Troubleshoot the server

How to use ATM traces

This section describes ATM traces and how to implement.

Note ATM traces are only available when using the Local Administration version of Transfer CFT.
We recommend using Central Governance to manage Transfer CFT.

Topic Description

Trace Describes the concepts behind performing an ATM trace in Transfer CFT.
management
concepts

Managing trace This topic describes how to begin and end the information collecting
information process.
collection

Trace Presents parameter setting commands, grouped by function.

commands
overview

Defining trace Describes the Transfer CFT general parameter for a trace.
in Transfer CFT
parameters

Initializing the Defines and describes a trace file which can be available to store
trace captured information and associates an identifier with this file and
description.

Configuring the Describes how to configure the Transfer CFT communication medium so
trace that you can write trace commands in the communication medium.
communication
medium

Defining a trace Describes how to create a trace file, to destroy it or to reinitialize it with
file externally an empty useable content.

Defining the Describes how to create a trace when Transfer CFT starts up, with the
internal trace possibility of tracing an initialization sequence, or during Transfer CFT
file operations.

Transfer CFT 3.1.3 Troubleshooting Guide 44

2 Troubleshoot the server

Topic Description

Using the start Describes the start trace command, which is associated with a unique
trace command identifier, defines and describes the conditions for starting and selecting
traced data, and associates a file identifier.

Using the stop Describes the stop trace command, which defines the conditions for
trace command stopping a trace.

About Transfer CFT traces

Transfer CFT traces are managed by the Advanced Trace Manager (ATM) component.

ATM is a problem resolution assistance tool that is used:

l To save the information exchanged at the monitor level, in one or more dedicated files

The information traced relates to protocol information (exchanges between Transfer CFT and its
remote partners) and/or Transfer CFT internal information (exchanges between Transfer CFT internal
components or between Transfer CFT tasks).

l To retrieve and interpret previously saved information, through an off­line analysis program

Users are only concerned by ATM in that they may need to initiate tracing, at the request of the
Transfer CFT Support service. The Transfer CFT Support service is then responsible for analyzing
traces. The topic Transfer CFT Traces Information Collection contains a description of the trace
commands.

The following section introduces the concepts surrounding the trace mechanism and how this
works in Transfer CFT.

Trace management concepts

About trace management

ATM trace management is comprised of two stages:

l Information collection, or trace acquisition in Transfer CFT, with records in one or more trace
files
l Examination of this information, outside Transfer CFT, at a later date or time

Only the information collection stage is covered in this section. Examination of information, which
Transfer CFT support staff carry out, is performed using trace files.

The following paragraphs describe:

l How to start trace acquisition, either before starting up Transfer CFT or during operations
l How to synchronize data collection with application events linked to transfers

Transfer CFT 3.1.3 Troubleshooting Guide 45

2 Troubleshoot the server

Collecting information
The implementation of traces in Transfer CFT involves three types of operations:

l Configuring the communication medium

l Defining the trace files
l Controlling collection: activation/shutdown, closing files, shutdown of the process

Configuring the ATM communication medium

The CONFIG command is required to:

l Initially define the communication medium with which the utility will function
l Redefine this medium during operations, if necessary

This communication medium can be the same as that defined for CFTUTIL.

Depending on the systems it can be either a file or a mailbox.

Defining trace files

One or more trace acquisition processes can be activated in Transfer CFT, to supply one or more
trace files.

To do this, the description of the trace file must be given to Transfer CFT, either:

l In the CFTUTIL parameter settings, using a CFTTRACE command which is taken into account
when Transfer CFT is started
l Or dynamically, using a SETTRC command, sent to the Transfer CFT communication medium
during its operations. The SETTRC command can be made before Transfer CFT is started, if the
communication medium is a file

The word process is not used here as a synonym for task. There is at most one task dedicated to
trace acquisition in Transfer CFT.
In general, when a CFTTRACE or SETTRC command is taken into account, this is accompanied by
the physical creation and initialization of the corresponding trace file. In some environments,
especially on mainframe platforms, this operation must be carried out in advance, using a TRCFILE
TYPE=TRACE command.

This command is also used to define a direct file.

For more information, refer to the specific documentation or the examples supplied with the
Transfer CFT products.

The CFTTRACE parameter settings command initializes a trace acquisition process and provides it
with operating parameters.

Depending on the value of this command’s START parameter, trace acquisition starts:

l As soon as Transfer CFT is started

l When a start trace command (STARTTRC) is entered

Transfer CFT 3.1.3 Troubleshooting Guide 46

2 Troubleshoot the server

During Transfer CFT operations, only the CFTTRACE command referenced by the CFTPARM
command’s TRACE parameter is taken into account:

CFTPARM ..., TRACE=identifier, ....

CFTTRACE ID=identifier, ...

Conversely, during Transfer CFT operations, several SETTRC commands can be taken into account.
However, after a SETTRC command, a STARTTRC command must always be entered. This command
provides Transfer CFT with the additional parameters to control and actually trigger trace
acquisition.

Note The CFTTRACE and SETTRC commands provide Transfer CFT with operating and trace
acquisition parameters. The term ‘‘trace vector" will therefore be used to represent these
items overall in the rest of the document.

Filtering traces by partner

This function enables you to filter FPDU protocol traces by partner.

Example

CFTTRACE STARTTRC ID=ID,TID=TID,PTRACE=16,FILTER=Part

The command to start a trace FPDU (PTRACE=16) only applies to thePart partner. When you start a
Trace, a new message is written in the LOG File with a CFTT57 message:

CFTT92I IDTU=&idtu CTX=&ctx IDT=&idt

Managing trace information collection

How to start and stop the information collection process

This topic describes how to begin and end the information collecting process.

Starting the information collection

To start information collection:

1. When Transfer CFT starts up, the user enters the CFTTRACE START parameter (START=CFT).
2. During Transfer CFT operations, the user enters a STARTTRC command.

Information collection is managed by a trace server task, which makes it possible to resolve trace file
access conflict problems. Serialization is ensured by an internal flag setting mechanism, which
enables message exchanges and synchronization of Transfer CFT tasks.

The collection operation does not pre­empt or significantly disturb other Transfer CFT mechanisms.

Consequently, if there is a bottleneck in the flag mechanism (if the volume of traces requested
exceeds flagging capabilities or system resources), messages are purely and simply lost.

Trace mechanisms include the following features:

Transfer CFT 3.1.3 Troubleshooting Guide 47

2 Troubleshoot the server

1. You can make traces started at the same time as Transfer CFT ‘co­exist with other traces, triggered during
Transfer CFT operations, for the same trace file or for different trace files
2. You can create a trace file with the CFTTRACE command, without having to synchronize collection with
Transfer CFT start­up. To do this, set the START parameter to DELAYED
3. If a STARTTRC command is entered before the corresponding file has been defined, it is simply rejected
and is without effect
4. Whether there are one or more CFTTRACE commands, a single task ensures that all the trace files are filled

Stopping the collection process

To stop collection, enter the command: STOPTRC.
The command is transmitted to Transfer CFT, which immediately shuts down information collection
defined for this trace and destroys the corresponding vector.

Note that:

l The process can be restarted with STARTTRC; it is possible to use new initialization parameters.
l If the same information is requested in several different traces and only one of these traces is shutdown,
then the information will still be traced (according to the definitions of the other traces still active).

Stopping the trace process

To close a trace file, and shutdown the process, enter the SETTRC MODE=DELETE command.

Transfer CFT processes the command as follows:

1. All traces with output to the file in question are shutdown immediately.
2. The trace file entry is deleted by the ATM manager.

The ATM component’s server task shutdowns as soon as there are no more trace files to manage,
that is, that there are no more active trace acquisition processes.

When Transfer CFT shuts down (SHUT), all the trace files are closed and the server task shuts down.

Trace commands

Trace parameter setting commands

Parameter setting commands, grouped by function, are presented in the following table.

Action Command From

Up­date the general parameters before Transfer CFT start­up CFTPARM CFTUTIL

Transfer CFT 3.1.3 Troubleshooting Guide 48

2 Troubleshoot the server

Action Command From

Define the trace file or files: CFTTRACE CFTUTIL

or TRCFILE CFTTRACE
l before Transfer CFT starts
l during Transfer CFT operations
SETTRC CFTTRACE

Start information collection:

l Transfer CFT start CFTTRACE CFTUTIL

l during Transfer CFT operations

STARTTRC CFTTRACE

Stop information collection STOPTRC CFTTRACE

Close files and shut down the process SETTRC CFTTRACE

Trace command overview

The following tables are an example of the commands and parameters to be used for the various
trace processes.

Defining the communication medium

Action Command Parameter Description

Define or redefine CONFIG FNAME The name of the file or mailbox

the communication medium

Defining trace files

Trace file Command Parameter Description

definition

Before starting CFTPARM TRACE=identifier CFTTRACE command

Transfer CFT identifier

CFTTRACE

or TRCFILE TYPE=TRACE The defined file is a trace

(1) file

During Transfer CFT SETTRC MODE=CREATE or

operations MODIFY

(1): TRCFILE is used in environments which do not allow dynamic file definition.

Transfer CFT 3.1.3 Troubleshooting Guide 49

2 Troubleshoot the server

Starting information collection

Starting information Command used to Parameter Command to

collection define the file enter

When starting up CFTTRACE START=CFT

Transfer CFT

TRCFILE (1) START=CFT CFTTRACE

During Transfer CFT CFTTRACE START=DELAYED STARTTRC

operations

SETTRC STARTTRC

(1): TRCFILE is used in environments which do not allow dynamic file definition.

Stopping collection - close the file and shutdown the process

Action Define the file Enter the

with command

Stop information collection CFTTRACE STOPTRC

SETTR STOPTRC

Stop collection, close the files and shutdown the CFTTRACE STOPTRC
process and
SETTRC
MODE=DELETE

SETTRC SETTRC
MODE=DELETE

Defining a trace

Defining the trace in CFTPARM

By filling in the TRACE parameter, the user prompts the loading of the trace items described below in
the CFTTRACE command when Transfer CFT is started. The other command parameters are not
covered in this topic.

Syntax
CFTPARM [TRACE = identifier]

Transfer CFT 3.1.3 Troubleshooting Guide 50

2 Troubleshoot the server

Parameters
[TRACE = identifier]

Indicates the presence and the identifier of an initial trace description, to be taken into account at
Transfer CFT start­up.

Character string, maximum length: 8; default value: " ".

Initializing the trace

Overview SETTRC
This command:

l Defines and describes a trace file which can be available to store captured information
l Associates an identifier with this file and description, which allows it to be identified uniquely, if
the user wishes to distribute several trace types into several different files

Syntax
SETTRC ID = identifier,
TRCFNAM = {" " | filename},
[TRCFTYP = {STANDARD | CIRCULAR},
[MODE = {CREATE | REPLACE | CLOSE},]

TRCFTYP = STANDARD
[TRCLREC = {0 | n}]

TRCFTYP = CIRCULAR
TRCLREC = {0 | n},
TRCNREC = n

Parameters
[ID = identifier]

Character string, maximum length: 8; uniquely identifies the trace file descriptor defined by this set
of parameters.

[MODE = {CREATE | REPLACE | CLOSE}]

Operation to be performed on the ‘‘trace file" entry designated by the ID

parameter:

l CREATE: Create an entry, and possibly the file

l REPLACE: Replace the file with another one for the same entry

Transfer CFT 3.1.3 Troubleshooting Guide 51

2 Troubleshoot the server

l CLOSE: Delete an entry, the file will then be closed

Where MODE = CLOSE, only the ID parameter is useful.

TRCFNAM = {" " | filename}

Name of trace file to be fed by traces.

Character string maximum length: 64 characters.

[TRCFTYP = {STANDARD | CIRCULAR}]

Trace file type:

l STANDARD: Sequential file written in "extend".

The new records are written after the old ones
l CIRCULAR: Direct access file, with a set number of fixed­length records.
This file is accessed through a circular up­date, the new records overwriting the old ones
[TRCLREC = {0 | n}]

Length of trace file’s physical records.

This parameter is:

l Mandatory if TRCFTYP = CIRCULAR.

Concatenation and segmentation algorithms make it possible to manage the real ­ essentially
variable ­ size of data to be written to this file
l Optional if TRCFTYP = STANDARD (sequential file, with fixed­size records)
[TRCNREC = n]

Number of trace file records.

This parameter is:

l Mandatory if TRCFTYP = CIRCULAR

l Not applicable if TRCFTYP = STANDARD

Configuring the trace communication

medium

About the trace CONFIG command

To write trace commands in the Transfer CFT communication medium, the medium must be
configured.

Transfer CFT 3.1.3 Troubleshooting Guide 52

2 Troubleshoot the server

Syntax
CONFIG TYPE = COM,
FNAME = {filename | string},
MEDIACOM = {FILE | MBX}

Parameters
FNAME = {filename | string}

Name of the file ( filename) or of the mailbox ( string ).

MEDIACOM = {FILE | MBX}

Type of communication medium, if the medium is appropriate for the system:

l FILE: Communication by file

l MBX: Communication by mailbox
TYPE = COM

Medium type.

Defining a trace file externally

About the TRCFILE command

Trace files can be created and pre­formatted in their order of occurrence or externally with a utility,
in particular for environments that cannot support such operations. The utility is integrated in
CFTTRACE, with the command TRCFILE TYPE = TRACE.

Use this command to create a trace file, to destroy it or to reinitialize it with an empty useable
content.

Syntax
TRCFILE TYPE = TRACE,
[MODE = {CREATE | REPLACE | DELETE},]
TRCFNAM = filename,
TRCFTYP = {STANDARD | CIRCULAR},

TRCFTYP = STANDARD
[TRCLREC = {1024 | n}]

TRCFTYP = CIRCULAR
TRCNREC = n,
TRCLREC = {0 | 1024 | n}

Transfer CFT 3.1.3 Troubleshooting Guide 53

2 Troubleshoot the server

Parameters
[MODE = {CREATE | REPLACE | DELETE},]

Type of operation to be carried out on the file:

l CREATE: Create and initialize a trace file that does not yet exist.
If the file already exists, this operation is refused
l REPLACE: Reinitialize an existing trace file.
If the file does not already exist, it is created
l DELETE: Delete a trace file
TRCFNAM = filename

Name of the trace file.

TRCFTYP = {STANDARD | CIRCULAR}

Type of trace file for which an operation is requested:

l STANDARD: Sequential file (fixed record size)

l CIRCULAR: Direct file (fixed record size)
[TRCLREC = {0 | 1024 | n}]

Size of records contained in the trace file.

This parameter is:

l Mandatory when TRCFTYP = CIRCULAR, with a default value of 0

l Optional when TRCFTYP = STANDARD with a default value of 1024
[TRCNREC = n]

Number of useable records contained in the direct file.

This parameter is:

l Mandatory when TRCFTYP = CIRCULAR

l Not applicable when TRCFTYP = STANDARD
TYPE = TRACE

Operation on a trace file.

Defining the internal trace file

About the CFTTRACE command

Depending on how the trace is started, the file defined is available:

Transfer CFT 3.1.3 Troubleshooting Guide 54

2 Troubleshoot the server

l When Transfer CFT starts up, with the possibility of tracing an initialization sequence
l During Transfer CFT operations

Syntax

CFTTRACE [FTRACE = {0 | 0..15},]

[MTRACE = {0 | 0..31},]
[PTRACE = {0 | 0..31},]
[XTRACE = {0 | 0..7},]
[S2TRACE = {0 | 0..255},]
[S3TRACE = {0 | 0..255},]
[N2TRACE = {0 | 0..63},]
[N3TRACE = {0 | 0..255},]
ID = identifier,
[TRCFNAM = " " | filename,]
[TRCFTYP = {STANDARD | CIRCULAR},]
[TRCLREC = n,]
[TRCNREC = n,]
[MODE = {CREATE | REPLACE | DELETE},]
START = {CFT | DELAYED}

Parameters
[FTRACE = {0 | 0..15}]

Checks the level 1 traces for Transfer CFT file tasks (CFTTFIL).

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: transfer controller trace

l 2: security controller trace
l 4: file access controller trace
l 8: trace of flagged messages

ID = identifier

Character string, maximum length: 8; uniquely identifies the trace file defined by the set of
parameters TRCFNAM, TRCFTYP, TRCLREC, TRCNREC.

[MODE = {CREATE | REPLACE | DELETE},]

Operation to be performed on the ‘‘trace file" entry designated by the ID parameter:

l CREATE: Create an entry

l REPLACE: Replace an entry
l DELETE: Delete an entry

Transfer CFT 3.1.3 Troubleshooting Guide 55

2 Troubleshoot the server

Where MODE=DELETE, only the ID parameter is useful.

[MTRACE = {0 | 0..31}]

Checks the level 1 traces to be collected for the Transfer CFT "scheduler" task (CFTMAIN).

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of catalog access events

l 2: Trace of ‘‘process" events (begin and end tasks)
l 4: Trace of ‘‘protocol" events
l 8: Trace of ‘‘operator" events
l 16: Trace of ‘‘file" events
[N2TRACE = {0 | 0..63}]

Checks the level 2 network traces to be collected for all Transfer CFT tasks.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of definition requests (define/undefine resource, register/unregister)

l 2: Trace of definition indications (future use)
l 4: Trace of connect / disconnect requests

l 8: Trace of connect / disconnect indications

l 16: Trace of requests during data exchange phase
l 32: Trace of indications during data exchange phase
[N3TRACE = {0 | 0..255}]

Checks level 3 network traces to be collected for all Transfer CFT tasks.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are
determined by each environment.

[PTRACE = {0 | 0..31}]

Checks the level 1 traces to be collected for the Transfer CFT protocol task (CFTTPRO).

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of flagged messages

l 2: Trace of flagged messages
l 4: Trace messages sent to CFTTFIL

Transfer CFT 3.1.3 Troubleshooting Guide 56

2 Troubleshoot the server

l 8: Trace of the controller motor

l 16: Trace of FPDUs
START = {CFT | DELAYED}

Starting the trace:

l CFT: at Transfer CFT start­up

l DELAYED: during Transfer CFT operations

If START = CFT, a trace vector is created with the identifier defined in the ID parameter. This
identifier is used in the STOPTRC command to stop collection.

[S2TRACE = {0 | 0..255}]

Checks the level 2 system traces to be collected for all Transfer CFT tasks.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: SAM network interface trace

l 2: SMM system interface trace
l 4: SFM system interface trace
l 8: SDM system interface trace
l 16: SSM system interface trace
l 32: STM system interface trace

l 64: SSY system interface trace

l 128: Memory space allocation trace
[S3TRACE = {0 | 0..255}]

Checks the level 3 system traces to be collected for all Transfer CFT tasks.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are
determined by each environment.

[TRCFNAM = {" " | filename}]

Name of trace file to be fed by traces.

Character string maximum length: 64 characters.

[TRCFTYP = {STANDARD | CIRCULAR}]

Trace file type:

l STANDARD: sequential file written in extend. The new records are written after the old ones.
l CIRCULAR: direct access file, with a set number of fixed­length records. This file is accessed
through a circular up­date, the new records over­writing the old ones
[TRCLREC = n]

Transfer CFT 3.1.3 Troubleshooting Guide 57

2 Troubleshoot the server

Trace file physical records (fixed) length.

This parameter is:

l Mandatory if TRCFTYP = CIRCULAR

l Optional if TRCFTYP = STANDARD
[TRCNREC = n]

Number of trace file records.

This parameter is mandatory if TRCFTYP = CIRCULAR.

[XTRACE = {0 | 0..7}]

Checks the level 1 traces for Transfer CFT EXIT type operations.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of the request field sent by Transfer CFT to the "EXIT" executive
l 2: Trace of the user work field
l 4: Trace of the data field

Using the start trace command

About the STARTTRC command

This command, which is associated with a unique identifier, performs the following tasks:

l Defines and describes the conditions for starting and selecting traced data
l Associates a file identifier, already defined by the SETTRC command, with this trace which
designated the file in which the traces will be stored

Syntax
START TRC ID = identifier,
TID = identifier
[FTRACE = {0 | 0..15},]
[MTRACE = {0 | 0..31},]
[PTRACE = {0 | 0..31},]
[XTRACE = {0 | 0..7},]
[S2TRACE = {0 | 0..255},]
[S3TRACE = {0 | 0..255},]
[N2TRACE = {0 | 0..63},]
[N3TRACE = {0 | 0..255}]

Transfer CFT 3.1.3 Troubleshooting Guide 58

2 Troubleshoot the server

Parameters
ID = identifier

Identifier which makes the trace vector defined by this parameter set uniquely identifiable.

This parameter is a character string, maximum length 8.

[FTRACE = {0 | 0..15}]

Checks the level 1 traces for Transfer CFT file tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: transfer controller trace

l 2: security controller trace
l 4: file access controller trace
l 8: trace of flagged messages
[MTRACE = {0 | 0..31}]

Checks the level 1 traces for Transfer CFT scheduler tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of catalog access events

l 2: Trace of process events (begin and end tasks)

l 4: Trace of protocol events

l 8: Trace of operator events
l 16: Trace of file events
[N2TRACE = {0 | 0..63}]

Checks the level 2 network traces to be collected for all Transfer CFT tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of definition requests (define/undefine resource, register/deregister)

l 2: Trace of definition indications (future use)
l 4: Trace of connect / disconnect requests
l 8: Trace of connect / disconnect indications
l 16: Trace of requests during data exchange phase
l 32: Trace of indications during data exchange phase
[N3TRACE = {0 | 0..255}]

Checks level 3 network traces to be collected for all Transfer CFT tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are
determined by each environment.

[PTRACE = {0 | 0..31}]

Transfer CFT 3.1.3 Troubleshooting Guide 59

2 Troubleshoot the server

Checks the level 1 traces to be collected for the Transfer CFT ‘‘protocol" task.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of flagged messages

l 2: Trace of flagged messages
l 4: Trace messages sent to CFTTFIL
l 8: Trace of the controller motor
l 16: Trace of FPDUs
[S2TRACE = {0 | 0..255}]

Checks the level 2 system traces to be collected for all Transfer CFT tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: SAM network interface trace

l 2: SMM system interface trace
l 4: SFM system interface trace
l 8: SDM system interface trace
l 16: SSM system interface trace
l 32: STM system interface trace
l 64: SSY system interface trace
l 128: Memory space allocation trace
[S3TRACE = {0 | 0..255}]

Checks the level 3 system traces to be collected for all Transfer CFT tasks.

The chosen value is a mask (logical OR) combination of the desired values. These values are
determined by each environment.

TID = identifier

Identifier of the SETTRC or CFTTRACE command which defines the collection’s output trace file.

This identifier should exist, in that it should have been initialized by a SETTRC or CFTTRACE
command.

This parameter is a character string, maximum length 8.

[XTRACE = {0 | 0..7}]

Checks the level 1 traces for Transfer CFT "EXIT" type operations.

This parameter is only relevant if the parameter START = CFT.

The chosen value is a mask (logical OR) combination of the desired values. These values are:

l 1: Trace of the request field passed by Transfer CFT to the exit executive
l 2: Trace of the user work field

Transfer CFT 3.1.3 Troubleshooting Guide 60

2 Troubleshoot the server

l 4: Trace of the data field

Using the stop trace command

About the STOPTRC command

This command defines and describes the conditions for stopping a trace. The trace to be stopped is
indicated by the identifier previously created by the STARTTRC command.

Syntax
STOPTRC ID = identifier

Parameters
ID = identifier

Identifier which uniquely identifies the trace vector defined by this set of parameters.

This parameter is a character string, maximum length: 8.

Transfer CFT 3.1.3 Troubleshooting Guide 61

Messages and error codes
3
This chapter lists the different types of messages that Transfer CFT generates, and corrective actions
when applicable. It begins with this section, which describes message formats, severity, and
additional conventions used in this documentation.

Message format

Format in the documentation

Transfer CFT messages provide information on the status of the Transfer CFT. Messages have the
general format and supporting information:

The message CFTxxx: the actual message that is

severity is displayed on Transfer CFT
displayed

Explanation The elements, such as variables, in the above message are

detailed.

Consequence Description of what happens to the Transfer CFT, or lists

corrective actions.

Action If applicable, add corrective action here.

Format in the product

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]

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

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

Transfer CFT 3.1.3 Troubleshooting Guide 62

3 Messages and error codes

Writing conventions
Messages are written according to the following conventions.

Message description
The Transfer CFT messages use the format CFTxnns, for example CFTC01E. The elements that make
up the message format are described in the following sections.

Where:

l x: message source
l nn: sequence number
l s: message severity

Message source
Code Description

C Catalog: Access to the catalog

E End: Transfer CFT shutdown phase

F File: Access to files

H External PeSIT: PeSIT protocol, non­SIT profile and CFT profile

I Init: Transfer CFT initialization phase

N Network

P Parameter: Access to parameter files

R Request: Requests that Transfer CFT received from CFTUTIL, applications, or

interactive functions

S System: System interface operations by the Transfer CFT

T Transfers: Actions relating to transfers

U CFTUTIL: Messages from the CFTUTIL utility

X Security: Security system (only in the log)

Y SSL: SSL protocol

Transfer CFT 3.1.3 Troubleshooting Guide 63

3 Messages and error codes

Sequence number
The sequence number is an index characterizing the message within a given class.

Severity
The severity code is described in the following table.

Code Indicates

I Informational message only

W An anomaly which may be an error

E An error requiring correction (parameter setting or environment error)

F A serious system error requiring the intervention of Product Support

Symbolic variables used in message text

The table below lists the symbolic variables used in message text.

Code Description

char Alphanumeric character

cr Function return code

cmd Parameter setting or operator command name

Example: CFTPARM, SEND

cpu_id Host computer's CPU number

ctx Internal context

diagn Diagnostic code of a network error

Specific to the access method and, in some cases, to the system
Expressed in hexadecimal form

diagi Internal CFT diagnostic code (DIAGI) of the catalog

diagp CFT protocol diagnostic code (DIAGP) of the catalog

dest Partner list identifier (CFTDEST command)

Transfer CFT 3.1.3 Troubleshooting Guide 64

3 Messages and error codes

Code Description

direct Transmission direction

fname File name

host Physical address of the remote partner

id Command identifier (value of the ID parameter)

idf Model file identifier (CFTSEND/CFTRECV command)

idt Transfer identifier

keyw Keyword in a parameter setting command or an operator request

Example: PART, DIRECT

local Location of a network error:

1: local
0: remote

label Freeform name relating to the software protection key

maxtrans Number of transfers authorized at any one time

mode Action requested

n Numeric character

nb Numeric code

ncr General network error code

ncs Network error code specific to the access method and system

net Network resource identifier (CFTNET command)

part Local partner identifier (CFTPART command)

prot Transfer CFT protocol identifier (CFTPROT command)

pevent Protocol event

pid Process identifier

pstate Protocol status

recov General error recovery code (in the case of a network error), independent of
the system or access method

Transfer CFT 3.1.3 Troubleshooting Guide 65

3 Messages and error codes

Code Description

reason Reason code for a network error

Specific to the access method and, in some cases, to the system
Expressed in hexadecimal form

sappl SAPPL parameter value (name of the sending application)

scs System return code describing a system interface access error

state Transfer status

str Character string forming the message label

vfm VFM base name

Transfer CFT 3.1.3 Troubleshooting Guide 66

3 Messages and error codes

Transfer CFT messages: CFTB

This topic lists the CFTBxx messages and provides a type, a description, and when applicable a
consequence and corrective action.

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

Transfer CFT 3.1.3 Troubleshooting Guide 67

3 Messages and error codes

Error CFTB03E: 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 occurring
during the send request. This code is expressed in hexadecimal form.

Error message CFTB06E: Flow control error NCR=&ncr NCS=&ncs NET=&net

Explanation Network flow control error.

Error CFTB07E: PART=&part TFIL task Synchronization error CR=&cr CS=&cs

Explanation Problem encountered when sending an internal Transfer CFT 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 CFTB08E: PART=&part Network release resp err NCR=&ncr NCS=&ncs

NET=&net

Explanation Cannot respond to a network disconnection indication.

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

Error CFTB09E: PART=&part Network connect req local err NCR=&ncr NCS=&ncs
NET=&net

Explanation Cannot make an outgoing connection request on the network.

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

Transfer CFT 3.1.3 Troubleshooting Guide 68

3 Messages and error codes

Error CFTB10E: PART=&part RECOV=&recov L=&local R=&reason D=&diagn

NET=&net

Explanation Physical connection refused.

Consequence Depending on the source of the refusal and the RECOV code, the transfer is set
to the K status (diagnostic code 303) or remains in the D status (diagnostic
code 302) and will be retried.

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

Explanation Cannot refuse an incoming call.

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

Explanation Cannot accept an incoming call.

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

Explanation Transfer CFT internal synchronization error.

Transfer CFT 3.1.3 Troubleshooting Guide 69

3 Messages and error codes

Transfer CFT messages: CFTC

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

Warning CFTC01W CFT catalog storage is short n record(s) free

Explanation Catalog storage is short n record(s) free.

Consequence The catalog is nearly full ­ there are only n records free. Consider modifications
to free up space.

Error CFTC01E CFT catalog storage is full

Explanation The catalog storage is full. A command SHUT FAST=KILL is executed.

Consequence The stored commands can only be retrieved by restarting Transfer CFT. First
purge the Transfer CFT catalog (and modify the retention dates, for example).

Warning CFTC03W: PART=&part IDF=&idf IDT=&idt _ Running out of time

message (HHMMSSCC)

Explanation The transfer start time is outside the interval authorized by the &part
partner.

Consequence The next transfer retry will take place at the specified time [HHMMSSCC].

Transfer CFT 3.1.3 Troubleshooting Guide 70

3 Messages and error codes

Warning CFTC04W: PART=&part IDF=&idf IDT=&idt _ State C delete forbidden

Explanation A DELETE command was executed on a catalog request (in the C state), but
this operation is not allowed.

Consequence The catalog entry could not be deleted.

Warning CFTC05W: PART=1part IDF=&idf IDT=&idt _ Delete failed

Explanation A DELETE command was executed on a catalog request (in a state other than C
or D), but it failed as a result of a catalog access error.

Consequence The catalog entry could not be deleted.

The CFTT21E message may be displayed before this message.

Error CFTC06E: PART=&part [IDF=&idf IDT=&idt _ Update failed

Explanation A Transfer CFT catalog access error was detected when executing commands,
such as END, START, ACT and INACT.

Consequence The catalog entry was not updated and the command was ignored.
The CFTT21E message is displayed prior to this message.

Information CFTC07I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt STATE=&state ­

Deleted

Explanation A Transfer CFT catalog entry for partner &part, with identifier &idf, idt &idt and
state &state, has been deleted.

Information CFTC08I: &str

Transfer CFT 3.1.3 Troubleshooting Guide 71

3 Messages and error codes

Explanation Possible values for &str are described here. The following messages are
displayed when the catalog is purged on Transfer CFT startup, or at the time set
for the daily purge. For example:
When there are no transfers to delete:
Purge Started
Purge catalog-size=1000 in-use=0 pre-filtered=0(0%)
Purge Treated: catalog empty
Purge deleted= n treated=n(d%) match=d%.
Purge Treated
Purge Treated: no record found to delete
When there are transfers to delete:
Catalog: Loading...
Catalog: Load Done
Catalog: Size=100, Used=8(8%)
Purge Started.
Purge catalog-size=100 in-use=8 pre-filtered=8(100)
Purge deleted=1 treated=1(12) match=100
Purge deleted=2 treated=2(25) match=100
….
Purge deleted=8 treated=8(100) match=100
Purge Treated.
When Transfer CFT starts:
If there are no transfers to delete:
Catalog: Loading...
Catalog: Load Done
Catalog: Size= &00, Used=0(0%)
If there are transfers to delete:
Catalog: Loading...
Catalog: Load Done
Catalog: Size=100, Used=8(8%)
If there is a problem with the catalog INIT:
Catalog: Recovering
Catalog: Recovery Done: n errors
Catalog Recovery: n transfers from C to D state

Information CFTC09I: PART=&part IDF=&idf IDT=&idt STATE=&state DIRECT=&direct :

&cmd not executed

Explanation The security system does not allow the user to execute this command on the
catalog.

Consequence The command is ignored.

This message is followed by the CFTX02W and CFTX04W messages.

Transfer CFT 3.1.3 Troubleshooting Guide 72

3 Messages and error codes

Information CFTC10I: PART=&part IDF or IDM=&idf STATE=&state MODE=&mode : &cmd

not executed

Explanation The security system does not allow the user to execute this command on the
catalog.

Consequence The command is ignored.

This message is followed by the CFTX04W message.

Information CFTC11I: PART=&part IDM=&idf IDT=&idt : SEND REPLY not executed

Explanation The security system does not allow the user to execute this command on the
catalog.

Consequence The command is ignored.

Note: This message is followed by the CFTX01W message.

Information CFTC12I: PART=&part STATE=&state DIRECT=&direct TYPE=&type

SENTINEL_STATE=&trkstate Deleted

Transfer CFT 3.1.3 Troubleshooting Guide 73

3 Messages and error codes

Explanation This Transfer CFT message is displayed for each transfer that is deleted when
the catalog is purged. Where:
l &state = transfer status (C/D/H/K/T/X)
l &direct = S (send) / R (recv)
l &type = F (file) / M (message)
l &trkstate = Sentinel state
Possible values are:
l TO_EXECUTE
l SUSPENDED
l RECEIVING
l SENDING
l CANCELED
l RECEIVED
l SENT
l CREATED
l INTERRUPTED
l ACKED
l NACKED

Consequence The command is ignored.

Information CFTC13I: Catalog resize (xxxx ­­> yyyy) done

Explanation A dynamic command to resize the catalog was executed. The first message
displays the new size, and the second message indicates that the resizing (from
the original size xxxx to the new size yyyy) is complete.

Consequence The catalog automatically expands to the new size (the <yyyy> value) when
possible, up to the maximum defined limit.

Error CFTC13E: Transfer CFT catalog resize (xxxx ­­> yyyy) reached max before
expansion

Explanation A dynamic command to automatically expand the catalog failed, as the

maximum number of records has already been reached. The catalog size
remains unchanged (the <xxxx> value).

Consequence Normal functioning with existing catalog size, and no catalog expansion
occurs.

Transfer CFT 3.1.3 Troubleshooting Guide 74

3 Messages and error codes

Information CFTC15I: Deprecated command not executed BLKNUM=&blknum PART=&part

IDT=&idt : Cmd=&cmd>

Explanation The BLKNUM parameter is disabled for this command.

Set the uconf parameter cft.cftcat.enable_deprecated_blknum=Yes
to enable BLKNUM.
Note Regardless of the cft.cftcat.enable_deprecated_
blknum parameter setting, BLKNUM is disabled in a multi­
node configuration (uconf:cft.multi_
node.enable=Yes), and this message is displayed.

Consequence The command is ignored.

Warning CFTC29W Catalog Alert fill threshold reached: level=80%, id=CAT0

Explanation 80% of the catalog space has been used. 80% is the amount set by the CFTCAT
TLVWARN parameter.
When the critical fill threshold is reached, a message is recorded in the Transfer
CFT log.
A batch in response to the alert, the CFTCAT TLVWEXEC parameter, is
submitted.

Warning CFTC30WCatalog Alert cleared: level=30%, id=CAT0

Explanation This alert stops when the fill level drops below the TLVCLEAR level.
When the alert stops, the message is recorded in the Transfer CFT log, and a
batch, the CFTCAT TLVCEXEC parameter, is submitted.

Transfer CFT 3.1.3 Troubleshooting Guide 75

3 Messages and error codes

Transfer CFT messages: CFTE

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

Information CFTE09I: CFT Stop complete

Explanation Transfer CFT has been shut down (following an error or request).

Error CFTI42E

Explanation CFTI42E PID=18236 CFTTCPS Task startup error failed to lock resource
'C:\Axway\Transfer_CFT\runtime\run\cfttcps.pid': resource already
CFTI42E+locked
CFTI35I PID=18236 CFTTCPS Task ended
CFTI08F Init error _ Protocol process

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>

Transfer CFT 3.1.3 Troubleshooting Guide 76

3 Messages and error codes

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

Transfer CFT 3.1.3 Troubleshooting Guide 77

3 Messages and error codes

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:
l Unknown FPDU type=n:
Reception of an FPDU, for which the type byte in the header is unknown
l Missing PI number n into FPDU fpdu:
Reception of an FPDU with missing mandatory PI
l PGI n in PGI into FPDU fpdu:
Reception of an FPDU embedding a PGI in a PGI
l Invalid length n for PI n into FPDU fpdu:
Reception of an FPDU with a PI of invalid length
l 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.

l ­1 PGI embedded in a PGI
l ­2 Output buffer overflow
l ­3 End of PGI without PGI
l ­4 External/internal type error
l ­5 End of FPDU with PGI not closed
l ­8 Invalid PI length
l ­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.

Transfer CFT 3.1.3 Troubleshooting Guide 78

3 Messages and error codes

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 CFTG08E: PART=&part Network release response error NCR=&ncr NCS=&ncs

message 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

Transfer CFT 3.1.3 Troubleshooting Guide 79

3 Messages and error codes

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=

Transfer CFT 3.1.3 Troubleshooting Guide 80

3 Messages and error codes

Explanation The AckCONNECT FPDU sent by the SERVER partner is invalid.

The field "&str" is an explicit character string:
l Version = n:
The protocol version negotiated by the SERVER partner is invalid
l Window without Pacing:
A synchronization window is specified even though the interval is null,
l 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
l 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
l Pacing = n greater than initial value = n:
The synchronization interval negotiated by the SERVER partner is larger than
that proposed
l Window = n greater than initial value = n:
The synchronization window negotiated by the SERVER partner is larger than
that proposed
l Resynchronization = n:
The value of the resynchronization option negotiated by the SERVER partner
does not comply with the specifications of the protocol
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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.

Transfer CFT 3.1.3 Troubleshooting Guide 81

3 Messages and error codes

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:
l SDU size = n greater than initial value = n:
The maximum NSDU size negotiated by the partner is greater than that
proposed
l 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)
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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=

Transfer CFT 3.1.3 Troubleshooting Guide 82

3 Messages and error codes

Explanation The AckWRITE FPDU sent by the SERVER partner does not conform.
The field "&str" is an explicit character string:
l Restart point without restart option:
The remote partner proposes a restart point for the transfer, even though it is a
new transfer
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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 CFTG17E: PART=&part Invalid Check Point acknowledge n

message

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

Transfer CFT 3.1.3 Troubleshooting Guide 83

3 Messages and error codes

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

Transfer CFT 3.1.3 Troubleshooting Guide 84

3 Messages and error codes

Explanation The CONNECT FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l CRC option = n: The remote partner proposes a value for the CRC option
which does not comply with protocol specifications
o This value is displayed
o Only the values 0 (no CRC) and 1 (application of a CRC) are correct
l Version = n: The protocol version proposed by the remote partner does not
comply with the specifications of the PeSIT protocol
o Only the values 1 (version D) and 2 (version E) are allowed
o The incorrect value is displayed in the message
l Window without Pacing: A synchronization window is specified even
though the interval is null
l 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
l Access = n: The incorrect value received is displayed in the message
l Resynchronization = n: The functional resynchronization unit is negotiated
by the value 0 (no) or 1 (yes). Any other value is not allowed
l Pacing = n not authorized: The synchronization interval negotiated by the
SERVER partner does not comply with the specifications of the SIT profile
o The values 1, 2 and 3 are not allowed
l Application type relation R=sapp S=rapp: The SIT profile imposes a
correlation between the sender and receiver applications
o This correlation is not respected
o The message displays the first byte of PI 3 and 4 of the CONNECT FPDU
in numeric form
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not
referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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.

Transfer CFT 3.1.3 Troubleshooting Guide 85

3 Messages and error codes

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

Transfer CFT 3.1.3 Troubleshooting Guide 86

3 Messages and error codes

Explanation The CREATE FPDU sent by the REQUESTER partner does not conform. The
field "&str" is an explicit character string:
l IDT is null: Reception of a CREATE FPDU with a null Transfer Identifier (PI
13)
l Restart = n: Invalid value for the restart option of a transfer
l Data Code = n: Unknown code for the data to be transported
l Priority = n: Invalid priority assigned to the transfer
l Record Format = n: Unknown record format
l Record size = n greater than Pacing:The record size is greater than the
synchronization interval
l 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)
l File Organization = n: Unknown file organization
l Key length without indexed organization: A key length is specified for a file
that is not indexed
l Key Position without indexed organization: A key position is specified for a
file that is not indexed
l 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

l Space Unit = n: Space reservation unit unknown

l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not
referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 87

3 Messages and error codes

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.

Transfer CFT 3.1.3 Troubleshooting Guide 88

3 Messages and error codes

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.

Transfer CFT 3.1.3 Troubleshooting Guide 89

3 Messages and error codes

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:
l Unknown FPDU type=n:
Reception of an FPDU, for which the type byte in the header is unknown
l Missing PI number n into FPDU fpdu:
Reception of an FPDU with missing mandatory PI
l PGI n in PGI into FPDU fpdu:
Reception of an FPDU embedding a PGI in a PGI
l Invalid length n for PI n into FPDU fpdu:
Reception of an FPDU with a PI of invalid length
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 90

3 Messages and error codes

Explanation Problem encountered while formatting an FPDU.

l ­1 PGI embedded in a PGI
l ­2 Output buffer overflow
l ­3 End of PGI without PGI
l ­4 External/internal type error
l ­5 End of FPDU with PGI not closed
l ­8 Invalid PI length
l ­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.

Transfer CFT 3.1.3 Troubleshooting Guide 91

3 Messages and error codes

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:
l 903: invalid password
l 970: password expired, or
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 92

3 Messages and error codes

Explanation The AckCONNECT FPDU sent by the SERVER partner is invalid.

The field "&str" is an explicit character string:
l 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,
l 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
l 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
l Pacing = n greater than initial value = n:
The synchronization interval negotiated by the SERVER partner is larger than
that proposed
l Window = n greater than initial value = n:
The synchronization window negotiated by the SERVER partner is larger than
that proposed
l Resynchronization = n:
The value of the resynchronization option negotiated by the SERVER partner
does not comply with the specifications of the protocol
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 93

3 Messages and error codes

Explanation The AckCREATE FPDU sent by the SERVER partner does not conform.
The "&str" string is an explicit character string:
l NSDU size = n greater than initial value = n:
The maximum NSDU size negotiated by the partner is greater than that proposed
l 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)
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 94

3 Messages and error codes

Explanation The AckWRITE FPDU sent by the SERVER partner does not conform.
The field "&str" is an explicit character string:
l Restart point without restart option:
The remote partner proposes a restart point for the transfer, even though it is a
new transfer
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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).

Transfer CFT 3.1.3 Troubleshooting Guide 95

3 Messages and error codes

Error CFTH20E: Invalid CONNECT FPDU &str

Transfer CFT 3.1.3 Troubleshooting Guide 96

3 Messages and error codes

Explanation The CONNECT FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l CRC option = n:
The remote partner proposes a value for the CRC option which does not comply
with protocol specifications.
l This value is displayed:
Only the values 0 (no CRC) and 1 (application of a CRC) are correct
l 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
l Window without Pacing:
A synchronization window is specified even though the interval is null
l 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
l 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.
l Resynchronization = n:
The functional resynchronization unit is negotiated by the value 0 (no) or 1
(yes). Any other value is not allowed
l 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
l 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
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU

Transfer CFT 3.1.3 Troubleshooting Guide 97

3 Messages and error codes

l PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 98

3 Messages and error codes

Explanation The CREATE FPDU sent by the REQUESTER partner does not conform. The field
"&str" is an explicit character string:
l IDT is null:
Reception of a CREATE FPDU with a null Transfer Identifier (PI 13)
l Restart = n:
Invalid value for the restart option of a transfer
l Data Code = n:
Unknown code for the data to be transported
l Priority = n:
Invalid priority assigned to the transfer
l Record Format = n:
Unknown record format
l Record size = n greater than Pacing:
The record size is greater than the synchronization interval
l 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).
l File Organization = n:
Unknown file organization
l Key length without indexed organization:
A key length is specified for a file that is not indexed
l Key Position without indexed organization:
A key position is specified for a file that is not indexed
l 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
l Space Unit = n:
Space reservation unit unknown
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:

Transfer CFT 3.1.3 Troubleshooting Guide 99

3 Messages and error codes

The presence of a PGI embedded in another PGI is invalid

l 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

Transfer CFT 3.1.3 Troubleshooting Guide 100

3 Messages and error codes

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

Transfer CFT 3.1.3 Troubleshooting Guide 101

3 Messages and error codes

Explanation The AckORF FPDU sent by the SERVER partner does not conform.
The field "&str" is an explicit character string:
l 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)
l Compression Value without Indicator:
A compression value is negotiated even though the indicator inhibits the
compression option
l Compression Indicator without Value:
The compression indicator is set even though the negotiated value is null
l Compression Value = n:
The negotiated compression value does not comply with to the specifications of
the PeSIT protocol
l Compression Negotiation: n for n:
The negotiated compression is greater than the proposed compression
l 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
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 102

3 Messages and error codes

Explanation The AckTRANSFER.END FPDU sent by the SERVER partner does not conform.
The field "&str" is an explicit character string:
l Byte count mismatch n for n:
The number of bytes transferred does not correspond to the Transfer CFT­
maintained counter
l Record count mismatch n for n:
The number of records transferred does not correspond to the Transfer CFT­
maintained counter
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 103

3 Messages and error codes

Explanation This message is only displayed in security­enabled mode and corresponds to a

security problem.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 104

3 Messages and error codes

Explanation The AckSELECT FPDU sent by the SERVER partner does not conform.
The field "&str" is an explicit character string:
l 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
l IDT is null:
Reception of an AckSELECT FPDU with a null Transfer Identifier (PI 13)
l Data Code = n:
Unknown code for the data to be transported
l Priority = n:
Invalid priority assigned to the transfer
l Record Format = n:
Unknown record format
l Record size = n greater than Pacing:
The record size is greater then the synchronization interval
l NSDU size negotiation n for n:
The negotiated NSDU size is greater than that proposed
l NSDU too small n:
The negotiated NSDU size is smaller than the minimum authorized value (128)
l File Organization = n:
Unknown file organization
l Key length without indexed organization:
A key length is specified for a file that is not indexed
l Key Position without indexed organization:
A key position is specified for a file that is not indexed
l 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
l Space Unit = n:
Space reservation unit unknown
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU

Transfer CFT 3.1.3 Troubleshooting Guide 105

3 Messages and error codes

l PGI n in PGI into FPDU:

The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 106

3 Messages and error codes

Explanation The ORF FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l 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)
l Compression Value without Indicator:
A compression value is negotiated even though the indicator inhibits the
compression option
l Compression Indicator without Value:
The compression indicator is set even though the negotiated value is null
l Compression Value = n:
The negotiated compression value does not comply with the specifications of
the PeSIT protocol
l 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
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 107

3 Messages and error codes

Explanation This message is only displayed in security­enabled mode and corresponds to a

security problem.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 108

3 Messages and error codes

Explanation The MESSAGE FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l IDT is null:
Reception of a MESSAGE FPDU with a null Transfer Identifier (PI 13)
l Attribute = n:
PI 14 in the MESSAGE FPDU is set to an invalid value (attribute request)
l Data Code = n:
Unknown code for the data to be transported
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 109

3 Messages and error codes

Explanation The START of MESSAGE FPDU sent by the REQUESTER partner does not
conform.
The field "&str" is an explicit character string:
l IDT is null:
Reception of a D.MESSAGE FPDU with a null Transfer Identifier (PI 13)
l Attribute = n:
PI 14 of the D.MESSAGE FPDU is set to an invalid value (attribute request)
l Data Code = n:
Unknown code for the data to be transported
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 110

3 Messages and error codes

Explanation The READ FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l Restart point must be null for new transfer:
Reception of a READ FPDU with a restart point other than 0 for a new transfer
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 111

3 Messages and error codes

Explanation The SELECT FPDU sent by the REQUESTER partner does not conform.
The field "&str" is an explicit character string:
l IDT not null:
Reception of a SELECT FPDU with a non­null Transfer Identifier (PI 13) for a
new transfer
l IDT null with restart:
Reception of a SELECT FPDU with a null Transfer Identifier (PI 13) for a transfer
to be restarted
l Attribute = n:
PI 15 of the SELECT FPDU is set to an invalid value (file attribute request)
l Restart = n:
PI 15 of the SELECT FPDU is set to an invalid value (restart or new transfer)
l Priority = n:
PI 17 of the SELECT FPDU is set to an invalid value (transfer priority)
l NSDU too small n:
The negotiated NSDU size is smaller than the minimum allowed value (128)
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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.

Transfer CFT 3.1.3 Troubleshooting Guide 112

3 Messages and error codes

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:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 113

3 Messages and error codes

Explanation The SYNC (set synchronization point) FPDU sent by the sender partner does
not conform.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l Invalid length n for PI n into FPDU:
The length of the PI is invalid (less than minimum length or greater than
maximum length)

Transfer CFT 3.1.3 Troubleshooting Guide 114

3 Messages and error codes

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:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received,
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 115

3 Messages and error codes

Explanation The AckIDT (acknowledge transfer interrupt) FPDU sent by the partner does
not conform.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 116

3 Messages and error codes

Explanation The RESYNC (dynamic transfer resynchronization) FPDU sent by the sender
partner does not conform.
The field "&str" is an explicit character string:
l Resynchronization is not authorized:
Dynamic resynchronization is not authorized (CFTPROT RESYNC parameter) or
the maximum number of resynchronizations is exceeded (CFTPROT RESTART
parameter),
l Mismatch between header and FPDU size:
The FPDU length indicated in the header is not equal to the length of the FPDU
received
l Unknown FPDU:
The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU:
The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:
The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU:
The presence of a PGI embedded in another PGI is invalid
l 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:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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.

Transfer CFT 3.1.3 Troubleshooting Guide 117

3 Messages and error codes

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:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 118

3 Messages and error codes

Explanation The Middle of Message FPDU sent by the requester partner does not conform.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received

l Unknown FPDU:The number identifying the received FPDU is not referenced

l Missing PI number n into FPDU:The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU:The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 119

3 Messages and error codes

Explanation The AckCLOSE FPDU sent by the server partner does not conform.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received

l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n into FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n into FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 120

3 Messages and error codes

Explanation The CLOSE (file close) FPDU sent by the requester partner does not conform.
The field "&str" is an explicit character string:
l Mismatch between header and FPDU size: The FPDU length indicated in the
header is not equal to the length of the FPDU received
l Unknown FPDU: The number identifying the received FPDU is not referenced
l Missing PI number n in FPDU: The PI is mandatory for this type of FPDU
l Unknown PI number n in FPDU: The PI is unknown for this type of FPDU
l PGI n in PGI into FPDU: The presence of a PGI embedded in another PGI is
invalid
l 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:
l 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>

Transfer CFT 3.1.3 Troubleshooting Guide 121

3 Messages and error codes

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

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

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

Where:
l PART: partner
l PROT: local protocol definition (CFTPROT)
l IDS: reference for this session
l pi7: the window and the interval of the negotiated synchronization
l HOST:
o Requester side: the host address configured through CFTTCP for the related
partner (either an IP or a logical hostname).
o 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:
l disctd – requester mode, or
l discts – server mode

Transfer CFT 3.1.3 Troubleshooting Guide 122

3 Messages and error codes

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:
l PROT: the local definition of the protocol (CFTPROT)
l 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

Transfer CFT 3.1.3 Troubleshooting Guide 123

3 Messages and error codes

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 CFTH63I PESIT DMZ session for messages only PART=&part IDS=&ids
message

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.

l &reason: Network reason
l &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.
l &ids = Session call id
l &call = interval for the DMZ control call

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

PROTOCOL=&protocol

Explanation Incoming calls are rejected:

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

Transfer CFT 3.1.3 Troubleshooting Guide 124

3 Messages and error codes

Transfer CFT messages: CFTI

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

Information CFTI00I: Snumb of spawned procedure is &str

Explanation Specific MVS: Information concerning the submission of a procedure that has its
job identifier specified in &str.

Fatal CFTI01F: &str

Transfer CFT 3.1.3 Troubleshooting Guide 125

3 Messages and error codes

Explanation Internal Transfer CFT execution error.

The field "&str" can have the following values:
l CFT error &scs:
Transfer CFT inter­task communication system problem (waiting for the
CFTMAIN scheduler task queue)
l CFT error _ usage expired:
The Transfer CFT user key (CFTPARM KEY) does not authorize Transfer CFT
execution beyond the expired period
l CFT error _ CFT usage not authorized:
The Transfer CFT user key (CFTPARM KEY) does not authorize Transfer CFT
execution on this operating system or computer
l CFT error _ file keys not available:
The Transfer CFT user keys are stored in an indirection file (CFTPARM KEY
parameter); this file cannot be accessed by Transfer CFT
l CFT error &scs _ Common_area allocation failed:
Definition of the memory area common to the Transfer CFT tasks has failed.
This can be caused by insufficient memory
l CFT error &scs _ Mailbox definition failed:
Transfer CFT is unable to link to a mailbox defined by the *CFTOM command
l CFT error &scs _ CFT semaphore definition failed:
Transfer CFT is unable to define an inter­task communications queue
l CFT error _ CFTEXIT ID=&id missing:
A Transfer CFT task dedicated to file EXITs could not be activated (the CFTEXIT
command relating to the identifier mentioned (ID) was not found)
l CFT error _ Maximum process CFTEXIT running reached:
A Transfer CFT task dedicated to file EXITs could not be activated (the
maximum number of EXIT processes that can be activated has already been
reached)
l CFT error &cs _ Initializing process CFTEXIT:
A Transfer CFT task dedicated to file EXITs could not be activated (the
maximum number of EXIT processes that can be activated has already been
reached)
l CFT error _ &Net Network Access Method Option not authorized
by license key:
The Transfer CFT is NOT authorized to use the optional network access method
designated by &Net (TCP/IP).
l CFT error _ SSL Protocol Option not authorized by license key:
A protocol defined in the CFTPARM object uses the SSL option, but the SSL
option is not available with this license key.
l CFT error _ EBICS Protocol Option not authorized by license key:

Transfer CFT 3.1.3 Troubleshooting Guide 126

3 Messages and error codes

The EBICS protocol is defined in a CFTPARM object, but the EBICS option is
not available with this license key.
l CFT error _ FIPS Compliance Option not authorized by license
key:
The uconf:cft.fips.enable_compliance parameter is set to Yes, but the FIPS
option is not available with this license key.
l CFT error _ File Transfer Acceleration Option not authorized by
license key:
The uconf:acceleration.enable parameter is set to Yes, but the acceleration
option is not available with this license key.

Consequence The transfer concerned by the incident is interrupted, which is the K status.

Action Check parameter settings, analyze the &cs code value to determine, if
necessary, the origin of the error:
l CFT error &scs _ LOG stop failed:
The message logging task cannot be stopped
l CFT error &scs _ mailbox delete failed:
A mailbox defined by a CFTCOM command cannot be deleted

Consequence The Transfer CFT initialization phase has stopped.

Action Analyze the &scs. code to determine the exact origin of the error.

Warning CFTI01W: &str

Explanation CFT error &scs _ Initializing process CFTTFIL: A Transfer CFT task dedicated to
transfer file access could not be activated.

Consequence Transfer CFT is not stopped, and transfers are not interrupted.

Action No action necessary.

Fatal CFTI02F: Init Error code &scs _ Allocating param. file &fname

Explanation During Transfer CFT initialization an error was detected when allocating the
Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase has stopped.

Action Check that the file is not already allocated; if it exists, correct the error and
then restart Transfer CFT.

Transfer CFT 3.1.3 Troubleshooting Guide 127

3 Messages and error codes

Error CFTI03F: Init Error code &scs _ Opening param. file &fname

Explanation During Transfer CFT initialization an error was detected when opening the
Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase has stopped.

Action Correct the error and then restart Transfer CFT.

Error CFTI04F: Init Error code &scs _ Allocating partners file &fname

Explanation During Transfer CFT initialization an error was detected when allocating the
Transfer CFT partner file.

Consequence The Transfer CFT initialization phase has stopped.

Action Check that the file is not already allocated, correct the error and then restart
Transfer CFT.

Error CFTI05F: Init Error code &scs _ Opening partners file &fname

Explanation During Transfer CFT initialization an error was detected when opening the
Transfer CFT partner file.

Consequence The Transfer CFT initialization phase has stopped.

Action Correct the error and then restart Transfer CFT.

Error CFTI06F: Init Error code &scs _ Allocating catalog file &fname

Explanation During Transfer CFT initialization an error was detected when allocating the
Transfer CFT catalog file.

Consequence The Transfer CFT initialization phase has stopped.

Action Check that the file is not already allocated, correct the error and then restart
Transfer CFT.

Transfer CFT 3.1.3 Troubleshooting Guide 128

3 Messages and error codes

Error CFTI08F: Init error _ Protocol process

Explanation During Transfer CFT initialization an error was detected when activating the
Transfer CFT protocol process.

Consequence The Transfer CFT initialization phase has stopped.

Action Inform Transfer CFT Support.

Error CFTI09F: Init error _ Communication process

Explanation During Transfer CFT initialization an error was detected when activating the
Transfer CFT communication process.

Consequence The Transfer CFT initialization phase has stopped.

Action Inform Transfer CFT Support.

Error CFTI10F: Init error _ Logger process

Explanation During Transfer CFT initialization an error was detected when activating the
Transfer CFT message logging process.
It may be a memory allocation or queue definition type system error (or a
problem when submitting a message to the queue).

Consequence The Transfer CFT initialization phase has stopped.

Action Inform Product Support.

Information CFTI11I: Init complete _ Logger process

Explanation Normal end of Transfer CFT logging process initialization.

Information CFTI12I: Init complete _ Protocol process

Explanation Normal end of Transfer CFT protocol process initialization.

Transfer CFT 3.1.3 Troubleshooting Guide 129

3 Messages and error codes

Information CFTI13I: Init complete _ Communication process

Explanation Normal end of Transfer CFT communication task initialization.

Information CFTI14I: CFT Init complete

Explanation Normal end of Transfer CFT initialization.

Error CFTI15F: Error code &ncs _ Trying to define resource &id

Explanation Rejection of the define resource request specified by the network interface.
The &ncs return code explains the cause of the rejection.

Consequence The Transfer CFT initialization phase has stopped.

Action Review Transfer CFT parameter settings (CFTNET commands).

Error CFTI16F: Error code &ncs _ Register request

Explanation Rejection of the register request request specified by the network interface.
The &ncs return code explains the cause of the rejection.

Consequence The Transfer CFT initialization phase has stopped.

Action Review Transfer CFT parameter settings (CFTPROT commands).

Error CFTI17F: Init error _ Account file &fname

Explanation During the Transfer CFT initialization phase an error was detected when
processing the accounting file (CFTACCNT command).

Consequence The Transfer CFT initialization phase has stopped.

Action Check the existence and integrity of the &fname file.

Information CFTI18I: _ &str

Transfer CFT 3.1.3 Troubleshooting Guide 130

3 Messages and error codes

Explanation This is a Transfer CFT welcome message describing the computer environment
and the main runtime characteristics, according to the options activated by the
software key (KEY parameter):
l Usage of this product is strictly limited to &cpu_id machine: The Transfer
CFT can only be executed on the computer with the designated CPU
l Usage of this product is strictly limited to &label: The Transfer CFT can only
be executed within a specific framework, as designated by &label
l Usage of this product is strictly limited until &date: The Transfer CFT cannot
be executed after the date designated by &date
l &Maxtrans simultaneous transfer(s) is(are) authorized: Transfer CFT cannot
process more than &Maxtrans simultaneous transfers. This value overrides
the MAXTRANS parameter in the CFTPARM command
l &Net Network Access Method Option is authorized: The Transfer CFT is
authorized to use the optional network access method designated by &Net
(TCP/IP)
o The information in this message is related to the UCONF setting for
server.authentication_method.
l &Prot Protocol Option is authorized: Transfer CFT is authorized to use the
protocol option designated by &Prot (Secure PeSIT)
If an attempt is made to use an unauthorized option, such as a network access
method or protocol option, Transfer CFT does not start, and displays a
message.
Information messages include:
l FNAME: CFTLOG name
l AFNAME: CFTALOG name
l TYPE: File FNAME: file communication name
l TYPE :Mbx FNAME : mailbox name
l TYPE :TCPIP HOST: host name PORT: port if synchronous
communication
If PassPort is used for SSL:
l CFTI18I hostname : addrhost
l CFTI18I port : port number

Consequence Transfer CFT is stopped during the initialization phase.

Information CFTI19I:© Copyright AXWAY,....

Explanation Transfer CFT copyright message.

Transfer CFT 3.1.3 Troubleshooting Guide 131

3 Messages and error codes

Fatal message CFTI20F: Semaphore definition failure CR=&cr CS= &scs

Explanation Cannot define the internal communications queue.

Consequence Transfer CFT is stopped during its initialization phase.

Error CFTI21F: ID=&id Resource define failure CS=&ncs NET=&net

Explanation Cannot define the resource, the identifier of which appears in the message.
This resource corresponds to a CFTNET command.

Consequence Transfer CFT is stopped during its initialization phase.

Error CFTI22F: ID=&id Register request failure CS=&ncs NET=&net

Explanation Cannot register a user, the identifier of which appears in the message. This
user corresponds to a CFTPROT command.

Consequence Transfer CFT is stopped during its initialization phase.

Error CFTI23F: MAIN synchronization failure CR=&cr CS=&scs

Explanation Internal synchronization error between the main Transfer CFT task and the
protocol task.

Consequence Transfer CFT is stopped during its initialization phase.

Information CFTI24I : &str

Transfer CFT 3.1.3 Troubleshooting Guide 132

3 Messages and error codes

Explanation Message displayed when viewing the command cache or the transfer cache:
CFTUTIL or CFTINT MQUERY command.
The messages depend on the type of cache concerned (command or catalog):
* TRANSFER CACHE IS EMPTY
The catalog cache is empty.
The messages vary according to the context:Or gives details of the cache
information (catalog or command cache) according to the type of information
displayed
For a line in the command cache, the information is divided into three parts:
l command execution
l DATE and TIME
l type of command (SWITCH ACCNT, SWITCH LOG or PURGE)
For a transfer, the information is divided into four parts:
l request activation time
l identifier of the partner concerned
l idf identifier and
l IDT value calculated by Transfer CFT

Information CFTI25I Init complete _ Security active [&str]

Explanation The description of the message &str specifies the activated security options:
l HAB: Normal end of initialization with activation of the Transfer CFT security
system
l SSL: Normal end of initialization with activation of the SSL protocol
The information in this message is affected by the UCONF setting for access
management.

Error CFTI26I Init complete _ Security not active

Explanation Normal end of initialization without activating the Security option (Transfer CFT
security system and the SSL protocol).

Error CFTI27F Init Error code &scs _ Opening security file &file

Explanation When Transfer CFT was initialized, a security system open error was detected.

Consequence The Transfer CFT initialization phase is stopped.

Transfer CFT 3.1.3 Troubleshooting Guide 133

3 Messages and error codes

Action Inform Product Support.

Information CFTI28I Init complete _

Explanation Message on initialization of CFTMAIN. With following Message CFTI18I FNAME

:catalog name.

Information CFTI34I PID=&id &task Task started successfully

Explanation The &task Task whose internal identifier is &pid has been started successfully.

Information CFTI35I PID=&id &task Task ended

Explanation The &task Task whose internal identifier is &pid has stopped.

Information CFTI36I CRONJOB: ID=%idcron, CRONTAB=%cronname %str

Explanation Idcron =ID de CFTCRON command

Cronname = id of the list in CRONTABS in CFTPARM
Str=
l INSERT OK: NEXT= date time ,TIME= %s ­ (%s = TIME of CFTCRON
command defined by ID)
l INSERT OK: NOACTIVE­ The CFTCRON with a STATE=NOACTIVE in the
configuration is not activated.
l Not enabled ­ (cronname not defined in the CRONTABS list)

Information CFTI39I

Explanation Displays information about the Transfer CFT Heartbeat. Possible states:
l Enable
l Update UCONF parameters
l Disable

Transfer CFT 3.1.3 Troubleshooting Guide 134

3 Messages and error codes

Error CFTI40E OMVS SEGMENT NOT DEFINED for user=xxxxxx.

Explanation z/OS only

If the OMVS segment is not defined for Transfer CFT and/or the
Copilot server owner, then Transfer CFT, the Copilot server, or
CFTUTIL (synchronous communication) stops and displays this
message.
To disable the display and check option, modify the
environment variable in the ..UPARM(CNFENV)target file as
follows:
omvs_check_disable=1.

Information CFTI41I OMVS information for

user=xxxxxx,uid=n,gid=n,home=(/xxxxx)

Explanation z/OS only

If the OMVS segment is defined for Transfer CFT and/or the
Copilot server owner, this information message displays.
To disable the display and check option, modify the
environment variable in the ..UPARM(CNFENV)target file as
follows:
omvs_check_disable=1.

Error CFTI42E PID=&pid &task Task startup error failed to lock

resource '&pid_file_name': resource already locked

Explanation The pid_file_name that is used to ensure process uniqueness

could not be locked causing the task to fail.
Locate and stop the locked process. If this does not resolve the
issue, restart the server using the "force­stop" mode.

Transfer CFT 3.1.3 Troubleshooting Guide 135

3 Messages and error codes

Transfer CFT messages: CFTN

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

Information CFTN01I NET=&net started

Explanation Startup of the network resource &net.

Information CFTN02I NET=&net PROTOCOL=&prot started

Explanation Startup of the protocol &prot associated with the &net network.

Error CFTN03E : Error creating SSL task &str

Explanation Problem with activating the CFTTSSL task. The error is specified by &str.

Consequence The transfer is aborted.

Action Contact the support team if necessary.

Error CFTN04E : Synchronization error (&str) SSLTID=&pid CR=&cr CS=&scs

Explanation Problem with sending an internal Transfer CFT message to a CFTTSSL task.

Transfer CFT 3.1.3 Troubleshooting Guide 136

3 Messages and error codes

Information CFTN05I &message

Explanation TCP/IP related information related to file transfer operations or resource

initialization. The message contains the explanation of the information.

Error CFTN05E &message

Explanation A TCP/IP error related to file transfer operations or resource initialization was
detected. The message contains the explanation of the error in plain text.

Consequence If the error occurs during the Transfer CFT initialization phase, this phase is
stopped. Otherwise, if the error is related to a file transfer, this transfer will not
proceed.

Action For an error occurring during the initialization phase, check the CFTNET
definitions. For an error involving a file transfer, check the CFTPART
definitions.

Warning CFTN05W &message

Explanation The same as CFTN05E, a TCP/IP related error, but the condition is
considered less severe.

Information CFTN06I No network class suitable for resource depletion prevention

activation

Explanation Information concerning the network resource depletion prevention feature.

Warning CFTN36W: TCPMAXUSER=&maxcnx reached. Network connect reject

host=&host port=&port

Explanation The maximum number of connections supported has been reached. An

incoming connection from host &host port &port is rejected.

Transfer CFT messages: CFTP

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

Message format

Transfer CFT 3.1.3 Troubleshooting Guide 137

3 Messages and error codes

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 CFTP01F: CFTPARM &id _ Not found

Explanation The &id identifier of the Transfer CFT parameter file (see the CFTPARM
parameter) is not defined.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTPARM parameter settings (see the CFTPARM parameter), correct
and restart Transfer CFT.

Error CFTP02F: CFTTRACE &id for CFTPARM &id _ Not found

Explanation When initializing Transfer CFT, the CFTTRACE &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTSYST parameter settings (see the CFTPARM parameter), correct
and restart Transfer CFT.

Error CFTP03F: CFTLOG &id for CFTPARM &id _ Not found

Explanation During Transfer CFT initialization the CFTLOG &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTLOG parameter settings (see the CFTPARM parameter), correct
and restart Transfer CFT.

Transfer CFT 3.1.3 Troubleshooting Guide 138

3 Messages and error codes

Error CFTP04F: CFTNET &id for CFTPARM &id _ Not found

Explanation During Transfer CFT initialization the CFTNET &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTNET parameter settings (see the CFTPARM parameter), correct
and restart Transfer CFT.

Error CFTP05F: CFTPROT &id for CFTPARM &id_ Not found

Explanation During Transfer CFT initialization the CFTPROT &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTPROT parameter settings (see CFTPROT), correct and restart
Transfer CFT.

Error CFTP06F: CFTCAT &id for CFTPARM &id _ Not found

Explanation During Transfer CFT initialization the CFTCAT &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTCAT parameter settings (see CFTCAT), correct and restart
Transfer CFT.

Error CFTP07F: CFTCOM &id for CFTPARM &id _ Not found

Explanation During Transfer CFT initialization the CFTCOM &id identifier was not found in
the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check the CFTCOM parameter settings (see CFTCOM), correct and restart
Transfer CFT.
CFTP08F: CFTNET &id for CFTPROT &id _ Not found

Transfer CFT 3.1.3 Troubleshooting Guide 139

3 Messages and error codes

Fatal CFTP08F: CFTNET &id for CFTPROT &id _ Not found

Explanation During Transfer CFT initialization the CFTNET &id identifier for a given
CFTPROT &id protocol was not found in the Transfer CFT parameter file.

Consequence The Transfer CFT initialization phase is stopped.

Action Check:
l the CFTNET and CFTPROT parameter settings (see the CFT CFTNET and
CFTPROT topics)
l the CFTPARM parameter settings
l the list of authorized protocols and network identifiers (NET=(.,.), PROT=
(.,.) ),that the number of items in this list does not exceed the maximum
authorized quota
Correct and restart Transfer CFT.

Error CFTP09F: CFTSEND &id for CFTPARM &id _ No default record found

Explanation During Transfer CFT initialization the identifier describing the default file
characteristics used for send transfers (CFTSEND parameter) is unknown.

Consequence The Transfer CFT initialization phase cannot continue correctly and Transfer
CFT is aborted.

Action Check the CFTPARM (DEFAULT=.) and CFTSEND parameter settings, correct
and restart Transfer CFT.

Error CFTP10F: CFTRECV &id for CFTPARM &id _ No Default record found

Explanation During Transfer CFT initialization the identifier describing the default file
characteristics used for receive transfers (CFTRECV parameter) is unknown.

Consequence The Transfer CFT initialization phase cannot continue correctly and Transfer
CFT is aborted.

Action Check CFTPARM (DEFAULT=.) and CFTRECV parameter settings, correct and
restart Transfer CFT.

Error CFTP13F: CFTXLATE &id _ Not found

Transfer CFT 3.1.3 Troubleshooting Guide 140

3 Messages and error codes

Explanation There is no CFTXLATE command, the identifier of which is &id.

Consequence The transfer requiring this translation table definition cannot be executed.

Action Specify a CFTXLATE command for this transfer direction and the source and
target alphabets.

Error CFTP14F: CFTACCNT &id for CFTPARM &id _ Not found

Explanation During Transfer CFT initialization the command describing the accounting
characteristics (CFTACCNT command), the ID parameter of which corresponds
to the ACCNT parameter in the CFTPARM command, was not found.

Consequence The Transfer CFT initialization phase cannot continue correctly and Transfer
CFT is aborted.

Action Check the CFTACCNT parameter settings, correct and restart Transfer CFT.

Error CFTP15F: CFTPROT &idprot for CFTPARM &idparm _ Not loading in memory

Explanation During Transfer CFT initialization the CFTPROT &idprot card could not be
loaded in memory (insufficient space).

Consequence This card cannot be used for transfers.

Action Reduce the number of CFTPROT card identifiers in the CFTPARM &idparm
command (see the Transfer CFT topics that correspond to your OS to find out
the parameter setting limits). After correcting your parameter settings, restart
Transfer CFT.

Error CFTP16F: CFTNET &idnet for CFTPARM &idparm _ Not loading in memory

Explanation During Transfer CFT initialization the CFTNET &idnet card could not be loaded
in memory (insufficient space).

Consequence This card cannot be used for transfers.

Action Reduce the number of CFTNET card identifiers in the CFTPARM &idparm
command (see the Transfer CFT topics that correspond to your OS to find out
the parameter setting limits).
After correcting your parameter settings, restart Transfer CFT.

Transfer CFT 3.1.3 Troubleshooting Guide 141

3 Messages and error codes

Error CFTP17F: CFTCOM &idcom for CFTPARM &idparm _ Not loading in memory

Explanation During Transfer CFT initialization the CFTCOM &idcom card could not be
loaded in memory (insufficient space).

Consequence This card cannot be used for transfers.

Action Reduce the number of CFTCOM card identifiers in the CFTPARM &idparm
command (see the Transfer CFT topics that correspond to your OS to find out
the parameter setting limits).
After correcting your parameter settings, restart Transfer CFT.

Error CFTP18F: Error of integrity

Explanation An integrity violation has been detected on the parameter or partner file when
the file is sealed. The previous message of the CFTIxxx (partner file) or
CFTPxxx (parameter file) type gives more information about the operation
requested on the file(s).

Consequence The Transfer CFT initialization phase is aborted.

Error CFTP19E: PART=&part IDF=&idf CFTAPPL=&id DIRECT=&direct not found

Explanation The security system is running but the CFTAPPL &id card used to assign an
owner to a transfer and corresponding to IDF=&idf was not found.

Consequence The transfer is rejected and no entry is created in the catalog.

Error CFTP20F: direct=server &id for CFTPROT &prot _ Not found

Explanation The security (SSL) being activated, the CFTSSL &id direct=server card whose
ID parameter corresponds to the value of the SSL parameter, CFTPROT
command was not found.

Consequence The Transfer CFT initialization phase has shut down.

Transfer CFT messages: CFTR

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

Message format

Transfer CFT 3.1.3 Troubleshooting Guide 142

3 Messages and error codes

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 CFTR02E: &cmd Failed _ Invalid date or time

Explanation The &cmd command contains at least one invalid date or time.

Consequence The command is ignored.

Action Check the command syntax.

Error CFTR03E: &cmd Failed _ &msg No record found for <PART=,IDF=,DIRECT=>

Explanation The &cmd command cannot be associated with any record in the Transfer CFT
catalog file (example: deletion of a non­existing record).
The &msg refers to the CFTR12I message contents.

Consequence The command is ignored.

Action Check the command syntax.

Error CFTR04E: &cmd Failed _ Keyword &keyw too large

Explanation The length of the &keyw keyword is greater than 8.

Consequence The command is ignored.

Action Check the description of this parameter in the Transfer CFT Online
documentation, correct the error and then resubmit the command.

Error CFTR05E: &cmd Failed _ Illegal separator for keyword &keyw

Explanation A parameter separator in the &cmd command is invalid.

Transfer CFT 3.1.3 Troubleshooting Guide 143

3 Messages and error codes

Consequence The command is ignored.

Action Check the command syntax (the separator must be a comma), correct the error
and then resubmit the command.

Error CFTR06E: &cmd Failed _ Keyword &keyw, missing quote

Explanation A closing quote (') is missing in the value assigned to the &keyw keyword.

Consequence The command is ignored.

Action Check the offending parameter, correct the error and then resubmit the
command.

Error CFTR07E: &cmd Failed _ Too many keywords

Explanation There are too many keywords for this command.

Consequence The command is ignored.

Action Check the command syntax, correct the error and then resubmit the
command.

Error CFTR08E: &cmd Failed _ Keyword &keyw unknown or duplicate

Explanation The &keyw keyword is unknown or duplicated in the command.

Consequence The command is ignored.

Action Check the command syntax, correct the error and then resubmit the
command.

Error CFTR09E: &cmd Failed _ Keyword &keyw missing

Explanation The &keyw keyword, which is mandatory for the command, is missing.

Consequence The command is ignored.

Action Check the command syntax, correct the error and then resubmit the
command.

Transfer CFT 3.1.3 Troubleshooting Guide 144

3 Messages and error codes

Error CFTR10E: &cmd Failed _ Keyword &keyw value out of bounds

Explanation The &keyw keyword of the &cmd command is numeric and its value is outside
the authorized limits.

Consequence The command is ignored.

Action Check the possible values for this parameter, correct the error and then
resubmit the command.

Error CFTR11E: &cmd Failed _ Invalid value for keyword &keyw

Explanation The value of the &keyw keyword of the &cmd command is not authorized (for
example: numeric value for an alphabetic­type parameter).

Consequence The command is ignored.

Action Check the possible values for this parameter, correct the error and then
resubmit the command.

Information CFTR12I: &cmd PART=&part [IDF=&idf | IDM=&idm]IDT=&idt Treated FOR

USER=&user

Explanation The command was executed correctly.

The partner's name (&part), the IDF (&idf) and the IDT (&idt) are only defined if
it is a SEND or RECV command.

Error CFTR13E: &cmd Failed _ IDT=&idt not allowed

Explanation During execution of a command (response to a message or transfer for

example) the required transfer identifier (&idt) was not found in the Transfer
CFT catalog.

Consequence The command is ignored.

Action Check the parameter settings of the command and the transfer identifier value.

Warning CFTR14W: &cmd Failed PART=&part _ No transfer found for this request

Transfer CFT 3.1.3 Troubleshooting Guide 145

3 Messages and error codes

Explanation When processing an ACT or INACT command, no transfer in the 'D' state and
with DIAGI=430 for ACT or in the 'C' state for INACT was found in the Transfer
CFT catalog for the partner(s) designated by &part.

Consequence The command takes effect for any subsequent transfers concerning the partner
(s).

Warning CFTR15W: &cmd not treated for user &user

Explanation The security system has refused to execute the MQUERY or SHUT command.
The CFTX03W message is displayed before this message.

Consequence The command is ignored.

Information CFTR16I: &message

Explanation Information concerning either the TURN command or the WLOG command.
l TURN command:
o PART=&part
o MODE=&mode (&str) &mode: create,replace,delete
o &str: “part not found”,”part inact”,”prot DMZ not found” ,”part not in
requester mode","commutation not available”,"see
omintime,omaxtime”,”already in command cache”,”not into command
cache”
l WLOG command:
o &message displayed in the Transfer CFT LOG

Error CFTR16E: &message

Explanation Displays error status in the WLOG command.

l &message displayed in the Transfer CFT LOG

Warning CFTR16W: &message

Explanation Displays warning status in the WLOG command.

l &message displayed in the Transfer CFT LOG

Information CFTR17I: &cmd In progress for USER &user &message

Transfer CFT 3.1.3 Troubleshooting Guide 146

3 Messages and error codes

Explanation This information message displays at the beginning of the processing for the
&cmd.
l Cmd =DELETE/END
l Message where PART=&part IDF=&idf [ IDT=&idt IDTU=&idtu IDA=&ida
STATE=&state]

Information CFTR20I &message

Explanation Information concerning the folder monitoring functionality.

l For each configured directory a related message is written to the log.
l When a file is automatically submitted for emission, a log message is also
written to the log.

Error CFTR20E &message

Explanation Error messages originating from the folder monitoring functionality.

Usually triggered by error conditions encountered on file manipulation as
renaming, deleting.

Fatal CFTR20F &message

Explanation Fatal messages originating from the folder monitoring functionality.

Indicates that a severe error condition was encountered and is preventing this
functionality from proceeding normally.

Error CFTR21E &cmd Failed _ No record found <IDTU=&idtu PART=&part

IDT=&idt>

Explanation During the internal command execution (&cmd) the required unique transfer
identifier (&idtu) was not found in the Transfer CFT catalog.

Consequence The command is ignored.

Transfer CFT 3.1.3 Troubleshooting Guide 147

3 Messages and error codes

Transfer CFT messages: CFTS

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

Warning CFTS01W: Synch. response time­out _ Waitresp uplifted

Explanation The message placed in a synchronous queue has received no response (time
limit expired).

Consequence Another attempt will be made.

Error CFTS02E: PART=&part [IDF=&idf | IDM=&idm] IDT=&idt DIRECT=&direct

&fname not found

Explanation The &fname procedure was not found for a given transfer (&idt).
This procedure was requested after a file or message transfer or subsequent to
an error (see the Transfer CFT Online documentation, EXEC parameters).

Information CFTS03I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt _ &fname executed

Action The procedure (&fname) has just been executed for a given transfer (&idt).
This procedure was requested at the end of a file or message transfer, or in the
event of an error (see the EXECxxx parameters).

Warning CFTS04W: Action file &fname is empty

Transfer CFT 3.1.3 Troubleshooting Guide 148

3 Messages and error codes

Explanation An action is envisaged at the end of a transfer or in the event of an error (see the
Transfer CFT Online documentation, EXECxxx parameters); the file to be
submitted is empty.

Error CFTS05E: Error code &scs _ Trying to access &str

The &str variable can have the following values:
&fname

Explanation An access error was detected on a file.

This file (&fname) corresponds to an action requested at the end of a transfer
or in the event of an error (see the Transfer CFT Online documentation
EXECxxx parameters).

Consequence The procedure will not be executed. If the action was requested at the end of a
transfer, the transfer ends normally.

Action Check that the characteristics of the file to be submitted are correct (attributes
and length) and inform Product Support if necessary.

Error CFTS06E: Error code &scs _ Trying to access temporary file

Explanation An action was requested at the end of a transfer or in the event of an error.
This action is submitted (see the EXECxxx parameters) through a buffer file
(&fname).
An access error was detected on this buffer file.

Consequence The procedure will not be executed. If the action was requested at the end of
the transfer, the transfer ends normally.

Action l Check that the characteristics of the buffer file are correct (attributes and
length).
l Check that it exists (created or defined logically in the Transfer CFT startup
procedure).
l Contact Product Support.

Error CFTS07E: Insufficient space for temporary file

Transfer CFT 3.1.3 Troubleshooting Guide 149

3 Messages and error codes

Explanation An action was requested at the end of a transfer or in the event of an error.
This action is submitted (see the Transfer CFT Online documentation, EXECxxx
parameters) through a buffer file (&fname). The space reserved for this file
proves insufficient.

Consequence The procedure will not be executed. If the action was requested at the end of
the transfer, the transfer ends normally.

Action Increase the file size, inform Product Support.

Error CFTS08E: Error code &scs _ Executing temporary file

Explanation The procedure (&fname) could not be executed for a given transfer (&idt).
This procedure was requested at the end of a file or message transfer or in the
event of an error (see the Transfer CFT Online documentation EXECxxx
parameters).

Consequence The procedure will not be executed. If the action was requested at the end of
the transfer, the transfer ends normally.

Action Analyze the &scs code and inform Product Support if necessary.

Error CFTS10E: File communication task error (&str1) _ &str2

Transfer CFT 3.1.3 Troubleshooting Guide 150

3 Messages and error codes

Explanation Following a synchronous message queue time­out, the communication task

aborted.
The str1 and str2 values are:

str1 Associated str2 value

define sem terminating

open terminating

memory terminating

post terminating

invalid sem terminating

catalog full terminating

<cs code> terminating

read continue

delete shut continue

Action Contact Product Support.

Error CFTS11E: Allocation error _ Trying to access temporary file

Explanation An action was requested at the end of a transfer or in the event of an error.
This action is submitted (see the Transfer CFT Online documentation, EXECxxx
parameters) through a buffer file (&fname). An allocation error was detected
on this buffer file.

Consequence The procedure will not be executed. If the action was requested at the end of
the transfer, the transfer ends normally.

Action l Check that the characteristics of the buffer file are correct (attributes and
length).
l Check that it exists (created or defined logically in the Transfer CFT startup
procedure).
l Contact Product Support.

Transfer CFT 3.1.3 Troubleshooting Guide 151

3 Messages and error codes

Warning CFTS12W: Error code &scs _ CFT write messages to output stream

Explanation The Transfer CFT logging process can no longer write messages in the log file
(s) (problem adding to the file, system incident).

Consequence Transfer CFT messages will be written to the standard output (screen for
example).

Action Analyze the &scs code and inform Product Support if necessary.

Error CFTS13E: Semaphore failure &cs_CFTTPRO aborted

Explanation Problem receiving an internal Transfer CFT message by the PROTOCOL task.

Consequence A message has perhaps been lost; the reactions are unpredictable.

Action Analyze the &scs code and inform Product Support if necessary.

Error CFTS14E: ID=&id error initializing process

Explanation Cannot run the end of transfer exit task. This message follows the Transfer
CFT message CFTI01.

Consequence No effect on the actual transfer (catalog not updated). The exit is not
executed. If an end of transfer procedure was defined, it is run.

Action Inform Product Support.

Information CFTS15I: PART = &part Kill Session Reference &ctx:&ctx

Explanation Internal message to Transfer CFT giving information on the transfer context
killed. The &ctx values specify the context concerned.

Error CFTS16E: Synch. response time­out_End transfer exit

Explanation The exit task is run but does not respond to the Transfer CFT. This corresponds
to the initial phase establishing communications between the Transfer CFT and
the exit task.

Transfer CFT 3.1.3 Troubleshooting Guide 152

3 Messages and error codes

Consequence None on the actual transfer (catalog not updated). The exit is not executed. If
an end of transfer procedure has been defined, it is run.

Action Inform Product Support.

Error CFTS17E: Error code &scs _ Trying to access End transfer exit

Explanation Error posting a Transfer CFT message to the exit task during inter­task
communications.

Consequence None on the actual transfer (catalog not updated). The exit is does not receive
any directives from the Transfer CFT.

Action Inform Product Support.

Warning CFTS18W: PART=&part [IDF=&idf | IDM=&idm] IDT=&idt _ Catalog record

label

Explanation label equals "State not updated x ­> y" (x = current state, y = requested state)
or "not deleted".
Transfer CFT catalog update problem.

Consequence The catalog entry corresponding to the transfer is not updated.

Action Inform Product Support.

Information CFTS19I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt _ Catalog record label

Explanation Information message label equals "updated x ­> y" (x = current state, y =
requested state) or "deleted".
The Transfer CFT catalog is updated.

Information CFTS20I: Message

Explanation Message specific to the user exit.

Information CFTS21I: PART=&part [IDF=&idf | IDM=&idm]IDT=&idt Exit request ID=&id

Transfer CFT 3.1.3 Troubleshooting Guide 153

3 Messages and error codes

Explanation Information message prior to sending information to the end of transfer exit.

Consequence None.

Information CFTS22I: Task time out End of transfer exit

Explanation Exit task re­entry time­out. The task is stopped automatically.

Consequence The exit task will be rerun by the next call.

Action If necessary, increase the value of the WAITTASK parameter in the CFTEXIT
card.

Error CFTS23E: Bad user return code <details>

Explanation Error message specific to the end­of­transfer user exit. The details that display
in the message depend on the CFTLOG format (v23 or v24).
Example
V24 format:
CFTS23E Bad User return code: 4 <IDTU=idtu PART=part1
IDF=idf1 IDT=idt >
V23 format:
CFTS23E Bad User return code : 4 PART=part1 IDF=idf1
IDT=idt

Consequence None.

Error CFTS26E XTRK task error &str

Explanation Error initializing the Sentinel monitoring task.

Action Take note of the complete text of the message (&str) and contact Axway
Product Support.

Error CFTS27E: Synchronous communication task error CR=&cr &str

Transfer CFT 3.1.3 Troubleshooting Guide 154

3 Messages and error codes

Explanation Synchronous communication task error.

CR=&cr &str CFT
l Internal synchronization error.
l Password authentication error due to invalid user or password.

Consequence Depending on the severity of the problem, the synchronous communication

task can be stopped or continued (and either Terminating or Continue is
displayed in the accompanying message &str).

Action Notify Technical Support, if necessary. Furnish the complete message as well
as the synchronous communication media parameters.

Information CFTS29I Cannot acces XTRK task _ &str"

Explanation Problem in communication with the Sentinel monitoring task.

Action Take note of the complete text of the message and contact Axway Product
Support.

Information CFTS30I XTRK Information &str"

Explanation Elements of information concerning the Sentinel monitoring task.

The field "&str" is an explicit string:
“Buffer File Info : Current = nn , Max=mm”
where:
l number of current records = nn
l maximum number of records = mm

Warning CFTS31W XTRK Warning &str Error Code = &cr \n"

message

Explanation The user is warned of a problem in communication with the Sentinel Server or
the Sentinel Agent. The message is stored in the overflow file for the Sentinel
monitoring task.
The text of the &str message specifies the possible type of warning:
sendMessage : send of a message to Sentinel

Transfer CFT 3.1.3 Troubleshooting Guide 155

3 Messages and error codes

Warning CFTS32W TCOMS Connection refused (address=nnn.nnn.nnn.nnn,

name=userid)

Explanation An incoming connection from name=userid and address=nnn.nnn.nnn.nnn

was rejected because this address is not authorised for Synchronous
Communication. See the CFTCOM object ADDRLIST parameter.

Information CFTS33I CFTLOG current file before switch

Explanation For SWITCH LOG or SWITCH ACCNT:

l Transfer CFT start­up
l SWITCH operator
l SWITCH cache command
l SWITCH if file is full during a write
l If no switch procedure is defined

Information CFTS34I CFTLOG executed switch proc

Explanation For SWITCH LOG or SWITCH ACCNT:

l Transfer CFT start­up
l SWITCH operator
l SWITCH cache command
l SWITCH if file is full during a write
l If no switch procedure is defined

Information CFTS35I CFTLOG current file after switch

Explanation For SWITCH LOG or SWITCH ACCNT:

l Transfer CFT start­up
l SWITCH operator
l SWITCH cache command
l SWITCH if file is full during a write
l If no switch procedure is defined

Transfer CFT 3.1.3 Troubleshooting Guide 156

3 Messages and error codes

Information CFTS36I CFTACCNT current file (no switch executed)

Explanation For SWITCH LOG or SWITCH ACCNT:

l Transfer CFT start­up
l SWITCH operator
l SWITCH cache command
l SWITCH if file is full during a write
l If the two CFTLOG files are full and are not performing the switch:
l CFTS36I CFTLOG current file (no switch executed): CFTOUT
l If the two CFTACCNT files are full and are not performing the switch:
l CFTS36I CFTACCNT current file (no switch executed): Files full

Information CFTS37I CRONJOB ID=%idcron, CRONTAB=%cronname %exec executed,

NEXT=%s
CFTS37I CRONJOB: ID=%s, CRONTAB=%s ACT DONE
CFTS37I CRONJOB: RECONFIG type=CRON DONE

Explanation Job defined by %exec is executed. correctly;The next submit is indicated in

NEXT=date time

Error CFTI38E CRONJOB: ID=%idcron, CRONTAB=%cronname INSERT FAILED

Explanation Insert failed due to incorrect entry or unexpected character. Check CRONTAB
parameters, such as TIME.

Error CFTS39E CRONJOB ID=%idcron, CRONTAB=%cronname exec %exec failed

Explanation Job failed. Could not file the file to submit. Check file properties.

Information CFTS40F: CFTACCNT FORMAT=(V23/V24) not available for &fname

Transfer CFT 3.1.3 Troubleshooting Guide 157

3 Messages and error codes

Explanation An error occurred in the FORMAT=V23/V24 (V23 default) parameter of CFTFILE

TYPE=ACCNT.
When using the V23 format, the saved description (for ACCOUNT files) is the
same
as in previous versions.
However when using the V24 format, the length for saving is 2048,and the
saved description
takes into account the new longer field lengths.
Note: The FORMAT parameter for the CFTACCNT command must be the same
setting as for
CFTFILE TYPE=ACCNT. If not, a message displays in the LOG and Transfer CFT
does
not start. The message is either::
CFTS40F CFTACCNT FORMAT=V24 not available for CFT.ACCNT
CFTS40F CFTACCNT FORMAT=V23 not available for CFT.ACCNT
Followed by the message: CFTI17F Init error _ Account file .CFT.ACCNT

Information CFTS41I: Catalog Alert exec &fname executed

Explanation The procedure &FNAME for a catalog alert was executed.

l When the critical fill threshold is reached, a message CFTC29W is recorded in
the Transfer CFT log.
A batch, which is defined by the CFTCAT TLVWEXEC parameter, is submitted.
l When the alert ceases, a message CFTC30W is recorded in the Transfer CFT
log.
A batch, which is defined by the CFTCAT TLVCEXEC parameter, is submitted.

Error CFTS42E: Catalog Alert exec &fname not found

or
CFTS42E : Catalog Alert exec &fname failed

Explanation The procedure &FNAME for a catalog alert was not found or failed on access
producing this error.
l When the critical fill threshold is reached, a message CFTC29W is recorded in
the Transfer CFT log.
The batch, which is defined by the CFTCAT TLVWEXEC parameter, is not
executed
l When the alert ceases, a message CFTC30W is recorded in the Transfer CFT
log
The batch, which is defined by the CFTCAT TLVCEXEC parameter, is not
executed.

Transfer CFT 3.1.3 Troubleshooting Guide 158

3 Messages and error codes

Information CFTS43I: RECONFIG

Explanation Displays information about CFTUTIL RECONFIG TYPE=UCONF.

Warning CFTS44W Unexpected message Class &n <TASK=&str>

Explanation An internal message received by the &str task has an unexpected class value
(&n).

Consequence The message is ignored.

CFTS45W Unexpected Message Type &n <TASK=&str CLASS=&str>

Explanation An internal message received by the &str task with CLASS=&str has an
unexpected type value (&n).

Consequence The message is ignored.

Fatal CFTS46F CFTPRX error _ &str

Explanation A fatal error occurred in the proxy task (CFTPRX). The error details are in &str.

Consequence Transfer CFT stops.

Action If necessary, contact Axway support.

Error CFTS47E CFTPRX error _ &str

Explanation A significant error occurred in the proxy task (CFTPRX). The error is detailed in
&str.

Consequence The concerned transfer goes into error.

Action If necessary, contact Axway support.

Transfer CFT 3.1.3 Troubleshooting Guide 159

3 Messages and error codes

Warning CFTS48W CFTPRX _ &str

Explanation An anomaly occurred in the proxy task (CFTPRX). The anomaly details are in
&str.

Information CFTS49I CFTPRX _ &str

Explanation Information message from the Proxy task (CFTPRX). The &str value gives
additional details.

Fatal CFTS50F CFTJRE error _ &str

Explanation A fatal error occurred when starting the CFT Java task (CFTJRE). The error is
detailed in &str.

Consequence Transfer CFT is stopping.

Action If necessary, contact Axway support.

Error CFTS51E CFTJRE error _ &str

Explanation A significant error occurred in the Transfer CFT Java task (CFTJRE). The error is
detailed in &str.

Consequence The concerned transfer goes in error.

Action If necessary, contact Axway support.

Warning CFTS52W CFTJRE _ &str

Explanation An anomaly occurred in the Transfer CFT Java task (CFTJRE). The anomaly is
detailed in &str.

Error CFTS53I CFTJRE _ &str

Explanation Information message from the Transfer CFT Java task (CFTJRE). The &str value
gives additional details.

Transfer CFT 3.1.3 Troubleshooting Guide 160

3 Messages and error codes

Error CFTS54F CFTACC task fatal CR=&cr &str

Explanation A fatal error occurred in the accelerator task (CFTACC). The error is detailed in
&str.

Consequence Transfer CFT is stopping.

Action If necessary, contact Axway support.

Information CFTS55I Acceleration &str

Explanation Information message from the Accelerator task (CFTACC). the &str value gives
more detail.

Error CFTS56E Central Governance error (<error_code>) <error_msg>

Explanation An error occurred when executing a <request> on Central Governance.

Consequence The Transfer CFT instance does not display the correct status.

Warning CFTS57W : Synchronous communication _ Authentication ignored :

authentication_enable=yes but authentication_method=none
or
CFTS57W : Synchronous communication _ Authentication ignored :
User=user01 Group=group01 provided a password but authentication_
enable=no

Explanation There are two possible scenarios:

l Authentication_enable=yes but authentication_method=none
In this case, in the unified configuration authentication is enabled but no
mode is defined: uconf: cft.server.cftcoms.authentication_enable=yes
uconf: cft.server.authentication_method=none
l User=user01 Group=group01 provided a password but authentication_
enable=no
In the CONFIG command the PASSWORD parameter is set, but in the unified
configuration it is disabled: uconf:cft.server.cftcoms.authentication_
enable=no

Transfer CFT 3.1.3 Troubleshooting Guide 161

3 Messages and error codes

Error CFTS59E Multi­node error _ &str

Explanation An important error occurred during the transfer recovery. The error is detailed
in &str.

Consequence The transfer in question is not recovered.

Action Contact the support team if necessary.

Warning CFTS60W Multi­node _ &str

Explanation An anomaly occured during the transfer recovery. The anomaly is detailed in
&str.

Information CFTS61I Multi­node _ &str

Explanation Displays information about the multi­node transfer recovery phase. The &str
value provides additional details.

Information CFTS62I: Schedule

Explanation Displays information about UCONF scheduling.

Transfer CFT 3.1.3 Troubleshooting Guide 162

3 Messages and error codes

Transfer CFT messages: CFTT

This topic lists the CFTTxx (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 CFTT00E: CFT request warning _ &str

message

Transfer CFT 3.1.3 Troubleshooting Guide 163

3 Messages and error codes

Explanation An error may have occurred during a request sent to the Transfer CFT. The &str
message label specifies the possible type of error:
l Unknown protocol request:
Internal error of the Transfer CFT, which receives an unexpected protocol event
l Unknown oper request:
The operator command received is unknown
l Not computable state:
The transfer is not possible (status other than "D" (Available)
l Transfer for myself rejected:
The target of the transfer is the local site (CFTPARM PART field) The Transfer CFT
therefore refuses to activate a transfer to itself
l Logger currently unreachable:
A SWITCH command,switching log files, was attempted while the LOG task (CFT
log) was not (or no longer) active
l Ignored (Catalog Full):
The catalog was 100% full and so the last SEND (or RECV) command could not
be processed; if it was submitted via the Transfer CFT communication file, it is
stored in the file and the associated communication process stops (for more
information, refer to the CFTC01W message)
l Request syntax error:
There is a syntax error in the request; inform Product Support
l Catalog request unknown:
The request is invalid
l Unknown process request:
An internal Transfer CFT error was detected; inform Product Support
l Unknown file request:
An internal Transfer CFT error was detected; inform Product Support
l Transfer already in progress:
An attempt was made to restart a transfer in progress; the transfer was not
restarted
l File already transferred:
An attempt was made to restart a terminated transfer; the transfer was not
restarted
l &file:
A read error was detected on the authorizations file (&file); inform Product
Support
l Access Exit Task unreachable: &diagp:
The directory exit task cannot be accessed (DIAGP specifies the cause); inform
Product Support

Transfer CFT 3.1.3 Troubleshooting Guide 164

3 Messages and error codes

l Request Ignored : time­out:

The request was not processed by the Transfer CFT (end time limit exceeded)
l Unable to attach Client mailbox:
Attachment to the client application was rejected
l Unable to send data to Client mailbox:
Data cannot be sent to the client application

Error CFTT01E: PART=&part IDF=&idf IDT=&idt _ Open mode not allowed

message

Explanation A transfer request was made in OPEN mode, but this mode is not supported for
the partner concerned.

Consequence The transfer is denied. The corresponding catalog entry is set to the KEEP
status.

Action Transfer the files with this partner in closed mode.

Error CFTT02E: PART=&part IDF=&idf IDT=&idt _ Transfer Area Full

message

Explanation A new transfer request was made but the maximum number of transfers
allowed at the same time has been reached.

Consequence The transfer is not executed.

Action Wait for a decrease in the number of transfers or increase the maximum
number of authorized transfers (this increase can only be made by the
technicians responsible for porting and customizing the Transfer CFT
product).

Error CFTT03E: PART=&part IDF=&idf IDT=&idt _ Max retry Reached

message

Transfer CFT 3.1.3 Troubleshooting Guide 165

3 Messages and error codes

Explanation The Transfer CFT has performed all retry actions to establish the link with the
partner.
l The transfer activation retry counter for this protocol has exceeded the
value of the RESTART parameter (CFTPROT command) In this case there
have been no other network connection attempts and there are no more
protocols in this partner's protocol list In this case the DIAGI code is set to
406
l The physical connection has resulted in an invalid network address. It is the
last address for this protocol; there is no backup partner. The internal
diagnostic code (DIAGI) is set to 405. When the catalog is displayed, it
overrides the value 301 signifying an invalid address
l The physical connection has resulted in a fatal network error. In this case
the DIAGI code is set to 303; the DIAGP value defines the source of the error
l The last physical connection attempted according to the values of the
RETRYM, RETRYN and RETRYW parameters has failed. It is the last protocol
in this partner's protocol list; there is no backup partner
Note: the internal diagnostic code (DIAGI) is set to 405. When the catalog is
displayed, it overrides the value 302 signifying a non­fatal network error.

Consequence The transfer is refused. The corresponding catalog entry is set to the KEEP
status.

Action Determine the error according to the DIAGI value. Analyze the DIAGP code.

Error CFTT05E: PART=&part IDF=&idf IDT=&idt _ Restart Failed

message

Explanation A file transfer restart request is not possible (the restart identifier is unknown,
for example).

Consequence The transfer is not restarted.

Action Try a new transfer.

Warning CFTT06W: PART=&part IDF=&idf IDT=&idt _ Partner switching IPART=&part

message

Explanation The partner (&part) cannot be reached within the authorized time slot
(OMINTIME, OMAXTIME).

Consequence The transfer will be retried via the intermediate partner IPART.

Transfer CFT 3.1.3 Troubleshooting Guide 166

3 Messages and error codes

Warning CFTT07W: Ending Transfer Task &n Failed _ A transfer Running

message

Explanation Attempt to delete a transfer task for which not all transfers have been
completed. &n designates an internal Transfer CFT task number incremented
each time a transfer task is activated.

Error CFTT08E: PART=&part IDF=&idf IDT=&idt _No prot available

message

Explanation The maximum number of retries authorized for a transfer using the &prot
protocol has been reached (see the Transfer CFT CFTPROT RESTART
parameter).

Consequence The entry corresponding to the transfer in the catalog is set to KEEP.

Action Analyze the causes of the broken communication link.

Error CFTT09E: PART=&part IDF=&idf IDT=&idt PROT=&prot _ Maximum cv

message affected

Explanation All virtual circuits associated with a partner in server mode have already been
allocated

Consequence The transfer is refused locally.

Action Wait for virtual circuits to be freed or increase the maximum number of virtual
circuits (see the Transfer CFT Online documentation CNXIN and CNXINOUT
parameters).

Error message CFTT10E: PART=&part PROT=&prot _ Protocol not authorized

Explanation The &prot protocol is not authorized for this partner.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check Transfer CFT parameter settings.

Error CFTT11E: PART=&part PROT=&prot CLASS=&n _ &net not found

message

Transfer CFT 3.1.3 Troubleshooting Guide 167

3 Messages and error codes

Explanation The network characteristics associated with the partner and for the &n class of
resources have not been found in the Transfer CFT partner file.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check the Transfer CFT parameter settings.

Warning CFTT12W: PART=&part IDF=&idf IDT=&idt _ Out of time to call

message

Explanation A transfer request was made outside the time slot authorized for this
partner.

Consequence The transfer is not executed (remains in the D state).

Action Execute a new transfer within the time slot authorized for this partner.

Information CFTT13I: PART=&part (IDF=&idf IDM=&idm) IDT=&idt _ Session parameters

message PROT=&prot SAP=&sap DIALNUM(or HOST)= &dialnum (or &host)

Explanation Information message for each dialno (or host) switch and protocol.

Error message CFTT14E: PART=&part IDF=&idf IDT=&idt _ Not found

Explanation The &part partner was not found in the Transfer CFT partner file.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check the Transfer CFT parameter settings.

Error CFTT15E: NPART=&part _ Not found

message

Explanation The network identifier of the &part partner was not found in the Transfer CFT
partner file.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check the Transfer CFT parameter settings.

Transfer CFT 3.1.3 Troubleshooting Guide 168

3 Messages and error codes

Error CFTT16E: PART=&part IDF=&idf _ No implicit send

message

Explanation The partner has made a selection request and no file is ready to be sent (SEND
on HOLD or implicit SEND).

Consequence The transfer is not executed (no catalog record is created).

Action Prepare a transfer (SEND state=hold) or declare an implicit send in the

Transfer CFT parameter settings.

Information CFTT17I: PART=&part IDF=&idf IDT=&idt _ STATE=HOLD

Explanation A transfer request was voluntarily put on Hold (see Transfer CFT Concepts,
Send on Hold).

Consequence The transfer is not executed and is on hold for a possible reception request.

Error CFTT18E: PART=&part IDF=&idf CFTAUTH id=&id _ Not found

message

Explanation The identifier of the list of files authorized for a partner was not found in the
Transfer CFT parameter file.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check the Transfer CFT parameter setting.

Error message CFTT19E: PART=&part _ Invalid remote password &str *

Explanation Transfer request was made and the partner sent an invalid password.
*where &str = supplied password is incorrect

Consequence The connection is refused.

Action Execute a new transfer with a valid password.

Error message CFTT20E : PART=&part _ PVC not allowed

Explanation The call collect connection request received is not authorized for this partner.

Transfer CFT 3.1.3 Troubleshooting Guide 169

3 Messages and error codes

Consequence The connection is refused.

Error CFTT21E: PART=&part IDF=&idf IDT=&idt _ Catalog access failed &scs ,&cr
message

Explanation During a transfer (or a transfer request) an undetermined Transfer CFT catalog
access error was detected (input/output error for example).

Consequence The transfer is interrupted (or not executed).

Action Analyze the &scs code and inform Product Support if necessary.

Error CFTT23E: PART=&part Shutdown in progress _ &str

message

Information A Transfer CFT shutdown is in progress, the request sent is not processed (the
&str message specifies the type of request).
Connect in being refused: connection request from one of its partners.

Error CFTT24E: PART=&part PROT=&prot _ Invalid call number &n

message

Explanation The called number received (server end) is not in the list of numbers defined
(and authorized) for this partner (&n represents the unauthorized number).

Consequence The connection is refused.

Error CFTT25E: PART=&part IDF=&idf _ IDF not authorized

message

Explanation During a transfer request the identifier of the file to be transferred is not
authorized for this partner (server or requester end).

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Request that another file be sent or authorize this identifier.

Transfer CFT 3.1.3 Troubleshooting Guide 170

3 Messages and error codes

Error CFTT26E: PART=&part IDF=&idf IDT=&idt _ Max transfer tasks

message

Explanation A new transfer request was made but the maximum number of transfer
processes has been reached (as has the maximum number of transfers per
process).

Consequence The transfer is not executed and remains in the D state.

Action Wait for a decrease in the number of transfers or increase the maximum
number of authorized processes or the maximum number of transfers per
process. This increase can only be made by the technicians responsible for
porting and customizing the Transfer CFT product.

Error CFTT27E: PART=&part IDF=&idf IDT=&idt _ Error &scs writing starts

message

Explanation The statistics relating to the designated transfer could not be written in the
accounting file.

Consequence The accounting file is incomplete.

Action Analyze the file access system code (&scs) to determine the source of the error.

Error CFTT28E: No outgoing CV configured on Network

message

Explanation An outgoing call attempt was made on a network resource configured with the
CALL = IN parameter (CFTNET command).

Consequence The requester transfer cannot be executed.

The catalog entry is set to the K state with a protocol diagnostic code (DIAGP):
"L 0B 22" ­ 0B meaning that network access is forbidden.
If another protocol (CFTPROT) using another network resource (CFTNET) is
declared for this partner (PROT parameter of the CFTPART command), Transfer
CFT will make another attempt on this resource.

Action Change the parameter settings so that the protocol designated for the partner
points to a network resource available for outgoing calls.

Error CFTT29E: DEST= &dest ­Invalid use _Define for [BOTH/LOCAL/COMMUT] use
message only

Transfer CFT 3.1.3 Troubleshooting Guide 171

3 Messages and error codes

Explanation A broadcast list can be used (FOR = parameter) with the value:
l LOCAL meaning that the partner list can only be used for a direct transfer.
l COMMUT meaning that the partner list can only be used for store and forward
operations.
l BOTH meaning that the partner list is used locally and for store and forward
operations.

Error CFTT30E: PART=&part IDF=&idf IDT=&idt _ Max Exit tasks

message

Explanation A new transfer request with an associated EXIT was requested but the
maximum number of EXIT processes has been reached.

Consequence The transfer is not executed (remains set to the D state).

Action Wait for a decrease in the number of transfers or increase the maximum
number of processes allowed.

Warning CFTT31W: Ending Exit Task &n Failed _ A transfer Running

message

Explanation Attempt to delete an EXIT task in which not all transfers have been completed.
&n designates an internal Transfer CFT task number incremented each time a
transfer task is activated.

Error CFTT32E: PART=&part IDF=&idf IDT=&idt _ Partner not found

message

Explanation The identifier of the &part partner was not found in the Transfer CFT partner
file.

Consequence The transfer is not executed. The corresponding catalog entry is set to KEEP.

Action Check the Transfer CFT parameter settings (see the Transfer CFT User Guide).

Error CFTT33E: PART = &dest IDF = &idf IDT = &idt _ Illegal use of CFTDEST
message

Transfer CFT 3.1.3 Troubleshooting Guide 172

3 Messages and error codes

Explanation The identifier of a partner mentioned in a list (CFTDEST command) is itself a

list identifier. As list embedding is not allowed, the transfer with this partner is
interrupted.
Transfers with the previous partners in the list are nevertheless activated, but
only for an explicit list (FNAME parameter of the CFTDEST command).

Consequence The transfer is interrupted with a DIAGI 401.

Action Change the partners list to show all the partners on one level.

Error CFTT34E: PART = &part IDF = &idf _ &cause

message

Explanation Access error on an external file describing a list of items:

l Partners list: CFTDEST FNAME=#filename,
l File group: SEND FNAME=#filename,
Possible values of &cause are:
l Allocating external file &file
l Opening external file &file
l Reading external file &file
The file processing phase (allocation, opening or reading) is specified in the
message.

Consequence The external file cannot be read ­ the corresponding transfers are not
activated.

Action Correct the file access problem.

Warning CFTT35W: PART=&part IDF=&idf IDT=&idt DELETE file &fname Failed _&str
message

Explanation A DELETE command is executed on a catalog request (in receive mode and in
a non­terminated H or K state).
The receive file corresponding to this request could not be deleted.
“ ” (no label): The file cannot be deleted; inform Product Support
l Allocate file error: File allocation error
l Open file error File open error
l Close file error: File closing error
l Free file error: File release error
l Allocate memory error: Memory allocation error

Transfer CFT 3.1.3 Troubleshooting Guide 173

3 Messages and error codes

Consequence The request is deleted from the catalog but the user is notified that the
&wfname file has not been deleted.

Warning CFTT36W: PART=&part IDF=&idf IDT=&idt ERASE file &fname Failed &str
message

Explanation A DELETE command is executed on a catalog request (in receive mode and in
a non­terminated state).K or H
The purge of the received file that corresponds with this request could not be
carried out:
l Allocate file error: File allocation error
l Open file error : File open error
l Close file error: File clofile close error
l Free file error: File release error
l Allocate memory error: Memory allocation error

Consequence The request is deleted from the catalog but the user is notified that the &fname
file has not been purged.

Information CFTT37I: PART=&part _ Not found and ignored for CFTDEST &id
message

Transfer CFT 3.1.3 Troubleshooting Guide 174

3 Messages and error codes

Explanation The new parameter NOPART for the CFTDEST command can have on of the
following values: ABORT (default value), CONTINUE, or IGNORE.
l ABORT: Transfer CFT continues functioning as it was before the request for
change.
No transfer is generated if a partner does not exist in the list of partners defined
in the PART parameter. If the list of partners is defined in the PART parameter. If
the list of partners is defined in a file (FNAME parameter) the transfers carried
out for the only for existing partners and the treatment is identical to that for the
NOPART=CONTINUE option.
l CONTINUE: If the partner does not exist, Transfer CFT indicates this in a
message in the LOG.
CFTT32E PART=idpart Not found. Pass the transfer in SFK diagi 408 and
continue the transfers for the other partners. The generic post remains in the K
state and the end of transfer procedure is not executed.
l IGNORE:
l If a partner does not exist in the list, Transfer CFT ignores the partner (there is
no transfer) and moves on to the next partner.
l A message is displayed in the LOG CFTT37I PART=idpart _ Not found and
ignored for CFTDEST iddest
l The generic job passes to the T state and is under the end of transfer
procedure.

Information CFTT38I: PART=&part _ Dynamic partner: &npart

Information When receiving an incoming call from an unknown source (no local partner
description corresponding to the &part network name received), the &npart
dynamic partner creation mechanism is triggered.

Error CFTT39E: PART=&part DIAG=&diag _ Access Exit Connect Reject

message

Explanation The connection is refused by the directory EXIT task; &diag contains the field
in the communication structure updated by the EXIT.

Consequence The transfer is aborted with the following diagnostics codes: 403, 409, 410,
411, 414, 415, 416, 418, 425, 426.

Transfer CFT 3.1.3 Troubleshooting Guide 175

3 Messages and error codes

Error CFTT40E: PART=&part DIAG=&diag _ Access Exit Error

message

Explanation An error has been detected in the directory EXIT task.

Consequence The transfer is aborted with the following possible diagnostics codes: 134,
423.

Error CFTT42E: >part&PART=<Partner switching IPART=PART not available

Explanation The IPART value must be different than the PART value.

Error CFTT44E: PART=&part IDF=&idf _ &str directory &file

message

Explanation The file selection phase is indicated in the message, where &str can be
allocating, opening, empty, or reading.
A directory access error has been detected when sending a list of file names or
a group of files based on a selection.
SEND FNAME = # FIL* or SEND FNAME = # DIR*.

Consequence If the directory could not be accessed (allocating, opening or empty), no

transfers are triggered.
If the directory could not be read when selecting the files in the directory, all
transfers preceding the error are triggered.

Error CFTT44W: PART=&part IDF=&idf _ &str directory &file (file not found
message ignored)

Explanation The file selection phase is indicated in the message, where &str can be
allocating, opening, empty, or reading.
A directory access error has been detected when sending a list of file names or
a group of files based on a selection.
SEND FNAME = # FIL* or SEND FNAME = # DIR*.

Consequence If the directory is empty, Transfer CFT ignores the fact that the file is not
found, and passes the transfer to the X phase.

Action Ignore this error.

Transfer CFT 3.1.3 Troubleshooting Guide 176

3 Messages and error codes

Error CFTT45E : PART=&part IDF=&idf _ &char not allowed in filename

message

Explanation Generic file receive requests are not supported.

&char designates the indirection character (FILE_SYMB) specific to each
environment.

Consequence The transfer cannot be performed.

Warning CFTT46W: PART=&part ,IDF=&idf ,IDT=&idt _ Part inactive: mode &str

message

Explanation The transfer attempt for partner &part cannot succeed as the partner is
inactive in &str mode:
l &str= requester or
l &str = server

Error CFTT47E PART=&part IDF=&idf IDT=&idt PROTOCOL=&id _ Cannot find SSL

message security profil

Explanation The attempted transfer the &part partner cannot be performed because the
security profile was not found.

Consequence The transfer can not be carried out.

Error CFTT48E PART=&part IDF=&idf SSL=&id _ Server Session rejected

message reason=&reason

Explanation The attempted transfer the &part partner cannot be performed because the
security profile is not valid, with as an internal reason (&reason).

Consequence The transfer can not be carried out.

Action Note the REASON (&reason) value and contact the product support team if
necessary.

Warning message CFTT49W: Unable to send data to Synchronous task

Explanation Synchronous communication task is inaccessible.

Transfer CFT 3.1.3 Troubleshooting Guide 177

3 Messages and error codes

Error CFTT50E _ Duplicate transfer with IDTU=A0000001 <IDTU=A000000A

PART=BCLPM + IDF=HETERODUP IDT=B0915105>

Explanation A duplicate transfer occurred.

IDTU=A000001 is the previously performed transfer.
For more information see the DUPLICAT field details.

Information CFTT51I: PART=&part ,&str session opened

Information The session is open, the connection request has been accepted (requester side
(&str= requester if not secured, &str=SSL requester) or server (&str = server if
not secured , &str=SSL server if secured)).

Information CFTT52I: PART=&part ,&str session closed

Information The session is closed: requester side (&str = requester if not secured, &str = SSL
requester if secured) or server (&str = server if not secured , &str = SSL server if
secured).

Information CFTT53I: PART=&part IDF=&idf IDT=&idt ,&str file &str1

Information The file is selected (&str1 = selected) or created (&str1 = created) either by the
requester (&str = requester) or by the server (&str = server).

Information CFTT54I: PART=&part IDF=&idf IDT=&idt ,&str file deselected

Information The file is deselected either by the requester (&str = requester) or by the server
(&str = server).

Information CFTT55I: PART=&part IDF=&idf IDT=&idt ,&str file opened

Information The file is opened either by the requester (&str = requester) or by the server
(&str = server).

Transfer CFT 3.1.3 Troubleshooting Guide 178

3 Messages and error codes

Information CFTT56I: PART=&part IDF=&idf IDT=&idt ,&str file closed

Information The file is closed either by the requester (&str = requester) or by the server (&str
= server.

Information CFTT57I: PART=&part IDF=&idf IDT=&idt ,&str transfer started

Information The transfer has been started either by the requester (&str = requester) or by the
server (&str = server).

Information CFTT58I: PART=&part IDF=&idf IDT=&idt ,&str transfer ended

Information The transfer has been completed either by the requester (&str = requester) or by
the server (&str = server).

Information CFTT59I: PART=&part IDM=&idf IDT=&idt ,&str <message|reply> transferred

Information The message or the reply has been sent either by the requester (&str =
requester) or by the server (&str = server).

Information CFTT60I: &str

Information The &str message is an information message, sent by the file EXIT associated
with the transfer.

Error CFTT61E: PART=&part IDM=&idf IDT=&idt local message reject &diagi

message ,&diagp

Explanation The local partner rejects the message transfer.

Consequence The message transfer is not executed.

Action Correct the error and try again.

Transfer CFT 3.1.3 Troubleshooting Guide 179

3 Messages and error codes

Error CFTT62E: PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

message

Explanation The transfer was interrupted by the operator (&diagp = "OPER") or by the file
EXIT (&diagp represents the phase of the EXIT which prompted the
interruption = "ALLOC", "OPEN", TRANS or CLOSE).

Consequence The transfer is aborted. The corresponding catalog entry is set to HOLD (after a
HALT command from the operator or an interrupt by the EXIT), KEEP (after a
KEEP command from the operator).

Action After an interruption by the operator, the transfer can be restarted manually
(START command).
After interruption by a file EXIT, the action is to be defined by the engineers
responsible for this file EXIT.

Error CFTT62E: PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

message

Explanation The transfer was interrupted by the operator (&diagp = "OPER") or by the file
EXIT (&diagp represents the phase of the EXIT which prompted the
interruption = "ALLOC", "OPEN", TRANS or CLOSE).

Consequence The transfer is aborted. The corresponding catalog entry is set to HOLD (after a
HALT command from the operator or an interrupt by the EXIT), KEEP (after a
KEEP command from the operator).

Action After an interruption by the operator, the transfer can be restarted manually
(START command).
After interruption by a file EXIT, the action is to be defined by the engineers
responsible for this file EXIT.

Error message CFTT64E PART=part IDF=idf _ Default IDF not enable

Explanation The default IDF functionality is disabled for the command.

Consequence The transfer is not executed and has the status K.

Action For parameter details, see UCONF General unified configuration parameters.

Error CFTT65E PART=&part IDF=&idf IDT=&idt PROT=&prot _ Protocol not

message available

Transfer CFT 3.1.3 Troubleshooting Guide 180

3 Messages and error codes

Explanation The &prot protocol is not authorized for this partner.

Consequence The transfer is not executed, and the corresponding catalog entry is set to
KEEP. DIAGI=410 ,DIAGP = NO PROT

Action Check the PROT value in the SEND or RECV transfer.

Error CFTT66E Maximum number of partners authorized by license key reached

message (using PART=XXXXXX)

Explanation Transfer CFT license keys support either a limited or unlimited number of
partners. The transfer is treated as if the partner does not exist.

Consequence An error occurred because you have reached the maximum number of partners
allowed by your license key.

Action In a command line window, you can enter the command CFTUTIL ABOUT to
check the number of partners that your license key authorizes. For additional
information on license keys, contact an Axway sales representative.

Error CFTT71E: PART=&part IDF=&idf IDT=&idt remote creation reject &diagi

message ,&diagp

Explanation The file was not created, the internal &diagi code explains the reason for the
rejection (see the chapter on internal Transfer CFT codes).

Consequence The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error CFTT72E: PART=&part IDF=&idf IDT=&idt remote selection reject &diagi

message ,&diagp

Explanation The file was not selected; the internal &diagi code explains the reason for the
rejection (see the topic on internal Transfer CFT codes).

Consequence The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Transfer CFT 3.1.3 Troubleshooting Guide 181

3 Messages and error codes

Error CFTT72W: PART=&part IDF=&idf IDT=&idt remote selection (file not found
message ignored) reject &diagi ,&diagp

Explanation The file was not selected because the file is not found.

Consequence Transfer CFT ignores that the file is not found, and passes to the X phase.

Action Ignore the error.

Error CFTT73E: PART=&part IDM=&idf IDT=&idt &diagi ,&diagp

message

Explanation The message was not sent.

Consequence The message transfer is aborted. The corresponding catalog entry is put on
HOLD.

Action Correct the error and try again.

Error message CFTT74E: PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

Explanation The transfer was interrupted by the remote partner.

Consequence The transfer is aborted, the corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error CFTT75E: PART=&part IDF=&idf IDT=&idt connect reject &diagi ,&diagp

message

Explanation The connection request was rejected by the partner.

Consequence The transfer failed. If the called number was engaged or a network incident
occurred (for example), the transfer will be retried several times (see the
RETRYM, RETRYN and RETRYW parameters).
If all retries fail, the transfer is not executed and the corresponding catalog
entry is set to KEEP.

Action Analyze the internal &diagi error code for the transfer and try to correct it.

Transfer CFT 3.1.3 Troubleshooting Guide 182

3 Messages and error codes

Error message CFTT76E: PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

Explanation The write transfer request is refused.

Consequence The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error message CFTT77E: PART=&part IDF=&idf IDT=&idt &diagi ,&diagp

Explanation The read transfer request is refused.

Consequence The transfer is not executed. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error CFTT78E: PART=&part IDF=&idf IDT=&idt remote transfer end reject &diagi
message ,&diagp

Explanation A problem was detected at the end of the transfer.

Consequence The transfer has terminated but is not considered to be valid, the
corresponding catalog entry is set to DISP (transfer to be restarted), on HOLD
(the transfer may be restarted) or to KEEP.

Action Automatically by Transfer CFT or manually by the user (correct the error,
restart or try a new transfer).

Error CFTT79E: PART=&part IDF=&idf IDT=&idt remote deselect reject &diagi

message ,&diagp

Explanation The file could not be deselected.

Consequence The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error message CFTT80E: PART=&part IDF=&idf IDT=&idt remote open reject &diagi ,&diagp

Explanation The file could not be opened.

Transfer CFT 3.1.3 Troubleshooting Guide 183

3 Messages and error codes

Consequence The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error message CFTT81E: PART=&part IDF=&idf IDT=&idt remote close reject &diagi ,&diagp

Explanation The file could not be closed.

Consequence The transfer is interrupted. The corresponding catalog entry is put on HOLD.

Action Correct the error and try again.

Error message CFTT82E: PART=&part IDF=&idf IDT=&idt transfer aborted &diagi ,&diagp

Explanation A serious error was detected.

Consequence The transfer is interrupted and the corresponding catalog entry is set to KEEP.

Action Correct the error and try again.

Information CFTT83I: PART=&part IDF=&idf IDT=&idt change direction(CD) for request

Explanation This message is only displayed for the ODETTE protocol and a RECV command.
It indicates that the remote partner has accepted its turn to transmit.

Information CFTT86I FNAME=%­64.64s S=ByteCount

Explanation Name of the file sent or received and the number of bytes in the file. This
message completes the CFTT54I message.

Information CFTT86I FNAME=%­64.64s S=ByteCount

Explanation Name of the file sent or received and the number of bytes in the file. This new
message completes the CFTT54I message.

Information CFTT86I PART=&part Change direction(TURN) sent

Explanation In the case of PeSIT protocol in a DMZ profile, the token (TURN) has been sent
to the partner &part.

Transfer CFT 3.1.3 Troubleshooting Guide 184

3 Messages and error codes

Information CFTT87I Change direction (TURN) received PART=&part IDS=&ids

Information In the case of PeSIT protocol in a DMZ profile, the token (TURN) has been
received by the partner &part, where IDS is the reference for the session context.

Information CFTT88I FNAME=&fname NBC=&n;

Information This message completes the message CFTT54I.

The following fields indicated:
l fname: name of the file sent
l n: number of bytes in the file

Information CFTT89I: PART=&part IDF=&idf IDT=&idt Faction on FNAME=&fname :

message &str+"deleted" or "erased"

Explanation New delete or erase message for a file following the faction parameter for a
transfer command (either send or receive).
At the end of the transfer the file was either erased or deleted
(FACTION=ERASE or FACTION=DELETE).
l IDF=&idf
l IDT=&idt
l Faction on FNAME=&fname
l &str\n str = deleted or erased

Warning CFTT90W: IDF=&idf IDT=&idt Faction on FNAME=&fname : erase failed cs

message

Explanation At the end of a transfer, if the parameter FACTION=ERASE cannot be carried out
(for example, if the file is already used by another user) the transfer moves to
the T state.

Warning CFTT90W: IDF=&idf IDT=&idt Faction on FNAME=&fname : delete failed cs

message

Explanation At the end of a transfer, if the parameter FACTION=DELETE cannot be carried

out (for example, if the file is already used by another user) the transfer moves
to the T state.

Action Delete or erase the file manually.

Transfer CFT 3.1.3 Troubleshooting Guide 185

3 Messages and error codes

Warning CFTT91W Change direction (TURN) not supported by server PART=DMZ1

message IDS=&ids

Explanation When using the DMZ mode, if the server does not accept the TURN, the session
is closed by the requester without message. The IDS is the reference for this
session context.

Action This message is edited on LOG file.

Warning CFTT93W Negative ack not supported PART=&part IDS=&ids

message

Explanation The final partner signals to the initial file sender that application errors were
detected. This occurs via a negative acknowledgements sent in a PeSIT Hors SIT
message, where IDS is the reference for the session context.

Action None

Information CFTT94I PART=&part IDF=&idf IDT=&idt FCHARSET=&str NCHARSET=&str

Explanation This information message relates to the extended transcoding used for this
transfer.

Transfer CFT 3.1.3 Troubleshooting Guide 186

3 Messages and error codes

Transfer CFT messages: CFTW

This topic lists the CFTWxx and CFTXxx 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>

Warning CFTW01W: PART=&part IDF=&idf IDT=&idt Temporary file &file deleted

Explanation The &file temporary file was deleted at the end of the transfer. The name of this
file is declared in the WFNAME parameter of the CFTSEND and CFTRECV
commands.

Warning CFTW02W: CFTSEND &idsend override SEND parameters

Explanation The parameters of the SEND command are overridden by the parameters in the
associated CFTSEND command.

Warning CFTW03W: _ Send command: Unauthorized usage of IDF = &idf

Explanation The &idf IDF is not authorized for the SEND command. Check your software key
restrictions.

Warning CFTW04W: _ Recv command: Unauthorized usage on IDF = &idf

Explanation The &idf IDF is not authorized for the RECV command. See the restrictions
concerning the value of your software key.

Transfer CFT 3.1.3 Troubleshooting Guide 187

3 Messages and error codes

Warning CFTW05W: PART=&part IDF = &idf Temporary file unknown, WFNAME not
defined in SEND

Explanation The WFNAME was not set in the CFTSEND command when preparing a transfer
requiring additional processing and sending a group of files.

Action Modify the parameter settings using a different IDF for this type of transfer.

Warning CFTW07W: PART=&part IDF = &idf _ SELFNAME not authorized for COPY

Explanation You cannot use a selection file when implementing additional processing prior
to a transfer (IEBCOPY with MVS for example).

Consequence The transfer is not triggered.

Action Do not use a selection file; you can, however, specify a generic file name
(FNAME= #FIL1*, FNAME= #TFILM*).

Warning CFTW08W: CFTRECV &idrecv override RECV parameters

Explanation The RECV command parameters are overridden by the parameters set in the
associated CFTRECV command.

Warning CFTW09I: nidf&idf NIDF=&idt CFTSEND &idf IDT=&part IDF=&PART=

CFTW091: PART=&part IDF=&idf IDT=&idt CFTRECV &idf NIDF=&nidf

Explanation Indicates the ID of the CFTSEND or CFTRECV that was actually used.
Example
CFTW091 PART=SERVER IDF=TRTR
IDT=D1918581 CFTRECV IDFDEF NIDF=TRTR

Transfer CFT 3.1.3 Troubleshooting Guide 188

3 Messages and error codes

Transfer CFT messages: CFTY

This topic lists the CFTYxx (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 CFTY03E PID=&pid System error [&string] CR=&cr CS=&cs

Explanation A new SSL task cannot initialize its working environment. According to the error
origin, various messages are given below.

Result The SSL session in progress is aborted.

Error CFTY03E PID=&pid System error [MMALLOC] CR=&cr CS=&cs

Explanation Dynamic memory allocation failure.

Error CFTY03E PID=&pid System error [SYDEF] CR=&cr CS=&cs

Explanation Task semaphore creation failure:

l CR=­1 Maximum semaphore count reached
l CR=­2 Internal error
l CR=­9 System error

Error CFTY03E PID=&pid System error [SYPOST] CR=&cr CS=&cs

Explanation Semaphore write failure:

l CR=­1 Undefined or already closed semaphore
l CR=­2 Too many messages waiting in semaphore
l CR=­3 Message length too long
l CR=­9 System error

Transfer CFT 3.1.3 Troubleshooting Guide 189

3 Messages and error codes

Error CFTY03E PID=&pid System error [SYWAIT] CR=&cr CS=&cs

Explanation Semaphore read failure:

l CR=­1 Undefined semaphore
l CR=­3 Already closed semaphore
l CR=­9 System error

Error CFTY03E PID=&pid System error [CTXDEF] CR=&cr CS=&cs

Explanation SSL session context manager creation failure:

l CR=­2,­3 Dynamic memory allocation failure
l CR=­9 Maximum context manager count reached

Error CFTY03E PID=&pid System error [STARTPKI] CR=&cr CS=&cs

Explanation PKI internal error. The CS code is in the form « PKII nnn » for a Transfer CFT
internal PKI error or « PKIE nnn » for an external PKI error. nnn is a SSL alert
code.

Error CFTY04E PID=&pid PKIFNAME=&string Internal PKI error [&string] CR=&cr

CS=&cs

Explanation A new SSL task cannot read the index file of the local certificate data base.
This file name is set by the parameter PKIFNAME of the CFTPARM command.
According to the error origin, various messages are given below.

Result The SSL session in progress is aborted.

Error CFTY04E PID=&pid PKIFNAME=&string Internal PKI error [FMALLOC] CR=&cr

CS=&cs

Explanation File allocation failure:

l CR=­1: File not found
l CR=­3: File already allocated (exclusive mode) by another application
l CR=­9: System error

Error CFTY04E PID=&pid PKIFNAME=&string Internal PKI error [DMOPEN] CR=&cr

CS=&cs

Transfer CFT 3.1.3 Troubleshooting Guide 190

3 Messages and error codes

Explanation File open failure:

l CR=­1: File not allocated
l CR=­2: Invalid open mode
l CR=­3: Access conflict
l CR=­9: System error

Error CFTY04E PID=&pid PKIFNAME=&string Internal PKI error [DMGN] CR=&cr

CS=&cs

Explanation File read failure:

l CR=­9: System error

Error CFTY04E PID=&pid PKIFNAME=&string Internal PKI error [HPUT] CR=&cr

CS=&cs

Explanation File loading error:

l CR=­3: Dynamic memory allocation error when loading file

Error CFTY05E PID=&pid PKIFNAME=&file Syntax error _ &string

Explanation The index file of the local certificate data base is not valid. This file name is set
by the parameter PKIFNAME of the CFTPARM command. According to the error
origin, various reasons are given below:
l MISSING SECTION=TrustedCas: the file doesn’t contain a [TrustedCas]
section. This section is used to declare certificate authorities (CA)
l SECTION=TrustedCas IS EMPTY: [TrustedCas] section is empty
l BAD VALUE LINE=linenumber: Invalid syntax for a certificate or private key
statement. The line number in the file is displayed
l INVALID SECTION LINE=linenumber: Invalid syntax for a section statement.
The line number in the file is displayed

Result The SSL session in progress is aborted.

Action Rectify the index file.

Error CFTY06E CTX=&ctx Certificate Request Message error _ &string

Transfer CFT 3.1.3 Troubleshooting Guide 191

3 Messages and error codes

Explanation SSL handshake error: a request certificate message, sent by the server, is
invalid. According to the error origin, various reasons are given below:
l UNSUPPORTED TYPE FIELD: The server requires an authentication type
which is not supported by Transfer CFT.
l INVALID DN LENGTH: The DN (Distinguished Name) length is invalid

Result The SSL session in progress is aborted. An alert is sent to the server.

Error CFTY07E CTX=&ctx System error [&string] CR=&cr CS=&cs

Explanation SSL handshake error. According to the error origin, various messages are given
below.

Result The SSL session in progress is aborted. An alert is sent to the remote entity.

Error CFTY07E CTX=&ctx System error [MMALLOC] CR=&cr CS=&cs

Explanation Dynamic memory allocation failure.

Result If the SSL handshake is in progress, the session is aborted and an alert is sent
to the remote entity.
If the SSL session is established (handshake successful) the network session is
cleared.

Error CFTY07E CTX=&ctx System error [SYPOST] CR=&cr CS=&cs

Explanation Semaphore write failure:

l CR=­1 :The semaphore is undefined or already closed
l CR=­2: Too many messages are waiting on the semaphore
l CR=­3: The message length is too big
l CR=­9: System error

Error CFTY07E CTX=&ctx System error [CTXALLOC] CR=&cr CS=&cs

Explanation Memory allocation error for a new SSL session context:

l CR=­2,­3: Dynamic memory allocation failure
l CR=­9: Maximum context count reached

Error CFTY07E CTX=&ctx System error [CTXCHK] CR=&cr CS=&cs

Explanation Invalid message received from another Transfer CFT task (context is invalid or
already free).

Error CFTY07E PROT=&prot SSLPID=&pid HOST=&host synchronization error

CR=&cr CS=&scs

Transfer CFT 3.1.3 Troubleshooting Guide 192

3 Messages and error codes

Explanation Problem with sending an internal Transfer CFT message to the protocol task
during the SSL initialization phase

Consequence The transfer is aborted

Action Analyze the &scs code and contact the product support team if necessary

Information CFTY08I PID=&pid Task started successfully

Explanation Successful creation of a new SSL task.

Information CFTY09I PID=&pid Task ended

Explanation SSL task ended.

Error CFTY10E PID=&pid CTX=&ctx Invalid reference on &string

Explanation Invalid network message received (context is invalid or already free).

Result Message is not treated.

Information CFTY11I CTX=&ctx PART=&id SSL=&id Closing client SSL session

Explanation A client SSL session is closed. The session reference and the transfer partner are
displayed.

Information CFTY12I CTX=&ctx PROT=&id SSL=&id Closing server SSL session

Explanation A server SSL session is closed. The session reference and the protocol are
displayed.

Error CFTY13E CTX=&ctx SSL Handshake local error [&string] CR=&cr

Explanation SSL session handshake failure.

Transfer CFT 3.1.3 Troubleshooting Guide 193

3 Messages and error codes

Result The SSL session in progress is aborted. An alert is sent to the remote entity.

Action Call the Transfer CFT hot line.

Analyse the &cr error code (refer to the SSL protocol error codes) as well as the
&cr error code. Contact the product support team if necessary.

Information CFTY14I CTX=&ctx PART=&id SSL=&id client session established

CIPHER=&num AUTH=&mode

Explanation Successful handshake. A new client SSL session is established. The negotiated
cypher suite and the authentication mode (SERVER or BOTH) are displayed.

Information CFTY15I CTX=&ctx PROT=&id SSL=&id server session established

CIPHER=&num AUTH=&mode

Explanation Successful handshake. A new server SSL session is established. The negotiated
cypher suite and the authentication mode (SERVER or BOTH) are displayed.

Information CFTY16I CTX=&ctx &message

Explanation Message sent by the external PKI exit.

Information CFTY17I CTX=&ctx &msg

Explanation Specific exit security (PKI System) message.

Error CFTY18E CTX=&ctx &str

Transfer CFT 3.1.3 Troubleshooting Guide 194

3 Messages and error codes

Explanation Internal error on calling up the internal PKI. The "&str" field can have the
following values:
l PKI_NOT_TREATED : PKI function not treated
l PKI_ERR_CERT_BAD : Incorrect certificate (format error)
l PKI_ERR_CERT_UNSUPPORTED : Certificate not supported
l PKI_ERR_CERT_REVOKED : Certificate revoked
l PKI_ERR_CERT_EXPIRED : Certificate expired
l PKI_ERR_CERT_UNKNOWN : Certificate unknown
l PKI_ERR_CERT_NOT_VALID : Certificate not valid
l PKI_ERR_CERT_BAD_SIGN : Integrity error (incorrect signature)
l PKI_ERR_CERT_BAD_HASH : Integrity error (hash code incorrect)
l PKI_ERR_CERT_BAD_CA :Certification organism certificate invalid
l PKI_ERR_CERT_ALGO_UNSUPPORTED : Unsupported ciphering algorithm
l PKI_ERR_CERT_NOT_FOUND : User certificate not found
l PKI_ERR_CA_NOT_FOUND : Certification organism certificate not found
l PKI_ERR_BAD_KEY : Invalid ciphering key
l PKI_ERR_BUF_TOO_SHORT : Memory buffer size too small
l PKI_ERR_SYS : Internal error linked to the system (memory allotment,
system function, and so on)

l PKI_ERR_PARM : Ciphering parameter invalid

l PKI_ERR_OTHERS : Other error (authentication, ciphering, integrity, and so
on)

Consequence The transfer is aborted.

Action Contact the product support team if necessary.

Information CFTY19I PART=&id SSL=&id opening client session CTX=&ctx on task

PID=&pid

Explanation Handshake is started for a new client SSL session. Transfer CFT gives a unique
reference to it. Using this reference, the session could be tracked.

Information CFTY20I PROT=&id SSL=&id opening server session CTX=&ctx on task

PID=&pid

Explanation Handshake is started for a new server SSL session. Transfer CFT gives a unique
reference to it. Using this reference, the session could be tracked.

Transfer CFT 3.1.3 Troubleshooting Guide 195

3 Messages and error codes

Information CFTY21I CTX=&ctx Remote server certificate accepted ROOTID=&id

Explanation A server certificate is accepted during a session handshake. The authority

identifier which has signed the certificate is displayed.

Information CFTY22I CTX=&ctx Remote client certificate accepted ROOTID=&id

Explanation A client certificate is accepted during a session handshake. The authority

identifier which has signed the certificate is displayed.

Information CFTY23I CTX=&ctx Client certificate ID=&id ROOTID=&id

Explanation Client certificate used locally for authentication.

Information CFTY24I CTX=&ctx Server certificate ID=&id ROOTID=&id

Explanation Server certificate used locally for authentication.

Information CFTY25I CTX=&ctx remote address HOST=&string

Explanation This message is displayed after the message CFTY20I. It gives the address (HOST
name or IP address using TCP/IP network) of the remote connected entity.

Information CFTY26I: CTX=&ctx Anonymous &str session

Explanation Opening of a secure session without authentication in either client or server

mode. Refer to the Transfer CFT Online documentation.
l &ctx= context SSL
l str = client or server

Warning CFTY28W CTX=&ctx &str2 = &filename

Explanation The file contains the remote certificate has not been recorded.

Transfer CFT 3.1.3 Troubleshooting Guide 196

3 Messages and error codes

Consequence The transfer can be performed but the remote certificate is not recorded.

Action Write down the &str2 value and contact the product support team if necessary.

Error CFTY41E: CFTCTX=<session_reference>, xpp call <PassportPS_API_

function>: error [<PassportPS_API_function_returncode>]

Explanation An error occurred during an exchange or connection with the PassPort PS

server.
<PassportPS_API_function> and <PassportPS_API_function_returncode>
identify the function in error and provide the return code for the function.

Error CFTY44E: CFTCTX=<session_reference>, long err msg : [<PassportPS_API_

error_code>]

Explanation An error occurred during an exchange or connection with the PassPort PS

server. The <PassportPS_API_error_code> describes the error.

Error CFTY45E: CFTCTX=<session_reference>, <PassportPS_API_error_message>

Explanation An error occurred during an exchange or connection with the PassPort PS

server. The <PassportPS_API_error_message> describes the error.

CFTUTIL utility output messages: CFTunnx

You find the utility output in either the standard output or redirection file.

Error CFTU00I: &Cmd _ Correct (&str)

Information The &Cmd command is executed correctly. The &str string represents the
parameters passed with this command (up to 50 characters).

Error CFTU01E: storage allocation error

Explanation The communication utility could not acquire the memory required to run.

Consequence Immediate shutdown of the communication utility.

Transfer CFT 3.1.3 Troubleshooting Guide 197

3 Messages and error codes

Action Inform Product Support.

Error CFTU02E: unable to allocate file &Fname

Explanation Problem allocating the file containing the parameter setting commands.

Consequence Immediate shutdown of the communication utility.

Action Check the existence and state of the file, correct the error and then restart the
communication utility.

Error CFTU03E: unable to open file &Fname

Explanation Problem opening the file containing the parameter setting commands.

Consequence Immediate shutdown of the communication utility.

Action Check the characteristics of the file to be opened and inform Product Support
if necessary.

Error CFTU04E: error reading input file &Fname

Explanation Problem reading the file containing the parameter setting commands.

Consequence Immediate shutdown of the communication utility.

Action Check the characteristics of the file to be opened and inform Product Support
if necessary.

Error CFTU05E: &Cmd Failed _ Unexpected end of file (command)

Explanation The end of the file was reached before the end of the command (the last
character of the command line may be a comma).

Consequence Immediate shutdown of the communication utility.

Action Review the command syntax, correct the error and then restart the
communication utility.

Transfer CFT 3.1.3 Troubleshooting Guide 198

3 Messages and error codes

Error CFTU06E: unexpected end of file before new command

Explanation The end of the file was reached before the start of a new command (a
comment in the file read may not be closed).

Consequence Immediate shutdown of the communication utility.

Action Add an end of comment marker (*/) to the file and then restart the
communication utility.

Error CFTU07E: &Cmd Failed _ unexpected end of file (comments)

Explanation The end of the file was reached before the end of the command (a comment
inside the command may not be closed).

Consequence Immediate shutdown of the communication utility.

Action Add an end of comment marker (*/) in the command and then restart the
communication utility.

Error CFTU08E: &Cmd Failed _ missing parenthesis

Explanation An opening or closing parenthesis is missing in the command syntax.

Consequence Immediate shutdown of the communication utility.

Action Review the command syntax, correct the error and then restart the
communication utility.

Error CFTU09E: &Cmd Failed _ command size too large

Explanation The length of the command name is greater than 8.

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax, correct the error and then restart the
communication utility.

Error CFTU10E: &Cmd Failed _ unknown command

Explanation The command is unknown.

Transfer CFT 3.1.3 Troubleshooting Guide 199

3 Messages and error codes

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax in the Transfer CFT Online documentation. Correct
the error and restart the communication utility.

Error CFTU11E: &Cmd Failed _ keyword &Keyw too large

Explanation The length of the &Keyw keyword is greater than 8.

Consequence Immediate shutdown of the communication utility.

Action Check the description of this parameter in the Transfer CFT parameter index,
correct the error and then restart the communication utility.

Error CFTU12E: &Cmd Failed _ illegal separator for keyword &Keyw

Explanation A parameter separator in the &Cmd command is invalid.

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax being sure that the separator is a comma. Correct
the error and then restart the communication utility.

Error CFTU13E: &Cmd Failed_missing quote

Explanation A closing quote (') is missing in the value assigned to a command parameter.

Consequence Immediate shutdown of the communication utility.

Action Check the invalid parameter; correct the error and then restart the
communication utility.

Error CFTU14E: &Cmd Failed _ too many keywords

Explanation There are too many keywords for this command.

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax. Correct the error and then restart the
communication utility.

Transfer CFT 3.1.3 Troubleshooting Guide 200

3 Messages and error codes

Error CFTU15E: &Cmd Failed _ keyword &Keyw unknown or duplicate

Explanation The &Keyw keyword is unknown or appears twice in the command.

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax. Correct the error and then restart the
communication utility.

Error CFTU16E: &Cmd Failed _ keyword &Keyw missing

Explanation The &Keyw keyword, which is mandatory for the command, is missing.

Consequence Immediate shutdown of the communication utility.

Action Check the command syntax, correct the error and then restart the
communication utility.

Error CFTU17E: &Cmd Failed _ keyword &Keyw value out of bounds

Explanation The &Keyw keyword of the &Cmd command is numeric and its value has
exceeded the authorized limits.

Consequence Immediate shutdown of the communication utility.

Action Check the possible values for this parameter, correct the error and then restart
the communication utility.

Error CFTU18E: &Cmd Failed _ invalid value for keyword &Keyw

Explanation The value of the &Keyw keyword of the &Cmd command is not authorized
(numeric value for an alphabetic parameter for example).

Consequence Immediate shutdown of the communication utility.

Action Check the possible values for this parameter. Correct the error and then restart
the communication utility.

Error CFTU19E: CFTDEST Failed _ keywords FNAME and &str are mutually exclusive

Transfer CFT 3.1.3 Troubleshooting Guide 201

3 Messages and error codes

Explanation If &str=PART
The components of a broadcast list can either be described within the command
(PART = parameter) or in an external file (FNAME = parameter). These two
parameters are mutually exclusive.
If &str=IDF
The IDENTIFIERS authorized in the CFTAUTH command can either be described
within the command (IDF = parameter) or in an external file (FNAME =
parameter). These two parameters are mutually exclusive.

Error CFTU20I: &str

Explanation CFTUTIL command interpreter information messages.

The &str is self­explanatory and can be of several types:
l Execution header: Information messages indicating the product, release,
copyright and execution start date and time
l Execution report: Information messages indicating the number of commands
interpreted, the number of errors detected and the execution end date and
time
l Dynamic modification of a Transfer CFT partner state: Part = &part : &str1
The ACT or INACT command has been executed correctly (&str1 indicates the
change of state for the &part partner: initial state ­> final state). There are four
possible states for a partner:
l ACTIVEBOTH: Partner active in both modes (requester and server)
l NOACTIVE: Partner inactive in both modes
l ACTIVEREQ: Partner active in the requester mode
l ACTIVESERV: Partner active in the server mode

Error CFTU24W : &Cmd _ Warning (&str)

Explanation A CFTUTIL command was correctly interpreted but no information was given;
the &str field specifies the reason.
Example: a CFTUTIL LISTCAT command on an empty Transfer CFT catalog
causes the following message to be displayed:
CFTU24W : LISTCAT Warning (no record found).

Error CFTU26E : &Cmd _ Error (&str)

Transfer CFT 3.1.3 Troubleshooting Guide 202

3 Messages and error codes

Explanation When executing the command, an error was detected. The &str field can be set
to one of the following values. Note that the following list is not exhaustive, as
the &str field is relatively self­explanatory:
l Parameter file opening error: Execution of the &Cmd command (LISTPARM
for example) resulted in an error when opening the parameter file.
l Partners file opening error: Execution of the &Cmd command (LISTPART for
example) resulted in an error when opening the partner file.
l Catalog file opening error: Execution of the &Cmd command (LISTCAT for
example) resulted in an error when opening the catalog file.
l Media communication file opening error: Execution of the &Cmd command
(LISTCOM for example) resulted in an error when opening the
communication file.
l File creation error: An error was detected when creating and formatting the
Transfer CFT internal datafile (CFTUTIL CFTFILE
TYPE=CAT/LOG/PARM/PART/ command).
l File delete error: An error was detected when executing a request to delete a
Transfer CFT internal datafile (CFTUTIL CFTFILE TYPE= ,MODE=DELETE
command).
l Output file creating error cs=&scs: Execution of the &Cmd command
(COPYFILE for example) resulted in an error when creating the output file.
l Input file opening error cs=&scs: Execution of the &Cmd command
(COPYFILE for example) resulted in an error when opening the input file.

l &id: Partner record already exists: Command execution, e.g. writing

information to the Transfer CFT partner file, resulted in an attempt to add a
record that already existed in the file (the &Cmd command requested is
designated by &Id).
l &id: Partner record &str error (&str=writing/reading/selecting): Command
execution resulted in a write/read/article selection error in the file (the
&Cmd command requested is designated by &Id).
l &id: Parameter record already exists: Command execution, writing
information to the Transfer CFT parameter file, resulted in an attempt to add
a record that already existed in the file (&Id being the command identifier).
l &id: Invalid value for NRPART paramete:r Executing the CFTPART
command, writing information to the Transfer CFT partner file, resulted in
an attempt to add a record that already existed in the file (&Id being the
CFTPART command identifier). In this case, the NRPART parameter is
already assigned to an existing CFTPART command.
l &id: Non bijective table: The conversion table specified in the file referenced
by the CFTXLATE DIRECT=BOTH command is not bijective (&Id being the
command identifier). Check that the conversion table specified is bijective
or create one command for each transfer direction (DIRECT=SEND or

Transfer CFT 3.1.3 Troubleshooting Guide 203

3 Messages and error codes

DIRECT=RECV).
l No partner found: A partner activation or deactivation command (ACT or
INACT) resulted in an error. The identifier indicated (ACT ID=&Part) does
not correspond to an existing partner identifier (CFTPART ID=&Part).
l Media communication is full: A transfer command (SEND or RECV) could
not be written to the Transfer CFT communication file. The maximum
number of requests in the communication file that have not yet been
processed by the Transfer CFT has been reached.
l Incompatible compression parameters: Execution of the COPYFILE
command resulted in an error when checking the attributes (record length
or format, compression code or state).
l Compression error: Executing the COPYFILE command resulted in an error
during the compression process.
l Decompression error:Executing the COPYFILE command resulted in an error
during the decompression process.
l &id: command not authorized: The command specified by the user is not
authorized by the Transfer CFT security system (&id being the command
identifier)
l Habilitation opening error: An error was detected when initializing the
Transfer CFT security system; a file required by the system could not be
opened correctly. Check that the initialization file exists and is valid
(contains the operating rules and indirections pointing to the object and
action dictionaries) and ensure that the security system dictionary files exist.
l Create channel failed: An error was detected when creating the Transfer CFT
synchronous communication media. Check that you have enough memory.
l Open channel failed: An error was detected when opening the Transfer CFT
synchronous communication media. Check that the synchronous
communication process is launched.
l Channel read error: An error was detected when reading the Transfer CFT
synchronous communication media. Check that the synchronous
communication process is launched.
l Channel write error: An error was detected when writing in the Transfer CFT
synchronous communication media. Check that the synchronous
communication process is launched.
l Close channel failed: An error was detected when closing the Transfer CFT
synchronous communication media. Check that the communication media
is not already closed.

Consequence The command is ignored.

Action Check the parameter settings, analyze the &scs code if it is set and, if
necessary, inform Product Support.

Transfer CFT 3.1.3 Troubleshooting Guide 204

3 Messages and error codes

Error CFTU30E : &Cmd Failed _ Unable to create file &Fname

Explanation Execution of the &Cmd command resulted in an error during the file create
process.
Example: redirection of CFTUTIL information messages to an invalid report file
(CONFIG TYPE=OUTPUT,FNAME=&Fname command).

Consequence The command is ignored.

Action Check the validity of the file name and, if necessary, inform Product Support.

Transfer CFT 3.1.3 Troubleshooting Guide 205

3 Messages and error codes

DIAGI: Diagnostic codes

Transfer CFT internal diagnostic codes

This code provides general information on the cause of the error. It is independent of the operating
system and of the network access method used for the transfer. Some codes are specific to a
protocol. If so, this is indicated in the label.

Diagnostic code values

Codes with a value between 001 and 499 indicate a local issue; values between 501 and 999
correspond to a fault reported by the partner.

This means that when you troubleshooting, if the code is greater than 500 it refers to a remote
issue. To find the actual DIAG, subtract 500 from the displayed code. If the DIAG is 962, for
example, the issue is a remote problem corresponding to DIAG 462 (no data sent on network).

Event column in diagnostic codes

The Event column explains the possible cause of the transfer error. Brief information on the type of
error which caused the transfer failure:

l SYS: System error

l NET: Error detected by the network layers (Transfer CFT layers, manufacturer or network layers)
l PROT: Fault detected by the file transfer protocol
l FILE: Transferred file access error returned by the operating system
l DATA: Error accessing Transfer CFT basic data: parameter, partners, catalog, communication,
log, statistics and secondary indirection files (lists of partners, files, and so on)
l PARAM: Transfer execution error following a parameter setting error
l AUTH: Transfer denied following an authorization check by Transfer CFT
l OVER: The transfer cannot be executed because the monitor's resources are saturated or a
parameter setting limit has been exceeded
l OUT: The transfer request is aborted after the maximum number of retries
l USER: The transfer is interrupted following an action by the operator
l SSL: Incident detected by the secured protocol SSL

Transfer CFT 3.1.3 Troubleshooting Guide 206

3 Messages and error codes

Consequence column in diagnostic codes

The Consequence column provides information on the Transfer CFT behavior following a transfer
failure. The resulting status of the transfer D, H or K:

l D: the transfer can still be executed using the RESTART, NEXT, RETRY or COMMUT mechanisms
l H or K: the transfer is aborted, the error procedure and ASIT EXIT (PeSIT SIT) may be executed

Further transfer attempts

For the D status, the following are possible to execute the transaction:

l RESTART: the transfer has been interrupted. The monitor waits for a period fixed by the WSCAN
parameter (CFTCAT command) before trying to restart the transfer with the same access data. It
increments the restart counter for the protocol, the counter limit being determined by the
RESTART parameter (CFTPROT command).
l NEXT: the transfer has been interrupted. The monitor waits for a period fixed by the WSCAN
parameter (CFTCAT command) before trying to restart the transfer with the same access data. It
does not increment the restart counter. There is therefore no limit to the number of retries
following this error.
l RETRY: the transfer has been interrupted. The monitor waits for a period fixed by the RETRY*
parameters before trying to restart the transfer, without changing the partner access data (same
protocol, same network address. It increments the retry counter specific to the partner access
data, the counter limit being determined by the RETRYM parameter (CFTnetwork command).

l COMMUT (switching): the transfer has been interrupted. The monitor waits for a period fixed by
the WSCAN parameter (CFTCAT command) before trying to restart the transfer. It ignores the
transfer access data and tries a "switching" path to reach the partner: another dial number,
another protocol or a backup partner.

Note Protocol switching also means communication system (network) switching. The switching
mechanism does not provide for use of other network resources (CFTNET commands
associated via the CLASS) for a given protocol (CFTPROT command). Problems associated
with network resources are masked by the common network access method which
manages them.

In the case of an H or K status the transfer is aborted, the error procedure and ASIT EXIT (PeSIT SIT)
can be executed:

l ABORT: the transfer is aborted

l Execution of the error procedure if the transfer switches to the K or H status:
o EXECE: the procedure is executed. This is the procedure defined by CFTPARM EXEC*E
parameters. If these parameters are not set, the procedure is not executed.
l Execution of the ASIT EXIT in PeSIT SIT protocol:
o ASIT EXIT: if the transfer uses the PeSIT protocol SIT profile, the ASIT EXIT is executed. The
EXIT is executed before the error procedure is submitted, if necessary. If this indication is not
declared, the ASIT EXIT is not executed.

Transfer CFT 3.1.3 Troubleshooting Guide 207

3 Messages and error codes

The "No CAT" indication specifies that no catalog entry had been created for the transfer when the
error occurred. The transfer request is rejected.

Table 1. Internal diagnostic codes table

Code Event Consequence

0 The transfer has ASIT EXIT

terminated correctly Execution of normal EXECRF or EXECSF end of transfer
procedures

001 SYS: Error creating the H status ­ ABORT, EXECE, ASIT EXIT
message queue or
allocating the memory

002 Context definition error H status ­ ABORT, EXECE, ASIT EXIT

003 SYS ­ Context allocation H status ­ ABORT, EXECE, ASIT EXIT

error

004 MQCONN

005 MQOPEN

006 MQPUT

100 FILE ­ File input/output H status ­ ABORT, EXECE, ASIT EXIT

error

101 FILE ­ Error creating the H status ­ ABORT, EXECE, ASIT EXIT
receive file

102 1.FILE ­ Error allocating H status ­ ABORT, EXECE in requester mode, ASIT EXIT
the transfer file
2.FILE ­ The receive file H status ­ ABORT, EXECE, ASIT EXIT
cannot be allocated The file is deleted
(FDISP=OLD case)

103 1.FILE ­ The file cannot H status ­ ABORT, EXECE in requester mode, ASIT EXIT
be deleted before the
receive file is created H status ­ ABORT, EXECE in requester mode, ASIT EXIT in
(FACTION = DELETE ) requester mode
2.FILE ­ Error deleting
the sent file, if a
deletion has been
requested (FACTION =
DELETE)

Transfer CFT 3.1.3 Troubleshooting Guide 208

3 Messages and error codes

Code Event Consequence

104 1. FILE ­ Error opening H status ­ ABORT, EXECE, ASIT EXIT

the transfer file
2. FILE ­ The receive file
cannot be erased
(FACTION = ERASE):
file opening problem
3. FILE ­ Prior to
reception, the receive
file could not be
opened to check that it
was empty (FACTION =
VERIFY)

105 1. FILE ­ Error closing H status ­ ABORT, EXECE, ASIT EXIT

the transfer file
2. FILE ­ The receive file
cannot be erased
(FACTION = ERASE):
file closing problem
3. FILE ­ Prior to
reception, the receive
file could not be closed
after checking that it
was empty (FACTION =
VERIFY)
4. FILE ­ The sent file
cannot be deleted
following an erase
request (FACTION =
ERASE )

106 FILE ­ Error recording H status ­ ABORT, EXECE, ASIT EXIT

the current position in
the transfer file
(synchronization point
setting)

107 FILE ­ Error setting the H status ­ ABORT, EXECE, ASIT EXIT
pointer to a re­
synchronization point in
the file (for a transfer
restart)

Transfer CFT 3.1.3 Troubleshooting Guide 209

3 Messages and error codes

Code Event Consequence

108 1. FILE ­ Send file read H status ­ ABORT, EXECE, ASIT EXIT
error in data transfer
phase
2. FILE ­ Prior to
reception, the receive
file could not be read to
check that it was empty
(FDISP = VERIFY case)

109 FILE ­ Data write error in H status ­ ABORT, EXECE, ASIT EXIT
the receive file

110 1. FILE ­ The send file H status ­ ABORT, EXECE in requester mode, ASIT EXIT in
does not exist requester mode
2. FILE ­ The receive file H status ­ ABORT, EXECE in requester mode, ASIT EXIT in
to be created does not requester mode
exist, even though the
FDISP parameter
requires it
(FDISP=OLD). DIAGP is
then set to NO OLD

111 FILE ­ Insufficient space H status ­ ABORT in requester mode, EXECE in requester
to create the file mode, ASIT EXIT in requester mode

112 Nonexistent unit

113 FILE ­ The file to be H status ­ ABORT, EXECE in requester mode

created already exists,
even though the FDISP
parameter prohibits it
(FDISP = NEW). DIAGP
is then set to NO NEW

114 FILE ­ Data write error in H status ­ ABORT, EXECE, ASIT EXIT
the receive file: file
space full

Transfer CFT 3.1.3 Troubleshooting Guide 210

3 Messages and error codes

Code Event Consequence

115 1. FILE ­ The transfer H status ­ ABORT, EXECE in requester mode, ASIT EXIT in
owner is not authorized requester mode
to access the file H status ­ ABORT, EXECE in requester mode, ASIT EXIT in
2. FILE ­ The file cannot requester mode
be deleted before the
receive file has been
created (FDISP =
H status ­ ABORT, EXECE, ASIT EXIT
DELETE case)Protected
file
3. FILE ­ The sent file
cannot be deleted
following a deletion
request
(FACTION = DELETE
case) Protected file

120 PROT ­ Counter check H status ­ ABORT, EXECE, ASIT EXIT

error

121 USER ­ Interruption by H status ­ ABORT, EXECE, ASIT EXIT

the operator

122 SYS ­ Error allocating D status ­ RESTART

memory when the
transfer is executed

123 FILE ­ Error setting the H status ­ ABORT, EXECE, ASIT EXIT
pointer to a
resynchronization point
in the file: the restart
point requested by the
partner is incorrect

124 PROT ­ Error: transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted

125 Max LRECL error

126 FILE ­ LRECL error H status ­ ABORT, EXECE, ASIT EXIT

(record length)

127 FILE ­ The receive file is H status ­ ABORT, EXECE, ASIT EXIT
not empty (FDISP =
VERIFY case)

Transfer CFT 3.1.3 Troubleshooting Guide 211

3 Messages and error codes

Code Event Consequence

128 1. FILE ­ Error H status ­ ABORT, EXECE, ASIT EXIT

deselecting the file H status ­ ABORT, EXECE, ASIT EXIT
2. FILE ­ Error H status ­ ABORT, EXECE and ASIT EXIT unless there is an
deselecting the receive allocation error in sender server mode
file
3. FILE ­ Error accessing
the send file (allocating
or opening),
subsequent to a file
erase request (FACTION
= ERASE)

129 FILE ­ Error during file H status ­ ABORT, EXECE, ASIT EXIT
decompression

130 FILE ­ Error during file H status ­ ABORT, EXECE, ASIT EXIT
compression

131 PROT ­ IDF different on H status ­ ABORT, EXECE

ODETTE SELECT

132 PARAM ­ Error accessing K status ­ ABORT

the parameter setting If the file does not exist, no transfer is executed. Only the
indirection file (list of generic request remains in the catalog. If an error occurs
files, list of partners) while reading the indirection file, the transfers generated
for the items (files or partners) that have already been
read are executed

133 PARAM ­ The FOR No catalog entry

parameter in the
CFTDEST command is
invalid
1. FOR=LOCAL when in
the switching mode
2. FOR=COMMUT when
not in the switching
mode

134 FILE ­ CFTEXIT call error H status ­ ABORT, EXECE, ASIT EXIT

135 1. FILE ­ The send file is D status ­ RESTART

locked
2. FILE ­ The receive file H status ­ ABORT, EXECE, ASIT EXIT
is locked

Transfer CFT 3.1.3 Troubleshooting Guide 212

3 Messages and error codes

Code Event Consequence

136 FILE ­ Duplication of the H status ­ ABORT, EXECE, ASIT EXIT

temporary file

137 FILE ­ The file exists, the H status ­ ABORT, EXECE, ASIT EXIT
"rename" operation is
therefore impossible

138 1. FILE ­ No temporary State K ­ ABORT

file has been defined in
the send mode and the
transfer requires the
COPY mechanism. No
transfer is triggered and
the generic request
remains in the catalog State K ­ ABORT, EXECE, ASIT EXIT
2. FILE ­ No temporary
file has been defined in
the receive mode for a
file with versions or for
a transfer requiring
deconcatenation
(COPY)

139 Incorrect attributes file

140 Invalid spacing

141 Cannot create directory

142 FILE ­ The "rename" H status ­ ABORT, EXECE, ASIT EXIT

operation failed

143 FILE LREC error

144 MVS transfer busy State D ­ Retry

145 1. The SEND file is K status ­ ABORT

outside of the
workingdir tree.
2. The temporary
SEND file is outside
of the workingdir
tree.

Transfer CFT 3.1.3 Troubleshooting Guide 213

3 Messages and error codes

Code Event Consequence

148 1. The RECV file is K status ­ ABORT

outside of the
workingdir tree.
2. The temporary
RECV file is outside of
the workingdir tree.

150 PARAM ­ Error accessing State K ­ ABORT. If the directory does not exist, no
the parameter setting transfers are triggered and only the generic request
indirection file when the remains in the catalog. If an error is detected when
file is a directory reading the directory, the transfers generated for the
items (directory menus) that have already been read are
triggered

151 PARAM ­ The selection State K ­ ABORT. Only the generic request remains in the
file cannot be used on catalog. No transfers are activated.
the directory specified

152 FILE ­ Error during the State H ­ ABORT, EXECE, ASIT EXIT
concatenation phase at
the start of the transfer
or during the de­
concatenation phase at
the send of the transfer.

153 FILE ­ Error during the State K ­ Short transfer cannot be restarted.
transfer. The file has
been overwritten.

154 An error occurred when Generates a DIAGI=730, DIAGP=ABO 399 on the remote
trying to transcode a file side as the sender cannot transcode before sending.
using NCHARSET See also DIAGC.
parameter in the
CFTSEND command
before a send.

Transfer CFT 3.1.3 Troubleshooting Guide 214

3 Messages and error codes

Code Event Consequence

155 This preprocessing error Generates:

occurs when a preexec
l DIAGP: NO EXEC
is specified, but
launching the exec file l DIAGC: PREEXEC LAUNCH ERROR
failed (usually because
the file was not found,
but could be due to a
busy or migrated file on
z/OS).
For details, see the
UCONF parameter
cft.server.transfer.raise_
error_when_exec_not_
found.

160 Handles the event 'no No catalog entry is created.

outstanding transfer or
implicit declaration'.

200 An error occurred on a

child transfer of this
parent (generic)
transfer. Refer to the
child transfer in error for
more information.

203 PROF=SIT non­priority

transfer

220 PROT ­ FPDU reception H status ­ ABORT, EXECE, ASIT EXIT

221 PROT ­ Int/ext type H status ­ ABORT, EXECE, ASIT EXIT

match error: the type of
a PI is not consistent
with its conversion type
in the external format
(for example, a PI in
DATE format to be
converted to the
STRING format)

222 PROT ­ Mandatory PI H status ­ ABORT, EXECE, ASIT EXIT

missing in FPDU

223 PROT ­ Invalid PI length H status ­ ABORT, EXECE, ASIT EXIT

Transfer CFT 3.1.3 Troubleshooting Guide 215

3 Messages and error codes

Code Event Consequence

224 PROT ­ Invalid PGI H status ­ ABORT, EXECE, ASIT EXIT

length

225 PROT ­ PGI missing H status ­ ABORT, EXECE, ASIT EXIT

from the FPDU

226 PROT ­ PGI embedded H status ­ ABORT, EXECE, ASIT EXIT

in another PGI

230 PROT ­ Protocol error. A H status ­ ABORT, EXECE, ASIT EXIT

protocol error has been
detected: DIAGP is set
to the PeSIT or ODETTE
code of the error
detected

231 PROT ­ Invalid action H status ­ ABORT, EXECE, ASIT EXIT

232 PROT ­ Event not H status ­ ABORT, EXECE, ASIT EXIT

found. An interaction
not recognized by the
protocol mechanisms
has been received in a
given transfer context

233 PROT ­ Message send K status ­ ABORT

operation refused by
the protocol used. The
following protocols do
not support message
send operations: PESIT
SIT, PESIT EXT,
ODETTE

240 PROT ­ Time­out D status ­ RETRY/COMMUT

expired (RTO
parameter)

241 Transfer time­out ­

requester

241 Transfer time­out ­

server

243 Network connection

time­out

Transfer CFT 3.1.3 Troubleshooting Guide 216

3 Messages and error codes

Code Event Consequence

244 Pre­connection time­

out

260 SSL ­ Security problem K state ­ ABORT

261 SSL ­ Error linked to an K state ­ ABORT

internal PKI

262 SSL ­ Error linked to the K state ­ ABORT

PKI system

263 SSL ­ Error linked to an K state ­ ABORT

external PKI

278 SSL ­ Invalid security K state ­ ABORT

profile

279 Requester opposition

280 SSL ­ Client not K state ­ ABORT

authorized

281 SSL ­ Insufficient K state ­ ABORT

authentication level

282 Embedding required

283 Encoding required

284 Signature required

285 Double signature

required

286 Closed service file

287 Sever does not

recognize this bank
(entity)

288 File type not supported

289 Secondary client id not

recognized

Transfer CFT 3.1.3 Troubleshooting Guide 217

3 Messages and error codes

Code Event Consequence

290 Secondary bank id not

recognized

291 First signatory is invalid

292 Second signatory is

invalid

293 First signatory

mechanism conflict

294 Second signatory

mechanism conflict

295 File type is not

compatible

301 NET ­ Network D status ­ COMMUT

addressing error (dial The transfer will be retried for a minimum period equal to
number) at the time of the WSCAN parameter of the CFTCAT command. The next
connection partner address in the DIALNO parameter list (CFTnetwork
command) will be used for the next retry. If the invalid
address is the last one in the list, the next protocol in the
PROT parameter list (CFTPART command) will be used for
the next retry. If the protocol used is the last in the list,
the transfer is either switched to the backup partner
(IPART parameter of the CFTPART command) or aborted
(K status) with code 405, while maintaining the
diagnostic code of the last retry

302 NET ­ Network link D status ­ RETRY/COMMUT

broken (cut­off, time­ Up to "RETRYM" retries are performed for the transfer and
out) outside the the access data. If the number of retries reaches the value
connection phase. in the RETRYM parameter, Transfer CFT "switches" the
DIAGP is then set to access data. The partner access data for the next retry will
VNRELI relate to the next DIALNO parameter (CFTNET command),
or the next PROT parameter (CFTPART command). The
restart counter is reset to 0. If the protocol used is the last
in the list, the transfer is either switched to the backup
partner (IPART parameter of the CFTPART command) or
aborted with code 405, while maintaining the diagnostic
code (DIAGP) of the last retry

Transfer CFT 3.1.3 Troubleshooting Guide 218

3 Messages and error codes

Code Event Consequence

303 NET ­ Network D status ­ COMMUT

parameter error at the The transfer is retried using the next protocol in the PROT
time of connection parameter list (CFTPART command) as the new partner
access point. If the protocol used is the last in the list, the
transfer is either switched to the backup partner (IPART
parameter of the CFTPART command) or aborted (K
status) with code 405, while maintaining the diagnostic
code of the last retry (see below)

304 Requester not

authorized (PESIT)

350 The user requesting the State H

transfer is not
authorized to perform it

351 The remote requester is State H

not authorized to use
the transfer. The
transfer was in the H
state. The monitor is
running in the
server/sender mode

352 The remote requester is State H

not authorized to create
a transfer. The monitor
is running in the
server/sender mode and
the transfer was to be
created via a CFTSEND
IMPL=YES

401 PARAM ­ Embedded K status ­ ABORT

broadcast list explicitly In the case of an explicit "multi­partner" request (PART
refused parameter in the CFTDEST command), a single partner,
itself defined as a partner list, aborts the request; only the
generic list request set to the K status remains in the
catalog. No transfer is executed. In the case of a "multi­
partner" request via an indirection file (FNAME parameter
in the CFTDEST command), only the requests prior to the
error are executed

Transfer CFT 3.1.3 Troubleshooting Guide 219

3 Messages and error codes

Code Event Consequence

402 PARAM ­ The PROT K status ­ ABORT

parameter of the
CFTPART command
does not belong to the
active protocol list
(PROT parameter of the
CFTPARM command)

403 PARAM: Invalid No CAT

password

404 PARAM: Open mode not No CAT (in server mode)

authorized

405 OUT: The monitor has K status ­ ABORT, EXECE, ASIT EXIT
tried all possible partner
access points: DIALNO,
PROT, IPART

Transfer CFT 3.1.3 Troubleshooting Guide 220

3 Messages and error codes

Code Event Consequence

406 1. OUT ­ Maximum K status ­ ABORT, EXECE

number of retries
reached (RESTART
parameter).
K status ­ ABORT, EXECE
DIAGP is set to MAXRST
2. AUTH ­ The required
start time for execution
of the transfer is outside
the authorized time slot K status ­ ABORT, EXECE
(OMINTIME /
OMAXTIME); there is no
other possible protocol
K status ­ ABORT, EXECE
for this partner. DIAGP
is set to CALL OUT
3. AUTH ­ The network
resource associated K status ­ ABORT, EXECE
with the protocol does
not accept outgoing
calls; there is no other
possible protocol for
K status ­ ABORT, EXECE
this partner
DIAGP is set to L 0B 022
4. PARAM ­ There is no
CFTN command for the
partner and for the last
protocol in the list
(CFTPART PROT
parameter). DIAGP is set
to MAXRST
5. OVER ­ The monitor
has reached the limit
(RESTART parameter)
of authorized retries for
the last partner protocol
(CFTPART PROT
parameter). DIAGP is set
to MAXRST
6. PARAM ­ The SROUT
parameter of the
protocol cannot be
used to execute the
transfer; there is no
other possible protocol
for this partner. DIAGP
is set to SROUT

Transfer CFT 3.1.3 Troubleshooting Guide 221

3 Messages and error codes

Code Event Consequence

407 PARAM ­ Paramètre Etat K ­ ABORT

NIDF inconnu

408 PARAM ­ PART K status ­ ABORT

parameter not described If a single CFTPART command is missing from an explicit
by a CFTPART "multi­partner" request (PART parameter in the CFTDEST
command command), the request is aborted. Only the generic list
request, set to the K status, remains in the catalog
No transfer is executed
In the case of a "multi­partner" request via an indirection
file (FNAME parameter in the CFTDEST command), only
transfers with no partner defined are halted
The other transfers are executed
NOTE: Complete broadcasting (or collection) will be
unsuccessful without operator intervention (partner
definition and transfer retry). The end of transfer
procedure will not be executed.

409 PARAM ­ Unknown H status ­ ABORT

NPART parameter

410 PARAM ­ Unknown K status ­ ABORT

CFTPROT command

411 AUTH ­ File identifier K status ­ ABORT

(IDF) not authorized If the IDF for one of the partners in an explicit "multi­
partner" request (PART parameter in the CFTDEST
command) is not authorized, the request is aborted; only
the generic list request set to the K status remains in the
catalog
No transfer is executed
In the case of a "multi­partner" request via an indirection
file (FNAME parameter in the CFTDEST command), only
transfers, the IDFs of which are not authorized for the
partner (CFTAUTH command) are set to halted
The other transfers remain active. Note:however,
complete broadcasting (or collection) will be
unsuccessful without operator intervention (grant
authorization to the partners and retry the transfer); the
end of transfer procedure will not be executed

412 DATA ­ Catalog access As the file could not be accessed, there is no change in
error the status or in the catalog DIAGI

Transfer CFT 3.1.3 Troubleshooting Guide 222

3 Messages and error codes

Code Event Consequence

413 AUTH ­ File identifier H status ­ ABORT

not authorized

414 1. AUTH ­ The start time K status ­ ABORT

for execution of the
transfer is outside the
authorized time slot
(MAXTIME / MAXDATE
of the SEND / RECV
command)
DIAGP is then set to
OUT TIME K status ­ ABORT
2. PARAM ­ The
outgoing time slot of
the partner is null
K status ­ ABORT
(OMINTIME /
OMAXTIME)
There is no intermediate
partner
DIAGP is then set to
CALL OUT
3. AUTH ­ No outgoing
call authorized for the
network resource
(CFTnetwork
CNXOUT=0)
DIAGP is then set to NO
CALL

415 OVER ­ Maximum D status ­ NEXT

number of partners
reached

Transfer CFT 3.1.3 Troubleshooting Guide 223

3 Messages and error codes

Code Event Consequence

416 1. OVER ­ Maximum D status ­ NEXT

number of transfers
reached (MAXTRANS D status ­ NEXT
parameter)
This status corresponds to a transfer refusal by the
The transfer cannot be protocol task of the monitor, even though the scheduler
executed has not reached the MAXTRANS limit
DIAGP is then set to This occurs when the protocol task maintains active
MAXTRANS connections after transfers have ended
2. OVER ­ Maximum
number of connections
reached for the network
resource
The transfer cannot be
executed
DIAGP is then set to
MAXCNX

417 1. OVER ­ Maximum D status ­ NEXT

number of file tasks
reached (MAXTASK
parameter)
The transfer cannot be
executed
D status ­ NEXT
2. SYS­ Insufficient
system resources
available to execute an
EXIT task
The transfer cannot be
executed

418 OVER ­ The total D status ­ RESTART

number of transfers in If the number of retries exceeds the value of the RESTART
progress exceeds one of parameter (CFTPROT command), the monitor switches to
the CNXIN, CNXOUT or the access data of the next protocol for this partner
CNXINOUT parameters
for the partner
The transfer cannot be
executed

419 DATA ­ The transfer to ABORT

be retried is not in the
catalog at the server
end

Transfer CFT 3.1.3 Troubleshooting Guide 224

3 Messages and error codes

Code Event Consequence

420 DATA ­ On reception of ABORT

a REPLY­type message,
the original transfer
concerned by this reply
is not found in the
catalog at the server
end

421 1. SYS ­ Error executing D status ­ NEXT

a monitor file task
2. SYS ­ Error executing
a monitor EXIT task K status ­ ABORT

423 SYS or PARAM ­ EXIT H status ­ ABORT

task creation error

424 PARAM ­ CFTXLATE H status ­ ABORT

command not found for
this transfer direction
and the source and
target alphabets

425 USER (Directory Exit) ­ No CAT

Call collect refused.

426 USER (Directory Exit) ­ No CAT (server mode)

Error in the Directory State K ­ ABORT (requester mode)
Exit task

428

430 PARAM ­ Transfer is State D ­ ACT

inactive on the
requester side

431 USER (Security) ­ No CAT

CFTAPPL card is absent

432 Duplicate transfer error

433 User/password error

434 AUTH ­ File identifier K status ­ ABORT

(default IDF) is not
authorized

Transfer CFT 3.1.3 Troubleshooting Guide 225

3 Messages and error codes

Code Event Consequence

451 1. PROT ­ (PeSIT) D status ­ RESTART

Reception of a protocol
connection refusal
(AckCONNECT FPDU).
D status ­ RESTART
(Odette) Reception of a
protocol connection
refusal (ESID). DIAGP is
then set to RELEASE
2. PROT ­ (PeSIT) D status ­ RESTART
(Odette) Violation of
the protocol
specifications
(unknown FPDU, or
invalid contents for
example). DIAGP is then
set to ACO in or RCO in
ennsnn
3. PROT ­ (PeSIT)
(Odette) Connection
time­out reached
without response
(DISCTC parameter of
the CFTPROT
command). DIAGP is
then set to TIMEOUT

452 PROT ­ (PeSIT) (Odette) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
message confirmation
FPDU

453 PROT ­ (PeSIT) (Odette) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
create confirmation
FPDU

454 PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
select confirmation
FPDU

455 PROT ­ (PeSIT) (Odette) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
deselect confirmation
FPDU

Transfer CFT 3.1.3 Troubleshooting Guide 226

3 Messages and error codes

Code Event Consequence

456 PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
open confirmation
FPDU

457 Reception of a negative

closed confirmation

458 Reception of a negative

read confirmation

459 PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
write confirmation
FPDU

460 PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT

Reception of a negative
end of transfer
confirmation FPDU

461 Received an abort with

diagnostics

462 No data sent on

network

463 Logon entry not

recognized

470 Expired password

471 PROT ­ (EBICS) H status ­ ABORT

Protocol recoverable
error. See DIAGP,
DIAGC.

472 PROT ­ (EBICS) K status ­ ABORT

Protocol non­
recoverable error. See
DIAGP, DIAGC.

473 PROT ­ (EBICS) invalid K status ­ ABORT

order type

Transfer CFT 3.1.3 Troubleshooting Guide 227

3 Messages and error codes

Code Event Consequence

474 PARAM ­ (EBICS) An K status ­ ABORT

error caused by the
signature file has been
detected. See DIAGC.

475 PARAM ­ (EBICS) K status ­ ABORT

mandatory parameter is
missing. See DIAGC.

499 ( ODETTE) CD okay

Codes with a value between 001 and 499 indicate a local issue; values between 501 and 999
correspond to a fault reported by the partner.
Therefore when troubleshooting if the code is greater than 500 it refers to a remote issue. To
find the actual DIAG, subtract 500 from the displayed code. If the DIAG is 916, for example,
the issue is a remote problem corresponding to DIAG 416 (Maximum number of transfers
reached).

500 Constant to add to a

remote11 code

600 FILE ­ (PeSIT) (Odette) H status­ ABORT, EXECE, ASIT EXIT

Transfer aborted by the
remote 1 end: file
input/output error ­
PeSIT / Odette code:
see DIAGP

604 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
1end: file opening error

605 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
11 end: file closing error

1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.

Transfer CFT 3.1.3 Troubleshooting Guide 228

3 Messages and error codes

Code Event Consequence

610 FILE ­ (PeSIT) (Odette) H status ­ ABORT, EXECE, ASIT EXIT

Transfer aborted by the
remote1 end: the file to
be read does not exist

611 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: insufficient space
to create the file

613 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: the file to be
created already exists

614 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: file space full

620 PROT ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: counter control
error

621 PROT ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: interruption by the
operator

626 PROT ­ (PeSIT) (Odette) H status ­ ABORT, EXECE, ASIT EXIT

Transfer aborted by the
remote1 end: error in
record length

635 FILE ­ (PeSIT) Transfer H status ­ ABORT, EXECE, ASIT EXIT

aborted by the remote1
end: file access conflict

1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.

Transfer CFT 3.1.3 Troubleshooting Guide 229

3 Messages and error codes

Code Event Consequence

660 REC (PeSIT) ­ Error H state ­ Transfer aborted by the remote1 end: no
660, ASE 205 on the outstanding transfer
requester side

720 1. PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT

Protocol abort by the
remote1 end: incorrect H status ­ ABORT, EXECE, ASIT EXIT
FPDU (transmission
error)
2. PROT ­ (Odette)
Protocol abort by the
remote1 end:
negotiation error

722 PROT ­ (PeSIT) Protocol H status ­ ABORT, EXECE

abort by the remote1 H status ­ ABORT, EXECE, ASIT EXIT
end: missing PI

730 1. PROT ­ Protocol error H status ­ ABORT, EXECE, ASIT EXIT

2. PROT ­ (PeSIT) H status ­ ABORT, EXECE, ASIT EXIT
Transfer aborted by the
remote1 end due to H status ­ ABORT, EXECE
protocol error ­ PeSIT
code: see DIAGP
3. PROT ­ (Odette)
Reception of an ESID
FPDU

740 NET ­ (PeSIT) Transfer D status ­ RETRY

aborted by the remote1
end: time­out ­ PeSIT
code: 317

850 PROT ­ (PeSIT) Protocol H Status ­ ABORT, EXECE

rejection by the remote1
end: authorization
problem

1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.

Transfer CFT 3.1.3 Troubleshooting Guide 230

3 Messages and error codes

Code Event Consequence

904 PROT ­ (PeSIT) Protocol H status ­ ABORT, EXECE, ASIT EXIT

rejection by the remote1
end: transfer denied
(open mode,
authorizations for
example)

909 PROT ­ (PeSIT only) D status ­ RESTART

Protocol rejection by
the remote1 end:
requestee identifier
unknown

916 PROT ­ (PeSIT only) D status ­ NEXT

Maximum number of
transfers reached at the
partner end (MAXTRANS
parameter)

919 Restart context not H status ­ ABORT, EXECE

available

920 PROT ­ (PeSIT) Protocol D status ­ RESTART

rejection by the remote1
end: on reception of a
REPLY­type message,
the partner does not
find the transfer
concerned by this reply
in its catalog

925 Call collect refused by No CAT

the remote1 system

928 Invalid caller number H status ­ ABORT, EXECE

930 PROT ­ Partner is ACT status

inactive on the server
side

1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.

Transfer CFT 3.1.3 Troubleshooting Guide 231

3 Messages and error codes

Code Event Consequence

933 Error in password

management parameter
RPASSWD or
SPASSWD: non­
authorized requester
identification

963 PROT ­ Protocol pre­ K status ­ ABORT, EXECE, ASIT EXIT

connection phase
rejected by the remote1
end (PeSIT LOGON):
LOGON string rejected

970 PROT ­ Protocol pre­ K status ­ ABORT, EXECE, ASIT EXIT

connection phase
rejected by the remote1
end (PeSIT LOGON):
password expired

1 For values between 501 and 999, check on the partner side.
1 For values between 501 and 999, check on the partner side.

Transfer CFT 3.1.3 Troubleshooting Guide 232

3 Messages and error codes

DIAGP: Event codes

This code is common to all protocols. When a value is specific to a protocol, the indication appears
in brackets.

In the case of the PeSIT protocol, this code forms part of the "eNNsNN"­type PeSIT DIAGP.

Table 2. Event Codes for all protocols

Code Meaning

00 VFABORTD ­ Transfer abort request by Transfer CFT

01 VFCAND ­ Transfer interrupt request by Transfer CFT

02 VFCANR ­ Response to a transfer interrupt indication

03 VFCHKD ­ Request to set a synchronization point

04 VFCHKR ­ Response to a synchronization point indication

05 VFCLOSD ­ Request to close file

06 VFCLOSRN ­ Negative response to a file close indication

07 VFCLOSRP ­ Positive response to a file close indication

08 VFCONRN ­ Negative response to a connect indication

09 VFCREAD ­ Request to create a file

10 VFCREARN ­ Negative response to a file create indication

11 VFCREARP ­ Positive response to a file create indication

12 VFDATAD ­ Request to send data

13 VFDSELD­ Request to select a file

14 VFDSELRN ­ Negative response to a select indication

15 VFDSELRP ­ Positive response to a select indication

16 VFDTNDD ­ End of data request

17 VFECOND ­ Request to connect in WRITE mode

18 VFECONRP ­ Positive response to a connect indication

Transfer CFT 3.1.3 Troubleshooting Guide 233

3 Messages and error codes

Code Meaning

19 VFLCOND ­ Request to connect in READ mode

20 VFLCONRP ­ Positive response to a connect indication

21 Not used

22 VFOMSGD ­ Request to send a message

23 VFOMSGRN ­ Negative response to a message indication

24 VFOMSGRP ­ Positive response to a message indication

25 VFOPEND ­ Request to open a file

26 VFOPENRN ­ Negative response to a file open indication

27 VFOPENRP ­ Positive response to a file open indication

28 VFRDY ­ Internal induction for the automaton table

29 VFRDYD ­ Internal induction for the automaton table

30 VFREADD ­ Request to read a file

31 VFREADRN ­ Negative response to a read request

32 VFREADRP ­ Positive response to a read request

33 VFRELD ­ Network close request

34 VFRELR ­ Response to network close request

35 Not used

36 VFRSTAR ­ Response to a re­synchronization request

37 VFSELD ­ Request to select a file

38 VFSELRN ­ Negative response to a select request

39 VFSELRP ­ Positive response to a select request

40 VFTRD ­ Request to start up a new transfer

41 VFTRNDD ­ Request to end a transfer

42 VFTRNDR ­ Response to an end of transfer request

Transfer CFT 3.1.3 Troubleshooting Guide 234

3 Messages and error codes

Code Meaning

43 VFTRNDRN ­ Negative response to an end of transfer

44 VFTRNDRP ­ Positive response to an end of transfer

45 VFWRITD ­ Request to write a file

46 VFWRITRN ­ Negative response to a write request

47 VFWRITRP ­ Positive response to a write request

48 VLOGD ­ Request to send a pre­logon message

49 VLOGRN ­ Negative response to a pre­logon message

50 VLOGRP ­ Positive response to a pre­logon message

51 Not used

52 VNCONRP (NETWORK) ­ Positive response to an incoming call

53 Not used

54 VNRELC (NETWORK) ­ Confirmation of network outage

55 VNRELI (NETWORK) ­ Network outage indication

56 VRABORT (PESIT) ­ Reception of an ABORT FPDU

57 VRACK (PESIT) ­ Reception of a pre­logon acknowledgment

58 VRACON (PESIT) ­ Reception of an AckCONNECT FPDU

59 VRACREAN (PESIT) Reception of a negative AckCREATE FPDU

60 VRACREAP (PESIT) Reception of a positive AckCREATE FPDU

61 VRACRFN (PESIT) ­ Reception of a negative AckCRF FPDU

62 VRACRFP (PESIT) ­ Reception of a positive AckCRF FPDU

63 VRADSELN (PESIT) ­ Reception of a negative AckDESELECT FPDU

64 VRADSELP (PESIT) ­ Reception of a positive AckDESELECT FPDU

65 VRAIDT (PESIT) ­ Reception of an AckCANCEL FPDU

66 VRAOMSGN (PESIT) ­ Reception of a negative AckMESSAGE FPDU

Transfer CFT 3.1.3 Troubleshooting Guide 235

3 Messages and error codes

Code Meaning

67 VRAOMSGP (PESIT) Reception of a positive AckMESSAGE FPDU

68 VRAORFN (PESIT) ­ Reception of a negative AckORF FPDU

69 VRAORFP (PESIT) ­ Reception of a positive AckORF FPDU

70 VRAREADN (PESIT) ­ Reception of a negative AckREAD FPDU

71 VRAREADP (PESIT) ­ Reception of a positive AckREAD FPDU

72 VRARESY (PESIT) ­ Reception of an AckRESYN FPDU

73 VRASELN (PESIT) ­ Reception of a negative AckSELECT FPDU

74 VRASELP (PESIT) ­ Reception of a positive AckSELECT FPDU

75 VRASY (PESIT) ­ Reception of a synchronization acknowledgment

76 VRATRNDN (PESIT) ­ Reception of a negative AckTRANSFER.END FPDU

77 VRATRNDP (PESIT) ­ Reception of a positive AckTRANSFER.END FPDU

78 VRAWRITN (PESIT) ­ Reception of a negative AckWRITE FPDU

79 VRAWRITP (PESIT) ­ Reception of a positive AckWRITE FPDU

80 VRCON (PESIT) ­ Reception of a CONNECT FPDU

81 VRCREA (PESIT) ­ Reception of a CREATE FPDU

82 VRCRF (PESIT) ­ Reception of a CRF (Close Remote File) FPDU

83 VRDSEL (PESIT) ­ Reception of a DESLECT FPDU

84 VRDTF (PESIT) ­ Reception of a DATA FPDU

85 VRDTFDA (PESIT) ­ Reception of a DATA (Start) FPDU

86 VRDTFFA (PESIT) ­ Reception of a DATA (End) FPDU

87 VRDTFMA (PESIT) ­ Reception of an end of DATA (Middle) FPDU

88 VRDTND (PESIT) ­ Reception of an end of DATA FPDU

89 VRIDT (PESIT) ­ Reception of a CANCEL FPDU

90 VRLOG (PESIT) ­ Reception of a pre­logon message

Transfer CFT 3.1.3 Troubleshooting Guide 236

3 Messages and error codes

Code Meaning

91 VRNACCN (NETWORK) ­ Outgoing call refused

92 VRNACCP (NETWORK) ­ Outgoing call accepted

93 VRNCON (NETWORK) ­ Incoming call indication

94 VROMSG (PESIT) ­ Reception of a MESSAGE FPDU

95 VRORF (PESIT) ­ Received an ORF (Open Remote File) FPDU

96 VRRCON (PESIT) ­ Received a Release CONNECT FPDU

97 VRRDY (NETWORK) ­ Network ready­to­send indication

98 Not used

99 VRREAD (PESIT) ­ Reception of a READ FPDU

100 VRREL (PESIT) ­ Reception of a RELEASE FPDU

101 VRRELCF (PESIT) ­ Reception of a RELEASE Confirm FPDU

102 VRRESY (PESIT) ­ Reception of a RE­SYNCHRONIZATION FPDU

103 VRSEL (PESIT) ­ Reception of a SELECT FPDU

104 VRSY (PESIT) ­ Reception of a SYNCHRONIZATION FPDU

105 VRTRND (PESIT) ­ Reception of a TRANSFER.END FPDU

106 VRWRIT (PESIT) ­ Reception of a WRITE FPDU

107 VVTIMO ­ Time­out

108 VFDATA1 ­ Internal induction for the automaton table

109 VRDTF1 ­ Internal induction for the automaton table

110 VVERCRC ­ Detection of a CRC error

111 VVERR ­ Detection of an inconsistent FPDU

112 VIABORTS ­ Internal induction for the automaton table

113 VIABORTC ­ Internal induction for the automaton table

114 VIRSTR ­ Internal induction for the automaton table

Transfer CFT 3.1.3 Troubleshooting Guide 237

3 Messages and error codes

Code Meaning

115 VINACCN ­ Internal induction for the automaton table

116 Not used

117 Not used

118 Not used

119 Not used

120 Not used

121 Not used

122 VRODMSG (PESIT) ­ Received a MESSAGE (Start) FPDU

123 VROMMSG (PESIT) ­ Received a MESSAGE (Middle) FPDU

124 VROFMSG (PESIT) ­ Received a MESSAGE (End) FPDU

125 Not used

126 VFCD (ODETTE) ­ Change direction request

127 VRASSID (ODETTE) Received an SSID (acknowledgment)

128 VRCD (ODETTE) ­ Reception of a CD (Change Direction)

129 VRCDT (ODETTE) ­ Reception of a CDT (Set Credit)

130 VREERP (ODETTE) ­ Reception of an EERP (End To End Response)

131 VREFNA (ODETTE) ­ Reception of an EFNA (End File Negative Answer)

132 VREFPA (ODETTE) ­ Reception of an EFPA (End File Positive Answer)

133 VREFID (ODETTE) ­ Reception of an EFID (End File Identification)

134 VRESID (ODETTE) ­ Reception of an ESID (End Session Identification)

135 Not used

136 Not used

137 VRRSSID (ODETTE) ­ Received an SSID (Start Session Identification) FPDU

138 VRRTR (ODETTE) ­ Received an RTR (Ready To Receive)

Transfer CFT 3.1.3 Troubleshooting Guide 238

3 Messages and error codes

Code Meaning

139 VRSFNA (ODETTE) ­ Reception of an SFNA (Start File Negative Answer)

140 VRSFPA (ODETTE) ­ Reception of an SFPA (Start File Positive Answer)

141 VRSFID (ODETTE) ­ Reception of an SFID (Start File Identification)

142 VRSSID (ODETTE) ­ Reception of an SFID (Start File Identification)

143 VRSSRM (ODETTE) ­ Reception of an SSRM (Start Session Ready Message)

144 VIESID (ODETTE) ­ Internal induction for the automaton table

145 VISSID (ODETTE) ­ Internal induction for the automaton table

146 VIRREAD (ODETTE) ­ Internal induction for the automaton table

147 VIDSEL (ODETTE) ­ Internal induction for the automaton table

148 VIABORTCD (ODETTE) ­ Internal induction for the automaton table

Transfer CFT 3.1.3 Troubleshooting Guide 239

3 Messages and error codes

RECOV: General network error recovery

codes
RECOV corresponds to the code common to all network access methods, providing a general
indication about the cause of the error.

One value can correspond to two causes, depending on whether the source of the error is at the
local or remote end; "L" is indicated in case of ambiguity:

l L=1: local
l L=0: remote

The codes are expressed in decimal form.

Table 3. RECOV - General Network Error Recovery Codes

Code Meaning

1 Normal remote end disconnection

2 L=1 Local time­out

L=0 Network time­out

3 L=1 Insufficient local resources

L=0 Protocol procedure error

4 No more contexts available

5 Incoming connection request while the maximum number of sessions (MAXCNX) for
this resource has been reached

9 Other non­fatal problems

64 Invalid call syntax

67 Incorrect remote address

68 Incorrect local address

99 The resources are temporarily unavailable

128 Malfunctions on the network

Undefined refusal reason

Transfer CFT 3.1.3 Troubleshooting Guide 240

3 Messages and error codes

General Transfer CFT protocol diagnostics

Diagnostics format
The following table defines the DIAGP formats.

Table 4. DIAGP Formats

Format Meaning

XXXXXXXX Mnemonic code

L HH HHH Local rejection of network connection

R HH HHH Remote rejection of network connection

HHHHHHHH Error in the system or network software at operating system level

eNNsNN (PeSIT) Unexpected event in the automaton

PDU iNN (PeSIT) FPDU does not conform to the specifications

XXX NNN (PeSIT) Received FPDU contains a diagnostic message

NNN HHHH (ODETTE) Received message contains a diagnostic message

XXX HHHH (ODETTE) Negotiation or send error

"Mnemonic"-Type DIAGP Codes

A "Mnemonic"­type DIAGP is a "character string" value providing information on the type of catalog
entry or the status of the transfer associated with this entry. Some codes are specific to a single
protocol.

Table 5. Specific codes

Code Protocol Meaning

ABOI_CD ODETTE CD send following reception of an ABORT indication (case of a RECV

IDF=* command)

ABORT Transfer CFT transfer abort request

Transfer CFT 3.1.3 Troubleshooting Guide 241

3 Messages and error codes

Code Protocol Meaning

ABORT_I ODETTE ABORT caused by the protocol engine, following detection of an

error

CALL OUT Call not made within the authorized call period (see
OMINTIME/OMAXTIME ­ OMINDATE/OMAXDATE parameters of
commands CFTPART, etc.)

CATUPDT Catalog update error (at sync point)

CD_ODT ODETTE (information) Indication of a "generic" entry for file reception

CLOSE_RN ODETTE Reception of a "negative CLOSE RESP" interaction from the file
access task: error closing the file sent

CREA_RN ODETTE Reception of a "negative CREATE RESP" interaction from the file
access task: error creating the receive file

COLLECT Indication of a "generic" entry for file collection. This entry does not
correspond to an actual transfer

CP Transfer performed without the compression option. This can be

caused by the REQUESTER or SERVER partner as compression is
negotiated

NONE

CP nn% Transfer performed with the compression option. The compression

rate is then displayed. This rate expresses the number of bytes to be
sent in relation to the number of bytes actually sent. The number of
bytes to be sent may be different from the number of bytes in the file
if the Transfer CFT truncates or pads records, depending on the
parameter settings

DAY CYC Indication of a "generic" entry for cyclic transfers (days). This entry
does not correspond to an actual transfer

DIFFUS Indication of a "generic" entry for file broadcasting. This entry does
not correspond to an actual transfer

DSEL_CN ODETTE Reception of a "negative DSELECT RESP" interaction from the file
access task: error deselecting the sent file

END_TFIL ODETTE Sending of a "RELEASE IND" interaction to the file access task in
order to stop the task (information)

ERR INC ODETTE Transfer ABORT ­ Reason not specified

Transfer CFT 3.1.3 Troubleshooting Guide 242

3 Messages and error codes

Code Protocol Meaning

ERRCOMP File compression error ­ the compression type requested is

incompatible with the file data

ERR LREC Error sending or receiving the file data. Transfer CFT detects an
invalid length for the data read or to be written

ERR_NCAR Error in the number of characters sent

ERR_NREC Error in the number of records

ERRPROT Protocol error when switching directions

ERR_UFMT ODETTE Internal error when deformatting the received FPDU

EVT ODETTE Reception of an unexpected event in the current phase of the

protocol automaton

ERRPASSW ODETTE Invalid partner LOGON password

EXAERR Processing error in the directory EXIT task

EXARJT Connection refusal via the directory EXIT task

EXATASK Load error for the directory EXIT task

EXAWRSP Waiting for a response from the directory EXIT task

EXIT EXIT task initialization problem

FCON_RN ODETTE Session parameter negotiation error, implying a connection

rejection

FORMAT FPDU formatting error

HOLD Indication of an "on­hold" transfer, waiting for a reception request

INACT Transfer refused due to partner inactivity

INV XFER Message transfer unauthorized with this protocol

LDT_TXT Rusize is greater than MAXRUSIZE in "T"

LIST_FI Indication of a "generic" entry for the file list. This entry does not
correspond to an actual transfer.

MALLOC Cannot allocate the working area required for the transfer
dynamically

Transfer CFT 3.1.3 Troubleshooting Guide 243

3 Messages and error codes

Code Protocol Meaning

MAXCNX The number of connection(s) for the resource (MAXCNX parameter

of the CFTNET command) has already been reached

MAXCV The number of connection(s) for the partner has already been
reached

MAXRETRY Maximum number of retries exceeded (see the RETRY* parameters)

MAXRST Maximum number of restarts for a protocol exceeded (see the

RESTART parameter of the CFTPROT command)

MAXTASK Maximum number of tasks exceeded (see the MAXTASK parameter of

the CFTPARM command)

MAXTRANS Maximum number of simultaneous transfers exceeded (see the

MAXTRANS parameter of the CFTPARM command)

MIN CYC Indication of a "generic" entry for cyclic transfers (minutes). This
entry does not correspond to an actual transfer

MON CYC Indication of a "generic" entry for cyclic transfers (months). This
entry does not correspond to an actual transfer.

MSG_ EERP send not authorized

NOAU

MSG_RN ODETTE The EERP message has not been acknowledged by the partner

MYSELF The target partner is the local site (CFTPARM PART)

NO AUTH Non­authorized partner or file (see the AUTH parameter, CFTAUTH

command, and the CFTPART security parameters)

NO NEW Receive file already exists for a reception request: (CFT)RECV

FDISP=NEW

NO OLD Receive file does not exist for a reception request: (CFT)RECV
FDISP=OLD

NO OPEN Transfer in open mode not authorized (see the OPEN parameter of
the partner's CFTPART command)

NO PARM Error due to incorrect Transfer CFT parameter settings

NO PART Partner does not exist (no CFTPART command for this partner
identifier)

Transfer CFT 3.1.3 Troubleshooting Guide 244

3 Messages and error codes

Code Protocol Meaning

NO PROT Protocol does not exist (no CFTPROT command for this protocol
identifier)

NO TURN ODETTE The Transfer CFT cannot hand over to the partner (CD) as the
partner handed over during the previous exchange

NO XLATE CFTXLATE command not found for this transfer direction, nor for
the source and target alphabets

NOCALL The partner cannot be called

NOCTX Message for a missing or inactive context

NOSELECT With the PeSIT protocol, SIT profile, the file selection request (RECV
command) is not authorized

NO_FILE ODETTE There are no more files to be sent (information)

NPART REQUESTER partner mismatch with SERVER partner in SIT profile.

Strict naming and consistency rules are imposed both by Transfer
CFT and by the PESIT standard.

N_REL_I ODETTE Reception of a network outage indication

OPER Transfer interrupt request by the operator

OUT TIME The transfer has exceeded the authorized time slot (MAXDATE,
MAXTIME parameters of the command)

RECV ALL Indication of a "generic" entry for global transfer receptions on

hold. This entry does not correspond to an actual transfer.

RELEASE Unexpected network outage, caused by the remote partner or the

network

RESTART0 Transfer interruption (it will be restarted at the beginning of the file)

RESTARTF Transfer interruption (it will be restarted at the restart point)

RTO Transfer CFT time­out during the transfer phase. This time­out
corresponds to the RTO parameter of the CFTPROT command

R_PASSW ODETTE The password given by the partner does not correspond to the
parameter settings (CFTPART command).

SFNA ODETTE Reception of an SFNA FPDU corresponding to a session parameter

negotiation problem

Transfer CFT 3.1.3 Troubleshooting Guide 245

3 Messages and error codes

Code Protocol Meaning

SROUT The partner cannot be called (SROUT parameter of the CFTPROT

command)

SSY TFIL Error sending data to CFTTFIL

SYPOST Communication error between Transfer CFT and the directory EXIT
task

TFIL ODETTE Reception of a transfer ABORT request originating from the file
access task

TIMEOUT Monitoring time­out during the connection phase, due particularly

to a missing response to a pre­connection (LOGON) string or a
CONNECT FPDU. With the SIT profile, there is no pre­connection
phase

TSK_EXIT Error initializing a file EXIT task.

VRESID ODETTE Transfer ABORT caused by the reception of an ESID FPDU (partner
session termination request)

WF RENAM Cannot rename the temporary file (WFNAME parameter) in FNAME,

at the end of the transfer

"L HH HHH"-Type DIAGP Codes

"L HH HHH"­type DIAGP codes correspond to network connection rejection diagnostics. The
character L indicates a local rejection. H represents a hexadecimal digit.

The two hexadecimal numbers respectively represent:

l REASON: a reason code according to the network context

l DIAGN: a diagnostic code according to the network context

For the meaning of these codes, refer to the Network Codes that correspond with the type of
network used in the transfer.

"R HH HHH"-Type DIAGP Codes

"R HH HHH"­type DIAGP codes correspond to network connection rejection diagnostics. The
character "R" indicates a remote rejection. H represents a hexadecimal digit.

The two hexadecimal digits respectively represent:

l REASON: a reason code according to the network context

l DIAGN: a diagnostic code according to the network context

Transfer CFT 3.1.3 Troubleshooting Guide 246

3 Messages and error codes

For the meaning of these codes, refer to the section Network Codes corresponding to the type of
network used by the transfer.

"HHHHHHHH"-Type DIAGP Codes

"HHHHHHHH"­type DIAGP codes correspond to the error diagnostics specific to the network or
system access software.

They are the "CS" or "NCS" codes.

Refer to the manufacturer's documentation (system code or network codes, depending on the type
of occurrence).

"eNNsNN"-Type PeSIT DIAGP Codes

"eNNsNN"­type PeSIT DIAGP codes correspond to the diagnostics representing an unexpected event
in the protocol automaton (where N represents a digit).

The two numbers respectively represent:

l The event code for all protocols

l The status code according to the protocol

For the meaning of this code, see Status Codes for the appropriate transfer protocol.

"PDU iNN"-Type PeSIT DIAGP Codes

"PDU iNN"­type PeSIT DIAGP codes correspond to the Transfer CFT diagnostics representing the
reception of a PeSIT FPDU that does not conform to protocol specifications (where N represents a
digit).

The code NN specifies the FPDU build error code.

"XXX NNN"-Type PeSIT DIAGP Codes

"XXX NNN"­type PeSIT DIAGP codes correspond to the Transfer CFT diagnostics representing the
reception of an FPDU with an error diagnostic code, where X represents a character and N a digit:

l NNN indicates the PeSIT protocol diagnostic in the FPDU

o For the meaning of this code, refer to the section PESIT Protocol Diagnostic Code.
l XXX represents the mnemonic code of the received FPDU ­ PeSIT protocol
o For the meaning of this code, refer to the section FPDU Mnemonic Codes PeSIT Protocol.

Transfer CFT 3.1.3 Troubleshooting Guide 247

3 Messages and error codes

"NNN HHHH"-Type ODETTE DIAGP Codes

Transfer CFT diagnostic codes corresponding to the reception of an FPDU with an error diagnostic
code. H represents a hexadecimal digit and N a digit:

l NNN is a numeric value corresponding to the ODETTE protocol diagnostic code

For the meaning of this code, refer to the section Protocol Diagnostic Codes.

l HHHH is a hexadecimal value corresponding to the Transfer CFT numeric code ODETTE protocol

See alsoTransfer CFT Numeric Codes ODETTE Protocol.

"XXX HHHH"-Type ODETTE DIAGP Codes

Transfer CFT diagnostic code identifying an FPDU negotiation or send error in the ODETTE protocol
(where H represents a hexadecimal digit and X a letter):

l XXX is a Transfer CFT mnemonic code ­ ODETTE protocol. This is an alphanumeric value
describing the origin of the anomaly or phase during which it occurred.

See also, Transfer CFT Mnemonic Codes ODETTE Protocol.

l HHHH is a Transfer CFT numeric code ­ ODETTE protocol. This is a hexadecimal value
corresponding to the internal protocol code.

Transfer CFT 3.1.3 Troubleshooting Guide 248

3 Messages and error codes

Miscellaneous codes
The codes in this topic are listed by protocol.

FPDU Build error codes (PeSIT)

This code specifies a build error in the received PeSIT FPDU. It forms the "PDU iNN"­type protocol
diagnostic code.

Error Description
code

1 Received AckCONNECT FPDU header does not conform: an error was detected in the
source or target identifier content. The source identifier must be null. The target
identifier must be the same as the source identifier sent in the CONNECT FPDU

2 Reception of two or more FPDUs concatenated in one NSDU. According to protocol

specifications, an FPDU cannot be followed or preceded by another FPDU

3 Reception of a CONNECT FPDU followed by two bytes that do not belong to it, but the
CRC option has not been implemented

4 Reception of a CONNECT FPDU with an incorrect CRC

5 Received CONNECT FPDU header does not conform: an error has been detected in the
source or target identifier content. The source identifier must not be null. The target
identifier must be null

6 Reception of an FPDU other than CONNECT with an incorrect CRC

7 Reception of two or more FPDUs concatenated in one NSDU, while the CRC option is
active. According to the protocol specifications, FPDU concatenation is inhibited with
the CRC option enabled

8 Header of a received FPDU does not conform: the size indicated is smaller than the
minimum size of an FPDU. The minimum size of an FPDU in the PeSIT protocol is six
bytes (length of the header). If a CRC is applied, the minimum size of an FPDU
becomes eight bytes (length of a header with its CRC)

9 Header of a received CONNECT­phase FPDU does not conform: an error has been
detected in the target identifier in the header

10 Header of a received CONNECT­phase FPDU does not conform: an error has been
detected in the source identifier in the header

Transfer CFT 3.1.3 Troubleshooting Guide 249

3 Messages and error codes

Error Description
code

11 Reception of a network message that is smaller than the minimum size of an FPDU. The
minimum size of an FPDU in the PeSIT protocol is six bytes (length of the header). If a
CRC is applied, the minimum size of an FPDU becomes eight bytes (length of a header
with its CRC)

12 Concatenated FPDU with invalid header

13 Reception of an NSDU that is larger than that negotiated

14 Header of a received FPDU does not conform: an error has been detected in the phase
byte

15 Header of the received RelCONNECT FPDU does not conform: an error has been
detected in the source or target identifier content. The source identifier must be null.
The target identifier must be the source identifier of the CONNECT FPDU

16 Header of a received FPDU does not conform: the size indicated is greater than the
length of the received network message

17 Header of a received SERVICE phase FPDU does not conform: an error has been
detected in the source or target identifier in the header

18 Received FPDU of unknown type

19 Received FPDU of a phase inconsistent with its type

Transfer CFT Numeric codes - OFTP (ODETTE) protocol

These codes, specific to the ODETTE protocol and internal to the Transfer CFT, indicate the source
of the failure. This code forms the DIAGP protocol diagnostic code. Values are expressed in
hexadecimal.

Error Description
code

0101 Application area allocation error

0102 Unknown event during network connection

0150 Protocol release error

0151 Invalid restart value

Transfer CFT 3.1.3 Troubleshooting Guide 250

3 Messages and error codes

Error Description
code

0152 CREDIT value error:

1. Reception of a CDT FPDU but the "credit" has not been used up
2. Reception of a CDT FPDU but the negotiated "credit" value is 0

0202 Restart position negotiation. The position returned by the partner is higher than the
proposed position

0203 Restart option proposed by the requester and that required by the server (RESYNC
parameter) are incompatible

0204 Compression negotiation. The compression value returned by the partner is greater
than the proposed value

0205 Network buffer length negotiation. The buffer size requested by the partner is less
than 128 or greater than that proposed

0206 CREDIT negotiation. The "credit" value requested by the partner is out of bounds

0207 Transfer DIRECTION negotiation. The value requested by the partner and the SRIN (or
SROUT) parameter value are incompatible

0208 PAD option negotiation (special logic). The partner requests "special logic" whilst the
PAD parameter is set to "NO" (default value)

0250 Restart position error. Reception of a restart request (SFID FPDU) but the "no restart"
option has been previously negotiated

0301 During the protocol recognition phase the Transfer CFT does not receive the expected
string: "ODETTE FTP READY"

0350 The total length of "subrecords" forming the FPDU is different from the FPDU size
specified in the SDATAIN field

0351 Invalid size for subrecord sent

0401 A restart is requested by the partner but the restart option is not set (RESYNC
parameter)

0402 Reception of a "CREATE CONF NEG" FPDU: creation of the receive file refused by the
partner

0501 Reception of an "ABORT" FPDU: transfer interrupted by the partner

0550 The SRUSIZE parameter value is less than 128, which is forbidden by the protocol

Transfer CFT 3.1.3 Troubleshooting Guide 251

3 Messages and error codes

Error Description
code

0551 Invalid restart parameter value

0601 IDF incompatibility. The received NIDF value does not correspond to the IDF
requested (RECV IDF=xxxx command).
Note: the only valid value for the IDF parameter of the RECV request is "*"

0650 Reception of a negative A_SELECT

0701 Error during the file de­selection phase at the partner end

0750 Internal monitor error: attempt to send a DATA FPDU but the "credit" has been
completely spent and the Transfer CFT is waiting for a CDT FPDU

0751 Record size is greater than the size of the exchange buffer

0A00 Local SSRM FPDU formatting error

0A02 Local SSID FPDU formatting error

0A03 Local ASSID FPDU formatting error

0A04 Local SFID FPDU formatting error

0A05 Local EFID FPDU formatting error

0A06 Local ESID FPDU formatting error

0A07 Local CDT FPDU formatting error

0A08 Local CD FPDU formatting error

0A09 ocal EERP FPDU formatting error

0A0A Local DTF FPDU formatting error

0B00 Formatting error in connection acknowledge FPDU

0B01 Local SFPA FPDU formatting error

0B02 Local SFNA FPDU formatting error

0B03 Local EFPA FPDU formatting error

0B04 Local EFNA FPDU formatting error

0B05 Local RTR FPDU formatting error

Transfer CFT 3.1.3 Troubleshooting Guide 252

3 Messages and error codes

Transfer CFT Mnemonic codes - ODETTE protocol

These codes, specific to the ODETTE protocol and internal to the Transfer CFT, indicate the source
of the fault.

This code forms the "XXX HHHH"­type DIAGP protocol diagnostic code. Values are expressed in
mnemonic form.

Error code Description

CDT Error during "credit" negotiation

DAT Synchronization problem in "credit" and "data" exchanges

FMT Internal FPDU formatting error

IDF Received NIDF incompatible with sent IDF

Note: only the RECV IDF=* command is valid in ODETTE

LDT Error in the network buffer size negotiation phase

MSG Error when acknowledging the EERP message

PAD Special logic negotiation error

POS Restart point negotiation error

RST Restart option negotiation error

SFI Error during negotiation of a send file parameter (SFID FPDU)

SSI Error during negotiation of a session parameter (SSID FPDU)

VER Error in the protocol software release number (at present this number is set to 1)

FPDU Mnemonic codes - PeSIT protocol

This code forms the "XXX NNN" or "XXX iNNN" DIAGP protocol diagnostic code in the PeSIT
protocol; it represents the XXX part. Values are expressed in mnemonic form.

Code FPDU

ABO ABORT

ACF Ack CLOSE REMOTE FILE

ACO Ack CONNECT

Transfer CFT 3.1.3 Troubleshooting Guide 253

3 Messages and error codes

Code FPDU

ACR Ack CREATE

AID Ack IDT

ADS Ack DESELECT

AMG Ack MESSAGE

AOF Ack OPEN REMOTE FILE

ARD Ack READ

ASE Ack SELECT

ASY Ack SYNC

ATE Ack TRANSFER END

AWR Ack WRITE

CON CONNECT

CRE Ack CREATE

CRF CLOSE REMOTE FILE

DMG Start of MESSAGE

DSE DESELECT

DTE DATA TRANSFER END

DTF DATA

FMG End of MESSAGE

IDT TRANSFER INTERRUPT

MMG Middle of MESSAGE

MSG MESSAGE

ORF OPEN REMOTE FILE

RCO Release CONNECT

RDF READ

Transfer CFT 3.1.3 Troubleshooting Guide 254

3 Messages and error codes

Code FPDU

RST RESTART

SEL SELECT

SYN CHECK

TFE TRANSFER END

WRI WRITE

Transfer CFT 3.1.3 Troubleshooting Guide 255

3 Messages and error codes

Network codes

NCR Common return code - Network

interface
The NCR code corresponds to the "cr" code returned by the network interface Transfer CFT
functions, using the formula: ncr = -(cr+20)

Supply this value to Product Support for troubleshooting operations.

NCS System return code - Network interface

The value of this code depends on the type of network and operating system. It corresponds to the
"cs" code returned by the network interface functions.

NCS - TCP/IP System Return Codes

If the value of the code is less than 500 (decimal), that is 1F4 (hexadecimal), it concerns the "errno"
variable provided by the TCP/IP resource. In this case, refer to the manufacturer's documentation
for the meaning of this code.

Hexadecimal Decimal Meaning

Code Code

0000023a 00000570 Reception of a Define Resource request concerning an already

registered resource

0000023b 00000571 Reception of an Undefine Resource request for a resource with

registered users

0000023c 00000572 Reception of an Undefine Resource request for a resource with

active connections

0000023d 00000573 Maximum number of connections to a resource reached during

a Connect Request

00000244 00000580 Cannot find an available port for the CFTTPRO polling socket

00000245 00000581 Reply to a synchronous request of incorrect length

00000246 00000582 CFTTPRO polling socket closed remotely during the TCP/IP
server activation confirmation phase

Transfer CFT 3.1.3 Troubleshooting Guide 256

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000247 00000583 Time­out while waiting for TCP/IP server activation

confirmation message

00000248 00000584 Time­out while waiting for a synchronous request reply

00000249 00000585 CFTTPRO polling socket closed by remote end during the
synchronous request reply wait phase

0000026d 00000621 Invalid parameter received in response to a synchronous

request (socket­based communication between CFTTCP and
CFTTPRO)

0000026e 00000622 Invalid parameter received in response to a synchronous

request (queue­based communication between CFTTCP and
CFTTPRO)

0000026f 00000623 Flow control is active when it should not be

00000270 00000624 Host identifier invalid in a Define Resource request

00000271 00000625 Host identifier invalid in an Undefine Resource request

00000272 00000626 Invalid parameter to be sent in response to a synchronous

request (Define Resource, Undefine Resource, Register Request
or Deregister Request)

00000273 00000627 Invalid parameter to be sent in response to a synchronous

request (Define Resource, Undefine Resource, Register Request
or Deregister Request)

00000274 00000628 Host identifier invalid in a Register Request

00000275 00000629 Unknown request type provided by CFTTPRO

00000276 00000630 Define Resource request denied because maximum number of

resources reached

00000280 00000640 Time­out when establishing the outgoing connection

000002b2 00000690 Remote polling closed during datagram transmission

000002ef 00000751 Link socket between CFTTPRO and CFTTCPS closed (in the case
of a socket connection)

000002f0 00000752 Socket closed by remote end (L1 byte write phase)

Transfer CFT 3.1.3 Troubleshooting Guide 257

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

000002f1 00000753 Socket closed by remote end (L2 byte write phase)

000002f2 00000754 Socket closed by remote end (data write phase)

000002f3 00000755 Socket closed by remote end (L1 byte read phase)

000002f4 00000756 Socket closed by remote end (L2 byte read phase)

000002f5 00000757 Socket closed by remote end (data read phase)

000002f6 00000758 Socket closed unexpectedly by remote end (L1 byte write
phase)

000002f7 00000759 Socket closed unexpectedly by remote end (L2 byte write
phase)

000002f8 00000760 Socket closed unexpectedly by remote end (data write phase)

000002f9 00000761 Invalid status for read automaton (rdstate)

000002fa 00000762 Read error (L1 read phase)

000002fb 00000763 Read error (L2 read phase)

000002fc 00000764 Link socket closed by CFTTPRO

000003c0 00000960 Register Request request for an unknown resource

000003c1 00000961 Symbolic name unknown for a polling port

000003c2 00000962 Use of a symbolic name for a polling port but this feature is not
supported by the system

000003c3 00000963 Host Internet address unknown

000003c4 00000964 Host symbolic name unknown

000003c5 00000965 Error in gethostbyname(): local host specification

000003c6 00000966 Error in gethostbyname(): remote host specification

000003d6 00000982 Undefine Resource request for an unknown resource

000003de 00000990 Register Request request for an unknown polling port name

Transfer CFT 3.1.3 Troubleshooting Guide 258

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

0000044e 00001102 Deregister Request request for an unknown reference: dynamic

table allocation

0000044f 00001103 Deregister Request request for an unknown reference: dynamic

allocation of the data area

00000450 00001104 Deregister Request request for an unknown reference: attribute

string incorrect

00000451 00001105 Deregister Request request for an unknown reference: call

parameter

00000452 00001106 Deregister Request request for an unknown reference: manager

not running

00000453 00001107 Deregister Request request for an unknown reference: contexts

still active

00000454 00001108 Deregister Request request for an unknown reference: table

access denied

00000455 00001109 Deregister Request request for an unknown reference: no more

available managers

00000456 00001110 Deregister Request request for an unknown reference: context

does not exist

00000457 00001111 Deregister Request request for an unknown reference: end of

table reached

00000468 00001128 ECONNREFUSED: The attempt to connect was rejected

000004b2 00001202 Context release problem during a Deregister Request: dynamic

table allocation

000004b3 00001203 Context release problem during a Deregister Request: dynamic

allocation of the data area

000004b4 00001204 Context release problem during a Deregister Request: incorrect

attribute string

000004b5 00001205 Context release problem during a Deregister Request: call

parameter

Transfer CFT 3.1.3 Troubleshooting Guide 259

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

000004b6 00001206 Context release problem during a Deregister Request: manager

not running

000004b7 00001207 Context release problem during a Deregister Request: contexts

still active

000004b8 00001208 Context release problem during a Deregister Request: table

access denied

000004b9 00001209 Context release problem during a Deregister Request: no more

managers available

000004ba 00001210 Context release problem during a Deregister Request: context

does not exist

000004bb 00001211 Context release problem during a Deregister Request: end of

table reached

00000516 00001302 Register context table scan error: dynamic table allocation

00000517 00001303 Register context table scan error: dynamic allocation of the data
area

00000518 00001304 Register context table scan error: incorrect attribute string

00000519 00001305 Register context table scan error: call parameter

0000051a 00001306 Register context table scan error: manager not running

0000051b 00001307 Register context table scan error: contexts still active

0000051c 00001308 Register context table scan error: table access denied

0000051d 00001309 Register context table scan error: no more managers available

0000051e 00001310 Register context table scan error: context does not exist

0000051f 00001311 Register context table scan error: end of table reached

0000057a 00001402 Connection context table scan error: dynamic table allocation

0000057b 00001403 Connection context table scan error: dynamic data area
allocation

0000057c 00001404 Connection context table scan error: incorrect attribute string

Transfer CFT 3.1.3 Troubleshooting Guide 260

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

0000057d 00001405 Connection context table scan error: call parameter

0000057e 00001406 Connection context table scan error: manager not running

0000057f 00001407 Connection context table scan error: contexts still active

00000580 00001408 Connection context table scan error: table access denied

00000581 00001409 Connection context table scan error: no more managers

available

00000582 00001410 Connection context table scan error: context does not exist

00000583 00001411 Connection context table scan error: end of table reached

000005de 00001502 Error in the search for an entry in the Register context table:
dynamic table allocation

000005df 00001503 Error in the search for an entry in the Register context table:
dynamic allocation of the data area

000005e0 00001504 Error in the search for an entry in the Register context table:
incorrect attribute string

000005e1 00001505 Error in the search for an entry in the Register context table: call
parameter

000005e2 00001506 Error in the search for an entry in the Register context table:
manager not running

000005e3 00001507 Error in the search for an entry in the Register context table:
contexts still active

000005e4 00001508 Error in the search for an entry in the Register context table:
table access denied

000005e5 00001509 Error in the search for an entry in the Register context table: no
more managers available

000005e6 00001510 Error in the search for an entry in the Register context table:
context does not exist

000005e7 00001511 Error in the search for an entry in the Register context table: end
of table reached

Transfer CFT 3.1.3 Troubleshooting Guide 261

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000642 00001602 Error in the search for an entry in the connection context table:
dynamic table allocation

00000643 00001603 Error in the search for an entry in the connection context table:
dynamic data area allocation

00000644 00001604 Error in the search for an entry in the connection context table:
incorrect attribute string

00000645 00001605 Error in the search for an entry in the connection context table:
call parameter

00000646 00001606 Error in the search for an entry in the connection context table:
manager not running

00000647 00001607 Error in the search for an entry in the connection context table:
contexts still active

00000648 00001608 Error in the search for an entry in the connection context table:
table access denied

00000649 00001609 Error in the search for an entry in the connection context table:
no more managers available

0000064a 00001610 Error in the search for an entry in the connection context table:
context does not exist

0000064b 00001611 Error in the search for an entry in the connection context table:
end of table reached

000006a6 00001702 Provider context (reference) invalid: dynamic table allocation

000006a7 00001703 Provider context (reference) invalid: dynamic allocation of the

data area

000006a8 00001704 Provider context (reference) invalid: incorrect attribute string

000006a9 00001705 Provider context (reference) invalid: call parameter

000006aa 00001706 Provider context (reference) invalid: manager not running

000006ab 00001707 Provider context (reference) invalid: contexts still active

000006ac 00001708 Provider context (reference) invalid: table access denied

Transfer CFT 3.1.3 Troubleshooting Guide 262

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

000006ad 00001709 Provider context (reference) invalid: no more managers

available

000006ae 00001710 Provider context (reference) invalid: context does not exist

000006af 00001711 Provider context (reference) invalid: end of table reached

0000070a 00001802 Socket reference invalid: dynamic table allocation

0000070b 00001803 Socket reference invalid: dynamic allocation of the data area

0000070c 00001804 Socket reference invalid: incorrect attribute string

0000070d 00001805 Socket reference invalid: call parameter

0000070e 00001806 Socket reference invalid: manager not running

0000070f 00001807 Socket reference invalid: contexts still active

00000710 00001808 Socket reference invalid: table access denied

00000711 00001809 Socket reference invalid: no more managers available

00000712 00001810 Socket reference invalid: context does not exist

00000713 00001811 Socket reference invalid: end of table reached

0000076e 00001902 Provider context (index) invalid: dynamic table allocation

0000076f 00001903 Provider context (index) invalid: dynamic allocation of the data
area

00000770 00001904 Provider context (index) invalid: incorrect attribute string

00000771 00001905 Provider context (index) invalid: call parameter

00000772 00001906 Provider context (index) invalid: manager not running

00000773 00001907 Provider context (index) invalid: contexts still active

00000774 00001908 Provider context (index) invalid: table access denied

00000775 00001909 Provider context (index) invalid: no more managers available

00000776 00001910 Provider context (index) invalid: context does not exist

Transfer CFT 3.1.3 Troubleshooting Guide 263

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000777 00001911 Provider context (index) invalid: end of table reached

000007d2 00002002 Provider context (update) invalid: dynamic table allocation

000007d3 00002003 Provider context (update) invalid: dynamic allocation of the

data area

000007d4 00002004 Provider context (update) invalid: incorrect attribute string

000007d5 00002005 Provider context (update) invalid: call parameter

000007d6 00002006 Provider context (update) invalid: manager not running

000007d7 00002007 Provider context (update) invalid: contexts still active

000007d8 00002008 Provider context (update) invalid: table access denied

000007d9 00002009 Provider context (update) invalid: no more managers available

000007da 00002010 Provider context (update) invalid: context does not exist

000007db 00002011 Provider context (update) invalid: end of table reached

00000836 00002102 Provider context (delete) invalid: dynamic table allocation

00000837 00002103 Provider context (delete) invalid: dynamic allocation of the data
area

00000838 00002104 Provider context (delete) invalid: incorrect attribute string

00000839 00002105 Provider context (delete) invalid: call parameter

0000083a 00002106 Provider context (delete) invalid: manager not running

0000083b 00002107 Provider context (delete) invalid: contexts still active

0000083c 00002108 Provider context (delete) invalid: table access denied

0000083d 00002109 Provider context (delete) invalid: no more managers available

0000083e 00002110 Provider context (delete) invalid: context does not exist

0000083f 00002111 Provider context (delete) invalid: end of table reached

0000089a 00002202 Context release problem: dynamic table allocation

Transfer CFT 3.1.3 Troubleshooting Guide 264

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

0000089b 00002203 Context release problem: dynamic allocation of the data area

0000089c 00002204 Context release problem: incorrect attribute string

0000089d 00002205 Context release problem: call parameter

0000089e 00002206 Context release problem: manager not running

0000089f 00002207 Context release problem: contexts still active

000008a0 00002208 Context release problem: table access denied

000008a1 00002209 Context release problem: no more managers available

000008a2 00002210 Context release problem: context does not exist

000008a3 00002211 Context release problem: end of table reached

000008fe 00002302 Provider context invalid for a Ready To Receive Request:

dynamic table allocation

000008ff 00002303 Provider context invalid for a Ready To Receive Request:

dynamic allocation of the data area

00000900 00002304 Provider context invalid for a Ready To Receive Request:

incorrect attribute string

00000901 00002305 Provider context invalid for a Ready To Receive Request: call
parameter

00000902 00002306 Provider context invalid for a Ready To Receive Request:

manager not running

00000903 00002307 Provider context invalid for a Ready To Receive Request:

contexts still active

00000904 00002308 Provider context invalid for a Ready To Receive Request: table
access denied

00000905 00002309 Provider context invalid for a Ready To Receive Request: no

more managers available

00000906 00002310 Provider context invalid for a Ready To Receive Request:

context does not exist

Transfer CFT 3.1.3 Troubleshooting Guide 265

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000907 00002311 Provider context invalid for a Ready To Receive Request: end of
table reached

00000962 00002402 Socket reference invalid: dynamic table allocation

00000963 00002403 Socket reference invalid: dynamic allocation of the data area

00000964 00002404 Socket reference invalid: incorrect attribute string

00000965 00002405 Socket reference invalid: call parameter

00000966 00002406 Socket reference invalid: manager not running

00000967 00002407 Socket reference invalid: contexts still active

00000968 00002408 Socket reference invalid: table access denied

00000969 00002409 Socket reference invalid: no more managers available

0000096a 00002410 Socket reference invalid: context does not exist

0000096b 00002411 Socket reference invalid: end of table reached

000009c6 00002502 Provider context (asynchronous return) invalid: dynamic table

allocation

000009c7 00002503 Provider context (asynchronous return) invalid: dynamic

allocation of the data area

000009c8 00002504 Provider context (asynchronous return) invalid: incorrect

attribute string

000009c9 00002505 Provider context (asynchronous return) invalid: call parameter

000009ca 00002506 Provider context (asynchronous return) invalid: manager not

running

000009cb 00002507 Provider context (asynchronous return) invalid: contexts still

active

000009cc 00002508 Provider context (asynchronous return) invalid: table access

denied

000009cd 00002509 Provider context (asynchronous return) invalid: no more

managers available

Transfer CFT 3.1.3 Troubleshooting Guide 266

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

000009ce 00002510 Provider context (asynchronous return) invalid: context does

not exist

000009cf 00002511 Provider context (asynchronous return) invalid: end of table

reached

00000a2a 00002602 Socket reference invalid for an Indication Datagram: dynamic

table allocation

00000a2b 00002603 Socket reference invalid for an Indication Datagram: dynamic

allocation of the data area

00000a2c 00002604 Socket reference invalid for an Indication Datagram: incorrect

attribute string

00000a2d 00002605 Socket reference invalid for an Indication Datagram: call

parameter

00000a2e 00002606 Socket reference invalid for an Indication Datagram: manager

not running

00000a2f 00002607 Socket reference invalid for an Indication Datagram: contexts

still active

00000a30 00002608 Socket reference invalid for an Indication Datagram: table

access denied

00000a31 00002609 Socket reference invalid for an Indication Datagram: no more

managers available

00000a32 00002610 Socket reference invalid for an Indication Datagram: context

does not exist

00000a33 00002611 Socket reference invalid for an Indication Datagram: end of

table reached

00000a8e 00002702 Search for a free context in the connection table: dynamic table
allocation

00000a8f 00002703 Search for a free context in the connection table: dynamic
allocation of the data area

00000a90 00002704 Search for a free context in the connection table: incorrect
attribute string

Transfer CFT 3.1.3 Troubleshooting Guide 267

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000a91 00002705 Search for a free context in the connection table: call parameter

00000a92 00002706 Search for a free context in the connection table: manager not
running

00000a93 00002707 Search for a free context in the connection table: contexts still
active

00000a94 00002708 Search for a free context in the connection table: table access
denied

00000a95 00002709 Search for a free context in the connection table: no more
managers available

00000a96 00002710 Search for a free context in the connection table: context does
not exist

00000a97 00002711 Search for a free context in the connection table: end of table
reached

00000af2 00002802 Search for a free context in the Register context table: dynamic
table allocation

00000af3 00002803 Search for a free context in the Register context table: dynamic
allocation of the data area

00000af4 00002804 Search for a free context in the Register context table: incorrect
attribute string

00000af5 00002805 Search for a free context in the Register context table: call
parameter

00000af6 00002806 Search for a free context in the Register context table: manager
not running

00000af7 00002807 Search for a free context in the Register context table: contexts
still active

00000af8 00002808 Search for a free context in the Register context table: table
access denied

00000af9 00002809 Search for a free context in the Register context table: no more
managers available

Transfer CFT 3.1.3 Troubleshooting Guide 268

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000afa 00002810 Search for a free context in the Register context table: context
does not exist

00000afb 00002811 Search for a free context in the Register context table: end of
table reached

00000bb9 00003001 Error during TCP/IP process creation: incorrect task name

00000bba 00003002 Error during TCP/IP process creation: definition error

00000bbb 00003003 Error during TCP/IP process creation: insufficient memory

00000bc1 00003009 Error during TCP/IP process creation: general problem

00000c1d 00003101 Queue acquisition error (queue­based communication between

CFTTCP and CFTTPRO): invalid queue

00000c1e 00003102 Queue acquisition error (queue­based communication between

CFTTCP and CFTTPRO): time­out

00000c1f 00003103 Queue acquisition error (queue­based communication between

CFTTCP and CFTTPRO): queue deleted

00000c25 00003109 Queue acquisition error (queue­based communication between

CFTTCP and CFTTPRO): general problem

00000c80 00003200 CFTTCP initialization error (tmbeg)

00000ce5 00003301 CFTTCP initialization error (tmstat): incorrect task

00000ced 00003309 CFTTCP initialization error (tmstat): general problem

00000dad 00003501 Queue error in Data Indication: invalid queue reference

00000dae 00003502 Queue error in Data Indication: counter capacity exceeded

00000daf 00003503 Queue error in Data Indication: control message or data too
large

00000db0 00003504 Queue error in Data Indication: invalid mode

00000db5 00003509 Queue error in Data Indication: general problem

00000db7 00003511 Queue error in Connect Reject Indication: invalid queue

reference

Transfer CFT 3.1.3 Troubleshooting Guide 269

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000db8 00003512 Queue error in Connect Reject Indication: counter capacity

exceeded

00000db9 00003513 Queue error in Connect Reject Indication: control message or

data too large

00000dba 00003514 Queue error in Connect Reject Indication: invalid mode

00000dbf 00003519 Queue error in Connect Reject Indication: general problem

00000dc1 00003521 Queue error in Release Indication: invalid queue reference

00000dc2 00003522 Queue error in Release Indication: counter capacity exceeded

00000dc3 00003523 Queue error in Release Indication: control message or data too
large

00000dc4 00003524 Queue error in Release Indication: invalid mode

00000dc9 00003529 Queue error in Release Indication: general problem

00000dcb 00003531 Queue error in Connect Accept Indication: invalid queue

reference

00000dcc 00003532 Queue error in Connect Accept Indication: counter capacity

exceeded

00000dcd 00003533 Queue error in Connect Accept Indication: control message or

data too large

00000dce 00003534 Queue error in Connect Accept Indication: invalid mode

00000dd3 00003539 Queue error in Connect Accept Indication: general problem

00000dd5 00003541 Queue error in Indication Datagram: invalid queue reference

00000dd6 00003542 Queue error in Indication Datagram: counter capacity exceeded

00000dd7 00003543 Queue error in Indication Datagram: control message or data

too large

00000dd8 00003544 Queue error in Indication Datagram: invalid mode

00000ddd 00003549 Queue error in Indication Datagram: general problem

00000ddf 00003551 Queue error in Connect Indication: invalid queue reference

Transfer CFT 3.1.3 Troubleshooting Guide 270

3 Messages and error codes

Hexadecimal Decimal Meaning

Code Code

00000de0 00003552 Queue error in Connect Indication: counter capacity exceeded

00000de1 00003553 Queue error in Connect Indication: control message or data too
large

00000de2 00003554 Queue error in Connect Indication: invalid mode

00000de7 00003559 Queue error in Connect Indication: general problem

00000de9 00003561 Queue error in Ready To Receive Indication: invalid queue

reference

00000dea 00003562 Queue error in Ready To Receive Indication: counter capacity

exceeded

00000deb 00003563 Queue error in Ready To Receive Indication: control message or

data too large

00000dec 00003564 Queue error in Ready To Receive Indication: invalid mode

00000df1 00003569 Queue error in Ready To Receive Indication: general problem

0000eb68 00060264 ECONNREFUSED: The attempt to connect was rejected

Transfer CFT 3.1.3 Troubleshooting Guide 271

3 Messages and error codes

PKIUTIL error codes

The following table lists the codes for the PKIU26E PKICER_Error ( msg {150nn/0}) type error
message.

Table 6. PKIUTIL error codes

Code Contains Meaning

15001 Command not The user is not authorized to use this command
authorized

15003 PKI file opening Error opening the file

error

15004 PKI invalid file Error opening the file with the request mode
opening mode

15005 PKI internal error Type of record unknown

15006 PKI record already The record already exists

exist

15007 PKI invalid Incorrect value for one of the fields in the command
parameter

15008 PKI Record writing Error writing to the file

error

15009 Not enough Memory allocation error

memory to proceed
this command

15010 Command OK Record complete

15011 No record found Record cannot be found

15012 PKI record reading Error reading the file

error

15013 PKI file end End of file reached

15014 PKI Record Error deleting a record

suppression error

15015 Certificate or Key Error opening a file to be imported (key or certificate)

reading error

Transfer CFT 3.1.3 Troubleshooting Guide 272

3 Messages and error codes

Code Contains Meaning

15016 Authorization failed Authorization problem

15017 PKI record not Internal datafile empty

found

15018 Certificate Length Certificate size too large

too long

15019 Error creating Creation of the extract file fout failed

extract file fout

15020 Error extracting a Creation of the file containing the certificate failed
PKI certificate

15021 PKI internal error Internal error

15022 PKI file integrity Certificate internal datafile integrity error

error

15024 Habilitation Error initializing the security system

opening error

15025 Parsing error on Certificate or key interpretation error

Certificate or Key

15026 PKI decipher error Error decrypting the certificate or key

15027 PKI cipher error Encryption error

15028 PKI decipher error Decryption error

15029 PKI sealing (MD5) MD5 sealing error

error

15030 PKI key file reading Error reading the password file
error

15031 IKNAME or INAME iname or ikname parameter mandatory

parameter
mandatory

15032 PKI record type Certificate type unknown

error

15034 Private and Public Public and private keys incompatible

key incompatible

Transfer CFT 3.1.3 Troubleshooting Guide 273

3 Messages and error codes

Code Contains Meaning

15035 CA Certificate not Root authority certificate cannot be found

found

15036 Signature check Signature invalid

failed

15038 PKI record conflict: Cannot insert/modify the certificate (User, Root, Inter, or
existing entity Other type), because there is already an entity using the same
ID in the PKI database

15039 PKI record conflict: Cannot insert/modify the entity, because there is already a
existing certificate certificate using the same ID in the PKI database

15099 Format not yet Certificate type not supported

supported

Protocol diagnostic codes

PeSIT protocol diagnostic codes

The PeSIT protocol uses two PIs to carry diagnostic messages: PI 2 and PI 29.

Transfer CFT is responsible for PI 29, which is valid only in version E. Transfer CFT uses PI 29 to
carry a clearform message describing the error. This message is not seen by the user.

The severity and nature of an error detected is specified by PI 2, which is valid for all profiles. It
consists of a first byte giving an error type and of two bytes providing a reason code. The code
corresponds to the last two bytes of PI 2.

This code comprises the "XXX NNN"­format (type) Transfer CFT DIAGP protocol diagnostic code.

To find the associated Transfer CFT internal diagnostic value that corresponds with the PeSIT
protocol diagnostic codes, refer to the topic PeSIT diagnostic codes.

Error FPDU Meaning

Code

100 RESYNC Transmission error (invalid CRC)

139 Invalid file attributes

Transfer CFT 3.1.3 Troubleshooting Guide 274

3 Messages and error codes

Error FPDU Meaning

Code

200 AckCREATE AckSELECT Insufficient file characteristics (insufficient

file parameters)

201 AckCREATE AckSELECT System resources currently insufficient

202 AckCREATE AckSELECT User resources currently insufficient

203 AckCREATE AckSELECT Non­priority transfer

204 AckCREATE File already exists

205 AckSELECT File does not exist

206 AckCREATE Available disk space smaller than file size

207 AckSELECT File in use

209 AckMSG Message type not supported

210 AckORF Negotiation failure

211 AckORF Cannot open file

212 AckCRF Cannot close file

213 IDT AckWRITE Fatal file input/output error

214 AckREAD Restart point negotiation failure

215 IDT Error specific to the system

216 IDT Operator­requested premature abort

217 IDT Too many synchronization points without

acknowledgment

218 IDT Cannot re­synchronize

219 IDT File space exceeded

220 IDT Record length greater than that declared

221 IDT Time­out

222 IDT Too much data without synchronization

point

Transfer CFT 3.1.3 Troubleshooting Guide 275

3 Messages and error codes

Error FPDU Meaning

Code

223 AckTRANSFER. Abnormal end of transfer

END AckDESELECT

224 AckTRANSFER.END Declared file size smaller than actual size

226 AckCREATE AckSELECT Transfer denied

228 File type not supported

229 File type incompatible with transfer

direction

230 File type incompatible with application

231 Transfer number not unique

232 Coding incompatible with file type

233 Restart context not available

234 Data entity size inconsistent with record

235 Record format incompatible with file type

236 Record length incompatible with file type

237 Incorrect client identifier

238 Non­authorized client

239 Non­authorized client / requester / file type

combination

240 Client not authorized on this server

241 Bank not authorized on this server

242 Old password invalid

243 New password invalid

245 Incorrect file length

246 No file of this type for this client

247 No file of this type on this server

Transfer CFT 3.1.3 Troubleshooting Guide 276

3 Messages and error codes

Error FPDU Meaning

Code

248 Identification type not supported

249 Nominative reference not supported

250 File already transferred

251 Reference type not supported

252 Start date too old

253 Incorrect date(s)

254 File service closed

299 All acknowledgment FPDUs Other fatal errors

300 RelCONNECT Congestion of local communication system

301 RelCONNECT Identification of called party unknown

302 RelCONNECT Called party not attached to an SSAP

303 RelCONNECT Maximum number of connections reached

304 RelCONNECT AckCREATE Non­authorized requester identification

AckSELECT ABORT

305 RelCONNECT SELECT negotiation failure

306 RelCONNECT RESYN negotiation failure

307 RelCONNECT SYNC negotiation failure

308 RelCONNECT Version number not supported

309 RelCONNECT ABORT Too many connections already in progress

310 ABORT Network incident

311 ABORT Remote PeSIT protocol error

312 RelCONNECT (if partner inactive) Shutdown of service requested by the user
ABORT/RELEASE

313 ABORT/RELEASE Connection closed due to inactivity

Transfer CFT 3.1.3 Troubleshooting Guide 277

3 Messages and error codes

Error FPDU Meaning

Code

314 ABORT/RELEASE Unused connection closed to open a new

connection

315 ABORT Negotiation failure

316 ABORT/RELEASE Connection closed by the administrator

317 ABORT Connection time­out

318 ABORT Mandatory PI missing or invalid

319 ABORT Incorrect number of records or bytes

320 ABORT Excessive number of re­synchronizations

321 RelCONNECT AckCREATE Call backup number

AckSELECT

322 RelCONNECT AckCREATE Call back later

AckSELECT

323 Incompatible CRC / connection mode

324 Incorrect requester identifier

325 Old password invalid

326 New password invalid

327 Receive access temporarily closed

328 Receive access not supported

329 Send access temporarily closed

330 Send access not supported

331 Excessive time­out value

332 Write not negotiated

333 Read not negotiated

334 Reverse charging refused

335 Invalid calling party number

Transfer CFT 3.1.3 Troubleshooting Guide 278

3 Messages and error codes

Error FPDU Meaning

Code

336 Server date and time refused

399 All ABORT acknowledgment FPDUs Other fatal errors

PeSIT reason code

PeSIT Description Transfer Service item
reason CFT concerned
code internal
diagnostic

Diagnostics imposing a re­synchronization

100 Transmission error 720 F.RESTART

Diagnostics imposing a restart

200 File characteristics insufficient 730 F.CREATE

F.SELECT

201 System resources temporarily 916 F.CREATE

insufficient F.SELECT

202 User resources temporarily 730 F.CREATE

insufficient F.SELECT

203 Transfer not overriding 730 F.CREATE

F.SELECT

204 File already exists 613 F.CREATE

F.SELECT

205 File does not exist 610 F.CREATE

F.SELECT

206 Reception of the file will cause 611 F.CREATE

an overflow of the disk quota F.SELECT

207 File occupied 635 F.CREATE

F.SELECT

208 File too old 730 F.CREATE

F.SELECT

Transfer CFT 3.1.3 Troubleshooting Guide 279

3 Messages and error codes

PeSIT Description Transfer Service item

reason CFT concerned
code internal
diagnostic

209 Message of this type not 920 F.CREATE

accepted on the reference F.SELECT
installation

210 Presentation context negotiation 730 F.OPEN

failure

211 Not possible to open file 604 F.OPEN

212 Not possible to close file 605 F.CLOSE

normally

213 Inhibiting input/output error 600 F.READ

F.WRITE
F.DATA.END
F.CANCEL

214 Restart point negotiation failure 730 F.READ

F.DATA.END
F.CANCEL

215 Specific system error 730 F.DATA.END

F.CANCEL

216 Intentional premature halt 621 F.DATA.END

F.CANCEL

217 Too many synchronization 730 F.DATA.END

points not acknowledged F.CANCEL

218 Re­synchronization not possible 730 F.DATA.END

F.CANCEL

219 File space full 614 F.DATA.END

F.CANCEL

220 Article longer than expected 626 F.DATA.END

F.CANCEL

221 Expected end of transmission 730 F.DATA.END

time F.CANCEL

Transfer CFT 3.1.3 Troubleshooting Guide 280

3 Messages and error codes

PeSIT Description Transfer Service item

reason CFT concerned
code internal
diagnostic

222 Too much data without 730 F.DATA.END

synchronization points F.CANCEL

223 Abnormal end of transfer 730 F.TRANSFER.END

F.DESELECT

224 The size of the file sent is greater 600 F.TRANSFER.END

than the one announced in F.DESELECT
F.CREATE

225 Workstation application 600 F.TRANSFER.END

congested: the file has F.DESELECT
effectively been received but
SCRS has not been able to give it
to the workstation application

226 Transfer refusal 904 F.CREATE

F.SELECT

299 Other 730 F.CREATE

F.SELECT
F.OPEN
F.CLOSE
F.READ
F.WRITE
F.DATA.END
F.CANCEL
F.TRANSFER.END
F.DESELECT
F.RESTART

Diagnostics imposing a reconnection

300 Local communication system 730 F.CONNECT

congested

301 Identification requested not 909 F.CONNECT

known

302 Requested system not attached 730 F.CONNECT

to a SSAP

Transfer CFT 3.1.3 Troubleshooting Guide 281

3 Messages and error codes

PeSIT Description Transfer Service item

reason CFT concerned
code internal
diagnostic

303 Remote communication system 730 F.CONNECT

congested
(too many connections)

304 Requested identification not 730 F.CONNECT

authorized (security) F.ABORT
F.CREATE
F.ABORT

305 Negotiation failure (SELECT) 730 F.CONNECT

306 Negotiation failure (RESYN) 730 F.CONNECT

307 Negotiation failure (SYNC) 730 F.CONNECT

308 Version number not supported 730 F.CONNECT

309 Too many connections already 916 F.CONNECT

in process for this processing F.ABORT
centre

310 Network incident 802 F.ABORT

311 Remote PeSIT protocol error 730 F.ABORT

312 Service closure requested by the 730 F.RELEASE

user F.ABORT

313 Connection broken at the end of 730 F.RELEASE

the TD inactivity interval F.ABORT

314 Connection used to host a new 730 F.RELEASE

connection F.ABORT

315 Negotiation failure 730 F.ABORT

316 Connection broken as a result of 730 F.RELEASE

an administration command F.ABORT

317 Time­out 740 F.ABORT

318 Mandatory PI absent or illegal PI 722 F.ABORT

contents

Transfer CFT 3.1.3 Troubleshooting Guide 282

3 Messages and error codes

PeSIT Description Transfer Service item

reason CFT concerned
code internal
diagnostic

319 Number of bytes or articles 620 F.ABORT

incorrect

320 Excessive number of 730 F.ABORT

resynchronizations for a transfer

321 Call the backup number 730 F.CONNECT

F.CREATE
F.ABORT

322 Call back later 730 F.CONNECT

F.CREATE
F.ABORT

399 Other 730 F.CONNECT

F.RELEASE
F.CREATE
F.ABORT

ODETTE Protocol Diagnostic Codes

These codes are specific to the ODETTE protocol and correspond to the "ODETTE diagnostic code"
transmitted by the protocol.

The values of these codes consist of the diagnostic code (two digits) to which the Transfer CFT adds
100 or 200 depending on the protocol phase concerned.

l Values between 100 and 199 correspond to the "SFNA" (Start File Negative Answer) and "EFNA"
(End File Negative Answer) protocol messages.
l Values between 200 and 299 correspond to the "ESID" (End Session IDentification) protocol
message.
l This code forms the "NNN NNNN"­type DIAGP protocol diagnostic code. Values are expressed in
decimal.

Error Description
code

101 File does not exist

102 Target site does not exist for the file

Transfer CFT 3.1.3 Troubleshooting Guide 283

3 Messages and error codes

Error Description
code

103 Source site does not exist for the file

104 File format not supported

105 Record length error (length not supported)

106 File too big

110 Invalid number of records

111 Invalid number of characters

112 Fatal file input/output error (file access method problem)

113 File already exists

199 Non­referenced errors

201 NSDU (Network System Data Unit) not recognized (faulty header)

202 Protocol error (reception of a invalid NSDU)

203 Requestee identification not known

204 Requester identifier not authorized or password incorrect

205 Congestion of local communication system (sudden shutdown of communication

system)

206 FPDU received with missing parameter or unexpected value

207 Invalid NSDU size received

208 User resources currently insufficient

209 End of time­out

210 Incorrect number of records. The number transported by the EFID FPDU does not
correspond to the number of received records counted by the Transfer CFT (F­ or V­
format files)

211 Number of characters incorrect. The number transported by the EFID FPDU does not
correspond to the number of received characters counted by the Transfer CFT (T­ or U­
format files)

Transfer CFT 3.1.3 Troubleshooting Guide 284

3 Messages and error codes

Reason and diagnostic network codes

Reason codes

REASON codes provide a general explanation of the error detected, or the refusal.

Diagnostic codes

DIAGNOSTIC (diag) codes provide a detailed explanation of the source of the error detected or the
refusal.

TCP/IP network codes

TCP/IP reason codes

REASON corresponds to the reason code returned by the TCP/IP communication system.

The codes are expressed in hexadecimal.

TCP/IP Reason codes

Code Description

00 Connection request rejected by the network or break caused by the remote partner

01 Time­out for a connection request. The called party is probably not connected to the
network.

02 Insufficient resources (other than memory)

03 Insufficient memory

04 The network access point reference passed to the connection is not valid

08 Invalid parameter in TCP request sent

09 Other cause of rejection

43 Invalid local or remote address

TCP/IP diagnostic codes

DIAGN (TCP/IP diagnostic codes) corresponds to the diagnostic code returned by the TCP/IP
communication system.

Transfer CFT 3.1.3 Troubleshooting Guide 285

3 Messages and error codes

The value of this code corresponds to the "errno" variable provided by the TCP/IP resource. In this
case, refer to the manufacturer's documentation for the meaning of this code.

PeSIT protocol diagnostic codes

The PeSIT diagnostic code is conveyed in the PI 2 code of a FPDU. It is broken down into one byte
giving an error code and two bytes providing a reason code. The contents of these last two bytes
converted into a decimal representation appears in the protocol diagnostics in "XXX NNN" format.

This topic lists the PeSIT reason codes, which are specified by the PeSIT protocol, and the
associated Transfer CFT internal diagnostic value.

Diagnostic protocol field format

This section presents the diagnostic protocol fields format for the PeSIT protocol. In PeSIT
protocol, the DIAGP or Diag Protocol fields can be organized in several ways:

l "HHHHHHHH" format

H represents a hexadecimal digit.

In general for Transfer CFT, this format represents an error code specific to the operating system of
the host computer and only relates to NON network resources (file access, task management, system
services, etc.).

For PeSIT, this field can also represent an error code specific to the method of access to the network
of the system concerned. In this case, the code is associated with the following internal diagnostics:

l 301: network addressing error in connection phase

l 302: network error (cut, timeout) during the data exchange phase
l 303: network parameter error in connection phase
l "eNNsNN" format

N represents a decimal digit. An unexpected event has arisen in the protocol controller.

This value should be given to the Technical support in the event of unexplained transfer difficulties.

l "PDU iNN" format

N represents a decimal digit. Reception of an FPDU not conforming to the protocol specifications.
The meanings associated with this message are explained further on in this book. For example,
DIAGP = "PDU i16" means that the header of an FPDU received does non conform, because its size
is greater than the length of the network message received.

l "XXX NNN" format

X represents an alphabetical character.

Transfer CFT 3.1.3 Troubleshooting Guide 286

3 Messages and error codes

N represents a decimal digit. Reception of an FPDU featuring an error diagnostic (PI 2) conforming
to the PeSIT protocol. XXX represents the FPDU received. NNN represents the PeSIT reason code
(the two least significant bytes sent in the PI 2 code of FPDUs). The possible values for the PeSIT
reason code are given further on in this appendix. The possible values for XXX are given in the
following table.

l "XXX iNN" format

X represents an alphabetical character.

N represents a decimal digit.
Reception of an FPDU having a parameter not conforming to the protocol specifications. As for the
previous format, XXX represents the FPDU received. NN indicates an error code which is used to
refine the problem detected. The possible values for XXX are given in the following table.
For example, DIAGP = "CRE i12" means that a CREATE FPDU has been received with an unknown
space reservation unit (PI 41).

Table 7. "XXX iNN" format values

XXX FPDU Definition

ABO ABORT Sudden connection interruption

ACF AckCRF File closing confirmation

ACO ACONNECT Connection confirmation

ACR AckCREATE File creation confirmation

ADS AckDESELECT File deselect confirmation

AMG AckMSG Message confirmation

AOF AckORF File opening confirmation

ARD AckREAD Read confirmation

ASE AckSELECT File selection confirmation

ATE AckTRANS.END End of transfer confirmation

AWR AckWRITE Write confirmation

CON CONNECT Connection request

CRE CREATE File creation

CRF CRF File closing

DMG MSGDM Message start

Transfer CFT 3.1.3 Troubleshooting Guide 287

3 Messages and error codes

XXX FPDU Definition

DSE DESELECT File deselect

DTE TRANS.END End of transfer

IDT IDT Transfer interruption

MSG MSG Message transmission

RCO RCONNECT Connection refusal

SEL SELECT File selection

l "Vxxxxxxx" format

The mnemonic Vxxxxxxx represents a protocol event.

This value should be given to the Technical support in the event of unexplained transfer difficulties.

Table 8. Vxxxxxxx format: possible protocol events

Vxxxxxxx Definition

"VFxxxxx" File transfer event (eg: VFCAND)

"VLOGxxxx" Event relative to the pre­connection message (eg: VLOGRP)

"VNxxxxxx" Network event (eg: VNRELI)

"VRxxxxxx" FPDU reception event (eg: VRABORT)

"VVxxxxxx" Internal event (eg: VVTIMO)

"VIxxxxxx" Induced internal event (eg: VIABORT)

PeSIT reason codes and the associated Transfer CFT internal diagnostic values

PeSIT reason code Transfer CFT internal diagnostic Service item concerned

Diagnostics imposing a re­synchronization

100 720 F.RESTART

Diagnostics imposing a restart

200 730 F.CREATE

F.SELECT

Transfer CFT 3.1.3 Troubleshooting Guide 288

3 Messages and error codes

PeSIT reason code Transfer CFT internal diagnostic Service item concerned

201 916 F.CREATE

F.SELECT

202 730 F.CREATE

F.SELECT

203 730 F.CREATE

F.SELECT

204 613 F.CREATE

F.SELECT

205 610 F.CREATE

F.SELECT

206 611 F.CREATE

F.SELECT

207 635 F.CREATE

F.SELECT

208 730 F.CREATE

F.SELECT

209 920 F.CREATE

F.SELECT

210 730 F.OPEN

211 604 F.OPEN

212 605 F.CLOSE

213 600 F.READ

F.WRITE
F.DATA.END
F.CANCEL

214 730 F.READ

F.DATA.END
F.CANCEL

215 730 F.DATA.END

F.CANCEL

Transfer CFT 3.1.3 Troubleshooting Guide 289

3 Messages and error codes

PeSIT reason code Transfer CFT internal diagnostic Service item concerned

216 621 F.DATA.END

F.CANCEL

217 730 F.DATA.END

F.CANCEL

218 730 F.DATA.END

F.CANCEL

219 614 F.DATA.END

F.CANCEL

220 626 F.DATA.END

F.CANCEL

221 730 F.DATA.END

F.CANCEL

222 730 F.DATA.END

F.CANCEL

223 730 F.TRANSFER.END

F.DESELECT

224 600 F.TRANSFER.END

F.DESELECT

225 600 F.TRANSFER.END

F.DESELECT

226 904 F.CREATE

F.SELECT

299 730 F.CREATE

F.SELECT
F.OPEN
F.CLOSE
F.READ
F.WRITE
F.DATA.END
F.CANCEL
F.TRANSFER.END
F.DESELECT
F.RESTART

Diagnostics requiring a reconnection

Transfer CFT 3.1.3 Troubleshooting Guide 290

3 Messages and error codes

PeSIT reason code Transfer CFT internal diagnostic Service item concerned

300 730 F.CONNECT

301 909 F.CONNECT

302 730 F.CONNECT

303 730 F.CONNECT

304 730 F.CONNECT

F.ABORT
F.CREATE
F.ABORT

305 730 F.CONNECT

306 730 F.CONNECT

307 730 F.CONNECT

308 730 F.CONNECT

309 916 F.CONNECT

F.ABORT

310 802 F.ABORT

311 730 F.ABORT

312 730 F.RELEASE

F.ABORT

313 730 F.RELEASE

F.ABORT

314 730 F.RELEASE

F.ABORT

315 730 F.ABORT

316 730 F.RELEASE

F.ABORT

317 740 F.ABORT

318 722 F.ABORT

319 620 F.ABORT

Transfer CFT 3.1.3 Troubleshooting Guide 291

3 Messages and error codes

PeSIT reason code Transfer CFT internal diagnostic Service item concerned

320 730 F.ABORT

321 730 F.CONNECT

F.CREATE
F.ABORT

322 730 F.CONNECT

F.CREATE
F.ABORT

399 730 F.CONNECT

F.RELEASE
F.CREATE
F.ABORT

Transfer CFT 3.1.3 Troubleshooting Guide 292

3 Messages and error codes

PeSIT E PI codes
When implementing specific extensions, Transfer CFT uses the PI codes of the E version of PeSIT to
convey specific values. These extensions are automatically activated when two partner Transfer CFTs
negotiate a protocol connection in PeSIT version E. For example, requesters specify PROF = ANY in
their CFTPROT object.

PeSIT E CFT/CFT extensions

PI 21 Compression
This field is used to negotiate the use of compression during the transmission of the file data. In
addition to horizontal compression and vertical compression, Transfer CFT provides the possibility
of using additional compression techniques:

l compression of an EBCDIC "space" character string

l character compacting

PI 31 Article format
This parameter specifies the file article format. It is defined using the NRECFM parameter of the
CFTSEND or SEND command. In addition to the fixed format and the PeSIT variable format, Transfer
CFT adds indefinite format semantics:

l NRECFM = F PI 31 = 0x00 (fixed)

l NRECFM = V PI 31 = 0x80 (variable)
l NRECFM = U PI 31 = 0x40 (indefinite)

PI 99 Free message
Format: 254 characters.

This parameter allows a message to be conveyed from one user to another in the free field of the
PeSIT service primitives. No control concerning the coding, structure or semantics of its contents is
imposed by the protocol.

This field is used to set up specific extensions by defining additional information.

The following parameters not provided for by the PeSIT protocol are conveyed:

l NBLKSIZE, file block size (CFTSEND or SEND commands)

l NFNAME, name of the file to be sent by the remote server (RECV command); this field is useful
for reception in open mode
l NTYPE, file type (CFTSEND or SEND commands)
l PARM, user parameter (CFTSEND or SEND command)

Transfer CFT 3.1.3 Troubleshooting Guide 293

3 Messages and error codes

l IDT, transfer identifier of the form Mddhhmms (transfer commands HALT, KEEP, START,
DELETE,...)
l PRI, transfer priority concerning 256 possible values (CFTSEND/SEND or CFTRECV/RECV
commands)
l SYST, operating system supporting the monitor sending the FPDU
l USERID, identifier of the user owning the file (CFTSEND or SEND commands)

This free field is also used to increase the size of certain parameters relative to the limit imposed by
the PeSIT protocol:

l Sending, or receiving, user identifier SUSER, or RUSER, limited to 8 characters by PI 03 (PI 04)
can be increased to 28 characters
l Sending, or receiving, application identifier SAPPL, RAPPL, limited to 8 characters by PI 03 (PI
04) can be increased to 48 characters
l File identifier NIDF, limited to 14 characters by PI 12, can be increased to 28 characters

Transfer CFT 3.1.3 Troubleshooting Guide 294

3 Messages and error codes

PeSIT-extension PI code descriptions

This topic describes the PI codes for PeSIT extensions. A PESIT extension is additional information
added to the PI that is specific to Transfer CFT. These extensions comprise the following:

l PI codes that receive an extension relative to the standardized usage

l PI codes that have been specially created and hence convey additional information

Any PI not mentioned in this section is used according to the standardized version of PeSIT.

Additionally, this topic provides the PI extension descriptions for the following functions:

l Message transfers
l Relay store and forward

Non-standard PI code usage

PI 03 Requester identification

This field specifies the name of the partner requesting the connection. It takes various formats
depending on the PeSIT service used:

l Establishing the protocol connection (FPDU CONNECT).

Format: 16 characters.

Transfer CFT defines and makes use of this field in the same way as for the support of the
standardized version of PeSIT.

l Creating a file (FPDU CREATE)

Format: 24 characters

Byte range Description

bytes 1 to 8 sending user’s name

bytes 9 to 16 sending partner’s network identification

bytes 17 to 24 sending application’s name

In requester mode, the first field is defined using the SUSER parameter of the SEND command (the
default value of SUSER is the local partner (NSPART)).

The final field corresponds to the sending application: SAPPL parameter of SEND. As it is possible to
route files (store and forward), the second field corresponds to the original local partner (NSPART).

In server mode, Transfer CFT recovers the PI 3 code in order to be able to define the symbolic
variables &SAPPL and &SUSER.

l Sending a message or an acknowledgement

(SEND TYPE = MESSAGE/REPLY, ...)

Transfer CFT 3.1.3 Troubleshooting Guide 295

3 Messages and error codes

The PI 3 code contains the same value as the one conveyed by the protocol connection request
(FPDU CONNECT) previously required to send this message.

PI 04 Server identification
This field specifies the name of the connection server partner. It takes various formats depending on
the PeSIT service used:

l Establishing the protocol connection (FPDU CONNECT)

Format: 16 characters

Transfer CFT defines and makes use of this field in the same way as for the support of the
standardized version of PeSIT.

l Creating a file (FPDU CREATE)

Format: 24 characters

Byte range Description

bytes 1 to 8 receiving user’s name

bytes 9 to 16 receiving partner’s network identification

bytes 17 to 24 receiving application’s name

In requesting mode, the first field is defined using the RUSER parameter of the SEND commands
(the default value of RUSER is the remote partner (NRPART).

The final field corresponds to the sending application: RAPPL parameter of SEND. As it is possible to
route files (store and forward), the second field corresponds to the final remote partner (NRPART).

In server mode, Transfer CFT recovers the PI 3 code in order to be able to define the symbolic
variables &RAPPL and &RUSER as required.

l Sending a message or an acknowledgement

(SEND TYPE = MESSAGE/REPLY, ...)

The PI 4 code contains the same value as the one conveyed by the protocol connection request
(FPDU CONNECT) previously required to send this message.

PI 11 File type
Each of the two bytes of this PI code is considered as a sub­field. The first byte is defined using the
FTYPE parameter of the transfer command. The second byte identifies the operating system
supporting the monitor which sends the FPDU. This is system dependent.

PI 12 Message name
Format: 8 characters

Transfer CFT 3.1.3 Troubleshooting Guide 296

3 Messages and error codes

When sending messages or acknowledgements (SEND TYPE = MESSAGE/REPLY, ...), Transfer CFT
defines this field using the IDM parameter of the transfer command. When receiving messages,
Transfer CFT recovers the PI 12 code to set the value of the &IDM variable.

For file transfers, Transfer CFT defines and makes use of the PI 12 code (file name) in the same way
as for the support of the standardized version of PeSIT.

PI 13 Transfer identifier
Format: 8 characters

Transfer CFT has extended this field to 8 bytes so that it can be defined by the transfer identifier IDT
saved in the catalog.

PI 21 Compression
This parameter specifies the file article format. It is defined using the NRECFM parameter of the
SEND command.

In addition to the fixed format and the PeSIT variable format, Transfer CFT adds indefinite format
semantics:This field is used to negotiate the use of compression during the transmission of the file
data. In addition to horizontal compression and vertical compression, Transfer CFT provides the
possibility of using additional compression techniques:

l compression of an EBCDIC "space" character string

l character compacting

PI 31 Article format
This parameter specifies the file article format. It is defined using the NRECFM parameter of the
SEND command. In addition to the fixed format and the PeSIT variable format, Transfer CFT adds
undefined format semantics:

l NRECFM = F PI 31 = 0x00 (fixed)

l NRECFM = V PI 31 = 0x80 (variable)
l NRECFM = U PI 31 = 0x40 (undefined)

PI 37 File label
When sending a FPDU SELECT, Transfer CFT defines the PI 37 code using the NFNAME parameter of
the RECV transfer command. On receiving this FPDU, Transfer CFT recovers the PI 37 code in order
to be able to define the symbolic variable &NFNAME as required. Otherwise, this field is only used if
the transfers with the partner can be performed in open mode. In other words, if the local Transfer
CFT authorizes the receiving partner to set the physical name of the sending file (implicit
transmission CFTSEND IMPL = YES, FNAME = &NFNAME, ...).

For the other FPDUs, Transfer CFT defines and makes use of this field in the same way as for the
support of the standardized version of PeSIT.

Transfer CFT 3.1.3 Troubleshooting Guide 297

3 Messages and error codes

Additional non-standard PI codes

PI 90 Size of file blocks

Format: 2 binary bytes.

Transfer CFT defines the PI 90 in the FPDU CREATE and AckSELECT using the NBLKSIZE parameter
of the CFTSEND or SEND command.

PI 91 File version number

When a file selection request is made (FPDU SELECT), Transfer CFT defines the PI 91 using the
NFVER parameter of the RECV transfer command.

PI 92 Message
Format: 80 characters.

This field is used to convey a message from one user to another using the message transfer service.
It is defined using the MSG parameter of the SEND TYPE = MESSAGE command or SEND TYPE =
REPLY command.

In message reception mode, Transfer CFT recovers the PI 92 in order to define the &MSG symbolic
variable.

PI 94 Application parameter
Format: 80 characters.

Transfer CFT defines the PI 94 in the CREATE, SELECT and AckSELECT FPDU using the PARM
parameter of the transfer command. On receiving such a FPDU, Transfer CFT recovers the PI 94 in
order to define the &MSG symbolic variable.

PI 99 Free message
Format: 254 characters.

This parameter allows a message to be conveyed from one user to another in the free field of the
PeSIT service primitives. No control concerning the coding, structure or semantics of its contents is
imposed by the protocol.

This field is used to set up specific extensions by defining additional information.

The following parameters not provided for by the PeSIT protocol are conveyed:

l NBLKSIZE, file block size (SEND commands)

l NFNAME, name of the file to be sent by the remote server (RECV command); this field is useful
for reception in open mode

Transfer CFT 3.1.3 Troubleshooting Guide 298

3 Messages and error codes

l NTYPE, file type (SEND commands)

l PARM, user parameter (SEND command)
l IDT, transfer identifier of the form Mddhhmms (transfer commands HALT, KEEP, START,
DELETE,...)
l PRI, transfer priority concerning 256 possible values (SEND or RECV commands)
l SYST, operating system supporting the monitor sending the FPDU
l USERID, identifier of the user owning the file (SEND commands)

This free field is also used to increase the size of certain parameters relative to the limit imposed by
the PeSIT protocol:

l Sending, or receiving, user identifier SUSER, or RUSER, limited to 8 characters by PI 03 (PI 04)
can be increased to 28 characters
l Sending, or receiving, application identifier SAPPL, RAPPL, limited to 8 characters by PI 03 (PI
04) can be increased to 48 characters
l File identifier NIDF, limited to 14 characters by PI 12, can be increased to 28 characters

Message transfer
The SEND TYPE = MESSAGE or SEND TYPE = REPLY commands cause FPDUs specific to Transfer
CFT to be exchanged: OMSG and AckOMSG.

The OMSG FPDU conveys an operator message which is either derived from:

l SEND TYPE = MESSAGE command

l SEND TYPE = REPLY command in response to a previously received transfer

The AckOMSG FPDU is the protocol acknowledgement of the OMSG FPDU associated with the
operator message.

The table below summarizes the structure of these FPDU.

Figure 1. Message transfer FPDU structure

FPDU Parameter

Name Code PI Description

OMSG 0x1F PI 03 Same as the CREATE FPDU of the standardized version

PI 04 Same as the CREATE FPDU of the standardized version

PI 12 IDM parameter of the SEND command

PI 13 IDT associated with the SEND command

Transfer CFT 3.1.3 Troubleshooting Guide 299

3 Messages and error codes

FPDU Parameter

Name Code PI Description

PI 92 Message text
MSG parameter of the SEND command

AckOMSG 0x3F PI 02 Diagnostic code

If the requester is in the connected state at the time the send command is taken into account, this
command initiates the sending of an OMSG FPDU over the protocol connection.

If the requester is not the connected state at the time the send command is taken into account, this
command initiates a standard connection request, sending of a CONNECT FPDU, with the write
transfer indication.

Relay file store and forward PI codes

The extensions to the PI 03 and PI 04 codes, initial requester partner and final server partner
concepts, allow two Transfer CFTs to store and forward files, Store and Forward mode.

The general file store and forward protocol principles are indicated in the Correspondences between
standardized PI codes and Transfer CFT application parameters, as supported by PeSIT.

Synchronous communication return codes

This section describes diagnosing the return code when using synchronous communication with
Transfer CFT.

How to find the return code

You can retrieve synchronous communication return codes using either a programming interface,
such as CAPI, or CFTUTIL.

Using a programming interface

In this method the cftau function locates the return code, as shown in the following example:

…
rc = cftau (“SWAITCAT”,” SELECT='IDTU==A000001’”)
if rc != 0 {
printf("SWAITCAT NOK RC=%d\n", rc);
…
}

Transfer CFT 3.1.3 Troubleshooting Guide 300

3 Messages and error codes

Using CFTUTIL
This method uses the internal variable_CMDRET in the SEND, RECV, or SWAITCAT commands to
retrieve the return code. You can create a script similar to the following example:

SWAITCAT SELECT='IDTU==”A000001”’
IF NAME = _CMDRET, VALUE = 0, TYPE = NEQ
PRINT MSG=”SWAITCAT NOK RC=”
PRINT MSG=%_CMDRET%
ENDIF

Note though that the _CMDRET value is not the same as the CFTUTIL return code, which could be:

l 0: no error
l 4: warning
l 8: error

In the following example the synchronous communication return code is 82, while the CFTUTIL is 8:

5:[CFU] SWAITCAT SELECT='IDTU=="A000001"'

CFTU25E SWAITCAT _ Error (SWAITCAT_NFOUND: select='IDTU=="A000001"' Not
Found)
CFTU00I (SELECT='IDTU=="A000001"')
6:[CFU] PRINT MSG=%_CMDRET%
82
CFTU00I PRINT _ Correct (MSG=82)
7:[CFU] /END
7:[CFU] CFTU00I RETURN _ Correct (CODE=8)
CFTU20I Number of Command(s) 6
CFTU20I Number of error(s) 1
CFTU20I Ending Session on 21/06/2012 Time is 16:06:32
CFTU20I Session active for 0:01:42

Send and receive related errors

For the return codes 70 through 79, the error occurred in the SEND or RECV transfer command, and
the transfer was not executed.

RC Error Description Action

70 APIS_READ_ Media configuration file error.

CONF_FILE

Transfer CFT 3.1.3 Troubleshooting Guide 301

3 Messages and error codes

RC Error Description Action

71 APIS_PARAM_ TIMEOUT parameter error. Refer to TIMEOUT in the

TIMEOUT Transfer CFT User's Guide.

72 APIS_PARAM_ LOWPORT parameter error. Refer to LOWPORT in the

LOWPORT Transfer CFT User's Guide.

73 APIS_PARAM_ HIGHPOINT parameter error. Refer to HIGHPORT in the

HIGHPORT Transfer CFT User's Guide.

74 APIS_PARAM_ LOWPORT and HIGHPORT are See above parameters.

BOTHPORT incompatible or incorrect.

75 APIS_CREATE_ Create channel failed.

SOCKET

76 APIS_OPEN_ Open channel failed.

SOCKET

77 APIS_ Channel write error occurred.

SOCKET_
WRITE

78 APIS_ Channel read error occurred

SOCKET_READ

79 APIS_CLOSE_ Close channel failed occurred.

SOCKET

SWAITCAT related errors

For the return codes 80 through 87, the error is related to the SWAITCAT command. Refer to the
SWAITCAT sections in the Transfer CFT User's Guide for more information.

RC Error Description Action

80 APIS_ Transfer error.The transfer reached the K or H Check the

SWAITCAT_ state. diagnostic, correct
FAILED problem if
necessary, and
restart.

Transfer CFT 3.1.3 Troubleshooting Guide 302

3 Messages and error codes

RC Error Description Action

81 APIS_ The transfer was not completed within the time Check the
SWAITCAT_ specified by the timeout value. After this timeout diagnostic, correct
TIMEOUT error, the transfer can have the status C (current) problem if
or D (for example if the network went down), but necessary.
note that it was not completed. Repeat SWAITCAT,
you may need to
repeat several times.

82 APIS_ The idtu was not found. The selected criteria Verify the selection
SWAITCAT_ provided in the command SWAITCAT cannot find parameters in the
NFOUND the transfer. SWAITCAT
command.

83 APIS_ Cannot find the transfer (transfer was deleted). The transfer was
SWAITCAT_ created but for some
DELETED reason it was
removed, for
example by the
DELETE command.

84 APIS_ The command contained an invalid parameter. Error in the

SWAITCAT_ command syntax.
PARAM_ Check the command
ERROR parameters in the
Transfer CFT User's
Guide.

87 APIS_ The number of transfers corresponding to the Refine the selection

SWAITCAT_ filter selection for the SWAITCAT command was criteria for the
TOO_MANY greater than 1. You cannot select more than 1 command so that it
transfer. returns a single
transfer.

Transfer CFT 3.1.3 Troubleshooting Guide 303