version 7 release 1 z/vm · 2019. 4. 19. · before using this document, you should be familiar...

z/VMVersion 7 Release 1

TCP/IP Messages and Codes

IBM

GC24-6330-01

Note:

Before you use this information and the product it supports, read the information in “Notices” on page569.

This edition applies to version 7, release 1, modification 0 of IBM z/VM (product number 5741-A09) and to allsubsequent releases and modifications until otherwise indicated in new editions.

Last updated: 2019-04-11© Copyright International Business Machines Corporation 1987, 2019.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

List of Tables......................................................................................................... v

About This Document...........................................................................................viiHow to Send Your Comments to IBM......................................................................xiSummary of Changes for z/VM TCP/IP Messages and Codes.................................. xii

Chapter 1. Domain Name System Resolver Messages..............................................1

Chapter 2. FTP Messages....................................................................................... 9

Chapter 3. LDAP Server Messages........................................................................ 79

Chapter 4. MPROUTE Messages..........................................................................233

Chapter 5. NETSTAT Messages........................................................................... 287

Chapter 6. NFS Messages...................................................................................295

Chapter 7. PING Messages.................................................................................325

Chapter 8. PORTMAP Messages..........................................................................329

Chapter 9. Remote Printing Messages.................................................................331

Chapter 10. Remote Procedure Call Messages.................................................... 343

Chapter 11. REXEC and REXECD Messages......................................................... 355

Chapter 12. Site Table Configuration Messages...................................................363

Chapter 13. Simple Mail Transfer Protocol (SMTP) Messages............................... 367

Chapter 14. Simple Network Management Protocol (SNMP) Messages.................407

Chapter 15. Secure Socket Layer (SSL) Messages................................................423

Chapter 16. TCP/IP Server Messages..................................................................441

Chapter 17. TCP/IP Utilities............................................................................... 517

Chapter 18. TFTP Messages............................................................................... 551

Chapter 19. TRACERTE Messages....................................................................... 555

Chapter 20. UFTD Messages...............................................................................559

iii

Chapter 21. Miscellaneous Messages..................................................................561Notices..............................................................................................................569Bibliography...................................................................................................... 573Index................................................................................................................ 579

iv

List of Tables

1. Meanings of Severity Codes........................................................................................................................viii2. Meanings of message type (action) codes................................................................................................... ix3. LDAP server return codes......................................................................................................................... 2164. Subcode X'30' Return Codes.................................................................................................................... 469

v

About This Document

This document provides information about the messages and codes that occur in the IBM® TCP/IP forz/VM® level 710 networks. This document can also help you to determine whether a specific problem is aresult of the VM TCP/IP implementation.

This document lists, by category, messages and codes for TCP/IP level 710.

This document also includes an appendix and a bibliography.

Intended AudienceThis document is intended for use by system programmers for diagnosing problems. You should use thisdocument to:

Analyze a problemClassify the problem as a specific typeDescribe the problem to the IBM Support Center.

You should be familiar with TCP/IP and the protocol commands to use this document.

Before using this document, you should be familiar with z/VM, CP, and CMS. In addition, TCP/IP level 710should already be installed and customized for your network.

Conventions and TerminologyYou should read this document when you want to know the meaning of messages and codes that youreceive when operating in TCP/IP networks.

Locating Messages in This DocumentThis document is organized by chapter and then by function within each chapter. Messages associatedwith each function are sorted either alphabetically or by message number. If the message you are lookingfor has a message number, that section of the manual is sorted by message number. In some cases, themessage you are looking for has a message number associated with it, but the functional section doesnot. In this case, do not use the message number for searching; search for the message alphabetically.

Understanding Message Text FormatThis document explains message conventions used in this document, how numbers are used in thisdocument, and the TCP/IP message format.

Message Conventions Used in This Document

The following message conventions are used throughout this document:

• Uppercase letters represent values that you must type without change (these values are not case-sensitive).

• Lowercase letters represent values that must be entered in lowercase (these values are case-sensitive).• Lowercase italicized letters represent variable parameters for which you supply the values.• Square brackets [ ] enclose optional or conditional values.

Optional values can be omitted; when certain values are omitted, default values are used.

Conditional values can be omitted, depending on the statement.• Braces { } enclose values from which you must choose a value.

© Copyright IBM Corp. 1987, 2019 vii

• Vertical line symbols | indicate that you must select a value from either side of the symbol.

How Numbers Are Used in This Document

The following describes how numbers are used in this document:

• Numbers over four digits are represented in metric style. A space is used rather than a comma toseparate groups of three digits.

For example, the number sixteen thousand, one hundred forty-seven is written 16 147.• Periods in numbers separate the whole and the fractional portions of the numeral.• Some messages in this document have message numbers that contain a component ID in the message

number. For example, in the message DTCLDP2100, the LDP indicates that it is the LDAP componentthat issued the message.

TCP/IP Message Format

Some messages in this document consist of a message identifier (for example, DTCCLW110E) andmessage text. The identifier distinguishes messages from each other. The text is a phrase or sentencedescribing a condition that has occurred or requesting a response from the user.

The format of some message identifiers is:

xxxmmm###e

or

xxxmmm####e

This message format consist of four fields:xxx

Three digit prefix, for example, DTC.mmm

The three digit module code indicates which module generated the message. This field is usually anabbreviation of the name of the module in which the error occurred.

### or ####The numeric message number consists of three or four digits that are associated with the conditionthat caused the message to be generated.

eThe one digit severity code is a letter that indicates what kind of condition caused the message. Thedefinition of the severity codes depends on the nature of the routine producing the message.

Table 1 on page viii lists the severity codes and their meaning for the TCP/IP messages.

Table 1: Meanings of Severity Codes

Severity Code Meaning

I

W

E

S

R

T

Information only

Warning

Error

Severe error

Command response

Termination message

viii About This Document

MPRoute and LDAP Server Message Format

The format of some MPRoute and LDAP server messages differs from that of the TCP/IP messages. Thefollowing shows the message numbering convention used.

For MPROUTE:

EZZnnnnt

For LDAP:

GLDnnnnt

where:EZZ

Is the product identifier for MPRoute.GLD

Is the product identifier for LDAP.nnnn

Is a unique 4-digit numeric value assigned to the message.t

Is the message type that indicates the action assigned to the message. Message types and theirmeanings are:

Table 2: Meanings of message type (action) codes

Type Code Meaning

A

E

D

I

Immediate action required.

Eventual action required.

Immediate decision required.

Informational.

The message ID is followed by a single space and the message text.

How the Term “internet” is Used in This DocumentIn this document, an internet is a logical collection of networks supported by gateways, routers, bridges,hosts, and various layers of protocols, which permit the network to function as a large, virtual network.

Note: The term "internet" is used as a generic term for a TCP/IP network, and should not be confusedwith the Internet, which consists of large national backbone networks (such as MILNET, NFSNet, andCREN) and a myriad of regional and local campus networks worldwide.

Where to Find More InformationFor more information about related publications, see “Bibliography” on page 573.

Links to Other Documents and WebsitesThe PDF version of this document contains links to other documents and websites. A link from thisdocument to another document works only when both documents are in the same directory or database,and a link to a website works only if you have access to the Internet. A document link is to a specificedition. If a new edition of a linked document has been published since the publication of this document,the linked document might not be the latest edition.

About This Document ix

x z/VM: TCP/IP Messages and Codes

How to Send Your Comments to IBM

We appreciate your input on this publication. Feel free to comment on the clarity, accuracy, andcompleteness of the information or give us any other feedback that you might have.

