tivoli data exchange version 1.2.0 messages and...

Tivoli Data ExchangeTivoli Data ExchangeTivoli Data ExchangeTivoli Data ExchangeVersion 1.2.0Version 1.2.0Version 1.2.0Version 1.2.0Messages and CodesMessages and CodesMessages and CodesMessages and Codes

Copyright 2001, Tivoli, Inc. All rights reserved.

Tivoli Data Exchange, Tivoli, and the Tivoli logo are registered trademarks or trademarks of Tivoli, Inc. AS/400,AIX, MQSeries, and OS/390 are registered trademarks of IBM Corp. InstallShield is a registered trademark ofInstallShield Software Corporation. Windows NT is a registered trademark of Microsoft Corp. UNIX is a registeredtrademark of The Open Group. Solaris and Java and all Java-based trademarks and logos are trademarks orregistered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All other trademarks are propertyof their respective owners.

ContentsContentsContentsContents

chapter 1chapter 1chapter 1chapter 1 About This GuideAbout This GuideAbout This GuideAbout This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7777Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Where to Look for More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

chapter 2chapter 2chapter 2chapter 2 Messages and CodesMessages and CodesMessages and CodesMessages and Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11111111Interpreting Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Locating the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Where to Find Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Tivoli Data Exchange Components . . . . . . . . . . . . . . . . . . . . . . . . . . 15Additional Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Informational Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17FTFRCI_NO_STATUS_MESSAGES_PRESENT . . . . . . . . . . . . . . . 19FTFRCI_REQUEST_EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20FTFRCI_REQUEST_COMPLETE . . . . . . . . . . . . . . . . . . . . . . . . . . 21FTFRCI_REQUEST_COMPLETE_UNSUCCESSFUL . . . . . . . . . . 22FTFRCI_REQUEST_CANCELLED . . . . . . . . . . . . . . . . . . . . . . . . . 23FTFRCI_REPLY_TO_PING_FAILED . . . . . . . . . . . . . . . . . . . . . . . 24FTFRCI_PING_COMPLETE_UNSUCCESSFUL . . . . . . . . . . . . . . 25FTFRCI_CANCEL_PENDING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26FTFRCI_RETRY_LIMIT_EXCEEDED . . . . . . . . . . . . . . . . . . . . . . 27FTFRCI_REQUEST_FLAGGED_FOR_EXPIRATION . . . . . . . . . . 28FTFRCI_NO_MORE_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29FTFRCI_RESEND_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31FTFRCW_NO_STATUS_MESSAGE_FOR_ID . . . . . . . . . . . . . . . . 32FTFRCW_STATUS_MESSAGE_PROCESSING_FAILED . . . . . . . 33FTFRCW_TXN_NOT_FOUND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34FTFRCW_INVALID_REPLY_DESTINATION . . . . . . . . . . . . . . . . 35FTFRCW_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37FTFRCE_MEMORY_ALLOCATION_FAILURE . . . . . . . . . . . . . . 42FTFRCE_MQPUT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43FTFRCE_MQCONNECT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . 44FTFRCE_MQOPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Tivoli Data Exchange Messages and Codes iii

FTFRCE_MQGET_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46FTFRCE_MQCMIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47FTFRCE_INPUT_REQUIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48FTFRCE_INVALID_OPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49FTFRCE_CONFIGFILE_ACCESS_FAILURE . . . . . . . . . . . . . . . . 50FTFRCE_MQINQ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51FTFRCE_CONTROL_MSG_NOT_FOUND . . . . . . . . . . . . . . . . . . 52FTFRCE_COMMAND_LINE_PROCESSING_FAILED . . . . . . . . 53FTFRCE_CONFIG_FILE_PROCESSING_FAILED . . . . . . . . . . . . 54FTFRCE_FTF_INITIALIZATION_FAILED . . . . . . . . . . . . . . . . . . 55FTFRCE_SYNCQ_PROCESSING_FAILED . . . . . . . . . . . . . . . . . . 56FTFRCE_CONTROLQ_PROCESSING_FAILED . . . . . . . . . . . . . . 57FTFRCE_MQBROWSE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 58FTFRCE_UNKNOWN_MESSAGE_TYPE . . . . . . . . . . . . . . . . . . . 59FTFRCE_MQCMIT_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60FTFRCE_REQUEST_PROCESSING_FAILED . . . . . . . . . . . . . . . . 61FTFRCE_INVALID_CONFIGURATION . . . . . . . . . . . . . . . . . . . . . 62FTFRCE_CANCELLATION_FAILURE . . . . . . . . . . . . . . . . . . . . . 63FTFRCE_SUBMIT_CANCEL_MESSAGE_FAILED . . . . . . . . . . . 64FTFRCE_SENDER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65FTFRCE_SUBMIT_REPLY_FAILURE . . . . . . . . . . . . . . . . . . . . . . 66FTFRCE_RECEIVER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . 67FTFRCE_FILE_IS_A_DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . 68FTFRCE_FILE_ALREADY_EXISTS . . . . . . . . . . . . . . . . . . . . . . . 69FTFRCE_UNABLE_TO_CREATE_DIRECTORY . . . . . . . . . . . . . 70FTFRCE_FILE_DOES_NOT_EXIST . . . . . . . . . . . . . . . . . . . . . . . . 71FTFRCE_INVALID_FILEHANDLE . . . . . . . . . . . . . . . . . . . . . . . . 72FTFRCE_INVALID_FILEMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . 73FTFRCE_FILE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . 74FTFRCE_INVALID_FILENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . 75FTFRCE_FILEWRITE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76FTFRCE_DYNALLOC_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . 77FTFRCE_UNSUPPORTED_FILETYPE . . . . . . . . . . . . . . . . . . . . . 78FTFRCE_CONFIG_FILE_NOT_SPECIFIED . . . . . . . . . . . . . . . . . 79FTFRCE_UNKNOWN_FTF_COMPONENT . . . . . . . . . . . . . . . . . 80FTFRCE_INVALID_TIMEOUT_VALUE . . . . . . . . . . . . . . . . . . . . 81FTFRCE_UUID_CREATE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . 82FTFRCE_MISSING_PARAMETER . . . . . . . . . . . . . . . . . . . . . . . . . 83FTFRCE_REPLY_PROCESSING_FAILED . . . . . . . . . . . . . . . . . . . 84FTFRCE_REPLY_TIMED_OUT . . . . . . . . . . . . . . . . . . . . . . . . . . . 86FTFRCE_FILE_READ_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . 87FTFRCE_INVALID_ARGUMENT . . . . . . . . . . . . . . . . . . . . . . . . . 88FTFRCE_INVALID_ICCQUEUE . . . . . . . . . . . . . . . . . . . . . . . . . . . 89FTFRCE_SOURCE_PREPROC_FAILED . . . . . . . . . . . . . . . . . . . . 90

iv Tivoli Data Exchange Messages and Codes

FTFRCE_INVALID_EXITNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . 91FTFRCE_INVALID_ENTRYPOINT . . . . . . . . . . . . . . . . . . . . . . . . . 92FTFRCE_EXITLOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93FTFRCE_EXITUNLOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . 94FTFRCE_EXIT_NO_PATH_SPECIFIED . . . . . . . . . . . . . . . . . . . . . 95FTFRCE_EXIT_PATH_TOO_BIG . . . . . . . . . . . . . . . . . . . . . . . . . . 96FTFRCE_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97FTFRCE_DYNFREE_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98FTFRCE_RECORD_TOOBIG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99FTFRCE_SOURCE_POSTPROC_FAILED . . . . . . . . . . . . . . . . . . 100FTFRCE_MANAGER_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . . 101FTFRCE_LOG_FILE_OPEN_FAILURE . . . . . . . . . . . . . . . . . . . . 102FTFRCE_INVALID_RECORDLENGTH . . . . . . . . . . . . . . . . . . . . 103FTFRCE_INVALID_BLKSIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104FTFRCE_INVALID_UNITNAME . . . . . . . . . . . . . . . . . . . . . . . . . . 105FTFRCE_INVALID_ALCUNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . 106FTFRCE_INVALID_FILEORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107FTFRCE_INVALID_RECORDFORMAT . . . . . . . . . . . . . . . . . . . . 108FTFRCE_MGRPRE_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . 109FTFRCE_MGRPOST_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . 110FTFRCE_SDRPRE_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . 111FTFRCE_SDRPOST_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . 112FTFRCE_RCVPRE_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . . . 113FTFRCE_RCVPOST_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . 114FTFRCE_SDRAUTH_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . 115FTFRCE_RCVAUTH_EXIT_FAILURE . . . . . . . . . . . . . . . . . . . . . 116FTFRCE_RECEIVE_IMMED_TIMEOUT . . . . . . . . . . . . . . . . . . . 117FTFRCE_SEND_IMMED_TIMEOUT . . . . . . . . . . . . . . . . . . . . . . 118FTFRCE_RECEIVE_IMMED_RECOVERY . . . . . . . . . . . . . . . . . 119FTFRCE_COMPRESSION_NOT_SUPPORTED . . . . . . . . . . . . . . 120FTFRCE_INVALID_CONFIG_STANZA_VALUE . . . . . . . . . . . . 121FTFRCE_MISSING_CONFIG_STANZA . . . . . . . . . . . . . . . . . . . . 122FTFRCE_NO_AVAILABLE_SYNC_QUEUE . . . . . . . . . . . . . . . . 123FTFRCE_ERROR_CHECKING_DATA . . . . . . . . . . . . . . . . . . . . . 124FTFRCE_UNABLE_TO_PROCESS_STAGE_ITEM . . . . . . . . . . . 125FTFRCE_FILE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126FTFRCE_MISSING_CONFIG_SECTION . . . . . . . . . . . . . . . . . . . 127FTFRCE_UNABLE_TO_PROCESS_REQUEST . . . . . . . . . . . . . . 128FTFRCE_INVALID_QUEUE_MANAGER_NAME . . . . . . . . . . . 129FTFRCE_INVALID_RESEND_REQUEST . . . . . . . . . . . . . . . . . . 130FTFRCE_ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FATAL_ERROR 131FTFRCE_INTERNAL_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132FTFRCE_NO_STAGE_QUEUES_DEFINED . . . . . . . . . . . . . . . . . 133FTFRCE_SECURITY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Tivoli Data Exchange Messages and Codes v

FTFRCE_UNABLE_TO_RETRIEVE_USERID . . . . . . . . . . . . . . 135FTFRCE_SOURCE_FILENAME_NOT_SPECIFIED . . . . . . . . . . 136FTFRCE_DEST_FILENAME_NOT_SPECIFIED . . . . . . . . . . . . . 137FTFRCE_SOURCE_QMGR_NOT_SPECIFIED . . . . . . . . . . . . . . 138FTFRCE_DEST_QMGR_NOT_SPECIFIED . . . . . . . . . . . . . . . . . 139FTFRCE_INVALID_DATA_POOL . . . . . . . . . . . . . . . . . . . . . . . . 140FTFRCE_UNABLE_TO_RETRIEVE_SECURITY_CONTEXT . 141FTFRCE_AS400_FILE_DIFFERS_FROM_SPECIFIED . . . . . . . . 142FTFRCE_AS400_INVALID_RCDLEN . . . . . . . . . . . . . . . . . . . . . 143FTFRCE_AS400_ERROR_CREATING_LIBRARY . . . . . . . . . . . 144FTFRCE_AS400_CRTLIB_NOT_SPECIFIED . . . . . . . . . . . . . . . 145FTFRCE_AS400_ERROR_CREATING_SRCPF . . . . . . . . . . . . . . 146FTFRCE_AS400_NOREPLACE_SPECIFIED . . . . . . . . . . . . . . . . 147FTFRCE_AS400_ERROR_CREATING_SAVEF . . . . . . . . . . . . . . 148FTFRCE_AS400_ERROR_CLEARING_SAVEF . . . . . . . . . . . . . 149FTFRCE_NON_PERSIST_STAGE_DATA_NOT_FOUND . . . . . 150FTFRCE_INVALID_DIRBLOCKS . . . . . . . . . . . . . . . . . . . . . . . . 151FTFRCE_INVALID_MODEL_DATASET . . . . . . . . . . . . . . . . . . . 152FTFRCE_FILE_CLOSE_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . 153FTFRCE_CONFIG_FILE_NOT_FOUND . . . . . . . . . . . . . . . . . . . 154FTFRCE_INVALID_FTFCFG_QUEUE . . . . . . . . . . . . . . . . . . . . . 155FTFRCE_TIME_SLICING_FAILED . . . . . . . . . . . . . . . . . . . . . . . 156FTFRCE_INVALID_IMMED_STAGEONLY_COMBINATION . 157FTFRCE_INVALID_QMGR_LENGTH . . . . . . . . . . . . . . . . . . . . . 158FTFRCE_QUERY_STAGE_FAILED . . . . . . . . . . . . . . . . . . . . . . . 159FTFRCE_DLL_LOAD_FAILED . . . . . . . . . . . . . . . . . . . . . . . . . . 160FTFRCE_DBCS_PROCESSING_FAILED . . . . . . . . . . . . . . . . . . 161FTFRCE_COMPRESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . . . . 162FTFRCE_DECOMPRESS_FAILURE . . . . . . . . . . . . . . . . . . . . . . 163FTFRCE_BUFFERTOOSMALL . . . . . . . . . . . . . . . . . . . . . . . . . . . 164FTFRCE_INVALID_INPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165FTFRCE_MAX_MSG_SIZE_EXCEEDED . . . . . . . . . . . . . . . . . . 166FTFRCE_CONNECTOR_SEND_FAILURE . . . . . . . . . . . . . . . . . 167FTFRCE_CONNECTOR_RECEIVE_FAILURE . . . . . . . . . . . . . . 168FTFRCE_CONNECTOR_CONNECTOR_REQUIRED . . . . . . . . 169FTFRCE_UNKNOWN_CONNECTOR_FILETYPE . . . . . . . . . . . 170FTFRCE_XML_CONVERSION_FAILURE . . . . . . . . . . . . . . . . . 171FTFRCE_XML_PROCESSING ERROR . . . . . . . . . . . . . . . . . . . . 172FTFRCE_BATCHCOUNT_EXCEEDED . . . . . . . . . . . . . . . . . . . . 173FTFRCE_DATABASE_CONNECTION_ERROR . . . . . . . . . . . . . 174

