z/VM V6.4 TCP/IP Messages and Codes · T able 1. Meanings of Severity Codes Severity Code Meaning I...

z/VM

TCP/IP Messages and CodesVersion 6 Release 4

GC24-6237-11

IBM

Note:Before you use this information and the product it supports, read the information in “Notices” on page 589.

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

This edition replaces GC24-6237-10.

© Copyright IBM Corporation 1987, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

About This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixIntended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixConventions and Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Locating Messages in This Document . . . . . . . . . . . . . . . . . . . . . . . . . . ixUnderstanding Message Text Format . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow the Term “internet” is Used in This Document . . . . . . . . . . . . . . . . . . . . . xi

Where to Find More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiLinks to Other Documents and Websites . . . . . . . . . . . . . . . . . . . . . . . . xii

How to Send Your Comments to IBM . . . . . . . . . . . . . . . . . . . . . . xiii

Summary of Changes for z/VM TCP/IP Messages and Codes . . . . . . . . . . . . xvGC24-6237-11, z/VM Version 6 Release 4 (December 2017) . . . . . . . . . . . . . . . . . . . xvGC24-6237-10, z/VM Version 6 Release 4 (August 2017) . . . . . . . . . . . . . . . . . . . . xv

Firewall Friendly FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvGC24-6237-09, z/VM Version 6 Release 4 (March 2017) . . . . . . . . . . . . . . . . . . . . xviGC24-6237-08, z/VM Version 6 Release 4 . . . . . . . . . . . . . . . . . . . . . . . . . xvi

z/VM LDAP Server and Utilities z/OS V2.2 Equivalency . . . . . . . . . . . . . . . . . . . xviz/VM MPROUTE Server z/OS V2.2 Equivalency . . . . . . . . . . . . . . . . . . . . . xvizManager Support Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiDomain Name System (DNS) IPv6 Support . . . . . . . . . . . . . . . . . . . . . . . xvii

GC24-6237-07, z/VM Version 6 Release 3 (September 2015) . . . . . . . . . . . . . . . . . . . xviiGC24-6237-06, z/VM Version 6 Release 3 (May 2015) . . . . . . . . . . . . . . . . . . . . . xvii

Multi-VSwitch Link Aggregation Support . . . . . . . . . . . . . . . . . . . . . . . . xviiGC24-6237-05, z/VM Version 6 Release 3 (June 2014) . . . . . . . . . . . . . . . . . . . . . xviii

MODE Support for the SSL Server . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiGC24-6237-04, z/VM Version 6 Release 3 . . . . . . . . . . . . . . . . . . . . . . . . . xviii

IPv6 Support for SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiRemoval of A220, CLAW, DHCP and LPD Support . . . . . . . . . . . . . . . . . . . . xviiiTLS 1.2 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiiOther Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

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