To send us your comments, go to z/VM Reader's Comment Form (www.ibm.com/systems/campaignmail/z/zvm/zvm-comments) and complete the form.

If You Have a Technical Problem

Do not use the feedback method. Instead, do one of the following:

• Contact your IBM service representative.• Contact IBM technical support.• See IBM: z/VM Support Resources (www.ibm.com/vm/service).• Go to IBM Support Portal (www.ibm.com/support/entry/portal/Overview).

© Copyright IBM Corp. 1987, 2019 xi

http://www.ibm.com/systems/campaignmail/z/zvm/zvm-commentshttp://www.ibm.com/systems/campaignmail/z/zvm/zvm-commentshttp://www.ibm.com/vm/service/http://www.ibm.com/support/entry/portal/Overview/

Summary of Changes for z/VM TCP/IP Messages and Codes

This information includes terminology, maintenance, and editorial changes. Technical changes oradditions to the text and illustrations for the current edition are indicated by a vertical line to the left ofthe change.

GC24-6330-01, z/VM Version 7 Release 1 (April 2019)This edition includes changes to support product changes provided or announced after the generalavailability of z/VM V7.1.

[PI99085] TCP/IP Support for OSA-Express7S 25G

With the PTF for APAR PI99085, z/VM V7.1 provides support for the new OSA-Express7S 25G adapter,which is available with the IBM z14 GA2. The OSA-Express7S 25G adapter, which provides directconnections to clients on local area networks (LANs), features a new OSA generation and a new portspeed of 25 Gb.

The following change has been made as a result of this support:

• The explanation for message DTCOSD392E is updated to include 25 Gigabit Ethernet.

For more information, see Chapter 16, “TCP/IP Server Messages,” on page 441.

GC24-6330-00, z/VM Version 7 Release 1This edition includes changes to support the general availability of z/VM V7.1.

GDDMXD/VM support removed

The z/VM Graphical Data Display Manager (GDDM) interface to the X Window System (GDDMXD/VM) is nolonger supported, and the GDDMXD/VM messages have been removed.

IMAP support removed

The z/VM Internet Message Access Protocol (IMAP) server is no longer supported, and the IMAPmessages have been removed.

VMSES/E MIGRATE command support withdrawn

The VMSES/E MIGRATE command and related commands, first supplied with z/VM V5.2, are no longerprovided or supported in z/VM V7.1. Related changes to TCP/IP message documentation follow:

• DTCmmm3138E is now DTCSLP3138E (see “SSLPOOL Messages” on page 533.• Chapter 17, “TCP/IP Utilities,” on page 517 is updated.

– MIGVMTCP messages DTCMIG3106W through DTCMIG3170I are removed.

xii z/VM: TCP/IP Messages and Codes

GC24-6237-11, z/VM Version 6 Release 4 (December 2017)This edition includes changes to support product changes provided or announced after the generalavailability of z/VM V6.4.

APAR PI83256 adds the following message:

• DTCSSL507E (see “SSL Server Messages” on page 423)

The following message has been updated:

• DTCOSD045E (see Chapter 16, “TCP/IP Server Messages,” on page 441)

GC24-6237-10, z/VM Version 6 Release 4 (August 2017)This edition includes changes to support product changes provided or announced after the generalavailability of z/VM V6.4.

The following message has been updated:

• 1046 (see “TCPRUN Messages” on page 537)

The following messages have been removed from Chapter 16, “TCP/IP Server Messages,” on page 441:

• DTCPRS068E• DTCPRS069I• DTCPRS080E

Firewall Friendly FTPWith the PTF for APAR PI80912, the purpose of the Firewall Friendly FTP is to configure the FTP client todetermine the party initially responsible for initiating data connections, improve compliance with RFC2428, and reflect the active/passive FTP mode and the EPSV4 setting.

The following message has been added in “FTP Client Unnumbered Messages” on page 43:

• FWFRIENDLY value value is not valid. Default value used.

The following messages have been updated in “FTP Client Unnumbered Messages” on page 43:

• PORT command failed; code reply• Usage of PORT command is OFF• Usage of PORT command is ON

GC24-6237-09, z/VM Version 6 Release 4 (March 2017)This edition includes changes to support product changes provided or announced after the generalavailability of z/VM V6.4.

GC24-6237-08, z/VM Version 6 Release 4This edition includes changes to support the general availability of z/VM V6.4.

z/VM LDAP Server and Utilities z/OS V2.2 EquivalencyThe LDAP server has been upgraded to the current level of the z/OS® product.

The following messages have been added for this support:

Summary of Changes for z/VM TCP/IP Messages and Codes xiii

GLD1299I GLD1338E GLD9202A

GLD1300E GLD1340E GLD9203A

GLD1301E GLD8507E GLD9204E

GLD1302E GLD8508E GLD9205A

GLD1310W GLD8509E GLD9206A

GLD1311E GLD8511I GLD9207A

GLD1313E GLD8512I

GLD1337E GLD9201A

The following messages have been changed for this support:

GLD1070E

GLD2401E

The following messages have been removed.

ITY6595E

ITY6596A

ITY6597A

ITY6598A

The following reason codes have been added for this support.

R001108 R004208 R010070

R001109 R004209 R010071

R004203 R004210 R010072

R004204 R006057 R010073

R004205 R006058 R010074

R004206 R010068

R004207 R010069

z/VM MPROUTE Server z/OS V2.2 EquivalencyThe MPRoute server has been upgraded to the current level of the z/OS product.

The following messages have been added for this support:

EZZ8172IEZZ8174I

The following messages have been changed for this support:

EZZ7900I EZZ7923I EZZ7948I




EZZ7922I EZZ7946I

xiv z/VM: TCP/IP Messages and Codes

zManager Support RemovedThe IBM z Unified Resource Manager (zManager) is no longer supported in z/VM V6.3. The vswitch typesof IEDN and INMN have been removed from documentation.

The following messages have been updated for this support:

DTCOSD438EDTCOSD439EDTCOSD441E

The following messages have been deleted for this support:

DTCIPI060E DTCIPI064E DTCIPU241I

DTCIPI061E DTCIPI065I DTCPAR236I

DTCIPI062E DTCIPI067I DTCPAR237I

DTCIPI063E DTCIUI066I DTCOSD432E

Domain Name System (DNS) IPv6 SupportThe TCP/IP support for IPv6 Domain Name Servers updates will support IPv6 domain name system (DNS)servers that have an IPv6 address.

The following message has been added for this support:

NSINTERADDR

Summary of Changes for z/VM TCP/IP Messages and Codes xv

xvi z/VM: TCP/IP Messages and Codes

Chapter 1. Domain Name System Resolver Messages

This section contains unnumbered messages that the CMSRESOL utility issues.

The "Message n" identifiers that are used in this section are not actual message numbers; they areincluded for accessibility purposes only.

Most of these messages include the subroutine that is active when the message is issued. Because thesame message can be issued by multiple subroutines, that portion of the message cannot be used toindex the message. In the message descriptions, the subroutine name is referred to as RoutineName. Ingeneral, the messages in this topic are shown in alphabetical order (without respect to case) according tothe first words of the message that are not substituted during message generation.

Message 1 Data outside of inner parens

Explanation: A CMSRESOL command line containeddata outside the inner parenthesis. See z/VM: TCP/IPUser's Guide for the syntax of the CMSRESOLcommand.

System action: The CMSRESOL command terminates.

User response: Correct the command syntax.

Severity: Error.

Message 2 DATAGRAM|CONN & timeout argsmissing

Explanation: A CMSRESOL command ended before aconnection method and a time-out interval werespecified. See z/VM: TCP/IP User's Guide for the syntaxof the CMSRESOL command.


User response: Use the correct command linearguments.

Severity: Error.

Message 3 Incomplete section entry

Explanation: A CMSRESOL command line containedan incomplete additional or answer entry, as indicatedby the section message variable. See z/VM: TCP/IPUser's Guide for the syntax of the CMSRESOLcommand.


User response: Use the correct command line syntax.

Severity: Error.

Message 4 Incomplete entry list

Explanation: A CMSRESOL command line containedan incorrect number of entries. See z/VM: TCP/IPUser's Guide for the syntax of the CMSRESOLcommand.


User response: Use the correct syntax on thecommand line.

Severity: Error.

Message 5 Incomplete question entry

Explanation: A CMSRESOL command line containedan incomplete question entry. See z/VM: TCP/IP User'sGuide for the syntax of the CMSRESOL command.


User response: Use the correct command syntax.

Severity: Error.

Message 6 Invalid arg arg

ExplanationA CMSRESOL command line contained an invalidconnection method argument. Valid arguments are:

• CONN• DATAGRAM

See z/VM: TCP/IP User's Guide for the syntax of theCMSRESOL command.



Severity: Error.

Message 7 Invalid class data

Explanation: A response received by the CMSRESOLcommand line contained a class that is not valid orunderstood by CMSRESOL. This can happen becausecorrupted data was returned to CMSRESOL from aname server or the query specified a class of * (thewildcard or "any" class), and data was returned that isnot supported by CMSRESOL.


User response: The query may be changed so that theinvalid class is not returned.

Severity: Error.

System Resolver Messages

© Copyright IBM Corp. 1987, 2019 1

Message 8 Invalid name server address'IPaddress'

Explanation: A CMSRESOL command line contained aname server address that is not valid. See z/VM:TCP/IP User's Guide for the syntax of the CMSRESOLcommand.


User response: Correct the IP address of the nameserver. It should be in dotted decimal form("xxx.xx.x.xxx").

Severity: Error.

Message 9 Invalid opcode 'value'

ExplanationAn invalid opcode was specified in a CMSRESOLcommand. Valid opcode values are:

• CQUERYM• CQUERYU• IQUERY• QUERY



User response: Use a correct value for the opcode inthe CMSRESOL command.

Severity: Error.

Message 10 Invalid qclass 'value'

ExplanationAn invalid qclass was specified in a CMSRESOLcommand. Valid qclass values are:

• *• CS• IN



User response: Use a correct value for the qclass inthe CMSRESOL command.

Severity: Warning.

Message 11 Invalid qtype 'value'

ExplanationAn invalid qtype was specified in a CMSRESOLcommand. Valid qtype values are:

*AAXFRCNAMEHINFOLOC97MBMDMFMGMILA

MILBMINFOMRMXNSNULLPTRSOATXTWKS



User response: Use a correct value for the qtype in theCMSRESOL command.

Severity: Error.

Message 12 Invalid timeout 'value'

Explanation: An invalid timeout was specified in aCMSRESOL command. It may have contained anonnumeric character. The interval specification mustcontain only digits. See z/VM: TCP/IP User's Guide forthe syntax of the CMSRESOL command.



Severity: Error.

Message 13 Name server addr missing

Explanation: A CMSRESOL command ended before aname server address was specified. See z/VM: TCP/IPUser's Guide for the syntax of the CMSRESOLcommand.


User response: Invoke CMSRESOL with the requiredADDRESS parameter.

Severity: Error.

Message 14 Resolver error calling routinertnname by functname: Returncode return_codeReason code 0x reason_code

Explanation: The Resolver function functname calledthe routine rtnname and received an unexpected error.

System action: Processing continues.

System programmer response: Contact your IBMrepresentative. Note the entire text of the errormessage and the command that was issued in order tohelp diagnose the problem.


2 z/VM: TCP/IP Messages and Codes

Message 15 Resolver error calling routinertnname by functname: Routinenot found.

Explanation: The Resolver function functname calledthe routine rtnname, but it was not found.

System action: Processing continues.

System programmer response: Make sure you arerunning the correct level of CMS. If not, this is thereason for the failure. If the CMS level is correct andrtnname is a CSL routine, issue the CSLMAP commandand make sure rtnname is available. If not, make sureit is loaded and try the command again.

Message 16 RoutineName: Active opensuccessful on connection connNum

Explanation: The name server has opened an activeconnection with a foreign host using connectionconnNum. This message is logged because TCPconnections are not normally used for name servercommunications. It does not indicate a problem.

System action: Execution continues.

User response: None.

Severity: Informational.

Message 17 RoutineName: Address conversionfailed for 'IPaddress'

Explanation: The data displayed in IPaddress is not avalid IP address.

System action: The effect of this error depends onwhat is being processed when it is discovered. Usuallyit will be accompanied by other messages.



Message 18 RoutineName: Buffer pointer is'bufferAddress'x

Explanation: This message displays the address of thebuffer that is about to be displayed. It is associatedwith various diagnostic traces. It can also occur whenan error has occurred and additional diagnosticinformation about the error is being written to theconsole.


User response: This message can be ignored if notaccompanied by other messages indicating an errorsituation.


Message 19 RoutineName: Can't close inactiveconnection connNum

Explanation: The program was unable to send theresponse and tried to close the connection, but thatconnection is now inactive. The close is unnecessary.




Message 20 RoutineName: Can't send tcp replyon inactive connection connNum

Explanation: The program was attempting to send aTCP reply packet back along the TCP connection it wasreceived on, but that connection is now inactive andthe reply will not be sent.




Message 21 RoutineName: ConnectionconnNum closed normally

Explanation: The specified connection closed whenexpected. The message is only issued duringdiagnostic tracing.

System action: None.



Message 22 RoutineName: Connection:connNum Foreign Address:IPaddress

Explanation: This message usually follows anothermessage. It provides the connection number and theIP address of a foreign host for a TCP connection. Themessage can be issued when a error has occurred on aconnection. It can also be issued during diagnostictracing.




Message 23 - RoutineName: Connection:connNum- RoutineName: Notification:noteType- RoutineName: Amount of spacein bytes: byteCount.- RoutineName: New state:tcpipState- RoutineName: Reason reasonInfo- RoutineName: Bytes delivered:byteCount- RoutineName: Push flag:flagValue


Domain Name System Resolver Messages 3

- RoutineName: Last urgent byte:value- RoutineName: Bytes to read:byteCount- RoutineName: Urgent span:value}

Explanation: This sequence of messages displays thecontent of a notification. Not all the messages will bepresent; the content depends on the type ofnotification that is received. The messages aredisplayed because an error just occurred with thisnotification, or diagnostic tracing is active.




Message 24 RoutineName: connTypeconnection never opened

Explanation: A passive or active connection nevercompleted the open process. It may have timed out orthe program may be in the process of shutting down.

System action: The connection information is cleanedup. The connection can then be used for other activity.


Severity: Warning.

Message 25 RoutineName: Data length size >UDPBUFSIZE

Explanation: The program received a query via UDPthat was larger than the UDP buffer size being used.The incoming data will be truncated, but that does notcreate any problems with program operation. Thismessage is only displayed if diagnostic tracing isactive.




Message 26 RoutineName: Data neverdelivered on connNum connection

Explanation: A passive or active connection neverreceived any data. This is an unexpected situation, andmay be accompanied by other error messages. Theconnection may have timed out or the program servermay be in the process of shutting down.

System action: The connection information is cleanedup. The connection will be reused for other activity.


Severity: Warning.

Message 27 RoutineName: DATAdeliverederror, bytes = byteCount

Explanation: The program server received a DATAdelivered notification, but the count of the bytesdelivered was less than 0.