IndexIndexIndexIndex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175175175175

vi Tivoli Data Exchange Messages and Codes

c h a p t e r 1

About This GuideAbout This GuideAbout This GuideAbout This Guide

The Messages and Codes guide lists and describes the error messages generatedby . It also describes the actions required to solve the problem that produced theerror message.

This chapter describes the information in this manual and the conventions usedto present the information. It contains the following sections:

Assumptions

This guide assumes that MQSeries and . have been installed and configuredaccording to the appropriate directions.

SectionSectionSectionSection PagePagePagePage

Intended Audience 8

How This Guide Is Organized 8

Contacting Customer Support 8

Where to Look for More Information 9

Conventions 9

Tivoli Data Exchange Messages and Codes 7

About This GuideAbout This GuideAbout This GuideAbout This GuideIntended Audience

Intended AudienceIntended AudienceIntended AudienceIntended AudienceThis guide is intended for the following groups:

• Developers using to design file-transfer solutions

• Users performing solutions

• administrators

• MQSeries administrators

• System administrators for the machine on which is running

How This Guide Is OrganizedHow This Guide Is OrganizedHow This Guide Is OrganizedHow This Guide Is OrganizedThe following table lists and describes the parts and chapters in this manual.

Contacting Customer SupportContacting Customer SupportContacting Customer SupportContacting Customer SupportWe are very interested in hearing from you about your experience with Tivoliproducts and documentation. We welcome your suggestions for improvements.If you have comments or suggestions about this documentation, please sende-mail to [email protected].

If you encounter difficulties with Tivoli products, contact Tivoli CustomerSupport. In the United States, the Tivoli number is 1-800-TIVOLI8 and the IBMnumber is 1-800-237-5511 (press or say 8 after you reach this number). Both ofthese numbers direct your call to the Tivoli Customer Support call center. Inaddition, you can enter http://www.tivoli.com/support to view the TivoliCustomer Support home page.

After you link to and submit the customer registration form, you will be able toaccess many customer support services on the Web. For support services outsidethe United States and Puerto Rico, contact your local IBM representative or yourauthorized IBM supplier.

ChapterChapterChapterChapter TitleTitleTitleTitle PurposePurposePurposePurpose

1 About This Guide Describes this manual and its contents.

2 Messages and Codes Lists and describes the messages and codes and listscorrective actions for solving the conditions that caused thecode’s generation.

8 Tivoli Data Exchange Messages and Codes

About This GuideAbout This GuideAbout This GuideAbout This GuideWhere to Look for More Information

Where to Look for More InformationWhere to Look for More InformationWhere to Look for More InformationWhere to Look for More InformationInformation about MQSeries issues is available in the MQSeries documentation.The IBM corporate website includes a web page that lists the MQSeries manualsand allows you access to an online version of each manual. At publication time,this page’s URL was:http://www.software.ibm.com/ts/mqseries/library/manuals.

ConventionsConventionsConventionsConventionsThe following elements are used in this guide to make it easier to use:

All syntax,operating system terms, and literalexamples are presented in this typeface.

Italics in a command string signify variables.

Text enclosed in angle brackets (< >) contains variable information. Replace thevariable information with the actual value.

The word select is used in text in the context of carrying out a series of menuchoices to invoke some function.

Note:Note:Note:Note:Notes provide additional information about the currentsubject.

Warning:Warning:Warning:Warning:Warnings alert you to situations that can cause problems,such as the loss of data, if you do not carefully followinstructions.

SidebarSidebarSidebarSidebarSidebars contain information that does not fit specificallywith the flow of the current topic, but is important to thetopic. Sidebars are usually a short topic.


c h a p t e r 2

Messages and CodesMessages and CodesMessages and CodesMessages and Codes

This chapter lists and describes Tivoli Data Exchange messages and codes andlists corrective actions for solving the conditions listed in each code. For eachcode, it lists the following information:

• Message number• Description• Tivoli Data Exchange user action• Tivoli Data Exchange administrator action• MQSeries administrator action• System administrator action• Comments

The messages and codes listed in this chapter are arranged in the followinggroups:

• Informational messages• Warning messages• Error messages

This chapter contains the following sections:

SectionSectionSectionSection PagePagePagePage

Interpreting Error Codes 12

Informational Messages 17

Warning Messages 31

Error Messages 37


Messages and CodesMessages and CodesMessages and CodesMessages and CodesInterpreting Error Codes

Interpreting Error CodesInterpreting Error CodesInterpreting Error CodesInterpreting Error Codes

Locating the Log File

Messages and codes from Tivoli Data Exchange are written to the log file as textentries. You can use any text editor to display the contents of the log file. The-lfile argument specified either in the Tivoli Data Exchange command or in theconfiguration file names the file and path of the log file. For information aboutTivoli Data Exchange logging capabilities look in the Tivoli Data ExchangeUser’s Guide, “Logging Information.”

Where to Find Error Codes

Tivoli Data Exchange generates error messages to the log file and optionally tothe command line. In OS/390, log messages are written to the SYSOUT for theFTFSTART job, see “Initializing” in the Tivoli Data Exchange InstallationGuide. Log messages are written under the following conditions:

• A transaction is interrupted.

• A transaction cannot start.

• A transaction has completed.

When the error message is written to the log file, two numbers appear with themessage’s text. The first number is the primary return code; the second numberis the secondary return code. When an error message appears in the log file, itappears as two nine digit numbers at the beginning of the line. The generalformat of the line is:

timeValue ppppppppp:sssssssss msgText

Where:

• timeValue - Contains the hour, minute, and second of the time themessage line was written. Format: hh:mm:ss.

• ppppppppp - Represents the primary return code. Often the first numberis nine digits with the first digit not being zero. If the first digit is notzero, the number is in three parts:



1. The first three digits contain the number of the component causingthe error. See “Tivoli Data Exchange Components” on page 15.

2. The second three digits contain the line-number of code issuing themessage.

3. The last three digits contain the Tivoli Data Exchange errornumber.

• sssssssss - Represents the secondary return code. These nine digitsindicate one of three situations:

1. The is in the same format as the primary return code.Consequently, Tivoli Data Exchange returns a second errorcondition.

2. The secondary return code begins with five zeros (00000). In thiscase the last four digits are an MQSeries error code.

3. The secondary return code is all zeros. In this case there is nosecondary return code.

• msgText - is the text associated with the error number.

ExampleExampleExampleExample

The following figure contains an example of a Tivoli Data Exchange log file:

The first five lines of the log contain startup information messages. Lines sixand seven contain error messages.

The error numbers in line six are 101409601:000002051. These numbers can bedeciphered as follows:



• The first number breaks into three separate codes based on thefollowing table:

• The second return code contains five zeros in the first five positionwhich indicates that the return code is an MQSeries code.

2051 is an MQSeries error code number. It can be referenced in theMQSeries documentation, See “Where to Look for More Information”on page 11.

The numbers in line seven are 101335623:000000000. These numbers can bedeciphered as follows:

• The first number is breaks into three separate codes based on thefollowing table:

• The second number is 000000000, indicating that there is no secondaryerror number.

DigitsDigitsDigitsDigits SampleSampleSampleSample DescriptionDescriptionDescriptionDescription

1-3 101 The number of the Tivoli DataExchange component having theproblem. See “Tivoli DataExchange Components” on page15.

4-6 409 The line of source code in theprogram where the message wasissued.

7-9 601 The message number to referencein this manual.

DigitsDigitsDigitsDigits SampleSampleSampleSample DescriptionDescriptionDescriptionDescription

1-3 101 The Tivoli Data Exchangecomponent having the problem.See “Tivoli Data ExchangeComponents” on page 15

4-6 335 The line of source code in theprogram where the message wasissued.

7-9 623 The message number to referencein this manual



Tivoli Data Exchange Components

The table that follows relates the number that appears in the first three digits ofthe error code to the component within Tivoli Data Exchange.

NumberNumberNumberNumber ComponentComponentComponentComponent

100 FTFCPT_RECEIVER

101 FTFCPT_SENDER

102 FTFCPT_SENDER_DATABLK

103 FTFCPT_SENDER_PROCESS

104 FTFCPT_SENDER_RECOVER

105 FTFCPT_SENDER_SENDER

106 FTFCPT_MANAGER

107 FTFCPT_PRE_POST_PROCESS_MONITOR

108 FTFCPT_REQUEST_API

109 FTFCPT_PING_API

110 FTFCPT_STATUS_API

111 FTFCPT_SHUTDOWN_API

112 FTFCPT_REQUEST_CL

113 FTFCPT_PING_CL

114 FTFCPT_STATUS_CL

115 FTFCPT_SHUTDOWN_CL

116 FTFCPT_MESSAGE_INTERFACE_HANDLER

117 FTFCPT_TMTGUI

118 FTFCPT_ISPFGUI

119 FTFCPT_STATUS_REPORT

120 FTFCPT_SHUTDOWN

121 FTFCPT_STATUS

122 FTFCPT_REQUEST

123 FTFCPT_PING

124 FTFCPT_CANCEL

125 FTFCPT_CANCEL_API

126 FTFCPT_CANCEL_CL

127 FTFCPT_FTFSTART



128 FTFCPT_STAGE_API

129 FTFCPT_STAGE_CL

130 FTFCPT_LOG

131 FTFCPT_CFG

132 FTFCPT_STATD

133 FTFCPT_STATD_API

134 FTFCPT_STATD_CL

NumberNumberNumberNumber ComponentComponentComponentComponent


Messages and CodesMessages and CodesMessages and CodesMessages and CodesInformational Messages

Additional Error Messages

Some components issue messages not contained in this manual. Other TivoliData Exchange manuals contain the following chapters which have their ownsections of error or status messages:

• Directory Monitor (Tivoli Data Exchange User’s Guide)

• Multi-File Connector (Tivoli Data Exchange Technical Reference)

• File to Message Connector (Tivoli Data Exchange TechnicalReference)

• Virtual Machine Connector (Tivoli Data Exchange TechnicalReference)

Informational MessagesInformational MessagesInformational MessagesInformational MessagesInformational messages pass useful information about Tivoli Data Exchangeprocessing. Informational message codes start with FTFRCI. These messages donot affect the outcome of the transaction. Usually, they do not requireintervention.

The following informational messages are described in this section.

NumberNumberNumberNumber Message TextMessage TextMessage TextMessage Text PagePagePagePage

001 FTFRCI_NO_STATUS_MESSAGES_PRESENT 19

002 FTFRCI_REQUEST_EXPIRED 20

003 FTFRCI_REQUEST_COMPLETE 21

004 FTFRCI_REQUEST_COMPLETE_UNSUCCESSFUL 22

005 FTFRCI_REQUEST_CANCELLED 23

006 FTFRCI_REPLY_TO_PING_FAILED 24

007 FTFRCI_PING_COMPLETE_UNSUCCESSFUL 25

008 FTFRCI_CANCEL_PENDING 26

009 FTFRCI_RETRY_LIMIT_EXCEEDED 27

010 FTFRCI_REQUEST_FLAGGED_FOR_EXPIRATION 28



011 FTFRCI_NO_MORE_DATA 29

012 FTFRCI_RESEND_DATA 30




FTFRCI_NO_STATUS_MESSAGES_PRESENT

Numeric ValueNumeric ValueNumeric ValueNumeric Value

001

DescriptionDescriptionDescriptionDescription