Chapter 2. FTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9FTP Server Numbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9FTP Server Unnumbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 32FTP Client Numbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36FTP Client Unnumbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 44FTP Reply Code Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 3. GDDMXD/VM Messages and Codes. . . . . . . . . . . . . . . . . . . 79GDDMXD/VM Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79ABEND Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Chapter 4. IMAP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 5. LDAP Server Messages. . . . . . . . . . . . . . . . . . . . . . . . 97LDAP Server Messages (1000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Utility Messages (2000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162TDBM Messages (3000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

© Copyright IBM Corp. 1987, 2017 iii

LDBM Messages (6000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175GDBM and Advanced Replication Messages (8000) . . . . . . . . . . . . . . . . . . . . . . 189

GDDM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Advanced replication messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

ICTX Plug-in Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Return and reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Chapter 6. MPROUTE Messages . . . . . . . . . . . . . . . . . . . . . . . . 249

Chapter 7. NETSTAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . 299

Chapter 8. NFS Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Numbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307SIGERROR Error Strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

Chapter 9. PING Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 337

Chapter 10. PORTMAP Messages . . . . . . . . . . . . . . . . . . . . . . . . 341

Chapter 11. Remote Printing Messages . . . . . . . . . . . . . . . . . . . . . 343LPQ Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343LPR and LPRSET Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344LPRM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Chapter 12. Remote Procedure Call Messages . . . . . . . . . . . . . . . . . . 355RPC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355RPCINFO Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360RPCGEN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

Chapter 13. REXEC and REXECD Messages . . . . . . . . . . . . . . . . . . . 365REXEC Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365REXECD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Chapter 14. Site Table Configuration Messages. . . . . . . . . . . . . . . . . . 373TESTSITE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373MAKESITE Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Chapter 15. SMTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 377SMTP Server Numbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 377SMTP Server Unnumbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 400SMTP Reply Code Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402SMTPRSCS Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

Chapter 16. SNMP Messages. . . . . . . . . . . . . . . . . . . . . . . . . . 417SNMPD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417SNMPLIB Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421SNMPTRAP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426SQESERV Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Chapter 17. SSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 433SSL Server Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433SSLADMIN and VMSSL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

Chapter 18. TCP/IP Server Messages . . . . . . . . . . . . . . . . . . . . . . 451Unnumbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

iv z/VM V6.4 TCP/IP Messages and Codes

Numbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451

Chapter 19. TCP/IP Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . 529CONVXLAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529FTPPERM and NFSPERM Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 532HOMETEST Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532IFCONFIG Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533IPFORMAT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541IPWIZARD Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543MIGVMTCP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545OBEYFILE Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552

OBEYFILE Numbered Message . . . . . . . . . . . . . . . . . . . . . . . . . . . 552OBEYFILE Unnumbered Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 553

SSLPOOL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553TCPMSMGR Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554TCPRUN Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557TCPSLVL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565Common TCP/IP Utility Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

Chapter 20. TFTP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 571

Chapter 21. TRACERTE Messages . . . . . . . . . . . . . . . . . . . . . . . 575

Chapter 22. UFTD Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Chapter 23. Miscellaneous Messages . . . . . . . . . . . . . . . . . . . . . . 581Common Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581COMMTXT Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591Terms and Conditions for Product Documentation . . . . . . . . . . . . . . . . . . . . . . 591IBM Online Privacy Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Bibliography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595Where to Get z/VM Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595z/VM Base Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595z/VM Facilities and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596Prerequisite Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597Other TCP/IP Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

Contents v

vi z/VM V6.4 TCP/IP Messages and Codes

Tables

1. Meanings of Severity Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi2. Meanings of message type (action) codes . . . . . . . . . . . . . . . . . . . . . . . . xi3. LDAP server return codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2264. Subcode X'30' Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

© Copyright IBM Corp. 1987, 2017 vii

viii z/VM V6.4 TCP/IP Messages and Codes

About This Document

This document provides information about the messages and codes that occur inthe IBM® TCP/IP for z/VM® level 640 networks. This document can also help youto determine whether a specific problem is a result of the VM TCP/IPimplementation.

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

This document also includes an appendix and a bibliography.

Intended AudienceThis document is intended for use by system programmers for diagnosingproblems. You should use this document 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 thisdocument.

Before using this document, you should be familiar with z/VM, CP, and CMS. Inaddition, TCP/IP level 640 should already be installed and customized for yournetwork.

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

Locating Messages in This DocumentThis document is organized by chapter and then by function within each chapter.Messages associated with each function are sorted either alphabetically or bymessage number. If the message you are looking for 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 thefunctional section does not. In this case, do not use the message numberfor searching; search for the message alphabetically.

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

Message Conventions Used in This DocumentThe following message conventions are used throughout this document:v Uppercase letters represent values that you must type without change (these

values are not case-sensitive).v Lowercase letters represent values that must be entered in lowercase (these

values are case-sensitive).v Lowercase italicized letters represent variable parameters for which you supply

the values.

© Copyright IBM Corp. 1987, 2017 ix

v Square brackets [ ] enclose optional or conditional values.Optional values can be omitted; when certain values are omitted, default valuesare used.Conditional values can be omitted, depending on the statement.

v Braces { } enclose values from which you must choose a value.v Vertical line symbols | indicate that you must select a value from either side of

the symbol.

How Numbers Are Used in This DocumentThe following describes how numbers are used in this document:v Numbers over four digits are represented in metric style. A space is used rather

than a comma to separate groups of three digits.For example, the number sixteen thousand, one hundred forty-seven is written16 147.

v Periods in numbers separate the whole and the fractional portions of thenumeral.

v Some messages in this document have message numbers that contain acomponent ID in the message number. For example, in the messageDTCIMP1065, the IMP indicates that it is the IMAP component that issued themessage.

TCP/IP Message FormatSome messages in this document consist of a message identifier (for example,DTCCLW110E) and message text. The identifier distinguishes messages from eachother. The text is a phrase or sentence describing a condition that has occurred orrequesting 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 themessage. This field is usually an abbreviation of the name of the module inwhich the error occurred.

### or ####The numeric message number consists of three or four digits that areassociated with the condition that caused the message to be generated.

e The one digit severity code is a letter that indicates what kind of conditioncaused the message. The definition of the severity codes depends on thenature of the routine producing the message.

Table 1 on page xi lists the severity codes and their meaning for the TCP/IPmessages.

x z/VM V6.4 TCP/IP Messages and Codes

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

MPRoute and LDAP Server Message FormatThe format of some MPRoute and LDAP server messages differs from that of theTCP/IP messages. The following 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 their meanings 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 bygateways, routers, bridges, hosts, and various layers of protocols, which permit thenetwork to function as a large, virtual network.

Note: The term “internet” is used as a generic term for a TCP/IP network, andshould not be confused with the Internet, which consists of large national

About This Document xi

backbone networks (such as MILNET, NFSNet, and CREN) and a myriadof regional and local campus networks worldwide.

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

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

xii z/VM V6.4 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, and completeness of the information or give us any other feedback thatyou might have.

Use one of the following methods to send us your comments:1. Send an email to [email protected]. Go to IBM z/VM Reader's Comments (www.ibm.com/systems/z/os/zvm/

zvmforms/webqs.html).

Include the following information:v Your namev Your email addressv The publication title and number:

z/VM V6.4 TCP/IP Messages and CodesGC24-6237-11

v The topic name or page number related to your commentv The text of your comment

When you send comments to IBM, you grant IBM a nonexclusive right to use ordistribute your comments in any way it believes appropriate without incurring anyobligation to you.

IBM or any other organizations will use the personal information that you supplyonly to contact you about the issues that you submit to IBM.

If You Have a Technical Problem

Do not use the feedback methods listed above. Instead, do one of the following:v Contact your IBM service representative.v Contact IBM technical support.v See IBM: z/VM Service Resources (www.ibm.com/vm/service/).v Go to IBM Support Portal (www.ibm.com/support/entry/portal/Overview/).

© Copyright IBM Corp. 1987, 2017 xiii

http://www.ibm.com/systems/z/os/zvm/zvmforms/webqs.htmlhttp://www.ibm.com/vm/service/http://www.ibm.com/support/entry/portal/Overview/

xiv z/VM V6.4 TCP/IP Messages and Codes

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

This document contains terminology, maintenance, and editorial changes. Technicalchanges are indicated by a vertical line to the left of the change. Some productchanges might be provided through service and also might be available for someprior releases.

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

APAR PI83256 adds the following message:v DTCSSL507E (see “SSL Server Messages” on page 433)

The following message has been updated:v DTCOSD045E (see Chapter 18, “TCP/IP Server Messages,” on page 451)

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

The following message has been updated:v 1046 (see “TCPRUN Messages” on page 557)

The following messages have been removed from Chapter 18, “TCP/IP ServerMessages,” on page 451:v DTCPRS068Ev DTCPRS069Iv DTCPRS080E

Firewall Friendly FTPWith the PTF for APAR PI80912, the purpose of the Firewall Friendly FTP is toconfigure the FTP client to determine the party initially responsible for initiatingdata connections, improve compliance with RFC 2428, and reflect theactive/passive FTP mode and the EPSV4 setting.

The following message has been added in “FTP Client Unnumbered Messages” onpage 44:v FWFRIENDLY value value is not valid. Default value used.

The following messages have been updated in “FTP Client UnnumberedMessages” on page 44:v PORT command failed; code replyv Usage of PORT command is OFFv Usage of PORT command is ON

© Copyright IBM Corp. 1987, 2017 xv

GC24-6237-09, z/VM Version 6 Release 4 (March 2017)This edition includes changes to support product changes provided or announcedafter the general availability 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:

GLD1299I GLD1338E GLD9202AGLD1300E GLD1340E GLD9203AGLD1301E GLD8507E GLD9204EGLD1302E GLD8508E GLD9205AGLD1310W GLD8509E GLD9206AGLD1311E GLD8511I GLD9207AGLD1313E GLD8512IGLD1337E GLD9201A

The following messages have been changed for this support:

GLD1070EGLD2401E

The following messages have been removed.

ITY6595EITY6596AITY6597AITY6598A

The following reason codes have been added for this support.

R001108 R004208 R010070R001109 R004209 R010071R004203 R004210 R010072R004204 R006057 R010073R004205 R006058 R010074R004206 R010068R004207 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

xvi z/VM V6.4 TCP/IP Messages and Codes

The following messages have been changed for this support:

EZZ7900I EZZ7923I EZZ7948IEZZ7901I EZZ7924I EZZ7952IEZZ7902I EZZ7925I EZZ7953IEZZ7906I EZZ7940I EZZ7955IEZZ7922I EZZ7946I

zManager Support RemovedThe IBM z® Unified Resource Manager (zManager) is no longer supported inz/VM V6.3. The vswitch types of IEDN and INMN have been removed fromdocumentation.

The following messages have been updated for this support:DTCOSD438EDTCOSD439EDTCOSD441E

The following messages have been deleted for this support:

DTCIPI060E DTCIPI064E DTCIPU241IDTCIPI061E DTCIPI065I DTCPAR236IDTCIPI062E DTCIPI067I DTCPAR237IDTCIPI063E DTCIUI066I DTCOSD432E

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

The following message has been added for this support:NSINTERADDR

GC24-6237-07, z/VM Version 6 Release 3 (September 2015)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

GC24-6237-06, z/VM Version 6 Release 3 (May 2015)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

Multi-VSwitch Link Aggregation SupportThe Multi-VSwitch Link Aggregation support provides the ability for a port groupof OSA-Express adapters to span multiple virtual switches within a single host oramong multiple systems running z/VM. Sharing a Link Aggregation Port Group(LAG) with multiple virtual switches increases optimization and use of theOSA-Express adapter when handling larger traffic loads.

The following messages have been added for this support:v DTCOSD205Ev DTCOSD206Ev DTCOSD451I

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

The following messages have been updated for this support:v DTCOSD230Ev DTCOSD406E

GC24-6237-05, z/VM Version 6 Release 3 (June 2014)This edition includes changes to support product changes provided or announcedafter the general availability of z/VM V6.3.

MODE Support for the SSL ServerThe z/VM SSL Server has been upgraded to enforce configurations which meetspecific cryptographic standards. This includes continued support for FIPS 140-2compliance as well as support for NIST SP 800-131A configurations.

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

IPv6 Support for SSLThe SSL server has been enhanced to support secure IPv6 SSL connections. Thefollowing servers and clients have added support for secure IPv6 connections:v TELNET server and clientv FTP server and clientv SMTP server

Furthermore, NETSTAT IDENT SSL and SSLADMIN have been enhanced todisplay secure IPv6 connections.

Removal of A220, CLAW, DHCP and LPD SupportThe removal of unsupported TCP/IP device drivers and servers is part of anongoing effort to provide only those TCP/IP services that are required bycustomers to support their enterprise.

TLS 1.2 SupportThe z/VM SSL Server has been upgraded to exploit V1.13 System SSL, whichfeatures Transport Layer Security version 1.2. This expands the cipher suites whichcan be used by the SSL server and provides increased security. Additionally,support for an SSL configuration PROTOCOL operand is added, which allows anadministrator to enable or disable versions of the SSL and TLS protocols.

Other ChangesMost of the new and changed messages, codes, and related text in this book arethe result of the following z/VM V6.3 functions, commands and routines that havebeen added or enhanced (this list is in alphabetical order and not all inclusive):v MPROUTE enhancements and z/OS 1.13 equivalency

xviii z/VM V6.4 TCP/IP Messages and Codes

Chapter 1. Domain Name System Resolver Messages

This chapter contains messages issued by the CMSRESOL utility.

Most of these messages include the subroutine that is active when the message isissued. Since the same message can be issued by multiple subroutines, that portionof the message cannot be used to index the message. In the message descriptions,the subroutine name is referred to as RoutineName. In general, the messages arelisted alphabetically without respect to case in the first words of the message thatare not substituted during message generation.

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.

DATAGRAM|CONN & timeout args missing

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.

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.

Incomplete entry list

Explanation: A CMSRESOL command line containedan incorrect number of entries. See z/VM: TCP/IP User'sGuide for the syntax of the CMSRESOL command.


User response: Use the correct syntax on thecommand line.

Severity: Error.

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.

Invalid arg arg

Explanation: A CMSRESOL command line containedan invalid connection method argument. Validarguments are:v CONNv DATAGRAM

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



Severity: Error.

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.

© Copyright IBM Corp. 1987, 2017 1

Invalid name server address 'IPaddress'

Explanation: A CMSRESOL command line contained aname server address that is not valid. See z/VM: TCP/IPUser'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.

Invalid opcode 'value'

Explanation: An invalid opcode was specified in aCMSRESOL command. Valid opcode values are:v CQUERYMv CQUERYUv IQUERYv QUERY



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

Severity: Error.

Invalid qclass 'value'

Explanation: An invalid qclass was specified in aCMSRESOL command. Valid qclass values are:v *v CSv IN



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

Severity: Warning.

Invalid qtype 'value'

Explanation: An invalid qtype was specified in aCMSRESOL command. Valid qtype values are:

*AAXFRCNAMEHINFOLOC97MBMDMFMGMILA

MILBMINFOMRMXNSNULLPTRSOATXTWKS



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

Severity: Error.

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.

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.

Resolver error calling routine rtnname by functname:Return code 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 error messageand the command that was issued in order to helpdiagnose the problem.

Invalid name server address • Resolver error calling routine

2 z/VM V6.4 TCP/IP Messages and Codes

Resolver error calling routine rtnname by functname:Routine not 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 sure itis loaded and try the command again.

- RoutineName: Active open successful onconnection 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.

- RoutineName: Address conversion failedfor '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.



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


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




- RoutineName: Can't send tcp reply oninactive 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.




- RoutineName: Connection connNumclosed normally

Explanation: The specified connection closed whenexpected. The message is only issued during diagnostictracing.

System action: None.



- RoutineName: Connection:connNum Foreign Address: IPaddress

Explanation: This message usually follows anothermessage. It provides the connection number and the IPaddress 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.




- - 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- RoutineName: Last urgent byte: value- RoutineName: Bytes to read: byteCount

Resolver error calling routine • -

Chapter 1. Domain Name System Resolver Messages 3

- 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 of notificationthat is received. The messages are displayed because anerror just occurred with this notification, or diagnostictracing is active.




- RoutineName: connType connection neveropened

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.

- 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 is active.




- RoutineName: Data never delivered onconnNum 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.

- RoutineName: DATAdelivered error, 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.

- RoutineName: Datagram reply truncated

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.

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

- RoutineName: Displaying storage at addrfor dLen ('hLen'x) bytesmemoryAddress hWord hWord hWordhWord *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 message willbe repeated as many times as necessary to display allthe data.


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


- RoutineName: Error returnCode beginningTCP/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 service

-


machine is not operational. The ReturnCode can be usedto 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.

- RoutineName: Error returnCode fromcalledRoutine

Explanation: The calledRoutine encountered an errorand returned with a nonzero returnCode. Othermessages may give more details about the nature of thespecific error. The error is probably the result of invaliddata being sent to the program from another system.The current question or transaction will not completesuccessfully, but the program should continueoperation and process other questions and transactionswithout any problems.

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


Severity: Error.

- RoutineName: Error in TCPIPservice: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.

- RoutineName: Error opening connectionto 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 senda 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.

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



- RoutineName: Insufficient data available

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.

- 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 server administratorof that system.

Severity: Error.

- RoutineName: name='name', type=type,class=class

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




- RoutineName: pointer is NULL

Explanation: This message may be seen duringdiagnostic tracing when certain control blocks are beingdisplayed. It means that the control block does not existand the pointer to it is not defined.


-




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




- RoutineName: Request for storage of sizebytesOfStorage

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




- RoutineName: Received bad packet fromIPaddress

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 by contactingthe owner of the host that is sending the bad packets.Traces can also dump the inbound packets so thecontent of these packets can be examined.


- RoutineName: Response from unexpectedaddress fromAddress, expectedexpectedAddress

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

not returned by a name server and was intended tocause problems for your name server. If this messageoccurs frequently, it may be prudent to investigate theiroccurrence.



Severity: Warning.

- RoutineName: Results from TcpStatus

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




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

- RoutineName: Timer expired for inactiveconnection

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

System action: The notification is ignored.


Severity: Warning.

- RoutineName: ttl=value rdata='value'

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




- RoutineName: Unexpected notificationnotificationID

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.


- RoutineName: Unexpected query typequeryType

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.

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.

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.

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.

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.

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.

- • Undefined state


System Resolver Messages


Chapter 2. FTP Messages

This chapter contains File Transfer Protocol (FTP) messages.

FTP Server Numbered MessagesThis section contains the numbered 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 not valid

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

© Copyright IBM Corp. 1987, 2017 9

Explanation: The listed statement is not a supportedFTP server configuration file statement. For informationabout statements and operands that can be specified forconfiguring the FTP server, see z/VM: TCP/IP Planningand 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 informational

message(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: Initialization completedDateTime

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 specified interruption_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.


DTCFTS0014I • DTCFTS0033E


DTCFTS0034E FRECEIVEerror note on #conn shows:reason

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


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 command code 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 management consolemachine in part by issuing an internal CP diagnose. CPissues an FTP services external interruption when theassociated HMC FTP services function is complete.

System action: FTP server execution continues.

User response: See message DTCFTS3006I to

determine the FTP services function and return codeassociated with the external interruption.




DTCFTS0100E Error: SECUREhandshakeCOMPLETEfor connection conn with secure status ofstatus.

Explanation: A software error exists in the FTP server.A SECUREhandshakeCOMPLETE event was receivedfor the specified connection, but the secure status of theconnection was the given status instead of the expectedstatus of TLSsecure for data connections andHANDSHAKING for control connections. Thefollowing status 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 the SecureSockets Layer. For an explanation of these return codes,see the section titled “SSL Function Return Codes” inz/OS Cryptographic Service System Secure Sockets LayerProgramming. Negative return codes indicate theproblem was detected by the TCP/IP stack.


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


Severity: Error.


DTCFTS0105E Unexpected notification_typenotification received on connection conn,ignoring.

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

DTCFTS0034E • DTCFTS0105E

Chapter 2. FTP Messages 11




Severity: Error.


DTCFTS0260I Using Kanji translate table FileNameFileType

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 the Kanjitranslation 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 not

contain 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 book for more information about loadingand customizing 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 book for more information about loadingand customizing 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 book for more information about loadingand customizing DBCS translation tables.


DTCFTS0260I • DTCFTS0267I


Severity: Error.


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

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.




Severity: Error.


DTCFTS0314E Translate table not specified forLOADDBCSTABLE statement

Explanation: The LOADDBCSTABLE statementrequires a valid table name to be specified. For detailedinformation about the LOADDBCSTABLE statement seez/VM: TCP/IP Planning and Customization.




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

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 withread/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 anonzero return code and was unable to obtain asecurity token for ESM calls.

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 missing classD privileges for virtual reader support

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 or deletevirtual reader files, the FTP server must be given classD 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 is notvalid

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 has beenconfigured for a user in the CHKIPADR exit or the listformat has been changed for a session using the FTPSITE subcommand.






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-settingis not valid

Explanation: The indicated type of TIMESTAMPsetting is not valid for the TIMESTAMP statement.Valid TIMESTAMP 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 setting isnot 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 PASSIVEPORTRANGE statementis 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 PASSIVEPORTRANGE statementis used.




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 wasnot specified on the SECURECONTROL statement inthe FTP server configuration file. The minimumsecurity level (ALLOWED, REQUIRED, or NEVER)must be specified when the SECURECONTROLstatement is used.




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 wasnot specified on the SECUREDATA statement in theFTP server configuration file. The minimum securitylevel (ALLOWED , REQUIRED, orNEVER) must bespecified when 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.

DTCFS0403E • DTCFTS0409E





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.




Severity: Error.


DTCFTS0411E TLSLABEL must be 1 to 8 charactersin length.

Explanation: The TLS label specified on theTLSLABEL statement in the FTP server configurationfile is not valid. The label must be 1 to 8 characters inlength.




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 Configuring theFTP 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 connection level islevel.

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 ALLOWEDor SECUREDATA REQUIRED statement. This is notallowed. In order to secure data connections, the FTPcontrol connection must already be secure.




User response: If secure data connections are desired,correct the SECURECONTROL statement in the FTPserver configuration file and restart the FTP server.Otherwise, correct the SECUREDATA statement andrestart 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.


Severity: Error.


DTCFTS0422E FTPKEEPALIVE setting setting is notvalid

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/IPserver's keepalive mechanism to avoid timing out idlecontrol connections.






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

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

Syste

Date post:	25-Dec-2019
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times