System action: The transaction is terminated. Thetransaction will have to be retried from the originatingend.


Severity: Error.

Message 28 RoutineName: Datagram replytruncated

Explanation: The data returned from the name serverwas truncated. This is not expected since a TCPconnection was used. The problem is most likely withthe name server.

System action: The operation is terminated.

User response: Route the question to a different nameserver.

Severity: Error.

Message 29 RoutineName: dataType data:length is 0

Explanation: A resource record of type dataTypeshould contain data, but the length of the data portionof the record is 0.

System action: The current transaction may fail. Theoriginating host will have to retry the operation.

User response: The error can occur because an invalidresource record was received from another program.

Severity: Warning.

Message 30 RoutineName: Displaying storageat addr for dLen ('hLen'x) bytesmemoryAddress hWord hWord hWord hWord *cData*

Explanation: These messages are used to display thecontents of memory during diagnostic tracing andwhen certain errors occur. The first indicates where inmemory the data being displayed is located and howmany bytes are being displayed. The second messageshows the contents of that section of memory. ThecharacterData will be displayed as EBCDIC, unless amessage indicates otherwise. The second messagewill be repeated as many times as necessary to displayall the data.


User response: The information may be useful indetermining the nature of any problem reported orbeing diagnosed.




Message 31 RoutineName: Error returnCodebeginning TCP/IP service

Explanation: TCP/IP services could not be initialized,making it impossible for the program to function. Themost common cause of this problem is TCP/IP servicemachine is not operational. The ReturnCode can beused to further investigate the nature of the problem.

System action: The program will terminate.

User response: Investigate why the error may haveoccurred. Correct the cause of the error and retry thecommand.

Severity: Error.

Message 32 RoutineName: Error returnCodefrom calledRoutine

Explanation: The calledRoutine encountered an errorand returned with a nonzero returnCode. Othermessages may give more details about the nature ofthe specific error. The error is probably the result ofinvalid data being sent to the program from anothersystem. The current question or transaction will notcomplete successfully, but the program shouldcontinue operation and process other questions andtransactions without any problems.

System action: The current operation is usuallyterminated. The host requesting the service isresponsible to retry the operation.


Severity: Error.

Message 33 RoutineName: Error inTCPIPservice: errorInfo

Explanation: An error occurred in a TCP/IP service.The failing service is identified by TCPIPservice and thenature of the failure is described by errorInfo. Althoughthe TCP/IP services are not expected to encountererrors, temporary network outages and other unusualcircumstances can lead to intermittent errors.

System action: This depends on the failing service. Itmay lead to the server terminating. It usually results inthe current operation being terminated. The hostrequesting the service is responsible to retry theoperation.


Severity: Error.

Message 34 RoutineName: Error openingconnection to remote name server

Explanation: An error occurred while attempting toopen a TCP connection to a remote name server. Theoperation that was going to be performed isterminated. This can happen when attempting to send

a request to a remote name server via TCP. The actionwill be retried. The situation can be caused by networkoutages or failures at the remote host.

System action: The operation will be retried.


Severity: Warning.

Message 35 RoutineName: Ignoring new statetcpipState on inactive connectionconnNum

Explanation: A Connection State Changed notificationarrived as the connection was being aborted. The statenumber and connection number are displayed.

System action: The name server ignores thenotification.



Message 36 RoutineName: Insufficient dataavailable

Explanation: The program received a datagramcontaining fewer bytes than was requested. The sizerequested was based on the amount expected andrequired to continue processing the current request.

System action: The current request fails.


Severity: Warning.

Message 37 RoutineName: Invalid flags 'xxxx'x

Explanation: A name being extracted from a nameserver packet is incorrectly constructed.

System action: The data from such a packet is usuallydiscarded. The program may return an error packet tothe sending host with a return code that indicates aformatting error.

User response: If these messages become excessive,turn on queue tracing to determine the source of thebad packets and contact the name serveradministrator of that system.

Severity: Error.

Message 38 RoutineName: name='name',type=type, class=class

Explanation: The contents of some of the fields of aresource record are displayed.




Message 39 RoutineName: pointer is NULL



Explanation: This message may be seen duringdiagnostic tracing when certain control blocks arebeing displayed. It means that the control block doesnot exist and the pointer to it is not defined.




Message 40 RoutineName: qname='name',qtype=type, qclass=class

Explanation: This message displays the contents of aname server query. This message is most often seenwhen various diagnostic traces are active, but can alsooccur when an error has occurred to indicate thequestion the error is associated with.




Message 41 RoutineName: Request for storageof size bytesOfStorage

Explanation: This message is usually seen duringdiagnostic storage tracing. It can also be seen if theprogram requests an invalid storage size (negative or0) or the virtual machine does not have enough freestorage to satisfy the name server's storage request.




Message 42 RoutineName: Received badpacket from IPaddress

Explanation: A packet was received from a nameserver or resolver, at the indicated IP address, thatcould not be processed because it appeared to beimproperly formatted.

System action: If the packet is a response to aquestion sent to a remote name server, the response isignored and attempt is made to get an answer fromsome other name server.

User response: If many invalid packets are beingreceived, then you can elect to investigate bycontacting the owner of the host that is sending thebad packets. Traces can also dump the inboundpackets so the content of these packets can beexamined.


Message 43 RoutineName: Response fromunexpected address fromAddress,expected expectedAddress

Explanation: A name server query was forwarded to aremote name server for processing. The response wasreceived, but it was not received from the IP addressthat it was sent to. This situation happens infrequently,and usually when it does it is not an indication of aproblem. There is a small chance that the responsewas not returned by a name server and was intendedto cause problems for your name server. If thismessage occurs frequently, it may be prudent toinvestigate their occurrence.



Severity: Warning.

Message 44 RoutineName: Results fromTcpStatus

Explanation: This is the header line preceding adisplay of the status of a TCP connection. The messageis only issued during diagnostic tracing.




Message 45 RoutineName: Timer expired forconnection connNum

Explanation: A TIMER expired notification whilewaiting for a TCP connection to close.

System action: The connection is aborted and theconnection block is cleaned up.


Severity: Warning.

Message 46 RoutineName: Timer expired forinactive connection

Explanation: A TIMER expired notification wasreceived for a connection block that is not in use.

System action: The notification is ignored.


Severity: Warning.

Message 47 RoutineName: ttl=valuerdata='value'

Explanation: The contents of some of the fields of aresource record are displayed.




Message 48 RoutineName: Unexpectednotification notificationID



Explanation: An unexpected notification arrived whilewaiting for activity on a connection. The notification IDis displayed.


User response: This message can be ignored if notaccompanied by other messages indicating an errorsituation.


Message 49 RoutineName: Unexpected querytype queryType

Explanation: A name server query arrived thatcontained a queryType that the program does notrecognize and cannot process.

System action: The query is ignored.


Severity: Warning.

Message 50 Timeout arg missing

Explanation: A CMSRESOL command line omitted atimeout-interval specification. See z/VM: TCP/IP User'sGuide for the syntax of the CMSRESOL command.


User response: Verify the correct use of the TIMEOUTvalue in the parameter list.

Severity: Error.

Message 51 Too many nested parentheses

Explanation: A CMSRESOL command line containedan incorrect number of nested parentheses; themaximum is two levels of nested parentheses. Seez/VM: TCP/IP User's Guide for the syntax of theCMSRESOL command.


User response: Verify the correct syntax of thecommand.

Severity: Error.

Message 52 Too many parms in section entry

Explanation: A CMSRESOL command line contained aquestion, additional, or answer entry with too manyparameters. See z/VM: TCP/IP User's Guide for thesyntax of the CMSRESOL command.