No message for the ID was found in the status queues. The messages isdisplayed as a result of running a status query and the logs contain no messagesassociated with the ID that was entered as part of the query.

Tivoli Data ExchangeTivoli Data ExchangeTivoli Data ExchangeTivoli Data Exchange User Actions User Actions User Actions User Actions

None.

Tivoli Data ExchangeTivoli Data ExchangeTivoli Data ExchangeTivoli Data Exchange Administrator Actions Administrator Actions Administrator Actions Administrator Actions

None.

MQSeries Administrator ActionsMQSeries Administrator ActionsMQSeries Administrator ActionsMQSeries Administrator Actions

None.

System Administrator ActionsSystem Administrator ActionsSystem Administrator ActionsSystem Administrator Actions

None.

CommentsCommentsCommentsComments

If you are using FTFSTAT, the message “No transfer events found for output”appears on the command line. This message does not appear in the logs.



FTFRCI_REQUEST_EXPIRED


002


Because the system date is past the expiration date of the transaction, thetransaction has expired. No further processing on that transaction will occur.


Refer to the Tivoli Data Exchange User’s Guide to see what user actions cancause a transaction to expire and how to correct the problem.


None


None


The expiration could have accrued because the system clock on one of the nodesinvolved is set incorrectly. If so, set the time and time zone of the machine andresubmit the transaction.


See “Interpreting Error Codes” on page 12.



FTFRCI_REQUEST_COMPLETE


003


Indicates that a particular transaction is complete. Although the message isgenerated for transactions that finish because of error, these transactions produceother messages, as well.


None.


None.


None.


None.


None.



FTFRCI_REQUEST_COMPLETE_UNSUCCESSFUL


004


Indicates unsuccessful completion of a file transfer transaction.


Determine the cause of the error from the error codes listed in the appropriatelog files.


Determine the cause of the error from the error codes listed in the appropriatelog files. The error might result from an incorrect Tivoli Data Exchangeconfiguration.


Determine the cause of the error from the error codes listed in the appropriatelog files. The error might result from an incorrect MQSeries configuration.


Determine the cause of the error from the error codes listed in the appropriatelog files. This error might result from a system configuration error.


None.



FTFRCI_REQUEST_CANCELLED


005


The Tivoli Data Exchange transaction has been cancelled due to a user request.


None.


None.


None.


None.


None.



FTFRCI_REPLY_TO_PING_FAILED


006


The Tivoli Data Exchange component was unable to reply to a Ping request.Because failure of a ping request is not considered critical, the message isinformational and the Tivoli Data Exchange components continue to run.


Verify entries in the calling interface for correct specification of the queuemanager names. If the names are correct, notify the Tivoli Data ExchangeAdministrator with the specific return code and reason code.


Verify the Tivoli Data Exchange configuration file for correct specification ofthe queue names for all components. Verify the queue name specification(specifically the CONTROL queue names) for the corresponding component onall the communicating nodes.

If the secondary return code is MQSeries related, verify with the MQSeriesAdministrator that the MQSeries definition correct.


If the error is MQSeries related, verify that the MQSeries configuration has beencarried out correctly. Tivoli Data Exchange provides the MQSeries reason codevalue for every failing MQSeries operation that Tivoli Data Exchange uses.


None.


See “FTFPING” in the Tivoli Data Exchange User’s Manual for help with theFTFPING command.



FTFRCI_PING_COMPLETE_UNSUCCESSFUL


007


The Tivoli Data Exchange Ping request has completed unsuccessfully.


Verify that all the queue managers entered into the calling interface werespecified correctly and notify the Tivoli Data Exchange administrator.


See “FTFPING” in the Tivoli Data Exchange User Guide for an understandingof the flow of the Tivoli Data Exchange Ping request. This message is issuedwhen the Tivoli Data Exchange manager component on the originating queuemanager (oqm) is unable to communicate to the Tivoli Data Exchange sender onthe source queue manager (sqm). This condition usually arises due to invalidspecification of the queue manager names or to incorrect MQSeriesconfiguration. The MQSeries object names, type of operation, and the MQSeriesreason code are logged by the Tivoli Data Exchange Manager. Determine theappropriate action and notify the MQSeries administrator.


If the MQSeries reason code indicates a configuration error, modify theMQSeries configuration and try the operation again.


If the MQSeries reason code indicates a system related problem (resource orsystem configuration), consult the appropriate MQSeries manuals and correctthe error.


See “Troubleshooting FTFPING” in the Tivoli Data Exchange User’s Manualfor help with the FTFPING command.



FTFRCI_CANCEL_PENDING


008


The Tivoli Data Exchange transaction has been marked as canceled due a userrequest. The message indicates that the cancel was entered, but the cancelrequest still needs to be sent to all components to be effective.


None.


None.


None.


None.


None.



FTFRCI_RETRY_LIMIT_EXCEEDED


009


Attempts to complete the Tivoli Data Exchange transaction were unsuccessfulafter exhausting the maximum number of retries allowed by Tivoli DataExchange.


Notify the Tivoli Data Exchange administrator. After the Tivoli Data Exchangeadministrator has taken corrective actions, reissue the command if necessary.


Tivoli Data Exchange attempted to retry the failing request the maximumnumber of times. View the logs from the different Tivoli Data Exchangecomponents (Manager, Sender and Receiver) and determine the root cause of theretry limit exhaustion. This condition could be due to Tivoli Data ExchangeConfiguration error, MQSeries configuration error, or system resourceshortages.


Verify the MQSeries configuration for any errors.


Verify that system resources are available.


None.



FTFRCI_REQUEST_FLAGGED_FOR_EXPIRATION


010


The Tivoli Data Exchange transaction has been marked for expiration by theTivoli Data Exchange Manager on the oqm. The actual request does not expireuntil either the Sender or the Receiver actually expires the request. Thisinformation message indicates that the Tivoli Data Exchange Managercomponent has not received the response for the expiration request from eitherthe Sender or Receiver.


None.


Verify that the configuration files on the communicating nodes use the sameMQSeries objects. View the logs of the Tivoli Data Exchange Sender andTivoli Data Exchange Receiver involved and verify that no error messages weregenerated for the particular Tivoli Data Exchange transaction.


Verify that the MQSeries channels are up between communicating nodes andthat no error conditions (queue full, put disabled, etc.) exist on the differentMQSeries objects used by Tivoli Data Exchange.


None.


None.



FTFRCI_NO_MORE_DATA


011


None.


None.


None.


None.


None.


None.



FTFRCI_RESEND_DATA


012


None.


None.


None.


None.


None.


None.


Messages and CodesMessages and CodesMessages and CodesMessages and CodesWarning Messages

Warning MessagesWarning MessagesWarning MessagesWarning MessagesWarning messages identify conditions that could lead to the failure of atransaction. These messages start with FTFRCW.

The warning messages listed in this section are:


300 FTFRCW_NO_STATUS_MESSAGE_FOR_ID 32

301 FTFRCW_STATUS_MESSAGE_PROCESSING_FAILED 33

302 FTFRCW_TXN_NOT_FOUND 34

303 FTFRCW_INVALID_REPLY_DESTINATION 35

304 FTFRCW_TIMEOUT 36



FTFRCW_NO_STATUS_MESSAGE_FOR_ID


300


No status messages were found for the ID that was entered in a status request.


Verify that the ID that was entered is correct.


None.


None.


None.


None.



FTFRCW_STATUS_MESSAGE_PROCESSING_FAILED


301


The Tivoli Data Exchange component in error was unable to process the statusmessage. Status messages are not required for the successful operation of TivoliData Exchange transactions. This message is issued if the Tivoli Data Exchangecomponent is unable to update the status subsystem with a new status.


None


Verify that the configuration file specifies correct names for the MQSeriesobjects for the status control and detail queue names. View the logs todetermine whether the error is MQSeries related and whether the MQSeriesreason code indicates a benign or severe error condition. Notify the MQSeriesadministrator.


Verify the maximum depth of the queues. Correct the MQSeries error, ifnecessary.


None.


See “Interpreting Error Codes” on page 12 for help deciphering the error codes.



FTFRCW_TXN_NOT_FOUND


302


The Tivoli Data Exchange transaction control message was not found in theinternal processing queues. This message is produced by the Tivoli DataExchange Manager in response to a cancel request from a user for analready-completed transaction or a response for a transaction arrives after thetransaction has been marked complete. Because of the flexibility provided byTivoli Data Exchange and MQSeries, messages from the different processingnodes for a particular transaction can arrive in any order. Tivoli Data ExchangeManager will issue this warning message if it receives a response from acomponent for a transaction that has already been completed.


None.


Network delays and incorrect Tivoli Data Exchange and MQSeriesconfigurations could be preventing the responses from reaching the Tivoli DataExchange Manager. Verify that the configuration settings are correct.


MQSeries configuration errors could be preventing the responses from reachingthe Tivoli Data Exchange Manager in the correct order. Verify that theMQSeries configuration is correct.


None.


None.



FTFRCW_INVALID_REPLY_DESTINATION


303


The Tivoli Data Exchange Manager on the current node received a responsefrom a node and the current node was not the intended recipient.


None.


Verify that the Tivoli Data Exchange configuration on both the current node andthe node originating the message is correct. View the log to see the message andthe node sending the message. Report the sending node to the MQSeriesadministrator.


Verify that the MQSeries configurations are correct. If you are using queuemanager alias features and are exploiting queue name resolution facilities ofMQSeries, it is possible that messages are ending up in queue managers notintended for them.


None.


None.



FTFRCW_TIMEOUT


304


The Tivoli Data Exchange Ping request has timed out.


Verify that the queue manager names specified in the Ping request are correctand reissue the request. If the problem persists, increase the timeout value in thePing request and reissue the request. Report any queue managers that haveresponded to the Tivoli Data Exchange administrator.


The Tivoli Data Exchange Ping request could time out due to a variety ofreasons. See “Troubleshooting FTFPING” in the Tivoli Data Exchange User’sGuide for help with FTFPING problems.


Tivoli Data Exchange Ping requests could time out due to MQSeries errors suchas channel down or incorrect channel configurations. Verify the log forMQSeries errors, determine the cause of the trouble, and correct it.


None.


When the message is generated to the logs, the following message appears onthe console: “FTF Ping timed out”.


Messages and CodesMessages and CodesMessages and CodesMessages and CodesError Messages

Error MessagesError MessagesError MessagesError MessagesError messages are generated for failed transactions and indicate the reason forfailure. These messages start with FTFRCE.

Error messages covered in this section are:


600 FTFRCE_MEMORY_ALLOCATION_FAILURE 42

601 FTFRCE_MQPUT_FAILURE 43

602 FTFRCE_MQCONNECT_FAILURE 44

603 FTFRCE_MQOPEN_FAILURE 45

604 FTFRCE_MQGET_FAILURE 46

605 FTFRCE_MQCMIT_FAILURE 47

606 FTFRCE_INPUT_REQUIRED 48

607 FTFRCE_INVALID_OPTION 49

608 FTFRCE_CONFIGFILE_ACCESS_FAILURE 50

609 FTFRCE_MQINQ_FAILURE 51

611 FTFRCE_CONTROL_MSG_NOT_FOUND 52

613 FTFRCE_COMMAND_LINE_PROCESSING_FAILED 53

614 FTFRCE_CONFIG_FILE_PROCESSING_FAILED 54

617 FTFRCE_FTF_INITIALIZATION_FAILED 55

618 FTFRCE_SYNCQ_PROCESSING_FAILED 56

619 FTFRCE_CONTROLQ_PROCESSING_FAILED 57

620 FTFRCE_MQBROWSE_FAILURE 58

621 FTFRCE_UNKNOWN_MESSAGE_TYPE 59

622 FTFRCE_MQCMIT_FAILED 60

623 FTFRCE_REQUEST_PROCESSING_FAILED 61

625 FTFRCE_INVALID_CONFIGURATION 62

626 FTFRCE_CANCELLATION_FAILURE 63

627 FTFRCE_SUBMIT_CANCEL_MESSAGE_FAILED 64

628 FTFRCE_SENDER_FAILURE 65

629 FTFRCE_SUBMIT_REPLY_FAILURE 66



630 FTFRCE_RECEIVER_FAILURE 67

631 FTFRCE_FILE_IS_A_DIRECTORY 68

632 FTFRCE_FILE_ALREADY_EXISTS 69

633 FTFRCE_UNABLE_TO_CREATE_DIRECTORY 70

634 FTFRCE_FILE_DOES_NOT_EXIST 71

635 FTFRCE_INVALID_FILEHANDLE 72

636 FTFRCE_INVALID_FILEMODE 73

637 FTFRCE_FILE_OPEN_FAILURE 74

638 FTFRCE_INVALID_FILENAME 75

639 FTFRCE_FILEWRITE_ERROR 76

640 FTFRCE_DYNALLOC_FAILED 77

641 FTFRCE_UNSUPPORTED_FILETYPE 78

642 FTFRCE_CONFIG_FILE_NOT_SPECIFIED 79

643 FTFRCE_UNKNOWN_FTF_COMPONENT 80

644 FTFRCE_INVALID_TIMEOUT_VALUE 81

645 FTFRCE_UUID_CREATE_FAILURE 82

646 FTFRCE_MISSING_PARAMETER 83

647 FTFRCE_REPLY_PROCESSING_FAILED 84

648 FTFRCE_REPLY_TIMED_OUT 86

649 FTFRCE_FILE_READ_FAILURE 87

650 FTFRCE_INVALID_ARGUMENT 88

651 FTFRCE_INVALID_ICCQUEUE 89

652 FTFRCE_SOURCE_PREPROC_FAILED 90

653 FTFRCE_INVALID_EXITNAME 91

654 FTFRCE_INVALID_ENTRYPOINT 92

655 FTFRCE_EXITLOAD_FAILED 93

656 FTFRCE_EXITUNLOAD_FAILED 94

658 FTFRCE_EXIT_NO_PATH_SPECIFIED 95

659 FTFRCE_EXIT_PATH_TOO_BIG 96

660 FTFRCE_EXIT_FAILURE 97

662 FTFRCE_DYNFREE_FAILED 98

663 FTFRCE_RECORD_TOOBIG 99




665 FTFRCE_SOURCE_POSTPROC_FAILED 100

667 FTFRCE_MANAGER_FAILURE 101

668 FTFRCE_LOG_FILE_OPEN_FAILURE 102

669 FTFRCE_INVALID_RECORDLENGTH 103

670 FTFRCE_INVALID_BLKSIZE 104

671 FTFRCE_INVALID_UNITNAME 105

672 FTFRCE_INVALID_ALCUNIT 106

673 FTFRCE_INVALID_FILEORG 107

674 FTFRCE_INVALID_RECORDFORMAT 108

675 FTFRCE_MGRPRE_EXIT_FAILURE 109

676 FTFRCE_MGRPOST_EXIT_FAILURE 110

677 FTFRCE_SDRPRE_EXIT_FAILURE 111

678 FTFRCE_SDRPOST_EXIT_FAILURE 112

679 FTFRCE_RCVPRE_EXIT_FAILURE 113

680 FTFRCE_RCVPOST_EXIT_FAILURE 114

681 FTFRCE_SDRAUTH_EXIT_FAILURE 115

682 FTFRCE_RCVAUTH_EXIT_FAILURE 116

683 FTFRCE_RECEIVE_IMMED_TIMEOUT 117

684 FTFRCE_SEND_IMMED_TIMEOUT 118

685 FTFRCE_RECEIVE_IMMED_RECOVERY 119

686 FTFRCE_COMPRESSION_NOT_SUPPORTED 120

701 FTFRCE_INVALID_CONFIG_STANZA_VALUE 121

702 FTFRCE_MISSING_CONFIG_STANZA 122

706 FTFRCE_NO_AVAILABLE_SYNC_QUEUE 123

708 FTFRCE_ERROR_CHECKING_DATA 124

711 FTFRCE_UNABLE_TO_PROCESS_STAGE_ITEM 125

712 FTFRCE_FILE_ERROR 126

713 FTFRCE_MISSING_CONFIG_SECTION 127

714 FTFRCE_UNABLE_TO_PROCESS_REQUEST 128

715 FTFRCE_INVALID_QUEUE_MANAGER_NAME 129

716 FTFRCE_INVALID_RESEND_REQUEST 130

717 FTFRCE_ FATAL_ERROR 131




718 FTFRCE_INTERNAL_ERROR 132

719 FTFRCE_NO_STAGE_QUEUES_DEFINED 133

720 FTFRCE_SECURITY_ERROR 134

722 FTFRCE_UNABLE_TO_RETRIEVE_USERID 135

723 FTFRCE_SOURCE_FILENAME_NOT_SPECIFIED 136

724 FTFRCE_DEST_FILENAME_NOT_SPECIFIED 137

725 FTFRCE_SOURCE_QMGR_NOT_SPECIFIED 138

726 FTFRCE_DEST_QMGR_NOT_SPECIFIED 139

727 FTFRCE_INVALID_DATA_POOL 140

728 FTFRCE_UNABLE_TO_RETRIEVE_SECURITY_CONTEXT 141

729 FTFRCE_AS400_FILE_DIFFERS_FROM_SPECIFIED 142

730 FTFRCE_AS400_INVALID_RCDLEN 143

731 FTFRCE_AS400_ERROR_CREATING_LIBRARY 144

732 FTFRCE_AS400_CRTLIB_NOT_SPECIFIED 145

733 FTFRCE_AS400_ERROR_CREATING_SRCPF 146

734 FTFRCE_AS400_NOREPLACE_SPECIFIED 147

735 FTFRCE_AS400_ERROR_CREATING_SAVEF 148

736 FTFRCE_AS400_ERROR_CLEARING_SAVEF 149

737* FTFRCE_NON_PERSIST_STAGE_DATA_NOT_FOUND 150

739 FTFRCE_INVALID_DIRBLOCKS 151

740 FTFRCE_INVALID_MODEL_DATASET 152

741 FTFRCE_FILE_CLOSE_FAILURE 153

742* FTFRCE_CONFIG_FILE_NOT_FOUND 154

743* FTFRCE_INVALID_FTFCFG_QUEUE 155

744* FTFRCE_TIME_SLICING_FAILED 156

745 FTFRCE_INVALID_IMMED_STAGEONLY_COMBINATION 150

746 FTFRCE_INVALID_QMGR_LENGTH 158

750 FTFRCE_QUERY_STAGE_FAILED 159

760* FTFRCE_DLL_LOAD_FAILED 160

761 FTFRCE_DBCS_PROCESSING_FAILED 161

801 FTFRCE_COMPRESS_FAILURE 162

802 FTFRCE_DECOMPRESS_FAILURE 163




803 FTFRCE_BUFFERTOOSMALL 164

804 FTFRCE_INVALID_INPUT 165

805* FTFRCE_MAX_MSG_SIZE_EXCEEDED 166

806* FTFRCE_CONNECTOR_SEND_FAILURE 167

807* FTFRCE_CONNECTOR_RECEIVE_FAILURE 168

808* FTFRCE_CONNECTOR_CONNECTOR_REQUIRED 169

809* FTFRCE_UNKNOWN_CONNECTOR_FILETYPE 170

810 FTFRCE_XML_CONVERSION_FAILURE 171

811 FTFRCE_XML_PROCESSING ERROR 172

812 FTFRCE_BATCHCOUNT_EXCEEDED 173

813 FTFRCE_DATABASE_CONNECTION_ERROR 174




FTFRCE_MEMORY_ALLOCATION_FAILURE


600


The Tivoli Data Exchange component issuing this error encountered a fatal errorin trying to allocate memory for its internal processing. Depending on the typeof operation the component is trying to execute, further processing may stop andthe component may terminate.


None.


Verify the logs to see which component is having the problem with memoryallocation. Restart that component.


None.


Verify to see if system resources are available.


None.



FTFRCE_MQPUT_FAILURE


601


The Tivoli Data Exchange component in error is unable to deposit a message inan MQSeries queue.


Report the error message to the Tivoli Data Exchange administrator.


Tivoli Data Exchange reports the MQSeries reason code from the MQPUT orMQPUT1 call as part of the secondary return code. Take corrective action basedon this reason code’s value.


Based on the MQSeries reason code for the PUT failure, you may have tocorrect the MQSeries configuration.


None.


None.



FTFRCE_MQCONNECT_FAILURE


602


The Tivoli Data Exchange component in error is unable to connect to the queuemanager.


Verify that the queue manager names specified in the calling interface arecorrect.


Tivoli Data Exchange reports the actual MQSeries reason code from theMQCONN call as part of the secondary return code. Take corrective actionbased on this reason code’s value.


Based on the MQSeries reason code for the connect failure, you may have tocorrect the MQSeries configuration.


None.





FTFRCE_MQOPEN_FAILURE


603


The Tivoli Data Exchange component in error is unable to open the specifiedqueue on the queue manager.


Verify that the queue names specified in the Tivoli Data Exchange configurationfile are correct.


Tivoli Data Exchange reports the MQSeries reason code from the MQOPEN callas part of the secondary return code. Take corrective action based on this reasoncode’s value.


Based on the MQSeries reason code for the open failure, you may have tocorrect the MQSeries configuration.


None.





FTFRCE_MQGET_FAILURE


604


The Tivoli Data Exchange component in error is unable to get a message froman MQSeries queue.


Report the error message to Tivoli Data Exchange administrator.


Tivoli Data Exchange reports the MQSeries reason code from the MQGET orMQGET1 calls as part of the secondary return code. Take corrective actionbased on this return code’s value.


Based on the MQSeries reason code for the get failure, you may have to correctthe MQSeries configuration.


None.





FTFRCE_MQCMIT_FAILURE


605


The Tivoli Data Exchange component in error is unable to issue an MQ commit.




Tivoli Data Exchange reports the MQSeries reason code from the commit call aspart of the secondary return code. If the reason code indicates a Tivoli DataExchange configuration problem, take corrective action based on its value.


Based on the MQSeries reason code for the commit failure, you may have tocorrect the MQSeries configuration.


Consider cleaning up disk space.





FTFRCE_INPUT_REQUIRED


606


More input is required by Tivoli Data Exchange on the command that wasentered at the calling interface.


Supply the input that is required. The missing input is probably the lqm optionrequired when you use Tivoli Data Exchange on an OS/390 system.


None.


None.


None.


When the message is generated to the logs, the following message appears onthe console: “Invalid options specified” appears on the console.



FTFRCE_INVALID_OPTION


607


An invalid option was specified on the command line.


Correct the command line argument and reissue the command.


None.


None.


None.


When the message is generated to the logs, the following message appears onthe console: “Invalid options specified” appears on the console.



FTFRCE_CONFIGFILE_ACCESS_FAILURE


608


Tivoli Data Exchange was unable to access the Tivoli Data Exchangeconfiguration file.




Be sure the Tivoli Data Exchange configuration file is available on the specifiedpath. This path is specified either in the configuration file option in the callinginterface or setting environment variables to point to the file.


None.


Verify permissions on the Tivoli Data Exchange configuration file.


None.



FTFRCE_MQINQ_FAILURE


609


The Tivoli Data Exchange component in error is unable to inquire the queuemanager to which it is connected.




Tivoli Data Exchange reports the MQSeries reason code from the MQINQ callas part of the secondary return code. Take corrective action based on this reasoncode’s value.


Based on the MQSeries reason code for the MQINQ failure, you may have tocorrect the MQSeries configuration.


None.


None.



FTFRCE_CONTROL_MSG_NOT_FOUND


611


The control message defining the transfer request is not found on the receiver'squeue. The transaction fails.


Verify inputs to file transfer request to ensure all parameters are valid. Resubmitthe request.


None.


Verify the Tivoli Data Exchange's queue depths on the receiver’s queuemanager.

• If the queues are full, a component in the system may have failed,preventing messages from being processed. Restart any failed components.

• If the queues are not full, contact Technical Support (see page 10 for contactinformation).


None.


None.



FTFRCE_COMMAND_LINE_PROCESSING_FAILED


613


The Tivoli Data Exchange component in error is unable to process thecommand-line arguments.


Correct the command line in error and reissue the command.


None.


None.


None.


None.



FTFRCE_CONFIG_FILE_PROCESSING_FAILED


614


The Tivoli Data Exchange component in error is unable to process the TivoliData Exchange configuration file.


None.


Tivoli Data Exchange reports the section and stanza of the configuration file thatis in error in the error log. Correct the section that is in error and reissue thecommand.


None.


None.


None.



FTFRCE_FTF_INITIALIZATION_FAILED


617


Tivoli Data Exchange encountered a problem initializing while attempting tosubmit a ping or request message to the manager. This condition correlates to afailure to create an FTF ID internally.


None.


Collect information from the logs and record any messages displayed on theconsole, then contact Technical Support (see page 10 for contact information).


None.


None.


None.



FTFRCE_SYNCQ_PROCESSING_FAILED


618


Tivoli Data Exchange encountered a problem attempting to process messages onthe sync queue.


None.


Make sure specified sync queue is not in use.


Make sure specified sync queue is defined.


None.


None.



FTFRCE_CONTROLQ_PROCESSING_FAILED


619


The Tivoli Data Exchange manager encountered an error processing a messagefrom the control queue.




Tivoli Data Exchange reports the MQSeries reason code from the GET call fromthe control queue as part of the secondary return code. Take corrective actionbased on this return code’s value if it is a Tivoli Data Exchange configurationproblem.


Based on the MQSeries reason code for the failure, you may have to correct theMQSeries configuration.


None.


None.



FTFRCE_MQBROWSE_FAILURE