Severity: Error.

Message 53 Too many right parens

Explanation: A CMSRESOL command line containedan incorrect number of right parentheses. See z/VM:TCP/IP User's Guide for the syntax of the CMSRESOLcommand.



Severity: Error.

Message 54 Undefined state stateValue

Explanation: The old connection state value was notan expected value.

System action: The connection state is set to a correctvalue.


Severity: Warning.



Chapter 2. FTP Messages

This chapter contains File Transfer Protocol (FTP) messages.

FTP Server Numbered MessagesThis section contains the numbered FTP server messages.

DTCFTS0002I Using translate table filenameTCPXLBIN.

Explanation: The FTP server has successfully loadedthe required translation table from the specifiedTCPXLBIN file.

System action: Program execution continues.


Module: FTSRVPA PASCAL


Procedure Name: Initialize

DTCFTS0003I Using built-in translate tables.

Explanation: The FTP server could not load theSRVRFTP TCPXLBIN or the STANDARD TCPXLBINtranslation file, so the server is going to use the default7-bit translation table.


User response: If the FTP server should use theSRVRFTP TCPXLBIN or the STANDARD TCPXLBINtranslation file, make sure the correct translation file isin the FTP server search order and restart the FTPserver.




DTCFTS0004E Server-FTP: program requires ECMODE ON.

Explanation: EC MODE is off.

System action: The server program halts at this point.

User response: Verify that EC MODE, or EC MODEemulation is on. Correct your input and try again.


Severity: Error.


DTCFTS0005E Server-FTP: unable to determinevirtual machine ID

Explanation: FTP cannot determine the servermachine’s virtual ID.


User response: Enter a valid virtual machineidentification code. Check the system configuration toensure that an FTP server machine has been identifiedand is operational.


Severity: Error.


DTCFTS0009E Port number port_number is notvalid

Explanation: The indicated port number is not a validsetting for the PORT statement. The port number mustbe a number between 1 and 65 534.

System action: Server initialization stops.

User response: Correct the configuration filestatement and restart the FTP server.


Severity: Error.

Procedure Name: ProcessConfigFile

DTCFTS0010I External Security Manager will beused

Explanation: The FTP server will use an ExternalSecurity Manager for authentication purposes.



Module: FTSVMSUB PASCAL


Procedure Name: SystemInitialize

DTCFTS0013E Unrecognized configuration filestatement: statement

Explanation: The listed statement is not a supportedFTP server configuration file statement. Forinformation about statements and operands that can

FTP Messages

© Copyright IBM Corp. 1987, 2019 9

be specified for configuring the FTP server, see z/VM:TCP/IP Planning and Customization.


User response: Delete or correct the statement that isin error, then restart the FTP server.


Severity: Error.

Procedure Name: DoNewCommand

DTCFTS0014I Using port port.

Explanation: The FTP server will listen for FTP clientson the specified port.




Severity: Informational


DTCFTS0015I Inactivity time is time.

Explanation: The FTP server will use the specifiedamount of time for determining when an inactiveconnection should be closed.






DTCFTS0019E Cannot start ServerFtp:ReturnCode

Explanation: You received a nonzero return code atinitialization.

System action: The server program halts.

User response: Identify the problem and resubmit thejob.


Severity: Error.

Procedure Name: MainLoop

DTCFTS0020E Server-FTP cannot do its initialpassive open

Explanation: An error occurred when the FTP serverattempted a passive open on the FTP service portconnection. Refer to any accompanying informationalmessage(s) that may precede this message to helpdetermine the cause for this initialization error. If noadditional messages are present, the reason for thenonzero return code is unknown.

System action: The FTP server program halts.

User response: Attempt to correct the problem, andthen restart the server.

DTCFTS0021I Server-FTP: Initializationcompleted DateTime

Explanation: FTP server initialization completed at thespecified date and time.






DTCFTS0031I Got note Other external interruptreceived, RuptCode =interruption_code

Explanation: The FTP server has received an externalinterruption that contains the specifiedinterruption_code.

System action: FTP server execution continues.

User response: Determine what type of externalinterruption has been received based on theinterruption code and what, if anything, should havebeen done by the FTP server in response to theinterruption. If necessary, contact the IBM SupportCenter for assistance.




DTCFTS0033E FSENDresponse note shows error:reason

Explanation: The FTP server received an error when ittried to send data over a connection. The reasonindicates the problem.


User response: Determine why the data could not besent over the connection. If needed, contact your IBMSupport Center for assistance.


Severity: Error.


DTCFTS0034E FRECEIVEerror note on #connshows: reason

Explanation: The FTP server received an error when ittried to receive data over a connection. The reasonindicates the problem.

FTP Messages



User response: Determine why the data could not bereceived over the connection. If needed, contact yourIBM Support Center for assistance.


Severity: Error.


DTCFTS0035I Connection conn: received note'type'

Explanation: The FTP server received the givennotification type on the specified connection. Thisnotification type is not supported.


User response: Determine why the FTP serverreceived the specified notification. If needed, contactyour IBM Support Center for assistance.




DTCFTS0045I Got note Other external interruptreceived (CP external commandcode 64)

Explanation: The FTP server has received a CPEXTernal command external interruption.

System action: The FTP server aborts all openconnections and terminates.

User response: Enter a second CP EXTernal commandto terminate the FTP server immediately withoutwaiting for open connections to be aborted.




DTCFTS0046I Got note Other external interruptreceived (FTP services code 9731)

Explanation: The FTP server has received an FTPservices external interruption. The FTP servercommunicates with the hardware managementconsole machine in part by issuing an internal CPdiagnose. CP issues an FTP services externalinterruption when the associated HMC FTP servicesfunction is complete.

System action: FTP server execution continues.

User response: See message DTCFTS3006I todetermine the FTP services function and return codeassociated with the external interruption.




DTCFTS0100E Error:SECUREhandshakeCOMPLETE forconnection conn with securestatus of status.

ExplanationA software error exists in the FTP server. ASECUREhandshakeCOMPLETE event was received forthe specified connection, but the secure status of theconnection was the given status instead of theexpected status of TLSsecure for data connections andHANDSHAKING for control connections. The followingstatus values exist:

CLEAR (0)TLSsecure (1)HANDSHAKING (2)

System action: Server execution continues.

User response: Contact your IBM Support Center forassistance.

Module: FTSEVEN PASCAL

Severity: Error.

Procedure Name: SecureTLSEvent

DTCFTS0104E Unable to secure connection conn:reason.

Explanation: An error occurred attempting to securethe specified connection using TLS. The reason givesmore information on what occurred. Positive returncodes indicate the problem was detected by theSecure Sockets Layer. For an explanation of thesereturn codes, see the section titled "SSL FunctionReturn Codes" in z/OS Cryptographic Service SystemSecure Sockets Layer Programming. Negative returncodes indicate the problem was detected by theTCP/IP stack.


User response: If needed, contact the IBM SupportCenter for assistance.


Severity: Error.


DTCFTS0105E Unexpected notification_typenotification received onconnection conn, ignoring.

Explanation: The specified notification was receivedfor the given unknown connection. The notification isignored.

FTP Messages

FTP Messages 11




Severity: Error.


DTCFTS0260I Using Kanji translate tableFileName FileType

Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPKJBIN binary translate table file.






DTCFTS0261I Using Hangeul translate tableFileName FileType

Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPHGBIN binary translate table file.






DTCFTS0262I Using TChinese translate tableFileName FileType

Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPCHBIN binary translate table file.






DTCFTS0263I *** Warning: Could not load theKanji translation table