620


The Tivoli Data Exchange manager encountered an error processing a messagefrom the sync queue.




Tivoli Data Exchange reports the MQSeries reason code from the GET call fromthe sync queue as part of the secondary return code. Take corrective actionbased on this return code’s value, if it is a Tivoli Data Exchange configurationproblem.




None.


None.



FTFRCE_UNKNOWN_MESSAGE_TYPE


621


Tivoli Data Exchange got a message from a queue that had an unknown messagetype.


Report the error message to Tivoli Data Exchange Administrator.


Collect the Tivoli Data Exchange logs, the Tivoli Data Exchange configurationfile, and contact Technical Support (see page 10 for contact information).


None.


None.


None.



FTFRCE_MQCMIT_FAILED


622


The Tivoli Data Exchange component in error is unable to issue an MQ commit.




Tivoli Data Exchange reports the MQSeries reason code from the commit call aspart of the secondary return code. Take corrective action based on this returncode’s value if it is a Tivoli Data Exchange configuration problem.


Based on the MQSeries reason code for the commit failure, you may have tocorrect the MQSeries configuration.


Consider cleaning up disk space.


See “Interpreting Error Codes” on page 12 for help in determining primary andsecondary return codes.



FTFRCE_REQUEST_PROCESSING_FAILED


623


Tivoli Data Exchange had a problem processing the request.




Tivoli Data Exchange reports the MQSeries reason code from the failure as partof the secondary return code. Take corrective action based on this return code’svalue if it is a Tivoli Data Exchange configuration problem.




None.





FTFRCE_INVALID_CONFIGURATION


625


The Tivoli Data Exchange Status GUI is unable to read the Tivoli DataExchange configuration file.


Verify that the configuration file exists and is readable. Also verifyFTF_CONFIG_FILE environment variable to see if it is set the correct value.


Verify that the configuration file exists and is readable. Also verifyFTF_CONFIG_FILE environment variable to see if it is set to the correct value.


None.


None.


None.



FTFRCE_CANCELLATION_FAILURE


626


A Tivoli Data Exchange cancel request failed.


None.


Verify that the ReceiverControlQueue and ReceiverSystemQueue are correctlydefined in the configuration file. The Tivoli Data Exchange log file contains thenode name of the Sender or Receiver involved.


None.


None.


None.



FTFRCE_SUBMIT_CANCEL_MESSAGE_FAILED


627


Cancel request message was not successfully submitted. If the cancel request isnot resubmitted in time, the file transfer may complete processing.


Verify that the cancel request input parameters are correct. Resubmit the request.


None.


Verify the Tivoli Data Exchange's queue depths on the receiver’s queuemanager.

• If the queues are full, a component in the system may have failed,preventing messages from being processed. Restart any failed components.

• If the queues are not full, contact Technical Support (see page 10 for contactinformation).


None.


If the cancel request is resubmitted and processed after the file transfer has beencompleted, the cancel request will be ignored by the system.



FTFRCE_SENDER_FAILURE


628


This message indicates a generic Tivoli Data Exchange Sender failure. TheTivoli Data Exchange Sender has reported a failure back to the Tivoli DataExchange manager.


Look in the Tivoli Data Exchange log file. Check the secondary error code formore detail.




None.


None.





FTFRCE_SUBMIT_REPLY_FAILURE


629


An attempt to reply to a component has failed.


Verify that the FTFIccQueue value is correctly defined in the configuration file.


Verify that the FTFIccQueue exists and is put and get enabled. Also check for aqueue full condition on the ICCQueue.


None.


None.


None.



FTFRCE_RECEIVER_FAILURE


630


This message indicates a generic Tivoli Data Exchange Receiver failure. TheTivoli Data Exchange Receiver has reported a failure to the Tivoli DataExchange Manager.






None.


None.


None.



FTFRCE_FILE_IS_A_DIRECTORY


631


The file Tivoli Data Exchange is attempting to read or write is a directory.


Correct the dpath or spath value in the transaction so that they point to a file andnot to a directory.


Check the Tivoli Data Exchange configuration file definitions for the source andtarget files. Verify that the spath and dpath values point to files rather thandirectories.


None.


None.


None.



FTFRCE_FILE_ALREADY_EXISTS


632


The specified target file already exists. Based on other values, Tivoli DataExchange can not overwrite the file.


A transfer was specified with the NOREPLACE option in the mode value.Either remove this value from your transaction or change the option to APPENDor REPLACE.


None.


None.


None.


None.



FTFRCE_UNABLE_TO_CREATE_DIRECTORY


633


Tivoli Data Exchange is unable to create the specified directory.


None.


None.


None.


Verify that the user of the Tivoli Data Exchange Receiver process haspermission to create the specified directory.


None.



FTFRCE_FILE_DOES_NOT_EXIST


634


The specified file does not exist in the path indicated by the spath and cfilearguments.


Verify that the file specified in the spath or cfile arguments exists. If it does not,change the file name to the name of a file that exists or add the file to theappropriate directory.


None.


None.


None.


None.



FTFRCE_INVALID_FILEHANDLE


635


The name of the file to be accessed is invalid. The file handle may havechanged, may be corrupt, the file or path may not exist, or the specified drivemay not exist or may not be connected.


Check accuracy of input parameters to the file transfer request. Verify that thefile name is accurate. Resubmit the request.


None.


None.


If the file transfer still fails, verify permissions on the file.


None.



FTFRCE_INVALID_FILEMODE


636


An invalid file mode has been specified in the transfer request. Valid file modesare OS dependent.


Verify that input parameters for file mode are correct. Resubmit the request.


None.


None.


If the request still fails, check the permissions on the file.


This error message most likely reflects a problem on the receiver side of thetransaction.



FTFRCE_FILE_OPEN_FAILURE


637


Tivoli Data Exchange is unable to open the source or target file for reading orwriting.


Verify that the files specified in the spath, dpath, and cfile values are correct.


None.


None.


Verify that the Tivoli Data Exchange Manager is able to read the specified files.


None.



FTFRCE_INVALID_FILENAME


638


The file name that was specified in the calling interface is invalid.


The file name that was specified does not conform to the requirements of thesource or target platform. Some platforms have restrictions on the number of andtype of characters that can appear in the file names. Correct the file name andresubmit the transaction.


None.


None.


None.


None.



FTFRCE_FILEWRITE_ERROR


639


Tivoli Data Exchange is unable to write data to the specified file.


Verify that the options are correctly specified for the target platform.


None.


None.


Verify for the following conditions on the target device:

• An out-of-space condition exists on the target drive.

• The target device is available.

• Insufficient permissions exist for writing the file.


None.



FTFRCE_DYNALLOC_FAILED


640


OS/390 is unable to allocate space for the target dataset. The error is specific tothe OS/390 platform.


Verify that the OS/390 options are correctly specified.


None.


None.


Verify an out-of-space condition on the target drive.


None.



FTFRCE_UNSUPPORTED_FILETYPE


641


The file selected for the target file is unsupported by Tivoli Data Exchange.


Verify that the recfmt argument has a correct value of:

• F, V, FB, or VB on OS/390.

• SAVE or SRCPF (source physical) on OS/400.


None.


None.


Verify that the correct file types are specified:

• OS/390 file is F, V, FB, or VB.

• OS/400 file is SAVE or SRCPF (source physical).


None.



FTFRCE_CONFIG_FILE_NOT_SPECIFIED


642


The Tivoli Data Exchange configuration file was not specified


Specify the path to the Tivoli Data Exchange configuration file in theconfiguration file value.


None.


None.


None


None.



FTFRCE_UNKNOWN_FTF_COMPONENT


643


An invalid component was passed to the FTF Shutdown API from the callinginterface.


Verify that your API call to FTFShutdown API is passing FTF_SENDER_CPT,FTF_RECEIVER_CPT, or FTF_MANAGER_CPT in the FTFShutdownInfodata structure. Also verify the FTF_Logger component.


None.


None.



None.



FTFRCE_INVALID_TIMEOUT_VALUE


644


This message appears only when the FTFEND API is used. The timeout valuethat has been specified in the FTFShutDownInfo structure is invalid. This valuecould have come from any calling interface.


Change the timeout value so that it is within the following valid ranges:

• Equal to or greater than zero.

• Equal to or less than 32767.


None.


None.


None.


None.



FTFRCE_UUID_CREATE_FAILURE


645


Tivoli Data Exchange was unable to create a unique FTFID for the file transfer.


Resubmit the file transfer request.


If resubmit fails, contact Technical Support (see page 10 for contactinformation).


None.


None.


None.



FTFRCE_MISSING_PARAMETER


646


This message occurs when the FTFShutdown API is called. The condition forthe message is either the input structure or the FTFShutDownReply structurehave a value of null.


None.


If you are calling these data structures from a C program, verify that theFTFShutdownInfo and the FTFShutdownReply are valid structures and check tosee that the value is not null. If there are still problems, contact TechnicalSupport (see page 10 for contact information).


None.


None.


None.



FTFRCE_REPLY_PROCESSING_FAILED


647


During execution of the FTFShutdown API, replies from each of thecomponents were not received to signal correct shut down.


This message comes from the FTFShutDown API.

• Verify that the FTF ICC queue is GET enabled.

• See if enough time has been allocated for all of the components toshutdown.

• If the problem continues, look for an MQSeries return code either onthe console or in the Tivoli Data Exchange log file and use this code tohelp in solving the problem.

Otherwise, contact Technical Support (see page 10 for contact information).


If an MQSeries return code is provided, this code may help in solving theproblem. Otherwise, contact Technical Support (see page 10 for contactinformation).








See “Interpreting Error Codes” on page 12 to help with determining primary andsecondary codes.



FTFRCE_REPLY_TIMED_OUT


648


Indicates that the calling interface has timed out while waiting for a response.The time-out condition can be due to a low time-out value or by components ofthe system not being available and ready to process files.


Increase the time to wait for a response. Verify that all components are availableand are ready to transfer files.


Verify that Tivoli Data Exchange components are functioning correctly.


Verify that MQSeries components are functioning correctly.


Verify that the network is available.


None.



FTFRCE_FILE_READ_FAILURE


649


The specified file could not be read. This error may occur if an invalid file nameis given, if there are security violations, or if there is a sharing violation with thefile.


Check the logs to see which file caused the error. Verify that the file name iscorrect in the calling interface and that proper security access is in place.


Verify that proper security access is in place.


Verify that proper security access is in place.


Verify that proper security access exists and that another process does not havethe file locked.


None.



FTFRCE_INVALID_ARGUMENT


650


The data structures being passed to Tivoli Data Exchange from a callingprogram are not valid.


Verify the FTFRequestMsgInfo data structure is used in the FTFReq API calland the FTFStageMsgInfo data structure used in the FTFStage API call. Be surethat all values are valid in the data structures. If the problem continues, thecontact Technical Support (see page 10 for contact information).


Contact Technical Support (see page 10 for contact information).






None.



FTFRCE_INVALID_ICCQUEUE


651


Indicates that the system cannot access the ICCQueue.


Contact MQSeries administrator.


Contact MQSeries administrator.


Check to see whether the ICCQUEUE that is specified in the configuration file’sFTFICCQueue property is correctly specified. Additionally, verify to see if theICCQueue exists and that it is get and put enabled.


None.


None.



FTFRCE_SOURCE_PREPROC_FAILED


652


Tivoli Data Exchange Sender failed to execute its pre-process exit.


Verify that the exit arguments passed to Tivoli Data Exchange’s FTFReq APIare correct. The values could be coming from a program or another callinginterface.


Verify that the exit dll files reside in the FTF_EXIT_PATH directory.


None.


None.


None.



FTFRCE_INVALID_EXITNAME


653


The specified exit name entered through a calling interface is an invalid exitname.


Verify that the exit arguments supplied to the calling interface are correct.


Verify that the exit DLL files reside in the FTF_EXIT_PATH directory.


None.


None.


None.



FTFRCE_INVALID_ENTRYPOINT


654


The entry point passed as exitentry value does not exist in the load libraryspecified.


Verify that the exit DLL file exists in the specified load library. Also, verify thatthe entry point exists in the load library specified with exit dll. The exit entrypoint name is case sensitive.


Verify that the proper version of the shared library is installed.


None.


None.


None.



FTFRCE_EXITLOAD_FAILED


655


Tivoli Data Exchange is unable to load the exit DLL from the specified library,possibly because of a sharing violation.






None.


None.


None.



FTFRCE_EXITUNLOAD_FAILED


656


Tivoli Data Exchange is unable to unload the exit DLL from the specifiedlibrary, possibly because of a sharing violation.






None.


None.


None.



FTFRCE_EXIT_NO_PATH_SPECIFIED


658


Tivoli Data Exchange could not locate the directory where the exit DLL filesreside.


None.


Verify that the environment variable FTF_EXIT_PATH is set and that thedirectory specified contains the exit DLL files.