Explanation: The FTP server was attempting to load aDBCS translation table from the TCPKJBIN binarytranslate table file. All files in the search orderhierarchy for TCPKJBIN either do not exist or do notcontain data in the required format for DBCS binarytranslate tables.

System action: No Kanji translation table is loaded,and program execution continues. Kanji DBCSconversion types will be unavailable.

User response: Configure a valid DBCS binarytranslate table file in the search order hierarchy forTCPKJBIN. See the z/VM: TCP/IP Planning andCustomization for more information about loading andcustomizing DBCS translation tables.


Severity: Error.


DTCFTS0265I *** Warning: Could not load theHangeul translation table

Explanation: The FTP server was attempting to load aDBCS translation table from the TCPHGBIN binarytranslate table file. All files in the search orderhierarchy for TCPHGBIN either do not exist or do notcontain data in the required format for DBCS binarytranslate tables.

System action: No Hangeul translation table is loaded,and program execution continues.

User response: Configure a valid DBCS binarytranslate table file in the search order hierarchy forTCPHGBIN. See the z/VM: TCP/IP Planning andCustomization for more information about loading andcustomizing DBCS translation tables. Hangeul andKSC5601 DBCS conversion types will be unavailable.


Severity: Error.


DTCFTS0267I *** Warning: Could not load theTchinese translation table

Explanation: The FTP server was attempting to load aDBCS translation table from the TCPCHBIN binarytranslate table file. All files in the search orderhierarchy for TCPCHBIN either do not exist or do notcontain data in the required format for DBCS binarytranslate tables.

System action: No Traditional Chinese translationtable is loaded, and program execution continues. TheTraditional Chinese DBCS conversion type will beunavailable.

User response: Configure a valid DBCS binarytranslate table file in the search order hierarchy forTCPCHBIN. See the z/VM: TCP/IP Planning andCustomization for more information about loading andcustomizing DBCS translation tables.


Severity: Error.

FTP Messages



DTCFTS0300I Unable to determine TCP/IP buffersize; default = 8K.

Explanation: An error occurred when the FTP serverqueried the stack for the TCP/IP buffer size. A defaultof 8K will be used.






DTCFTS0307E Configuration file name is not valid

Explanation: The configuration file name specifiedwith the SRVRFTP command contains more than eightcharacters.


System programmer response: None.

User response: Correct the appropriate :Parms. tagentry in the DTCPARMS file, then restart the FTPserver.


Severity: Error.

Procedure Name: InitConfigs

DTCFTS0308E Configuration file type is not valid

Explanation: The configuration file type specified withthe SRVRFTP command contains more than eightcharacters.





Severity: Error.


DTCFTS0309E Configuration file mode is not valid

Explanation: The configuration file mode specifiedwith the SRVRFTP command contains more than twocharacters.





Severity: Error.


DTCFTS0310I Unable to find input file: filenamefiletype filemode

Explanation: The configuration file listed in themessage does not exist on any minidisk that has beenaccessed by the FTP server.


User response: Verify the correctness of theappropriate :Parms. tag entry in the DTCPARMS fileand that the specified file is located on a minidisk thatis accessed by the FTP server, then restart the server.


Severity: Error.


DTCFTS0311E Invalid numeric operand found:operand

Explanation: While parsing the FTP serverconfiguration file, the FTP server found the specifiedoperand when it expected to find a number.


User response: Correct the appropriate configurationfile statement and restart the FTP server.


Severity: Error.

Procedure Name: Error

DTCFTS0312E Port number not specified forPORT statement

Explanation: The PORT statement requires a portnumber to be specified.




Severity: Error.


DTCFTS0313E Setting not specified for INACTIVEstatement

Explanation: The INACTIVE statement requires atiming value (in seconds) to be specified.



FTP Messages

FTP Messages 13


Severity: Error.


DTCFTS0314E Translate table not specified forLOADDBCSTABLE statement

Explanation: The LOADDBCSTABLE statementrequires a valid table name to be specified. Fordetailed information about the LOADDBCSTABLEstatement see z/VM: TCP/IP Planning andCustomization.




Severity: Error.


DTCFTS0315E INACTIVE time seconds is not valid

Explanation: The timing value specified for theINACTIVE statement is not correct. The INACTIVEtime setting must be an integer between 1 and1,048,576.




Severity: Error.


DTCFTS0317E Unrecognized option: option

Explanation: An unsupported option was specified onthe SRVRFTP command.


User response: Specify only supported options on theSRVRFTP command.


Severity: Error.

Procedure Name: ParseOptions

DTCFTS0349E Translate table table-name is notvalid

Explanation: The indicated translation table is notvalid for the LOADDBCSTABLE statement. For detailedinformation about the LOADDBCSTABLE statement seez/VM: TCP/IP Planning and Customization.




Severity: Error.

Procedure Name: ProcessConfigFile

DTCFTS0358E RDR statement filemode fm is notvalid or is not writable

Explanation: The indicated file mode is not a valid filemode, or the file mode is valid but is not accessed withread/write status.


User response: Ensure the file mode specified for theRDR statement is valid and that the file mode inquestion can be accessed by the FTP server with read/write status, then restart the FTP server.

Module: FTSRVPA PASCAL, FTSVMSUB PASCAL

Severity: Error.

Procedure Name: Error, SystemInitialize

DTCFTS0359I Filemode 'RDRfm' will be used forreader file support

Explanation: The specified file mode will be used totemporarily store files before they are sent to a virtualreader.






DTCFTS0360E Filemode not specified for RDRstatement

Explanation: The RDR statement requires a valid filemode to be specified.




Severity: Error.


DTCFTS0363I DMSESM rc=rc; All minidisk linkswill be performed using native CPsecurity services

Explanation: CSL routine DMSESM returned a nonzeroreturn code and was unable to obtain a security tokenfor ESM calls.

FTP Messages


System action: FTMAIN is exited.

User response: Contact your RACF® administrator todetermine the cause of the problem.


Severity: Error.


DTCFTS0365E DMSPWCHK call returns rc;Logdata: 'data'

Explanation: The DMSPWCHK CSL routine, used forpassword validation produced a return code greaterthan 8. Therefore, the password supplied by a clientwas not validated. The LogData information shown, ifany, is that provided by DMSPWCHK.


User response: Contact the system administrator forthe External Security Manager (ESM) that is in use, forassistance in resolving this problem.


Severity: Error.

Procedure Name: DoPass

DTCFTS0366E Wrong level of CMS: routine notfound

Explanation: A CSL routine returned with a -7 returncode, meaning the routine was not found.


User response: Re-IPL with the appropriate level ofCMS.

Module: FTSRVPA, FTSVMSUB

Severity: Error.

Procedure Name: Initialize, SystemInitialize,CheckPassword

DTCFTS0367E Wrong level of CP: Diagnose 88 notavailable

Explanation: Diagnose 88 support is not available inthe level of CP that you are running.


User response: Upgrade to the appropriate level ofz/VM.

Module: FTSVMSUB

Severity: Error.


DTCFTS0368I Warning: FTP server is missingclass D privileges for virtual readersupport

Explanation: The FTP server needs class D privilegesin order to delete or list spool files in a virtual reader.Since the FTP server is missing class D privileges, thiscapability will not be available for virtual readersupport.


User response: If users need to be able to list ordelete virtual reader files, the FTP server must begiven class D privileges.


Severity: Error.


DTCFTS0369E Format type not specified forLISTFORMAT statement

Explanation: The LISTFORMAT statement requires atype of list format to be specified; valid list formattypes are VM and UNIX.




Severity: Error.


DTCFTS0370E LISTFORMAT type list_format isnot valid