None.


None.


None.



FTFRCE_EXIT_PATH_TOO_BIG


659


The specified path for the exit (FTF_EXIT_PATH plus the exit library name)exceeds maximum path specified in the FTF_MAX_PATH parameter. Theestablished value is 256 characters.


Specify a path that has fewer than 256 characters.


None.


None.


None.


None.



FTFRCE_EXIT_FAILURE


660


The specified exit reported an error while executing the exit module.


The reason for the failure is provided as the secondary return code. Perform theappropriate actions based on its value.


None.


None.


None.


None.



FTFRCE_DYNFREE_FAILED


662


A FREE was attempted and failed on the OS/390 platform.










None.



FTFRCE_RECORD_TOOBIG


663


The size of the record being written to a file on the OS/390 platform is largerthan the what has been specified in the lrecl argument.


Change the lrecl argument size or decrease the sending record size and retry thedata transfer.





None.



FTFRCE_SOURCE_POSTPROC_FAILED


665


The Tivoli Data Exchange Sender was unable to process the post-process exitthat was specified.


This condition generally occurs when the Tivoli Data Exchange Sender isperforming an error recovery action after a hard crash and cannot find apost-process completion marker, which indicates a successful execution of thepost-process exit. The transaction ends with an error. Verify that the values in thefields are correct. Reissue the request by specifying a correct post-process exit.


None.


None.


None.


None.



FTFRCE_MANAGER_FAILURE


667


The queue manager failed during file transfer.


Look for a secondary error code for more specific information regarding thefailure. Check inputs to file transfer request and resubmit.


Look into queue manager log for additional information regarding the failure.


None.


None.


This code is generic and should be accompanied by a secondary error messagewith more specific information.



FTFRCE_LOG_FILE_OPEN_FAILURE


668


A Tivoli Data Exchange process was unable to open its log file. Possible causesinclude a corrupt log file, changes in system permissions, or disconnected ornonexistent drive.


None.


Verify accuracy of path and log file name parameters. Restart the component.


None.


Check the specified log file and verify its path and permissions. Restart thecomponent. If the error persists, contact Technical Support (see page 10 forcontact information).


None.



FTFRCE_INVALID_RECORDLENGTH


669


The lrecl value contains a value of zero or less than zero for an OS/390 target.


Correct the record length specification by using a GUI, ISPF, or 5250 interfaceand reissue the request.


None.


None.


None.


None.



FTFRCE_INVALID_BLKSIZE


670


The blksize argument specified in the transaction for an OS/390 target file isinvalid. There are many conditions under which this error message is issued.The conditions may be:

• The blocksize specified is less than zero.• The target file is formatted as fixed and the block size does not equal the

record length.• The target file is formatted as either fixed block or variable block and the

block is not a multiple of the record length.• The target file is formatted as a variable file and the record length is not at

least four bytes less than the block size.


Correct the block size and reissue the request.


None.


None.


None.


None.



FTFRCE_INVALID_UNITNAME


671


The unit argument was not specified as part of the transaction with an OS/390target.


The unit name was not specified in the calling interface and no default value wasspecified in the configuration file at either the sending node or the receivingnode. Specify a valid unit name in any of the supported components or specifythe unit name in the configuration file.

Tivoli Data Exchange does not verify whether the specified unit name is definedto the system until a dynamic allocation request is issued. Verify the valid unitnames with your system administrator.


None.


None.


None.


None.



FTFRCE_INVALID_ALCUNIT


672


The specified alcunit argument is invalid. Tivoli Data Exchange supportsallocation unit types of CYL (cylinder), BLK (block), and TRK (track).


Specify a valid value for the allocation unit and reissue the request. You canspecify the allocation unit in the interface or the Tivoli Data Exchangeconfiguration file.


None.


None.


None.


None.



FTFRCE_INVALID_FILEORG


673


The organization value contains an invalid dataset organization for the targetnode on an OS/390 platform. Tivoli Data Exchange supports the following dataset organizations: PS (physical sequential) and PDS (partitioned dataset).



Tivoli Data Exchange Tivoli Data Exchange Tivoli Data Exchange Tivoli Data Exchange Administrator ActionsAdministrator ActionsAdministrator ActionsAdministrator Actions

None.


None.


None.


None.



FTFRCE_INVALID_RECORDFORMAT


674


An invalid record format was specified for the OS/390 target. The supportedrecord formats are Fixed, Fixed Block, Variable and Variable Block.




None.


None.


None.


None.



FTFRCE_MGRPRE_EXIT_FAILURE


675


The Tivoli Data Exchange Manager failed while executing the pre-process exit.


Verify that the supplied exit arguments are correct.


Verify that the exit DLLs reside in the FTF_EXIT_PATH.


None.


None.


None.



FTFRCE_MGRPOST_EXIT_FAILURE


676


The Tivoli Data Exchange Manager component failed while executing thepost-process exit.


Verify that the supplied exit arguments are correct.


Verify the exit DLLs reside in the FTF_EXIT_PATH.


None.


None.


None.



FTFRCE_SDRPRE_EXIT_FAILURE


677


The Tivoli Data Exchange Sender failed while executing the pre-process exit.


Verify that the supplied exit arguments are correct. Retrieve the transaction’sstatus from the logs and relay the information to the Tivoli Data Exchangeadministrator.


Verify the following:

• The exit DLLs reside in the FTF_EXIT_PATH.

• The exit argument supplied are correct.


None.


None.


None.



FTFRCE_SDRPOST_EXIT_FAILURE


678


The Tivoli Data Exchange Sender failed while executing the post-process exit.








None.


None.


None.



FTFRCE_RCVPRE_EXIT_FAILURE


679


The Tivoli Data Exchange Receiver failed while executing the pre-process exit.








None.


None.


None.



FTFRCE_RCVPOST_EXIT_FAILURE


680


The Tivoli Data Exchange Receiver failed while executing the post-process exit.


Verify that the supplied exit arguments are correct. Retrieve the transaction’sstatus of the and relay the information to the Tivoli Data Exchangeadministrator.






None.


None.


None.



FTFRCE_SDRAUTH_EXIT_FAILURE


681


The userID on the Tivoli Data Exchange sender that is requesting the transactiondoes not have the authority to execute the exit.


Verify that the exit arguments are correct.


None.


None.


Verify that the Tivoli Data Exchange userID had authority to execute thespecified exit.


None.



FTFRCE_RCVAUTH_EXIT_FAILURE


682


The userID on the Tivoli Data Exchange receiver that is requesting thetransaction does not have the authority to execute the exit.


Verify that the exit arguments are correct.


None.


None.


Verify that the Tivoli Data Exchange userID had authority to execute thespecified exit.


None.



FTFRCE_RECEIVE_IMMED_TIMEOUT


683


The receiver failed to receive immediate “heartbeat” message from the sender.Error may be caused by heavy network traffic, or component or channel failure.The file transfer fails.


Resubmit the request.


Check that the sender component involved in the transfer is running.


Verify that the channels between the sender and receiver machines are running.


None.


On an immediate transfer, the sender and receiver periodically exchangemessages to confirm that the other component is running and preserve theintegrity of the synchronous data transfer. If either component doesn’t hear backfrom the other in time, an error message is generated.



FTFRCE_SEND_IMMED_TIMEOUT


684


The sender failed to receive immediate “heartbeat” reply from the receiver. Errormay be caused by heavy network traffic, or component or channel failure. Thefile transfer fails.


Resubmit the request.


Check that the receiver component involved in the transfer is running.


Verify that the channels between the sender and receiver machines are running.


None.


On an immediate transfer, the sender and receiver periodically exchangemessages to confirm that the other component is running and preserve theintegrity of the synchronous data transfer. If either component doesn’t hear backfrom the other in time, an error message is generated.



FTFRCE_RECEIVE_IMMED_RECOVERY


685


This message gets reported if the receiver started processing an immediatetransfer and went down before the transfer was completed. When the receivercomes back up it recovers the transfer and this error is reported.

Tivoli Data Exchange User Actions User Actions User Actions User Actions

None.


None.


None.


None.


None.



FTFRCE_COMPRESSION_NOT_SUPPORTED

Numeric Valu6Numeric Valu6Numeric Valu6Numeric Valu6

686


This message gets reported when you attempt to run compression on the 4690platform..


Correct the command by removing the compression argument and resubmit.


None.


None.


None.


None.



FTFRCE_INVALID_CONFIG_STANZA_VALUE


701


The specified stanza in the Tivoli Data Exchange configuration file contains aninvalid value.


None.


Verify the logs for the stanza that contains the invalid value. Verify that allconfiguration file stanzas have correct values.


None.


None.


None.



FTFRCE_MISSING_CONFIG_STANZA


702


A required stanza in the Tivoli Data Exchange configuration file is missing.


None.


Add the stanza and value to the configuration file. The required stanza isdisplayed as part of the message. Verify the format of the example provided inthe Tivoli Data Exchange configuration file, located in the Tivoli Data Exchangeroot directory.


None.


None.


None.



FTFRCE_NO_AVAILABLE_SYNC_QUEUE


706


The component, that issued this error message, is unable to find a SYNC queueon which to operate. Each of the Tivoli Data Exchange components (Manager,Sender and Receiver) requires an MQSeries message queue designated for useas a SYNC queue. Each instance of the component uses this queue on anexclusive basis. See Tivoli Data Exchange User’s Guide, “FTFRCV” or“FTFSDR” on how Tivoli Data Exchange resolves the SYNC queue names.



• Check the secondary return code and report any MQSeries specificerrors to the MQSeries administrator.

• The configuration file for the correct specification of the SYNC queuenames and the number of instances specified.

• Ensure that another instance of the component is not already running


Define the necessary objects and cross-check the queue names with theMQSeries object definitions


Verify that all MQSeries objects are defined.


None.


None.



FTFRCE_ERROR_CHECKING_DATA


708


Tivoli Data Exchange was unable to retrieve status data.


Resubmit the status request.


None.


Verify the Tivoli Data Exchange's queue depths on the status queue.

• If the queue is full, a component in the system may have failed, preventingmessages from being processed. Restart any failed components.

• If the queue is not full, contact Technical Support (see page 10 for contactinformation).


None.


The status API may return this message if it cannot find the data or if the queuesare full.



FTFRCE_UNABLE_TO_PROCESS_STAGE_ITEM


711


Tivoli Data Exchange was unable to successfully process the staged item. Thiserror can occur during sending, purging, or querying.


Verify that the argument values supplied to the Tivoli Data Exchange commandare correct. Verify that the associated file has been staged.


None.


Verify that the stage queues have the correct settings. Verify that these queuesare get and put enabled.


None.


None.



FTFRCE_FILE_ERROR


712


Tivoli Data Exchange failed to open or close a file. Look for secondary errorcode for more explicit information.


Verify that input parameters of request are valid. Resubmit the request.


None.


None.


Verify the permissions and existence of the file.


Possible causes include permissions, access conflicts, and invalid parameters(file by name specified does not exist, path is not valid). This code is generic andgenerally is accompanied by a secondary error code such asFTFRCE_INVALID_FILEHANDLE or FTFRCE_INVALID_FILEMODE.



FTFRCE_MISSING_CONFIG_SECTION


713


A required section in the Tivoli Data Exchange configuration file is missing.


None.


The required section is displayed as part of the message. Provide the section andvalue in the configuration file. Verify the format of the example provided in theTivoli Data Exchange configuration file.


None.


None.


None.



FTFRCE_UNABLE_TO_PROCESS_REQUEST


714


A general transmission failure has occurred and Tivoli Data Exchange wasunable to successfully complete the transaction.


None.


Verify that all Tivoli Data Exchange components are running. Verify the logsfor further information about components and other errors.


Verify that the MQSeries queue managers are running and configured correctly.


Verify that the proper permissions are correct for the transaction.


None.



FTFRCE_INVALID_QUEUE_MANAGER_NAME


715


Tivoli Data Exchange was unable to validate the supplied queue manager.


Verify the queue manager names supplied in the transaction.


Verify existence of any queue manager overrides in the Tivoli Data Exchangeconfiguration file.


None.


None.


None.



FTFRCE_INVALID_RESEND_REQUEST


716


The block size is less that zero in the resend request sent to the Tivoli DataExchange Sender from the Tivoli Data Exchange Receiver. Negative block sizesare invalid.


None.


Verify the logs for more information. Call Technical Support (see page 10 forcontact information).


None.


None.


None.



FTFRCE_FATAL_ERROR


717


Tivoli Data Exchange encountered a condition that prevents it from continuingto process. Other error codes signal specific conditions where values aremissing. This error indicates a general error that was not trapped by the morespecific errors. Tivoli Data Exchange will shut down when this error occurs.


None.


Attempt to stop the remaining Tivoli Data Exchange components and restartthem. Call Technical Support (see page 10 for contact information).


Verify the statuses of the MQSeries queue managers.