Explanation: The indicated type of list format is notvalid for the LISTFORMAT statement. Valid list formattypes are VM and UNIX.




Severity: Error.


DTCFTS0371I Default list format is format

Explanation: The FTP server will use the specifieddefault list format unless a specific list format hasbeen configured for a user in the CHKIPADR exit or thelist format has been changed for a session using theFTP SITE subcommand.






FTP Messages

FTP Messages 15

DTCFTS0372E AUTOTRANS setting setting is notvalid

Explanation: The indicated automatic translationsetting is not valid for the AUTOTRANS statement.Valid automatic translation settings are ON and OFF.




Severity: Error.


DTCFTS0373I Default automatic translation isturned setting

Explanation: The FTP server will use the specifieddefault automatic translation setting unless a specificautomatic translation setting has been configured for auser in the CHKIPADR exit or the automatic translationsetting has been changed for a session using the FTPSITE subcommand.






DTCFTS0374E Setting not specified forAUTOTRANS statement

Explanation: The AUTOTRANS statement requires anautomatic translation setting to be specified; validsettings are ON and OFF.




Severity: Error.


DTCFTS0376E TIMESTAMP setting timestamp-setting is not valid

Explanation: The indicated type of TIMESTAMPsetting is not valid for the TIMESTAMP statement. ValidTIMESTAMP settings are ON and OFF.




Severity: Error.


DTCFTS0400E Setting not specified forSYSTEMGREETING statement

Explanation: The SYSTEMGREETING statementrequires a setting to be specified; valid settings are ONand OFF.


User response: Correct the SYSTEMGREETINGconfiguration file statement and restart the FTP server.


Severity: Error.


DTCFTS0401E SYSTEMGREETING setting settingis not valid

Explanation: The indicated setting is not valid for theSYSTEMGREETING statement. Valid settings for theSYSTEMGREETING statement are ON and OFF.


User response: Correct the SYSTEMGREETINGconfiguration file statement and restart the FTP server.


Severity: Error.


DTCFTS0402E Low port not specified forPASSIVEPORTRANGE statement.

Explanation: A low port value indicating the start ofthe passive port range was not specified on thePASSIVEPORTRANGE statement in the FTP serverconfiguration file. A low port and high port value mustbe specified when the PASSIVEPORTRANGEstatement is used.

System action: Server initialization halts.

User response: Correct the FTP server configurationfile and restart the FTP server.


Severity: Error.


DTCFS0403E High port not specified forPASSIVEPORTRANGE statement.

Explanation: A high port value indicating the end ofthe passive port range was not specified on thePASSIVEPORTRANGE statement in the FTP serverconfiguration file. A low port and high port value mustbe specified when the PASSIVEPORTRANGEstatement is used.

FTP Messages





Severity: Error.


DTCFTS0404E PASSIVEPORTRANGE low portvalue value is not valid.

Explanation: The specified low port value given on thePASSIVEPORTRANGE statement in the FTP serverconfiguration file is not valid. The value must be anumber between 0 and 65535.




Severity: Error.

Procedure Name: Error.

DTCFTS0405E PASSIVEPORTRANGE high portvalue value is not valid.

Explanation: The specified high port value given onthe PASSIVEPORTRANGE statement in the FTP serverconfiguration file is not valid. The value must be anumber between 0 and 65535.




Severity: Error.


DTCFTS0406E Setting not specified forSECURECONTROL statement.

Explanation: A minimum security level setting was notspecified on the SECURECONTROL statement in theFTP server configuration file. The minimum securitylevel (ALLOWED, REQUIRED, or NEVER) must bespecified when the SECURECONTROL statement isused.




Severity: Error.


DTCFTS0407E SECURECONTROL setting setting isnot valid.

Explanation: The specified setting given on theSECURECONTROL statement in the FTP serverconfiguration file is not valid. The value must beALLOWED, REQUIRED, or NEVER.




Severity: Error.


DTCFTS0408E Setting not specified forSECUREDATA statement.

Explanation: A minimum security level setting was notspecified on the SECUREDATA statement in the FTPserver configuration file. The minimum security level(ALLOWED , REQUIRED, orNEVER) must be specifiedwhen the SECUREDATA statement is used.




Severity: Error.


DTCFTS0409E SECUREDATA setting setting is notvalid.

Explanation: The specified setting given on theSECUREDATA statement in the FTP serverconfiguration file is not valid. The value must beALLOWED, REQUIRED, or NEVER.




Severity: Error


DTCFTS0410E Label not specified for TLSLABELstatement.

Explanation: A label was not specified on theTLSLABEL statement in the FTP server configurationfile. The label must be specified when the TLSLABELstatement is used.


FTP Messages

FTP Messages 17



Severity: Error.


DTCFTS0411E TLSLABEL must be 1 to 8characters in length.

Explanation: The TLS label specified on the TLSLABELstatement in the FTP server configuration file is notvalid. The label must be 1 to 8 characters in length.




Severity: Error.


DTCFTS0414I Default secure control connectionlevel is level.

Explanation: The specified minimum security levelwill be used when processing FTP client requests tosecure control connections. Refer to the Configuringthe FTP Server chapter in z/VM: TCP/IP Planning andCustomization for more information.



Module: FTSEVEN PASCAL, FTSVMSUB PASCAL


Procedure Name: DoSecure, DisplaySettings

DTCFTS0415I Default secure data connectionlevel is level.

Explanation: The specified minimum security levelwill be used when processing FTP client requests tosecure data connections. Refer to the Configuring theFTP Server chapter in z/VM: TCP/IP Planning andCustomization for more information.





Procedure Name: DoSecure, DisplaySettings

DTCFTS0416I TLS label is label.

Explanation: The specified label will be used whensecuring control and data connections using TLS. Referto the Configuring the FTP Server chapter in z/VM:

TCP/IP Planning and Customization for moreinformation.





Procedure Name: DoTLSLabel, DisplaySettings

DTCFTS0418I Passive data port range is portslow_port to high_port.

Explanation: The specified port range will be used forpassive FTP data transfer. Refer to the Configuring theFTP Server chapter in z/VM: TCP/IP Planning andCustomization for more information.





Procedure Name: DisplaySettings

DTCFTS0419E SECUREDATA setting must beNEVER when SECURECONTROLsetting is NEVER.

Explanation: The minimum security level for controlconnections has been configured as NEVER using theSECURECONTROL statement in the FTP serverconfiguration file, but secure data connections havebeen configured using the SECUREDATA ALLOWED orSECUREDATA REQUIRED statement. This is notallowed. In order to secure data connections, the FTPcontrol connection must already be secure.


User response: If secure data connections aredesired, correct the SECURECONTROL statement inthe FTP server configuration file and restart the FTPserver. Otherwise, correct the SECUREDATA statementand restart the FTP server.


Severity: Error.


DTCFTS0421E Setting not specified forFTPKEEPALIVE statement

Explanation: The FTPKEEPALIVE statement requires asetting to be specified; valid settings are ON and OFF.


User response: Correct the FTPKEEPALIVEconfiguration file statement and restart the FTP server.


FTP Messages


Severity: Error.


DTCFTS0422E FTPKEEPALIVE setting setting isnot valid

Explanation: The indicated setting is not valid for theFTPKEEPALIVE statement. Valid settings for theFTPKEEPALIVE statement are ON and OFF.


User response: Correct the FTPKEEPALIVEconfiguration file statement and restart the FTP server.


Severity: Error.


DTCFTS0423I Warning: Unable to set KEEPALIVEoption for FTP control connection:result

Explanation: FTP server failed to turned on TCP/IPserver's keepalive mechanism for current controlconnection.


User response: Use the specified result to determinean appropriate action. If necessary, call the IBMSupport Center for assistance.


Severity: Warning.

Procedure Name: NewConnectionEvent

DTCFTS0424I KEEPALIVE has been enabled

Explanation: FTP server has turned on TCP/IP server'skeepalive mechanism to avoid timing out idle controlconnections.






DTCFTS0425I Keepalive setting for controlconnections

Explanation: The specified FTP keepalive mechanismwill be used when a control connection is establishedwith FTP server. Refer to the Configuring the FTPServer chapter in z/VM: TCP/IP Planning andCustomization for more information.





Procedure Name: DoFTPkeepalive, DisplaySettings

DTCFTS2500I NewConnectionEvent: Bad statestate

Explanation: NewConnectionEvent was called whenthe connection was in the specified state instead ofCONNECTIONopening state.




Severity: Informational


DTCFTS2512E Error completion on #connection:reason

Explanation: The specified connection closedunexpectedly for the given reason.

System action: The FTP server continues execution.

User response: Use the specified reason to determinean appropriate action. If necessary, call the IBMSupport Center for assistance.


Procedure Name: CloseCompletedEvent

DTCFTS2515I SRVRFTP: timer expired on non-control connection

Explanation: A timer expired on a data connection.There should not be a timer associated with a dataconnection.




Severity: Error.

Procedure Name: TimerExpiredEvent

DTCFTS2519E FTP Server shutdown initiated.

Explanation: The ShutDownAndDie procedure issuesthis informational message.

System action: When an external interrupt is received,the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated.The variable ShuttingDown is set to true onceshutdown has been initiated. A delay may occur whilewaiting for connections to close. If a second external

FTP Messages

FTP Messages 19

interrupt is received while shutting down, the programterminates immediately.

User response: Correct the problem and resubmit thejob.


Severity: Error.

Procedure Name: ShutDownAndDie

DTCFTS2520E No connections open. Shutdownwill occur immediately.

Explanation: The ShutDownAndDie procedure sendsthis informational message when there are no openconnections.

System action: When an external interrupt is received,the procedure ShutDownAndDie is called. Allconnections are aborted and SRVRFTP terminated.The variable ShuttingDown is set to true onceshutdown has been initiated. A delay may occur whilewaiting for connections to close. If a second externalinterrupt is received while shutting down, the programterminates immediately.



Severity: Error.


DTCFTS2521E Number connections in use. Standby while the connections areaborted.

Explanation: The ShutDownAndDie procedure issuesthis informational message when there are openconnections. These open connections must beterminated before shutdown is complete.

System action: When an external interrupt is received,the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated.The variable ShuttingDown is set to true onceshutdown has been initiated. A delay can occur whilewaiting for connections to close. If a second externalinterrupt is received while shutting down, the programterminates immediately.

User response: Comply with the instructions that aredisplayed in later messages.


Severity: Error.


DTCFTS2522E Enter a second STOP command toshutdown immediately

Explanation: The ShutDownAndDie procedure issuesthis message when there are open connections. Youmust terminate these open connections beforeshutdown is complete.

System action: When an external interrupt is received,the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated.The variable ShuttingDown is set to true onceshutdown has been initiated. A delay can occur whilewaiting for connections to close. If a second externalinterrupt is received while shutting down, the programterminates immediately.

User response: To terminate the open connections,enter the STOP command.


Severity: Error.


DTCFTS2524E Currently shutting down; will shutdown immediately.

Explanation: The ShutDownAndDie procedure issuesthis informational message to inform you thatprocessing will halt momentarily.

System action: When an external interrupt is received,the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated.The variable ShuttingDown is set to true onceshutdown has been initiated. A delay may occur whilewaiting for connections to close. If a second externalinterrupt is received while shutting down, the programterminates immediately.



Severity: Error.


DTCFTS2582E List format format for User user inCHKIPADR is not valid

Explanation: The indicated type of list format is notvalid for the CHKIPADR exit. Valid list format types areVM and UNIX.


User response: Correct the CHKIPADR exit.


Severity: Error.

Procedure Name: VMIpAdrChk

DTCFTS2583E Format type not specified inLISTFORMAT command for Useruser in CHKIPADR

FTP Messages


Explanation: The LISTFORMAT statement requires atype of list format to be specified; valid list formattypes are VM and UNIX.




Severity: Error.


DTCFTS2589I FTPKEEPALIVE setting setting isnot valid

Explanation: The indicated setting is not valid for theFTP server SMSG FTPKEEPALIVE command. Validkeepalive mechanism settings are ON and OFF.


User response: Correct the FTP server SMSGFTPKEEPALIVE command.



Procedure Name: DoFTPkeepalive

DTCFTS2592E AUTOTRANS setting setting forUser user in CHKIPADR is not valid

Explanation: The indicated automatic translationsetting is not valid for the CHKIPADR exit. Validautomatic translation settings are ON and OFF.




Severity: Error.


DTCFTS2593E Setting not specified forAUTOTRANS command for Useruser in CHKIPADR

Explanation: The AUTOTRANS statement requires atype of automatic translation setting to be specified;valid automatic translation settings are ON and OFF.




Severity: Error.


DTCFTS2600I {LINES | TRANSLATE} value notspecified forVMFILETYPEDEFAULT statement

Explanation: An error exists in the TCPIP DATA file. Avalue was not specified for the indicated LINES orTRANSLATE parameter. This parameter has beenspecified as part of the VMFILETYPEDEFAULTstatement that defines default translationcharacteristics.

System action: None

User response: Review the TCPIP DATA file, andensure that an appropriate value is specified with theLINES or TRANSLATE parameter for the indicatedstatement. For detailed information about thisstatements, see z/VM: TCP/IP Planning andCustomization.


Severity: Error.

Procedure Name: ProcessParms

DTCFTS2601I {LINES | TRANSLATE} value notspecified for VMFILETYPEextension statement

Explanation: An error exists in the TCPIP DATA file. Avalue was not specified for the indicated LINES orTRANSLATE parameter. This parameter has beenspecified as part of the VMFILETYPE statement thatdefines translation characteristics for the indicated fileextension.

System action: None

User response: Review the TCPIP DATA file, andensure that an appropriate value is specified with theLINES or TRANSLATE parameter for the indicatedstatement. For detailed information about thesestatements, see z/VM: TCP/IP Planning andCustomization.


Severity: Error.


DTCFTS2602I {LINES | TRANSLATE} value valuefor VMFILETYPEDEFAULTstatement is not valid

Explanation: An error exists in the TCPIP DATA file.The indicated value is not supported for use with theLINES or TRANSLATE parameter. This parameter hasbeen specified as part of the VMFILETYPEDEFAULTstatement that defines default translationcharacteristics.


User response: Review the TCPIP DATA file, andensure that an appropriate value is specified with theLINES or TRANSLATE parameter for the indicatedstatement. For detailed information about these

FTP Messages

FTP Messages 21

statements, see z/VM: TCP/IP Planning andCustomization.


Severity: Error.


DTCFTS2603I {LINES | TRANSLATE} value valuefor VMFILETYPE extensionstatement is not valid

Explanation: An error exists in the TCPIP DATA file.The indicated value is not supported for use with theLINES or TRANSLATE parameter. This parameter hasbeen specified as part of the VMFILETYPE statementthat defines translation characteristics for theindicated file extension.


User response: Review the TCPIP DATA file, andensure that an appropriate value is specified with theLINES or TRANSLATE parameter for the indicatedstatement. For detailed information about thisstatement, see z/VM: TCP/IP Planning andCustomization.


Seve