None.


None.



FTFRCE_INTERNAL_ERROR


718


Internal Tivoli Data Exchange processing has failed. Other error codes signalspecific conditions where values are missing. This error indicates a general errorthat was not trapped by the more specific errors. Tivoli Data Exchange willremain running even through this error is encountered.


None.


Attempt to stop the remaining Tivoli Data Exchange components and restartthem. Call Technical Support (see page 10 for contact information).


Verify the statuses of the MQSeries queue managers and the associated TivoliData Exchange queues. Verify for queue full conditions.


None.


None.



FTFRCE_NO_STAGE_QUEUES_DEFINED


719


Tivoli Data Exchange was unable to access the stage queues.


None.


Verify that the Tivoli Data Exchange configuration file is correct for theMQSeries configuration being used. Verify that the stage queue or stage pool isdefined.


Verify that the default Tivoli Data Exchange queues were created and verify thatany override Tivoli Data Exchange queues were created. If override queues havenot been created, create the queues and restart Tivoli Data Exchange.


None.


None.



FTFRCE_SECURITY_ERROR


720


Tivoli Data Exchange was unable to validate the user that issued the request.


Verify that you have permissions to access the MQSeries objects.


None.


Verify that the userID issuing the request has permissions to access theMQSeries objects.


None.


None.



FTFRCE_UNABLE_TO_RETRIEVE_USERID


722


Tivoli Data Exchange is unable to retrieve the userID that issued the request.


None.


Call Technical Support (see page 10 for contact information).


None.


None.


None.



FTFRCE_SOURCE_FILENAME_NOT_SPECIFIED


723


No path to the source file was specified for the Tivoli Data Exchangetransaction.


Verify that the source path was supplied for the Tivoli Data Exchange request. Ifyou call the API directly, verify that you are supplying the source fileinformation in the FTFRequestMsgInfo data structure. If you are working withan interface, enter a source file name.


None.


None.


None.


None.



FTFRCE_DEST_FILENAME_NOT_SPECIFIED


724


No path to the destination file was specified for the Tivoli Data Exchangerequest.


Verify that the destination path and file name is supplied for the Tivoli DataExchange transaction. If you call the API directly, verify that you are supplyingthe source file information in the FTFRequestMsgInfo data structure. If you areworking with an interface, enter a destination path and file name.


None.


None.


None.


None.



FTFRCE_SOURCE_QMGR_NOT_SPECIFIED


725


No source queue manager was specified for the Tivoli Data Exchange request.This error can occur when staged items are purged or queried.


Verify that the source queue manager was supplied for the Tivoli Data Exchangetransaction. If you are calling the API directly, the source queue managerinformation is supplied to the FTFRequestMsgInfo data structure. If you areusing an interface, supply the source queue manager.


None.


None.


None.


None.



FTFRCE_DEST_QMGR_NOT_SPECIFIED


726


No destination queue manager was specified for the Tivoli Data Exchangerequest.


Verify that the destination queue manager was supplied for the Tivoli DataExchange request and, if you are calling the API directly, be sure the targetqueue manager information is supplied in the FTFRequestMsgIno data structure.If you are using an interface, supply the destination queue manager.


None.


None.


None.


None.



FTFRCE_INVALID_DATA_POOL


727


Tivoli Data Exchange is unable to find the data pool associated with thetransaction.


If you are not using the default pool, verify that the correct pool is beingspecified during the request.


Verify that the Tivoli Data Exchange configuration file has the correct pooldefinitions.


Verify that the queues associated with the pools have been created.


None.


None.



FTFRCE_UNABLE_TO_RETRIEVE_SECURITY_CONTEXT


728


Tivoli Data Exchange failed to retrieve the context for the user that issued theTivoli Data Exchange request.


None.




None.


None.


None.



FTFRCE_AS400_FILE_DIFFERS_FROM_SPECIFIED


729


AS/400 only. The AS400FT (AS400 File Type) specified is different from theexisting target file’s type. The AS400FT is specified in the configuration fileand can be overridden by supplying the AS400FT argument in your interface.


Verify that the target file matches the AS400FT argument specified. Correct thevalue of the argument and reissue the command.


None.


None.


None.


None.



FTFRCE_AS400_INVALID_RCDLEN


730


AS/400 only. The rcdlen (record length) of an existing file is smaller than thercdlen specified. The rcdlen defaults to 92 for Source Physical Files.


Verify that a value of the redlen argument is greater than or equal to the redlenof the existing target file.


None.


None.


None.


None.



FTFRCE_AS400_ERROR_CREATING_LIBRARY


731


AS/400 only. An error occurred while Tivoli Data Exchange was trying todynamically allocate a new AS/400 library.


Verify that a valid library name has been specified. Be sure that the propersecurity access is enabled for the library.


Verify that proper security access is enabled for the library.


None.


Verify that there is sufficient disk space to allocate the library.


None.



FTFRCE_AS400_CRTLIB_NOT_SPECIFIED


732


AS/400 only. The specified library does not exist and the crtlib (create library)argument was not used in your calling interface. In order to have the systemdynamically allocate a library if it does not exist, you must specify the crtlibargument.


Specify the crtlib argument to dynamically allocate a new library and reissue thecommand. Valid values are YES or NO.


None.


None.


None.


None.



FTFRCE_AS400_ERROR_CREATING_SRCPF


733


AS/400 only. An error occurred while Tivoli Data Exchange was trying todynamically allocate a Source Physical File (SRCPF). This error may occurunder the following conditions:

• An invalid file name is given.• There are security violations.• There is not enough disk space.• There is a sharing violation with the file.



• Proper security access is enabled.• A valid file name was specified.• There is enough disk space available.


Verify that proper security access is enabled.


None



• Another process does not have the file locked.• Another process is trying to allocate the file.• There is sufficient disk space available.


None.



FTFRCE_AS400_NOREPLACE_SPECIFIED


734


AS/400 only. The target file’s specified mode was NOREPLACE and the filealready exists.


Use a mode of REPLACE or APPEND to overwrite or append to the target file.


None.


None.


None.


None.



FTFRCE_AS400_ERROR_CREATING_SAVEF


735


AS/400 only. An error occurred while Tivoli Data Exchange was trying todynamically allocate a Save file. This error occurs in the following instances:

• An invalid file name is given.• There are security violations.• There is not enough disk space.• There is a sharing violation with the file.


Verify whether the proper security access is enabled.


Verify whether the proper security access is enabled on the specified file.


None.


Verify the following conditions:• Another process does not have the file locked and a process trying to be

allocated using the file.• There is sufficient disk space available.


None.



FTFRCE_AS400_ERROR_CLEARING_SAVEF


736


AS/400 only. An attempt was made to clear an existing SAVE file. A SAVEfile must be cleared before any data can be written to it.


Verify whether the proper security access is enabled to the specified file.








None.



FTFRCE_NON_PERSIST_STAGE_DATA_NOT_FOUND


737


None.


None.


None.


None.


None.


None.



FTFRCE_INVALID_DIRBLOCKS


739


OS/390 Only. A specified value for directory blocks is not valid. This erroroccurs under the following conditions:

• The target dataset specified is a PDS member.• The PDS did not exist and Tivoli Data Exchange tried to dynamically

allocate the target dataset.• A negative directory block value was specified.


Specify a valid value for the number of directory blocks and reissue the request.You can specify a valid value either through the command arguments or throughthe configuration file.


None.


None.


None.


None.



FTFRCE_INVALID_MODEL_DATASET


740


OS/390 Only. An invalid dataset name in the model dataset for the GenerationData Group (GDG) allocation has been specified.


Correct the dataset model specification and resubmit the transaction.


None.


None.


None.


None.



FTFRCE_FILE_CLOSE_FAILURE


741


Tivoli Data Exchange failed to close the file on either the sender or receiverside. The transaction fails.


Verify that the request input parameters are correct. Resubmit the request.


None.


None.


Verify the permissions and existence of the file.


None.



FTFRCE_CONFIG_FILE_NOT_FOUND


742


None.


None.


None.


None.


None.


None.



FTFRCE_INVALID_FTFCFG_QUEUE


743


None.


None.


None.


None.


None.


None.



FTFRCE_TIME_SLICING_FAILED


744


OS/390 Only. An invalid dataset name in the model dataset for the GenerationData Group (GDG) allocation has been specified.


Correct the dataset model specification and resubmit the transaction.


None.


None.


None.


None.



FTFRCE_INVALID_IMMED_STAGEONLY_COMBINATION


745


The use of the immediate and stageonly arguments in a command is not one thatcan be executed. The immediate argument calls for and an instant synchronousdata transfer between the Sender and Receiver. The stageonly argument transfersdata to the staging area. The two commands are in conflict.


Split the command into two operations if both arguments need to be executed.Otherwise remove one of the arguments from the command and resubmit.


None.


None.


None.


None.



FTFRCE_INVALID_QMGR_LENGTH


746


The queue manager specified cannot be more than the length allowed byMQSeries for the queue manager name.


Correct the length of the queue manager name and reissue the command.


None.


None.


None.


None.



FTFRCE_QUERY_STAGE_FAILED


750


Tivoli Data Exchange failed to retrieve the staged items.


Verify that the source queue manager name is correct and reissue the command.


Verify that Tivoli Data Exchange components are running and that the userIDhas permissions to the MQSeries objects.


Verify that GET is enabled on the stage queues.


None.


None.



FTFRCE_DLL_LOAD_FAILED


760


Tivoli Data ExchangeTivoli Data ExchangeTivoli Data ExchangeTivoli Data Exchange failed to retrieve the staged items.


Verify that the source queue manager name is correct and reissue the command.


Verify that Tivoli Data Exchange components are running and that the userIDhas permissions to the MQSeries objects.


Verify that GET is enabled on the stage queues.


None.


None.



FTFRCE_DBCS_PROCESSING_FAILED


761


The DBCS argument has been specified as a command-line option and theTivoli Data Exchange Sender could not process the input file correctly.


When DBCS is specified, writing records to the output file is handled differentlythat in a normal Tivoli Data Exchange data transfer. Verify that the msgsizeargument contains a number large enough to contain the largest record. Changethe arguments and reissue the command.


None


None


None.


None.



FTFRCE_COMPRESS_FAILURE


801


An error detected during execution of the compression exit.


Verify that the compression DLL exit is located in the path.


Verify that the directory is specified in the FTF_EXIT_PATH environmentvariable.


None.


None.


None.



FTFRCE_DECOMPRESS_FAILURE


802


An error was detected during the execution of the decompression exit.


Verify that the decompression DLL exit is located in the path.


Verify that the directory is specified in the FTF_EXIT_PATH environmentvariable.


None.


None.


None.



FTFRCE_BUFFERTOOSMALL


803


Buffer used in decompression of data messages is too small.


Either:

• Resubmit the request without using file compression.

• Increase the message size parameter in the transfer request andresubmit the request (with compression).




None.


None.


Tivoli Data Exchange should detect that the buffer size is too small andautomatically reallocate sufficient space rather than fail the transaction.



FTFRCE_INVALID_INPUT


804


An invalid argument was detected in the specified interface.


Correct the arguments values and resubmit the command to the interface.


None.


None.


None.


None.



FTFRCE_MAX_MSG_SIZE_EXCEEDED


805






None.


None.


None.


None.



FTFRCE_CONNECTOR_SEND_FAILURE


806






None.


None.


None.


None.



FTFRCE_CONNECTOR_RECEIVE_FAILURE


807






None.


None.


None.


None.



FTFRCE_CONNECTOR_CONNECTOR_REQUIRED


808


This is a TPF-specific message designating that a connector is required for thetransfer.


None.


None.


None.


None.


None.



FTFRCE_UNKNOWN_CONNECTOR_FILETYPE


809


When running the portal, a file type, not expected was encountered.


Verify that the correct file type has been specified.


None.


None.


None.


None.



FTFRCE_XML_CONVERSION_FAILURE


810


There is a error in converting the data to XML.


Check the format of the data.


None.


None.


None.


None.



FTFRCE_XML_PROCESSING ERROR


811


There is an error processing the XML data.


Check the format of the data.


None.


None.


None.


None.



FTFRCE_BATCHCOUNT_EXCEEDED


812


The internal buffer pointers have moved past the end of the allocated bufferarray. The FTFSTATD component terminates.


Check for memory leaks in other applications or, if you have implemented acustom exit, check to see if it impinged on FTFSTATD’s memory space. Restartthe STATD component.


None.


None.


None.


None.



FTFRCE_DATABASE_CONNECTION_ERROR


813


There is an ODBC connection failure when initializing the databaseenvironment prior to message offloading. The FTFSTATD componentterminates.


Check the database connection setup and restart the STATD component.


None.


None.


None.


None.


IndexIndexIndexIndex

AAAA

AS/400 errors 78, 142, 143, 144, 145, 146,147, 148, 149

authorization errors 115, 116

CCCC

cancel message errors 64configuration file errors 50, 54, 62, 79, 121,

122, 127control message errors 52, 82conventions 9

DDDD

Dynalloc errors 77, 98

EEEE

error codesadditional error messages 17

interpreting 12where to find 12

error numberserror number 001 19error number 002 20error number 003 21error number 004 22error number 005 23error number 006 24error number 007 25error number 008 26error number 009 27error number 010 28error number 011 29error number 012 30error number 300 32error number 301 33error number 302 34error number 303 35error number 304 36error number 600 42error number 601 43error number 602 44error number 603 45error number 604 46error number 605 47error number 606 48


E

error number 607 49error number 608 50error number 609 51error number 611 52error number 613 53error number 614 54error number 617 55error number 618 56error number 619 57error number 620 58error number 621 59error number 622 60error number 623 61error number 625 62error number 626 63error number 627 64error number 628 65error number 629 66error number 630 67error number 631 68error number 632 69error number 633 70error number 634 71error number 635 72error number 636 73error number 637 74error number 638 75error number 639 76error number 640 77error number 641 78error number 642 79error number 643 80error number 644 81error number 645 82error number 646 83error number 647 84error number 648 86error number 649 87error number 650 88error number 651 89error number 652 90error number 653 91error number 654 92

error number 655 93error number 656 94error number 658 95error number 659 96error number 660 97error number 662 98error number 663 99error number 665 100error number 667 101error number 668 102error number 669 103error number 670 104error number 671 105error number 672 106error number 673 107error number 674 108error number 675 109error number 676 110error number 677 111error number 678 112error number 679 113error number 680 114error number 681 115error number 682 116error number 683 117error number 684 118error number 685 119error number 686 120error number 701 121error number 702 122error number 706 123error number 708 124error number 711 125error number 712 126error number 713 127error number 714 128error number 715 129error number 716 130error number 717 131error number 718 132error number 719 133error number 720 134error number 722 135


F

error number 723 136error number 724 137error number 725 138error number 726 139error number 727 140error number 728 141error number 729 142error number 730 143error number 731 144error number 732 145error number 733 146error number 734 147error number 735 148error number 736 149error number 737 150error number 739 151error number 740 152error number 741 153error number 742 154error number 743 155error number 745 157error number 750 159error number 760 160error number 761 161error number 801 162error number 802 163error number 803 164error number 804 165error number 805 166error number 806 167error number 807 168error number 808 169error number 809 170error number 810 171error number 812 173error number 813 174

exit errors 90, 91, 92, 93, 94, 95, 96, 97, 100,109, 110, 111, 112, 113, 114, 115,

116, 162, 163

FFFF

file access errors 72, 73, 102, 126, 153, 164file transfer cancel request error 64file-record errors 68, 69, 71, 74, 75, 76, 78,

87, 103, 136, 137FTFRCE_AS400_CRTLIB_NOT_SPECIFIED

145FTFRCE_AS400_ERROR_CLEARING_SAVE

F 149FTFRCE_AS400_ERROR_CREATING_LIBR

ARY 144FTFRCE_AS400_ERROR_CREATING_SAVE

F 148FTFRCE_AS400_ERROR_CREATING_SRCP

F 146FTFRCE_AS400_FILE_DIFFERS_FROM_SPE

CIFIED 142FTFRCE_AS400_INVALID_RCDLEN 143FTFRCE_AS400_NOREPLACE_SPECIFIED

147FTFRCE_BATCHCOUNT_EXCEEDED 173FTFRCE_BUFFERTOOSMALL 164FTFRCE_CANCELLATION_FAILURE 63FTFRCE_COMMAND_LINE_PROCESSING_

FAILED 53FTFRCE_COMPRESS_FAILURE 162FTFRCE_COMPRESSION_NOT_SUPPORTE

D 120FTFRCE_CONFIG_FILE_NOT_FOUND 154FTFRCE_CONFIG_FILE_NOT_SPECIFIED

79FTFRCE_CONFIG_FILE_PROCESSING_FAI

LED 54FTFRCE_CONFIGFILE_ACCESS_FAILURE

50FTFRCE_CONNECOR_CONNECTOR_REQU

IRED 169FTFRCE_CONNECTOR_RECEIVE_FAILURE

168FTFRCE_CONNECTOR_SEND_FAILURE

167


F

FTFRCE_CONTROL_MSG_NOT_FOUND 52FTFRCE_CONTROLQ_PROCESSING_FAILE

D 57FTFRCE_DATABASE_CONNECTION_ERRO

R 174FTFRCE_DBCS_PROCESSING_FAILED 161FTFRCE_DECOMPRESS_FAILURE 163FTFRCE_DEST_FILENAME_NOT_SPECIFIE

D 137FTFRCE_DEST_QMGR_NOT_SPECIFIED

139FTFRCE_DLL_LOAD_FAILED 160FTFRCE_DYNALLOC_FAILED 77FTFRCE_DYNFREE_FAILED 98FTFRCE_ERROR_CHECKING_DATA 124FTFRCE_EXIT_FAILURE 97FTFRCE_EXIT_NO_PATH_SPECIFIED 95FTFRCE_EXIT_PATH_TOO_BIG 96FTFRCE_EXITLOAD_FAILED 93FTFRCE_EXITUNLOAD_FAILED 94FTFRCE_FATAL_ERROR 131FTFRCE_FILE_ALREADY_EXISTS 69FTFRCE_FILE_CLOSE_FAILURE 153FTFRCE_FILE_DOES_NOT_EXIST 71FTFRCE_FILE_ERROR 126FTFRCE_FILE_IS_A_DIRECTORY 68FTFRCE_FILE_OPEN_FAILURE 74FTFRCE_FILE_READ_FAILURE 87FTFRCE_FILEWRITE_ERROR 76FTFRCE_FTF_INITIALIZATION_FAILED 55FTFRCE_INPUT_REQUIRED 48FTFRCE_INTERNAL_ERROR 132FTFRCE_INVALID_ALCUNIT 106FTFRCE_INVALID_ARGUMENT 88FTFRCE_INVALID_BLKSIZE 104FTFRCE_INVALID_CONFIG_STANZA_VAL

UE 121FTFRCE_INVALID_CONFIGURATION 62FTFRCE_INVALID_DATA_POOL 140FTFRCE_INVALID_DIRBLOCKS 151FTFRCE_INVALID_ENTRYPOINT 92FTFRCE_INVALID_EXITNAME 91FTFRCE_INVALID_FILEHANDLE 72

FTFRCE_INVALID_FILEMODE 73FTFRCE_INVALID_FILENAME 75FTFRCE_INVALID_FILEORG 107FTFRCE_INVALID_FTFCFG_QUEUE 155FTFRCE_INVALID_ICCQUEUE 89FTFRCE_INVALID_IMMED_STAGEONLY_

COMBINATION 157FTFRCE_INVALID_INPUT 165FTFRCE_INVALID_MODEL_DATASET 152FTFRCE_INVALID_OPTION 49FTFRCE_INVALID_QUEUE_MANAGER_NA

ME 129FTFRCE_INVALID_RECORDFORMAT 108FTFRCE_INVALID_RECORDLENGTH 103FTFRCE_INVALID_RESEND_REQUEST 130FTFRCE_INVALID_TIMEOUT_VALUE 81FTFRCE_INVALID_UNITNAME 105FTFRCE_LOG_FILE_OPEN_FAILURE 102FTFRCE_MANAGER_FAILURE 101FTFRCE_MAX_MSG_SIZE_EXCEEDED 166FTFRCE_MEMORY_ALLOCATION_FAILUR

E 42FTFRCE_MGRPOST_EXIT_FAILURE 110FTFRCE_MGRPRE_EXIT_FAILURE 109FTFRCE_MISSING_CONFIG_SECTION 127FTFRCE_MISSING_CONFIG_STANZA 122FTFRCE_MISSING_PARAMETER 83FTFRCE_MQBROWSE_FAILURE 58FTFRCE_MQCMIT_FAILED 60FTFRCE_MQCMIT_FAILURE 47FTFRCE_MQCONNECT_FAILURE 44FTFRCE_MQGET_FAILURE 46FTFRCE_MQINQ_FAILURE 51FTFRCE_MQOPEN_FAILURE 45FTFRCE_MQPUT_FAILURE 43FTFRCE_NO_AVAILABLE_SYNC_QUEUE

123FTFRCE_NO_STAGE_QUEUES_DEFINED

133FTFRCE_NON_PERSIST_STAGE_DATA_NO

T_FOUND 150FTFRCE_QUERY_STAGE_FAILED 159FTFRCE_RCVAUTH_EXIT_FAILURE 116


L

FTFRCE_RCVPOST_EXIT_FAILURE 114FTFRCE_RCVPRE_EXIT_FAILURE 113FTFRCE_RECEIVE_IMMED_RECOVERY

119FTFRCE_RECEIVE_IMMED_TIMEOUT 117FTFRCE_RECEIVER_FAILURE 67FTFRCE_RECORD_TOOBIG 99FTFRCE_REPLY_PROCESSING_FAILED 84FTFRCE_REPLY_TIMED_OUT 86FTFRCE_REQUEST_PROCESSING_FAILED

61FTFRCE_SDRAUTH_EXIT_FAILURE 115FTFRCE_SDRPOST_EXIT_FAILURE 112FTFRCE_SDRPRE_EXIT_FAILURE 111FTFRCE_SECURITY_ERROR 134FTFRCE_SEND_IMMED_TIMEOUT 118FTFRCE_SENDER_FAILURE 65FTFRCE_SOURCE_FILENAME_NOT_SPECI

FIED 136FTFRCE_SOURCE_POSTPROC_FAILED 100FTFRCE_SOURCE_PREPROC_FAILED 90FTFRCE_SOURCE_QMGR_NOT_SPECIFIED

138FTFRCE_SUBMIT_CANCEL_MESSAGE_FAI

LED 64FTFRCE_SUBMIT_REPLY_FAILURE 66FTFRCE_SYNCQ_PROCESSING_FAILED 56FTFRCE_UNABLE_TO_CREATE_DIRECTO

RY 70FTFRCE_UNABLE_TO_PROCESS_REQUES

T 128FTFRCE_UNABLE_TO_PROCESS_STAGE_I

TEM 125FTFRCE_UNABLE_TO_RETRIEVE_SECURI

TY_CONTEXT 141FTFRCE_UNABLE_TO_RETRIEVE_USERID

135FTFRCE_UNKNOWN_CONNECTOR_FILET

YPE 170FTFRCE_UNKNOWN_FTF_COMPONENT 80FTFRCE_UNKNOWN_MESSAGE_TYPE 59FTFRCE_UNSUPPORTED_FILETYPE 78FTFRCE_UUID_CREATE_FAILURE 82

FTFRCE_XML_CONVERSION_FAILURE171

FTFRCE_XML_PROCESSING_ERRORerror numbers

error number 811 172FTFRCI_CANCEL_PENDING 26FTFRCI_NO_MORE_DATA 29FTFRCI_NO_STATUS_MESSAGES_PRESEN

T 19FTFRCI_PING_COMPLETE_UNSUCCESSFU

L 25FTFRCI_REPLY_TO_PING_FAILED 24FTFRCI_REQUEST_CANCELLED 23FTFRCI_REQUEST_COMPLETE 21FTFRCI_REQUEST_COMPLETE_UNSUCCE

SSFUL 22FTFRCI_REQUEST_EXPIRED 20FTFRCI_REQUEST_FLAGGED_FOR_EXPIR

ATION 28FTFRCI_RESEND_DATA 30FTFRCI_RETRY_LIMIT_EXCEEDED 27FTFRCW_INVALID_REPLY_DESTINATION

35FTFRCW_NO_STATUS_MESSAGE_FOR_ID

32FTFRCW_STATUS_MESSAGE_PROCESSIN

G_FAILED 33FTFRCW_TIMEOUT 36FTFRCW_TXN_NOT_FOUND 34

IIII

ICCQueue errors 66, 89immediate 119

LLLL

log filelocating 12

log file access errors 102


T

MMMM

memory allocation errors 42message text 13messages

error 37informational 17warning 31

MQSeries related errors 43, 44, 45, 46, 47, 51,58, 60

OOOO

OS/390 errors 77, 78, 98, 104, 106, 107, 108,151, 152

PPPP

ping messages 24, 25pool errors 140primary return code 12

QQQQ

queue manager errors 101, 129, 138, 139

RRRR

receiver errors 67, 116, 117request messages 20, 21, 22, 23, 28, 29, 30

SSSS

secondary return code 13

security errors 134, 141sender errors 65, 115, 118stage errors 125, 133, 159status data errors 124status messages 32, 33sync queue errors 123synchronization errors 117, 118

TTTT

technical support 8text of message 13time value 12timeout errors 36, 81, 86


tivoli data exchange version 1.2.0 messages and...

Documents