z/VM: TCP/IP Messages and Codes · Preface z/VM: TCP/IP Level 430 Messages and Codes is intended to...

z/VM™

TCP/IP Level 430Messages and CodesVersion 4 Release 3.0

GC24-6022-02

��

Note:Before using this information and the product it supports, read the information under “Notices” on page 415.

Third Edition (December 2002)

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

This edition replaces GC24–6022–01.

© Copyright International Business Machines Corporation 1987, 2002. All rights reserved.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

|

||

|

Contents

Preface . . . . . . . . . . . . . . . vWho Should Read This Book . . . . . . . . . vWhat You Should Know before Reading This Book . vWhat This Book Contains . . . . . . . . . . v

Locating Messages in This Book . . . . . . . vHow To Use This Book . . . . . . . . . . . v

How the Term “internet” is Used in This Book. . viWhere to Find More Information . . . . . . . vi

Links to Other Books . . . . . . . . . . viHow to Send Your Comments to IBM. . . . . . viUnderstanding Message Text Format . . . . . . vi

Message Conventions Used in This Book . . . viiHow Numbers Are Used in This Book . . . . . viiTCP/IP Message Format . . . . . . . . . . vii

Summary of Changes . . . . . . . . ixThird Edition for z/VM Version 4 (December 2002) ixSecond Edition for z/VM Version 4 (May 2002) . . ixFirst Edition for z/VM Version 4 (October 2001) . . ixFirst Edition for z/VM Version 3 (February 2001) . . x

Chapter 1. BOOTPD and DHCPDMessages . . . . . . . . . . . . . . 1

Chapter 2. Domain Name Server andResolver Messages . . . . . . . . . 15

Chapter 3. FTP Messages. . . . . . . 33FTP Server Numbered Messages . . . . . . . 33FTP Server Unnumbered Messages . . . . . . 48FTP Client Numbered Messages . . . . . . . 50FTP Client Unnumbered Messages . . . . . . 58FTP Reply Code Messages . . . . . . . . . 63

Chapter 4. GDDMXD/VM Messages andCodes . . . . . . . . . . . . . . . 83GDDMXD/VM Messages. . . . . . . . . . 83ABEND Codes . . . . . . . . . . . . . 83

Chapter 5. IMAP Messages . . . . . . 85

Chapter 6. MPROUTE Messages . . . . 99

Chapter 7. NETSTAT Messages . . . . 119

Chapter 8. NFS Messages . . . . . . 125Numbered Messages . . . . . . . . . . . 125SIGERROR Error Strings . . . . . . . . . 145

Chapter 9. PING Messages . . . . . 155

Chapter 10. PORTMAP Messages . . . 159

Chapter 11. Remote PrintingMessages . . . . . . . . . . . . . 161LPD Messages . . . . . . . . . . . . . 161LPQ Messages . . . . . . . . . . . . . 168LPR and LPRSET Messages . . . . . . . . 170LPRM Messages . . . . . . . . . . . . 178

Chapter 12. Remote Procedure CallMessages . . . . . . . . . . . . . 181RPC Messages . . . . . . . . . . . . . 181RPCINFO Messages . . . . . . . . . . . 186RPCGEN Messages . . . . . . . . . . . 188

Chapter 13. REXEC and REXECDMessages . . . . . . . . . . . . . 191REXEC Messages . . . . . . . . . . . . 191REXECD Messages . . . . . . . . . . . 193

Chapter 14. ROUTED Messages . . . 199

Chapter 15. Site Table ConfigurationMessages . . . . . . . . . . . . . 219TESTSITE Messages . . . . . . . . . . . 219MAKESITE Messages. . . . . . . . . . . 219

Chapter 16. SMTP Messages . . . . . 223SMTP Server Numbered Messages . . . . . . 223SMTP Server Unnumbered Messages . . . . . 241SMTP Reply Code Messages . . . . . . . . 243SMTPRSCS Messages. . . . . . . . . . . 253

Chapter 17. SNALINK Messages . . . 257

Chapter 18. SNMP Messages. . . . . 265SNMPD Messages . . . . . . . . . . . . 265SNMPLIB Messages . . . . . . . . . . . 269SQESERV Messages . . . . . . . . . . . 274

Chapter 19. SSL Messages . . . . . 279SSL Server Return Codes . . . . . . . . . 291SSL Server Reason Codes . . . . . . . . . 291

Chapter 20. TCP/IP Server Messages 295Unnumbered Messages . . . . . . . . . . 295Numbered Messages . . . . . . . . . . . 295

Chapter 21. TCP/IP Utilities . . . . . 359CONVXLAT Messages . . . . . . . . . . 359FTPPERM and NFSPERM Messages . . . . . . 361HOMETEST Messages . . . . . . . . . . 362IFCONFIG Messages . . . . . . . . . . . 363IPWIZARD Messages. . . . . . . . . . . 369

© Copyright IBM Corp. 1987, 2002 iii

||

||

||

||||

||||

||

||||

OBEYFILE Messages . . . . . . . . . . . 371TCPRUN Messages . . . . . . . . . . . 371

Chapter 22. TFTP Messages . . . . . 377

Chapter 23. TFTPD Messages . . . . 381

Chapter 24. UFTD Messages . . . . . 383

Chapter 25. X.25 Messages . . . . . 387

Chapter 26. Miscellaneous Messages 409Common Messages . . . . . . . . . . . 409COMMTXT Messages . . . . . . . . . . 409

Notices . . . . . . . . . . . . . . 415Trademarks . . . . . . . . . . . . . . 417

Bibliography. . . . . . . . . . . . 419z/VM Internet Library . . . . . . . . . . 419VM Collection CD-ROM. . . . . . . . . . 419

z/VM Base Publications . . . . . . . . . . 419Evaluation . . . . . . . . . . . . . 419Installation and Service . . . . . . . . . 419Planning and Administration . . . . . . . 419Customization . . . . . . . . . . . . 419Operation . . . . . . . . . . . . . 419Application Programming . . . . . . . . 419End Use . . . . . . . . . . . . . . 420Diagnosis. . . . . . . . . . . . . . 420

Publications for z/VM Additional Facilities . . . 420DFSMS/VM® . . . . . . . . . . . . 420Language Environment® . . . . . . . . 420OSA/SF . . . . . . . . . . . . . . 420TCP/IP for z/VM . . . . . . . . . . . 421

Publications for z/VM Optional Features . . . . 421DirMaint™ . . . . . . . . . . . . . 421PRF . . . . . . . . . . . . . . . 421RTM . . . . . . . . . . . . . . . 421RACF® for VM . . . . . . . . . . . . 421

Other TCP/IP Related Publications . . . . . . 421

Index . . . . . . . . . . . . . . . 423

iv z/VM: TCP/IP Messages and Codes

Preface

z/VM: TCP/IP Level 430 Messages and Codes is intended to provide informationabout the messages and codes that occur in the TCP/IP Level 430 networks. Thisbook can also help you to determine whether a specific problem is a result of theVM TCP/IP implementation.

For comments and suggestions about z/VM: TCP/IP Level 430 Messages and Codes,use the Readers’ Comment Form located at the back of this book. This formprovides instructions on submitting your comments by mail, FAX, or electronicmail.

Who Should Read This BookThis book is intended for use by system programmers for diagnosing problems.You should use this book 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 book.

What You Should Know before Reading This BookBefore using this book, you should be familiar with z/VM, CP, and CMS. Inaddition, TCP/IP Level 430 should already be installed and customized for yournetwork.

What This Book ContainsThis book lists, by category, messages and codes for IBM TCP/IP Level 430.

This book also includes an appendix and a bibliography.

Locating Messages in This BookThis book 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.

How To Use This BookYou should read this book when you want to know the meaning of messages andcodes that you receive when operating in TCP/IP networks.

© Copyright IBM Corp. 1987, 2002 v

How the Term “internet” is Used in This BookIn this book, an internet is a logical collection of networks supported by gateways,routers, bridges, hosts, and various layers of protocols, which permit the networkto 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 nationalbackbone 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 419.

Links to Other BooksThe PDF version of this book provides links to other IBM books by file name. Thename of the PDF file for an IBM book is unique and identifies the book and itsedition. The book links provided in this book are for the editions (PDF file names)that were current when this PDF file was generated. Newer editions of some books(with different file names) may exist. A PDF link from this book to another bookworks only when a PDF file with the requested file name resides in the samedirectory as this book.

How to Send Your Comments to IBMYour feedback is important in helping us to provide the most accurate andhigh-quality information. If you have comments about this book or any other VMdocumentation, send your comments to us using one of the following methods. Besure to include the name of the book, the publication number (including thesuffix), and the page, section title, or topic you are commenting on.v Visit the z/VM web site at:

http://www.ibm.com/eserver/zseries/zvm/

There you will find the feedback page where you can enter and submit yourcomments.

v Send your comments by electronic mail to one of the following addresses:

Internet: [email protected]

IBMLink™: GDLVME(PUBRCF)v Fill out the Readers’ Comments form at the back of this book and return it by

mail, by fax (1–607–752–2327), or by giving it to an IBM representative. If theform is missing, you can mail your comments to the following address:

IBM CorporationInformation DevelopmentDepartment G60G1701 North StreetEndicott, New York 13760-5553USA

Understanding Message Text FormatThis section describes general concepts needed to define and configure the virtualmachines, servers, and applications in TCP/IP.

vi z/VM: TCP/IP Messages and Codes

|

|||||||

http://www.ibm.com/eserver/zseries/zvm/

Message Conventions Used in This BookThe following message conventions are used throughout this book:

Uppercase letters represent values that you must type without change (thesevalues are not case-sensitive).Lowercase letters represent values that must be entered in lowercase (thesevalues are case-sensitive).Lowercase italicized letters represent variable parameters for which you supplythe values.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.Braces { } enclose values from which you must choose a value.Vertical line symbols | indicate that you must select a value from either side ofthe symbol.

How Numbers Are Used in This BookThe following describes how numbers are used in this book: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 book have message numbers that contain a component IDin the message number. For example, in the message DTCIMP1065, the IMPindicates that it is the IMAP component that issued the message.

TCP/IP Message FormatSome messages in this book 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 themodule in which the error occurred.

### or #### The numeric message number consists of three or four digits thatare associated with the condition that caused the message to begenerated.

Preface vii

e The one digit severity code is a letter that indicates what kind ofcondition caused the message. The definition of the severity codesdepends on the nature of the routine producing the message.

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

Table 1. Meanings of Severity Codes

SeverityCode Meaning

IWESRT

Information onlyWarningErrorSevere errorCommand responseTermination message

viii z/VM: TCP/IP Messages and Codes

Summary of Changes

This section describes the technical changes made in this edition of the book and inprevious editions. For your convenience, the changes made in this edition areidentified in the text by a vertical bar (|) in the left margin. This edition may alsoinclude minor corrections and editorial changes that are not identified.

Third Edition for z/VM Version 4 (December 2002)This edition enables the manual for the LookAt message facility.

Second Edition for z/VM Version 4 (May 2002)This edition contains updates for the General Availability of TCP/IP Level 430.

New messages have been added to the listed chapters for support of the following:v HiperSockets enhancements and Stack Performance - Chapter 20, “TCP/IP

Server Messages”v IFCONFIG command — IFCONFIG Messagesv IPWIZARD command - IPWIZARD Messagesv Stack vulnerability reduction - Chapter 7, “NETSTAT Messages”

Four digit message prefixes have been added to the Chapter 3, “FTP Messages”along with reworked message descriptions. Messages have also been separated intoclient vs. server type.

Four digit message prefixes have been added to the Chapter 16, “SMTP Messages”.An unnumbered message section, as well as additional reply code messages havebeen added.

Four digit message prefixes have been added to the Chapter 7, “NETSTATMessages” along with new messages and explanations.

First Edition for z/VM Version 4 (October 2001)This edition contains updates for the General Availability of TCP/IP Level 420.

New messages have been added to the listed chapters for support of the following:v IMAP -new chapter Chapter 5, “IMAP Messages”v HiperSockets - Chapter 20, “TCP/IP Server Messages”

Message DTCIPU086I was added in support of preventing some Denial of Service(DOS) attacks.

© Copyright IBM Corp. 1987, 2002 ix

|

|

|

||

|

|

|

|||

|||

||

First Edition for z/VM Version 3 (February 2001)This edition contains updates for the General Availability of z/VM 3.1.0.

New messages have been added to the listed chapters for support of the following:v IP Multicasting - Chapter 20, “TCP/IP Server Messages”v FTP Web Browser - Chapter 3, “FTP Messages”v Queued Direct I/I (QDIO) - Chapter 20, “TCP/IP Server Messages”v MPROUTE - new Chapter 6, “MPROUTE Messages”v Secure Socket Layer (SSL) - Chapter 20, “TCP/IP Server Messages” and new

Chapter 19, “SSL Messages”

This edition also contains minor editorial and technical changes, along withmiscellaneous service APAR changes.

x z/VM: TCP/IP Messages and Codes

Chapter 1. BOOTPD and DHCPD Messages

This chapter contains BOOTPD and DHCPD messages. Follow the User Response,as appropriate, within each message area to resolve the problem.

TCP0001E Machine File was not specified

Explanation: The machine file was not specified.

System Action: Execution of the command orsubcommand terminated.

User or Operator Response: Reissue the command orsubcommand with the machine file specified.

Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHC

TCP0001E Configuration File was not specified

Explanation: The configuration file was not specified.

System Action: Execution of the command orsubcommand terminated.

User or Operator Response: Reissue the command orsubcommand with the configuration file specified.


TCP0003E Too many operands on the subcommandline

Explanation: Too many operands were specified onthe subcommand line.

System Action: Execution of the subcommandterminated.

User or Operator Response: Reissue the subcommandwith the correct number of operands.


TCP0003E Too many operands on the statementline

Explanation: Too many operands were specified onthe statement line.

System Action: Execution of the statement terminated.

User or Operator Response: Correct the statement andreload the file which contained the statement.


TCP0004E Unrecognized option option - continuing

Explanation: An unrecognized option wasencountered on the command line. Processing of thecommand continued.

System Action: Execution of the command completedwith the unrecognized option

User or Operator Response: If necessary, reissue thecommand with the correct option specified. beingignored.


TCP0005E Unrecognized subcommand or statementname - continuing

Explanation: The specified subcommand or statementwas not recognized.

System Action: The statement or subcommand wasnot processed.

User or Operator Response: If the error was causedby a statement in a machine or configuration file,correct the statement in the file and reenter thecommand or subcommand that read the file. If theerror was caused by a subcommand, reissue thesubcommand with subcommand name correctlyspecified.


TCP0006E Unrecognized operand - operand

Explanation: An unrecognized operand was detectedon the command, subcommand, or statement.

System Action: Execution of the command,subcommand, or statement terminated.

User or Operator Response: If the error was causedby a statement in a machine or configuration file,correct the statement in the file and reenter thecommand or subcommand that read the file. If theerror was caused by a command or subcommand,reissue the command or subcommand with theoperand correctly specified.


© Copyright IBM Corp. 1987, 2002 1

TCP0007I Prior error message refers to line line infile

Explanation: The preceding error message indicatedan error in a machine file or configuration file. Thismessage identifies the line that caused the error.

System Action: None.

User or Operator Response: None.


TCP0007I Prior error message refers to statementstmtnumb in file. The statement in erroris: stmt

Explanation: The preceding error message indicatedan error in a machine file or configuration file. Thismessage identifies the statement that caused the error.




TCP0101E RC=rc loading Machine file: fn ft fm

Explanation: An unexpected return code was receivedwhen reading a machine file.

System Action: The statements in the machine filewere not executed.

User or Operator Response: You may receive a returncode that is the same as one of the return codes theFSREAD macro instruction. For more information onFSREAD and a complete list of the return codes itgenerates, see z/VM: CMS Macros and FunctionsReference.


TCP0102E RC=rc trying to start communications

Explanation: An error prevented the activation orreactivation of the UDP environment.

System Action: If STAYUP mode is active, the serverwill wait a period of

User or Operator Response: If STAYUP is not active,then IPL CMS and restart the server after you correctthe problem. time and attempt to activate the UDPenvironment. Otherwise, the server shuts down.


TCP0103E Unable to establish the Event MonitorEnvironment

Explanation: An error prevented the enablement ofthe event monitor environment.

System Action: The server shuts down.

User or Operator Response: IPL CMS and restart theserver.


TCP0106E Unable to read file: file

Explanation: An error occurred while attempting toread the specified file.

System Action: Execution of the command orsubcommand terminates.

User or Operator Response: This error indicates aproblem Verify access to the file and that the file can beread. After problems are corrected, reenter thecommand or subcommand that caused the file to beread.


TCP0107E Unable to start cyclic timer: timer token,RC=return code, RE=reason code

Explanation: An error occurred while attempting tostart a cyclic timer used by the server.


User or Operator Response: Correct the problem thatprevented the timer from being started and restart theserver. See z/VM: CMS Application Multitasking for moreinformation on the TimerStartInt function, its returncode, and reason codes.

Source File: DHCPD EXEC

TCP0110E Unable to write file: file Pipe rc=rc

Explanation: An error occurred while attempting towrite to the specified file.

System Action: DHCPD server shuts down.

User or Operator Response: Verify access to the fileand that the file can be written. See z/VM: CMSPipelines Reference for more information on the '>>' PIPEstage return code. The most probable cause was thatthere was not enough disk space to update the DHCPDBINDINFO or DHCPDWRK BINDINFO file. Afterproblems are corrected, restart the DHCPD server.


BOOTPD and DHCPD Messages

2 z/VM: TCP/IP Messages and Codes

TCP0110E Unable to write file: file Copyfile rc=rc

Explanation: An error occurred while attempting tocreate the specified file using the CMS COPYFILEcommand.

System Action: DHCPD server shuts down.

User or Operator Response: Verify access to the targetdisk and that the file can be created. See z/VM: CMSCommand and Utility Reference for more information onthe CMS COPYFILE command and the return code.The most probable cause was that there was notenough room to create the file on the disk or directory.After problems are corrected, restart the DHCPD server.


TCP0200E Incorrect CMS level. CMS 11 or later isrequired

Explanation: The server was attempted to be run on alevel of CMS that does not support all of the requiredfunctions used by the server.


User or Operator Response: Run the server on thecorrect level of CMS.


TCP0205E Error encountered while attempting toNUCXLOAD RXSOCK13, rc=retcode

Explanation: An error was encountered when theNUCXLOAD command was issued to load RXSOCK13.


User or Operator Response: See z/VM: CMS Commandand Utility Reference for more information on the CMSNUCXLOAD command and how to correct theproblem.


TCP0300E Could not find my help file: fn HELP *

Explanation: The file which contains the server’s helpinformation was not found on an accessed disk ordirectory.

System Action: The help information is not displayed.

User or Operator Response: Contact the systemadministrator to locate the missing file.


TCP0400E Unable to determine IP address foripaddr Will not answer htype=htypechaddr=chaddr

Explanation: The IP address could not be determinedfor the specified client.

System Action: The server will not respond torequests from the specified client.

User or Operator Response: The probable cause forthis error is that the ":ip" tag is missing for this client orthat it is not specified in lowercase. Correct themachine file for the client and reload the machine file.

Note: The htype and chaddr operands may be missing iftheir related tags were not specified in themachine file.

Source File: BOOTPD EXEC

TCP0401E IP address for tag is not valid Will notanswer htype=htype chaddr=chaddr

Explanation: An invalid IP address was specified withthe indicated tag for the client.

System Action: The server will not respond torequests from the specified client.

User or Operator Response: Correct the machine filefor the client and reload the machine file.

Note: The htype and chaddr operands may be missing iftheir related tags were not specified in themachine file.


TCP0402E tag tag value of tagval for entry is not avalid IP address. The tag will beignored

Explanation: An invalid IP address was specified withthe indicated tag for the entry.

System Action: The tag is ignored.

User or Operator Response: Correct the machine filefor the entry and reload the machine file.


TCP0403E Client IP address is not valid: operand

Explanation: An invalid IP address specified on theCLIENT statement.

System Action: The CLIENT statement is ignored.

User or Operator Response: Correct the CLIENTstatement and reload the machine file. This will causeany following statements that relate to the CLIENTstatement to be improperly handled and may causeadditional errors.


Chapter 1. BOOTPD and DHCPD Messages 3


TCP0404E Boot Strap Server IP address is notvalid: operand

Explanation: An invalid IP address specified on theBOOTSTRAPSERVER statement.

System Action: The BOOTSTRAPSERVER statement isignored.

User or Operator Response: Correct theBOOTSTRAPSERVER statement and reload themachine file.


TCP0500E Unrecognized Adapter IP Address:operand

Explanation: An IP address was specified for anadapter that does not exist on the system.

System Action: Processing of the statement orsubcommand terminates.

User or Operator Response: If the error was causedby a statement in a configuration file, correct thestatement in the file and reenter the command orsubcommand that read the file. If the error was causedby a subcommand, reissue the subcommand with theoperand correctly specified.


TCP0500E Unrecognized Gateway IP Address:operand

Explanation: An invalid IP address was specified for aGateway.




TCP0500E Unrecognized Subnet IP Address:operand

Explanation: An IP address specified as a subnetaddress on a subcommand or statement was notrecognized as a valid address for a subnet connected tothe host system.




TCP0500E Unrecognized target IP Address: operand

Explanation: An IP address specified on asubcommand or statement was not recognized as avalid address.




TCP0502E Target IP Address is missing

Explanation: A target IP address was not specified.




TCP0510E Address range specified on the SUBNETstatement overlaps a previouslyspecified SUBNET range

Explanation: A SUBNET statement specified a rangeof addresses that overlaps a range specified by apreceding SUBNET statement.

System Action: Processing of the statementterminates.

User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.




TCP0511E IP address specified on the CLIENTstatement is the same as a previouslyspecified CLIENT IP address

Explanation: A CLIENT statement specified an IPaddress that is already reserved by a previous CLIENTstatement.




TCP0520E IP address is missing

Explanation: An IP address was expected but notspecified.

System Action: Execution of the subcommand orstatement terminated.

User or Operator Response: If the error was causedby a statement in a machine or configuration file,correct the statement in the file and reenter thecommand or subcommand that read the file. If theerror was caused by a subcommand, reissue thesubcommand with the operand correctly specified.


TCP0521E Hardware type is missing

Explanation: The hardware type was not specified.

System Action: Execution of the subcommand orstatement terminated.

User or Operator Response: If the error was causedby a statement in a machine file, correct the statementin the file and reenter the command or subcommandthat read the file. If the error was caused by asubcommand, reissue the subcommand with theoperand correctly specified.


TCP0522E Client ID is missing

Explanation: The client ID was not specified.




TCP0523E Class name is missing

Explanation: The class name was not specified.




TCP0524E Vendor name is missing

Explanation: The vendor name was not specified.




TCP0530E IP address is not valid

Explanation: An IP address was incorrectly specified.




TCP0531E Hardware type is not valid

Explanation: The hardware type was incorrectlyspecified. The value must be an integer between 0 and255, inclusive.






TCP0532E Client ID is not valid

Explanation: The specified client ID is not valid.




TCP0600E Starting brace is not valid

Explanation: A starting brace "{" was encounteredwhere one was not expected.


User or Operator Response: Correct the machine fileand reenter the command or subcommand that readthe file.


TCP0601E Ending brace is not valid

Explanation: An ending brace "}" was encounteredwhere one was not expected.




TCP0602E Option number operand is not valid

Explanation: An option number was specified that isnot valid. Option numbers must be integers between 0and 255, but not including 0 and 255




TCP0603E Option number operand is missing anoption value

Explanation: An option value was not specified on theOPTION statement.




TCP0610E stmt1 is not valid inside stmt2 statements

Explanation: stmt1 was specified within a level (stmt2)that does not allow such statements.




TCP0620E Too few operands specified

Explanation: The statement or subcommand endedbefore the specification of all required operands


User or Operator Response: If the error was causedby a statement in a machine or configuration file,correct the statement in the file and reenter thecommand or subcommand that read the file. If theerror was caused by a subcommand, reissue thesubcommand with the missing operands specified.


TCP0621E Address range is missing or not valid

Explanation: An address range on a statement orsubcommand was either not specified or specifiedincorrectly.




TCP0622E Label name is missing or not valid

Explanation: A label name was either not specified orspecified incorrectly.






TCP0623E Priority operand is not valid

Explanation: The specified priority value is not a validinteger.




TCP0624E CLASS name is missing or not valid

Explanation: A class name was either not specified orspecified incorrectly.




TCP0625E An IP address range is not allowed on astmt statement at the global level

Explanation: A single IP address is required for thestatement at the global level.




TCP0626E VENDOR name is missing or not valid

Explanation: A VENDOR name is missing or specifiedincorrectly.




TCP0627E HEX value is not a valid hexadecimalstring

Explanation: A specified hexadecimal value is notvalid.




TCP0628E Option statements are not allowed whenVENDOR statement contains the HEXkeyword

Explanation: An OPTION statement was specifiedwithin the VENDOR level for which the HEX keywordwas specified on the VENDOR statement. The OPTIONstatement may not be specified for the VENDOR.




TCP0629E Option operand was already specified

Explanation: An OPTION statement for the specifiedoption was specified more than once at the currentlevel.




TCP0630E Option value is not a valid string

Explanation: The option value was expected to be astring but it was incorrectly specified. Strings must beeither a single word that does not begin with a singleor double quote, or begin and end with the same singleor double quote.






TCP0631E Type value 'value' is not recognized foruser defined option type option

Explanation: The value specified for the indicatedoption is not a recognized option value.




TCP0631E Type value 'value' is not recognized forinternally defined option type option

Explanation: The value specified for the indicatedoption is not a recognized option value. The valueshould correspond to a keyword indicating how anyspecification of the option should be handled. Forexample, it may indicate whether the option datashould be treated as a signed integer.

System Action: The Option is not defined. Any optionstatements for this option are treated according to therules for undefined options.

User or Operator Response: This error indicates aproblem within the DHCPD server. Contact the IBMSupport Center to notify them of the problem. You willneed to provide the complete message text.


TCP0632E Option operand value is not valid Optionoperand value is not valid: value

Explanation: The value specified for the indicatedoption is not valid.




TCP0635E The specified client is not associatedwith an address

Explanation: The specified client is not activelyassociated with an address. For a client to be associatedwith an address, there must be an address that isactively being leased to the client.

System Action: Processing of the subcommandterminates.

User or Operator Response: Verify and reenter thesubcommand with the correct client ID.


TCP0636E The specified client is associated withmore than one address. You must deletethe lease using the address

Explanation: The subcommand was specified usingthe CLIENT operand. It was determined that the clientis being served on more than one subnet. Thesubcommand can not determine which subnet shouldbe changed.


User or Operator Response: Specify the subcommandusing the ADDRESS operand instead of the CLIENToperand so that the subcommand can distinguishwhich subnet to change.


TCP0637E address is not active

Explanation: The specified address is not activelyleased to a client.


User or Operator Response: Respecify thesubcommand with the correct address.


TCP0638E The address range specified on the stmtstatement is not a subset of theSUBNET address range

Explanation: An address was specified on theindicated statement which is at a more specific levelthan the current SUBNET level. The address is notwithin the specified address range for the SUBNET.Statements that relate to a specific subnet must specifyno specific address or an address within the range ofthe current subnet.




TCP0639E The address specified on the stmtstatement is not within the SUBNETaddress range

Explanation: An address range was specified on theindicated statement which is at a more specific levelthan the current SUBNET level. The address range isnot a subset of the specified address range for theSUBNET. Statements with address ranges that relate toa specific subnet must specify ranges which are aproper subset of the range of the current subnet.






TCP0640E The option length is missing for userdefined option type option

Explanation: The length operand was not specified onthe statement which defines the indicated option.


User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file. The Option is notdefined. Any option statements for this option aretreated according to the rules for undefined options.


TCP0640E The option length is missing forinternally defined option type option

Explanation: The length operand was not specified foran option that was being internally defined by theDHCPD server.


User or Operator Response: This error indicates aproblem within the DHCPD server. Contact the IBMSupport Center to noify them of the problem. You willneed to provide the complete message text.


TCP0641E The minimum value is missing for userdefined option type option

Explanation: The minimum value operand was notspecified on the statement which defines the indicatedoption.

System Action: Processing of the statementterminates. The Option is not defined. Any optionstatements for this option are treated according to therules for undefined options.



TCP0641E The minimum value is missing forinternally defined option type option

Explanation: The minimum value operand was notspecified for an option that was being internallydefined by the DHCPD server.




TCP0642E The maximum value is missing for userdefined option type option

Explanation: The maximum value operand was notspecified on the statement which defines the indicatedoption.




TCP0642E The maximum value is missing forinternally defined option type option

Explanation: The maximum value operand was notspecified for an option that was being internallydefined by the DHCPD server.




TCP0643E The minimum value is not valid foruser defined option type option

Explanation: The minimum value operand wasincorrectly specified on the statement which defines theindicated option.






TCP0643E The minimum value is not valid forinternally defined option type option

Explanation: The minimum value operand wasincorrectly specified for an option that was beinginternally defined by the DHCPD server.




TCP0644E The maximum value is not valid foruser defined option type option

Explanation: The maximum value operand wasincorrectly specified on the statement which defines theindicated option.




TCP0644E The maximum value is not valid forinternally defined option type option

Explanation: The maximum value operand wasincorrectly specified for an option that was beinginternally defined by the DHCPD server.




TCP0645E The minimum value is greater than themaximum value for user defined optiontype option

Explanation: The minimum value is greater than themaximum value specified on the statement whichdefines the indicated option.




TCP0645E The minimum value is greater than themaximum value for internally definedoption type option

Explanation: The minimum value is greater than themaximum value specified for an option that was beinginternally defined by the DHCPD server.




TCP0650E Label name is greater than 64 characters:operand

Explanation: The specified label name is longer thanthe allowed maximum length.




TCP0651E Label name is specified more than once:operand

Explanation: The indicated label was specified morethan once on the statement.






TCP0652E Label list is too long

Explanation: The list of labels is too long. It may beno more than 5000 characters long. Extra blanks areremoved before the maximum is checked.




TCP0653E Label name is specified in both theInOrder and Balance lists: label

Explanation: The indicated label name was specifiedon both the INORDER: and BALANCE: statements.




TCP0654E Subnet statements for address specifydifferent labels: label1 label2

Explanation: A SUBNET statement was encounteredfor a subnet that was already specified on anotherSUBNET statement. The label names specified on thetwo SUBNET statements are not the same.

System Action: Processing of the statementterminates. This will cause any following statementsthat relate to the SUBNET statement to be improperlyhandled and may cause additional errors.

User or Operator Response: Correct the statement inthe machine file so that both SUBNET statementsspecify the same label and reenter the command orsubcommand that read the file.


TCP0655E Unable to determine the subnet maskfor subnet subnet

Explanation: The SUBNET statement for the specifiedsubnet did not specify the subnet mask and the maskcould not be determined from the subnet address.


User or Operator Response: This usually indicatesthat the subnet address was incorrectly specified.Correct the statement in the machine file and reenterthe command or subcommand that read the file.


TCP0660E The specified time value is not valid:operand

Explanation: The time value must be a whole number.




TCP0661E The specified unit of time is not valid:operand

Explanation: The specified unit of time is notrecognized or valid for the statement.




TCP0662E The specified time is outside theallowed range

Explanation: The specified time is outside the timerange allowed for the statement.




TCP5000W DHCPDecline received for address, sentby client ID Address is not available foruse

Explanation: The indicated client declined the addressthat was served to it. This will occur when the clientdetermines that an address that it was going to acceptis currently in use.

System Action: The address is marked unavailableuntil

User or Operator Response: Determine the reason forthe decline. Either remove the address from theappropriate subnet in the machine file and reload themachine file, or remove the client that is currentlyusing the address so that DHCPD may serve theaddress to a client. the DHCPD server is restarted.




TCP5001W ICMP ECHO REPLY received for addressAddress is not available for use ClientID id value will not be serviced at thistime

Explanation: A response to an ICMP ECHO REQUESTwas received for an address that is being allocated. Thisis an unexpected event that indicates that the address isalready in use although its use was unknown to theDHCPD server.

System Action: The current client that was going toreceive the address will not receive a response at thistime. The address is marked unavailable until theDHCPD server is restarted.

User or Operator Response: Determine the reason forthe address being active. Either remove the addressfrom the appropriate subnet in the machine file andreload the machine file, or remove the client that iscurrently using the address so that DHCPD may servethe address to a client.


TCP6500I Socket(SendTo) to port at ipaddrreturned: returned values

Explanation: An error occurred on a SOCKETSENDTO function.

System Action: If STAYUP mode is active, the serverwill wait a period of time and attempt to activate theUDP environment. Otherwise, the server shuts down.

User or Operator Response: See the z/VM: CMSCallable Services Reference for information on theSOCKET returned values. Correct the problem.


TCP6501I Socket(Initialize) returned: returnedvalues

Explanation: An error occurred on a SOCKETINITIALIZE function.




TCP6502I Socket(Socket) returned: returned values

Explanation: An error occurred on a SOCKETSOCKET function.

System Action: If STAYUP mode is active, the server

will wait a period of time and attempt to activate theUDP environment. Otherwise, the server shuts down.



TCP6503I Socket(SetSockOpt) on socket socketreturned: returned values

Explanation: An error occurred on a SOCKETSETSOCKOPT function.




TCP6504I Socket(Ioctl) on socket socket returned:returned values

Explanation: An error occurred on a SOCKET IOCTLfunction.




TCP6505I Socket(Bind) on socket, port port, addressaddress returned: returned values

Explanation: An error occurred on a SOCKET BINDfunction.






TCP6506I Socket(IoCtl,SiocGifConf) returned:returned values

Explanation: An error occurred on a SOCKET IOCTLSIOCGIFCONF function.




TCP6507I Socket(GetHostId) returned: returnedvalues

Explanation: An error occurred on a SOCKETGETHOSTID function.




TCP6508I Socket(Close) on socket socket returned:returned values

Explanation: An error occurred on a SOCKET CLOSEfunction.




TCP6509I Socket(IoCtl,SiocGifNetMask) forinterface name returned: returned values

Explanation: An error occurred on a SOCKET IOCTLSIOCGIFNETMASK function.




TCP6510I Socket(Select) returned: returned values

Explanation: An error occurred on a SOCKET SELECTfunction.




TCP6511I Socket(RecvFrom) returned: returnedvalues

Explanation: An error occurred on a SOCKETRECVFROM function.




TCP6512I TCP6512I Socket(IoCtl,SiocGifBrdAddr)for interface name returned: returned values

Explanation: An error occurred on a SOCKET IOCTLSIOCGIFBRDADDR function.

System Action: If STAYUP mode is active, then theserver will wait a period of time and attempt toactivate the UDP environment. Otherwise, the servershuts down.





Chapter 2. Domain Name Server and Resolver Messages

This chapter contains messages issued by the name server and the CMSRESOLutility. Also, these messages are used by the utilities required for setting up andpriming a name server that uses SQL (NSDBLOAD, NSTABLE, and NSACQ).

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.

@ − current origin origin

Severity: Informational.

Explanation: NSDBLOAD encountered an @ in theinput file. This instructs it to continue using thepreviously defined origin. This is normally encounteredwith embedded files. It displays the origin it willcontinue using.



ACQUIRE PUBLIC DBSPACE NAMES tableName(PAGES=count)


Explanation: NSACQ issues this message echoing theSQL command used to acquire space for the nameserver.



Couldn’t open output file

Severity: Error.

Explanation: NSDBLOAD encountered an erroropening its output file. The program terminates withexit code 99.

System Action: NSDBLOAD terminates.

User or Operator Response: Verify that write accessexists to the file mode that NSDBLOAD is using towrite its output file. By default, this is file mode A.

Couldn’t read input master file

Severity: Error.

Explanation: NSDBLOAD encountered an erroropening a resource record file previously generated.


User or Operator Response: Verify that the file can befound in the current search order.

Couldn’t read output resource record file

Severity: Error.

Explanation: NSDBLOAD encountered an erroropening the file it created to store the resource recordsgenerated in an earlier step, or at an earlier time. Thedata from this file is used to create the records in theSQL data base.


User or Operator Response: Verify NSDBLOAD’saccess to the file.

Create index tableName on tableName


Explanation: NSDBLOAD is creating an index fortableName using the same name prior to adding thenew resource records to the table.

System Action: Processing continues.


Creating table tableName


Explanation: NSTABLE issues SQL commands tocreate the indicated table.

System Action: Create the SQL table.



Currently used TABLES: TableNameList


Explanation: NSDBLOAD is using the indicatedtables.



Data base update completed.


Explanation: NSDBLOAD has completed the databaseupdate.



Data outside of inner parens

Severity: Error.

Explanation: A CMSRESOL command line containeddata outside the inner parenthesis. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.

System Action: The CMSRESOL command terminates.

User or Operator Response: Correct the commandsyntax.

DATAGRAM|CONN|IUCV & timeout args missing

Severity: Error.

Explanation: A CMSRESOL command ended before aconnection method and a time-out interval werespecified. See TCP/IP User’s Guide for the syntax of theCMSRESOL command.


User or Operator Response: Use the correct commandline arguments.

Delete all data from tableName table


Explanation: NSDBLOAD is about to delete all datafrom the indicated table.



Deleted all data in SQL table tableName


Explanation: NSDBLOAD has completed deleting alldata in the indicated SQL table.



Do you want to create resource records froma master file(y/n)?


Explanation: The NSDBLOAD command is promptingyou to determine if the resource records should becreated from a master file or the program should endnow.

System Action: If the response is N, the program willterminate.

User or Operator Response: Enter Y or N.

Do you want to delete all resource records fromdb(y/n)?


Explanation: The NSDBLOAD command is promptingyou to determine if all resource records should bedeleted from the database.



Do you want to insert the RR in the SQL tablenow(y/n)?


Explanation: NSDBLOAD is prompting you todetermine if the resource records defined in the inputparameters should be inserted into the SQL tables now.



Do you want to translate all data to lower case?(y/n)


Explanation: NSDBLOAD is prompting you todetermine if all input data should be converted tolowercase. The case needs to match theHOSTNAMECASE setting configured in the NSMAINDATA file.



Do you want to translate all data to upper case?(y/n)


Explanation: NSDBLOAD is prompting you todetermine if all data should be translated to uppercase.The case needs to match the HOSTNAMECASE settingconfigured in the NSMAIN DATA file.

DNS and Resolver Messages




Drop index tableName


Explanation: NSDBLOAD is deleting the current datafor this table.



Error occurred deleting table info

Severity: Error.

Explanation: NSDBLOAD encountered an errordeleting SQL table information.



Error(s) occurred reading master datafile

Severity: Error.

Explanation: NSDBLOAD encountered an error whileprocessing the master data file.


User or Operator Response: Verify the syntax of thedata in the master data file.

EXEC SQLINIT DBNAME(dbname)


Explanation: NSACQ issues this message echoing theSQL command used to initialize its access to SQL.



Finished adding data to table ...


Explanation: NSDBLOAD has finished adding data toits SQL table.



format: NSACQ dbname dbspace npagesNSACQ acquires a dbspace in dbname with

N number of pages.Defaults:

dbname TCPDBAdbspace TCPSPACEnpages 5120


Explanation: The NSACQ command line syntax isdisplayed in response to the NSACQ ? command.

System Action: NSACQ terminates.


format: NSTABLE [Fn [Ft [Fm (for xxxx]]]]NSTABLE creates two tables for each primary andsecondary domain defined for a VM user id.Default file is: NSMAIN DATA A


Explanation: This help text is displayed whenNSTABLE is invoked with ? as the command lineargument. The text displayed has brackets aroundoptional parameters.

System Action: NSTABLE terminates.


Include file not defined

Severity: Error.

Explanation: NSDBLOAD encountered an $INCLUDEstatement in the input file without an accompanyingfile specification.

System Action: The $INCLUDE statement is ignored.NSDBLOAD processing continues.

User or Operator Response: Correct the $INCLUDEstatement.

Incomplete section entry

Severity: Error.

Explanation: A CMSRESOL command line containedan incomplete additional or answer entry, as indicatedby the section message variable. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.


User or Operator Response: Use the correct commandline syntax.

Incomplete entry list

Severity: Error.

Explanation: A CMSRESOL command line containedan incorrect number of entries. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.


User or Operator Response: Use the correct syntax onthe command line.


Chapter 2. Domain Name Server and Resolver Messages 17

Incomplete question entry

Severity: Error.

Explanation: A CMSRESOL command line containedan incomplete question entry. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.


User or Operator Response: Use the correct commandsyntax.

Invalid arg arg

Severity: Error.

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

See TCP/IP User’s Guide for the syntax of theCMSRESOL command.



Invalid class data

Severity: Error.

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 or Operator Response: The query may bechanged so that the invalid class is not returned.

Invalid name server address 'IPaddress'

Severity: Error.

Explanation: A CMSRESOL command line contained aname server address that is not valid. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.


User or Operator Response: Correct the IP address ofthe name server. It should be in dotted decimal form("xxx.xx.x.xxx").

Invalid opcode 'value'

Severity: Error.

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



User or Operator Response: Use a correct value forthe opcode in the CMSRESOL command.

Invalid qclass 'value'

Severity: Warning.

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



User or Operator Response: Use a correct value forthe qclass in the CMSRESOL command.

Invalid qtype 'value'

Severity: Error.

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

ALOC97DBUPDDBQRYNSMDMFCNAMESOAMBMGMR

MXTXTNULLWKSPTRHINFOMINFOAXFRMILBMILA*



User or Operator Response: Use a correct value for



the qtype in the CMSRESOL command.

Invalid timeout 'value'

Severity: Error.

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



Invalid wild card definition

Severity: Warning.

Explanation: NSDBLOAD encountered an invalidwildcard definition in the input file.

System Action: Processing of the master data filecontinues, but when that is complete, NSDBLOAD willterminate.

User or Operator Response: Correct the input file. SeeRFC1035 for the correct wild card entry.

Invoked with extraneous parameters defined

Severity: Error.

Explanation: The NSACQ command was invokedwith extraneous parameters. The correct syntax can beobtained by issuing the NSACQ command with the ″?″parameter.

System Action: NSACQ terminates.

User or Operator Response: Reissue the commandwith the correct syntax.

IUCV Connect rc = returnCode

Severity: Error.

Explanation: A connection could not be made to thedomain name server using IUCV. To use IUCV, thename server must be running on the VM host wherethis command was issued. The returnCode may help inidentifying the nature of the failure.


User or Operator Response: Report the problem toyour system programmer.

System Programmer Response: Verify that the nameserver has access to the IUCV link. Verify that both thename server and the user have IUCV capability definedfor them in their directory entries.

IUCV not possible - HNDIUCV rc = returnCode

Severity: Error.

Explanation: CMSRESOL could not connect to thedomain name server using IUCV. To use IUCV, thename server must be running on the VM host wherethis command was issued. The returnCode may help inidentifying the nature of the failure.


User or Operator Response: Report the problem toyour system programmer.

System Programmer Response: Verify that the nameserver has access to the IUCV link. Verify that both thename server and the user have IUCV capability definedfor them in their directory entries.

IUCV required for data base update

Severity: Error.

Explanation: A CMSRESOL command line contained aparameter mismatch. If the CMSRESOL command lineopcode field indicates a database update (DBASE), theconnection method must be IUCV. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.


User or Operator Response: Correct the CMSRESOLcommand to communicate by means of IUCV.

IUCV Sever failed rc= returnCode

Severity: Error.

Explanation: CMSRESOL encountered an errorsevering an IUCV connection.


User or Operator Response: Report the problem tothe system programmer.

System Programmer Response: If no other messagesaccompany this error, the error can be ignored, sincethe CMSRESOL command has terminated.

Line lineNumber Obsolete root definition. Replacedwith '.'

Severity: Warning.

Explanation: NSDBLOAD encountered an obsoleteroot definition, '..', in the input file.

System Action: NSDBLOAD replaces the obsoletedata from the input file with the current root definition,'.', and continues.

User or Operator Response: Change the rootdefinition from '..' to '.' in the input file.



Line lineNumber SOA mailbox error: badValue

Severity: Error.

Explanation: NSDBLOAD encountered an incorrectlyspecified value in one of the SOA fields. The erroroccurred while processing the indicated line in themaster data file.

System Action: Processing of the master data filecontinues, but when that is complete, NSDBLOAD willterminate.

User or Operator Response: Correct the input file. SeeRFC1034 for the correct format of an SOA record in amaster data file.

Name server addr missing

Severity: Error.

Explanation: A CMSRESOL command ended before aname server address was specified. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.


User or Operator Response: Invoke CMSRESOL withthe required ADDRESS parameter.

New origin origin


Explanation: NSDBLOAD encountered an $ORIGINstatement in its input file. This origin is used forsubsequent statements.



Origin definition error

Severity: Error.

Explanation: NSDBLOAD encountered an $ORIGINstatement in the input file without an accompanyingdefinition.


User or Operator Response: Correct the $ORIGINstatement in the input data file.

Origin has not been defined

Severity: Error.

Explanation: A relative domain name defined in theinput file requires a domain origin suffix, but no$ORIGIN statement has been provided.


User or Operator Response: Correct the input file toinclude an "$ORIGIN domainName" statement.

RoutineName: Active open successful on connectionconnNum


Explanation: The name server has open 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.


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


RoutineName: An invalid address (IPaddress) wasspecified in the FORWARDERS statement

Severity: Error.

Explanation: The FORWARDERS statement contains atleast one incorrect IP address.

System Action: The name server will fail itsinitialization and terminate.

User or Operator Response: The configurationstatement must be corrected before the name server canbe started successfully.

RoutineName: Branch table error

Severity: Error.

Explanation: This message indicates we received anIUCV interrupt for a function we do not support.

System Action: All processing for the IUCV interruptis skipped.

User or Operator Response: None

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 or Operator Response: This message can beignored if not accompanied by other messagesindicating an error situation.

RoutineName: Cache is FULL - Cannot make anyentries


Explanation: This message is displayed when thename server would have cached an answer, but thecache was already full of valid cache entries.

System Action: The entry is not cached. If theinformation is requested again, it will not be availablein the cache. The name server will have to obtain itagain.

User or Operator Response: If this message is seenfrequently and there are no messages indicating ashortage of storage, the size of the cache should beincreased to allow more cache entries to be saved,increasing name server efficiency.

RoutineName: CACHINGONLY cannot be used withPRIMARY or SECONDARY statements

Severity: Error.

Explanation: These configuration statements aremutually exclusive. The name server will not start ifthe configuration file processor encounters aCACHINGONLY statement and either of a PRIMARYstatement or a SECONDARY statement.

System Action: Name server initialization will fail andthe name server will terminate.

User or Operator Response: Correct the conflict in theconfiguration file.

RoutineName: Compressed name continues past end ofpacket


Explanation: This message is displayed duringdiagnostic tracing when an inbound packet isimproperly formatted. The problem is that the length ofthe data we are extracting indicates that there is notenough room left in the received packet to contain thedata.

System Action: The decoding of the packet halts. Thepacket will be rejected as improperly formatted. If thepacket was a question to us, a FORMAT ERRORresponse is sent. If the packet is a response to aquestion we sent to another name server, we ignore theresponse and attempt to get the answer from someother name server.

User or Operator Response: If many invalid packetsare being received, then you can elect to investigate bycontacting the owner of the host that is sending the badpackets. Traces can also dump the inbound packets so

the content of these packets can be examined.

RoutineName: Connection: connNumRoutineName: Notification: noteTypeRoutineName: Amount of space in bytes: byteCount.RoutineName: New state: tcpipStateRoutineName: Reason reasonInfoRoutineName: Bytes delivered: byteCountRoutineName: Push flag: flagValueRoutineName: Last urgent byte: valueRoutineName: Bytes to read: byteCountRoutineName: 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: Connection: connNum ForeignAddress: 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: connType connection never opened

Severity: Warning.

Explanation: A passive or active connection nevercompleted the open process. It may have timed out orthe name server may be in the process of shuttingdown.

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


RoutineName: Connection connNum closed normally


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





RoutineName: Data length size > UDPBUFSIZE


Explanation: The name server received a query viaUDP that was larger than the UDP buffer size beingused. The incoming data will be truncated, but thatdoes not create any problems with name serveroperation. This message is only displayed if diagnostictracing is active.



RoutineName: Data never delivered on connNumconnection

Severity: Warning.

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 name servermay be in the process of shutting down.

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


RoutineName: DATAdelivered error, bytes = byteCount

Severity: Error.

Explanation: The name 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.


RoutineName: Datagram reply truncated

Severity: Error.

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 or Operator Response: Route the question to adifferent name server.

RoutineName: dataType data: length is 0

Severity: Warning.

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 or Operator Response: If the data is from a localSQL table, the input for that table may need to becorrected. The error can also occur because an aninvalid resource record was received from anothername server.

RoutineName: dataType data: no comma or blank

Severity: Warning.

Explanation: Data from an invalid resource record oftype dataType was encountered. The resource record ismissing a required comma or blank, separatingportions of the data.

System Action: Processing of the resource recordterminates. The resource record data cannot be sent toanother host.

User or Operator Response: Correct the informationin the SQL tables.

RoutineName: Data never delivered on connNumconnection

Severity: Warning.

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 name servermay be in the process of shutting down.

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


RoutineName: Disk re-access before SMSG processingis not available


Explanation: The name server is not able toautomatically access all file modes before issuing theSMSG command, because the name server cannot findthe DTCREACC MODULE. That module should havebeen installed when the product was installed. Thisonly creates a problem if the SMSG authorization exechas been modified since the name server was laststarted, because the new version of the exec will not befound.

System Action: Exection continues. The name serverwill not see any changes made to the SMSG



authorization exec since the last time the name serverwas started. It is possible that an error reading theSMSG authorization exec could occur, due to the waythe CMS file system works in the case of disks that areaccessed readonly.

User or Operator Response: The name serverconfiguration should be changed to conform to IBMrecommendations.

RoutineName:Displaying storage at addr for dLen(’hLen’x) bytes

memoryAddress 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 message willbe repeated as many times as necessary to display allthe data.


User or Operator Response: The information may beuseful in determining the nature of any problemreported or being diagnosed.

RoutineName: Duplicate SQL table name tableName

Severity: Error.

Explanation: The name server encountered a duplicateSQL base table name when processing the name serverconfiguration file. The table names used on the Primaryand Secondary statements in the name serverconfiguration file must be unique.

System Action: The name server continues, but anyzone except the first with the indicated name will notbe transferred or useable.

User or Operator Response: Check the name serverconfiguration file and make any changes required tocorrect the situation. Ensure the data is loaded for anynew Primary tables you define.

RoutineName: Error returnCode adding RR to database

Severity: Error.

Explanation: The name server encountered an errorinserting a zone transferred resource record into anSQL table. This can happen if the zone data iscorrupted or if we run out of space in SQL.

System Action: The resource record is not added tothe SQL tables. The zone transfer is terminated.


RoutineName: Error returnCode beginning TCP/IPservice

Severity: Error.

Explanation: TCP/IP services could not be initialized,making it impossible for the name server to function.The most common cause of this problem is TCP/IPservice machine is not operational. The ReturnCode canbe used to further investigate the nature of theproblem.

System Action: The name server will terminate.

User or Operator Response: Investigate why the errormay have occurred. Correct the cause of the error andrestart the name server.

RoutineName: Error returnCode from calledRoutine

Severity: Error.

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 name server from anothersystem. The current question or transaction will notcomplete successfully, but the name server 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.


RoutineName: Error in TCPIPservice: errorInfo

Severity: Error.

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


RoutineName: Error opening connection to remotename server

Severity: Warning.

Explanation: An error occurred while attempting toopen a TCP connection to a remote name server. Theoperation that was going to be performed is



terminated. This can happen when attempting toinitiate a zone transfer or when sending a request to aremote name server via TCP. The action will be retried.The situation can be caused by network outages orfailures at the remote host.

System Action: The operation will be retried.


RoutineName: FORWARDERS address IPaddressignored, only limit are allowed

Severity: Warning

Explanation: The FORWARDERS statement containedmore than limit IP addresses. Any IP addressesencountered after this limit is reached are ignored. Thisis done to balance reliability and performance. Morethan 3 addresses can adversely impact performancewithout significantly improving reliability.

System Action: Exection continues.


RoutineName:Foreign name server responds withRCODE = rcode

Severity: Warning

Explanation: The name server was in the process oftransferring a zone from a remote name server. In thepacket being processed, the foreign name serverindicated that there was a problem. The nature of theproblem is indicated by the value ofrcode. Thisindication could also mean the the foreign name serverhas refused to transfer the zone to us. In that case thevalue of rcode is 5.

System Action: Exection continues. The zone transferwill be attempted again later.

User or Operator Response: If the problem persists,the administrator of the remote name server should becontacted and informed of the problem.

RoutineName: Ignoring fileId file, forwarding in use


Explanation: The name server will not use thespecified root cache file, because forwarding is in use.When a FORWARDERS statement is specified in theconfiguration file, the name server will only use the IPaddresses of the name servers to help answerquestions.

System Action: Exection continues.


RoutineName: Insufficient data available

Severity: Warning.

Explanation: The name server 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 will fail. Therequest will be retried by the originating host.


RoutineName: Invalid flags 'xxxx'x

Severity: Error.

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

System Action: The data from such a packet is usuallydiscarded. The name server may return an error packetto the sending host with a return code that indicates aformatting error.

User or Operator Response: If these messages becomeexcessive, turn on queue tracing to determine thesource of the bad packets and contact the name serveradministrator of that system.

RoutineName: Label 0 or > 63 - input 'hostString'

Severity: Error.

Explanation: A name server host name had an invalidlength. The maximum length is 63 characters for anyportion of the name, the portions being separated bydots. The length cannot be 0. This is usually the resultof invalid data in the local SQL database.

System Action: The packet that was being constructedwill be discarded. The invalid data cannot be sent toanother host.

User or Operator Response: The hostString can beused to indicate what data to check in the SQLdatabase.

RoutineName: dataType length > maxLength

Severity: Warning.

Explanation: The data being processed in a resourcerecord is too long.

System Action: The name server truncates the data tothe MAX length indicated and sends that data.

User or Operator Response: Correct the resourcerecord defined in the SQL tables.



RoutineName: Limiting cacheName cache size to newSize


Explanation: The maximum size of the cache is beingreduced so it won’t limit name server operation. This isdone when the name server is running low on memory.When more memory is available, the name server willallow the cache to expand.

System Action: Execution continues. Old cache entriesmay be deleted to accomodate the change in size.

User or Operator Response: If this is a persistentproblem, the virtual machine size for name servercould be increased.

RoutineName: Name server shut down with CP EXT


Explanation: The name server was shut down by anexternal interrupt, issued with the CP EXT command atthe name server console.



RoutineName: Name server shutting down due toTCP/IP

Severity: Error.

Explanation: The TCP/IP stack has informed thename server that it is stopping.

System Action: The name server will terminate, sinceit cannot operate without the TCP/IP stack. When theTCP/IP stack restarts, it will start the name server ifyou have configured the TCP/IP stack to do so.


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


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



RoutineName: New serial value old serial value


Explanation: The name server has received the serialof the zone it is considering transferring. It isdisplaying the new and the old serials. If they match, azone transfer is not required. This message only occurswhen diagnostic tracing is active.



RoutineName: New domain SOA: serial serial refreshvalue


Explanation: The name server is in the process oftransferring a zone and has just received the currentSOA record for the zone. It is displaying the values inthe SOA record. This message only occurs whendiagnostic tracing is active.



RoutineName: No data available

Severity: Warning.

Explanation: The name server received a datagramwithout data.

System Action: The datagram is ignored.


RoutineName: No room: retend memoryAddress retpmemoryAddress


Explanation: The name server exceeded buffercapacity. The location of the memory and the currentposition in memory are also displayed, since they maybe helpful in identifying the cause of the error. Themessage will be accompanied by another messageindicating what type of data was being processed whenthe error occurred.

This message will be displayed any time the situationoccurs if tracing is enabled. Otherwise, it will only bedisplayed when the answer portion of the packet hadto be truncated. Since that condition can lead tounresolved hosts, that error is considered ″Warning″level, and is displayed even when tracing is disabled.Depending on how the partial answer is handled, itstill may not result in any observable problem.

System Action: The partial packet is used. The data itcontains is usually sufficient to continue processing.


RoutineName: No room for InformationType

Severity: Warning.

Explanation: The name server exceeded buffercapacity. The InformationType that was being processedis displayed. This can be caused by the receipt of atruncated packet. It can also occur when an outboundpacket is being constructed and not all the data will fit.In most cases, this does not indicate a problem. If thehost that asked the question did not get all theinformation it needed because it would not fit in asingle packet, it will ask additional questions or



attempt to obtain the data via TCP.


System Action: The partial packet is used. The data itcontains is usually sufficient to continue processing.


RoutineName: No room for header

Severity: Warning.

Explanation: The name server could have exceededbuffer capacity while building a packet, if the erroroccurred while attempting to send a packet. Also, thepacket received by the name server may have been toosmall to contain a name server packet header. Othermessages will indicate the direction of the packet.


System Action: The packet is ignored.

User or Operator Response: When the packets areinbound, they represent errors on the part of thesender. If these messages become excessive, turn onqueue tracing to determine the source of the badpackets and contact the name server administrator ofthat system.

RoutineName: No room for label - input 'hostString'

Severity: Warning.

Explanation: A packet was being constructed, and thebuffer in which it is being constructed has run out ofspace. There are usually multiple packets put in abuffer in response to questions from foreign hosts. Thismessage, by itself, does not indicate any error.


System Action: Datagram construction is halted. The

truncated datagram is forwarded to the requesting host.

User or Operator Response: If this message isoccurring often, ensure that QUEUE tracing is disabled.

RoutineName: No room for type and class

Severity: Warning.

Explanation: The name server exceeded buffercapacity. This can be caused by the receipt of atruncated packet. It can also occur when an outboundpacket is being constructed and not all the data will fit.In most cases, this does not indicate a problem. If thehost that asked the question did not get all theinformation it needed because it would not fit in asingle packet, it will ask additional questions orattempt to obtain the data via TCP.


System Action: The host uses the partial packet. Thedata it contains is usually sufficient, and processingcontinues..


RoutineName: No SOA or NS records found

Severity: Warning.

Explanation: The message indicates a probableconfiguration problem. If you have configured tooperate the name server as a secondary name server,and have never previously started it so that the SQLtables do not have any data for the domains you aresupporting, then this message does not represent anproblem. If you are acting as a primary name server,the SQL data should contain SOA and NS records foryou to operate properly.


User or Operator Response: Verify that the zone datacontains the correct SOA and NS resource records.

RoutineName: Notice arrives -->


Explanation: We have just started processing a newpiece of work delivered via the PASCAL API. Themessage is only issued during diagnostic tracing.





RoutineName: NoticeType notify arrived on connectionconnNum


Explanation: A PASCAL API notification is beingprocessed by the name server. The type of thenotification or the new state if it is a Connection StateChanged notification is displayed, along with theconnection number associated with the notification. Themessage is only issued during diagnostic tracing.



RoutineName: Passive open for port portNumber failed,rc = ReturnCode

Severity: Error.

Explanation: The name server could not start itscommunications with the TCP/IP stack.

System Action: During initialization and in mostother cases, this will cause the name server toterminate.

User or Operator Response: Examine the ReturnCodeto determine the nature of the error.

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: Purging the entire cacheName cache


Explanation: This message is seen during shutdownand if an SMSG PURGE command is issued to purgean entire cache.

System Action: Execution continues. If we are notshutting down, the cache will start to grow again asnew entries are added.


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: Raising cacheName cache size limit tonewSize


Explanation: The cache is being enlarged, because it issmaller than the configured size and there is enoughmemory available to allow it to grow without limitingname server operation.

System Action: Execution continues. The cache willstart to grow as new entries are added.


RoutineName: Request for storage of size bytesOfStorage


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



RoutineName: Recursion not configured or requested


Explanation: The name server does not know theanswer to the question and it is no going to askanother name server for help (it will not do recursion).This is either because the name server has beenconfigured to prevent recursion using theNORECURSION statement, or the query beingprocessed did not have the recursion desired flag set.

System Action: Recursion is not performed and anyCNAMES and the best referral zones and addresses areput in the return packet.


RoutineName: Received bad packet from IPaddress


Explanation: A packet was received from a nameserver or resolver at the IP address indicated that wewere unable to process because it appeared to beimproperly formatted.

System Action: If the packet was a question to us, aFORMAT ERROR response is sent. If the packet is aresponse to a question we sent to another name server,we ignore the response and attempt to get the answerfrom some other name server.

User or Operator Response: If many invalid packets



are being received, then you can elect to investigate bycontacting the owner of the host that is sending the badpackets. Traces can also dump the inbound packets sothe content of these packets can be examined.

RoutineName: Resetting refresh value


Explanation: The zone-transfer refresh timer haspopped, and the name server has contacted a remotename server to see if our name server’s data needs tobe refreshed from the remote name server. The messageindicates a zone transfer is not required at this time.

System Action: The zone-transfer refresh timer is resetand restarted.


RoutineName: Response from unexpected addressfromAddress, expected expectedAddress

Severity: Warning.

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



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: Sending domainName zone


Explanation: This message indicates that the localname server is transferring the domainName zone tosome other host. This message is only displayed ifdiagnostic tracing is active.



RoutineName: TABLES specified in PRIMARY orSECONDARY statements are conflicting

Severity: Error.

Explanation: This indicates that a table we defined ina PRIMARY or SECONDARY statement in theconfiguration file does not exist or is defined in anotherPRIMARY or SECONDARY statement.

System Action: Name server initialization will fail andthe name server will terminate.

User or Operator Response: Correct the error in theconfiguration file.

RoutineName: TCP table not defined, no zones defined

Severity: Error.

Explanation: There do not appear to be any SQLtables defined, but there are configuration statementspresent that indicate the need to use SQL. A SQL tablecontaining resource records must be defined.

System Action: The name server attempts to continue.It may be able to operate in a caching only mode.

User or Operator Response: Correct the configurationerror either by creating an SQL table or using acaching-only configuration.

RoutineName: TCP/IP service initiated


Explanation: The name server’s TCP/IP initializationwas successful.



RoutineName: tcpclose failed for active conn connNum

Severity: Warning.

Explanation: After returning a query answer, thename server fails to close the TCP connection. Theremote host may have already closed the connection.



RoutineName: The following traces are in effect:traceList


Explanation: This message shows the list of traces thatare currently active.





RoutineName: The FORWARDERS statement requiresat least 1 address traceList

Severity: Error.

Explanation: The FORWARDERS statement requires atleast one valid IP address to be specified. No addresseswere provided on the FORWARDERS statement.

System Action: The name server will fail itsinitialization and terminate.

User or Operator Response: The configurationstatement must be corrected before the name server canbe started successfully.

RoutineName: Timer expired for connection connNum

Severity: Warning.

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

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


RoutineName: Timer expired for inactive connection

Severity: Warning.

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

System Action: The name server ignores thenotification.


RoutineName: ttl=value rdata='value'


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



RoutineName: Unable to find VM password in rdata

Severity: Error.

Explanation: An attempt was made to update thename server data in SQL via IUCV. When the updatepacket was parsed, no VM password was found. Apassword is required to make any changes to the SQLdata.

System Action: The SQL update is ignored.


RoutineName: Unable to extract TCP view informationfrom SQL, rc = returnCode


Explanation: The default SQL table TCP does notexist. This special table is used to record whether weare using the ″0″ or ″1″ level of any SQL tables.

System Action: The name server will default to usingthe ″0″ level of any SQL tables.


RoutineName: Undefined remote name server for zonedomainName

Severity: Error.

Explanation: The configuration statement for asecondary name server did not specify an IP addressfor the name server from which to obtain the zoneinformation.

System Action: The zone data is not loaded oravailable locally.

User or Operator Response: Correct the SECONDARYstatement in the configuration file.

RoutineName: Undefined state stateValue

Severity: Warning.

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

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


RoutineName: Undefined remote name server for zonedomainName

Severity: Error.

Explanation: The configuration statement for asecondary name server did not specify an IP addressfor the name server from which to obtain the zoneinformation.

System Action: The zone data is not loaded oravailable locally.

User or Operator Response: Correct the SECONDARYstatement in the configuration file.

RoutineName: Unexpected question

Severity: Error.

Explanation: During a zone transfer, a question hasarrived in the middle of the transfer data. This shouldnot happen; it is a violation of the protocol.



System Action: The zone transfer aborts. Name serverexecution continues.


RoutineName: Unexpected notification notificationID


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


User or Operator Response: This message can beignored if not accompanied by other messagesindicating an error situation.

RoutineName: Unexpected query type queryType

Severity: Warning.

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

System Action: The query is ignored.


RoutineName: Unknown type during SQLfunction

Severity: Warning.

Explanation: The name server encountered anunknown resource record type while preparing toperform a SQLfunction database operation.

System Action: The name server’s response to thequestion indicates the query failed.


RoutineName: Using cache file 'FileId'


Explanation: The name server is using FileId as theinput file for defining the remote name servers that willbe used in a CACHINGONLY configuration.



RoutineName: Using input file FileId


Explanation: The name server issues this message toindicate what configuration file it is using.



RoutineName: VM id of Name Server Required forIUCV

Severity: Error.

Explanation: A CMSRESOL command line omitted thename server VM ID. This field is required if IUCV isselected as the connection method; otherwise, it can beomitted. See TCP/IP User’s Guide for the syntax of theCMSRESOL command.

System Action: CMSRESOL halts and exits.

User or Operator Response: Correct the commandsyntax.

RoutineName: VM password is longer than max of 8chars

Severity: Error.

Explanation: An attempt was made to update thename server data in SQL via IUCV. When the updatepacket was parsed, the data that was expected to be aVM password was longer than 8 characters and wasconsidered to be invalid. A password is required tomake any changes to the SQL data.

System Action: The SQL update is ignored.


Select remarks


Explanation: NSDBLOAD is issuing an SQL SELECTREMARKS command while attempting to determinewhether to update the ″0″ table or the ″1″ table.



Table tableName already exists


Explanation: NSTABLE creates two SQL tables foreach SQL base table name. An SQL table with thatname already exists. This message will be seen whenrunning NSTABLE to create new tables when there areother tables defined in the configuration file that havebeen previously created.

System Action: Execution continues. The existingtables are not changed in any way.


Timeout arg missing

Severity: Error.

Explanation: A CMSRESOL command line omitted atimeout-interval specification. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.




User or Operator Response: Verify the correct use ofthe TIMEOUT value in the parameter list.

Too many nested parentheses

Severity: Error.

Explanation: A CMSRESOL command line containedan incorrect number of nested parentheses; themaximum is two levels of nested parentheses. SeeTCP/IP User’s Guide for the syntax of the CMSRESOLcommand.


User or Operator Response: Verify the correct syntaxof the command.

Too many parms in section entry

Severity: Error.

Explanation: A CMSRESOL command line contained aquestion, additional, or answer entry with too manyparameters. See TCP/IP User’s Guide for the syntax ofthe CMSRESOL command.



Too many right parens

Severity: Error.

Explanation: A CMSRESOL command line containedan incorrect number of right parentheses. See TCP/IPUser’s Guide for the syntax of the CMSRESOLcommand.



UNEXPECTED SQL ERROR RETURNEDSQLCODE: returnCodeCHANGES WILL BE BACKED OUTFAILING SQL STATEMENT IS:

SQLstatement

Severity: Error.

Explanation: These messages may be issued fromNSACQ or NSTABLE. The command encountered afatal SQL error.

System Action: All previous non-committed work isrolled back. The command terminates with a returncode of returnCode.

User or Operator Response: Examination of theSQLstatement and the returnCode may indicate the

nature of the problem. Correct the problem and retrythe command.

Update statistics on the tableName table


Explanation: NSDBLOAD updates the statistics for thetable just processed after all the records have beenadded.



Using input file FileName


Explanation: NSTABLE and NSDBLOAD issue thismessage to indicate what configuration file they areusing.



Using sql table tableName


Explanation: NSDBLOAD is indicating which SQLtable will be processed.

System Action: NSDBLOAD continues.


Zone transfer request failed

Severity: Warning.

Explanation: The attempt to connect to a foreign nameto accomplish a zone transfer has failed.

System Action: We will try to obtain the zone data ata later time.




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


Source File: 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 or Operator Response: If the FTP server shoulduse the SRVRFTP TCPXLBIN or the STANDARDTCPXLBIN translation file, make sure the correcttranslation file is in the FTP server search order andrestart the FTP server.



DTCFTS0004E Server-FTP: program requires ECMODE ON.

Severity: Error.

Explanation: EC MODE is off.

System Action: The server program halts at this point.

User or Operator Response: Verify that EC MODE, orEC MODE emulation is on. Correct your input and tryagain.



DTCFTS0005E Server-FTP: unable to determinevirtual machine ID

Severity: Error.

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


User or Operator Response: Enter a valid virtualmachine identification code. Check the systemconfiguration to ensure that an FTP server machine hasbeen identified and is operational.



DTCFTS0009E Port number port_number is not valid

Severity: Error.

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 or Operator Response: Correct the configurationfile statement and restart the FTP server.


Procedure Name: ProcessConfigFile

DTCFTS0010I External Security Manager will beused


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



Source File: FTSVMSUB PASCAL

Procedure Name: SystemInitialize


|

||

|

|||

|

|||

|

|

|

|

||

|

||||

|

|||||

|

|

|||

|

|

|

|||

|

|

|||

|

||

|

||||

|

|

||

|

|||

|

||

|

|

|||

|

||

|

|

|

|

DTCFTS0013E Unrecognized configuration filestatement: statement

Severity: Error.

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 TCP/IP Planning andCustomization.


User or Operator Response: Delete or correct thestatement that is in error, then restart the FTP server.


Procedure Name: DoNewCommand

DTCFTS0014I Using port port.

Severity: Informational

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





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

Severity: Error.

Explanation: You received a nonzero return code atinitialization.

System Action: The server program halts.

User or Operator Response: Identify the problem andresubmit the job.


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 or Operator Response: Attempt to correct theproblem, and then restart the server.

DTCFTS0021I Server-FTP: Initialization completedDateTime


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





DTCFTS0033E FSENDresponse note shows error:reason

Severity: Error.

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


User or Operator Response: Determine why the datacould not be sent over the connection. If needed,contact your IBM Support Center for assistance.



DTCFTS0034E FRECEIVEerror note shows: reason

Severity: Error.

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


User or Operator Response: Determine why the datacould not be received over the connection. If needed,contact your IBM Support Center for assistance.



FTP Messages


|||

|

|||||

|

||

|

|

||

|

||

|

|

|

|

||

|

|||

|

|

|

|

||

|

||

|

||

|

|

|

|||

|||||||

|

||

|||

|

||

|

|

|

|

|||

|

|||

|

|||

|

|

||

|

|||

|

|||

|

|

DTCFTS0035I Connection conn: received note ’type’

Severity: Error.

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


User or Operator Response: Determine why the FTPserver received the specified notification. If needed,contact your IBM Support Center for assistance.



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





DTCFTS262I Using TChinese translate table FileNameFileType


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

Severity: Error.

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 or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPKJBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



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

Severity: Error.

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 isloaded, and program execution continues.

User or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPHGBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables. Hangeul andKSC5601 DBCS conversion types will be unavailable.



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

Severity: Error.

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

FTP Messages

Chapter 3. FTP Messages 35

||

|

|||

|

|||

|

|

||||

|

|||

|

|

|

|

|||

|

|||

|

|

|

|

||||

|

|||

|

|

|

|

|

|||

|

||||||

|||

|||||

|

|

|||

|

||||||

||

||||||

|

|

|||

|

||||||

||

Traditional Chinese DBCS conversion type will beunavailable.

User or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPCHBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



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

Severity: Error.

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


User or Operator Response: Correct the appropriate:Parms. tag entry in the DTCPARMS file, then restartthe FTP server.

System Programmer Response: None.


Procedure Name: InitConfigs

DTCFTS0308E Configuration file type is not valid

Severity: Error.

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






DTCFTS0309E Configuration file mode is not valid

Severity: Error.

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






DTCFTS0310I Unable to find input file: filenamefiletype filemode

Severity: Error.

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


User or Operator Response: Verify the correctness ofthe appropriate :Parms. tag entry in the DTCPARMSfile and that the specified file is located on a minidiskthat is accessed by the FTP server, then restart theserver.



DTCFTS0311E Invalid numeric operand found:operand

Severity: Error.

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


User or Operator Response: Correct the appropriateconfiguration file statement and restart the FTP server.


Procedure Name: Error

DTCFTS0312E Port number not specified for PORTstatement

Severity: Error.

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


FTP Messages


||

|||||

|

|

|||

|

|||

|

|

|

|

||

|

|||

|

|||

|

|

|

||

|

|||

|

|||

|

|

|

||

|

|||

|

|||

|

|

|

|||

|

|||

|

|||||

|

|

|||

|

|||

|

||

|

|

|||

|

||

|




DTCFTS0313E Setting not specified for INACTIVEstatement

Severity: Error.

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





DTCFTS0314E Translate table not specified forLOADDBCSTABLE statement

Severity: Error.

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





DTCFTS0315E INACTIVE time seconds is not valid

Severity: Error.

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





DTCFTS0317E Unrecognized option: option

Severity: Error.

Explanation: An unsupported option was specified onthe SRVRFTP command.


User or Operator Response: Specify only supportedoptions on the SRVRFTP command.


Procedure Name: ParseOptions

DTCFTS0349E Translate table table-name is not valid

Severity: Error.

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





DTCFTS0358E RDR statement filemode fm is notvalid or is not writable

Severity: Error.

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


User or Operator Response: Ensure the file modespecified for the RDR statement is valid and that thefile mode in question can be accessed by the FTP serverwith read/write status, then restart the FTP server.

Source File: FTSRVPA PASCAL, FTSVMSUB PASCAL

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

Severity: Error.

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

FTP Messages


||

|

|

|||

|

||

|

||

|

|

|||

|

||||

|

||

|

|

||

|

||||

|

||

|

|

||

|

||

|

||

|

|

||

|

||||

|

||

|

|

|||

|

|||

|

||||

|

|

|||

|

|||

|

|

|

|

|||

|

||





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

Severity: Error.

Explanation: CSL routine DMSESM returned anonzero return code and was unable to obtain asecurity token for ESM calls.

System Action: FTMAIN is exited.

User or Operator Response: Contact your RACFadministrator to determine the cause of the problem.



DTCFTS0365E DMSPWCHK call returns rc; Logdata:’data’

Severity: Error.

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 or Operator Response: Contact the systemadministrator for the External Security Manager (ESM)that is in use, for assistance in resolving this problem.


Procedure Name: DoPass

DTCFTS0366E Wrong level of CMS: routine notfound

Severity: Error.

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


User or Operator Response: Re-IPL with theappropriate level of CMS.

Source File: FTSRVPA, FTSVMSUB

Procedure Name: Initialize, SystemInitialize,CheckPassword

DTCFTS0367E Wrong level of CP: Diagnose 88 notavailable

Severity: Error.

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


User or Operator Response: Upgrade to theappropriate level of z/VM.

Source File: FTSVMSUB


DTCFTS0368I Warning: FTP server is missing classD privileges for virtual reader support

Severity: Error.

Explanation: The FTP server needs class D priviledgesin 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 or Operator Response: If users need to be ableto list or delete virtual reader files, the FTP server mustbe given class D privileges.



DTCFTS0369E Format type not specified forLISTFORMAT statement

Severity: Error.

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





DTCFTS0370E LISTFORMAT type list_format is notvalid

Severity: Error.

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



FTP Messages


|

||

|

|

||||

|

|||

|

||

|

|

|||

|

|||||

|

|||

|

|

|||

|

||

|

||

|

||

|

|||

|

||

|

||

|

|

|||

|

|||||

|

|||

|

|

|||

|

|||

|

||

|

|

|||

|

|||

|

||



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

Severity: Error.

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





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

Severity: Error.

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





DTCFTS0376E TIMESTAMP setting timestamp-settingis not valid

Severity: Error.

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





DTCFTS2500I NewConnectionEvent: Bad state state


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


User or Operator Response: Contact your IBMSupport Center for assistance.

Source File: FTSEVEN PASCAL

Procedure Name: NewConnectionEvent

DTCFTS2515I SRVRFTP: timer expired onnon-control connection

Severity: Error.

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




Procedure Name: TimerExpiredEvent

DTCFTS2519E FTP Server shutdown initiated.

Severity: Error.

Explanation: The ShutDownAndDie procedure issuesthis informational message.

System Action: When an external interrupt is

FTP Messages


|

|

||

|

|||||

|

|

|

|

|||

|

|||

|

||

|

|

|||

|

||||||

|

|

|

|

|||

|

|||

|

||

|

|

|||

|

|||

|

||

|

|

||

|

|||

|

||

|

|

|||

|

|||

|

||

|

|

||

|

||

|

received, the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated. Thevariable ShuttingDown is set to true once shutdownhas been initiated. A delay may occur while waiting forconnections to close. If a second external interrupt isreceived while shutting down, the program terminatesimmediately.

User or Operator Response: Correct the problem andresubmit the job.


Procedure Name: ShutDownAndDie

DTCFTS2520E No connections open. Shutdown willoccur immediately.

Severity: Error.

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

System Action: When an external interrupt isreceived, the procedure ShutDownAndDie is called. Allconnections are aborted and SRVRFTP terminated. Thevariable ShuttingDown is set to true once shutdownhas been initiated. A delay may occur while waiting forconnections to close. If a second external interrupt isreceived while shutting down, the program terminatesimmediately.




DTCFTS2521E Number connections in use. Stand bywhile the connections are aborted.

Severity: Error.

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 isreceived, the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated. Thevariable ShuttingDown is set to true once shutdownhas been initiated. A delay can occur while waiting forconnections to close. If a second external interrupt isreceived while shutting down, the program terminatesimmediately.

User or Operator Response: Comply with theinstructions that are displayed in later messages.



DTCFTS2522E Enter a second STOP command toshutdown immediately

Severity: Error.

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 isreceived, the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated. Thevariable ShuttingDown is set to true once shutdownhas been initiated. A delay can occur while waiting forconnections to close. If a second external interrupt isreceived while shutting down, the program terminatesimmediately.

User or Operator Response: To terminate the openconnections, enter the STOP command.



DTCFTS2524E Currently shutting down; will shutdown immediately.

Severity: Error.

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

System Action: When an external interrupt isreceived, the procedure ShutDownAndDie is called. Allconnections are aborted, and SRVRFTP terminated. Thevariable ShuttingDown is set to true once shutdownhas been initiated. A delay may occur while waiting forconnections to close. If a second external interrupt isreceived while shutting down, the program terminatesimmediately.




DTCFTS2582E List format format for User user inCHKIPADR is not valid

Severity: Error.

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


User or Operator Response: Correct the CHKIPADRexit.


Procedure Name: VMIpAdrChk

FTP Messages


|||||||

||

|

|

|||

|

|||

||||||||

||

|

|

|||

|

||||

||||||||

||

|

|

|

|||

|

||||

||||||||

||

|

|

|||

|

|||

||||||||

||

|

|

|||

|

|||

|

||

|

|

DTCFTS2583E Format type not specified inLISTFORMAT command for User userin CHKIPADR

Severity: Error.

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





DTCFTS2592E AUTOTRANS setting setting for Useruser in CHKIPADR is not valid

Severity: Error.

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





DTCFTS2593E Setting not specified forAUTOTRANS command for User user inCHKIPADR

Severity: Error.

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





DTCFTS2600I {LINES | TRANSLATE} value notspecified for VMFILETYPEDEFAULTstatement

Severity: Error.

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

System Action: None

User or Operator Response: Review the TCPIP DATAfile, and ensure that an appropriate value is specifiedwith the LINES or TRANSLATE parameter for theindicated statement. For detailed information about thisstatements, see TCP/IP Planning and Customization.


Procedure Name: ProcessParms

DTCFTS2601I {LINES | TRANSLATE} value notspecified for VMFILETYPE extensionstatement

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.A value 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 or Operator Response: Review the TCPIP DATAfile, and ensure that an appropriate value is specifiedwith the LINES or TRANSLATE parameter for theindicated statement. For detailed information aboutthese statements, see TCP/IP Planning and Customization.



DTCFTS2602I {LINES | TRANSLATE} value valuefor VMFILETYPEDEFAULT statement isnot valid

Severity: Error.

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


User or Operator Response: Review the TCPIP DATAfile, and ensure that an appropriate value is specifiedwith the LINES or TRANSLATE parameter for theindicated statement. For detailed information aboutthese statements, see TCP/IP Planning and Customization.



DTCFTS2603I {LINES | TRANSLATE} value valuefor VMFILETYPE extension statement isnot valid

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The indicated value is not supported for use with the

FTP Messages


||||

|

|||

|

||

|

|

|||

|

|||

|

||

|

|

||||

|

|||

|

||

|

|

||||

|

|||||

|

|||||

|

|

||||

|

||||||

|

|||||

|

|

||||

|

|||||

|

|||||

|

|

||||

|

||

LINES or TRANSLATE parameter. This parameter hasbeen specified as part of the VMFILETYPE statementthat defines translation characteristics for the indicatedfile extension.


User or Operator Response: Review the TCPIP DATAfile, and ensure that an appropriate value is specifiedwith the LINES or TRANSLATE parameter for theindicated statement. For detailed information about thisstatement, see TCP/IP Planning and Customization.



DTCFTS2604I Parameter parameter specified forVMFILETYPEDEFAULT statement is notrecognized

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The parameter listed is not supported for use with theVMFILETYPEDEFAULT statement. This parameter hasbeen specified as part of the VMFILETYPEDEFAULTstatement that defines default translation characteristics.


User or Operator Response: Review the TCPIP DATAfile, and verify this parameter was specified correctlyfor the indicated statement and was not misspelled. Fordetailed information about this statement, see TCP/IPPlanning and Customization.



DTCFTS2605I Parameter parameter specified forVMFILETYPE extension statement is notrecognized

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The parameter listed is not supported for use with theVMFILETYPE statement. This parameter has beenspecified as part of the VMFILETYPE statement thatdefines translation characteristics for the indicated fileextension.


User or Operator Response: Review the TCPIP DATAfile, and verify this parameter was specified correctlyfor the indicated statement and was not misspelled. Fordetailed information about this statement, see TCP/IPPlanning and Customization.



DTCFTS2606E Unable to processVMFILETYPEDEFAULT statement;DMSTCD rc rc rsc rsc

Severity: Error.

Explanation: An error occurred while using theDMSTCD CSL routine to process the TCPIP DATA file.


User or Operator Response: Use the return code andreason code from the DMSTCD CSL routine todetermine why the error occurred. Refer to the z/VM:CMS Callable Services Reference for return and reasoncodes.


Procedure Name: ProcessFileExtInfo

DTCFTS2607E Unable to process VMFILETYPEstatement; DMSTCD rc rc rsc rsc

Severity: Error.

Explanation: An error occurred while using theDMSTCD CSL routine to process the TCPIP DATA file.


User or Operator Response: Use the return code andreason code from the DMSTCD CSL routine todetermine why the error occurred. Refer to the z/VM:CMS Callable Services Reference for return and reasoncodes.



DTCFTS2608I Parameter not specified forVMFILETYPEDEFAULT statement

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The VMFILETYPEDEFAULT statement was specified,but a LINES or TRANSLATE parameter has not beenincluded.


User or Operator Response: Review the TCPIP DATAfile and modify the VMFILETYPEDEFAULT statementto include a LINES or TRANSLATE parameter (or both)that defines default line or translation characteristics.Alternatively, delete the currentVMFILETYPEDEFAULT statement if the default lineand translation characteristics for this statement areacceptable. For detailed information about theVMFILETYPEDEFAULT statement, see TCP/IP Planningand Customization.



FTP Messages


||||

|

|||||

|

|

||||

|

|||||

|

|||||

|

|

||||

|

||||||

|

|||||

|

|

|

||||

|

||

|

|||||

|

|

|||

|

||

|

|||||

|

|

|||

|

||||

|

||||||||||

|

|

DTCFTS2609I Extension not specified forVMFILETYPE statement

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.A VMFILETYPE statement has been specified for whicha file extension (file type) has not been included.


User or Operator Response: Review the TCPIP DATAfile and modify the VMFILETYPE statement that is inerror to include (at a minimum) a file extensionparameter. For detailed information about theVMFILETYPE statement, see TCP/IP Planning andCustomization.



DTCFTS2610I {LINES | TRANSLATE} parameterspecified for VMFILETYPEDEFAULTstatement cannot be repeated

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The listed LINES or TRANSLATE parameter has beenspecified more than once for theVMFILETYPEDEFAULT statement that defines defaulttranslation characteristics. Parameters cannot berepeated for this statement.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPEDEFAULT statementthat is in error. For detailed information about thisstatements, see TCP/IP Planning and Customization.



DTCFTS2611I {LINES | TRANSLATE} parameterspecified for VMFILETYPE extensionstatement cannot be repeated

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The listed LINES or TRANSLATE parameter has beenspecified more than once for the VMFILETYPEstatement that defines translation characteristics for theindicated file extension. Parameters cannot be repeatedfor these statements.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPE statement that is inerror. For detailed information about this statement, seeTCP/IP Planning and Customization.



DTCFTS2612I {LINES | TRANSLATE} parametersyntax is not correct forVMFILETYPEDEFAULT statement;delimiter '=' is missing

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The listed LINES or TRANSLATE parameter has beenspecified but the indicated delimiter has not beenincluded. The parameter in error has been specified aspart of the VMFILETYPEDEFAULT statement thatdefines default translation characteristics.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPEDEFAULT statementthat is in error. Ensure that an equal sign (=) is used toseparate the LINES parameter keyword from itscorresponding value. Also, ensure that no spaces areincluded when LINES or TRANSLATE parameters andvalues are specified. For detailed information aboutthese statements, see TCP/IP Planning and Customization.



DTCFTS2613I {LINES | TRANSLATE} parametersyntax is not correct for VMFILETYPEextension statement; delimiter '=' ismissing

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The listed LINES or TRANSLATE parameters havebeen specified but the indicated delimiter has not beenincluded. The parameter in error has been specified aspart of the VMFILETYPE statement that definestranslation characteristics for the indicated file extension.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPE statement that is inerror. Ensure that an equal sign (=) is used to separatethe TRANSLATE parameter keyword from itscorresponding value. Also, ensure that no spaces areincluded when LINES or TRANSLATE parameters andvalues are specified. For detailed information aboutthese statements, see TCP/IP Planning and Customization.



FTP Messages


|||

|

|||

|

||||||

|

|

||||

|

||||||

|

||||

|

|

||||

|

||||||

|

||||

|

|

|||||

|

||||||

|

||||||||

|

|

|||||

|

||||||

|

||||||||

|

|

|||

DTCFTS2614I VMFILETYPEDEFAULT statementsyntax is not correct; delimiter 'delimiter'is not valid

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The indicated delimiter is not supported for use withthe LINES or TRANSLATE parameters. Theseparameters are associated with theVMFILETYPEDEFAULT statement that defines defaulttranslation characteristics.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPEDEFAULT statementthat is in error. For detailed information about thesestatements, see TCP/IP Planning and Customization.



DTCFTS2615I VMFILETYPE statement syntax is notcorrect; delimiter ' delimiter' is not valid

Severity: Error.

Explanation: An error exists in the TCPIP DATA file.The indicated delimiter is not supported for use withthe LINES or TRANSLATE parameters. Theseparameters are associated with the VMFILETYPEstatement that defines translation characteristics for theindicated file extension.


User or Operator Response: Review the TCPIP DATAfile, and correct the VMFILETYPE statement that is inerror. For detailed information about these statements,see TCP/IP Planning and Customization.



DTCFTS2622I VMFILETYPE extension FileExttruncated to eight characters


Explanation: The indicated file extension is longerthan eight characters, therefore it has been truncated.The maximum length of a file extension defined by theVMFILETYPE statement in the TCPIP DATA file iseight characters.





DTCFTS2623I Wildcard in middle of file extensionFileExt ignored


Explanation: The specified file extension (defined bythe VMFILETYPE statement in the TCPIP DATA file)contains a wildcard character (’*’) in the middle of thefile extension. Wildcard characters can be used at thebeginning or end of a file extension. When used in themiddle of the file extension, the asterisk is considered aliteral character of the file extension.


User or Operator Response: Specify separateVMFILETYPE statements for each file extensioncovered by the wildcard.



DTCFTS4014E Time Date: ReturnCode

Severity: Error.

Explanation: FTP cannot communicate.

System Action: The time, date, and return code reasonare displayed, and the program discontinuesprocessing.

User or Operator Response: Wait and try again.

Source File: FTSUTIL PASCAL

Procedure Name: CheckResult

DTCFTS4016E Server-FTP Time Date: ReturnCode

Severity: Error.

Explanation: This message implies an error in theserver FTP code.


User or Operator Response: Ask the systemprogrammer for instructions.

System Programmer Response: Contact the IBMSupport Center.



DTCFTS4025I TcpOpen in OpenConnection returnsmessage text

Explanation: The FTP server attempted to open anFTP connection that already exists. The includedmessage text corresponds to a return code value that isassociated with the TcpOpen procedure (which is usedto initiate a TCP connection).

If the open attempt is for an FTP data connection, andthe corresponding FTP control connection already has

FTP Messages


||||

|

||||||

|

||||

|

|

|||

|

||||||

|

||||

|

|

|||

|

|||||

|

|

|

|

|

|||

|

|||||||

|

|||

|

|

||

|

|

|||

|

|

|

||

|

||

|

||

||

|

|

|||

|||||

||

an open data connection, then no further action isrequired. Otherwise, the open attempt fails, and theFTP server issues accompanying error messageFTSRVP020E, after which the FTP server terminates.

System Action: FTP continues.

User or Operator Response: If the open failure is foran FTP control connection, refer to accompanying errormessage(s) to determine a proper course of action toresolve this problem.

DTCFTS4030E TryToSend gets error from TcpFSend:reason

Severity: Error.

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


User or Operator Response: Determine why the stackcannot send data over the connection.


Procedure Name: TryToSend

DTCFTS7001E Server-FTP: Attempt to open log filereturns ReturnCode

Severity: Error.

Explanation: A nonzero return code resulted from anattempted CMS FILEDEF to append to the FTPSERVELOG file.

System Action: The return code reason is listed at theend of the message.

User or Operator Response: Check your VMconfiguration. When you are satisfied that everything iscorrect, resubmit the job request.



DTCFTS7002E Unable to proceed: all possible filemodes in use!

Severity: Error.

Explanation: You have used all available minidiskaccess mode codes. This requires the use of modes Athrough Z. Although the operating system allows theuse of modes A through Z, no meaningful computerprocessing can be accomplished using this CMSconfiguration.


User or Operator Response: You can free at least oneaccessing mode to allow this FTP request to beresubmitted.



DTCFTS7003I Diagnose 88 authorization and Class Bprivilege confirmed


Explanation: The FTP server has Diagnose X’88’ andClass B privileges in order to authenticate FTP serverusers.





DTCFTS7012E TidyFile: FINIS returns ReturnCode

Severity: Error.

Explanation: The listed nonzero return code wasgenerated during an invocation of the AMPXSVC2procedure while performing TidyFile. The procedure iscalled only for a Data connection to clean up the localfile.

System Action: If the DataFile has been opened and isnot yet closed, the procedure closes the file and clearsany related filedef.

User or Operator Response: Correct the problem andtry again.


Procedure Name: TidyFile

DTCFTS7014E Cannot determine z/VM level

Severity: Error.

Explanation: The FTP server tried to determine thelevel of z/VM using the QUERY CPLEVEL command,but the command failed.


User or Operator Response: Try to determine why theQUERY CPLEVEL command might have failed. Ifnecessary, contact your IBM Support Center forassistance.


Procedure Name: GetReleaseLevel

DTCFTS7015E Unsupported z/VM level

Severity: Error.

Explanation: The FTP server is not supported on thelevel of z/VM that is installed.

System Action: System initialization stops.

FTP Messages


||||

|

||||

|||

|

|||

|

||

|

|

|||

|

|||

||

|||

|

|

|||

|

||||||

|

|||

|

|

|||

|

|||

|

|

|

|

||

|

|||||

|||

||

|

|

||

|

|||

|

||||

|

|

||

|

||

|

User or Operator Response: Install a supported levelof z/VM and restart the FTP server.


Procedure Name: GetReleaseLevel

DTCFTS7017I Warning: Cannot setIGNOREincomingPUSH option: reason


Explanation: An error occurred when the FTP servertried to set the IGNOREincomingPUSH option on aconnection. The reason indicates what error occurred.


User or Operator Response: Determine if other errorsoccurred because the IGNOREincomingPUSH optioncould not be set.


Procedure Name: DoFile

DTCFTS7021I IAC Encountered on conn #nn: xxxx


Explanation: An IAC control sequence wasencountered on the control connection numbered nn.The actual command encountered is xxxx, where thefirst byte is the interrupt character (should always bex’FF’) and the second byte is the actual command. Seethe TELNET RFC for details commands.


User or Operator Response: None. This is aninformational message encountered in FTP servertraces.

Source File: FTSCMD PASCAL

Procedure Name: DoCommand()

DTCFTS7022I Command Received on conn #nn:command


Explanation: A FTP command was encountered on thecontrol connection numbered nn of the FTP server. Theactual command encountered is Command, which is theentire command string up to its terminating carriagereturn. This aids in problem diagnosis by indicatingexactly what commands are being received from theconnected FTP clients.


User or Operator Response: None; this is aninformational message encountered in FTP servertraces.



Procedure Name: DoCommand()

DTCFTS7023E FTP server is missing class Bprivileges or diagnose 88 authorization

Severity: Error.

Explanation: The FTP server virtual machine requiresclass B privileges and Diagnose 88 authorization forpassword checking and minidisk links.

System Action: The server program halts at this point

User or Operator Response: Ensure that the FTPserver virtual machine’s user directory entry includesClass B privileges and an OPTION DIAG88 statement.



DTCFTS8004I Link Error: DMSLINK owner addr byuser username returns rc

Severity: Error.

Explanation: CSL routine DMSLINK had a pagingerror attempting to LINK a minidisk.


User or Operator Response: Contact your RACFadministrator to determine the cause of the problem.


Procedure Name: MinidiskLink

DTCFTS8009E DMSLINK Error: VMRDR,Entity=target_user Userid=agent_user,rc=rc

Severity: Error.

Explanation: An error occurred when the FTP servertried to link the agent_user to the target_user virtualreader.

System Action: Program execution continues

User or Operator Response: Use the return code fromthe DMSLINK CSL routine to determine why the erroroccurred. Refer to the z/VM: CMS Callable ServicesReference for return and reason codes.


Procedure Name: CheckRDR

DTCFTS8101I RACROUTE AUTH call returnsSafRc=Safrc, RacfRc=RacfRc,RacfReas=RacfRsc


Explanation: The FTP server used the RACROUTEmacro to determine a user’s SFS authorization, but themacro returned an unknown reason code.

FTP Messages


||

|

|

|||

|

|||

|

|||

|

|

||

|

||||||

|

|||

|

|

|||

|

|||||||

|

|||

|

|

|

|||

|

|||

|

|||

|

|

|||

|

||

|

||

|

|

||||

|

|||

|

||||

|

|

||||

|

|||


User or Operator Response: Use the reason code fromthe RACROUTE macro to determine what erroroccurred. Contact your IBM Support Center forassistance.


Procedure Name: DoQAuth

DTCFTS8104I No CMS Byte File System supportavailable


Explanation: The FTP server attempted to call theBPX1VM5 callable service to notify the BFS servermachine that it should ignore file pool administrationauthority for the FTP server virtual machine (it shoulduse the effective UID and GID values for authoritychecking), but the call has failed. If the FTP server isrunning on z/VM Version 2 Release 1, then APARVM60747 is required in order for FTP to support BFS.

System Action: Server initialization continues with noBFS support available.

User or Operator Response: Try to determine why thecall to the BPX1VM5 function failed, and correct theproblem. If the TRACE parameter was specified whenthe FTP server is started, the debug trace file (FILEDEBUGTRA) on the server’s 191 disk will contain thereturn code information from the call to BPX1VM5.



DTCFTS8105E An error occurred during FTP servertermination while attempting to notifythe Byte File System that it should nowrespect file pool administrationauthority for the FTP server virtualmachine.

Severity: Error.

Explanation: The FTP server attempted to call theBPX1VM5 callable service to notify the BFS servermachine that it should now respect file pooladministration authority for the FTP server virtualmachine, but the call has failed.

System Action: The BFS server will not honor filepool admin authority when determining authorizationlevels for the FTP server virtual machine (it willcontinue to use the effective UID and GID values forchecking authorization).

User or Operator Response: Try to determine why thecall to the BPX1VM5 function failed, and correct theproblem. If the TRACE parameter was specified whenthe FTP server is started, the debug trace file (FILEDEBUGTRA) on the server’s 191 disk will contain thereturn code information from the call to BPX1VM5.


Procedure Name: SystemTerminate

DTCFTS8199E SFSFLAG is on but WorkUnit is zero;System Error.

Severity: Error.

Explanation: An internal error occurred.


User or Operator Response: Close the currentconnection and issue the Open command to re-establishthe connection.


Procedure Name: DoCwd

DTCFTS8400I You are not authorized to issuecommands to this server

Severity: Error.

Explanation: The FTP server SMSG interface is forprivileged users only. Your user ID must be included inthe TCPIP OBEY list for your SMSG commands to berecognized by the FTP server.



Source File: FTSEVEN

Procedure Name: SMSGEvent

DTCFTS8502I Load of FTPExit failed, RC = rc

Severity: Error.

Explanation: The load of the FTP user exit, FTPEXIT,has failed with the indicated return code from the VMSLOAD command. Any exit routine loaded by theprocedures listed below remains in storage.


User or Operator Response: Correct the problem andtry loading the exit again. Either restart the server oruse the SMSG FTPEXIT RELOAD command.

Source File: FTSVMSUB, FTSEVEN

Procedure Name: SystemInitialize, DoReload

DTCFTS8505I FTPEXIT: Unexpected return, type =ExitType, rc = rc

Severity: Error.

Explanation: The Ftp server exit (FTPEXITASSEMBLE) returned to the server with a return codeother than 0, 4, 8, or 12.


FTP Messages


|

||||

|

|

|||

|

||||||||

||

||||||

|

|

|||||||

|

|||||

|||||

||||||

|

|

|||

|

|

|

|||

|

|

|||

|

||||

|

|

|

|

||

|

||||

|

|||

|

|

|||

|

|||

|

User or Operator Response: Review the FTPEXITASSEMBLE file and correct the problem; thenreassemble and reload the FTPEXIT routine.

Source File: FTSVMSUB, FTSCMD

Procedure Name: CallFTPexit, DoCommand

DTCFTS8509I FTPExit has been reloaded at addressby user


Explanation: The FTPExit has been successfullyreloaded at the specified address because the specifieduser submitted the FTP server SMSG FTPEXITRELOAD command.




Procedure Name: DoReload

DTCFTS8512E Reload of FTPExit by user failed, RC= rc

Severity: Error.

Explanation: An error occurred when the FTP servertried to reload the FTPExit in response to an FTP serverSMSG FTPEXIT RELOAD command submitted by thespecified user.


User or Operator Response: Use the return code fromthe LOAD instruction to determine why the erroroccurred. If necessary, contact your IBM Support Centerfor assistance.


Procedure Name: DoReload

FTP Server Unnumbered MessagesThis section contains the unnumbered FTP server messages. Messages in thissection do not contain headers as headers would not be seen when they are issued.

AUTOTRANS setting setting is not valid

Severity: Error.

Explanation: The indicated type of automatictranslation setting is not valid for the FTP server SMSGAUTOTRANS command. Valid automatic translationsettings are ON and OFF.

System Action: The default server automatictranslation setting is not changed.

User or Operator Response: Issue a valid FTP serverSMSG AUTOTRANS command specifying a validautomatic translation setting.


Procedure Name: DoAutoTrans

Cannot drop connection conn_num - data connection

Severity: Error.

Explanation: The indicated connection numberrepresents a data connection and cannot be dropped.




Procedure Name: DoDrop

Cannot release filemode fm - reserved by the server

Severity: Error.

Explanation: The SMSG RELEASE command was

received but the file mode specified is reserved forserver use and cannot be released/detached using thiscommand.




Procedure Name: DoRelease

Connection conn_num has already been dropped.Cannot drop connection conn_num - no user or

active user.

Severity: Error.

Explanation: No active connection exists with theindicated connection number.





Currently processing PUT to reader. Cannot changereader filemode

Severity: Error.

Explanation: The FTP server RDR file mode cannot bechanged while the FTP server is processing a PUT to areader directory.


FTP Messages


|||

|

|

|||

|

||||

|

|

|

|

|||

|

||||

|

||||

|

|

|

User or Operator Response: Wait until the FTP serveris finished processing the PUT to a reader directory andreissue the FTP server SMSG RDRmode command. Ifthe problem persists, contact your IBM Support Centerfor assistance.


Procedure Name: DoRDR

Currently processing PUT to reader. Cannot disablePUT to reader support.

Explanation: The FTP server PUT to reader filesupport cannot be changed while the FTP server isprocessing a PUT to a reader directory.


User or Operator Response: Wait until the FTP serveris finished processing the PUT to a reader directory andreissue the FTP server SMSG RDRmode OFF command.If the problem persists, contact your IBM SupportCenter for assistance.



Filemode fm on RDRmode statement is not valid ornot writable

Severity: Error.

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


User or Operator Response: Issue an SMSGRDRmode command that specifies a valid file modethat is accessed by the FTP server in read/write status.



FTP connection number conn_num is invalid.No connection number specified

Severity: Error.

Explanation: The indicated number is not aconnection number associated with any connectionsbeing managed or used by the FTP server, or noconnection number was specified.

System Action: None

User or Operator Response: Reissue your commandwith an appropriate connection number specified.



Invalid filemode fm specified.Filemode fm not accessed by the server.

Severity: Error.

Explanation: The SMSG RELEASE command wasreceived but the file mode was not a valid file mode oris not currently accessed by the FTP server.


User or Operator Response: Issue SMSG QUERYACCESSED command to obtain a list ofdisks/directories currently accessed by the FTP server.Then reissue the SMSG RELEASE command with avalid file mode specified.



List format list_format is not valid

Severity: Error.

Explanation: The indicated type of list format is notvalid for the FTP server SMSG LISTFORMATcommand. Valid list format types are VM and UNIX.

System Action: The default server list format is notchanged.

User or Operator Response: Issue a valid FTP serverSMSG LISTFORMAT command specifying a valid listformat type.


Procedure Name: DoListFormat

No filemode specified

Severity: Error.

Explanation: The SMSG RELEASE command wasreceived but no file mode was specified.


User or Operator Response: Issue the SMSGRELEASE command with an appropriate file modespecified.



No list format specified

Severity: Error.

Explanation: The FTP server SMSG LISTFORMATcommand require a list format to be specified, but nolist format was given. Valid list format types are VMand UNIX.

System Action: The default server list format is notchanged.

FTP Messages


User or Operator Response: Issue a valid FTP serverSMSG LISTFORMAT command specifying a valid listformat type.



No such user user can be foundNo active user can be found

Severity: Error.

Explanation: The user specified is not currently anactive FTP user or there are no active FTP users at thistime.




Procedure Name: DoQueryUser

REFresh must be followed by VMFiletype keyword

Severity: Error.

Explanation: The FTP server SMSG REFresh commandmust have the VMFiletype keyword given.


User or Operator Response: Issue the SMSG REFreshVMFiletype command.


Procedure Name: DoRefresh

TIMESTAMP setting setting is not valid

Severity: Error.

Explanation: The indicated type of time stamp setting

is not valid for the FTP server SMSG TIMESTAMPcommand. Valid time stamp settings are ON and OFF.


User or Operator Response: Issue a valid FTP serverSMSG TIMESTAMP command specifying a valid timestamp setting.



TIMESTAMP setting was not specified

Severity: Error.

Explanation: The FTP server SMSG TIMESTAMPcommand requires a valid time stamp setting to bespecified. Valid time stamp settings are ON and OFF.


User or Operator Response: Issue a valid FTP serverSMSG TIMESTAMP command specifying a valid timestamp setting.



Too many parameters on RDRmode command

Severity: Error.

Explanation: An FTP server SMSG RDRmodecommand was issued specifying too many parameters.


User or Operator Response: Issue a valid SMSGRDRmode command.



FTP Client Numbered MessagesThis section contains the numbered FTP client messages.

DTCFTC0005E Unable to use TCP: reason

Severity: Error.

Explanation: An error occurred when the FTP clienttried to begin using TCP/IP services. The reasonindicates what error occurred.

System Action: Command execution stops.

User or Operator Response: Ensure that the TCP/IPserver is running and retry the FTP command.

Source File: FTMAIN PASCAL


DTCFTC0006E Error in init: Handle returnsReturnCode

Severity: Error.

Explanation: Program initialization was unsuccessful.

System Action: FTMAIN is exited.

User or Operator Response: Check the return codes,correct your input, and resubmit the job.



FTP Messages


|

|||

|

|||

|

||

|

|

|||

|

|

|

||

|

|

DTCFTC0015E Missing parm after TRANSLATE

Severity: Error.

Explanation: The FTP command TRANSLATE optionrequires a translation table file name.

System Action: Command execution continues.

User or Operator Response: To specify a non-standardtranslation table file, quit out of the FTP command andre-issue the FTP command with the TRANSLATEoption giving a translation table file name.

Source File: FTPROCS PASCAL

Procedure Name: GetOptions

DTCFTC0018E FTP: Unknown option ’option’

Severity: Error.

Explanation: The FTP command contained thespecified unsupported option.


User or Operator Response: If needed, quit out of theFTP command and issue an FTP command with asupported option.



DTCFTC0031E Invalid argument string

Severity: Error.

Explanation: A quoted string contains a quote withinthe quoted string. This is not valid.

System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.

User or Operator Response: Enter a valid command.

Source File: FTUTIL PASCAL

Procedure Name: FtpToken

DTCFTC0032E Cannot find closing quote incommand string

Severity: Error.

Explanation: A subcommand was entered with aquoted string but the ending quote could not be found.


User or Operator Response: Enter a validsubcommand containing a quoted string ensuring thatthe closing quote is present.

Source File: FTUTIL PASCAL

Procedure Name: FtpToken

DTCFTC0033E ImageMode: software error

Severity: Error.

Explanation: An internal error has occurred. The callto the ImageMode procedure is not valid.




Procedure Name: ImageMode

DTCFTC0034E ImageMode: can not allocate bufferspace

Severity: Error.

Explanation: The current subcommand cannot beprocessed because the FTP client cannot obtain neededbuffer space.


User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.



DTCFTC0035E ImageMode: svc2 error rc

Severity: Error.

Explanation: An error occurred trying to write to afile using the ampxsvc2 procedure.





DTCFTC0038E Software error: unsupported mode:mode

Severity: Error.

Explanation: An internal error occurred. TheAsciiToRecord procedure was called with anunsupported transfer type.

FTP Messages


||

|

||

|

||||

|

|

||

|

||

|

|||

|

|

||

|

||

|||

|

|

|

|||

|

||

|||

|||

|

|

||

|

||

|||

||

|

|

|||

|

|||

|||

||||

|

|

||

|

||

|||

||

|

|

|||

|

|||




Procedure Name: AsciiToRecord

DTCFTC0039E Software error: not connection

Severity: Error.

Explanation: An internal error occurred. While usingstream mode, either the source for a GET is not aconnection or the destination for a PUT is not aconnection.




Procedure Name: AsciiToRecord, RecordToAscii

DTCFTC0040E Cannot allocate buffer space

Severity: Error.

Explanation: An error occurred when the FTP clienttried to allocate buffer space to perform the GETsubcommand in stream mode.





DTCFTC0041E CMS write error rc

Severity: Error.

Explanation: An error occurred attempting to use theFSWRITE macro to write to a file.


User or Operator Response: Use the return code fromthe FSWRITE macro to determine what error occurred.For return codes, refer to thez/VM: CMS Macros andFunctions Reference.



DTCFTC0042E Can not find end of record characterin data stream.

Severity: Error.

Explanation: The FTP client cannot determine the endof a record for a file being retrieved from the FTPserver.


User or Operator Response: Ensure the file beingretrieved has the appropriate end of record charactersand reissue the GET subcommand.



DTCFTC0050E Software error: unsupported mode:mode

Severity: Error.

Explanation: An internal error occurred. TheRecordToAscii procedure was called with anunsupported transfer type.




Procedure Name: RecordToAscii

DTCFTC0051E CMS error code rc in LISTFILE

Severity: Error.

Explanation: An error occurred trying to determinethe file mode of a local file.


User or Operator Response: Use the return code fromthe CMS LISTFILE command to determine what erroroccurred.



DTCFTC0052E CMS error code rc in QUERY DISK

Severity: Error.

Explanation: An error occurred trying to determine

FTP Messages


|||

||

|

|

||

|

||||

|||

||

|

|

||

|

|||

|||

||||

|

|

||

|

||

|||

||||

|

|

|||

|

|||

|||

|||

|

|

|||

|

|||

|||

||

|

|

||

|

||

|||

|||

|

|

||

|

|

disk information using the CMS QUERY DISKcommand.





DTCFTC0053E Software error: no mode is availableto reaccess the disk

Severity: Error.

Explanation: When performing a PUT or APPENDfrom the S disk, the FTP client must reaccess the 190disk at a different file mode than S. There were no filemodes available to reaccess the disk.


User or Operator Response: Release a file mode andreissue the PUT or APPEND subcommand.



DTCFTC0054E CMS error code rc in ACCESS

Severity: Error.

Explanation: When performing a PUT or APPENDfrom the S disk, the FTP client must reaccess the 190disk at a different file mode than S. An error occurredwhen the FTP client tried to access a file mode usingthe CMS ACCESS command.

System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues. Refer to the z/VM: CMSCommand and Utility Reference for further assistanc.

User or Operator Response: Use the return code fromthe CMS ACCESS command to determine what erroroccurred.




Severity: Error.

Explanation: An error occurred when the FTP clienttried to allocate buffer space to perform the PUT orAPPEND subcommand in stream mode.

System Action: If the command exit option is in use,

command execution stops; otherwise commandexecution continues.




DTCFTC0056E CMS error code rc

Severity: Error.

Explanation: An error occurred when the FTP clienttried to read data from disk in order to perform a PUTor APPEND.




Procedure Name: RecordToAscii, RecordToBlock

DTCFTC0061E CMS error code rc in RELEASE

Severity: Error.

Explanation: When performing a PUT or APPENDfrom the S disk, the FTP client must reaccess the 190disk at a different file mode than S. An error occurredwhen the FTP client tried to release the file mode usingthe CMS RELEASE command.


User or Operator Response: Use the return code fromthe CMS RELEASE command to determine what erroroccurred. Refer to the z/VM: CMS Command andUtility Reference for further assistance.



DTCFTC0067E Software error: not connection

Severity: Error.

Explanation: An internal error occurred. While usingblock mode, either the source for a GET is not aconnection or the destination for a PUT is not aconnection.


User or Operator Response: Contact your IBM

FTP Messages


||

|||

||

|

|

|||

|

||||

|||

||

|

|

||

|

|||||

||||

|||

|

|

||

|

|||

|

||

||||

|

|

||

|

|||

|||

||

|

|

||

|

|||||

|||

||||

|

|

||

|

||||

|||

|

Support Center for assistance.


Procedure Name: RecordToBlock


Severity: Error.

Explanation: An error occurred when the FTP clienttried to allocate buffer space to perform the PUT orAPPEND subcommand in block mode.




Procedure Name: RecordToBlock


Severity: Error.

Explanation: An error occurred when the FTP clienttried to allocate buffer space to perform the GETsubcommand in block mode.




Procedure Name: BlockToRecord

DTCFTC0081E Notification error: message

Severity: Error.

Explanation: An error occurred while waiting for adata connection to open.

System Action: Command execution continues

User or Operator Response: Use the message todetermine what error occurred. If needed, contact yourIBM Support Center for assistance.


Procedure Name: UntilOpen

DTCFTC0100E CMS return code: rc

Severity: Error.

Explanation: The CMS command entered failed withthe specified return code.


User or Operator Response: Use the return code fromthe CMS command entered to determine what erroroccurred.

Source File: FTCVMSUB PASCAL

Procedure Name: DoCMS

DTCFTC0102E Unknown host: ForeignName

Severity: Error.

Explanation: The foreign host specified on the OPENsubcommand could not be resolved.


User or Operator Response: Specify a known host orIP address on the OPEN subcommand.


Procedure Name: DoConnect

DTCFTC0103E Nonnumeric port designation: port

Severity: Error.

Explanation: A nonnumeric port was specified on theFTP command. If a port is specified on the FTPcommand, it must be a number in the range of 1through 65535.


User or Operator Response: Reissue the FTPcommand specifying a valid numeric port.



DTCFTC0104E Port number too large: port

Severity: Error.

Explanation: The port number specified on the FTPcommand is too large. The port number must be anumber in the range of 1 through 65535.


FTP Messages


|

|

|

||

|

|||

|||

||||

|

|

||

|

|||

|||

||||

|

|

||

|

||

|

|||

|

|

|

||

|

||

|||

|||

|

|

||

|

||

|||

||

|

|

||

|

||||

|||

||

|

|

||

|

|||

|||

User or Operator Response: Reissue the FTPcommand specifying a valid numeric port.



DTCFTC0192E Openfscb: bad mode

Severity: Error.

Explanation: An internal error occurred. TheOpenFscb procedure was called with an invalid mode.




Procedure Name: OpenFscb

DTCFTC0198E In SysClose: GetNextNote returns:message

Severity: Error.

Explanation: An error occurred while waiting for aconnection to close.

System Action: Command execution continues

User or Operator Response: Use the message todetermine what error occurred. If needed, contact yourIBM Support Center for assistance.

Source File: FTSYPRO PASCAL

Procedure Name: SysClose

DTCFTC0203E Error - should not call closefile

Severity: Error.

Explanation: An internal error occurred. The SysCloseprocedure was called with an invalid mode.




Procedure Name: SysClose

DTCFTC0211E GetFromTcp: not a connection

Severity: Error.

Explanation: The FTP client tried to get data from aconnection that is not valid or is not in a valid state.




Procedure Name: GetFromTcp

DTCFTC0254E Could not initiate emulation of ECmode

Severity: Error.

Explanation: This message is output from theSysPrintError procedure just before FTP shutdown.


User or Operator Response: Correct your input andtry again.


Procedure Name: SysPrintError

DTCFTC0260E Cannot perform MPUT, Disk A is full

Severity: Error.

Explanation: The FTP client was attempting to createa temporary file on the A disk in order to process theMPUT and there was not enough space available.

System Action: The MPUT is not processed and theFTP client continues execution.

User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits.


Procedure Name: DoMPUT

DTCFTC0261E Cannot perform MPUT, filemode A isnot accessed or not writable

Severity: Error.

Explanation: The FTP client was attempting to createa temporary file on the A disk in order to process theMPUT but the A disk was either not accessed oraccessed in Read Only mode.


User or Operator Response: Access a Read/Write diskas filemode A then reissue the command.



DTCFTC0262E Cannot perform MPUT, LISTFILEcommand failed with a return code rc

Severity: Error.

Explanation: In order to process the MPUT

FTP Messages


||

|

|

||

|

||

|||

||

|

|

|||

|

||

|

|||

|

|

||

|

||

|

||

|

|

||

|

||

|||

||

|

|

|||

|

||

|

||

|

|

||

|

|||

||

|||

|

|

|||

|

||||

||

||

|

|

|||

|

|

subcommand, the FTP client attempted to create atemporary file on the A disk using the LISTFILEcommand with the APPEND option, but the LISTFILEcommand failed with the specified return code.


User or Operator Response: Check the return codefrom the LISTFILE commnd to determine the reason forthe error.



DTCFTC0278E In SysRead: GetNextNote returns:message

Severity: Error.

Explanation: An error occurred while trying to readdata on a connection.


User or Operator Response: Use the message todetermine what error occured. If needed, contact yourIBM Support Center for assistance.


Procedure Name: GetFromTcp, SysRead

DTCFTC0281E Cannot read file, file attributes notavailable.

Explanation: While attempting to transfer a file, thefile attributes are obtained via an internal CMS systemcall. This system call failed, so we were unable totransfer the file. One situation that causes this problemis when the file is in an SFS file pool, the file is ESMprotected, and the SFS CRR server is not running. Apossibility in the case of minidisk files is that theminidisk is corrupted.

System Action: Error messages are issued and thetransfer is aborted.

User or Operator Response: Contact your systemprogrammer or support desk. You may be able to getaround the problem if the file is in an SFS filepool bycopying the file to a minidisk and transferring the filefrom the minidisk.

System Programmer Response: Investigate thecharacteristics of the file to determine why the fileattributes may not be available to the user attemptingthe file transfer.


Procedure Name: RecordToAscii()

DTCFTC0331E In SendToTcp: GetNextNote returns:message

Severity: Error.

Explanation: An error occurred waiting for anotification after sending data to the FTP server.


User or Operator Response: Use the message todetermine what error occurred.


Procedure Name: SendToTcp

DTCFTC0334E In SendToTcp: Server not responding,closing connection.

Severity: Error.

Explanation: The connection timed out while trying tosend data to the FTP server.


User or Operator Response: Determine why theconnection timed out without completing the datatransfer successfully.



DTCFTC0357E Data to be written exceeds maximumfile LRECL; source ASCII file probablylacks record delimiters.

Severity: Error.

Explanation: This message is issued during theprocessing of an FTP GET subcommand where thesource file is in ASCII format and the target file is to beconverted to an EBCDIC format. After receivingnotification that the data transfer was complete, thecode detected that the residual byte count (the numberof bytes that had not yet been written to disk) exceededthe maximum supported LRECL. FTP GET logicprocesses each buffer of data received from TCPIP towrite out each delimited line (delimited by CR-LF) to aseparate file record. This error implies that, after thedata transfer was completed, the data not yet written todisk represented a string whose length was in excess ofthe maximum supported file LRECL (65535).

System Action: The file transfer is aborted. No data iswritten to disk. If FTP had been invoked with the EXIToption, the FTP session is terminated with return code16150. Otherwise, the Command prompt is displayedand FTP awaits the next user subcommand.

User or Operator Response: Ensure that the source

FTP Messages


||||

||

|||

|

|

|||

|

||

|||

|||

|

|

|||

||||||||

||

|||||

||||

|

|

|

|||

|

||

|||

||

|

|

|||

|

||

|||

|||

|

|

||||

|

||||||||||||||

|||||

|

ASCII file has its lines correctly delimited by a CR-LFsequence (as required by the FTP RFC). If the file doesnot have proper line delimiters, update the file toinclude the CR-LF sequence at the end of each line andretransmit the file. An alternative is to reduce the totalnumber of bytes in the source file to be less than orequal to 65535. FTP logic will then process the file asthough it contained a single record. It will be thereceiver’s responsibility to decompose the resultant fileinto records corresponding to the original file structure.



DTCFTC0358E Error storing file: The empty file wasnot stored on the local directory.

Severity: Error.

Explanation: You attempted to transfer a null file andone of the following conditions occurred:

v The target directory is a minidisk and null files arenot supported on minidisks. If there was an existingfile with the same name as the one being transferred,it has been deleted.

v The target system has a backlevel CMS or SFS Serverwhich do not support the commands necessary tocreate the null file. If there was an existing file withthe same name as the one being transferred, anexplicit rollback has occurred and the file will stillexist.



Source File: FTSVMSUB PASCAL, FTPROCS PASCAL

DTCFTC0360E Not authorized to access requestedlocal file.

Severity: Error.

Explanation: You attempted to write to a file in thelocal directory for which you do not have writeauthority.


User or Operator Response: Change to another localdirectory or contact the directory owner to gain properauthorization to the file.



DTCFTC0368E Input Disk or Input Terminal mustbe specified with FILEDEF input.

Severity: Error.

Explanation: An error occurred while using the FTPExec interface. A device was specified with FILEDEFinput that was not DISK or TERMINAL.


User or Operator Response: Specify a device type ofDisk or Terminal and try again.


Procedure Name: InputOutput

DTCFTC0376E Wrong level of CMS: routine notfound

Severity: Error.

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





DTCFTC0391E File transfer aborted. Shortage of diskspace

Severity: Error.

Explanation: The file transfer associated with the GETcommand has been aborted because there is notenough space of the local disk to fit the file.


User or Operator Response: Ensure there is enoughspace on the local disk and reissue the GETsubcommand.


Procedure Name: AsciiToRecord, BlockToRecord,ImageMode

DTCFTC0392E File transfer aborted. Input string istoo long

Severity: Error.

Explanation: The data transfer associated with a GETcommand has been aborted because the input buffer istoo large.





FTP Messages


||||||||||

|

|

|||

|

||

||||

||||||

|

|

|

|||

|

|||

|

|||

|

|

|||

|

|||

|

||

|

|

|||

|

||

|

||

|

|

|||

|

|||

|||

|||

|

||

|||

|

|||

|||

||

|

|

FTP Client Unnumbered MessagesThis section contains the unnumbered FTP client messages. Messages in thissection do not contain headers as headers would not be seen when they are issued.

Cannot load HANGEUL translate table file


Explanation: The FTP client 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 isloaded, and program execution continues. Hangeul orKSC5601 DBCS conversion types will be unavailable.

User or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPHGBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



Cannot load KANJI translate table file


Explanation: The FTP client 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 or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPKJBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



Cannot load TCHINESE translate table file


Explanation: The FTP client 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 or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor TCPCHBIN. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



Cannot write to FILEDEF 'OUTPUT DISK' file.

Severity: Error.

Explanation: An OUTPUT DISK OS data set definitionhas been established using a prior FILEDEF command,but his definition cannot be used. When such adefinition exists, FTP dialog output is directed to thenamed CMS file.


User or Operator Response: If necessary, use theQUERY FILEDEF command to display all filedefinitions in effect. Then, verify that the minidisk ordirectory associated with this definition is available,and has been accessed with read/write status. Ifsubcommand output is not to be directed in thismanner, use the FILEDEF CLEAR command to removethe offending definition.


Procedure Name: OpenInputOutput

Data connections will be initiated by the client


Explanation: The PASSIVE subcommand has beenaccepted.

System Action: Data transfers will be performed inpassive mode. Processing continues normally.



Procedure Name: DoPassive

DIR/LS unimplemented in either Block Mode orImage Type


Explanation: While preparing to issue a DIR or LS

FTP Messages


||

||||

|

||||||

|||

|||||

|

|

||

|

||||||

|||

|||||

|

|

||

|

||||||

||||

|||||

|

|

||

|

|||||

|

||||||||

|

|

||

|

||

||

|

|

|

|||

|

|

command, the FTP client attempted to dynamicallyswitch from a transfer mode of Binary to Stream orfrom a data format of Image to ASCII. The switch hasbeen rejected by the foreign host.

System Action: The requested operation is notperformed. If the FTP session was established in batchmode, it is terminated with the reply code and errorcode received from the attempt to reset the mode tostream or the format to ASCII. Otherwise, the″Command:″ prompt is presented and the client waitsfor the next user interaction.

User or Operator Response: In practice, this messageshould never be seen since hosts are required by theFTP RFC to support switching between Binary andStream or Image and ASCII. The failure should bebrought to the attention of your system programmer.As a possible circumvention, try explicitly establishingthe required mode and format using the applicablesubcommands before issuing the DIR or LSsubcommand. The transfer mode and data format canthen be reset after obtaining the requested output.Alternately, it may be possible to obtain the directoryinformation before setting the transfer mode and dataformat.

System Programmer Response: Check the availabledocumentation for any possible prohibitions againstissuing subcommands requiring ASCII format andStream mode while other transfer characteristics are ineffect. If any are found, ensure that your usercommunity is aware of the restrictions and anyapplicable circumvention methods. If there are none,refer the error to the Support organization for theserver code which rejected the dynamic switch.


Procedure Name: GetDIR

FILEDEF 'INPUT DISK' file not found.

Severity: Error.

Explanation: An INPUT DISK OS data set definitionhas been established using a prior FILEDEF command,but no corresponding CMS file for this definition exists.When such a definition exists, FTP relies upon this fileas a source for subcommand input.


User or Operator Response: If necessary, use theQUERY FILEDEF command to display all filedefinitions in effect. Then, verify that a CMS file of theappropriate name exists, and contains the desiredsubcommand input. If subcommand input is not to beobtained in this manner, use the FILEDEF CLEARcommand to remove the offending definition.


Procedure Name: OpenInputOutput

FSENDresponse note shows error: reason


Explanation: An error occurred when trying to senddata to the remote FTP server.


User or Operator Response: Use the reason todetermine what error occurred. If necessary, contactyour IBM Suport Center for assistance.



FTP DATA token CCONNTIME out of range -Default value used.


Explanation: The value for CCONNTIME in the FTPDATA file is not valid.

System Action: FTP client will use the default timeoutvalue for CCONNTIME. Processing continues normally.

User or Operator Response: If necessary, terminatethe FTP session and correct the CCONNTIME keywordvalue in the FTP DATA file.

Source File: FTBVMSUB PASCAL

Procedure Name: ReadVMFtpData

FTP DATA token DATACTTIME out of range -Default value used.


Explanation: The value for DATACTTIME in the FTPDATA file is not valid.

System Action: FTP client will use the default timeoutvalue for DATACTTIME. Processing continuesnormally.

User or Operator Response: If necessary, terminatethe FTP session and correct the DATACTTIME keywordvalue in the FTP DATA file.



FTP DATA token DCONNTIME out of range -Default value used.


Explanation: The value for DCONNTIME in the FTPDATA file is not valid.

System Action: FTP client will use the default timeoutvalue for DCONNTIME. Processing continues normally.

User or Operator Response: If necessary, terminate

FTP Messages


||||

|||||||

|||||||||||||

|||||||||

|

|

||

|

|||||

|

|||||||

|

|

||

|

||

|

|||

|

|

|||

|

||

||

|||

|

|

|||

|

||

|||

|||

|

|

|||

|

||

||

|

the FTP session and correct the DCONNTIME keywordvalue in the FTP DATA file.



FTP DATA token INACTTIME out of range - Defaultvalue used.


Explanation: The value for INACTTIME in the FTPDATA file is not valid.

System Action: FTP client will use the default timeoutvalue for INACTTIME. Processing continues normally.

User or Operator Response: If necessary, terminatethe FTP session and correct the INACTTIME keywordvalue in the FTP DATA file.



FTP DATA token MYOPENTIME out of range -Default value used


Explanation: The value for MYOPENTIME in the FTPDATA file is not valid.

System Action: FTP client will use the default timeoutvalue for MYOPENTIME. Processing continuesnormally.

User or Operator Response: If necessary, terminatethe FTP session and correct the MYOPENTIMEkeyword value in the FTP DATA file.



In ReadVMFtpData: FTP DATA file not available -Default values used


Explanation: No FTP DATA file could be found in theminidisk search order of the user. This message is onlyissued if client tracing is active.

System Action: FTP client will use the default timeoutvalues or the timeout values specified on the TIMEOUTinvocation parameter, if given. Processing continuesnormally.

User or Operator Response: None. If you had createdan FTP DATA file to provide timeout overrides,terminate the FTP session, insure the proper minidisksare accessed, and invoke FTP again to run with thedesired overrides.



In UntilOpen: Passive Open for Fd conn Timeout


Explanation: The timer associated with a dataconnection expired while waiting for the connection toopen.

System Action: The data connection is aborted andcommand execution continues.

User or Operator Response: Determine why the dataconnection to the remote server could not be openedwithin the timeout period.


Procedure Name: UntilOpen

Invalid local file name FileName; Use name.type .modeor name.type

Severity: Warning.

Explanation: User warning instructing you aboutimproper usage of the Use instruction.


User or Operator Response: Follow the Useinstructions.

Source File: FTPROCS PASCAL, FTSYPRO PASCAL

Procedure Name: DomPut

Local file not found or cannot be accessed

Severity: Error.

Explanation: An attempt to locate a local file on anaccessed disk or directory failed for one of thefollowing reasons:

v The file does not exist.

v For SFS directory files, you do not have read or writeauthority for the file.


User or Operator Response: Verify that the file namewas specified correctly and that the file is located on anaccessed disk or directory, then reissue the command.

If the file is stored in an SFS directory, use the CMSQUERY AUTHORITY command to verify that properaccess authorization has been granted for this file.

Source File: FRSYPRO PASCAL


Logon prompting disabled, quitting application.

Severity: Error.

Explanation: The NOPROMPT option has disabledprompts for user name and password values and noNETRC DATA file entry was found that matches the

FTP Messages


||

|

|

|||

|

||

||

|||

|

|

|||

|

||

|||

|||

|

|

|||

|

|||

||||

|||||

|

|

||

|

|||

||

|||

|

|

|||

|

||

|

||

|

|

||

|

|||

|

||

|

|||

|||

|

|

||

|

|||

host specified as part of your command.


User or Operator Response: Ensure the NETRC DATAfile contains an entry for the target host when theNOPROMPT option is used. If you wish to beprompted for a user name and password, omit thisoption when the FTP command is issued.

Source File: FTMAIN


TimeOut value out of range. Must be between 15 and720. Default Used.


Explanation: The Timeout value specified on theinvocation of FTP was not valid.

System Action: FTP client will use the default timeoutvalues. Processing continues normally.

User or Operator Response: If necessary, terminatethe FTP session and invoke FTP again with aTIMEOUT value between 15 and 720.

Source File: FTPARSE PASCAL


TimeOut xx is not a numerical number. Default Used.


Explanation: The Timeout value specified on theinvocation of FTP was not valid.

System Action: FTP client will use the default timeoutvalues. Processing continues normally.

User or Operator Response: If necessary, terminatethe FTP session and invoke FTP with a TIMEOUTvalue between 15 and 720.



Unable to determine TCP/IP buffer size; default = 8K.


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





Unknown Translate table table specified in FTP DATAfile - token ignored


Explanation: An unsupported translate table namewas specified on the LOADDBCSTABLE statement inthe FTP DATA file. The statement is ignored.


User or Operator Response: If needed, quit out of theFTP command, ensure that the LOADDBCSTABLEstatement is correct, and reissue the FTP command.



Unknown Token token in FTP DATA file - TokenIgnored.


Explanation: Processing of the FTP DATA fileencountered a keyword that is not valid. The valueidentified in the text of the message is the token thatwas taken as the incorrect keyword.

System Action: FTP client will continue processing.Valid timeout values encountered in the FTP DATA filewill be used. All other timeout thresholds will be set totheir default values.

User or Operator Response: If the error was due to anincorrect spelling of one of the supported keywords,terminate the FTP session and correct the entry in theFTP DATA file. If the line identified in the message isnot intended to be interpreted as a keyword, modifythe line so that it begins with a comment delimiter (asemicolon).



Usage: HANGEUL <(NOTYPE>Usage: HANGEUL <(NOTYPE>

change file transfer type to Hangeul


Explanation: Either help for the FTP client HANGEULsubcommand was requested, or an invalid FTP clientHANGEUL subcommand was entered.

System Action: Program execution continues. Thecurrent FTP transfer type is unchanged.

User or Operator Response: Use the help informationto enter a valid HANGEUL subcommand. See theTCP/IP User’s Guide book for more information aboutusing FTP client subcommands.


Procedure Name: DoHelp or DoTypes

FTP Messages


|

|

|||||

|

|

|||

|

||

||

|||

|

|

||

|

||

||

|||

|

|

||

|

|||

|

|

|

|

|

|||

|

|||

|

|||

|

|

|||

|

||||

||||

|||||||

|

|

||||

|

|||

||

||||

|

|

Usage: JIS83KJ <(<ASCII | JISROMAN><NOTYPE>>Usage: JIS83KJ <(<ASCII | JISROMAN><NOTYPE>>

change file transfer type to JIS 1983 Kanji


Explanation: Either help for the FTP client JIS83KJsubcommand was requested, or an invalid FTP clientJIS83KJ subcommand was entered.


User or Operator Response: Use the help informationto enter a valid JIS83KJ subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.



Usage: JIS78KJ <(<ASCII | JISROMAN><NOTYPE>>Usage: JIS78KJ <(<I | JISROMAN>TYPE>>

change file transfer type to JIS 1978 Kanji


Explanation: Either help for the FTP client JIS78KJsubcommand was requested, or an invalid FTP clientJIS78KJ subcommand was entered.


User or Operator Response: Use the help informationto enter a valid JIS78KJ subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.



Usage: KSC5601 <(NOTYPE>Usage: KSC5601 >(NOTYPE>

change file transfer type to KSC5601


Explanation: Either help for the FTP client KSC5601subcommand was requested, or an invalid FTP clientKSC5601 subcommand was entered.


User or Operator Response: Use the help informationto enter a valid KSC5601 subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.



Usage: TCHINESE <(NOTYPE>Usage: TCHINESE <(NOTYPE>

change file transfer type to Traditional Chinese


Explanation: Either help for the FTP client TCHINESEsubcommand was requested, or an invalid FTP clientTCHINESE subcommand was entered.


User or Operator Response: Use the help informationto enter a valid TCHINESE subcommand. See theTCP/IP User’s Guide book for more information aboutusing FTP client subcommands.



Usage: TYPE {A | E | I | F <1> | B <1|2|3 <A|R>|4<A|R>|5|6|7>}


Explanation: Either help for the FTP client TYPEsubcommand was requested, or an invalid FTP clientTYPE subcommand was entered.


User or Operator Response: Use the help informationto enter a valid TYPE subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.



Warning: Cannot set IGNOREincomingPUSH option:reason


Explanation: An error occurred when the FTP clienttried to set the IGNOREincomingPUSH option on aconnection. The reason indicates what error occurred.


User or Operator Response: Determine if other errorsoccurred because the IGNOREincomingPUSH optioncould not be set.


Procedure Name: DoTrFile, GetDir

Width ’width’ is not numeric; Default value is in effect


Explanation: The value specified for the WIDTH

FTP Messages


||||||

|

|||

||

||||

|

|

|||||

|

|||

||

||||

|

|

||||

|

|||

||

||||

|

|

||||

|

|||

||

||||

|

|

|||

|

|||

||

||||

|

|

|||

|

|||

|

|||

|

|

||

|

|

option upon command invocation was not a numberbetween 1 and 32767.

System Action: The default WIDTH value (80) is usedby the FTP client. Processing continues.

User or Operator Response: If necessary, terminatethe current FTP session. Then, start a new session forwhich a valid WIDTH value is specified.



Width ’width’ is not within the range 1 to 32767;Default value is in effect


Explanation: The value specified for the WIDTH

option upon command invocation was not a numberbetween 1 and 32767.

System Action: The default WIDTH value (80) is usedby the FTP client. Processing continues.

User or Operator Response: If necessary, terminatethe current FTP session. Then, start a new session forwhich a valid WIDTH value is specified.



FTP Reply Code MessagesThis section contains the reply code messages. Messages in this section do notcontain headers as headers would not be seen when they are issued.

200 Representation type is Hangeul


Explanation: The FTP server has received a validTYPE B 5 command from the FTP client. The currenttransfer type has successfully been changed to HangeulDBCS.

System Action: Program execution continues. Thecurrent FTP transfer type is changed.



Procedure Name: DoType

200 Representation type is KANJI JIS 1978 shift-inASCII


Explanation: The FTP server has received a validTYPE B 4 or TYPE B 4 A command from the FTP client.The current transfer type has successfully been changedto JIS 1978 Kanji DBCS, using the ASCII shift-in escapesequence.





200 Representation type is KANJI JIS 1978 shift-inJISROMAN


Explanation: The FTP server has received a validTYPE B 4 R command from the FTP client. The currenttransfer type has successfully been changed to JIS 1978Kanji DBCS, using the JISROMAN shift-in escapesequence.





200 Representation type is KANJI JIS 1983 shift-inASCII


Explanation: The FTP server has received a validTYPE B 3 or TYPE B 3 A command from the FTP client.The current transfer type has successfully been changedto JIS 1983 Kanji DBCS, using the ASCII shift-in escapesequence.





FTP Messages


||

||

|||

|

|

|||

|

|

||

||

|||

|

|

|

200 Representation type is KANJI JIS 1983 shift-inJISROMAN


Explanation: The FTP server has received a validTYPE B 3 R command from the FTP client. The currenttransfer type has successfully been changed to JIS 1983Kanji DBCS, using the JISROMAN shift-in escapesequence.





200 Representation type is KSC-5601


Explanation: The FTP server has received a validTYPE B 6 command from the FTP client. The currenttransfer type has successfully been changed to KoreanStandard Code KSC-5601 DBCS.





200 Representation type is TChinese


Explanation: The FTP server has received a validTYPE B 7 command from the FTP client. The currenttransfer type has successfully been changed toTraditional Chinese (5550) DBCS.





220 User UserName has Acc_Type authority


Explanation: The message displays the authority levelof the user.


User or Operator Response: This is an informationalmessage from the SITE QAUTH command.


Procedure Name: DoSite

230 Directory userid.RDR does not exist

Severity: Error.

Explanation: The user ID entered is not a valid userID on that system.


User or Operator Response: Correct the user IDportion of the working directory established for youruser ID in CHKIPADR EXEC.



230 System error 24 occured trying to access directory

Severity: Error.

Explanation: Routine DMSLINK returned with areturn code 24. A paging error has occurred.

System Action: A message is written to the FTP serverconsole.

User or Operator Response: Contact your system orRACF administrator.



230 System error occurred setting up a readerdirectory

Severity: Error.

Explanation: An error occurred defining a virtualpunch or issuing a spool command to the target user’sreader.


User or Operator Response: Reissue the commandand if the error reoccurs, contact your TCP/IPadministrator to debug the problem.



230 You are not authorized for userid.RDR

Severity: Error.

Explanation: You do not have the authority to accessthe user’s reader.





FTP Messages


421 No connection to foreign server.

Severity: Warning.

Explanation: The connection may have closed due to aTimeOut or an error may have occurred.

System Action: If you specified the EXIT parameterwhen you entered the FTP environment, FTPterminates. Otherwise, you are prompted for the nextFTP subcommand.

User or Operator Response: Issue an OPEN commandto re-establish a connection to a foreign host.


Procedure Name: DoNoop

425 Can’t open data connection: ReturnCode

Severity: Error.

Explanation: The data connection cannot be opened.

System Action: The return code reason is displayed atthe end of this message.

User or Operator Response: Identify the networkproblem, correct it, and resubmit the job.


Procedure Name: DoList

450 Delete failed, another user has the dircontroldirectory accessed R/W.

Severity: Error.

Explanation: Only one user at a time can have adirectory control directory accessed in read/writemode. When another user has a directory accessed inread/write mode, you cannot change files in thatdirectory, even if you are authorized to do so.


User or Operator Response: Enter the QUERYACCESSORS command to find if a user is accessing thedirectory R/W. If so, contact this user to release thedirectory, and enter the command again.

Source File: FTSCMD PASCAL, FTSVMSUB PASCAL

Procedure Name: DoRnto, DoDelete; DoFile

450 Directory is temporarily unavailable, SFSdirectory lock detected.

Severity: Error.

Explanation: The FTP Server is unable to issue CMSACCESS for the directory.


User or Operator Response: Try to enter thecommand a few more times. if the lock persists, try to

resolve the lock conflict. Enter the QUERY LOCKcommand to find out which user is holding the lock.


Procedure Name: FindMode, DoList

450 Disk access fails; you no longer have any workingdirectory

Severity: Error.

Explanation: When RACF is specified, only a readlink is attempted to avoid extraneous NOTIFYmessages sent to the owner of the minidisk in case thewrite LINK, which the user may not even want, isdenied.


User or Operator Response: The working directoryminidisk is not in write mode access. Correct thesituation and try again.


Procedure Name: DoAcct

450 Insufficient resources to process requested action

Severity: Error.

Explanation: At the time your request (subcommand)was received, the FTP server was not able to gainaccess to the appropriate minidisk or SFS directory;thus, the supplied subcommand could not beprocessed. This situation may arise when the FTPservices for the host in question are being heavily used.


User or Operator Response: Wait for a while, thenreissue the subcommand for which this reply wasreturned. If the problem persists, contact the z/VMhost system administrator.


Procedure Name: FindMode

450 Minidisk temporarily unavailable

Severity: Error.

Explanation: The system cannot access the VMminidisk containing the working directory. Thistemporary problem is probably caused by VMperformance.


User or Operator Response: Wait for a while and tryagain.



FTP Messages


450 Minidisk unexpectedly inaccessible

Severity: Error.

Explanation: This VM system problem is probablycaused by multiple, concurrent, minidisk accessrequests. The working directory minidisk cannot bere-accessed.





450 No current working directory defined

Severity: Error.

Explanation: You must define a working directory forFTP processing.


User or Operator Response: Define a workingdirectory before proceeding.



450 Rename failed, another user has the dircontroldirectory accessed R/W.

Severity: Error.






450 Store failed, another user has the dircontroldirectory accessed R/W.

Severity: Error.






450 Store failed, filepool is unavailable.

Severity: Error.

Explanation: The file pool provided on the command,or the file pool allowed to default on the command, iseither incorrect or unavailable.


User or Operator Response: Check to see if the filepool was allowed, then contact your system supportpersonnel to determine the status of the file pool.



450 Store failed, unable to access the directory.

Severity: Error.

Explanation: The FTP Server cannot access the SFSdirectory.


User or Operator Response: Make sure you areauthorized for the file pool and determine the status ofthe file pool.



450 System error occurred trying to determine BFSauthorization

Severity: Error.

Explanation: The FTP server virtual machineattempted to call the BPX1SEU callable service and theBPX1SEG callable service to set the effective UID andGID of the server to that of the logged in user, but thecall failed.

System Action: The FTP server cannot perform BFSactivities without being able to set the effective UIDand GID. Any attempts to access BFS information willresult in this error).

User or Operator Response: Make sure that the FTPserver has been given a UID value of zero in the VMuser directory (this is done using a ″POSIXINFO UID0″ statement).

Source File: FTSVMSUB PASCAL, FTSUTIL PASCAL,FTSEVEN PASCAL

FTP Messages


Procedure Name: DoSite, DoFile, CDtoBFS, SendData,DataArrivedEvent

450 Write access temporarily unavailable for directorydirectory, try again.

Severity: Error.

Explanation: You attempted to write to a file in adirectory control directory for which there areconcurrent transfer requests.





451 Data transfer aborted: file is locked.

Severity: Error.

Explanation: Return code 70 trying to write to the file;file is locked.


User or Operator Response: Try to reissue thecommand a few times. If the lock persists, try toresolve the lock conflict. Enter the QUERY LOCKcommand to find out which user is holding the lock.


Procedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent

451 Data transfer aborted: not authorized to write tofile

Severity: Error.

Explanation: You attempted to write to a file forwhich you do not have write authority, or youattempted to create a new file in a directory for whichyou do not have write authority.


User or Operator Response: Change to anotherdirectory or contact the directory owner to gain properauthorization to the file or directory.


Procedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent,NewConnectionEvent

451 Error closing BFS data set. System error.

Severity: Error.

Explanation: BFS System Error.


User or Operator Response: Retry the command. Ifthe problem persists, contact your system supportpersonnel.


Procedure Name: DataReply

451 Error closing data set. File not open or invalid ornot authorized

Severity: Error.

Explanation: Error occurred on the CMS FINIScommand. File was not found.





451 Error closing SFS data set. Rollback performed

Severity: Error.

Explanation: SFS Error occurred closing one or moreSFS files.

System Action: A rollback has occurred. Additionally,some updates to non-recoverable files were notcommitted during the rollback.

User or Operator Response: Retry the command. Ifthe problem persists contact your system supportpersonnel.



451 Error closing SFS data set. System error.

Severity: Error.

Explanation: SFS System Error.





451 Error closing SFS data set. System limit exceeded.

Severity: Error.

Explanation: System limits were exceeded whenattempting to commit the changes.

FTP Messages


System Action: The SFS work unit was rolled back.

User or Operator Response: Contact you systemsupport personnel.



451 Error writing or closing reader file.

Severity: Error.

Explanation: An error occurred trying to write to orclose a spool file.





451 Transfer aborted: file not found, disk notaccessed, or insufficient authority.

Severity: Error.

Explanation: Bad return code encountered whilereading the file.


User or Operator Response: Check to make sure filewas specified correctly and issue SITE QAUTH to makesure you have the proper authority.


Procedure Name: Senddata

451 Unexpected software error

Severity: Error.

Explanation: This descriptive message indicates that anonzero return code was generated during theexecution of a CMS STATE command. An expectedEXEC program is missing from the disk.


User or Operator Response: Tell the systemprogrammer about the problem.



451 Unexpected system error

Severity: Error.

Explanation: This message indicates that a nonzeroreturn code was generated during the processing of anFTP server request. None of the built-in error checking

functions could determine the cause of the problem.





452 The disk used to temporarily store reader fileshas insufficient space available

Severity: Error.

Explanation: An error occurred trying to STOR a fileto a VM reader.


User or Operator Response: Contact your systemadministrator to increase the size of the disk identifiedon the RDR startup parameter.



500 Unknown command

Severity: Error.

Explanation: You entered an unrecognizablecommand.


User or Operator Response: Examine your inputsyntax to identify and correct your error.



501 ACCT not allowed with SFS or BFS directories

Severity: Error.

Explanation: An account command was entered whilethe current working directory is set to an SFS or BFSdirectory. The ACCT command is only valid withminidisks.


User or Operator Response: In order to use the ACCTcommand, the current working directory must bechanged to a minidisk using the CWD command.



FTP Messages


501 Directory userid.RDR does not exist;Directory remains old_directory

Severity: Error.

Explanation: The user ID entered is not a valid userID on that system.


User or Operator Response: Correct the user ID andreenter the command.


Procedure Name: CDtoRDR

501 Error occurred attempting to purge spool filennnn, rc=rc

Severity: Error.

Explanation: An error occurred on the CP PURGEuserid RDR spool ID command.


User or Operator Response: Check the return codeand determine the reason for the error.

Source File: FTSCMD

Procedure Name: DoDelete

501 Invalid BYUSER name in USER command501 BYUSER name is missing from USER

command

Severity: Error.

Explanation: BYUSER name was specified an asterisk(*) or was missing from the USER command.


User or Operator Response: Correct the syntax andreenter the command.

Source File: FTSCMD

Procedure Name: DoUser

501 Invalid character in file name BadFileName

Severity: Error.

Explanation: You have made a syntax error in thelisted file name identifier.


User or Operator Response: Correct your syntax andresubmit the job.



501 Invalid directory supplied

Severity: Error.

Explanation: The account command failed becauseyou requested a working directory that is not valid.


User or Operator Response: Check your input logicand syntax, then resubmit the command.



501 Invalid file identifier; use ‘name.type’

Severity: Error.

Explanation: You entered an incorrect file type andthe file type is not set to the default.


User or Operator Response: Reenter the commandand follow the usage instructions.



501 Invalid file identifier. Use "name.type"

Severity: Error.

Explanation: You entered an incorrect file type andthe file type is not set to the default.


User or Operator Response: Reenter the commandand follow the usage instructions.



501 Invalid spoolid in Delete command

Severity: Error.

Explanation: The spool file ID entered is not valid.



Source File: FTSCMD


501 No minidisk password supplied with ‘ACCT’

Severity: Error.

Explanation: You must enter a password with theaccount command.


FTP Messages


User or Operator Response: Reenter the accountcommand and supply a valid minidisk password.



501 Password missing in PASS command

Severity: Error.

Explanation: You did not enter your password.


User or Operator Response: Enter a valid passwordfor the user ID requested.



502 Command failed. You are not authorized to viewor delete files

Severity: Error.

Explanation: The subcommand entered was for a VMreader directory, to which you are not authorized.


User or Operator Response: Login as the user whoseVM reader you wish to manipulate.


Procedure Name: DoList, DoDelete

502 Command not supported for VM reader files

Severity: Error.

Explanation: The subcommand entered is notimplemented for VM reader files.


User or Operator Response: Use Telnet instead of FTPto manipulate VM reader files.

Source File: FTSCMD, FTSVMSUB

Procedure Name: DoRnFr, DoCwd, DoFile

502 Support for STOR to VM reader is not enabled.

Severity: Error.

Explanation: The FTP server was started without theRDR parameter, which is necessary for STORcommands to a VM reader.


User or Operator Response: Use Telnet instead of FTPto manipulate VM reader files or contact the systemadministrator to enable FTP reader support.



502 text

Severity: Error.

Explanation: The FTP user exit has rejected thesubcommand. text provides more information about theerror.



Source File: FTSCMD, FTSVMSUB

Procedure Name: DoCommand, CallFTPexit

503 Your InterNet Address is not allowed forthis server

503 Your UserId is not authorized for this server

Severity: Fatal.

Explanation: The FTP server CHKIPADR exit hasrejected your InterNet Address and user ID.


User or Operator Response: Contact your systemsupport personnel.



504 Block mode implemented with type EBCDIC only

Severity: Error.

Explanation: A file transfer in block mode has beenattempted with a file transfer type of something otherthan EBCDIC.


User or Operator Response: If the file transfer modeis set to block (MODE B), then the file transfer typemust be set to EBCDIC (TYPE E).



504 Type not Supported: Translation Table is notLoaded.


Explanation: The FTP server has received a validDBCS TYPE command from the FTP client, but theDBCS translation table required for that transfer type isnot loaded.


User or Operator Response: Configure a valid DBCS

FTP Messages


binary translate table file in the search order hierarchyfor the required DBCS translation table, and specifyLOADDBCSTABLE in FTP DATA for the requiredDBCS translation table. See the TCP/IP Planning andCustomization book for more information about loadingand customizing DBCS translation tables.



504 Unknown Shift-in option option


Explanation: The FTP server received a TYPE B 3 orTYPE B 4 command from the FTP client containing aninvalid shift-in option. The valid shift-in options forTYPE B 3 (JIS83KJ) and TYPE B 4 (JIS78KJ), are A andR, indicating the ASCII and JISROMAN shift-in escapesequences respectively.


User or Operator Response: Resend the TYPEcommand, specifying a valid shift-in option. See theTCP/IP User’s Guide book for more information aboutusing FTP DBCS TYPE subcommands.



521 Directory already exists, taking no action.

Severity: Error.

Explanation: You specified a MKDIR command for adirectory that already exists.


User or Operator Response: Reissue the MKDIRcommand for a new directory or rename the existingdirectory.


Procedure Name: DoMkDir

530 A system error occurred during passwordvalidation; Login rejected

Severity: Error.

Explanation: An unexpected return code was receivedfrom the password verification routine, DMSPWCHK.Either a paging error occurred or no decision could bemade by ESM.

System Action: A message is displayed on the FTPserver console.




530 Login attempt by UserName rejected530 Login attempt of UserName byByUserName rejected

Severity: Error.

Explanation: You entered an incorrect login or logonpassword.


User or Operator Response: Enter the correct login orlogon password.



530 Login attempt by UserName rejected; passwordexpired

530 Login attempt of UserName by ByUserNamerejected;password expired

Severity: Error.

Explanation: Your login password has expired.


User or Operator Response: You must logon to theVM user ID to change the pasword, it cannot bechanged through FTP.



532 Before action files on Owner Address, you mustsupply the write password using the ACCT command

Severity: Error.

Explanation: An attempt was made to change thecontents of a minidisk, and a write password wasnever supplied. The server tried to obtain write access,supposing that the minidisk might be accessiblewithout the password. That attempt failed and theserver is now advising the client to provide thepassword for the minidisk via the ACCT command.Actions that may cause this message are writing,renaming, or deleting a file on the minidisk when writeauthority has not been established.

System Action: Write access to the minidisk is notallowed. The requested operation fails.

User or Operator Response: Provide a valid minidiskpassword to the server using the ACCT command.


Procedure Name: UpGradeLink

FTP Messages


532 Invalid password; Owner Address remainsReadOnly

Severity: Error.

Explanation: The listed working directory minidisk isaccessed in a read-only mode because you did notenter a correct minidisk password.


User or Operator Response: Enter a valid accountminidisk password.



532 Invalid password; WorkingDirectory

Severity: Error.

Explanation: You entered an incorrect password forthe referenced minidisk working directory.


User or Operator Response: Enter a valid password.



532 Permission denied to LINK to NewOwnerNewAddress

Severity: Error.

Explanation: The account command failed becauseyou did not have RACF authority to write-link thelisted working directory minidisk.


User or Operator Response: Check with your RACFadministrator for the proper authority.



532 Permission denied for write LINK to NewOwnerNewAddress

Severity: Error.

Explanation: The account command failed becauseyou did not have RACF authority to write-link thelisted working directory minidisk.





532 System error 24 occurred trying to access directory

Severity: Error.

Explanation: Routine DMSLINK returned with areturn code 24. A paging error has occurred.



Source File: FTSVMSUB Pascal


550 ACCT fails: WorkingDirectory

Severity: Error.

Explanation: The account command failed becauseyou do not have the proper RACF authority.





550 Attempt to rename ’RnfrBFSFile’ to ’RntoBFSFile’has failed

Severity: Error.

Explanation: An error was encountered by the FTPserver virtual machine while attempting to issue anOPENVM RENAME command to rename a BFS file asspecified by the RENAME command.


User or Operator Response: Use the SITE PERMITcommand to check your current authorization, and tryto determine why the OPENVM RENAME failed.


Procedure Name: DoRnto

550 AUTOTRANS setting setting is not valid

Severity: Error.

Explanation: The indicated automatic translationsetting is not valid for the AUTOTRANS operand. Validsettings are ON and OFF.


User or Operator Response: Specify a valid setting(ON or OFF) when the SITE AUTOTRANSsubcommand is issued.



FTP Messages


550 BFS Directory does not exist or you are notauthorized for it.

Severity: Error.

Explanation: An attempt was made to change thecurrent working directory to a BFS directory that doesnot exist or that you do not have authorization for.


User or Operator Response: Specify an existingdirectory for which you have authorization using theCWD command, or use the MKDIR command to createthe new directory prior to attempting to change thecurrent working directory to it.


Procedure Name: CDtoBFS

550 BFS directory error

Severity: Error.

Explanation: An unusual error was encountered bythe FTP server virtual machine while attempting toissue an OPENVM LISTFILE command in order togenerate the response to a DIR or LS command. Thiserror can be the result of targeting a BFS directory thatcontains other than regular BFS files.


User or Operator Response: Try to understand whythe OPENVM LISTFILE command failed, and correctthe problem. If the TRACE parameter was specifiedwhen the FTP server is started, the debug trace file(FILE DEBUGTRA) on the server’s 191 disk willcontain the bad return code that was received from theOPENVM LISTFILE command.



550 BFS file (’BFSfile’) not found

Severity: Error.

Explanation: The specified BFS file does not exist.


User or Operator Response: The command that wasentered requires a BFS file identifier for an existing file.


Procedure Name: ParseBFSIdentifier

550 Cannot get SFS WorkUnit; directory remainsworking directory

Severity: Error.

Explanation: The FTP Server attempted to get an SFSworkunit and failed. Either no workunit IDs are

available or there is no storage available for associatinga user ID with a workunit.


User or Operator Response: Contact your systemsupport personnel. They may have to re-IPL the FTPserver virtual machine to make some workunits IDsavailable.


Procedure Name: DoCwd, DoPass

550 Command fails; LINK command returnedReturnCode; WorkingDirectory

Severity: Error.

Explanation: You cannot do a write-link to the listedminidisk for the specified reason.


User or Operator Response: Correct your link logic,your syntax, or try another minidisk.



550 Command failed: Directory or file is locked.550 Command failed: The directory is locked.550 Command failed: The file is locked.550 The specified file is locked.550 Unable to send filename file or directory

is locked.

Severity: Error.

Explanation: A lock exists on the file or the directory.


User or Operator Response: Enter the QUERY LOCKcommand to find out which user is holding the lock. Ifthe QUERY LOCK does indicate that a lock is held,contact the user and ask that the lock be deleted.

Source File: FTSVMSUB PASCAL, FTSCMD PASCAL

Procedure Name: FileOk; DoDelete, DoRnto

550 Directory in use and FORCE option was notspecified.

550 Authorities exist on the directory and FORCEwas not specified.

550 An explicit lock is held on the directory orfiles in the directory.

Severity: Error.

Explanation: Bad return code received from the SITEDIRATTR command.


FTP Messages


User or Operator Response: See the z/VM: CMSCommand and Utility Reference for more information onthe DIRATTR command.



550 Error opening file: File has invalid recordformat

550 Error opening file: Insufficient virtual storageavailable

550 Error opening file: APPC/VM error550 Error opening file: File sharing conflict550 Error opening file: A required system resource

is unavailable550 Error opening file: File cannot be opened for

REPLACE. (Code = n)

Severity: Error.

Explanation: The FSOPEN failed when you attemptedto replace an existing file. No data has been written. Ifshown, 'code = n' is the return code from the CMSFSOPEN Macro.


User or Operator Response: Correct the problem andreissue the command or change the command to writea new file, instead of replacing a file.

Source File: FTSVMSUB PASCAL, FTBVMSUBPASCAL

Procedure Name: SOpenFscb, OpenFscb

550 Error rsc reading filename TCPXLBIN from disk ordirectory

Severity: Error.

Explanation: The server was unable to read thetranslate table. The reason code contains the returncode from the failing FSOPEN or FSREAD macro.


User or Operator Response: Try to determine why thespecified translate table could not be read and correctthe problem.


Procedure Name: Initialize, DoSite2

550 FileName does not exist.

Severity: Error.

Explanation: FTP cannot find the file you marked fordeletion on any of the accessed minidisks.


User or Operator Response: Correct your input syntaxand try again.



550 FileName does not exist or you are not authorized.

Severity: Error.

Explanation: FTP cannot find the file you specified oryou do not have authorization to the specified file.


User or Operator Response: Correct your input syntaxand try again. If your current working directory is anSFS directory, issue SITE QAUTH to make sure you areauthorized for the specified file.

Source File: FTSCMD

Procedure Name: DoDelete, DoRnto

550 Format type not specified for SITE LISTFORMAToperand

Severity: Error.

Explanation: The LISTFORMAT operand of the SITEsubcommand was used, but a list format type was notprovided.


User or Operator Response: Specify a valid list formattype (VM or UNIX) when the SITE LISTFORMATsubcommand is issued.



550 FTP Server does not have administrator authorityfor this file pool; directory remains : working directory.

Severity: Fatal.

Explanation: The FTP Server virtual machine does nothave administrator authority to the file pool.


User or Operator Response: Contact your systemsupport personnel.



550 Invalid directory identifier in Site cmd. Use fullyqualified name or "."

Severity: Error.

Explanation: Command syntax was not valid for SiteGrant, Revoke, QDirattr or Dirattr.


User or Operator Response: SITE commands Grant,

FTP Messages


Revoke, QDirattr, Dirattr only accept the fully qualifieddirectory name or ’.’ for the current working directory.Correct the syntax and reissue command.



550 Invalid file identifier in SITE QAUTH cmd. UseSITE QAUTH fn ft.

Severity: Error.

Explanation: The command syntax was incorrect forthe Query Authority command.


User or Operator Response: SITE QAUTH is only forthe current working directory or files within the currentworking directory. Use SITE QAUTH fn ft. Correct thesyntax and reissue command.



550 Invalid filename specified in Site command Use’SITE XLATE filename’

Severity: Error.

Explanation: The SITE XLATE or SITE TRANSLATEcommand syntax was incorrect.




Procedure Name: DoSite2

550 Invalid SITE command; you are not using a BFSdirectory.

Severity: Error.

Explanation: The SITE QPERMIT and the SITEPERMIT commands are only valid when the currentworking directory is set to a BFS directory.


User or Operator Response: Use the CWD commandto set the current working directory to the BFSdirectory you wish to issue the SITE command againstand reissue the command.



550 LISTFORMAT type list_format is not valid

Severity: Error.

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


User or Operator Response: Specify a valid list formattype (VM or UNIX) when the SITE LISTFORMATsubcommand is issued.



550 m1 is not allowed: Owner Address is ReadOnly

Severity: Error.

Explanation: You cannot do a write-link to the listedminidisk because it is accessed in a read-only mode.


User or Operator Response: Correct your link logic ortry another minidisk.


Procedure Name: UpgradeLink

550 MKDIR for BFS failed.

Severity: Error.

Explanation: An unusual error was encountered bythe FTP server virtual machine while attempting toissue an OPENVM CREATE DIR command in order tohonor a MKDIR request.


User or Operator Response: Try to understand whythe OPENVM CREATE DIR command failed, andcorrect the problem.



550 NewOwner New Address is not a validminidisk/directory.

Severity: Error.

Explanation: The minidisk/directory specified was notfound.


User or Operator Response: Check your input syntaxand try again.



FTP Messages


550 One or more files in this directory are open.

Severity: Error.

Explanation: A file or files contained in the targetdirectory was open at the time the RMDIR was issued.


User or Operator Response: Ensure that all files in thetarget directory are closed before the RMDIR commandis issued.


Procedure Name: DoRmDir

550 Parent directory control directory is accessedread-only

550 The directory is accessed read-only.

Severity: Error.

Explanation: You cannot create a subdirectory in adirectory control directory or erase a directory controldirectory that is accessed read-only.


User or Operator Response: Another user currentlyhas the directory control directory accessed read-only.Retry the command later.


Procedure Name: DoMkDir, DoRmDir

550 Parent directory does not exist or you are not theowner of it.

Severity: Error.

Explanation: The MKDIR command is only allowedfor the owner of the parent directory or for a user withadministrator authority.


User or Operator Response: Ensure you havespecified the directory correctly. If you are not anadministrator, make sure you are the owner of theparent directory.



550 Permission denied for write LINK to NewOwnerNewAddress

Severity: Error.

Explanation: A write-link is not allowed to the listedminidisk for an unspecified reason.


User or Operator Response: Correct your link logic ortry another minidisk.



550 Permission denied to LINK to NewOwnerNewAddress;

Severity: Error.

Explanation: A LINK permission rejection occurred.


User or Operator Response: Identify the problem withthe LINK command and try again.



550 Setting not specified for SITE AUTOTRANSoperand

Severity: Error.

Explanation: The AUTOTRANS operand of the SITEsubcommand was used, but an automatic translationsetting was not provided.


User or Operator Response: Specify a valid automatictranslation setting (ON or OFF) when the SITEAUTOTRANS subcommand is issued.



550 SFS directory name format may be wrong;directory remains working directory.

Severity: Error.

Explanation: The specified directory name is notvalid.


User or Operator Response: Check your input syntaxand reenter the command.

Source File: FSTVMSUB PASCAL


550 SFS Error - a lock may be held on the parentdirectory ofnew directory; directory remainsworking directory.

550 SFS Error - a lock may exist on the parentdirectory.

Severity: Error.

Explanation: Currently, you are not allowed to CD to

FTP Messages


a subdirectory of a locked directory.


User or Operator Response: Try to reissue thecommand a few times. If the lock persists, try toresolve the lock conflict.



550 SFS file pool may not exist; directory remains :working directory.

Severity: Error.

Explanation: The file pool provided on the command,or the file pool allowed to default on the command, iseither incorrect or unavailable.


User or Operator Response: Determine the default filepool using the QUERY FILEPOOL CURRENTcommand and contact your system support personnelto determine the status of the file pool.



550 SFS system error; cslname rc x reason y550 SFS System Error; cslname rc x reason y ;

directory remains workingdirectory

Severity: Error.

Explanation: A Shared File System (SFS) error hasbeen encountered by the z/VM FTP server. TheCallable Services Library (CSL) routine (cslname)associated with this error, and its return code andreason code, are indicated in this reply message.


User or Operator Response: Retry the command. Ifthe problem persists, contact your system supportpersonnel. For more information about the return codeand reason code returned by cslname, see the z/VM:CMS Callable Services Reference, (SC24-6004).

Source File: FTSVMSUB PASCAL, FTSCMD PASCAL

Procedure Name: FileOk, DoCwd, DoMkDir,DoRmDir; DoDelete, DoRnto, DoPass

550 Specified directory contains one or moresubdirectories.

Severity: Error.

Explanation: You cannot erase a directory thatcontains a subdirectory.


User or Operator Response: Remove all subdirectories

from the directory you want to erase, then reissue theoriginal RMDIR command.



550 Spool file nnnn does not exist

Severity: Error.

Explanation: The specified spool file was not found,therefore it could not be deleted.


User or Operator Response: Ensure the spool file IDis correct and re-enter the DELETE command.



550 System error 24 occurred trying to access directory

Severity: Error.

Explanation: Routine DMSLINK returned with areturn code 24. A paging error has occurred. A pagingerror has occurred.


User or Operator Response: Contact your system orRACF aministrator.


Procedure Name: DoCwd, UpGradeLink

550 System error occurred setting up a readerdirectory.

Severity: Error.

Explanation: An error occurred defining a virtualpunch or issuing a spool command to the target user’sreader.





550 The Directory is not empty.

Severity: Error.

Explanation: An attempt has been made to erase aBFS directory that is not empty.


User or Operator Response: Remove all files and

FTP Messages


|

|

||

|

||

|

|

subdirectories from the directory you wish to erase andreissue the command.



550 The foreign file was not erased.550 Error storing file: The empty file was not

stored on the foreign host.550 The foreign file has been erased.550 Error storing file: The empty file was not

stored on the foreign host.

Severity: Error.

Explanation: You attempted to transfer a null file andone of the following conditions occurred:

v The target directory is a minidisk and null files arenot supported on minidisks. If there was an existingfile with the same name as the one being transferred,it has been deleted.

v The target system has a backlevel CMS or SFS Serverwhich do not support the commands necessary tocreate the null file. If there was an existing file withthe same name as the one being transferred, anexplicit rollback has occurred and the file will stillexist.



Source File: FTSVMSUB PASCAL, FTPROCS PASCAL

Procedure Name: HandleNullFile

550 The operation was successful but the work unitcould not be committed.

Severity: Error.

Explanation: SFS detected a problem and initiated arollback. There may have been a problemcommunicating with the file pool.


User or Operator Response: Contact your systemsupport personnel to determine the status of the filepool.


Procedure Name: DoRmdir

550 The specified directory does not exist or you arenot authorized to remove it.

Severity: Error.

Explanation: The directory that you specified couldnot be found or you are not authorized for it. Adirectory can only be erased by the directory owner orthe administrator.


User or Operator Response: Ensure you havespecified the correct directory. If you are not anadministrator, make sure you are the owner of thedirectory you are trying to remove.



550 The working directory is empty

Severity: Error.

Explanation: There are no files in the workingdirectory.


User or Operator Response: If this situation istolerable, continue. Otherwise, correct the problembefore resubmitting the job.



550 Translate file filename TCPXLBIN is in an invalidformat

Severity: Error.

Explanation: The translate table was found, but couldnot be loaded because it is not a valid TCP/IP translatefile.


User or Operator Response: Try to determine why thespecified translate table could not be read and correctthe problem.



550 Translate file ’filename TCPXLBIN’ not found

Severity: Error.

Explanation: The server was unable to locate thetranslate table specified.


User or Operator Response: Ensure you havespecified the file name correctly and reenter thecommand.

Source File: FTPRVPA, FTSVMSUB


FTP Messages


550 Unable to append to the Null directory.

Severity: Error.

Explanation: The z/VM FTP server does not allowdata to be appended to a null (*dev.null) workingdirectory; only PUT or MPUT operations are acceptedfor this type of directory. The requested APPENDoperation is not performed.


User or Operator Response: Ensure that only PUT orMPUT subcommands are used to transfer data to a*dev.null working directory. For more informationabout using this type of directory, refer to the UsageNotes associated with the CD or CWD FTPsubcommands in the TCP/IP User’s Guide.


Procedure Name: HandleFileOpen

550 Unable to append to filename550 Unable to append to filename, file or directory

is locked.550 Unable to append to filename, you are not

authorized.550 Unable to append to filename, SFS create file

error.550 Unable to append to filename, virtual storage

capacity exceeded.

Severity: Error.

Explanation: The z/VM FTP server detected an errorwhile attempting to open the indicated SFS or minidiskfile during APPEND processing. Possible causes for thiserror are:v Another user holds an explicit lock on the target SFS

file or directoryv Access to the file has been denied due to lack of

proper authorizationv An attempt to create a new file in the target SFS

directory has failedv An insufficient virtual storage condition has been

detected.


User or Operator Response: Identify the reason forthis failure based on the format of the receivedmessage, then retry the APPEND operation (forexample, after the inhibiting lock has been released, orafter the proper file or directory authorization has beenobtained). If the reason for this error cannot beascertained or an insufficient virtual storage conditionhas been encountered, contact the TCP/IPadministrator of the foreign host in question. Forpersistent problems, detailed information about thereason for this failure can be obtained by tracing FTPserver activity.



550 Unable to append to fixed record format file inImage mode.

Severity: Error.

Explanation: The z/VM FTP server does not allowdata to be appended to existing fixed-length recordformat SFS or minidisk files when the file transferTYPE has been set to Image or Binary. The requestedAPPEND operation is not performed.


User or Operator Response: Use the EBCDIC orASCII subcommand to change the file transfer typefrom Binary or Image to an appropriate transfer type,then retry the APPEND operation.



550 Unable to delete BFS file: ’BFSfile’

Severity: Error.

Explanation: An error was encountered by the FTPserver virtual machine while attempting to issue anOPENVM ERASE command to delete a BFS file thathas been targeted for deletion by a DELETE command.


User or Operator Response: Use the SITE PERMITcommand to check your current authorization, and tryto determine why the OPENVM ERASE failed.



550 Unable to send filename, file or directory is locked

Severity: Error.

Explanation: An attempt to retrieve a file on a GEToperation has failed because another user holds anexplicit lock on the requested SFS file or directory.


User or Operator Response: Retry the GET operationafter the inhibiting file or directory lock has beenreleased. If necessary, contact the TCP/IP administratorof the remote host for assistance in resolving problemsassociated with file or directory locking.



FTP Messages


550 Unable to store filename550 Unable to store filename, file or directory

is locked.550 Unable to store filename, you are not

authorized.550 Unable to store filename, SFS create file error.550 Unable to store filename, virtual storage

capacity exceeded.

Severity: Error.

Explanation: The z/VM FTP server detected an errorwhile attempting to open the indicated SFS or minidiskfile during PUT processing. Possible causes for thiserror are:v Another user holds an explicit lock on the target SFS

file or directoryv Access to the file has been denied due to lack of

proper authorizationv An attempt to create a new file in the target SFS

directory has failedv An insufficient virtual storage condition has been

detected.


User or Operator Response: Identify the reason forthis failure based on the format of the receivedmessage, then retry the PUT operation (for example,after the inhibiting lock has been released, or after theproper file or directory authorization has beenobtained). If the reason for this error cannot beascertained or an insufficient virtual storage conditionhas been encountered, contact the TCP/IPadministrator of the foreign host in question. Forpersistent problems, detailed information about thereason for this failure can be obtained by tracing FTPserver activity.



550 Unable to store unique filename550 Unable to store unique filename, file or

directory is locked.550 Unable to store unique filename, you are not

authorized.550 Unable to store unique filename, SFS create

file error.550 Unable to store unique filename, virtual

storage capacity exceeded.

Severity: Error.

Explanation: The z/VM FTP server detected an errorwhile attempting to open the indicated SFS or minidiskfile during PUT or MPUT processing, for which ″storeunique″ processing has also been requested. Possiblecauses for this error are:v Another user holds an explicit lock on the target SFS

file or directory

v Access to the file has been denied due to lack ofproper authorization

v An attempt to create a new file in the target SFSdirectory has failed

v An attempt to create the named file (or auniquely-named copy of this file) has failed

v An insufficient virtual storage condition has beendetected.

System Action: The file transfer operation is notperformed. After this message has been returned to theclient, the FTP server marks the connection as ″ready toreceive″ and quiesces activity, waiting for the nextinteraction with the client.

User or Operator Response: Identify the reason forthis failure based on the format of the receivedmessage, then retry the PUT or MPUT operation (forexample, after the inhibiting lock has been released, orafter the proper file or directory authorization has beenobtained).

If the failure is associated with ″store unique″processing, use the SUNIQUE subcommand to turn offthe ″store unique″ file transfer attribute (if appropriate)and attempt the file transfer again.

Note: A ″store unique″ error may arise when the FTPserver cannot derive or obtain a unique filename for storing the file in question. In such acase, it may be necessary to delete one or morefiles that have already been uniquely stored bythe FTP server. For information to help youdetermine whether a uniquely stored file (if any)is a candidate for deletion, refer to the UsageNotes associated with the ″SUNIQUE″ FTPsubcommand in the TCP/IP User’s Guide.



550 Wildcards not supported in QAUTH for protectedSFS

Severity: Error.

Explanation: Wildcards are not supported for theQuery Authority.


User or Operator Response: Reissue the commandwith file name and file type.



550 Write access unavailable for Owner Address due toother links

Severity: Error.

Explanation: Another VM user has accessed yourworking directory minidisk in write mode. VM does

FTP Messages


not allow multiple write access to prevent two usersfrom modifying the same file at the same time.


User or Operator Response: Wait until the other userde-accesses the minidisk, or assign another nonaccessedminidisk as working storage.



550 You are not allowed to create a top-level directory.

Severity: Error.

Explanation: You cannot create top directories usingthe MKDIR command. The top directory is created bybeing enrolled in the file pool, (FILEPOOL:USERID).


User or Operator Response: If you meant to create adirectory within the directory structure, use the MKDIRcommand with one more level.(FILEPOOL:USERID.SUBDIRECTORY).



550 You are not authorized for userid.RDR;Directory remains old_directory

Severity: Error.

Explanation: You do not have the authority to accessthe user’s reader.





550 You are not using an SFS/BFS directory. CD..is not allowed.

550 You are not in an SFS directory.550 You can not MakeDirectory because you are

not in SFS.550 You are not using an SFS directory. CDUP is

not allowed.550 You can not Remove Directory because you are

not in SFS.

Severity: Error.

Explanation: SFS/BFS commands are not allowedunless your current working directory is an SFS/BFSdirectory.


User or Operator Response: Issue CD command to

change your current working directory to an SFS/BFSdirectory.


Procedure Name: DoCwd, DoSite, DoMkDir, DoCdup,DoRmDir

550 You can not erase a top-level directory.

Severity: Error.

Explanation: You attempted to erase a top directory.This directory cannot be erased.


User or Operator Response: To erase all objectscontained in the directory, issue an appropriate series oferase commands for those objects.


Procedure Name: DoRmdir

550 You can not remove the current working directory.

Severity: Error.

Explanation: You issued an RMDIR command for thecurrent working directory.


User or Operator Response: Use the CD command tochange to another SFS directory and reissue thecommand.



550 You do not have read access to your currentworking directory any more. Use CDcommand to select a new directory/mini-disk.

550 The SFS directory NewDir does not exist oryou are not authorized; directory remainsWorkingDirectory.

Severity: Error.

Explanation: The directory assigned as your currentdirectory may not exist or you are not authorized for it.


User or Operator Response: Select a newdirectory/mini-disk or contact the directory owner forauthorization.


Procedure Name: DoList, DoCwd

FTP Messages


552 Data transfer aborted, BFS file space is full

Severity: Error.

Explanation: There is not enough room in the filespace to complete the request.


User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits in the file pool.


Procedure Name: WriteBFSData

552 Data transfer aborted due to disk overflow.552 Data transfer aborted, SFS file space is full.552 Data transfer aborted. Disk overflow occurred

on disk used to temporarily store reader files.

Severity: Error.

Explanation: There is no room on the minidisk or inthe file space to complete the request.


User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits in the file pool or increase the cylinders onthe minidisk.


Procedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent

552 Storage group space limit exceeded.

Severity: Error.

Explanation: There is no room in the filespace tocomplete the request.


User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits in the file pool.


Procedure Name: DoMkDir, DoRmDir

553 Invalid BFS file identifier: ’BFSfile’

Severity: Error.

Explanation: The specified BFS file identifier is notvalid.


User or Operator Response: Correct the BFS filespecification and reissue the command.



553 Invalid character (″/″) in BFS file identifier:’BFSfile’

Severity: Error.

Explanation: The ″/″ command is not allowed in aBFS file identifier.


User or Operator Response: Correct the invalid BFSfile specification and reissue the command.



553 Invalid CMS file identifier FileName553 Invalid character in filename FileName550 File FileName is not on an accessed mini-disk550 File error ReturnCode in accessing FileName

Severity: Error.

Explanation: FTP sends one of these four messages,depending on the problem.


User or Operator Response: Correct thecorresponding problem and resubmit the job.


Procedure Name: FileOk

553 Invalid quote specification in BFS file identifier:’BFSfile’

Severity: Error.

Explanation: Incorrect use of quotes was used on aBFS file identifier (quote specifications must bematched up).


User or Operator Response: Correct the BFS filespecification and reissue the command.



FTP Messages


Chapter 4. GDDMXD/VM Messages and Codes

This chapter contains the GDDMXD/VM messages and ABEND codes you canencounter when you use GDDMXD/VM.

GDDMXD/VM Messages

Color s not available.

Explanation: The color s was not found in the XWindow System server’s database. The color s wasspecified in a GColornn or a GMCPnn entry in the XDEFAULTS file.

User or Operator Response: Choose a color that is inthe database and update the X DEFAULTS file.

File GDXALTCS PSS not found. No alternatecharacter set.

Explanation: The file GDXALTCS PSS could not belocated. No alternative character set is available.

User or Operator Response: If you need thealternative character set to run APL, access the diskcontaining the file and try again.

No free storage. Please increase virtual storage size.

Explanation: GDDMXD/VM is unable to allocateneeded virtual storage. The virtual storage size of thevirtual machine should be increased.

User or Operator Response: Increase the virtualmachine storage size and try again.

Unable to allocate pixmap.

Explanation: Pixmaps are used by GDDMXD/VM tosimulate the IBM 3179G graphics presentation spaceand programmed symbols storage. Insufficientresources are available at the workstation to allocate apixmap.

User or Operator Response: Attempt to free upworkstation resources by reducing the number of activeapplications and try again.

Unable to establish connection to workstation.

Explanation: The X Window System was unable toconnect to the workstation at the Internet addressspecified in the CMS global variable display (groupCENV). This message is followed by ABEND 103.

User or Operator Response: Correct the address in theglobal variable and try again.

ABEND Codes

Code: 102

Explanation: Either GDXLIOX0 MODULE orGDXADML1 MODULE could not be found.

User or Operator Response: Access the diskcontaining these modules and try again.

Code: 103

Explanation: The X Window System was unable toconnect to the workstation at the Internet addressspecified in the CMS global variable Display (groupCENV).

User or Operator Response: Correct the address in theglobal variable and try again.

Code: 104

Explanation: The X Window System has detected anerror and is unable to continue. This ABEND isgenerally preceded by an X Window System message.

User or Operator Response: Try again. If the errorreoccurs, report the problem to your IBM SupportCenter.


GDDMXD/VM Messages and Codes


Chapter 5. IMAP Messages

This section contains the IMAP messages.

DTCIMP1000E ip_address Buffer overrun receivingcommand

Explanation: While connected to the IMAP server, theIMAP client at the given IP address tried to send moredata across the connection than could be received intothe connection’s buffer. This may be done intentionallyto cause errors in the IMAP server.

System Action: IMAP continues but the connection isterminated.

System Programmer Response: Look for similarerrors associated with the given IP address todetermine if actions are intentional.

DTCIMP1001E ip_address Error opening file filename:DMSOPEN rs=reason_code

Explanation: An error occurred while trying to openthe specified file using the DMSOPEN CSL routine.

System Action: IMAP continues.

System Programmer Response: Use the given reasoncode from the DMSOPEN CSL routine to determinewhy the error occurred.

DTCIMP1002E ip_address Error closing file filename:DMSCLOSE rs= reason_code

Explanation: An error occurred while trying to closethe specified file using the DMSCLOSE CSL routine.


System Programmer Response: Use the given reasoncode from the DMSCLOSE CSL routine to determinewhy the error occurred.

DTCIMP1003E ip_address Error reading file filename:DMSREAD rs=reason_code

Explanation: An error occurred while trying to readthe specified file using the DMSREAD CSL routine.


System Programmer Response: Use the given reasoncode from the DMSREAD CSL routine to determinewhy the error occurred.

DTCIMP1004E ip_address Error writing file filename:DMSWRITE rs=reason_code

Explanation: An error occurred while trying to writeto the specified file using the DMSWRITE CSL routine.


System Programmer Response: Use the given reasoncode from the DMSWRITE CSL routine to determinewhy the error occurred.

DTCIMP1005E Error completing asynchronous SFSrequest: DMSCHECK rc=return_code,rs=reason_code

Explanation: The DMSCHECK CSL routine returnedthe specified return code and reason code while tryingto determine if an asynchronous SFS request hadcompleted.


System Programmer Response: Use the given returncode and reason code from the DMSCHECK CSLroutine to determine why the error occurred.

DTCIMP1006E ip_address Error committing to IMAPSFS mailstore: DMSCOMMrs=reason_code

Explanation: An error occurred while trying tocommit changes to the SFS file pool containing theIMAP mailstore using the DMSCOMM CSL routine.


System Programmer Response: Use the given reasoncode from the DMSCOMM CSL routine to determinewhy the error occurred.

DTCIMP1007E ip_address Error creating directorydirname: DMSCRDIR rs=reason_code

Explanation: An error occurred while trying to createthe specified directory using the DMSCRDIR CSLroutine.


System Programmer Response: Use the given reasoncode from the DMSCRDIR CSL routine to determinewhy the error occurred.


DTCIMP1008E ip_address Error opening directorydirname: DMSOPDIR rs=reason_code

Explanation: An error occurred while trying to openthe specified directory using the DMSOPDIR CSLroutine.


System Programmer Response: Use the given reasoncode from the DMSOPDIR CSL routine to determinewhy the error occurred.

DTCIMP1009E ip_address Error closing directorydirname: DMSCLDIR rs=reason_code

Explanation: An error occurred while trying to closethe specified directory using the DMSCLDIR CSLroutine.


System Programmer Response: Use the given reasoncode from the DMSCLDIR CSL routine to determinewhy the error occurred.

DTCIMP1010E ip_address Error checking for filefilename: DMSEXIFI rs=reason_code

Explanation: The DMSEXIFI CSL routine returned thespecified reason code for the given file.


System Programmer Response: Use the given reasoncode from the DMSEXIFI CSL routine to determinewhy the error occurred.

DTCIMP1011E ip_address Error getting directory infofor dirname: DMSGETDI rs=reason_code

Explanation: An error occurred while trying to obtainthe given directory’s information using the DMSGETDICSL routine.

System Action: IMAP continues

System Programmer Response: Use the given reasoncode from the DMSGETDI CSL routine to determinewhy the error occurred.

DTCIMP1012E ip_address Error erasing filename:DMSERASE rs=reason_code

Explanation: An error occurred while trying to erasethe specified object using the DMSERASE CSL routine.


System Programmer Response: Use the given reasoncode from the DMSERASE CSL routine to determinewhy the error occurred.

DTCIMP1013E Error returning SFS work unit id:DMSRETWU rc=return_code,rs=reason_code

Explanation: An error occurred while trying to returnan SFS work unit id using the DMSRETWU CSLroutine.


System Programmer Response: Use the given returncode and reason code from the DMSRETWU CSLroutine to determine why the error occurred.

DTCIMP1014E ip_address Specified user userid isunknown or not registered

Explanation: An operation requiring a valid user IDwas attempted, but the specified user is not enrolled inthe IMAP mailstore.


System Programmer Response: To allow the operationto succeed, the specified user must be enrolled in theIMAP mailstore.

DTCIMP1015E ip_address User userid is not valid orspecified password is not valid

Explanation: The specified user has tried to log on tothe IMAP server from the specified IP address, buteither the user ID is not valid or the user specified aninvalid password.

System Action: The connection from the specified IPaddress remains unauthenticated.

System Programmer Response: Determine if the givenuser ID exists. If the user ID is valid, then the usersupplied an incorrect password.

DTCIMP1016E ip_address Error attempting toauthenticate user userid: DMSPWCHKrc= rc

Explanation: The DMSPWCHK CSL routine failedwith the given return code while trying to authenticatethe specified user ID.

System Action: The connection from the specified IPaddress remains unauthenticated.

System Programmer Response: Use the return codefrom the DMSPWCHK CSL routine to determine whythe error occurred.

DTCIMP1017E Error replying to a request from theadministrative interface: QueueReplyrc=return_code, rs=reason_code

Explanation: An error occurred when the IMAP servertried to respond to an administrative interface

IMAP Messages


command using the QueueReply() CMS multitaskingfunction.


System Programmer Response: Use the given returncode and reason code from the QueueReply CMSmultitasking function to determine why the erroroccurred.

DTCIMP1018E ip_address Error receiving data:QueueReceiveBlock rc=return_code,rs=reason_code

Explanation: An error occurred while waiting for anasynchronous socket read of data over a connectionfrom the specified IP address.

System Action: The connection is terminated.

System Programmer Response: Use the given returncode and reason code from the QueueReceiveBlockCMS multitasking function to determine why the erroroccurred.

DTCIMP1019E Error deleting event monitor:EventMonitorDelete rc=return_code,rs=reason_code

Explanation: An error occurred while trying to deletean event monitor using the EventMonitorDelete CMSmultitasking function. The event monitor (associatedwith a work unit ID) is used to monitor changes to theIMAP mailstore.


System Programmer Response: Use the given returncode and reason code from the EventMonitorDeleteCMS multitasking function to determine why the erroroccurred.

DTCIMP1020E Error resetting event monitor:EventMonitorReset rc=return_code,rs=reason_code

Explanation: An error occurred while trying to resetan event monitor using the EventMonitorReset CMSmultitasking function. The event monitor (associatedwith a work unit ID) is used to monitor changes to theIMAP mailstore.


System Programmer Response: Use the given returncode and reason code from the EventMonitorResetCMS multitasking function to determine why the erroroccurred.

DTCIMP1021E Error attempting to allocate pagealigned storage

Explanation: The IMAP server was unable to allocatevirtual storage.


System Programmer Response: Wait for virtualstorage to become available or define a larger virtualstorage size for the IMAP server virtual machine.

DTCIMP1022W ip_address The space allocated in theIMAP mailstore for user userid has beenexhausted

Explanation: The specified user has used all of theirallocated space in the IMAP SFS mailstore.


System Programmer Response: If available, allocatemore space for the user in the SFS mailstore.Otherwise, the user must free up space by deleting oldmessages.

DTCIMP1023E Error copying file: routinerc=return_code, rs=reason_code

Explanation: An error occurred while attempting tocopy a file. The error occurred using the given CSLroutine.


System Programmer Response: Use the given returncode and reason code from the given CSL routine todetermine why the error occurred.

DTCIMP1024E ip_address Error renaming objectobjectname: DMSRENAM rs=reason_code

Explanation: An error occurred while trying torename the specified file or directory in the IMAP SFSmailstore using the DMSRENAM CSL routine.


System Programmer Response: Use the given reasoncode from the DMSRENAM CSL routine to determinewhy the error occurred.

DTCIMP1025W Date date does not conform to theRFC822 date format specification and isbeing ignored

Explanation: An IMAP client supplied an invalid dateand time for a note.

System Action: IMAP continues. The date is ignoredand the current date and time is used.


IMAP Messages

Chapter 5. IMAP Messages 87

DTCIMP1026I Administrative request from useruserid: request

Explanation: The IMAP server received the givenadministrative interface command (request) from thespecified user.



DTCIMP1027I ip_address Connected

Explanation: An IMAP client from the specified IPaddress has connected to the IMAP server.



DTCIMP1028I ip_address Authenticated as user userid

Explanation: An IMAP client from the specified IPaddress has authenticated their connection to the IMAPserver using the specified user ID.



DTCIMP1029I ip_address Connection terminated

Explanation: The connection to the IMAP server fromthe specified IP address has been terminated by theIMAP client or has been terminated by the IMAPserver due to an error.


System Programmer Response: See previousmessages to determine what error occurred.

DTCIMP1030I ip_address Disconnected

Explanation: The connection to the IMAP server fromthe specified IP address has ended.



DTCIMP1031E Error transferring file spoolid to useruserid:rc=rc

Explanation: An error occurred while attempting totransfer the specified spool file to the specified user ID.

System Action: The IMAP server attempts to transferthe spool file to the user ID specified in theBADFILEID configuration file statement.

System Programmer Response: Determine if the spoolfile was transferred to the BADFILEID or if the spoolfile is still in the IMAP server’s reader. Try to transferthe file to the given user. If unable to transfer the file,contact your IBM Support Center for assistance.

DTCIMP1032I File spoolid transferred to user userid

Explanation: The specified spool file has beentransferred to the specified user ID.


System Programmer Response: If the spool file wastransferred to the user ID specified in the BADFILEIDstatement in the IMAP configuration file, see previousmessages to determine why the spool file wastransferred to the BADFILEID.

DTCIMP1033E Error reading spool file using *SPL:rc= rc

Explanation: The IMAP server encountered an errorwhile attempting to read a spool file using the *SPLsystem service.

System Action: The spool file is transferred to theuser ID specified in the BADFILEID statement in theIMAP configuration file. A later message indicateswhich spool file had the error.

System Programmer Response: Contact your IBMSupport Center for assistance.

DTCIMP1034E Unable to open configuration filefilename: DMSOPEN rs=reason_code

Explanation: An error occurred while trying to openthe specified configuration file using the DMSOPENCSL routine.


System Programmer Response: Use the given reasoncode from the DMSOPEN CSL routine to determinewhy the error occurred.

DTCIMP1035E Missing token on statement statementin configuration file

Explanation: The given statement requires moretokens than were specified in the IMAP configurationfile.


System Programmer Response: Correct theconfiguration file statement and restart the IMAPserver.

DTCIMP1036E Unable to validate filepoolidfilepoolid: DMSGETWU rc=return code

Explanation: The IMAP server was unable to validatethe file pool ID specified in the FILEPOOLIDconfiguration file statement because the IMAP servercould not obtain a work unit using the DMSGETWUCSL routine.


IMAP Messages


System Programmer Response: Use the given returncode and reason code from the DMSGETWU CSLroutine to determine why the error occurred.

DTCIMP1039E Filepool filepoolid is unavailable ornot valid, or IMAP server userid is notan SFS administrator

Explanation: The file pool ID specified in theFILEPOOLID statement in the IMAP configuration fileis not valid or is not logged on, or the IMAP serverdoes not have SFS file pool administrator authority forthe specified file pool.


System Programmer Response: Verify that the filepool ID specified in the FILEPOOLID configuration filestatement is correct, the SFS file pool virtual machine isrunning, and if the IMAP server has administratorauthority to the SFS file pool. Correct any problemsand restart the IMAP server.

DTCIMP1040E Error querying file pool: DMSQUSGrc=return_code, rs=reason_code

Explanation: An error occurred when the IMAP servertried to validate the IMAP mailstore SFS file pool IDusing the DMSQUSG CSL routine.

System Action: Server intitialization stops.

System Programmer Response: Use the given returncode and reason code from the DMSQUSG CSL routineto determine why the error occurred.

DTCIMP1041E Unknown configuration filestatement statement

Explanation: The listed statement is not a supportedIMAP server configuration file statement. Forinformation about statements and operands that can bespecified for configuring the IMAP server, see TCP/IPPlanning and Customization.


System Programmer Response: Delete or correct thestatement that is in error, then restart the IMAP server.

DTCIMP1042E No FILEPOOLID specified in theconfiguration file

Explanation: The FILEPOOLID statement is requiredand must be specified in the IMAP server configurationfile.


System Programmer Response: Specify theFILEPOOLID statement in the IMAP serverconfiguration file and restart the IMAP server.

DTCIMP1043E No BADFILEID specified in theconfiguration file

Explanation: The BADFILEID statement is requiredand must be specified in the IMAP server configurationfile.


System Programmer Response: Specify theBADFILEID statement in the IMAP serverconfiguration file and restart the IMAP server.

DTCIMP1044W Ignoring request from userid thatwas not sent with QueueSendReply

Explanation: The IMAP server received a messageover the administrative interface queue that was notsent using the QueueSendReply CMS multitaskingfunction. The message is ignored.



DTCIMP1045E Invalid token token on statementstatement in configuration file

Explanation: The specified token is not valid for thegiven configuration file statement.



DTCIMP1046E Excessive token token on statementstatement in configuration file

Explanation: Too many tokens were specified for thegiven configuration file statement, starting with thetoken specified in the message.



DTCIMP1047E Invalid command input: command

Explanation: The specified console command is not avalid input command.


System Programmer Response: Enter a valid consolecommand.

IMAP Messages


DTCIMP1048I Shutting down at your request.

Explanation: The IMAP server is shutting downbecause a SHUTDOWN administrative command wasentered

System Action: IMAP shuts down.


DTCIMP1049I Additional reader thread created atyour request

Explanation: An additional thread is created forprocessing reader files because a STARTRDRadministrative command was entered.



DTCIMP1050E Unknown command entered:command

Explanation: An unsupported console command wasentered on the IMAP server.


System Programmer Response: If necessary, enter avalid console command.

DTCIMP1051E Flag or TIC not as expected

Explanation: An unrecognized Channel CommandWord (CCW) flag or Transfer in Channel (TIC)command was encountered while processing a spoolfile.



DTCIMP1052E Card image would overrun buffer

Explanation: The receiving buffer for spool file data issmaller than the amount of data in a card image, so thebuffer would be overrun if processing continued. It islikely that the card image is corrupted.



DTCIMP1053E Premature end of cards

Explanation: An error occurred while processing aspool file. The spool file data did not contain all of itscard images.



DTCIMP1054E Invalid netdata segment sizeencountered

Explanation: An error occurred while processing aspool file. The spool file contained a NETDATA recordwhich had a segment size less than one.



DTCIMP1055E Invalid netdata segment flagsencountered

Explanation: An error occurred while processing aspool file. The spool file contained a NETDATA recordwhich had an unrecognized segment flag.



DTCIMP1056E Invalid control record encountered

Explanation: An error occurred while processing aspool file. The spool file contained a NETDATA controlrecord that did not begin with an INMR0 string.



DTCIMP1057E Recipient user ID in spool file is toolarge

Explanation: The recipient user ID of a spool file islarger than the maximum user ID allowed by RFC821.

System Action: The spool file is transferred to the

IMAP Messages


user ID specified in the BADFILEID statement in theIMAP configuration file. A later message indicateswhich spool file had the error.


DTCIMP1058E Error connecting to *SPL:re=return_code

Explanation: An error occurred while trying toconnect to the *SPL system service. The IMAP servermust have an IUCV *SPL CP directory statement inorder to be authorized to use the *SPL system service.Also, the IMAP server must have an adequateMAXCONN value in its OPTION MAXCONN CPdirectory statement for as many reader threads that arebeing used by the IMAP server and for as manyconcurrent client connections that the IMAP server willbe processing.

System Action: Reader thread terminates.

System Programmer Response: See followingmessages to determine why the error occurred.

DTCIMP1059I Verify userid has an adequateMAXCONN value

Explanation: An error occurred while trying toconnect a reader thread to the *SPL system service. TheIMAP server must have an adequate MAXCONN valuein its OPTION MAXCONN CP directory statement foras many reader threads that are being used by theIMAP server and for as many concurrent clientconnections that the IMAP server will be processing.

System Action: The reader thread terminates.

System Programmer Response: Determine if theIMAP server’s MAXCONN value is adequate. If not,correct the MAXCONN value and restart the IMAPserver. If the MAXCONN value is already adequate,contact your IBM Support Center for assistance.

DTCIMP1060I Reader thread terminating

Explanation: A thread for processing incoming readerfiles encountered an error and must terminate.

System Action: Reader thread terminates.

System Programmer Response: See previousmessages to determine why the error occurred.

DTCIMP1061E Error reading spool file using *SPL:rc=return_code (reader thread issuspended)

Explanation: An error occurred while trying to read aspool file using the the *SPL system service. The erroroccurred on a thread used to process incoming readerfiles.

System Action: The thread which encountered theerror is suspended and IMAP continues.

System Programmer Response: You may issue aSTARTRDR administrative commnd to allow the IMAPserver to rsume processing of incoming mail. Contactyour IBM Support Center for assistance.

DTCIMP1062E File spoolid originated from userid,who is not authorized to send mail tothis IMAP server

Explanation: The given spool file originated from auser ID that is not authorized to send mail to the IMAPserver. Incoming mail must originate from a user IDlisted in the MAILORIGINID configuration filestatement.

System Action: The spool file is transferred to theuser ID specified in the BADFILEID configuration filestatement.

System Programmer Response: If mail should beallowed to originate from the specified user ID, add theuser ID to the MAILORIGINID configuration filestatement and restart the IMAP server.

DTCIMP1063E File spoolid created on an unsupporteddevice

Explanation: The given spool file was not created on avirtual punch device. The IMAP server only supportsspool files that were created on a virtual punch device.


System Programmer Response: Determine what to dowith the unsupported file.

DTCIMP1064E Unable to determine recipient forspool file spoolid, may not be inNETDATA format

Explanation: The IMAP server is unable to determineif the given spool file is in NETDATA format. Allincoming mail must be in NETDATA format.


System Programmer Response: Determine what to dowith the unsupported file.

DTCIMP1065I File spoolid added to INBOX of useruserid as UID uid

Explanation: The given spool file has beensuccessfully received by the IMAP server and has beenadded to the INBOX of the given user ID.


IMAP Messages



DTCIMP1066E Error adding file spoolid to folderINBOX for user userid: rs=reason_code

Explanation: An error occurred while receiving thegiven spool file. The file has not been added to theuser’s INBOX. The specified spool file reason_code isdocumented in the TCP/IP Diagnosis Guide .


System Programmer Response: See the reason_codedocumentation and previous error messages todetermine why the error occurred.

DTCIMP1067I Verify userid has IUCV *SPLdirectory statement

Explanation: An error occurred while trying toconnect to the *SPL system service. The IMAP servermust have an IUCV *SPL CP directory statement inorder to be authorized to use the *SPL system service.

System Action: The reader thread terminates.

System Programmer Response: Determine if theIMAP server’s CP directory contains an IUCV *SPLstatement. If not, add the IUCV *SPL CP directorystatement to authorize the IMAP server to use the *SPLsystem service, and restart the IMAP server. If theIUCV *SPL CP directory statement is already in theIMAP server’s CP directory, then contact your IBMSupport Center for assistance.

DTCIMP1068E Error using *SPL to reset the seen bitfor all spool files: rc=return_code

Explanation: The IMAP server encountered an errorwhile using the *SPL system service to attempt to resetthe seen bits of all spool files.

System Action: All threads used to process incomingreader files are terminated.


DTCIMP1069I Reader support terminating

Explanation: An error occurred while initializing thethreads used to process incoming reader files.

System Action: All threads used to process incomingreader files are terminated.

System Programmer Response: See previousmessages to determine why the error occurred.

DTCIMP1070E Configuration file name filename isnot valid

Explanation: The configuration file name specifiedwith the IMAPMAIN command contains more thaneight characters.


System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.

DTCIMP1071E Configuration file type filetype is notvalid

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



DTCIMP1072E Configuration file mode filemode isnot valid

Explanation: The configuration file mode specifiedwith the IMAPMAIN command contains more thantwo characters.



DTCIMP1073E Excessive parms, starting with parm

Explanation: Too many parameters were specified onthe IMAPMAIN command, starting with the specifiedparameter. For more information on the IMAPMAINcommand, see TCP/IP Planning and Customization.



DTCIMP1074E Error determining filemode ofconfiguration file: DMSERPrc=return_code

Explanation: An error occurred while trying todetermine the file mode of the IMAP serverconfiguration file using the DMSERP CSL routine.


System Programmer Response: Use the return codefrom the DMSERP CSL routine to determine why theerror occurred.

IMAP Messages


DTCIMP1075E Wrong level of CMS: routine notfound

Explanation: The given CSL routine was not foundand returned a -7 return code.


System Programmer Response: Re-IPL the IMAPserver with the appropriate level of CMS.

DTCIMP1076E Error creating ESM token: DMSESMCreate_Token rc=return_code, ESM rc=ESM_rc, ESM reason code ESM_rs

Explanation: An error occurred while trying to createan External Security Manager (ESM) token using theDMSESM CSL routine.


System Programmer Response: Use the given returncode, ESM return code, and ESM reason code from theDMSESM CSL routine to determine why the erroroccurred.

DTCIMP1077E IMAP server is missing DiagnoseX'88 authorization

Explanation: The IMAP server must be authorized touse DIAGNOSE X’88’ in order to validate IMAP clientpasswords.


System Programmer Response: Ensure that the CPdirectory of the IMAP server virtual machine containsan OPTION DIAG88 statement, and restart the IMAPserver.

DTCIMP1078E Wrong level of CP: Diagnose X'88 notavailable

Explanation: Diagnose 88 support is not available inthe level of CP that the IMAP server is running.


System Programmer Response: Upgrade to theappropriate level of z/VM.

DTCIMP1079E Error deleting ESM token: DMSESMDelete_Token rc=return_code, ESMrc=ESM_rc, ESM rs=ESM_rs

Explanation: An error occurred while trying to deletean External Security Manager (ESM) token using theDMSESM CSL routine.

System Action: IMAP terminates.

System Programmer Response: Use the given returncode, ESM return code, and ESM reason code from theDMSESM CSL routine to determine why the erroroccurred.

DTCIMP1080E ip_address Specified password expiredfor user userid

Explanation: The given user’s password has expired.


System Programmer Response: The user must changetheir logon password.

DTCIMP1081E Unrecognized option: option

Explanation: An unsupported option was specified onthe IMAPMAIN command after an open parenthesis.For more information on the IMAPMAIN command,see TCP/IP Planning and Customization.



DTCIMP1082E Configuration file filename not found

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


System Programmer Response: Verify the correctnessof the appropriate :Parms. tag entry in the DTCPARMSfile and that the specified file is located on a minidiskthat is accessed by the IMAP server, then restart theserver.

DTCIMP1083E Error attempting to obtain limitsinformation for the file space:DMSQLIMU rs=reason_code

Explanation: An error occurred while attempting toobtain file space limits information for a user using theDMSQLIMU CSL routine.


System Programmer Response: Use the return codefrom the given CSL routine to determine why the erroroccurred.

DTCIMP2000E ip_address Bad parameters received oncommand command

Explanation: The specified command received fromthe specified IP address contained invalid parameters.



IMAP Messages


DTCIMP2001E ip_address Bad part specifier specifier

Explanation: The FETCH command from the given IPaddress contained an invalid part specifier.



DTCIMP2002W ip_address Non-permanent flag, flag,is being ignored

Explanation: The IMAP client at the specified IPaddress attempted to set a non-permanent flag. Thespecified flag is ignored.



DTCIMP3000E ip_address Bad command commandreceived; connection state state

Explanation: The IMAP client at the specified IPaddress supplied the given command while in thespecified connection state. Either the command is notvalid or the command is not valid while in thespecified connection state.



DTCIMP3001E ip_address Bad parameters received oncommand command

Explanation: The IMAP client at the specified IPaddress supplied invalid parameters on the givencommand.



DTCIMP3002E ip_address command command failed,see previous messages for details

Explanation: The given command from the IMAPclient at the specified IP address failed.



DTCIMP3003E ip_address command command failed:rc=return_code, rs=reason_code

Explanation: The given command from the IMAPclient at the specified IP address failed.


System Programmer Response: Previous messagesmay help determine what error occurred.

DTCIMP3004E ip_address Access to mailbox denied,must be selected write to STORE orEXPUNGE

Explanation: The IMAP client at the given IP addressattempted to send a STORE or EXPUNGE commandwhile the specified mailbox was not selected in writemode.



DTCIMP3005E ip_address Write access to mailboxmailbox denied

Explanation: The IMAP client at the given IP addressattempted to append or copy to the specified mailbox,but the client does not have write access to themailbox.



DTCIMP3006E ip_address Bad mailbox name mbxname

Explanation: The IMAP client at the given IP addresssupplied an invalid mailbox name in a command.



DTCIMP3007E ip_address Mailbox mailbox does notexist

Explanation: The IMAP client at the given IP addresssupplied a command with a mailbox name that doesnot exist.



DTCIMP3008E ip_address Mailbox mailbox alreadyexists

Explanation: The IMAP client at the given IP addressattempted to create a mailbox that already exists orattempted to rename a mailbox to a mailbox thatalready exists.



DTCIMP3009E ip_address Error selecting mailboxmailbox

Explanation: The IMAP client at the given IP addressattempted to select the specified mailbox, but themailbox is marked as \NoSelect.


IMAP Messages



DTCIMP3010E ip_address Error creating mailboxmailbox

Explanation: The IMAP client at the given IP addressattempted to create the specified mailbox, but themailbox could not be created.


System Programmer Response: See previousmessages to determine why the mailbox could not becreated.

DTCIMP3011E ip_address Error deleting mailboxmailbox

Explanation: The IMAP client at the given IP addressattempted to delete the specified mailbox, but themailbox could not be deleted. The mailbox may havebeen selected by another connection.



DTCIMP3012E ip_address Error relocating directorydirname

Explanation: The IMAP client at the given IP addressattempted to rename the specified directory to INBOX.



DTCIMP3013E ip_address Error renaming mailboxmailbox: see previous message

Explanation: The IMAP client at the given IP addressattempted to rename the specified mailbox, but themailbox could not be renamed. The mailbox may havebeen selected by another connection. Previous messageswill indicate otherwise if the mailbox could not berenamed for another reason.



DTCIMP3014E ip_address Error copying file filename:rc=return_code, rs=reason_code

Explanation: The IMAP client at the given IP addressattempted to copy the specified file, but the file couldnot be copied.


System Programmer Response: See previousmessages to determine why the file could not becopied.

DTCIMP3015E ip_address Error committing work foruser userid on command command:rs=reason_code

Explanation: The IMAP server was unable to committhe work for the given command from the specifieduser at the given IP address. The call to theDMSCOMM CSL routine returned the given reasoncode.


System Programmer Response: Use the reason codefrom the DMSCOMM CSL routine to determine whythe error occurred.

DTCIMP3016E ip_address Unable to obtain work unitfor user userid

Explanation: The IMAP server was unable to obtain awork unit for the specified user at the given IP address.

System Action: The connection remainsunauthenticated.


DTCIMP3017E ip_address Error appending new noteto folder mbxname for user userid:rs=reason_code

Explanation: An error occurred while receiving a newnote from the given IP address. The note has not beenadded to the specified folder. The given reason_codecorresponds to the documented spool file reason codesin the TCP/IP Diagnosis Guide.


System Programmer Response: See the reason_codedocumentation and previous error messages todetermine why the error occurred.

DTCIMP3018E ip_address EXPUNGE mailbox failed:multiple concurrent selectors

Explanation: The IMAP client at the given IP addressattempted to EXPUNGE the specified mailbox, but themailbox was selected by multiple connections.Expunging a mailbox with multiple selectors is notsupported..


System Programmer Response: The client shouldretry the EXPUNGE when it is the only selector of themailbox.

DTCIMP4000E Malloc error, requested size was bytes.

Explanation: An error occurred when the IMAP serverattempted to allocate bytes amount of storage.


IMAP Messages


System Programmer Response: Increase the virtualstorage size of the IMAP server virtual machine. If theproblem persists, contact your IBM Support Center forassistance.

DTCIMP4001E ip_address Malloc error, requested sizewas bytes. Active command was command

Explanation: An error occurred when the IMAP serverattempted to allocate bytes amount of storage whileprocessing the specified command.

System Action: The connection to the specified IPaddress is terminated.


DTCIMP4002E ip_address Error starting timer:TimerStartInt rc=return_code,rs=reason_code

Explanation: An error occurred while attempting tostart the timer associated with the connectionestablished to the given IP address.

System Action: The connection to the given IPaddress is terminated.

System Programmer Response: Use the return codeand reason code from the TimerStartInt CMSmultitasking function to determine why the erroroccurred. For return and reason codes, see z/VM: CMSApplication Multitasking.

DTCIMP5000E Error creating thread: pthread_createrc=return_code, rs=reason_code

Explanation: An error occurred when the IMAP serverattempted to create a thread using pthread_create.

System Action: If necessary, IMAP terminates.

System Programmer Response: Use the return codefrom pthread_create to determine why the erroroccurred. The reason code given is the C errno variable.

DTCIMP5001E Error creating event monitor:EventMonitorCreate rc=return_code,rs=reason_code

Explanation: An error occurred when the IMAP serverattempted to create an event monitor for notification ofconsole commands using the EventMonitorCreate CMSmultitasking function.


System Programmer Response: Use the return codeand reason code from the EventMonitorCreate CMSmultitasking function to determine why the erroroccurred. For return and reason codes see z/VM: CMSApplication Multitasking.

DTCIMP5002E Error waiting on event: EventWaitrc=return_code, rs=reason_code

Explanation: An error occurred while waiting for anasynchronous request to complete using the EventWaitCMS multitasking function.


System Programmer Response: Use the return codeand reason code from the EventWait CMS multitaskingfunction to determine why the error occurred. Forreturn and reason codes see z/VM: CMS ApplicationMultitasking.

DTCIMP5003E Error creating queue: QueueCreaterc=return_code, rs=reason_code

Explanation: An error occurred while attempting tocreate a message queue using the QueueCreate CMSmultitasking function.


System Programmer Response: Use the return codeand reason code from the QueueCreate CMSmultitasking function to determine why the erroroccurred. For return and reason codes see z/VM: CMSApplication Multitasking.

DTCIMP5004E Error identifying service queue:QueueIdentifyService rc=return_code,rs=reason_code

Explanation: An error occurred while trying toidentify a service queue using the QueueIdentifyServiceCMS multitasking function.


System Programmer Response: Use the return codeand reason code from the QueueIdentifyService CMSmultitasking function to determine why the erroroccurred. For return and reason codes see z/VM: CMSApplication Multitasking.

DTCIMP5005E An error occurred during serverinitialization

Explanation: An error occurred while the IMAP serverwas initializing.



DTCIMP5006E Error creating semaphore: SemCreaterc=return_code, rs=reason_code

Explanation: An error occurred while attempting tocreate a semaphore using the SemCreate CMSmultitasking function.


IMAP Messages


System Programmer Response: Use the return codeand reason code from the SemCreate CMS multitaskingfunction to determine why the error occurred. Forreturn and reason codes see z/VM: CMS ApplicationMultitasking.

DTCIMP5007E Error creating mutex: MutexCreaterc=return_code, rs=reason_code

Explanation: An error occurred while attempting tocreate a mutex using the MutexCreate CMSmultitasking function.


System Programmer Response: Use the return codeand reason code from the MutexCreate CMSmultitasking function to determine why the erroroccurred. For return and reason codes see z/VM: CMSApplication Multitasking.

DTCIMP5008E Error on socket call: routinerc=return_code

Explanation: An error occurred on the given socketcall.


System Programmer Response: Record the routinename and the return code and contact your IBMSupport Center for assistance.

DTCIMP5009E Error setting internal date date:DateTimeSubtract rc=return_coders=reason_code

Explanation: An error occurred while attempting toset the internal date of a note. The given date wasreturned from the DateTimeSubtract CMS multitaskingfunction.


System Programmer Response: Use the return codeand reason code from the DateTimeSubtract CMSmultitasking function to determine why the erroroccurred. For return codes see z/VM: CMS ApplicationMultitasking.

DTCIMP5010E Error on socket call: routinerc=return_code, rs=reason_code

Explanation: An error occurred on the given socketcall during IMAP initialization.


System Programmer Response: Record the routinename along with the return code and reason code andcontact your IBM Support Center for assistance.

DTCIMP5011E ip_address Response buffer overrun oncommand command

Explanation: The buffer used to reply to the specifiedcommand on the connection to the given IP addresshas been overrun.

System Action: IMAP terminates


DTCIMP5012E ip_address Unexpected error whiledetermining if user userid is enrolled:procedure_name rc=return_code

Explanation: An error occurred while determining ifthe given user is enrolled in the IMAP mailstore. Theerror occurred while calling the given procedure.


System Programmer Response: Use the return codefrom the given CSL routine to determine why the erroroccureed.

DTCIMP5013E Unknown error errno: rc=return_code,rs=reason_code

Explanation: The IMAP server’s ErrorHandleprocedure was called with an unknown error number.



DTCIMP5014E ip_address Error on socket call: socketrc=return_code

Explanation: An error occurred on the given socketcall for the specified IP address.


System Programmer Response: Examine the returncode from the socket call to determine what erroroccurred.

DTCIMP5015E Binary tree balance factor not correct

Explanation: The internal binary tree of selectedmailboxes contains a node with a balance factor that isnot correct.


System Programmer Response: Restart the IMAPserver and contact your IBM Support Center forassistance.

IMAP Messages


DTCIMP5016E Mailbox mbx not in binary tree

Explanation: The specified mailbox could not befound in the internal binary tree of selected mailboxes.


System Programmer Response: Restart the IMAPserver and contact your IBM Support Center forassistance.

DTCIMP5017E An invalid thread switch occurred

Explanation: An invalid thread switch occurred whileattempting to receive data on a connection.



DTCIMP5018E Invalid connection address provided

Explanation: A socket read completed and theconnection address given was not valid.



IMAP Messages


Chapter 6. MPROUTE Messages

This section contains the MPROUTE messages.

DTCMPR7800I MPROUTE starting

Explanation: The MPROUTE application is starting.




DTCMPR7801I Deleting stack route to destination,mask mask via gateway, link link, metricmetric, type type

Explanation: MPROUTE is deleting the specified routefrom the stack’s route table. This is a route thatMPROUTE discovered through the OSPF or RIPprotocol or as the result of a directly connectedinterface. The route is no longer available.




DTCMPR7802I MPROUTE invalid option specified:option

Explanation: An unsupported command line optionwas used. option is the invalid option.

System Action: MPROUTE terminates.


System Programmer Response: Verify command lineoptions used when MPROUTE was started and retry.

DTCMPR7803I MPROUTE, functionerrno=errno:description, errno2=errno2

Explanation: The indicated function failed with theindicated error. errno is the system error code.



System Programmer Response: Correct the systemerror reported.

DTCMPR7804I MPROUTE exiting

Explanation: The MPROUTE application is exitingnormally.



System Programmer Response: Restart MPROUTE ifdesired.

DTCMPR7805I MPROUTE exiting abnormally -RC(returncode)

Explanation: Application is exiting abnormally withthe specified return code:

Reason CodeCause

1 Exited due to unrecoverable error

3 Exited due to receipt of terminating signal

4 Exited due to invalid start up parameterpassed to MPROUTE

5 Exited due to failure to add route to TCP/IPstack’s route table

6 Exited due to failure to obtain storage viamalloc

7 Exited due to the TCP/IP stack going down

8 Exited while initializing the PSA environment

9 Exited while initializing the log/trace facility

11 Exited while initializing the OSPF, RIP andINFORMATIONAL sockets

12 Exited while configuring the MPROUTEapplication

13 Exited while obtaining the TCP/IP stack’sroute table

14 Exited while initializing the RIP protocol

15 Exited while initializing the OSPF protocol

16 Exited while dynamically adding an OSPFinterface

17 Exited due to failure to delete route fromTCP/IP stack’s route

18 Exited due to failure to change route inTCP/IP stack’s route table



System Programmer Response: Take necessarycorrective action based upon specified return code andany preceding messages indicating the cause of theabnormal exit. Restart MPROUTE if desired.


DTCMPR7806I Changing stack route to destination,mask mask via gateway, link link, metricmetric, type type

Explanation: MPROUTE is deleting the specified routefrom the stack’s route table. This is a route thatMPROUTE discovered through the OSPF or RIPprotocol or as the result of a directly connectedinterface. The route is no longer available.




DTCMPR7807I Abnormal termination - out ofstorage

Explanation: MPROUTE requested storage for acontrol block or buffer and that request has failed.



System Programmer Response: Resolve the storageshortage.

DTCMPR7810I Route not deleted from stack routingtable - reason

Explanation: A dynamic route was not deleted fromthe stack’s routing table for the specified reason.




DTCMPR7812I Could not obtain stack interfaceflags, ioctl errno=errno:description,errno2=errno2

Explanation: An attempt to obtain the flags for aTCP/IP interface failed with the specified error.



System Programmer Response: Possible internal error.Contact the IBM Support Center.

DTCMPR7813I Could not obtain stack interfacebroadcast address, ioctlerrno=errno:description, errno2=errno2

Explanation: An attempt to obtain the broadcastaddress for a TCP/IP interface failed with the specifiederror.



System Programmer Response: Possible internal error.

Contact the IBM Support Center.

DTCMPR7814I Unable to create socket type type,errno=errno:description, errno2=errno2

Explanation: An attempt to create a socket of thespecified type failed with the specified error.



System Programmer Response: Attempt to correct thereported system error. This problem may be caused by:

v An attempt to initialize the MPROUTE server whilethe TCP/IP stack is not operational.

v An improperly configured TCPIP DATA file (or lackthereof).

If the problem persists, report it to the IBM SupportCenter.

DTCMPR7815I Socket socket bind to port port,address address failed,errno=errno:description, errno2=errno2

Explanation: An attempt to bind to the specified portfailed with the specified error.




DTCMPR7816I Unable to set option option for typesocket socket, errno=errno:description,errno2=errno2

Explanation: An attempt to set the specified option onthe specified socket failed with the specified error.




DTCMPR7817I Using type OSPF protocol protocol

Explanation: The specified protocol number is beingused for OSPF communication.




MPROUTE Messages


||

||

||

||

DTCMPR7818I Unable to listen on socket socket,errno=errno:description, errno2=errno2

Explanation: An attempt to listen on the specifiedsocket failed with the specified error.




DTCMPR7819I Invalid value for keyword coded ontype statement

Explanation: The value coded for the specifiedkeyword on the specified configuration statement in theMPROUTE configuration file was invalid.

System Action: If the keyword has a default value,the default is taken. Otherwise, MPROUTE terminates.


System Programmer Response: Correct the valuecoded for the specified keyword in the MPROUTEconfiguration file.

DTCMPR7820I Required parameter for keyword notcoded on type statement

Explanation: A required keyword for which no defaultcan be taken was not coded on the specifiedconfiguration statement in the MPROUTE configurationfile.



System Programmer Response: Add the requiredkeyword to the appropriate configuration statement inthe MPROUTE configuration file.

DTCMPR7821I Ignoring duplicate type statement

Explanation: Found a duplicate of the specifiedconfiguration statement in the MPROUTE configurationfile.

System Action: The duplicate statement is ignored.


System Programmer Response: Remove the duplicatestatement from the MPROUTE configuration file.

DTCMPR7822I Could not find configuration file

Explanation: The MPROUTE configuration file couldnot be found.



System Programmer Response: Check the search

hierarchy for the existance of the MPROUTEconfiguration file. Code the configuration file if onedoes not exist.

DTCMPR7825I MPROUTE unrecoverable error(error)

Explanation: MPROUTE is exiting due to the specifiedunrecoverable error.

System Action: MPROUTE exits.



DTCMPR7826I Unable to accept connections onsocket socket, errno=errno:description,errno2=errno2

Explanation: An attempt to accept a connection on thespecified socket failed with the specified error.




DTCMPR7827I Adding stack route to destination,mask mask via gateway, link link, metricmetric, type type

Explanation: MPROUTE is adding the specified routeto the stack’s route table. This route may have beendiscovered through OSPF or RIP protocols or may bethe result of a directly connected interface.




DTCMPR7828I Error adding/deleting/changing stackroute, return code retcode, iocterrno=errno:description, errno2=errno2

Explanation: An attempt to add, delete, or change aroute in the stack’s route table has failed for thespecified reason.




MPROUTE Messages

Chapter 6. MPROUTE Messages 101

DTCMPR7829I Route not changed in stack routingtable - reason

Explanation: A dynamic route was not changed in thestack’s routing table for the specified reason.




DTCMPR7830I error at line line of MPROUTEconfiguration file processing token

Explanation: The specified error occurred on thespecified line in the MPROUTE configuration file. Theerror was encountered on or just previous to thespecified token.



System Programmer Response: Correct the error inthe MPROUTE configuration file.

DTCMPR7837I Could not obtain stack interfaceindex, ioctl errno=errno:description,errno2=errno2

Explanation: The attempt to obtain the list ofinterfaces defined to the TCP/IP stack failed with thespecified error.




DTCMPR7838I Using configuration file: filename

Explanation: The specified configuration file is beingused to configure MPROUTE.




DTCMPR7839I type receive thread terminates

Explanation: The specified MPROUTE thread isterminating. Communications over this thread areterminated.



System Programmer Response: Actions determinedby preceding messages indicating the cause of thethread termination.

DTCMPR7840I sendto() error, errno=errno:description,errno2=errno2

Explanation: The indicated error occurred whileattempting to send a packet of data to an adjacentrouter.

System Action: If error is due to TCP/IP stack goingdown, MPROUTE terminates.


System Programmer Response: This may be atemporary condition caused by the fact thatinformational socket packets have not yet beenprocessed. If this message appears repeatedly, contactthe IBM Support Center.

DTCMPR7841I type receive socket closedunexpectedly

Explanation: A TCPIP socket used for communicationsby MPROUTE has closed or has timed out.



System Programmer Response: Investigate possibleproblems with TCPIP. Restart MPROUTE.

DTCMPR7842I type function error,errno=errno:description, errno2=errno2

Explanation: The indicated function failed with theindicated error. errno is the system error code.



System Programmer Response: Correct the systemerror reported.

DTCMPR7857I error (text) on MPROUTE SMSGcommand

Explanation: The specified error has occurred whileprocessing an MPROUTE SMSG command.

System Action: The MPROUTE SMSG command isignored.


System Programmer Response: Verify the syntax ofthe SMSGY command and reissue.

DTCMPR7858I Unable to send debug and/or traceoutput to debug destination

Explanation: MPROUTE was unable to access thedebug destination for storage of debug and/or traceoutput.

System Action: MPROUTE continues, unable to writedebug and trace information.

MPROUTE Messages




DTCMPR7861I Sink network discarding packet todestination

Explanation: An OSPF or RIP packet, intended for thespecified destination, is being discarded due to the lackof an active interface to the destination.




DTCMPR7862I Received type interface name

Explanation: MPROUTE has learned of a statuschange of the specified type for the specified TCP/IPinterface.

System Action: MPROUTE makes any necessarychanges to its processing based upon the status change.Also, any necessary changes are made to routes thatuse this interface.



DTCMPR7863I Received type route to destination

Explanation: The status of the specified route, definedby a GATEWAY statement in the TCPIP profile, haschanged.

System Action: MPROUTE makes any necessarychanges to its internal route table based upon the statuschange.



DTCMPR7864I Deleting all stack routes todestination, mask mask

Explanation: MPROUTE is deleting all routes to thespecified destination/mask from the TCP/IP stack’sroute table. This is occurring either because the routeno longer exists or because it has changed (in whichcase the new route is added following the deletion).




DTCMPR7865I Class mask class_mask being used forinterface interface

Explanation: The specified interface was notconfigured in the MPROUTE configuration file throughan OSPF_Interface, RIP_Interface, or Interface

configuration statement. Therefore, a default mask isbeing used based upon the network class.

System Action: The default (class) mask is used forthe interface. The network that can be accessed throughthis interface is computed by ANDing the interfaceaddress with this mask. A route to the resultingnetwork (through this interface) is added to the TCP/IPstack’s route table.


System Programmer Response: If the specified maskis not desired for the specified interface, modify theMPROUTE configuration file to add an OSPF_Interface,RIP_Interface, or Interface configuration statement forthe interface.

DTCMPR7866I MPROUTE SMSG commandaccepted

Explanation: A SMSG command has been received byMPROUTE.

System Action: The SMSG command is processed.



DTCMPR7867I Invalid type value specified in SMSGcommand

Explanation: An invalid value of the specified typewas entered in an SMSG command received byMPROUTE.

System Action: The SMSG command is ignored.


System Programmer Response: Verify the syntax ofthe SMSG command and reissue.

DTCMPR7868I Dead Router Interval must be greaterthan Hello Interval on type statement,taking defaults

Explanation: A configuration statement of thespecified type has been encountered in the MPROUTEconfiguration file on which the Dead Router Interval isless than or equal to the Hello Interval. This is aninvalid configuration.

System Action: MPROUTE continues, using thedefault values for Dead Router Interval and HelloInterval for the interface.


System Programmer Response: Modify theMPROUTE configuration file to either increase theDead Router Interval or decrease the Hello Interval.

MPROUTE Messages


DTCMPR7869I MPROUTE configuration file mustcontain OSPF or RIP interfacestatements

Explanation: MPROUTE has found no OSPF_Interfaceor RIP_Interface configuration statements in theMPROUTE configuration file.



System Programmer Response: Modify theMPROUTE configuration file, adding the appropriateOSPF_Interface and/or RIP_Interface configurationstatements.

DTCMPR7870I OSPF and RIP interface statementsfor ipad (name) have different values forkwrd

Explanation: MPROUTE has found an OSPF_Interfaceand a RIP_Interface configuration statement for thespecified interface and they have different values forthe specified keyword. This is an invalid configuration.



System Programmer Response: Modify theMPROUTE configuration file to correct the problem.

DTCMPR7871I No matching interface statements foripad (name)

Explanation: No matching OSPF_Interface,RIP_Interface, or Interface statement was found for thespecified TCP/IP interface.

System Action: MPROUTE continues. The specifiedinterface will not be used by the OSPF and RIPprotocols. Also, the class mask will be used incalculating the network route to be added to the routetable.


System Programmer Response: If it is desired that thespecified interface be used by the OSPF and/or RIPprotocol, modify the MPROUTE configuration file toadd an OSPF_Interface and/or RIP_Interfaceconfiguration statement. Otherwise, add an Interfaceconfiguration statement if the class mask should not beused in calculating the network route to be added tothe route table.

DTCMPR7872I MPROUTE found another routingapplication already active

Explanation: MPROUTE was unable to allocaterequired TCPIP resources. These resources are onlyused by routing applications. Another instance ofMPROUTE or another routing application is runningon the TCP/IP stack.



System Programmer Response: Stop the activerouting application and restart MPROUTE.

DTCMPR7873I Required parameter parm missing onMPROUTE SMSG command

Explanation: The specified required parameter wasnot provided on a SMSG command received byMPROUTE.

System Action: The MODIFY command is ignored.


System Programmer Response: Verify the syntax ofthe SMSG command and re-issue.

DTCMPR7875I No default route defined

Explanation: Either there is no default routeconfigured in the MPROUTE configuration file or thedefault route configured could not be started. This isprobably caused by the next hop interface for that routebeing inactive.

System Action: MPROUTE continues with no defaultroute configured.


System Programmer Response: Activate the next hopinterface and the default route will become active.

DTCMPR7876I -- protocol Packet Sent ------ Type: typeversion

Explanation: A packet, of the specified type andversion, has been sent by the specified protocol.




DTCMPR7877I -- protocol Packet Received -- Type:type version

Explanation: A packet, of the specified type andversion, has been received by the specified protocol.




DTCMPR7878I formatstring

Explanation: Used for displaying formatted packetoutput.


MPROUTE Messages




DTCMPR7879I reason multicast group group oninterface interface

Explanation: MPROUTE is joining or leaving thespecified multicast group on the specified interface.These groups are used for RIPv2 and OSPF protocols.




DTCMPR7881I field required for point to point linkname

Explanation: MPROUTE has found an OSPF_Interface,RIP_Interface or Interface configuration statement forthe specified interface, which is a point to point link.The specified keyword is required for a point to pointlink and it was not provided.



System Programmer Response: Modify theMPROUTE configuration file, adding the requiredkeyword.

DTCMPR7882I Processing static route from stack,destination dest, mask mask, gateway gw

Explanation: The specified route is defined through aTCPIP GATEWAY statement. MPROUTE has learned ofthis route during initialization. MPROUTE cannotoverride or modify this route. Consider removing thisGATEWAY statement while using MPROUTE, allowingOMPROUTE to dynamically learn and manage theroute.

System Action: MPROUTE will add the route to itsinternal route table and will never modify the route oradd a route to the same destination.


System Programmer Response: If possible, removethis GATEWAY statement while using MPROUTE,allowing MPROUTE to dynamically learn and managethe route.

DTCMPR7882W Unable to open MPROUTECONFIG file (config)

Explanation: The MPROUTE configuration file couldnot be found or could not be opened.



System Programmer Response: Check the search

order for the existence of the MPROUTE configurationfile. If the configuration file does not exist, create oneby copying the MPROUTE SCONFIG sampleconfiguration file as MPROUTE CONFIG. Then makethe appropriate changes to reflect your Routingenvironment.

DTCMPR7883I Processing interface from stack,address addr, name name, index indx,flags flgs

Explanation: The specified interface is defined to theTCP/IP stack. MPROUTE has learned of this interfaceduring initialization.




DTCMPR7884I RouterID id not a configured systeminterface, taking default

Explanation: MPROUTE has found the RouterIDconfiguration statement in the OMPROUTEconfiguration file. The specified ID is not a configuredinterface.

System Action: MPROUTE ignores the RouterIDconfiguration statement and selects one of theconfigured interfaces as the Router ID.


System Programmer Response: Modify theMPROUTE configuration file, providing a configuredinterface as the Router ID.

DTCMPR7885I Route not added to stack routingtable - reason

Explanation: A dynamic route was not added to thestack’s routing table for the specified reason.




DTCMPR7886I MPROUTE SMSG commandaccepted

Explanation: An SMSG command has been receivedby MPROUTE.

System Action: The SMSG command processed.



MPROUTE Messages


DTCMPR7888I one statement ignored, conflicts withprevious two statement

Explanation: MPROUTE has found a configurationstatement in the OMPROUTE configuration file thatconflicts with a previous configuration statement.

System Action: MPROUTE continues, ignoring thespecified configuration statement.


System Programmer Response: Modify theMPROUTE configuration file to resolve the conflict.

DTCMPR7890I kwd ignored when stmt statement is awildcard

Explanation: MPROUTE has found the specifiedwildcard statement in the OMPROUTE configurationfile with the specified keyword provided. This keywordis meaningless when the statement is a wildcard.

System Action: MPROUTE continues, ignoring thekeyword provided.


System Programmer Response: Modify theMPROUTE configuration file, removing the extrakeyword.

DTCMPR7891I Multiple stmt statements for subnetsub have kwd coded as primary

Explanation: MPROUTE has found more than one ofthe specified configuration statement in the MPROUTEconfiguration file for the specified subnet. Each of thesestatements has the specified keyword coded as″primary″.

System Action: MPROUTE continues, ignoring the″primary″ setting on all but one of the configurationstatements.


System Programmer Response: Modify theMPROUTE configuration file, ensuring that only one ofthe statements for the specified subnet have thespecified keyword coded as ″primary″.

DTCMPR7893I IP address *.*.*.* not valid onInterface statement, statement ignored

Explanation: MPROUTE has found an Interfaceconfiguration statement in the OMPROUTEconfiguration file with an IP_Address parameter of*.*.*.*. This is not allowed.

System Action: MPROUTE continues, ignoring thespecified configuration statement.


System Programmer Response: Modify the

MPROUTE configuration file, replacing the fullwildcard configuration statement with either explicitstatements for each interface or more explicit wildcardstatements.

DTCMPR7894I Neighbors must be coded fornon-broadcast capable stmt name

Explanation: MPROUTE has found the specifiedconfiguration statement in the OMPROUTEconfiguration file. This statement is for a non-broadcastlink. In this situation, neighbors must be coded on theconfiguration statement. Without this information,MPROUTE cannot communicate over the link.



System Programmer Response: Modify theMPROUTE configuration file, providing neighbordefinitions for the neighbors that can be reached overthe non-broadcast link.

DTCMPR7895I Processing SMSG command fromuser_id - command

Explanation: An SMSG command request wasreceived from the indicated user ID.

System Action: The SMSG command is processed.



DTCMPR7896I Could not obtain stack routing table,ioctl errno=errno:description,errno2=errno2

Explanation: The attempt to obtain the contents of theTCP/IP stack’s route table failed with the specifiederror.




DTCMPR7898I MPROUTE Initialization Complete

Explanation: The MPROUTE application hascompleted its initialization.




MPROUTE Messages


DTCMPR7900I Bad length packet, from source, typetype

Explanation: An OSPF packet of the specified type hasbeen received. The OSPF length field indicates a longerpacket than indicated by the IP header length field.

System Action: The packet is discarded.


System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.

DTCMPR7901I Bad packet checksum, from source,type type

Explanation: An OSPF packet of the specified type hasbeen received. The packet has an invalid OSPFchecksum.




DTCMPR7902I Bad OSPF version, from source, typetype

Explanation: An OSPF packet of the specified type hasbeen received. The version field in the OSPF header isnot equal to 2.




DTCMPR7903I No matching SPF-interface for packetfrom source, type type

Explanation: An OSPF packet of the specified type hasbeen received. Either the IP destination specified in thepacket is not acceptable, or the parameters in the OSPFheader (like area ID) do not match the parametersconfigured for the receiving interface. This may be anacceptable situation if you have a physical networkbroken into multiple networks through TCP/IP.




DTCMPR7904I Packet authentication failure, fromsource, type type

Explanation: An OSPF packet of the specified type hasbeen received. The packet fails to authenticate.



System Programmer Response: Verify theauthentication type and authentication key specified forthe appropriate interfaces on this and the source router.The types and keys must match in order forauthentication to succeed.

DTCMPR7905I No matching OSPF neighbor forpacket from source, type type

Explanation: An OSPF packet of the specified type hasbeen received. The packet is not a hello packet, anddoes not match any existing OSPF neighbor. This is anacceptable situation when MPROUTE has just beenstarted and is receiving non-hello packets that thesource router has multicasted onto the network prior toan adjacency being formed with the source router.




DTCMPR7906I Bad packet type received from source,type type

Explanation: An OSPF packet of the specified type hasbeen received. The OSPF packet type field is invalid.




DTCMPR7908I Received packet type type from source

Explanation: An OSPF packet of the specified typewas received from the specified source.




DTCMPR7909I Sending unicast type type dstdestination

Explanation: A unicast OSPF packet of the specifiedtype has been sent to the specified IP destination.



MPROUTE Messages



DTCMPR7910I Sending multicast, type type,destination destination net net_indexinterface name

Explanation: A multicast OSPF packet of the specifiedtype sent out the specified interface to the specifieddestination.




DTCMPR7911I Retransmitting packet, type type,source -> destination

Explanation: A unicast OSPF packet of the specifiedtype is being retransmitted, using the specified sourceand destination.




DTCMPR7912I No FSM match, interface interface,state state, event event

Explanation: The specified event occurred while aninterface was in the specified state. This occurrence isnot covered by the interface Finite State Machine.

System Action: The event is ignored.



DTCMPR7913I State change, interface interface, newstate state, event event

Explanation: The specified event occurred on thespecified interface, causing its state to transition to thespecified new state.




DTCMPR7914I No match for hello received onvirtual link, from source

Explanation: A hello packet was received that couldonly match a virtual link, yet that link is notconfigured.




DTCMPR7915I Network mask mismatch in hellofrom source

Explanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the network mask of their commonnetwork.



System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the network masks configured for thecommon network match.

DTCMPR7916I Hello interval mismatch in hellofrom source

Explanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the hello interval to be used on thecommon network.



System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the hello intervals configured for thecommon network match.

DTCMPR7917I Dead interval mismatch in hellofrom source

Explanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the ″dead router interval″ to be usedon the common network.



System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the dead router intervals configured forthe common network match.

DTCMPR7918I No FSM match, neighbor neighbor,state state, event event

Explanation: The specified event has been generatedfor the specified neighbor, which is currently in thespecified state. This was not anticipated by theneighbor Finite State Machine.

System Action: The event is ignored.


System Programmer Response: Possible internal error.

MPROUTE Messages


Contact the IBM Support Center.

DTCMPR7919I State change, neighbor neighbor, newstate state, event event

Explanation: The specified event has been generated,causing the specified neighbor to transition to thespecified new state.




DTCMPR7920I Outstanding Database Descriptionpacket not avail for neighbor neighbor

Explanation: An attempt was made to retransmit aDatabase Description packet to the specified neighbor,but the packet could not be found.

System Action: Retransmission is aborted.



DTCMPR7922I Bad length Link state advertisementreceived from neighbor

Explanation: A link state advertisement has beenreceived from the specified neighbor, and theadvertisement’s length field indicates that the entireadvertisement is NOT fully contained in the receivedLink State Update Packet.

System Action: The partial advertisement isdiscarded.



DTCMPR7923I from neighbor, LS advertisementchecksum fails: LS type type iddestination org source

Explanation: A link state advertisement has beenreceived from the specified neighbor. Theadvertisement is identified by its LS type and two-partoriginating ID. The checksum field contained in theadvertisement is invalid.

System Action: The advertisement is ignored.



DTCMPR7924I from neighbor, bad LS type,advertisement: typ type id destination orgsource

Explanation: A link state advertisement has beenreceived from the specified neighbor. Theadvertisement is identified by its LS type and two-partoriginating ID. The advertisement’s LS type field isinvalid.




DTCMPR7925I from neighbor, AS external link adv.on Virtual Link: typ type id destinationorg source

Explanation: A link state advertisement has beenreceived from the specified neighbor. It was receivedover a virtual link, yet its LS type is equal to ASexternal link. AS external link state advertisementsshould not be sent over virtual links.




DTCMPR7926I from neighbor, old LS advertisement:typ type id destination org source

Explanation: A link state advertisement has beenreceived from the specified neighbor. Theadvertisement is older than the current database copy.




DTCMPR7927I from neighbor, self update: typ type iddestination org source

Explanation: A link state advertisement has beenreceived. The advertisement was originated by therouter itself, yet is newer than the database copy. Thisindicates that it originated before the router was laststarted. This causes the router to either advance the LSsequence number and originate a new instantiation ofthe advertisement, or flush the advertisement, if it’s asummary LSA and the attached area does not wish toimport summary LSAs anymore.



MPROUTE Messages



DTCMPR7928I from neighbor, new LS advertisement:typ type id destination org source

Explanation: A link state advertisement has beenreceived from the specified neighbor. Theadvertisement is newer than the current database copy.

System Action: The advertisement is flooded out allother interfaces, and installed in the routing database.



DTCMPR7929I from neighbor, Old acknowledgmentfor advertisement: typ type id destinationorg source

Explanation: An unexpected link stateacknowledgment has been received from the specifiedneighbor. The acknowledgment, however, is for aprevious instantiation of the link state advertisement.

System Action: The acknowledgment is ignored.



DTCMPR7930I Bad acknowledgment from neighborfor advertisement: typ type id destinationorg source

Explanation: An unexpected link stateacknowledgment has been received from the specifiedneighbor. The acknowledgment, however, is for thecurrent instantiation of the link state advertisement.

System Action: The acknowledgment is ignored.



DTCMPR7931I LS update retransmission to neighborneighbor

Explanation: A Link State Update packet containingretransmitted link state advertisements has been unicastto the specified neighbor. This probably indicatespacket loss during the flooding procedure.




DTCMPR7932I LS acknowledgment sent directly toneighbor neighbor

Explanation: A Link State Acknowledgment packethas been sent directly to the specified neighbor. This isin response to duplicate link state advertisements

received from the neighbor. This probably indicatespacket loss during the flooding procedure.




DTCMPR7933I Flushing advertisement: typ type iddestination org source

Explanation: The specified link state advertisementcontained in the link state database has not beenrefreshed for 2 hours. The advertisement is deletedfrom the database. This probably indicates that theoriginator of the advertisement is unreachable.




DTCMPR7934I Originating LS advertisement: typtype id destination org source

Explanation: The specified link state advertisement isbeing (re)originated by the router. This can be due totopological change, or the necessity to refresh.




DTCMPR7935I New MPROUTE route to destinationdesttype destination, type routetype cost cost

Explanation: The OSPF routing table build process hasdetected a new best route to the specified destination,having the specified cost.

System Action: The new route will be placed inMPROUTE’s internal route table, replacing any existingroute to the same destination if the new route is better.The new route will also be added to the TCP/IP stack’sroute table providing that there is not a static route tothe destination defined to the TCP/IP stack through theGATEWAY configuration statement.



DTCMPR7936I NBMA hello sent to IP destinationneighbor

Explanation: An OSPF hello has been sent to thespecified IP destination. This has been done over anon-broadcast, multi-access interface.




MPROUTE Messages


DTCMPR7937I The OSPF routing protocol isdisposition

Explanation: Displayed on router startup. Indicatesoperational status of the OSPF protocol.




DTCMPR7938I OSPF Interface interface (name) is notan IP interface, interface not installed

Explanation: Displayed on router start up when anOSPF interface address is configured, yet this addresshas not been configured to the TCP/IP stack.

System Action: The OSPF interface is not installed.


System Programmer Response: Modify theMPROUTE configuration file or the TCP/IP stackconfiguration, ensuring that the specified interface isconfigured in both.

DTCMPR7939I Duplicate LS acknowledgmentreceived from neighbor neighbor

Explanation: Unexpected link state acknowledgmenthas been received from the specified neighbor. Thisprobably indicates packet loss during the floodingprocedure.

System Action: The link state acknowledgment isignored.



DTCMPR7940I from neighbor, bad age field,advertisement: typ type id destination orgsource

Explanation: The specified link state advertisementhas been received from the specified neighbor. Theadvertisement’s LS age field is invalid.




DTCMPR7941I Transit area area not configured,virtual link ignored

Explanation: A virtual link has been configured tohave a certain transit area, yet that area has not beenconfigured.

System Action: The virtual link is ignored.


System Programmer Response: Modify theMPROUTE configuration file to correct the transit areaconfigured for the virtual link, if incorrect, or toconfigure the area.

DTCMPR7942I Backbone area is not configured, allvirtual links discarded

Explanation: MPROUTE has found Virtual_Linkconfiguration statements in the OMPROUTEconfiguration file, but the backbone area is notconfigured. Virtual links cannot be used unless abackbone area is configured.

System Action: All Virtual_Link configurationstatements are ignored.


System Programmer Response: Modify theMPROUTE configuration statement to configure thebackbone area.

DTCMPR7943I Destination desttype destination nowunreachable

Explanation: The specified destination has been foundto be unreachable during the OSPF routing table buildprocess.

System Action: The route to the specified destinationwill be removed from MPROUTE’s internal route tableas well as the TCP/IP stack’s route table.



DTCMPR7945I from neighbor, received unexpectedMaxAge: typ type id destination org source

Explanation: The specified link state advertisementhas been received from the specified neighbor. Its age isMaxAge and there is no current instantiation of theadvertisement in the router’s database.

System Action: The advertisement is acknowledgedand then discarded without flooding.



DTCMPR7946I error in advertisement: typ type iddestination org source

Explanation: The specified link state advertisementhas been received from the specified neighbor. Theadvertisement contains an error.

System Action: The advertisement is discarded.


System Programmer Response: Contact themanufacturer of the OSPF application on the source

MPROUTE Messages


router to report the problem.

DTCMPR7947I Stub area mismatch in hello fromsource

Explanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the attached area’s ability to processAS external link advertisements.

System Action: The Hello packet is ignored.


System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the routers agree on the attached area’sstub status.

DTCMPR7948I from neighbor, type 5 LSA in stubarea, adv: typ type id destination orgsource

Explanation: A type 5 (AS External Link) link stateadvertisement has been received from the specifiedneighbor. The advertisement is being flooded through astub area, and is therefore ignored.

System Action: The link state advertisement isdiscarded.



DTCMPR7949I Dijkstra calculation performed, onnumber area(s)

Explanation: As a result of a topology change, therouting table has been recalculated, starting with theDijkstra calculation.




DTCMPR7950I Network LSA with old AdvertisingRouter: (type,destination,source)

Explanation: A network links advertisement havingone of our addresses as Link State ID, but whoseAdvertising Router is not our Router ID, has beenreceived. These advertisements are flushed, as they areassumed to be out-of-date.

System Action: The advertisement is flushed.



DTCMPR7951I Reparsing Network LSA: LS_ID

Explanation: A network link is being reparsed, owingto the fact that there are multiple network-LSAs in thenetwork with the same Link State ID. This indicatesthat a router has changed OSPF Router IDs, and hasoriginated the same router-LSA before and after thechange. This is a normal, but rare, event.




DTCMPR7956I OSPF area area not configured,interface interface not installed

Explanation: Displayed on router startup when anOSPF interface address is configured, but the attachedarea configured for the interface is not a configuredarea.

System Action: MPROUTE continues, but thespecified interface will not be used as an OSPFinterface.


System Programmer Response: Modify theMPROUTE configuration file to correct theAttached_Area parameter on the specifiedOSPF_Interface statement, if incorrect, or to configurethe area.

DTCMPR7961I Demand circuit support active forarea area

Explanation: Displayed when there are no more DCbit clear LSAs in any of the area’s link state databasesand it is valid to set the DoNotAge bit.




DTCMPR7962I Demand circuit support not active forarea area

Explanation: Displayed when an LSA with the DC bitclear is added to one of the area’s link state databasesand any LSAs with the DoNotAge bit set are purged.




MPROUTE Messages


DTCMPR7963I Unchanged advertisement: typ type iddestination org source suppressed fordemand interfaces

Explanation: Displayed when an LSA is not floodedover one or more circuits configured as demand circuitsbecause there is no change in the content of the LSAfrom a previous version.




DTCMPR7964I Hello’s on interface interface toneighbor neighbor are being suppressed.

Explanation: Displayed when hello suppressionbecomes active for the specified interface and neighbor.




DTCMPR7965I Cbit clear indicate LSA received inarea area from source.

Explanation: Displayed when a special type 4 indicateLSA is received in a non stub area to indicate thepresence of routers outside the area that do not supportDoNotAge processing.




DTCMPR7966I Cbit clear indicate LSA originated inarea area.

Explanation: Displayed when the local routeroriginates a special type 4 indicate LSA to indicate thepresence of routers outside the area that do not supportDoNotAge processing.




DTCMPR7967I advertisement discarded, overflowsbuffer: LS type type id destination orgsource

Explanation: A link state advertisement was discardedbecause it would be too large to fit in the router’s dataarea. A router links LSA has become excessively largedue to a large number of direct connections to neighborrouters within a single area.



System Programmer Response: Reconfigure thenetwork to reduce the size of the largest link stateadvertisement or increase the size of router data areasto hold the LSA. The data area used to build LSAs canbe increased to the size of the local router’s buffer byconfiguring the maximum LSA size. The size of thelocal router’s buffer can be enlarged by increasing thesize of the largest mtu for a locally attachedsubnetwork.

DTCMPR8000I bad version version received fromhost source

Explanation: The version field in the RIP header didnot match the current version. This is probably causedby an error in the source host.

System Action: The received RIP packet is ignored.


System Programmer Response: Contact themanufacturer of the source host and report theproblem.

DTCMPR8001I request received from host source

Explanation: A RIP routing table request was receivedfrom another host.

System Action: A routing table update will be sent tothe requesting host.



DTCMPR8002I trace on to file received from hostsource

Explanation: A request from a host to turn RIP tracingon to a given log file was received.

System Action: This request is ignored.



DTCMPR8003I trace off received from host source

Explanation: A request from a host to turn RIP tracingoff was received.

System Action: This request is ignored.



MPROUTE Messages


DTCMPR8004I response received from host source

Explanation: A RIP routing table update was received.Note that it may take more than one response packet totransmit the entire routing table, especially if therouting table is large.




DTCMPR8005I bad command code command receivedfrom host source

Explanation: A RIP message was received with anunrecognized command code. This is probably causedby an error or out of date software in the source host.



System Programmer Response: Contact themanufacturer of the source host and report theproblem.

DTCMPR8006I response received from off networkhost source

Explanation: A RIP routing update response wasreceived from a machine which was not directlyattached to the network the response came in on. Sincenormal RIP software is generally written to send dataonly to connected nets, this is probably indicative of ahostile event.



System Programmer Response: Examine audit trailsand other information to determine the original sourcehost.

DTCMPR8008I dynamic route to destination fromsource disallowed

Explanation: A dynamic route was received but isbeing ignored because the configuration of RIP on therouter does not allow dynamic routes except for thosein a table, and this route was not in that table.

System Action: Received dynamic route is ignored.



DTCMPR8009I network destination now unreachablevia router router, deleted

Explanation: An incoming RIP update from the routerthat was previously listed as the next hop to thedestination network has announced that the destination

is unreachable (i.e. at metric ’infinity’). The RIP route tothat destination is being deleted.

System Action: The route is deleted from MPROUTE’sinternal route table as well as the TCP/IP stack’s routetable.



DTCMPR8010I update route to net destination atmetric metric hops via router router

Explanation: A new (better) route to the givendestination has been learned through RIP and has beeninstalled.

System Action: The new route will be placed inMPROUTE’s internal route table, replacing any existingroute to the same destination if the new route is better.The new route will also be added to the TCP/IP stack’sroute table providing that there is not a static route tothe destination defined to the TCP/IP stack through theGATEWAY configuration statement.



DTCMPR8011I send request to address source

Explanation: MPROUTE is sending a RIP request fromeach of the addresses associated with an interfacewhich has just come up.




DTCMPR8012I sending broadcast response toaddress destination in count packets withnumber routes

Explanation: The router is sending a normal RIPbroadcast update (triggered either by a timer or achange in the routing table) to the specified address.




DTCMPR8013I sending response to addressdestination in count packets with numberroutes

Explanation: The router is sending a RIP update(triggered by a request from another host) to thespecified address.



MPROUTE Messages



DTCMPR8015I sending packet to destination

Explanation: A RIP packet (either a routing tableupdate, or when an interface first comes up, a request)was sent to the specified destination.




DTCMPR8017I network route to destination timed out

Explanation: There was a route in the route table tothe specified destination through a router which hasnot been heard from for a while. The route has beendeleted.

System Action: The route is marked unreachable inMPROUTE’s internal route table and is deleted fromthe TCP/IP stack’s route table.



DTCMPR8018I network route to destination deleted

Explanation: There was a route in the route table tothe specified destination through a router which hasnot been heard from for a while. The route waspreviously marked unreachable, and is now beingdeleted.

System Action: The route is deleted from MPROUTE’sinternal route table.



DTCMPR8019I Mismatch version version receivedfrom host source

Explanation: The version field in the received RIPheader did not match the configured version on thereceiving interface.



System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the RIP version configured for theappropriate interfaces match.

DTCMPR8020I Authentication error received fromhost source

Explanation: A RIP packet from the specified host hasbeen rejected due to an authentication error caused byeither invalid authentication info or authentication not

being enabled. This is probably caused by amisconfiguration.



System Programmer Response: Modify theconfiguration on either the source or local router,ensuring that the authentication configurations areconsistent.

DTCMPR8021I sending RIP2 response to addressdestination from source in count packetswith number routes

Explanation: The router is sending a normal RIP2update (triggered either by a timer or a change in therouting table) to the specified address.




DTCMPR8023I The RIP routing protocol is disposition

Explanation: Displayed on router start up. Indicatesoperational status of the RIP protocol.




DTCMPR8024I RIP message received on non RIPinterface source from destination isignored.

Explanation: A RIP routing message was received onan interface which is not configured as a RIP interface.




DTCMPR8025I RIP send to destination fails

Explanation: An attempt to send a RIP packet to theindicated destination has failed. This may be atemporary condition, however if the message is issuedrepeatedly this condition requires attention.



System Programmer Response: Other MPROUTEmessages will give the errno explanation for thisfailure.

MPROUTE Messages


DTCMPR8054I Add failed for net network; badnetwork number

Explanation: This message is generated when anetwork cannot be added to the routing table becauseof a bad network number. This software considers thenet above to be invalid.



System Programmer Response: If the net is valid,there is a possible internal error, contact the IBMSupport Center.

DTCMPR8055I Re-adding static route to net network

Explanation: This message is generated when a staticroute to a network is brought back into use.




DTCMPR8057I Added network network to interfaceinterface on net net_index interface name

Explanation: This message is generated when a routeto a directly-connected network is added toMPROUTE’s internal routing table as a result of theroute being defined to the TCP/IP stack through theGATEWAY statement.




DTCMPR8058I Ignoring bad static route to network,mask mask

Explanation: This message is generated when a badstatic route is encountered.




DTCMPR8059I Added network network with routevia gateway on net net_index interfacename

Explanation: This message is generated when a routeto a indirectly-connected network is added toMPROUTE’s internal routing table as a result of theroute being defined to the TCP/IP stack through theGATEWAY statement.




DTCMPR8061I Deleted net network route via gatewaynet net_index interface name

Explanation: This message is generated when aninterface goes down and the corresponding route isdeleted from the route table.




DTCMPR8062I Subnet network defined

Explanation: This message is generated when a newsubnetted network is defined.




DTCMPR8063I Deleting subnetted network network

Explanation: This message is generated when asubnetted network is deleted. This happens when thereare no longer any interfaces to that network.




DTCMPR8064I RIP disabled on interface variablelength subnet masks

Explanation: The router is configured with variablelength subnet masks on the same network, which RIPcan’t handle. Thus RIP is disabled on the interface.




DTCMPR8066I IP protocol does not run over type

Explanation: An IP address was configured for a typeof network which currently doesn’t support IP.




MPROUTE Messages


DTCMPR8067I Network net_index interface name isinactive

Explanation: This message is generated when aninactive network interface is encountered duringinitialization, no direct routes will be created on thisnetwork.




DTCMPR8079I SMSG command from user_id notauthorized

Explanation: The listed user ID was not found in theOBEY list. Only user IDs that are defined in the OBEYlist are authorized to issue SMSG commands to theMPROUTE server.

System Action: MPROUTE continues.

User or Operator Response: Notify the systemprogrammer about this action, if warranted.

System Programmer Response: If this user shouldhave this authority, update the OBEY list. See TCP/IPPlanning and Customization for more information.

DTCMPR8081I Cannot establish communicationservices with the TCP/IP stack

Explanation: The BEGINtcpIPservice routine failedwhen MPROUTE attempted to establish a connection tothe TCP/IP stack.

System Action: MPROUTE ends abnormally.

User or Operator Response: Notify the systemprogrammer about the problem.

System Programmer Response: Verify the TCP/IPstack is operational. If necessary, restart the TCP/IPserver.

DTCMPR8087E Unable to start MPROUTE. Adynamic router is already running.

Explanation: Currently another dynamic Router isalready running with the TCP/IP stack.

System Action: MPROUTE ends abnormally.


System Programmer Response: Verify which dynamicrouter you wish to run and only have this one runningwith the stack.

DTCMPR8088I The (ETC GATEWAYS) file wasfound, MPROUTE server will ignore it

Explanation: This is an informational message only. Itis issued for migration issues. This ensures the userknows that the ETC GATEWAYS file is not going to beissued by the MPROUTE server.

System Action: MPROUTE continues.



MPROUTE Messages


MPROUTE Messages


Chapter 7. NETSTAT Messages

This chapter contains the NETSTAT messages used to monitor the network. Forproblems, see the TCP/IP User’s Guide or TCP/IP Planning and Customization formore information which may be of assistance in resolving the problem.

DTCNET100E NETSTAT: Missing parameter afterDROP

Severity: Error.

Explanation: You specified a DROP parameter withouta value.

System Action: The NETSTAT program exits.

User or Operator Response: Specify the TCP/IPconnection address to drop following the DROPparameter, and resubmit the NETSTAT command.

For information about the DROP parameter of theNETSTAT command, see TCP/IP User’s Guide.

Source File: CMNETST PASCAL

Procedure Name: ParseCommandLine

DTCNET101E NETSTAT: TCP parameter requires avirtual machine

Severity: Error.

Explanation: You specified a TCP parameter withoutspecifying a TCP/IP server.


User or Operator Response: Specify a TCP/IP serverfor which commands are to be directed, and re-submitthe NETSTAT command. For more information aboutthe TCP parameter of the NETSTAT command, see theTCP/IP User’s Guide.



DTCNET103E Invalid parameter: BadParameter

Severity: Error.

Explanation: You specified an invalid parameter.


User or Operator Response: Remove the invalidparameter and resubmit the NETSTAT command.

For information about the syntax of the NETSTATcommand, see TCP/IP User’s Guide.



DTCNET104E Invalid option(s) specified withINTERVAL: options

Severity: Error.

Explanation: You specified an extraneous option onthe NETSTAT command.


User or Operator Response: Remove the extraneousoption and resubmit the NETSTAT command. Forinformation about the syntax of the NETSTATcommand, see the TCP/IP User’s Guide.

Source File: NETSTAT EXEC

DTCNET105E NetStat Error: explanation

Severity: Error.

Explanation: TCP/IP could not obtain requestednetwork statistics. An error was encountered asdescribed by the explanation.


User or Operator Response: One of the followingNETSTAT options could not obtain the requiredinformation:v Allconnv Connv Devlinksv Gatev Homev Poolv Socketv Telnet.

Inform the system programmer the NETSTAT option inwhich you encountered the error.

System Programmer Response: Check the TCP/IPProfile in the PROFILE TCPIP file for the definition ofthe erroneous NETSTAT option.

For information about modifications to the TCP/IPProfile, see TCP/IP Planning and Customization.


Procedure Name: BadReturnCode


|

||

|

||

|

|||||

|

|

|

||

|

||

|

||||

|

|

DTCNET154E explanation

Severity: Error.

Explanation: An error occurred processing theNETSTAT CP parameter as described by the explanation.


User or Operator Response: Examine the error asdescribed by the explanation. Resolve the problem andresubmit the NETSTAT command.


Procedure Name: DoCpCmd

DTCNET160E No such connection

Severity: Error.

Explanation: A connection could not be successfullydropped.


User or Operator Response: The drop parameterspecified an unknown connection. Verify the connectionparameter, and resubmit the NETSTAT command.

For information about the DROP parameter of theNETSTAT command, see the TCP/IP User’s Guide.



DTCNET266E Cannot use TCP/IP: explanation

Severity: Error.

Explanation: TCP/IP could not begin processing. Anerror has been encountered as described by theexplanation.


User or Operator Response: Inform the systemprogrammer of the type of error you have encountered.

System Programmer Response: Modify TCP/IP tocorrect the problem the user encountered. Forinformation about modifications to TCP/IP, see TCP/IPPlanning and Customization.


Procedure Name: Main

DTCNET325E TCPIP reports error: You are notauthorized to issue this command

Severity: Error.

Explanation: You are not authorized to issueNETSTAT commands CP, DelArp, Drop, ResetDos orResetPool.

System Action: The request is ignored. Processing

continues with the next request.

User or Operator Response: Ask the systemprogrammer to authorize you to use the privilegedNETSTAT commands.

System Programmer Response: Modify the TCP/IPOBEY statement to allow the user to issue NETSTATcommands.

For information about modifications to TCP/IP OBEYstatement, see the TCP/IP Planning and Customization.


Procedure Name: DoDrop, DoResetPoolInform,DoCpCmd, DoDeleteArp, DoResetDos

DTCNET326E Netstat: Missing or invalid parameterafter ARP

Severity: Recoverable error.

Explanation: The parameter following ARP is eithernot valid or missing.


User or Operator Response: Specify the TCPIPaddress to be queried by ARP, and re-enter theNETSTAT command.




DTCNET331E INTERVAL option must be invokedvia the NETSTAT EXEC

Severity: Error.

Explanation: The NETSTAT MODULE was invokeddirectly.


User or Operator Response: Change the invocationsuch that the NETSTAT EXEC gets executed. (ie.″address command ’NETSTAT INTERVAL’″ is notallowed)



DTCNET338E Addr MAC address is not in the ARPtable


Explanation: The address specified is not currently inthe ARP table.




NETSTAT Messages


|

|

|

|

|||

|

||

||||

|

|

||

|

|||

|

|

|||

|||

||

|

||

|

||

|

||

|

||||

|

|

|


Procedure Name: DoQueryArp

DTCNET339E Userid specified for TCP must be 8characters or less

Severity: Error.

Explanation: You specified a TCP/IP server name thatis too long.

System Action: The NETSTAT programs exits.

User or Operator Response: Specify a valid TCP/IPserver user ID and resubmit the NETSTAT command.For more information about the TCP parameter of theNETSTAT command, see the TCP/IP User’s Guide.



DTCNET341E NETSTAT: Missing or invalid IPaddress after DELARP

Severity: Error.

Explanation: The parameter following DELARP iseither not valid or missing.


User or Operator Response: Specify a valid IP addressto be deleted from the ARP cache and re-enter theNETSTAT command.



DTCNET343E NETSTAT: Missing or invalidparameter after IDENTIFY

Severity: Error.

Explanation: The parameter following IDENTIFY iseither not valid or missing.


User or Operator Response: Specify a valid IP addressto produce information identifying the associatedconnections. For more information about the IDENTIFYparameter of the NETSTAT command, see the TCP/IPUser’s Guide.



DTCNET347E NETSTAT: Missing or invalid IPaddress after BLOCK

Severity: Error.

Explanation: The parameter following BLOCK iseither not valid or missing.


User or Operator Response: Re-enter the NETSTATcommand with a valid IP address you wish to ignoreor allow incoming traffic from. For more informationabout the BLOCK parameter of the NETSTATcommand, see the TCP/IP User’s Guide.



DTCNET348E NETSTAT: Missing or invalid IPaddress after UNBLOCK

Severity: Error.

Explanation: The parameter following UNBLOCK iseither not valid or missing.


User or Operator Response: Re-enter the NETSTATcommand with a valid IP address you wish to ignoreor allow incoming traffic from. For more informationabout the UNBLOCK parameter of the NETSTATcommand, see the TCP/IP User’s Guide.



DTCNET349E TCPIP reports error explanation

Severity: Error.

Explanation: While processing the NETSTATRESETPOOL option, an error has been encountered asdescribed by the explanation.


User or Operator Response: Inform the systemprogrammer that you encountered an error processingthe NETSTAT RESETPOOL option.

System Programmer Response: Check the PROFILETCPIP file for the definition of the POOLSIZE.

For information about modifications to the TCP/IPProfile POOLSIZE, see the TCP/IP Planning andCustomization.


Procedure Name: DoResetPoolInform

DTCNET371E Netstat: Connection number ConnNumis not valid

Severity: Error.

Explanation: The indicated connection number is nota valid setting for the NETSTAT DROP statement. Theconnection number must be numeric.


User or Operator Response: Specify a valid numeric

NETSTAT Messages

Chapter 7. NETSTAT Messages 121

||

|

||

|

||||

|

|

||

|

||

|

|||

|

|

||

|

||

|

|||||

|

|

||

|

||

|

|||||

|

|

||

|

||

|

|||||

|

|

|

|

TCP/IP connection number to drop following theDROP parameter, and resubmit the NETSTATcommand.




DTCNET400W A denial-of-service attack has beendetected; issue NETSTAT DOS for moreinformation.

Severity: Warning.

Explanation: One or more denial-of-service attackshave been detected. This message will continue to beissued on all future NETSTAT commands until either aNETSTAT DOS or NETSTAT RESETDOS command isissued.


User or Operator Response: Issue the NETSTAT DOScommand to obtain information about the type andfrequency of attacks.



DTCNET500E MonQuery fails: explanation

Severity: Error.

Explanation: TCP/IP could not obtain the RequestedControl Block information. An error has beenencountered as described by the explanation.


User or Operator Response: One of the followingNETSTAT options could not obtain the requiredControl Block information:v Allconnv Conn.

Inform the system programmer the NETSTAT option inwhich you encountered the error.

System Programmer Response: Check the TCP/IPProfile in the PROFILE TCPIP file for the definition ofthe erroneous NETSTAT option.

For information about modifications to the TCP/IPProfile, see TCP/IP Planning and Customization.


Procedure Name: PipeData

DTCNET501E explanation

Severity: Error.

Explanation: The OBEY function encountered an errordescribed by the explanation.


User or Operator Response: Correct the error andre-enter the NETSTAT command.


Procedure Name: DoObey

DTCNET504E NETSTAT: Missing statement afterOBEY

Severity: Error.

Explanation: You used the OBEY function withoutspecifying a configuration statement to be processed.


User or Operator Response: Specify the TCP/IPconfiguration statement to be processed following theOBEY function and re-enter the NETSTAT command.For information about the OBEY function of theNETSTAT command, see TCP/IP User’s Guide.


Procedure Name: DoObey

DTCNET509E Selecting connections can only bedone with ALL, ALLConn, CLients,COnn, Gate, IDENTify, Interval, TELnet


Explanation: You attempted to select a connectionwithout the use of one of the specified parameters.


User or Operator Response: Specify a valid NETSTATcommand before selecting connections and re-enter theNETSTAT command.



Procedure Name: LimitSearchTo

DTCNET510E Parenthesis but no search criteria


Explanation: You specified a NETSTAT commandwithout the appropriate search criteria.


User or Operator Response: Specify the search criteriaand re-enter the NETSTAT command.




NETSTAT Messages


|||

|

|||||

|

|||

|

|

|

|

|

||

|

||

|

|

||

|

||

|

|||||

|

|

|

|

DTCNET511E Close parenthesis precedes searchcriteria


Explanation: You entered the NETSTAT commandwith incorrect syntax.


User or Operator Response: Correct the syntax errorby removing the close parenthesis before the searchcriteria, and re-enter the NETSTAT command.




DTCNET512E Too many selection values: Maximumis number


Explanation: You specified too many selection values.


User or Operator Response: Remove extraneousselections and re-enter the NETSTAT command.




DTCNET513E Search criteria parameter string is toolong


Explanation: You specified a search parameter stringthat was longer than 16 characters.


User or Operator Response: Correct the search criteriaparameters and re-enter the NETSTAT command.




DTCNET514E Select Option Specified but no searchcriteria


Explanation: You specified a NETSTAT commandwithout the appropriate search criteria.


User or Operator Response: Specify the search criteriaand re-enter the NETSTAT command.




DTCNET515E Invalid netstat option: option


Explanation: You specified a NETSTAT commandwith an invalid option.


User or Operator Response: Re-enter the NETSTATcommand with a valid option.




DTCNET516E Interval value of val is invalid

Severity: Error.

Explanation: You specified an interval value that isnot valid and could not be interpreted.


User or Operator Response: Specify a valid intervaland re-enter the NETSTAT command. For moreinformation about the Interval parameter of theNETSTAT command, see the TCP/IP User’s Guide.



DTCNET517E Interval value of val is invalid.Maximum allowed is 3600

Severity: Error.

Explanation: You specified an interval value that istoo large.


User or Operator Response: Specify a valid intervalvalue between 1 and 3600 seconds and re-enter theNETSTAT command. For more information about theInterval parameter of the NETSTAT command, see theTCP/IP User’s Guide.



NETSTAT Messages

Chapter 7. NETSTAT Messages 123

|

|

|

|

|

|

|

NETSTAT Messages


Chapter 8. NFS Messages

This chapter contains Network File System (NFS) messages.

Numbered MessagesThis section contains the numbered messages.

DTCNFS1300E Mask argument should be followedby hexadecimal mask value.

Explanation: An incorrect syntax was received for arequest to set the mask for the VMNFS server internaltrace facility.

System Action: The default mask value is used.

User or Operator Response: Either restart the VMNFSserver with a correct mask value or use the SMSGcommand to reset the mask.

Source File: NFSMAINC C

Procedure Name: main

DTCNFS1301E Mask value mask is invalid; must behexadecimal.

Explanation: An incorrect value was received for arequest to set the mask for the VMNFS server internaltrace facility.

System Action: The default mask value is used.

User or Operator Response: Either restart the VMNFSserver with a correct mask value or use the SMSGcommand to reset the mask.



DTCNFS1302I Trace mask value set to mask

Explanation: The mask for the VMNFS server internaltrace facility has been set.





DTCNFS1303E Buffer argument should be followedby decimal number.

Explanation: An incorrect syntax was received for arequest to set the number of disk block buffers to beused by the VMNFS server.

System Action: The default number of block buffers is256.

User or Operator Response: If desired, restart theVMNFS server with a correct block buffers value.



DTCNFS1304E Number of buffers value buffers isinvalid; must be decimal number.

Explanation: An incorrect value was received for arequest to set the number of disk block buffers to beused by the VMNFS server.


User or Operator Response: If desired, restart theVMNFS server with a correct disk block buffers value.



DTCNFS1305E Number of buffers value buffers is toosmall; using default of default_buffers.

Explanation: The number of disk block buffersspecified is too small.


User or Operator Response: If desired, restart theVMNFS server with a correct block buffers value.



DTCNFS1306I Number of disk block buffers set tonnnn

Explanation: This informational message was issuedbecause the B argument was specified when VMNFSwas invoked.






DTCNFS1307E Invalid VMNFS command argumentignored: number nn, value hex-value

Explanation: An invalid argument was specified whenVMNFS was invoked.

System Action: The incorrect value is ignored.

User or Operator Response: Correct the argument andreissue the command.



DTCNFS1308I access-type access control will be usedto validate NFS minidisk mountrequests.

Explanation: This message displays the type of accesscontrol used (for example CP link password, ExternalSecurity Manager (ESM), or Autolink).


User or Operator Response: If you wish to change theaccess control used, restart VMNFS with theappropriate argument.



DTCNFS1309I Anonymous access will be allowed

Explanation: :Anonymous.Yes has been specified inDTCPARMS, or the 'N' start-up parameter was used,indicating that the VMNFS server will allowanonymous MOUNT requests. Anonymous MOUNTrequests are those that do not specify userid= andpassword= parameters in the MOUNT or in apreceding MOUNTPW or PCNFSD request.


User or Operator Response: If anonymous access isnot desired, change the DTCPARMS entry to:Anonymous.No and restart the server.



DTCNFS1310I External mount monitor VMNFSMONEXEC will be used

Explanation: This message indicates an externalmonitor is present to screen mount requests and givesthe file mode where the exec was found.





DTCNFS1312I No external mount monitor(VMNFSMON EXEC) is present.

Explanation: The VMNFS server did not find anexternal mount monitor.

System Action: No external mount monitor is used.

User or Operator Response: If necessary, restartVMNFS to access the disk with the VMNFSMONEXEC.



DTCNFS1313I Opened debug file vmnfs.log

Explanation: The ’D’ (debug) argument was specifiedwhen VMNFS was started.

System Action: Trace information will be written tovmnfs.log.




DTCNFS1314I Registration with Portmap failed;waiting 30 seconds before trying again.

Explanation: The registration by VMNFS with the portmapper has failed.

System Action: VMNFS attempts registration threetimes.

User or Operator Response: If necessary, determine ifthe port mapper is available.



DTCNFS1315I Registration completed.

Explanation: Registration with the port mapper hascompleted.

System Action: VMNFS processing continues.




DTCNFS1316S nfsmain: return code returncode fromcextpost

Explanation: An attempt to create an interrupthandler failed. The return code is listed to help withproblem resolution.

NFS Messages


System Action: VMNFS server processing terminates.

User or Operator Response: See the HNDEXTmacroinstruction in the z/VM: CMS Macros andFunctions Reference.



DTCNFS1318E Unexpected exit code exitcode from:function

Explanation: An unexpected error occurred whenissuing the listed command. In order to process clientrequests for SFS objects asynchronously, VMNFS has itsown CSL routines to front-end DMSMARK. Set-upprocessing to load and drop the CSL routines failedwith the listed exitcode.

System Action: VMNFS Server processing continueswithout SFS requests.

User or Operator Response: Try to determine thereason for the error. Error codes for functions such asRTNLOAD and RTNDROP are documented in thez/VM: CMS Command and Utility Reference. If it can notbe corrected, report it to the IBM Support Center.



DTCNFS1321I SFS operations will be supported.

Explanation: This message indicates that NFS clientrequests for SFS objects will be honored.





DTCNFS1322E Exit code = exitcode from call toVMNFSANC

Explanation: The call to load the VMNFSANCMODULE as a nucleus extension failed.

System Action: VMNFS Server processing terminates.

User or Operator Response: etermine why the modulecannot be located or loaded. The listed exitcodes for theNUCEXT SET macroinstruction are documented in thez/VM: CMS Macros and Functions Reference, and shouldhelp with problem determination. If necessary, call theIBM Support Center.



DTCNFS1324I External interrupt requestedtermination.

Explanation: The VMNFS server received a request toterminate the server.





DTCNFS1325E Unknown POST code for nfsecb:postcode (0xhex-postcode) ignored at time.

Explanation: An ECB post call was received that wasnot recognized by the VMNFS server.

System Action: The ECB post is ignored.




DTCNFS1329E time Error code ReturnCode fromaborted task.

Explanation: The task was aborted at the given timewith the listed return code. A failure occurred thatprevents a task from completing. If this conditionrecurs, it may be because of a damaged CMS minidiskfile system. Task abort codes are defined in nfs.h (seeABORT_BAD_IO and so on).

System Action: VMNFS Server processing continues.

User or Operator Response: If you cannot determinea cause for the problem, call the IBM Support Center.Restart the VMNFS program after such an error if thereis any indication of unusual problems. Most suchproblems cause an automatic restart by a call toSIGERROR.

Source File: NFSMAIN C


DTCNFS1331S Error code ReturnCode from c_ciucvsever path pathid

Explanation: This message indicates a c_ciucv severpath failure. The nonzero return code and the pathid arelisted to help with problem resolution. This difficulty isdetected when the VMNFS server tries to change aread-only link to a disk into a read-write link, becauseit has received a valid client request that requires writeaccess. For the client request to be valid, the subjectdisk was linked read-write at some time in the past:either a restart of the VMNFS server, or an SMSGdetach request from a CMS user, caused the earlierwrite link to be detached.

System Action: The program exits by calling

NFS Messages

Chapter 8. NFS Messages 127

SIGERROR, which leads the VMNFS PROFILE EXEC torestart the NFS server.

User or Operator Response: If this condition recurs,report it to the IBM Support Center.

Source File: FH@HIST C

Procedure Name: fh_check

DTCNFS1332S fh_check: error code ReturnCode (xrc)from c_ciucv connect request to vaddrvaddr disk userid.address

Explanation: VMNFS tried to connect a new IUCVpath to *BLOCKIO for a disk that has been changedfrom its earlier read link mode-only to the new linkmode read-write. See the related message: Error code rc(rc) from c_ciucv sever path pathid (pathid)

System Action: The program continues. An errorstatus is sent to the NFS client.

User or Operator Response: A restart of the VMNFSserver can help. If the error recurs, report it to the IBMSupport Center.



DTCNFS1333S Vaddr vaddr userid.address

Explanation: Identifies the disk for which an IUCVconnection request to *BLOCKIO failed. This isfollowed by a call to SIGERROR.





DTCNFS1334E db_lookup: File Handle type isFILEPOOL; corresponding History Filerecord type is minidisk; serial number isSerialNumber.

Explanation: This message indicates a problem withthe File Handle history file (VMNFS HISTORY). Thefile handle indicates the mounted object is a SFS or BFSdirectory, but the matching record in the file handlehistory file does not contain the same indication.

System Action: The NFS client’s request isabandoned.

User or Operator Response: Try to determine whetherthe history file is corrupt or the client sent a bad filehandle. Clear the VMNFS HISTORY file as described in'Configuring the Network File System' in the TCP/IPPlanning and Customization.


Procedure Name: db_lookup

DTCNFS1335E time ck_mdate finds invalid label ondisk userid.address.

Explanation: VMNFS can not find the label record onthe listed minidisk.

System Action: VMNFS will attempt to detach thefailing minidisk.

User or Operator Response: Determine if there is aproblem with the minidisk and if necessary, call theIBM Support Center.


Procedure Name: ck_mdate

DTCNFS1336I time ck_mdate is detachinguserid.address.

Explanation: This message is issued after messageDTC1335E. VMNFS is detaching the minidisk.





DTCNFS1337E ck_mdate: RC=ReturnCode fromdetach.

Explanation: VMNFS received a nonzero return codewhile detaching a minidisk. The ReturnCode is listed tohelp with problem isolation.


User or Operator Response: If the error recurs, reportit to the IBM Support Center.



DTCNFS1338E ck_mdate: RC=ReturnCode fromrefresh during detach processing.

Explanation: VMNFS received a nonzero return codeduring detach processing. The ReturnCode is listed tohelp with problem isolation.

System Action: VMNFS server processing continues.

User or Operator Response: If the problem recurs,report it to the IBM Support Center.



NFS Messages


DTCNFS1339E time open_path: userid.address is not aCMS EDF minidisk.

Explanation: The label read from a disk indicates thedisk is not a CMS format disk.

System Action: Error status is returned to the NFSclient.


Source File: RDLABEL C

Procedure Name: open_path

DTCNFS1340E open_path error code code (0xcode)device address

Explanation: Valid values are as follows:

< 0: c_iucv value * -1 (error in CMSIUCV .connect macro).> 0 error from *BLOCKIO:

<100 = error in connect to *BLOCKIO request.>100 = (100 + error in *BLOCKIO read request).

1000 = Bad label format.

System Action: Error status (such as ENOMEM) isreturned to the NFS client.



Procedure Name: rdlabel

DTCNFS1342E Invalid argument arg ignored.

Explanation: The VMNFS server received an SMSGrequest with an invalid argument.


User or Operator Response: Correct the commandand reissue.

Source File: REQSMSG C

Procedure Name: smquery

DTCNFS1343I Valid query arguments are: LINK,MOUNT, RESOURCE, and CONFIG

Explanation: An invalid SMSG QUERY request wassent to the VMNFS server. The valid arguments arelisted in the message.


User or Operator Response: Correct the QUERYcommand and reissue.


Procedure Name: smquery

DTCNFS1350I Refresh command came from: userid atnodeid

Explanation: This message accompanies a previousmessage with an invalid syntax. It indicates where theoriginal request was issued from.




Procedure Name: smrefresh

DTCNFS1351W Disk userid.address is not currentlylinked.

Explanation: The disk specified in a REFRESH orDETACH request is not linked. This may occur becausethe VMNFS server has restarted and not received aclient request for which this disk was needed. It mayalso occur because a CMS user has already sent aDETACH request that specified this disk.

System Action: The program returns to the caller.



Procedure Name: smrefresh, smdetach

DTCNFS1352E time Refresh request for [userid.address| VMNFS.CONFIG] rejected becauseunique access cannot be obtained

Explanation: VMNFS attempted to gain control of theminidisk to be refreshed, or of the VMNFS server as awhole, but could not.


User or Operator Response: Reissue the refreshcommand.



DTCNFS1353I [Disk | File] [userid.address|VMNFS.CONFIG] refreshed.

Explanation: The request to refresh the minidisk orVMNFS CONFIG file was successful.





NFS Messages


DTCNFS1354E time [Disk | File] [userid.address |VMNFS.CONFIG] refresh failed; errorcode = ReturnCode

Explanation: For VMNFS.CONFIG, an error wasreceived while trying to check for the file’s existence orread the file.

For userid.address, valid values are as follows:< 0: c_iucv value * -1 (error in CMSIUCV.connect macro).> 0: error from *BLOCKIO:

<100 = error in connect to *BLOCKIO request.>100 = (100 + error in *BLOCKIO read request).

1000 = Bad label format.


User or Operator Response: Examine the error codeand earlier console messages, and try to determine thecause for a refresh failure. If you are unable to resolvethe problem, contact your IBM Support Center forassistance.



DTCNFS1356I time SMSG from userid, string

Explanation: When certain tracing is activated, thismessage displays the response, string, sent to user IDuserid as a result of processing an SMSG request.





DTCNFS1357E detach: rc = ReturnCode from IUCVsever path pathid for device vaddr(userid.address disk).

Explanation: An IUCV sever path for the listed pathidfailed for the listed return code reason. The sever pathoperation was issued because a CMS user sent a detachrequest to the VMNFS server specifying the disk forwhich this path was established to the *BLOCKIOsystem service.

System Action: The storage used by the Device Blockis freed and the listed return code is returned to thecaller.

User or Operator Response: Examine the return codeand try to determine the cause for a sever path failure.Re-IPL the VMNFS virtual machine; it re-establishesminidisk links and open IUCV paths automatically asclient requests are received that refer to those CMSdisks.


Procedure Name: smdetach

DTCNFS1359I time SMSG from origin: detachuserid.address

Explanation: A request was received to detach thelisted minidisk.

System Action: VMNFS will process the detachrequest.




DTCNFS1360I RC=Return_Code from detachinguserid.address

Explanation: An error occured while processing adetach request. This message, sent to the requester if acommand reply is desired, records that an erroroccurred during the processing of a detach SMSGrequest.

System Action: The detach request is aborted.




DTCNFS1361E RC = ReturnCode from refreshuserid.address during detach processing.

Explanation: One of the first steps in processing adetach SMSG request is to execute the code that is usedto purge disk buffers for a refresh operation. Thismessage, sent to the requester if a command reply isdesired, records that an error occurred during theprocessing of a detach SMSG request.

System Action: The detach request is aborted.




DTCNFS1362E Trace write failed; error ReturnCode

Explanation: This message indicates an unsuccessfultrace file transaction for the listed return code reason.The return codes are generated by the functiondump_tv, defined in the file tracev.c.



Source File: REQSMSG C, SIGERROR C

Procedure Name: smtwrite

NFS Messages


DTCNFS1363E Trace data write request failed to filefileid by UserID at address (time).

Explanation: This message indicates an unsuccessfultrace file transaction (SMSG TWRITE command). Thismessage is written to the VMNFS console; anothermessage is returned to the CMS user who issued thecommand.





DTCNFS1364I Trace write successful to file fileid

Explanation: An SMSG request to write the trace filewas successful.



Source File: REQSMSG C, SIGERROR C


DTCNFS1365I Trace data written to file fileid byuserid at nodeid (time).

Explanation: An SMSG request to write the trace datato a file was successful.





DTCNFS1366E Invalid mask value; trace maskremains mask-value

Explanation: An SMSG request to change the tracemask value was not valid.

System Action: VMNFS server processing continuesusing the old trace mask value.

User or Operator Response: Reissue the request,specifying a valid value.


Procedure Name: smmask

DTCNFS1367I Trace mask set to new_mask_value;previous value was old_mask_value

Explanation: An SMSG request was made to changethe trace mask value.

System Action: VMNFS server processing continuesusing the new mask value.




DTCNFS1368I Trace mask set to new_mask_value byorigin; previous value was old_mask_value

Explanation: An SMSG request to set the trace maskvalue was processed.

System Action: VMNFS server processing continuesusing the new mask value.




DTCNFS1369E reqsmsg: discarding too long SMSGfrom origin

Explanation: An SMSG request was received with aninvalid syntax.


User or Operator Response: Correct the request andreissue.


Procedure Name: reqsmsg

DTCNFS1371E Unknown verb in command: command

Explanation: An SMSG request was received for anunknown command.


User or Operator Response: Correct the message andreissue.



DTCNFS1374E *blockio: *BLOCKIO error ReturnCodefrom c_iucv send.

Explanation: An unexpected error was received whileprocessing a *BLOCKIO function. The return code islisted.

System Action: An error status is returned to the NFSclient.

User or Operator Response: Determine the initialfailing case and report it to the IBM Support Center.

Source File: BLOCKIO C

Procedure Name: blockio_driver

NFS Messages


DTCNFS1375E blockio: abnormal responseReturnCode (not ’message complete’)

Explanation: An unexpected return code was receivedwhile processing a *BLOCKIO function. The returncode is listed.

System Action: An error status is sent to the NFSclient.

User or Operator Response: Determine the initialfailing case and report it to the IBM Support Center.



DTCNFS1376I Multiple-block requests are notsupported by *BLOCKIO in this versionof CP; single-block requests will beused.

Explanation: A request by VMNFS to usemultiple-block requests failed.

System Action: VMNFS server processing continuesusing single-block I/O.

User or Operator Response: Determine if the wronglevel of CP is being used.



DTCNFS1377E blockio: *BLOCKIO general errorReturnCode

Explanation: An unexpected return code was receivedfrom a *BLOCKIO request.


User or Operator Response: Determine the initialfailing case, and report it to the IBM Support Center.



DTCNFS1378S CMS level is not correct. Return_codereturned by DMSQEFL.

Explanation: The VMNFS server determined that thecorrect level of CMS was not being used. A level of 14is the minimum supported.


User or Operator Response: Correct the level of CMSused by the VMNFS server.

Source File: INIT C

Procedure Name: init

DTCNFS1381E blockio: block {read|write} errorReturn_Code block number =block_number block address =buffer_address : disk vaddr = vdev disk =userid.address

Explanation: An unexpected return code was receivedwhile processing a *BLOCKIO function. The listedinformation will help indicate where the error occurred.


User or Operator Response: Determine the initialfailing case, and report it to the IBM Support Center.


Procedure Name: wr_bloks, bmbread

DTCNFS1383I reqmount: unknown authorizationflavor flavor from foreign address address

Explanation: An unknown style of authentication wasreceived. VMNFS accepts only AUTH_UNIX,AUTH_DES, or AUTH_SHORT.

System Action: An error response is returned to theNFS client.

User or Operator Response: Determine why anunsupported authentication style was used by theclient.

Source File: REQSTART C

Procedure Name: check_auth

DTCNFS1384I time Umount userid.address usage data:

Explanation: VMNFS received a request to unmountthe specified device.




Procedure Name: reqmount

DTCNFS1385E reqmount: disk userid.address notdetached by umount (too busy).

Explanation: A VMNFS request to unmount aminidisk could not be processed because it could notobtain exclusive access to the minidisk.


User or Operator Response: Reissue the umount.



NFS Messages


DTCNFS1386I Umount: userid.address detached

Explanation: A request to unmount a minidisk wassuccessful.





DTCNFS1387I time Umount-all userid.address usagedata:

Explanation: VMNFS received a request to umount alldisks and directories.





DTCNFS1388I Umount-all: userid.address detached

Explanation: A request to unmount a directory wassuccessful.





DTCNFS1389I Unknown or unsupported NFSprocedure (number procedurenumber)

Explanation: The specified NFS procedure requestfrom the listed IP address was not one of the NFSprocedures that are supported by the VMNFS server.Procedures not supported are:v Get filesystem root (3) [obsolete]v Write to cache (7) [intended for the next version of

NFS protocol]

System Action: The error status is sent to the NFSclient.

User or Operator Response: Determine why anunsupported procedure was requested by the client.Applications that depend on services not available inCMS must use a different NFS server.



DTCNFS1390I NFS client address = address

Explanation: The specified NFS procedure requestfrom the listed IP address was not one of the NFSprocedures that are supported by the VMNFS server.Procedures not supported are:v Get filesystem root (3) [obsolete]v Write to cache (7) [intended for the next version of

NFS protocol]

System Action: The error status is sent to the NFSclient.

User or Operator Response: Determine why anunsupported procedure was requested by the client.Applications that depend on services not available inCMS must use a different NFS server.



DTCNFS1391E Undecodable header in receivedrequest.

Explanation: This error message is issued to the serverin the case of an incorrect NFS call message. If theprogram cannot decode the header, it is ignored, andthis message is issued. This message usually occursbecause of corruption of a NFS client’s datagramduring transmission in the network from client toserver.

System Action: The incorrect datagram is ignored.

User or Operator Response: Check whether the NFSclient system is generating checksums for NFSdatagrams. Many client systems do not generatechecksums to run with less overhead, but can beconfigured, typically by setting a flag in the kernal, togenerate them. Datagrams arriving with invalidchecksums are discarded by TCPIP, therefore theVMNFS server never sees them. NFS clients, when aresponse is not received for a request, attempt recoveryby resending the request. If the retransmitted requestarrives with a correct checksum, it is accepted and isunlikely to produce this message.


Procedure Name: reqstart

DTCNFS1392I Unknown program.

Explanation: The requested program was notMOUNTPROG (100005), NFSPROC (100003), orPCNFSDPROG (150001). These are the only programssupported by the VM NFS server.

System Action: Error status (program not available) issent to the client.

User or Operator Response: Determine why an NFSclient is calling a program not documented in the NFS

NFS Messages


RFC. Perhaps the client can be configured to avoidmaking these calls.


Procedure Name: reqstart

DTCNFS1394I time Bad password or no LOGON BYprivileges for userid userid by byuseridfrom address.

Explanation: An invalid password was given on amount request, or if userid and byuserid are different,byuserid does not have LOGON BY privileges for userid.


User or Operator Response: Correct the password orgive LOGON BY privileges to byuserid.

Source File: NFSLINK C

Procedure Name: checkpw

DTCNFS1400E Return code Return_Code from:command

Explanation: An unexpected return code was receivedwhile processing the listed AUTOLINK command. Thereturn code displayed should help in problemdetermination.


User or Operator Response: Determine the cause ofthe error. If necessary, call the IBM Support Center.


Procedure Name: nfslink

DTCNFS1403E Unexpected return code rc reasoncode rs from call to CMS_function innfsfunction.

Explanation: All anticipated return codes from calls toVM services are interpreted and used to generate anappropriate response to the NFS client. This message iswritten when some other, unanticipated return code isreceived.

System Action: A status of interrupted system call issent to the NFS client.


Source File: LINKDEV C


DTCNFS1404E Unexpected return code ReturnCodefrom: command

Explanation: The listed CP command failed with thelisted return code.

System Action: Another message is sent to the

SIGERROR procedure, which denotes that thiscondition has occured, then the program exits, to berestarted by PROFILE EXEC. If this error isencountered during initialization the VM NFS serverterminates.


Source File: NFSLINK C, INIT C

Procedure Name: nfslink, init

DTCNFS1406E time {SFS|BFS|MDISK|blank} errorfrom CMS_function: return codereturn_code reason code reason_code,function nfs_function called from addresswuerror data:length=lengthnumber=number total_errors=total_errorsfperror data:data warning_codes:warnings

Explanation: An unexpected return code and reasoncode was received while processing a request.


User or Operator Response: Determine the initialfailing case. For BFS errors, information is available inthe z/VM: OpenExtensions Callable Services Reference. ForSFS errors, information is available in the z/VM: CMSMacros and Functions Reference. If necessary, report theerror to the IBM Support Center.

Source File: FINDSFS C, BFSPROC C, INIT C,NFSMAINC C, NFSSFSWU C, NFSSMSG C, NFSXLATC, IO1 C, BFSOFILE C.

Procedure Name: nfs_function

DTCNFS1410E call_VMNFSMON: rc = return_codefrom: globalv_cmd. GLOBALV data willbe ignored.

Explanation: An unexpected error was received fromthe GLOBALV command after calling the VMNFSMONexit routine.

System Action: VMNFS ignores the GLOBALV data.

User or Operator Response: Determine why theGLOBALV failed, and if necessary, contact the IBMSupport Center.


Procedure Name: call_VMNFSMON

DTCNFS1411E call_VMNFSMON: error parsingGLOBALV data from external mountmonitor.

Explanation: An unexpected error occurred parsingthe GLOBALV data after calling the VMNFSMON exitroutine.

NFS Messages



User or Operator Response: Correct the GLOBALVproblem or if necessary, contact the IBM SupportCenter.


Procedure Name: call_VMNFSMON

DTCNFS1416E SIGERROR called: errorstring

Explanation: SIGERROR is called when a condition isrecognized that makes it impossible or unwise for theVMNFS server to continue. Many of these conditionsare never expected to occur, except when there is alogic error in the VMNFS code.

Some of these conditions occur because of activityoutside the control of the NFS server, such asmodification by another CMS virtual machine of aminidisk to which VMNFS has a read-only link. TheSMSG REFRESH command tells the VMNFS server todiscard all information it has from a disk that may beincorrect because of modification by another virtualmachine. Nevertheless, there is no guarantee that theREFRESH commands are received before VMNFSattempts to use the incorrect information.

See the section “SIGERROR Error Strings” on page 145for detailed information on the error string that isreceived with this message.

System Action: After the message string is output, thesum_op procedure is called to output a system statussummary report. The program is then exited byinvoking procedure c_hiucv to clear all IUCV activity,then procedure cendtcpip is invoked to clear allTCP/IP activity, and finally the program exits with areturn code of 1.

User or Operator Response: Follow the instructionsgiven in the documentation for the specific errormessage issued.

Source File: SIGERROR C

Procedure Name: SIGERROR

DTCNFS1420E Function: request for task (address)terminated with pending disk blockwrites.

Explanation: Termination of the task occurred withoutflushing the pending data to the minidisk or directory.Updates will be lost.


User or Operator Response: If the error recurs, reportit to the IBM Support Center.

Source File: TASKEND C, BLOCKIO C

Procedure Name: TASKEND, wr_bloks

DTCNFS1421E RC = Return_Code from command

Explanation: The VMNFS server did not find a 191minidisk defined or an error occurred while trying todetermine if the 191 minidisk was defined.


User or Operator Response: Make a minidisk with anaddress of 191 available to the VMNFS server. If themsg indicates a condition code, try to determine thefailing case and report the problem to the IBM SupportCenter.

Source File: INIT C


DTCNFS1422E Init error: cannot understandresponse to ″CP Query Virtual 191″

Explanation: The expected response was not receivedfrom the command.


User or Operator Response: Try to determine thefailing case and report the problem to the IBM SupportCenter.

Source File: INIT C


DTCNFS1423E VMNFS requires a read-write 191disk.

Explanation: The response from ″CP Query Virtual191″ indicated that the 191 disk was not linked in therequired read-write mode.


User or Operator Response: Make the 191 diskavailable in read-write mode to the VMNFS server.

Source File: INIT C


DTCNFS1424I The Language Environment Cruntime library is not configured todiscern Daylight Savings Time.

Explanation: This message is generated on the consoleof the VM NFS server when the NFS server detects thatDaylight Savings Time information is not available onthe system.


User or Operator Response: Make sure that theLanguage Environment is set up correctly for yoursystem. See the ″Configuring the NFS Server″ chapterin the TCP/IP Planning and Customization book for moreinformation.

Source File: INIT C

NFS Messages



DTCNFS1425I File times reported by VMNFS willbe inaccurate for times when daylightsavings was in effect.

Explanation: This message accompanies messageDTC1424I on the console of the VM NFS server virtualmachine when Daylight Savings Time information isnot available on the system. When this message isdisplayed, the file time(s) reported to NFS clients willbe inaccurate for times when Daylight Savings was ineffect.


User or Operator Response: Make sure that theLanguage Environment is set up correctly for yoursystem. See the ″Configuring the NFS Server″ chapterin the TCP/IP Planning and Customization book for moreinformation.

Source File: INIT C


DTCNFS1426I Disk with label label at virtual addressaddress accessed as mode mode has beenreleased.

Explanation: The VMNFS server requires a range ofminidisk addresses to be reserved for use by VMNFS.If any are found in the range of 0600 to 0A00, VMNFSreleases them.


User or Operator Response: You may want toredefine any minidisks that conflict with this range.

Source File: INIT C


DTCNFS1427E IUCV initialization error code code(0xcode)

Explanation: The listed incorrect code was returnedfrom procedure c_hiucv when a HNDIUCV SEToperation was commanded.

System Action: Another message is sent to theSIGERROR procedure, which denotes that an IUCVfailure has occurred, and the program exits.

User or Operator Response: Determine the cause forthe failure, correct it, and try again.

Source File: INIT C


DTCNFS1428E init: cannot allocate tracev buffer ofnumber (0xnumber) bytes.

Explanation: Storage request failed.

System Action: The program exits with a code of 103and halts.

User or Operator Response: Define a larger virtualstorage for the VMNFS virtual machine.

Source File: INIT C


DTCNFS1429E tracev: invalid argument type type incall from address address

Explanation: Calls to the tracev function copy internaloperational data about the VMNFS server to a circularbuffer. A call has prepared an invalid parameter list forthe tracev function, which probably indicates anoncritical code error in the VMNFS server. Thisinformation is intended for debug purposes, and thetrace operation is not necessary to the normal operationof the VMNFS server.


User or Operator Response: Report the problem tothe IBM Support Center.

Source File: TRACEV C

Procedure Name: tracev

DTCNFS1430I Format is: tvprint fileid.

Explanation: This message is displayed when theTVPRINT module is not invoked with the correctnumber of parameters.

System Action: TVPRINT processing terminates.

User or Operator Response: Correct the parametersand reissue the command.

Source File: TVPRINT C


DTCNFS1431I Example: tvprint tracev.file






NFS Messages


DTCNFS1432I If HEX is specified, hexadecimaldisplay of all trace data follows theformatted display.






DTCNFS1433E Invalid tracev buffer size buff_size(0xhex_buff_size)

Explanation: An incorrect size of the internal tracebuffer was determined.


User or Operator Response: Ensure the correct fileidwas specified on the TVPRINT command.



DTCNFS1434I tracev buffer size is buff_size(hex_buff_size) bytes.

Explanation: This message displays the size of theinternal trace buffer. A request will be made to obtainvirtual storage of this size.

System Action: TVPRINT processing continues.




DTCNFS1435E Cannot allocate tracev buffer ofbuff_size (0xhex_buff_size) bytes.

Explanation: A request to obtain virtual storage in thelisted size was unsuccessful.


User or Operator Response: Define a larger virtualmachine for use in formatting the trace file.



DTCNFS1436E fseek error on input file.

Explanation: An unexpected return code was receivedwhile processing the trace file.


User or Operator Response: Determine if the correctinput file was used.



DTCNFS1437E Error reading tracev buffer frominput file

Explanation: An unexpected return code was receivedwhile processing the tracev buffer.





DTCNFS1438E Failure reading tracev buffer

Explanation: An unexpected return code was receivedwhile reading the input file.





DTCNFS1439E Cannot allocate storage map.

Explanation: A request to obtain storage by theTVPRINT module failed.


User or Operator Response: Define a larger virtualmachine to process the trace file or determine if thecorrect input file was used.



DTCNFS1440E Failure reading storage map

Explanation: An unexpected error was receivedreading the storage map while processing the TVPRINTcommand.





NFS Messages


DTCNFS1441E Format error in simple storage map.

Explanation: The storage map being processed wasnot in the correct format.





DTCNFS1442I low-level trace buffer size isnum_bytes (hex_num_bytes)

Explanation: This message indicates the size of thelow-level trace buffer that will be displayed.





DTCNFS1443E Unable to allocate low-level tracebuffer of num_bytes (0xhex_num_bytes)bytes.

Explanation: A request to obtain storage for thelow-level trace buffer could not be satisfied.





DTCNFS1444E Cannot open tracev callid file fileid

Explanation: An unexpected error was received tryingto open the specified file.


User or Operator Response: Determine if the file isavailable.



DTCNFS1445E Format error reading tracev callid filefileid at line line_num : datum

Explanation: While processing the callid file, anunexpected error occurred.


User or Operator Response: Determine if the correctcallid file was used.



DTCNFS1446I Time stamp of first tracev element is:time

Explanation: This message indicates the timeassociated with the trace element.





DTCNFS1447E Invalid format for tracev element atrelative address address, previouselement at relative address prev_address

Explanation: An invalid trace record was found.


User or Operator Response: Determine if the correcttrace file was used.



DTCNFS1448E Invalid callid value value(0xhex_value).

Explanation: An unexpected value was found whileprocessing the trace file.


User or Operator Response: Determine if the correcttrace file was used.



DTCNFS1450E Unrecognized tracev callid value value(0xhex_value)

Explanation: An unexpected value was found whileprocessing the trace file.

System Action: Processing of the element is ignored.




DTCNFS1464I Directory is not locked.

Explanation: This message indicates the minidiskdirectory was not locked.



NFS Messages




DTCNFS1472I time Rename of Name Translation fileon disk userid.address is not possiblebecause temporary file##NFS##.#RNAMES# exists.

Explanation: The file name that was entered cannot beused because the file name already exists.

System Action: Error status NFSERR_NOTEMPTY issent to the NFS client.

User or Operator Response: Advise the disk owner. ACMS ERASE command can delete the ##NFS###RNAMES# file.

Source File: NFSRENAM C

Procedure Name: nsfrename

DTCNFS1473E File erase failure: disk userid.addressfile filename filetype

Explanation: This message signals a file erase failure.This should not occur in ordinary circumstances. Anerror probably exists in the file system structure on theCMS disk. Possible causes include:v Failure in the VMNFS codev Damage because of concurrent write links to a

minidisk from more than one CMS virtual machinev Disk write errors because I/O operations were not

correctly completed (because of power or hardwarefailures).

System Action: I/O error status is returned to theNFS client.

User or Operator Response: A CMS FORMATcommand creates a new file system structure on aminidisk. Because FORMAT eradicates all existing fileson a minidisk, verify that backup data for the disk isavailable, or copy all files that can be read from theaffected disk to a safe place, before starting a formatoperation. It is likely that CMS reports a fatal filesystem error when trying to copy at least one file onthe disk. When this happens, restart CMS and try thenext file.


Procedure Name: nfserase

DTCNFS1477S FINDBLOK: wait for Buffer Blockfailed block=block_numberdevice=userid.address vaddr=vaddr

Explanation: A task waiting for a disk read operationstarted by another task recognized that the readoperation failed. The I/O error is reported by the taskthat initiated the operation. This message records thefact that a second task was affected by the same failure.

System Action: The NFS client’s request isabandoned.

User or Operator Response: None. The taskprocessing it is aborted.

Source File: FINDBLOK C

Procedure Name: findblok

DTCNFS1482E returning cc=cc rc=ReturnCode fromdiag 0x4C

Explanation: An incorrect return code was receivedfrom a Diagnose code X'4C'. The VMNFS virtualmachine probably does not have the privilege neededto use this Diagnose code.

System Action: The program continues with a returnof FALSE.

User or Operator Response: Correct the CP directoryentry for VMNFS. If VMNFS cannot use DiagnoseX'4C', the invalid password count is reached, and allsubsequent LINK requests can be failed by CP.

Source File: NFSUTIL C

Procedure Name: senddata

DTCNFS1486E Record length exceeds CMS Vmaximum: file offset xoffset

Explanation: The program fails the test for an attemptto create a record longer than the maximum length thatCMS allows, which is 64K bytes. This message isfollowed by an operation summary.

System Action: NFSERR_IO is returned to the NFSclient.


Source File: NFSWRIT1 C

Procedure Name: write_V

DTCNFS1492I Maxlen value inappropriate; 256 willbe used.

Explanation: The maxlen value specified as anargument on the PRINTLOG command is not valid. Itis either 0 or too large.

System Action: VMNFS PRINTLOG processingcontinues using a value of 256.


Source File: PRINTLOG C


NFS Messages


DTCNFS1493E Cannot open output file fileid

Explanation: The PRINTLOG command encounteredan error opening the listed output file.

System Action: PRINTLOG processing terminates.

User or Operator Response: Try to determine theerror with the file and reissue the PRINTLOGcommand.



DTCNFS1495E Error code Error_code from creadbin atrecord number nnnnn

Explanation: In processing the trace log file, thePRINTLOG encountered an error. The listed error codeshould help in problem determination.


User or Operator Response: Try to determine theproblem and reissue the PRINTLOG command.



DTCNFS1497E Incorrect argument.

Explanation: A problem was found while formattingthe VMNFS trace file.


User or Operator Response: Determine if the correcttrace log file was used as input to the PRINTLOGcommand. If necessary, report the problem to the IBMSupport Center.



DTCNFS1499I Current operation summary at time

Explanation: This informational header message liststhe timestamp for the current operational summaryreport to follow.

System Action: Control is always returned to thecaller for further processing after the SUM_OP report iswritten to stderr.

User or Operator Response: The SUM_OP procedurecreates a current operation summary report for the NFSprogram. This report is often the result of an errorcondition in NFS. Use the report to help with problemresolution where possible.

Source File: SUM_OP C

Procedure Name: sum_op

DTCNFS1500I Task block address is zero: there is nocurrent operation.

Explanation: The VMNFS server is stopped by a #CPEXT command entered from its console.





DTCNFS1501I Task block address: TaskBlockAddress

Explanation: This message lists the task block addressfor the current operational summary report.





DTCNFS1502I Client IP address: address(nnn.nnn.nnn.nnn)

Explanation: This informational message lists theClient IP address in hexadecimal and dotted decimalnotation for the current operational summary report.





DTCNFS1503I Queued write request at offset xoffset,length xlength

Explanation: This message lists the queued writerequest data for the current task in an operationalsummary report.


User or Operator Response: The SUM_OP procedurecreates a current operation summary report for the NFSprogram. This report is often the result of an error

NFS Messages


condition in NFS. Use the report to help with problemresolution where possible.



DTCNFS1504I RPC program program version versionprocedure procedure

Explanation: This informational message lists RPCprogram data for the current operational summaryreport.





DTCNFS1505I File filename filetype on diskuserid.address (vaddr vaddr )

Explanation: This message lists the file name, type,and user ID for the current operational summaryreport. This message is written for each file in use bythe current task.





DTCNFS1508I Return code ReturnCode reason codeReasonCode from DMSLINK for"CP_link_command_string"

Explanation: This message is written by the defaultexit routine named nfsbadpw supplied with theVMNFS server. The nfsbadpw routine can be replacedby the local installation to perform another sort oflogging of LINK requests.

DMSLINK is a CSL routine that performs the functionof a CP LINK command. CP_link_command_string isequivalent to the values passed to DMSLINK.

DTCNFS1509I Mount command from addressddd.ddd.ddd.ddd

Explanation: This message is written by the defaultexit routine named nfsbadpw supplied with theVMNFS server. COMMAND is the CP LINK commandthat was attempted during processing of a client’smount request. The nfsbadpw routine can be replacedby the local installation to perform another sort oflogging of failed LINK requests.

System Action: The program continues. Depending onthe error, status such as access denied or read-only filesystem might be returned to the NFS client.


Source File: NFSBADPW C

Procedure Name: nfsbadpw

DTCNFS1511E module name: socket function() call online line number failed, reason is: reason

Explanation: A call to module name: socket function hasfailed. The reason for the failure will be included in themessage.


User or Operator Response: Try to determine theinitial failing case, and report it to the IBM supportCenter.

If the message displayed lists the module name asNFSMAINC and socket function as bind, with the reasonbeing: Address already in use (EADDRINUSE), youmay have been running a prior release version of theVM NFS server and re-ipled CMS in the virtualmachine, and then started the current release of the VMNFS server. If this was the case, the prior releaseversion of the VM NFS server may not correctly cleanup its use of resources.

Source File: NFSMAINC C, NFSUTIL C, SIGERROR C


DTCNFS1512W TCPCSLIB CSLLIB not available;SFS operations are disabled.

Explanation: The required CSLLIB was not found.Requests for SFS & BFS objects will not be processed.

System Action: Processing continues for minidiskrequests only.

User or Operator Response: Determine why theTCPCSLIB CSLLIB could not be found.



NFS Messages


DTCNFS1513I time NFSPROC_NULL call receivedfrom address, XID 0xID

Explanation: An NFSPROC_NULL request wasreceived by the VMNFS server.

System Action: A null reply is sent to the NFS client.



Procedure Name: reqnfs

DTCNFS1514E Format is: replytag verb ...

Explanation: An SMSG request with an invalid syntaxwas received by the VMNFS server.


User or Operator Response: Correct the SMSG requestand reissue.



DTCNFS1515I TRACENUL flag is now trace_value

Explanation: An SMSG request to set the TRACENULflag was processed.





DTCNFS1516I time Syntax error in Refresh commandfrom origin: SMSG string

Explanation: VMNFS received an SMSG Refreshcommand with invalid syntax.


User or Operator Response: Correct the syntax andreissue the command.



DTCNFS1519W File filename not found; initializationcontinuing

Explanation: The identified file, used by VMNFSserver initialization, was not found.

System Action:

v VMNFS initialization continues. For VMNFSCONFIG, MOUNTs specifying lines=ext or trans=extwill not work as described in the "NFS File ExtensionDefaults" section of the TCP/IP User’s Guide. Instead,

all file names will default to lines=CMS andtrans=no, which is equivalent to the record=binarydefault.

v If filename is VMNFS HISTORY or VMNFSTRANSLAT, the VMNFS HISTORY and VMNFSTRANSLAT files are recreated. This causes all currentmounts to be invalidated. Clients who havepreviously mounted a file system will receive anerror indicating that the file handle is STALE. Thefile system must be remounted.


Source File: INIT C

Procedure Name: init_config

DTCNFS1520E The file pool server is not at theproper release level

Explanation: An attempt was made to MOUNT a BFSdirectory residing in a file pool server running at arelease level earlier than VM/ESA Version 2 Release3.0.

System Action: Error status NFSERR_IO is sent to theNFS client.

User or Operator Response: Contact system supportto upgrade the file pool server to at least VM/ESAVersion 2 Release 3.0.

Source File: BFSPROCS C

Procedure Name: Mount_BFS

DTCNFS1521I item on line lineno of file VMNFSCONFIG is error

Explanation: An error was encountered whileprocessing the file VMNFS CONFIG. The item describesthe option or record that is in error. The error describesboth the cause of the problem and the action taken -either to ignore the entire record or to ignore the optionthat is in error.

System Action: The record or option is ignored.

User or Operator Response: Correct the record inVMNFS CONFIG that has the error.

Source File: INIT C


DTCNFS1523I File filename TCPXLBIN used fordefault translation table

Explanation: The translation table in the identified filewill be used for ASCII/EBCDIC translation when noXLATE value is specified on client mount requests.

System Action: VMNFS server initialization continues.


Source File: NFSXLAT C

NFS Messages


Procedure Name: init_xlat

DTCNFS1524W Error reading file filename filetype fm;initialization continues

Explanation: The identified file, used by VMNFSserver initialization, was not found on any of theaccessed disks, or an error occurred while reading thefile.

System Action: VMNFS server initialization continues.If filetype is TCPXLBIN, any NFS clients who havepreviously mounted file systems usingXLATE=filename will receive an error indicating thatthe file handle is STALE. The file system must beremounted.




DTCNFS1525E No space remaining in VMNFSTRANSLAT file. Unable to addtablename

Explanation: An NFS client attempted to mount a filesystem using XLATE=, specifying a translation tablethat is not active. There is no room to add the newactive translation table.

System Action: Error status NFSERR_IO is sent to theNFS client.

User or Operator Response: The TCP/IPadministrator can 'refresh' the translation tablemapping by stopping the VMNFS server machine,erasing the VMNFS TRANSLAT file on the server’s191 disk, and restarting the server. Note that this alsoresults in a refresh of the VMNFS HISTORY file. Thisinvalidates all file handles. Clients who have previouslymounted a file system will receive an error indicating thatthe file handle is STALE. The file system must be remounted.


Procedure Name: name_xlat_locate

DTCNFS1526W VMNFS HISTORY and VMNFSTRANSLAT do not match

Explanation: The two files, which are used by VMNFSserver initialization, exist but the timestamps indicatethat they are not in synchronization.

System Action: The files are erased and recreated, andVMNFS server initialization continues. Any NFS clientswho have previously mounted a file system will receivean error indicating that the file handle is STALE. Thefile system must be remounted.


Source File: INIT C


DTCNFS1527E Error reading file filename, serverterminated.

Explanation: The VM NFS server requires file filenamefor its operation. An attempt to read this file failed

System Action: VMNFS Server processing terminates.

User or Operator Response: Determine why thenamed file cannot be read.

Source File: INIT C


DTCNFS1528I Accept of socket m greater thanFD_SETSIZE n

Explanation: An accept of a TCP socket connectionreturned a socket descriptor with a value greater thanFD_SETSIZE which cannot be used by the VM NFSserver.

System Action: The VM NFS server rejects theconnection attempt. To prevent having to reject futureTCP connections, the VMNFS server will set up to closeall existing TCP socket connections with NFS clientsthat have been inactive for more than 5 minutes.



Procedure Name: Handle_New_TCP_Client

DTCNFS1536W Error calling set groups function.BPX1VM5 return code rc and reasoncode rs

Explanation: Initialization encountered a problemcalling the function, which sets the group list (GID list)for a user ID identified on MOUNTs. When there is aproblem with this function, only the VM user’s primaryGID (from the POSIXINFO statement) will be used onrequests for BFS files and directories. The user’ssupplementary GID list (from the POSIXGLISTstatement) will not be used.

System Action: Initialization continues.

User or Operator Response: Examine return andreason codes in the message to determine the reasonfor the failure.

Source File: INIT C


DTCNFS1543E Cannot allocate virtual storage

Explanation: The VMNFS server was not able toprocess a request, because an error was returned on anattempt to allocate virtual storage.


NFS Messages




Procedure Name: add_cmi

DTCNFS1544E Authorization denied byVMNFSSMG.EXEC

Explanation: The system administrator activated anexit for the VMNFS server, called VMNFSSMG EXEC,which denied your SMSG request.


User or Operator Response: Contact your systemadministrator to see why the request was denied.

Source File: NFSSMSG C

Procedure Name: SMAUTH

DTCNFS1546E Unable to accept new TCPconnections from NFS clients

Explanation: When attempting to accept a TCPconnection for an NFS client, the VM NFS serverreceived an error indicating the TCP connection limithas been reached.

System Action: The limit for the number of NFSclients using the TCP transport protocol has beenreached. The VM NFS server will not accept new NFSclient connections over the TCP transport protocol untilexisting NFS clients close their connections with theVM NFS server.

User or Operator Response: When this conditionoccurs, NFS clients using the TCP transport protocolwill be unable to connect to the VM NFS server untilexisting connections are closed.

The VM NFS server is configured to handle a specificnumber of TCP transport protocol connections withNFS clients. The VM NFS system administrator canincrease this number by specifying a larger value forthe MAXTCPUSERS configuration record in theVMNFS CONFIG file. See the TCP/IP Planning andCustomization book for the description of theMAXTCPUSERS configuration record and VMNFSCONFIG file.



DTCNFS1547E Size of buffer defined for UDP is toosmall

Explanation: The lrg_env_size parameter on theLARGEENVELOPEPOOLSIZE configuration statementhas a value less than 8192. It must be 8192 or larger forthe VM NFS server to operate correctly.


User or Operator Response: The VM NFS

administrator must change the lrg_env_size parameterto have a value of 8192 or larger.



DTCNFS1553I MAXTCPUSERS value adjusted fromn1 to n2

Explanation: The VM NFS server could not use n1 asthe maximum number of concurrent NFS clients usingthe TCP transport protocol. Instead it will use n2.

System Action: The VM NFS server has set n2 as themaximum number of concurrent NFS clients using theTCP transport protocol.

User or Operator Response: In order for the VM NFSserver to use the MAXTCPUSERS value of n1, theSKCBPOOLSIZE configuration parameter for theTCP/IP stack must be configured to be n1 or greater.See "Configuring the TCP/IP Virtual Machine", inTCP/IP Planning and Customization.


Procedure Name: Init_Socket

DTCNFS1554E Unable to allocate storage for<read|write> fd set

Explanation: Initialization of the VM NFS server wasunable to obtain storage for the specified read or writefd set.

System Action: VM NFS server processing terminates

User or Operator Response: Make sure the VM NFSserver is defined to be the recommended virtualmachine size or larger. If it is not, increase the size ofthe virtual machine to the recommended virtualmachine size as defined in the TCP/IP Planning andCustomization.



DTCNFS1555E Unable to initialize external securitymanager environment. Return codeReturnCode, reason code ReasonCode.

Explanation: An attempt was made to initialize theexternal security manager because :ESM_Enable.Yeswas specified in the DTCPARMS file or the 'R' start upparameter was specified. The call to CSL routineDMSESM failed with the return and reason codesshown.

System Action: Initialization terminates.

User or Operator Response: Consult the z/VM: CMSCallable Services Reference for information on the on theexternal security manager codes returned by theDMSESM CREATE_TOKEN CSL routine.

NFS Messages




DTCNFS1556E Log data: Log_data

Explanation: An earlier message indicated there was aproblem with a call to a CMS function, and that CMSfunction returned detailed log_data describing the error.




Procedure Name: checkpw

DTCNFS1557E No EXPORT list defined whenEXPORTONLY YES was specified

Explanation: The list of export entries from theVMNFS CONFIG file is empty and the EXPORTONLYYES option has been specified.

System Action: If this occurs during the firstinitialization of the VMNFS CONFIG file, the serverwill be stopped. If it occurs during a smsg refresh, thismessage will be output, but the server will stay up.

User or Operator Response: When this conditionoccurs, NFS clients will not be able to mount anything.In order to make the server useful again, the VMNFSCONFIG file must be refreshed with new EXPORTentries or EXPORTONLY NO. Also, anything mountedprevious to a refresh of the server will remain mountedafter the refresh.

Source File: INIT C


DTCNFS1559E VM NFS server is missing class Bprivileges or diagnose 88 authorization

Explanation: The VM NFS server virtual machinerequires class B privileges and Diagnose 88authorization for password checking and minidisklinks.

System Action: The VM NFS server terminates.

User or Operator Response: Ensure that the VM NFSserver virtual machine’s user directory entry includesClass B privileges and an OPTION DIAG88 statement.

Source File: INIT C


DTCNFS1560E Incorrect level of CP; requiredfunction not available

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

System Action: The VM NFS server terminates.

User or Operator Response: Upgrade to theappropriate level of /vm;.

Source File: INIT C


DTCNFS1561E Unable to set desiredMAXTCPUSERS value.

Explanation: An error occurred trying to set theMAXTCPUSERS value.


User or Operator Response: Verify that the VM NFSserver is built with the correct COMMTXT TXTLIB. Ifcorrect, report the problem to the IBM Support Center.


Procedure Name: Init_Socket

DTCNFS1562E Unrecoverable NFS Client error,reason code 0xnnnn parm 0xnnnn

Explanation: The VM NFS client encountered an errorand could not continue.

System Action: The virtual machine is put into a waitstate. Optionally, a dump of the virtual machine maybe taken depending on the CMS AUTODUMP settingfor the virtual machine (use the Q AUTODUMPcommand for CMS to determine the setting).

User or Operator Response: Note the message withthe reason code and parm field. The user must re-IPLCMS in the virtual machine. Try to determine the initialfailing case, and report it to the IBM SupportCenter.This message may be received while using theNFS client and after a recoverable CMS abend (forexample, HX) in your virtual machine.

Source File: DTCCAVM.ASSEMBLE

Procedure Name: VMABEND

SIGERROR Error StringsFollowing are the SIGERROR error strings associated with message DTCNFS1416E.

SIGERROR is called when a condition is recognized that makes it impossible orunwise for the VMNFS server to continue. Many of these conditions are neverexpected to occur, except when there is a logic error in the VMNFS code.

NFS Messages


Some of these conditions occur because of activity outside the control of the NFSserver, such as modification by another CMS virtual machine of a minidisk towhich VMNFS has a read-only link. The SMSG REFRESH command tells theVMNFS server to discard all information it has from a disk that may be incorrectbecause of modification by another virtual machine. Nevertheless, there is noguarantee that the REFRESH commands are received before VMNFS attempts touse the incorrect information.

Can not register NFS with PORTMAPPER

Severity: Error.

Explanation: Failed to register NFS and MOUNTprograms with port mapper. The only common reasonfor this is that the PORTMAP virtual machine is notrunning.


User or Operator Response: Evaluate possible reasonsfor this failure. Use the RPCINFO command to test forcomplete failure of PORTMAP.



Can’t open debug file

Severity: Error.

Explanation: The DEBUG, and/or the GENLOGruntime options are selected. The VMNFS LOG fileopen failed.


User or Operator Response: Correct any minidiskaccess problems (for example, read-only disk) beforecontinuing.



clcvm.c - Fatal header serialization error.

Severity: Fatal.

Explanation: The xdr_callhdr procedure failed whilean RPC client handle was created for a call to Portmapto register the NFS or MOUNT programs.


User or Operator Response: Examine the header inquestion, determine a reason for the failure, and correctthe problem before continuing.

Source File: NFSCVM C

Procedure Name: clcvm_create

delbb_r: buffer not in use by current task.

Severity: Error.

Explanation: This message is issued by procedure

delbb_r when an attempt to delete the reference by thecurrent task to a disk block buffer fails, because thisbuffer is not on the list of buffers referenced by thistask. This is probably because of an error in theVMNFS program logic.


User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.

Source File: GETBB C

Procedure Name: delbb_r

DELFB: File Block not connected to Device Block.

Severity: Error.

Explanation: During an attempt to remove a FileBlock from the chain anchored in the Device Block, theFile Block was not located. File Blocks are deletedduring erase and rename client requests, and during arefresh operation.


User or Operator Response: Suspect system problems.Try to determine the initial failing case, and report it tothe IBM Support Center.


Procedure Name: DELFB

DELFB: File Block use count is positive, but no taskis using it.

Severity: Error.

Explanation: Internal error in the VMNFS program.





DELFB: use count negative.

Severity: Error.

Explanation: The expected File Block use count waszero and a negative value was found.

NFS Messages






Directory unlock error.

Severity: Error.

Explanation: A call to release a lock on a minidiskwas made by a task that does not hold this lock. This isa logic error in the VMNFS program.



Source File: NFSCREAT C

Procedure Name: unlock_directory

Fatal directory error in make_tf.

Severity: Fatal.

Explanation: The system failed to get a pointer to thedirectory FST by GETBLOK to create a NameTranslation File because of a logic error in VMNFS, or adamaged minidisk file system.


User or Operator Response: Try reformatting the CMSminidisk. If problems recur, contact the IBM SupportCenter.

Source File: FNTRANS C

Procedure Name: make_tf

Fatal directory error in nfscreate.

Severity: Fatal.

Explanation: The system failed to get a pointer to thedirectory FST by GETBLOK when processing a client’screate-file request because of a logic error in VMNFS,or a damaged minidisk file system.


User or Operator Response: Try reformatting the CMSminidisk. If problems recur, contact the IBM SupportCenter.


Procedure Name: create_file

fh_check: cannot reconnect.

Severity: Error.

Explanation: A disk had to be relinked in write mode,but the attempt to create a new path to *BLOCKIO forthat disk failed.





fh_check: IUCV sever failure.

Severity: Error.

Explanation: Unexpected return code; probable errorin VMNFS program logic.





GETBB: no available blocks

Severity: Error.

Explanation: All disk block buffers are in use. Thesebuffers are managed by VMNFS in aLeast-Recently-Used scheme. This message probablyindicates a logic error in the code that manages thepool of buffers.




Procedure Name: GETBB

GETBLOCK: error from FINDBLOK

Severity: Error.

Explanation: A disk block has been read, but the blockbuffer holding it cannot be located. Error in VMNFSprogram logic.




Procedure Name: GETBLOCK

NFS Messages


GETBLOCK: error from RWBLOCKS

Severity: Error.

Explanation: Error reading a block from disk. This isthe most common symptom that results when theVMNFS server attempts to read information from adisk that has been changed by another CMS virtualmachine. It results from the attempt to extract diskblock numbers from a pointer block that has beenreassigned and now contains file data that are not validblock numbers.

System Action: VMNFS is restarted by PROFILEEXEC. This forces all disk information needed toservice subsequent client requests to be read again, andshould clear the problem until a similar situationoccurs.



Procedure Name: GETBLOCK

GETFBLOK: bad file block number argument.

Severity: Error.

Explanation: An attempt was made to read a block ofdata from a file that exceeds the number of blocks inthe file. If this occurs sporadically, it is probablybecause of changes made to disks by other virtualmachines about which the VMNFS server is unaware. Ifit occurs in other circumstances, suspect damage to thefile system on the disk involved.


User or Operator Response: If the minidisk filesystem is damaged, reformat the disk. If the problempersists, try to determine the initial failing case, andreport it to the IBM Support Center.

Source File: FINDFILE C

Procedure Name: GETFBLOK

getrem: invalid offset

Severity: Error.

Explanation: VMNFS program logic error.



Source File: GETREM C

Procedure Name: getrem

History File block allocation error.

Severity: Error.

Explanation: In the case of a sparse block in the file,when an attempt is made to allocate a real block, theprocedure fails and this error message is issued.


User or Operator Response: Check for a full 191 diskused by VMNFS.

Source File: FHãHIST C

Procedure Name: findfhr

init: error making device block for history file

Severity: Error.

Explanation: The VMNFS server’s 191 device is not anormal CMS minidisk.



Source File: INIT C


init: IDENTIFY error

Severity: Error.

Explanation: A CMS IDENTIFY command failed(nonzero return code).



Source File: INIT C


init: IUCV initialization error.

Severity: Error.

Explanation: The procedure c_hiucv sends anincorrect return code, which indicates that IUCVinitialization failed.



Source File: INIT C


init: translation table error

Severity: Error.

Explanation: An attempt to load the special translatetable file VMNFS TCPXLBIN, or the standard translatetable file STANDARD TCPXLBIN, found that the

NFS Messages


second or third records in the file did not contain 256bytes.


User or Operator Response: Correct the translationfile before you try again.

Source File: INIT C


Invalid diskaddr arg to findfhr.

Severity: Error.




Source File: FHãHIST C

Procedure Name: findfhr

LINKDEV: failure in NFSTISET

Severity: Error.




Source File: LINKDEV C

Procedure Name: MAKE_DB

make_tf: lost file

Severity: Error.

Explanation: An error occurred while trying to createa Name Translation file on a minidisk. This is probablybecause of a VMNFS program logic error.





make_tf: translation file already exists

Severity: Error.


System Action: Try to determine the initial failingcase, and report it to the IBM Support Center.




nfscreate: just-created file cannot be found

Severity: Error.





Procedure Name: mkdopres

nfslink: detach command failed

Severity: Error.

Explanation: A CP DETATCH command failed. Thefailing command and its return code is displayed justbefore this error signal.



Source File: NFSLINK


nfsrename: missing FST

Severity: Error.

Explanation: Cannot locate the FST for a directory.VMNFS program logic error.




Procedure Name: nfsrename

No storage for TCP client list element

Severity: Error

Explanation: Error getting storage when acceptingnew TCP client connection.

System Action: VMNFS is restarted automaticallywhich should clear the storage problem.




NFS Messages


No Task Block for TCP is availableNo Task Block for UDP is availableNo Task Block is available

Severity: Error.

Explanation: No task blocks are available. Anotherclient request was received when all tasks were busyprocessing previous requests. The number of tasks iscurrently 64.


User or Operator Response: Try to determine whetherunusual conditions in VM can be responsible (forexample, disks that are not responding promptly toI/O requests, perhaps because they have failed, or arereserved by another system that shares them). If suchan explanation cannot be found, report the trouble tothe IBM Support Center.



QUEUEB: no Device Block.

Severity: Error.





Procedure Name: QUEUEB

RDLABEL: invalid disk block size.

Severity: Error.

Explanation: The process that reads the label from adisk fails when it finds an unacceptable block size inthe label. Possibly a corrupted disk label, or not a CMSminidisk.


User or Operator Response: Try to determine the diskinvolved. If CMS can access the disk without problems,report the problem to the IBM Support Center.


Procedure Name: RDLABEL

rdlabel: IUCV sequence error.

Severity: Error.

Explanation: Unexpected status from an IUCVoperation to *BLOCKIO.




Procedure Name: open_path

refresh: Buffer Block use count not zero.

Severity: Error.

Explanation: Program logic expected the Buffer usecount to be zero at this point in the procedure and thecount was not zero.


User or Operator Response: If this condition recurs,try to determine the initial failing case, and report it tothe IBM Support Center.


Procedure Name: refresh

RELBBs: Buffer Block use count is negative.

Severity: Error.

Explanation: Processing includes reducing the usecount of all Buffer Blocks referenced by the endingtask. The use count should not be negative after it isdecremented. VMNFS program logic error.



Source File: GETBB

Procedure Name: RELBBs

rename: lost temporary file.

Severity: Error.

Explanation: An error occurred during the process ofrenaming the Name Translation file. A NameTranslation file has the CMS file ID ##NFS###NAMES#. You cannot rename if there are entries inthe Name Translation file. If the file is empty, you candelete and rename requests. If the new name for thefile is one that requires translation, you must create anew Name Translation file. The original NameTranslation file is renamed to a temporary name first,while you create the new Name Translation file. Thetemporarily named file could not be located when itwas time to change its name to correspond with theCMS file name in the new Name Translation file.



NFS Messages



Procedure Name: nfsrename

reqmount: error from SVC_REPLY.

Severity: Error.

Explanation: An error in SVC_REPLY occured whentrying to send a reply message to an NFS client whomade a mount request. VMNFS program logic error.




Procedure Name: reply_proc

reqstart: no MountInfo structure available.

Severity: Error.

Explanation: An attempt to obtain an unusedMountInfo control block failed. The number of thesecontrol blocks is defined by the compile-time constantMAX_MNT_INFO in the file nfs.h. MountInfo blocksare created in response to client mountpw requests, andare automatically purged after five minutes, or soonerif a matching mount request is received from the sameclient. Normally, only a few mountpw requests areoutstanding at any moment. This error may be becauseof unusual operation of an NFS client.

System Action: When the VMNFS server is restartedby the normal operation of PROFILE EXEC whenSIGERROR calls exit(), all pending MountInfo data(from mountpw requests) is forgotten. Clients mustrepeat their mountpw and related mount requests.

User or Operator Response: If an unusual clientcondition cannot be discerned as the cause of thisproblem, report the problem to the IBM SupportCenter. The log file created when VMNFS is invokedwith the G option records all VMNFS server clientrequests received, and the replies sent to those requests,which can be useful for identifying clients requests.


Procedure Name: reply_proc

rtnname: Error reading VMNFS TRANSLAT.

Severity: Error.

Explanation: The VMNFS server was unable to readthe VMNFS TRANSLAT file.




Procedure Name: name_xlat_locate

rtnname: Error using translation table.

Severity: Error.

Explanation: An error was received on a call toperform ASCII/EBCDIC translation; the defaulttranslation table could not be found.



Source File: NFSSYMLK C, NFSXDRI C, PCAUTH C,REQSTART C.

Procedure Name: Multiple routines.

rtnname: translation table error.

Severity: Error.

Explanation: There was an error in attempting toinitialize the default translation table for the VMNFSserver.

System Action: VMNFS server initialization isterminated.

User or Operator Response: Make sure that theVMNFS TCPXLBIN or STANDARD TCPXLBIN file isin the correct format, and available on a disk accessedin the VMNFS server machine’s search order.



rtnname: VMNFS HISTORY/TRANSLAT file error.

Severity: Error.

Explanation: An attempt to verify and initialize theVMNFS HISTORY and VMNFS TRANSLAT file hasfailed.


User or Operator Response: Examine the serverconsole for additional error messages.

Source File: INIT C

Procedure Name: recreate_history_files, init_history.

RWBLOCKS: not read nor write.

Severity: Error.



User or Operator Response: Try to determine the

NFS Messages


initial failing case, and report it to the IBM SupportCenter.

Source File: IO1 C

Procedure Name: RWBLOCKS

RWBLOCKS: write operation Buffer Block not found.

Severity: Error.

Explanation: The disk block write routine cannot finda buffer block containing the data to write. VMNFSprogram logic error.



Source File: IO1 C

Procedure Name: RWBLOCKS

Selectex failed

Severity: Error.

Explanation: This msg follows msg DTCNFS1511E.See the information in that msg for the reason for thefailure.





smdetach: lost Device Block.

Severity: Error.






taskend: deferred task not waiting.

Severity: Error.

Explanation: Part of task termination processing is tomark dispatchable any tasks that are waiting for theending task to complete. A task is recorded as waitingfor the ending task to complete, but the waiting task isnot in the list of waiting tasks. VMNFS program logicerror.



Source File: TASKEND C

Procedure Name: TASKEND

TASKEND: File Block use count is negative.

Severity: Error.

Explanation: Part of task termination processing is toreduce the use count of all File Blocks referenced by theending task. The use count field of a File Block shouldnot be negative. VMNFS program logic error.



Source File: TASKEND C

Procedure Name: TASKEND

tf_client: name too long.

Severity: Error.





Procedure Name: tr_client

ThreadYield counter corrupted- {A | B}

Severity: Error.

Explanation: An internal error has occurred in the VMNFS program.



Source File: NFSMAINC.C

Procedure Name: MAIN

tr_add: name too long.

Severity: Error.



NFS Messages




Procedure Name: tr_add

tr_CMS: name too long.

Severity: Error.





Procedure Name: tr_CMS

tr_get_record failed.

Severity: Error.

Explanation: A Name Translation file (CMS fileid##NFS## #NAMES#) is corrupted. This can be a usererror because the file is written on a CMS user’sminidisk and nothing prevents a user from modifyingit.


User or Operator Response: The summary operationreport that follows should help identify the disk that isinvolved. If the Name Translation file is deleted fromthe disk, this error does not occur, but the translationsare lost. Possibly a backup copy of the NameTranslation file can be restored to the minidisk. If not,after the faulty Name Translation file is deleted (by aCMS ERASE command), the NFS client has to examinethe files on the CMS disk with the objective ofrenaming them to the desired client names.


Procedure Name: tr_get_record

tracev: string too long.

Severity: Error.

Explanation: This message is issued by TRACEV Cwhen an attempt is made to process a character stringexceeding 255 characters. VMNFS program logic error.



Source File: TRACEV C

Procedure Name: tracev

write_V: offset computation yields invalid block.

Severity: Error.

Explanation: Either an error in VMNFS serverprogram logic, or a CMS minidisk file system can becorrupted.



Source File: NFSWRIT1 C

Procedure Name: write_V

NFS Messages


NFS Messages


Chapter 9. PING Messages

This chapter contains the PING messages used to monitor the network. For moreinformation, see the TCP/IP User’s Guide or TCP/IP Planning and Customization.

BeginTcpIp failed: ReturnCode

Severity: Warning.

Explanation: TCP/IP could not begin processing.

System Action: The PING program halts and exits.

User or Operator Response: Inform the systemprogrammer the type of error you encountered.

System Programmer Response: Modify TCP/IP tocorrect the problem the user encountered.

For information about modifications to TCP/IP, see theTCP/IP Planning and Customization book.

Source File: CMPING PASCAL


Handle failed: ReturnCode

Severity: Warning.

Explanation: TCP/IP cannot handle notes.


User or Operator Response: Tell the systemprogrammer the type of error you encountered.





Host name or address not found.

Severity: Warning.

Explanation: You specified an unknown host name orIP address.


User or Operator Response: Correct the syntax of thehost name or IP address specified, and resubmit thePING command.

For information about the syntax of the PINGcommand, see the TCP/IP User’s Guide.



Length must be between 8 & 8500

Severity: Warning.

Explanation: An invalid LENGTH parameter wasspecified.


User or Operator Response: Specify a LENGTHparameter between the accepted minimum andmaximum values, and resubmit the PING command.

For information about the LENGTH parameter of thePING command, see the TCP/IP User’s Guide.



Missing number after COUNT option

Severity: Warning.

Explanation: You specified a COUNT parameterwithout a value.


User or Operator Response: Specify a COUNTparameter value greater than or equal to zero followingthe COUNT parameter, and resubmit the PINGcommand.

For information about the COUNT parameter of thePING command, see the TCP/IP User’s Guide.



Missing number after LENGTH option

Severity: Warning.

Explanation: You specified a LENGTH parameterwithout a value.


User or Operator Response: Specify a LENGTHparameter value between the accepted minimum andmaximum values, and resubmit the PING command.

For information about the LENGTH parameter of thePING command, see the TCP/IP User’s Guide.




Missing number after TIMEOUT option

Severity: Warning.

Explanation: You specified a TIMEOUT parameterwithout a value.


User or Operator Response: Specify a TIMEOUTparameter value between the accepted minimum andmaximum values, and resubmit the PING command.

For information about the TIMEOUT parameter of thePING command, see the TCP/IP User’s Guide.



MonQuery buffer sizes failed: ReturnCode

Severity: Error.

Explanation: The size of the PING request was greaterthan the maximum size allowed by TCP/IP.


User or Operator Response:

1. Use the LENGTH parameter to specify a smallerlength parameter value, and resubmit the PINGcommand.

For information about the LENGTH parameter ofthe PING command, see the TCP/IP User’s Guide.

2. Verify the specified size of the PING request. Themaximum PING length is determined by the largeenvelope size parameter in TCP/IP. If the size of thefailed PING request looks correct, check with yoursystem programmer to verify the large envelopesize parameter.

System Programmer Response: Verify the largeenvelope size parameter of theLARGEEVELOPEPOOLSIZE statement.

For information about the large envelope sizeparameter in TCP/IP, see the TCP/IP Planning andCustomization book.



MonQuery buffer sizes returns bad lengthMonQueryLen

Severity: Error.

Explanation: The PING request was too large forTCP/IP to accept.



1. Use the LENGTH parameter to specify a smallerlength parameter value, and resubmit the PINGcommand.

For information about the LENGTH parameter ofthe PING command, see the TCP/IP User’s Guide.

2. Verify the specified size of the PING request. Themaximum PING length is determined by the largeenvelope size parameter in TCP/IP. If the size of thefailed PING request looks correct, check with yoursystem programmer to verify the large envelopesize parameter.

System Programmer Response: Verify the largeenvelope size parameter of theLARGEEVELOPEPOOLSIZE statement.

For information about the large envelope sizeparameter in TCP/IP, see the TCP/IP Planning andCustomization.



Non-numerical argument BadArgument

Severity: Warning.

Explanation: You specified a non-numerical argumentwhen a numerical argument was expected.


User or Operator Response: Correct the syntax of theinvalid parameter, and resubmit the PING command.



Procedure Name: SafeConvert

PING: Extraneous parameter BadParameter

Severity: Warning.

Explanation: You specified an extraneous parameter.


User or Operator Response: Remove the extraneousparameter and resubmit the PING command.




Ping request failed: ReturnCode

Severity: Warning.

Explanation: The PING request could not complete.The listed return code explains why the PING requestfailed. For example, the TIMEOUT parameter expired.

PING Messages



User or Operator Response: Examine the return code,correct the cause of the problem, and resubmit thePING command. If the problem continues, contact yoursystem programmer.

For information about the possible reasons for a PINGrequest failure, see the TCP/IP User’s Guide.





PING: Unknown host HostName

Severity: Warning.

Explanation: The host name specified was not in thehost address cross-reference table.



1. Correct the syntax of the host name and resubmitthe PING command.


2. Verify that the specified host name is valid. If thehost name looks correct, check with your systemprogrammer to verify the host addresscross-reference table.

System Programmer Response: Verify the hostaddress cross-reference table.

For information about the host address cross-referencetable in TCP/IP, see the TCP/IP Planning andCustomization.



PING: Unknown option BadOption

Severity: Warning.

Explanation: You specified an unknown option.


User or Operator Response: Remove the unknownoption, and resubmit the PING command.




Timeout must be between MINpingTIMEOUT &MAXpingTIMEOUT

Severity: Warning.

Explanation: You specified an invalid TIMEOUTparameter.


User or Operator Response: Specify a TIMEOUTparameter between the accepted minimum andmaximum values, and resubmit the PING command.

For information about the TIMEOUT parameter of thePING command, see the TCP/IP User’s Guide.



PING Messages

Chapter 9. PING Messages 157

PING Messages


Chapter 10. PORTMAP Messages

This chapter contains PORTMAP messages. Procedure names are shown in eachmessage section. For PORTMAP problems, see the TCP/IP Programmer’s Referencefor RPCINFO, PING, and NETSTAT.

See the RPC parameters to determine the requirements for the parameters. Alsocheck:v System console (verify that PORTMAP and TCPIP are running)v Sufficient memory availability.

Note: The parameter list may be important for determining incorrect or missinginformation.

couldn’t do tcp_create

Severity: Fatal.

Explanation: PORTMAP encountered an error creatinga TCP socket; the program exits.

System Action: The program exits.

User or Operator Response: Check for memoryavailability. Check that the tcpip machine is running.Restart.

Source File: portmap c

Procedure Name: main() svctcp_create()

couldn’t do udp_create ReturnCode

Severity: Fatal.

Explanation: Portmap encountered an errorestablishing a UDP socket. The program exits.


User or Operator Response: Check for memoryavailability. Check that the tcpip machine is running.Restart.


Procedure Name: main() svcudp_create()

portmap cannot bind ReturnCode

Severity: Fatal.

Explanation: Portmap encountered an error binding aname to a socket. The program exits.


User or Operator Response: Check the name that isbinding. Check memory availability. Ping the bindingsystem. Check if same net family. Check the portnumber.


Procedure Name: main() bind()

portmap cannot bind ReturnCode

Severity: Fatal.

Explanation: Portmap encountered an error binding asocket to a name. The program exits.


User or Operator Response: Check the name that isbinding. Check memory availability. Ping the bindingsystem. Check if same net family. Check the portnumber.


Procedure Name: main() bind()

portmap cannot create socket ReturnCode

Severity: Fatal.

Explanation: Portmap encountered an error creating asocket. The program exits.


User or Operator Response: Check memoryavailability. Check that tcpip is running.


Procedure Name: main() socket()

portmap: started


Explanation: Portmap execution has begun.

System Action: The program continues.




Procedure Name: main() reg_portmapper()

run_svc returned unexpectedly

Severity: Fatal.

Explanation: Portmap service execution unexpectedlyterminated; portmap aborts. The program should neverreach this message. svc_run normally waits on a select()call.

System Action: The program aborts.

User or Operator Response: Restart portmap. Analyzeresponses to the portmap from the network.


Procedure Name: main() svc_run()

stderr, svc_sendreply

Severity: Fatal.

Explanation: An error occurred while sending thereply back to the client. Portmap aborts. The messageprints out only during debugging (-d/-D optionparameter).




Procedure Name: reg_srv() svc_sendreply()

PORTMAP Messages


Chapter 11. Remote Printing Messages

This chapter contains remote printing messages.

LPD MessagesThis section contains LPD messages.

Abort failed ReturnCode.

Severity: Error.

Explanation: An attempt to abort a TCP connectionfailed.

User or Operator Response: Wait for the connectionto time out and try again.


Source File: LPD PASCAL

Procedure Name: DoNewConnState

Attempted SMSG from userid ignored.

Severity: Warning.

Explanation: You are not authorized to send amessage to LPD. The command you sent is ignored.


User or Operator Response: Request authorizationfrom the system programmer.


Procedure Name: ProcessSMSG

BeginTcpip: ReturnCode

Severity: Error.

Explanation: An error occurred connecting to TCP/IPservices.



System Programmer Response: Check to see thatTCPIP services are running.


Procedure Name: PrepareTCP

Call to DTCXLATE failed with reason code: reasoncode

Severity: Error.

Explanation: The DTCXLATE routine used to read

TCP/IP translation tables failed with the indicatedreason code. This condition indicates an internal errorhas occurred; the listed reason code corresponds to thepositional parameter that caused this error.

System Action: LPD server processing terminates.

User or Operator Response: Inform the systemadministrator of this problem.

System Programmer Response: Inform the IBMsupport center of this problem.


Procedure Name: ProcessOptions, PreparePrinters

Callable service routine DTCXLATE is not available.Unable to load tablename TCPXLBIN *

Severity: Error.

Explanation: The DTCXLATE CSL routine was notfound when trying to load the specified translate table.




Procedure Name: ProcessOptions, DoXlateTable

Cannot find the file filename filetype filemode.

Severity: Warning.

Explanation: You specified a file that does not exist onthe disks to which you have access.


User or Operator Response: Reissue the commandwith the correct file specification.


Procedure Name: ProcessOperands

Cannot open filename filetype.

Severity: Error.

Explanation: The indicated configuration file couldnot be opened.


System Action: The program halts.

User or Operator Response: Check the accessrestrictions on the specified file.


Procedure Name: PreparePrinters

Cannot reach host

Severity: Warning.

Explanation: The host you specified could not bereached. This host is specified as the remote host on theREMOTE statement in the configuration file.


User or Operator Response: Confirm that theconfiguration file entry is correct and determine thereason the host could not be reached. Correct theconfiguration file, if necessary, and reissue thecommand.


Procedure Name: GetHostResol

Cannot use mode mode as spool for printer

Severity: Warning.

Explanation: The indicated disk mode could not beused as a spool disk for the specified printer.


User or Operator Response: Use the default disk.

System Programmer Response: Check to see thatLPSERVE is accessing its A disk in read-write mode.


Procedure Name: CompletePrinters

CMSPPRT: DoSioWat failed. CSW = Keys CCWAdrUnitStat ChanStat Bytes

Severity: Error.

Explanation: A DoSioWat call failed in CMSPPRT.



System Programmer Response: Restart the LPSERVEmachine.

Source File: CMSPPRT PASCAL

Procedure Name: PrintL

Command not understood.

Severity: Error.

Explanation: An invalid command was received bymeans of SMSG.


User or Operator Response: Check the command andtry again.



Connection connection terminated because ReturnCode

Severity: Error.

Explanation: LPD terminated this connection for theindicated reason.


User or Operator Response: Check the indicatedreason and take the appropriate action.


Procedure Name: DoEndConnection

Content of file tablename TCPXLBIN {specified forservice servicename} is not valid

Severity: Error.

Explanation: The content of the file listed in themessage was not as expected; thus, no data translationcan be performed using this file. If a service name islisted, this condition was detected for the table definedfor that service in the LPD configuration file; otherwise,this error is associated with a default translation table.The file in question may not have been properlycreated or may have been altered or corrupted throughsome means.


User or Operator Response: Verify the correcttranslate table file name has been specified. If this is thecase, see TCP/IP Planning and Customization forinformation about using and creating translation tables,to determine why this file cannot be used. Correct anyproblems, then reinitialize the LPD server.



Could not define address as a punch

Severity: Error.

Explanation: A CP DEFINE command failed for theindicated device.


LPD Messages



System Programmer Response: Verify the punchaddress.


Procedure Name: DefineCPDevice

Could not define device for job. Unknown type typetreated as "NONE".

Severity: Warning.

Explanation: LPD could not find a devicespecification. The device type was treated as NONE.Known types are PRINTER, PUNCH, and NONE.



System Programmer Response: Verify the SERVICESstatement in LPD CONFIG file on the LPSERVE’s Adisk.


Procedure Name: GetJobDevice

Could not define printer at vaddr. Return code wasReturnCode

Severity: Error.

Explanation: A CP DEFINE failed for the indicatedprinter address.



System Programmer Response: Verify the printeraddress.


Procedure Name: DefineCPDevice

Could not DETACH PUNCH address. Return code wasReturnCode

Severity: Error.

Explanation: A CP DETACH command failed for theindicated punch device.



System Programmer Response: Check the punchstatus.


Procedure Name: SendFailingMail

Could not do IDENTIFY. RC = ReturnCode

Severity: Error.

Explanation: An attempt to determine the local node’sname failed. This is a necessary step to prepare theprinters.


User or Operator Response: Verify the printer name.



Could not erase name type mode. RC = ReturnCode

Severity: Warning.

Explanation: The program could not erase theindicated file.



System Programmer Response: Check the accessinformation of LPSERVE’s A disk.


Procedure Name: EraseFile

Could not open control file site CFjob printer. Jobabandoned.

Severity: Error.

Explanation: The indicated control file could not beopened.

System Action: The job aborts.


System Programmer Response: Check to see if theLPR client is sending a corrupted control file to theserver.


Procedure Name: ProcessControlFile

Could not open data file site ftype. Job abandoned.

Severity: Error.

Explanation: The indicated file could not be opened.

System Action: The job is terminated.

User or Operator Response: Retry the LPR command.The data file sent to the LPSERVE machine failedbecause it was corrupted. If the error condition

LPD Messages

Chapter 11. Remote Printing Messages 163

continues, tell the system programmer about theproblem.


Procedure Name: DoSendStep

Could not open "name QUEUE"

Severity: Error.

Explanation: The indicated printer queue file couldnot be opened.


User or Operator Response: Wait until the file isprinted.


Procedure Name: SavePrinterQueue

Could not open "name SITE"

Severity: Warning.

Explanation: The indicated SITE file could not beopened.



System Programmer Response: Ensure that the IPaddress is in the indicated file so that LPD can openthe file.


Procedure Name: LoadSite

Could not open site JFJob.

Severity: Error.

Explanation: The program could not open theindicated file.



System Programmer Response: Ensure that the IPaddress is in the indicated file so that LPD can openthe file.



Could not retrieve SMSG

Severity: Warning.

Explanation: An attempt to read the next SMSGfailed. The queue may be empty.





Could not spool device address. Return code wasReturnCode

Severity: Error.

Explanation: A CP spool command failed with theindicated return code.



System Programmer Response: Check the deviceaddress for the local pointer.



Could not spool PUNCH address to smtp. Return codewas ReturnCode

Severity: Error.

Explanation: This message is sent to you throughSMTP mail if you specified mail as a FAILEDJOBparameter in the LPD CONFIG file.



System Programmer Response: Check the punchaddress.


Procedure Name: SendFailingMail

Could not TAG device address string. Return code wasReturnCode. Response was ResponseString.

Severity: Error.

Explanation: A CP TAG command failed.



System Programmer Response: Check to see that thetag value is correct.



LPD Messages


CP command failed. RC = ReturnCode Responseresponse

Severity: Error.

Explanation: A CP command, issued as a result of acommand received by way of an SMSG, failed.


User or Operator Response: Check the SMSGcommand sent to LPSERVE.



Disk mode is not accessed or is not writable.

Severity: Warning.

Explanation: The indicated site disk is not accessed oris not writable by this user ID. The site disk must allowwrite access to this user.



System Programmer Response: Check to ensure thatLPD has write access to its A disk.



Error reasoncode reading file tablename TCPXLBIN{specified for service servicename}

Severity: Error.

Explanation: An I/O error occurred during an attemptto read the named translation table from an accesseddisk or directory. The file for which this error occurredis either a default translation table or, if a service nameis listed, the table defined for that service in the LPDconfiguration file.


User or Operator Response: The listed reason codecorresponds to an FSOPEN or FSREAD return code.Consult the z/VM: CMS Callable Services Reference forinformation about this error code and correct anyproblems. Then, reinitialize the LPD server.



Failed to allocate block for jobnumber from site

Severity: Error.

Explanation: A step block, required for remoteprinting, could not be allocated for this job because ofinsufficient memory.



System Programmer Response: Re-IPL the LPSERVEvirtual machine. Increase virtual memory for LPSERVE,if necessary.


Procedure Name: DoNewSubcommand

Failed to open site filetype.

Severity: Error.

Explanation: The indicated file could not be opened.



System Programmer Response: Re-IPL LPSERVE toclear the last error.


Procedure Name: DoNewSubcommand

Failed to write to printer address. RC = ReturnCode

Severity: Error.

Explanation: An error occurred writing to this printer.



System Programmer Response: Check the printeraddress and status.

Source File: LPDFLPF PASCAL

Procedure Name: WritePrinter

Failed to write to punch address. RC = ReturnCode

Severity: Error.

Explanation: An error occurred writing to theindicated punch.



System Programmer Response: Check the status ofpunch service.


Procedure Name: PunchLine

LPD Messages


IDENTIFY output format different than expected

Severity: Warning.

Explanation: The output of a CMS IDENTIFYcommand was in an unexpected format.


User or Operator Response: From the CMS commandline, type "ID" to obtain sample output. Have thisinformation available when contacting the IBM SupportCenter.



Ignoring job number from site site because there is noSITE file.

Severity: Warning.

Explanation: A job was received from a site with nocorresponding SITE file.

System Action: The job is ignored.

User or Operator Response: Check the LPR client andtry again.


Procedure Name: LoadPrinterQueue

Ignoring TCP/IP notice tag on connection connection

Severity: Warning.

Explanation: The indicated notification is ignoredbecause of a probable error in the connection.


User or Operator Response: Check the taginformation and try again.


Procedure Name: ProcessTCP

InitEmulation failed

Severity: Error.

Explanation: An error occurred initializing EC modeemulation, which is necessary to run TCP/IP in avirtual machine with ECMODE OFF.



System Programmer Response: Investigate the statusof EC mode emulation.


Procedure Name: PrepareTCP

Job is in unrecognized state (state).

Severity: Warning.

Explanation: A job is in an unrecognized state.


User or Operator Response: Check the network statusand tell the system programmer about the problem.

System Programmer Response: Re-IPL the LPSERVEmachine.


Procedure Name: ProcessWork

Job job abandoned. Job file too short.

Severity: Error.

Explanation: The indicated job was abandonedbecause the job file did not contain enoughinformation. The printer name, site name, or lengthfields could not be read.


User or Operator Response: Check the network statusand try again.


Procedure Name: LoadJob

Job job abandoned. Not enough storage.

Severity: Error.

Explanation: The program could not allocate storageto process another job.



System Programmer Response: If the file is large andif the LPSERVE is used as a spool, increase the diskcapacity for LPSERVE.


Procedure Name: LoadJob

Out of storage for connections

Severity: Error.

Explanation: A connection record could not be builtbecause sufficient memory was not available.



System Programmer Response: If this condition

LPD Messages


frequently occurs, allocate more virtual memory for thisvirtual machine.


Procedure Name: AllocConnection

Program error: Invalid option (option)

Severity: Error.

Explanation: You specified an invalid option.


User or Operator Response: Reissue the commandwith the correct option.


Procedure Name: PreparePrinters, ProcessOptions

Site file "name SITE" record 1 unreadable.

Severity: Warning.

Explanation: The first record in the indicated SITE fileis unreadable



System Programmer Response: Ensure that the IPaddress is in the indicated file.



Site file "SName SITE" record 2 unreadable.

Severity: Warning.

Explanation: The second record in the indicated SITEfile is unreadable.


System Programmer Response: Ensure that the IPaddress is in the indicated file. None.



spooltype kind is unknown (type).

Severity: Error.

Explanation: A printer specification contained anunknown spool type. RSCS did not recognize theprinter.



System Programmer Response: Check the printer ID.



The keyword word is ambiguous. Use a longerabbreviation.

Severity: Warning.

Explanation: The indicated configuration file keywordabbreviation is ambiguous.


User or Operator Response: Replace thisconfiguration file entry with a longer abbreviation andreissue the command.


Procedure Name: ProcessOptions

The keyword word is not a keyword.

Severity: Warning.

Explanation: The indicated configuration file keywordis not valid.


User or Operator Response: Correct the configurationfile and reissue the command.


Procedure Name: ConfigService

The keyword word is too short. Use a longerabbreviation.

Severity: Warning.

Explanation: The indicated configuration file keywordabbreviation is ambiguous.


User or Operator Response: Replace the indicatedconfiguration file keyword with a longer abbreviationof the keyword and reissue the command.



The keyword word was not recognized.

Severity: Error.

Explanation: The indicated configuration file keywordis not valid.


User or Operator Response: Correct the configurationfile entry and reissue the command.

LPD Messages




The option option is ambiguous. Use a longerabbreviation.

Severity: Warning.

Explanation: The abbreviation specified for thiscommand-line option is ambiguous.


User or Operator Response: Reissue the commandwith a longer abbreviation for the intended option.



The option option was not recognized. Use theTRACE, TYPE or VERSION options as needed.

Severity: Error.

Explanation: An invalid option was specified on thecommand line. The message lists the valid options.


User or Operator Response: Reissue the commandwith valid option specifications.



The service name has been described more than once.

Severity: Warning.

Explanation: A SERVICE statement specified the sameprinter name as one already specified in theconfiguration file.


User or Operator Response: Remove the duplicatestatement and any associated statements, such asLOCAL, RSCS, or REMOTE, and reissue the command.



Translation file tablename TCPXLBIN {for serviceservicename} not found

Severity: Error.

Explanation: The named translation table was notlocated on any currently accessed minidisk. If a servicename is listed, this condition was detected for the tabledefined for that service in the LPD configuration file;otherwise, the listed file is a default translation table.


User or Operator Response: Verify the correcttranslate table file name has been specified, and thatthis file is present in the LPD server machine CMSsearch order. Correct any problems, then reinitialize theLPD server.



Use a class of A to Z, 0 to 9.

Severity: Error.

Explanation: The class was not valid.


User or Operator Response: Confirm that theconfiguration file entry is correct. Only capital Athrough Z or 0 through 9 can be used.

LPQ MessagesThis section contains LPQ messages.

Both the printer and the host name are not known.

Severity: Error.

Explanation: The program could determine neither theprinter name nor the host name.


User or Operator Response: Check the host name andprinter name before you reissue the command.

Source File: LPQ PASCAL


Cannot get a printer name.

Severity: Error.

Explanation: The program could not find the printername on the command line or in the GLOBALV file.


User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer name.



LPD Messages


Cannot get the printer host.

Severity: Error.

Explanation: The default host name could not be readfrom the GLOBALV file.


User or Operator Response: Specify the host name onthe command line, or use LPRSET to set up the defaulthost name.




Severity: Error.

Explanation: You specified an invalid option on thecommand line.


User or Operator Response: Reissue the commandwith valid options.



The host name is not known.

Severity: Error.

Explanation: The program could not determine thehost name.


User or Operator Response: Use the valid host namewith the command. A valid host name is one that canbe resolved by the program.



The option option was not recognized. Use the ALL,HOST, PRINTER, TRACE, TYPE or VERSIONoptions as needed.

Severity: Error.

Explanation: You specified an invalid option on thecommand line. Valid options are listed.





The printer name is not known.

Severity: Error.

Explanation: The program could not determine theprinter name.


User or Operator Response: Check the printer nameat the server machine and reissue the command with avalid printer name.



LPQ Messages


LPR and LPRSET MessagesThis section contains messages issued by LPR and LPRSET.

0000 TCP/IP installation error: DTCUMETEXT not found

Severity: Error

Explanation: The TCP/IP message repository file(DTCUME TEXT) is required so messages can be issuedby this program, but this file was not found in the CMSsearch order.


User or Operator Response: Ensure the TCP/IP“Client” code minidisk (TCPMAINT 592, by default) islinked and accessed before the program that issued thismessage is invoked again. If this problem persists,inform the system administrator.

System Programmer Response: This error indicates anincorrect or incomplete product installation. Ensure thelisted file is present on the TCP/IP “Client” codeminidisk. If such a file is present, it is possible that thisdisk contains an older version (level) of TCP/IP.

Source File: LPR, LPRSET EXEC

2001 File mode 'fm' is not valid; acceptedvalues are: A-Z. The default file mode(fm-default) will be used

Severity: Warning.

Explanation: The indicated file mode is not alphabetic;that is, not within the character range of A through Z.

System Action: Command execution continues, withthe listed default used in place of the provided filemode.


Source File: LPR EXEC

2002 File mode number 'nn' is not valid;accepted values are: 0-6. The default filemode (fm-default) will be used

Severity: Warning.

Explanation: The indicated file mode number is notnumeric; that is, not within the range of 0 through 6.

System Action: Command execution continues, withthe listed default used in place of the provided filemode.



2003 Ignoring additional file identifierinformation: aaaaaaaa

Severity: Warning.

Explanation: More file identifier information wasprovided than was expected; this extra information hasbeen ignored. The provided file name, file mode andfile type continue to be used for processing.




2004 File 'fn ft fm' was not found

Severity: Error.

Explanation: The listed file was not found at theindicated file mode.


User or Operator Response: Verify all file identifierinformation has been correctly specified. Also, ensurethe disk or directory on which the file resides isaccessed.


2005 No file has been identified for printing

Severity: Error.

Explanation: The LPR command was invoked withprint-specific options, but information that identifies afile to be printed has been omitted.


User or Operator Response: Provide the file name, filetype and (optionally) the file mode of the file to beprinted when this command is issued.


2006 A file type must be provided for file:filename

Severity: Error.

Explanation: The LPR command was invoked withoutsufficient information to identify the file to be printed;only the indicated file name was provided.


User or Operator Response: Provide the file name, filetype and (optionally) the file mode of the file to beprinted when this command is issued.


LPR and LPRSET Messages


2007 File identifier 'fileid' is not valid

Severity: Error.

Explanation: The provided file information does notcomprise a valid CMS file identifier.


User or Operator Response: Verify all file identifierinformation has been correctly specified.


2008 Use the form: command filename filetype(filemode)

Severity: Error.

Explanation: The indicated command (LPR) wasinvoked with a question mark (?) instead ofconventional file identifier information. In response, theminimal usage information indicated is displayed.




2009 The option1 option can be used only ifthe option2 option is also used.

Severity: Error.

Explanation: The first option listed (option1) cannot beused unless the second option (option2) has alreadybeen specified as part of the command. Thisdependency usually applies to the NICKNAME andTAG options, but may apply to other commandoptions.


User or Operator Response: Review the descriptionsof both options (option1 and option2) identified by thismessage, then retry the command with the correctoption combination.


2010 The option option value (value) is not{valid | a valid number}.

Severity: Error.

Explanation: The value specified for the indicatedoption was determined to not be correct. Depending onthe option listed, the provided value may:

be too long, or too short.contain inappropriate characters.be required to be a numeric value, possibly a wholenumber.


User or Operator Response: Review the description ofthe listed option to determine why the current value

was not accepted, then retry the command with anappropriate value specified.


2011 The option1 and option2 options aremutually exclusive.

Severity: Error.

Explanation: The two options listed (option1 andoption2) cannot be used together.


User or Operator Response: Specify only one of thelisted options when this command is issued. Ifnecessary, review the description of both options todetermine which option should be used.


2012 Option option is not recognized or is notvalid.

Severity: Error.

Explanation: The option listed is not supported bythis command.


User or Operator Response: Verify the option wasspecified correctly and has not been misspelled. Ifnecessary, review the command description todetermine whether the listed option can be used withthis command.


2013 An RSCS link or node parameter hasbeen incorrectly specified. Specify linkand node parameters using one of thefollowing formats: linkid,nodeidlinkid@nodeid linkid AT nodeid

Severity: Error.

Explanation: The link and node values supplied withthe RSCS option are not valid, or have not beencorrectly specified.


User or Operator Response: Verify both the RSCS linkand node values were provided, and that these werespecified using one of the formats listed in themessage.


2014 Error reading file: file Return code: rc

Severity: Error.

Explanation: An error occurred while attempting toread the specified file.




User or Operator Response: Verify access to the listedfile, and that the file can be read. If necessary, see thez/VM: CMS Pipelines Reference for more informationabout the '<' PIPE stage return code.


2015 An error occurred while processing{RSCS header | 'file' data} records

Severity: Error.

Explanation: An error occurred while attempting towrite the records of the indicated type to a virtualprinter or virtual punch device.


User or Operator Response: The most probable causefor this error is a CMS PIPE command error. To obtainmore information, reissue the command and includethe TRACE option.


2016 Unable to define a devicetype devicewithin address range vdev1-vdev2

Severity: Error.

Explanation: All virtual addresses within the indicatedrange are in use. Therefore, the indicated virtual devicecould not be defined.


User or Operator Response: Review the usage of theaddresses within the indicated range, then makeavailable at least one of these virtual addresses.


2017 Server serverid is not defined in the CPdirectory

Severity: Error.

Explanation: While attempting to establishappropriate settings to process your print request, thelisted server was found to not be valid for this system.


User or Operator Response: Verify the listed user IDwas correctly:v specified with the SERVER option,v defined in a CMS NAMES file, orv set using the LPRSET command.

If necessary, contact the system administrator todetermine what server should be used to process yourrequest.


2018 File 'file' is too wide to print

Severity: Error.

Explanation: The indicated file has a logical recordlength (LRECL) greater than 1280. For this file, RSCScannot process records longer than 1280 bytes.


User or Operator Response: Verify the record lengthof the listed file is required for the data that it contains.If possible, alter the record length using appropriateCMS or XEDIT commands, and retry the command. Ifthe record length for this file cannot be changed to 1280or less, it cannot be printed using RSCS.


2019 Matching string delimiter (delim-char)not found.

Severity: Error.

Explanation: A value was specified that begins with arecognized delimiter — usually a single (') or double (")quote — but a second, or closing, delimiter was notpresent in the operands provided.


User or Operator Response: Properly delimit thevalue in question by including a closing delimiter, oromit the initial delimiter (if it is not required) when thiscommand is issued.


2020 The option option cannot be used for{asynchronous | synchronous}processing.

Severity: Error.

Explanation: The listed option was specified, but itsuse is not supported for the indicated type, or mode, ofprocessing.


User or Operator Response: Review the optionsspecified for this command and verify they are allapplicable to the current processing mode, and that theprocessing mode is itself correct. If necessary, reviewthe command and option descriptions to identifysuitable options for this processing mode, or forinformation about changing modes.


2021 The option option has been incorrectlyspecified.

Severity: Error.

Explanation: The listed option has been recognized,



but cannot be used, possibly due to a dependency onone or more other options.

User or Operator Response: Review the descriptionfor this option to determine the conditions for its use,then correct any problems and retry the command.



2022 No printer has been identified toprocess file: file

Severity: Error.

Explanation: The listed file cannot be processedbecause a printer has not been specified on which thefile is to be printed.


User or Operator Response: Specify a printer (or printqueue name) using one of the following means:

Provide a printer name with the PRINTER optionwhen the command is issued.Define a printer (and host) using a CMS NAMESfile entry, then specify that nickname with theNICKNAME option when the command is issued.Define a default printer (and host) by using theLPRSET command.


2023 No host has been identified to processfile: file

Severity: Error.

Explanation: The listed file cannot be processedbecause a printer host has not been specified to whichthe file should be directed.


User or Operator Response: Specify a printer hostname using one of the following means:

Provide a host name with the HOST option whenthe command is issued.Define a host (and printer) using a CMS NAMESfile entry, then specify that nickname with theNICKNAME option when the command is issued.Define a default host (and printer) by using theLPRSET command.


2024 No value was provided with the optionoption.

Severity: Error.

Explanation: When the indicated option is used, anon-null value must also be specified; however, nosuch value was present.


User or Operator Response: Specify an appropriatevalue in addition to this option when the command isissued.


2025 Nickname name in file file does notdefine usable data

Severity: Error.

Explanation: An attempt was made to retrieveinformation defined by the listed nickname from theindicated file. However, definitions or informationrelevant to the processing performed by this commandwere not present.


User or Operator Response: Verify the entriesassociated with this nickname are correctly defined inthe indicated file, and that the nickname itself iscorrect; then retry the command.


2026 Tag tagname for nickname name in filefile defines a value that is not valid

Severity: Error.

Explanation: The value defined by the indicated tagwas determined to not be correct. Depending on thetag listed, the defined value may:v be too long, or too short.v contain inappropriate characters.v define more data than should be present.v be required to be a numeric value, possibly a whole

number.


User or Operator Response: Review the description ofthe listed tag to determine why the current value wasnot accepted, then correct the nickname entry in theindicated file and retry the command.


2027 Tag tagname for nickname name in filefile does not define any data

Severity: Error.

Explanation: An attempt was made to retrieveinformation defined by the listed nickname from theindicated file. However, only the tag itself is present.


User or Operator Response: Verify the correctnickname/tag was specified, or define an appropriatevalue using this tag, then retry the command.




2028 Tag tagname for nickname name in filefile does not define a {printer | host}

Severity: Error.

Explanation: The value defined by the listed tag wasdetermined to not be correct; a printer or a host namewas expected to be present, but no such value exists.


User or Operator Response: Verify the correctnickname/tag was specified, or define an appropriatevalue using this tag, then retry the command.


2029 CMS file mode number number detected.File fn ft fm cannot be processed withthe command command.

Severity: Error.

Explanation: An attempt has been made to print a filethat has the indicated CMS file mode number. Filesdesignated with this file mode number cannot beprocessed by the LPR command.


User or Operator Response: Change the file modenumber associated with the file to be printed to onethat is not restricted by the LPR command, then retrythe operation. Refer to the description of the filemodeoperand for the LPR command in the TCP/IP User’sGuide for information about restricted file modenumbers.

For certain file mode numbers, it may be possible toprint the file using asynchronous operations.


2031 command Level level, Internal version IDversion


Explanation: The indicated information is providedwhen the QUERY option has been processed.




2038 The following command failed: commandReturn code: rc

Severity: Error.

Explanation: The indicated CP or CMS commandfailed with the listed return code.


User or Operator Response: Review the appropriate

CP or CMS documentation to determine why thiscommand failed, and correct any problems.


2039 Internal error in routine: routinenameError information: errortext

Severity: Error.

Explanation: A logic error was detected duringcommand processing.





2040 Use this form: command printer host

Severity: Error.

Explanation: This message is displayed if:

1. no operands, or an insufficient number of operandswere provided at invocation.

2. the indicated command (LPRSET) is invoked with aquestion mark (?) instead of conventional printerand host information. In response, the minimalusage information indicated is displayed.


User or Operator Response: If this message wasproduced in response to the first condition listed,specify both a printer and host name when thecommand is issued.

Source File: LPRSET EXEC

2041 Parameters cannot be specified with theoption option

Severity: Error.

Explanation: When the indicated option is used,printer and host values cannot be specified.


User or Operator Response: Do not include printerand host information when the listed option is used.


2042 Supported options are: optionlist


Explanation: The LPRSET command was invokedwith a question mark (?) insead of conventional printerand host information. In response, minimal usage



information is displayed that includes the options listedby this message.




2043 Suitable arguments or options were notspecified with the option option

Severity: Error.

Explanation: The indicated option has been specified,but no options or values were provided upon whichthis option will have an effect.


User or Operator Response: Omit the indicated option(if appropriate), or include one or more applicableoperands when the command is issued. If necessary,review the description of this command and its optionsto determine an appropriate combination of values andoptions.


2044 Only the following options can bespecified with the option option:optionlist

Severity: Error.

Explanation: A conflict exists between one or morespecified options, one of which is cited in the message.When this option is specified, only certain additionaloptions may be used; these have also been listed in themessage.


User or Operator Response: If necessary, review theoption descriptions for this command to determine anappropriate combination of options.


2045 Ignoring additional destinationinformation: aaaaaaaa

Severity: Warning.

Explanation: More print destination information wasprovided than was expected; this extra information hasbeen ignored. The provided printer and host valuescontinue to be used for processing.




2050 Printer and host values have not beendefined


Explanation: At present, no printer or host defaultsare being maintained using CMS global variables.




2051 Your LPR printer is currently set to:printer at: host


Explanation: The indicated printer and host values arethose being maintained using CMS global variables; thecurrent values are listed.




2052 Server is defined as: serverid {(Default)}


Explanation: The indicated server ID will be used toprocess asynchronous print requests. If a user-specificvalue has not been established through use of a priorLPRSET command, the system default is indicated.




2053 Printer is connected on link: linkid{(Default)}


Explanation: The indicated RSCS link will be used toprocess asynchronous print requests. If a user-specificvalue has not been established through use of a priorLPRSET command, the system default is indicated.




2054 Printer is connected on node: nodeid{(Default)}


Explanation: The indicated RSCS node will be used toprocess asynchronous print requests. If a user-specificvalue has not been established through use of a prior



LPRSET command, the system default is indicated.




2055 LPR mode: {ASYNCHRONOUS |SYNCHRONOUS} {(Default)}


Explanation: The indicated processing mode(asynchronous or synchronous) will be used to processprint requests. If a user-specific mode has not beenestablished through use of a prior LPRSET command,the system default is indicated.




2056 Nickname: name


Explanation: The indicated nickname will be used toobtain printer destination information (and possiblyother print-related values) from a CMS NAMES filewhen print requests are processed.




2057 Nickname Tag: tagname


Explanation: The indicated nickname tag will be usedto obtain printer and host addressing information froma CMS NAMES file when print requests are processed.




2058 The provided {printer | host} name isnot valid

Severity: Error.

Explanation: The printer or host name you providedis not valid. The value may be too long or too short, ormay contain inappropriate characters.


User or Operator Response: Review the descriptionfor the printer or host name to determine why thecurrent value was not accepted, then retry thecommand with an appropriate value specified.



Severity: Error.

Explanation: The program could determine neither theprinter name nor the host name.


User or Operator Response: Check the host name andthe printer name and reissue the command.

Source File: LPRP PASCAL


Call to DTCXLATE failed with reason code: reasoncode

Severity: Error.

Explanation: The DTCXLATE routine used to readTCP/IP translation tables failed with the indicatedreason code. This condition indicates an internal errorhas occurred; the listed reason code corresponds to thepositional parameter that caused this error.





Procedure Name: GetTranslateTables

Callable service routine DTCXLATE is not available.Unable to load tablename TCPXLBIN *

Severity: Error.

Explanation: The DTCXLATE CSL routine was notfound when trying to load the specified translate table.





Cannot find the file filename filetype filemode.

Severity: Warning.

Explanation: The file specified on the command linedoes not exist.


User or Operator Response: Specify the correct filename with the command.






Severity: Error.

Explanation: The program could not find the printername in the GLOBALV file.


User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer.




Severity: Error.

Explanation: The host name could not be read fromthe GLOBALV file.





Content of file tablename TCPXLBIN is not valid

Severity: Error.

Explanation: The content of the file listed in themessage was not as expected; thus, no data translationcan be performed using this file. The file in questionmay not have been properly created or may have beenaltered or corrupted through some means.


User or Operator Response: Verify the correcttranslate table file name has been specified. If this is thecase, see TCP/IP Planning and Customization forinformation about using and creating translation tables,to determine why this file cannot be used. Correct anyproblems, then retry the command.



Error reasoncode reading file tablename TCPXLBIN.

Severity: Error.

Explanation: An I/O error occurred during an attemptto read the named translation table from an accesseddisk or directory.


User or Operator Response: The listed reason codecorresponds to an FSOPEN or FSREAD return code.Consult the z/VM: CMS Callable Services Reference forinformation about this error code and correct anyproblems. Then, retry the command.



Host host did not accept printer name printer.

Severity: Warning.

Explanation: The indicated host did not recognize theindicated printer.


User or Operator Response: Check for the correctprinter name at the foreign host and specify it with thecommand.



Translation file tablename TCPXLBIN not found

Severity: Error.

Explanation: The named translation table was notlocated on any currently accessed minidisk.


User or Operator Response: Verify the correcttranslate table file name has been specified, and thatthis file is present in the CMS search order. Correct anyproblems, then retry the command.



Translation file tablename TCPXLBIN not found

Severity: Error.

Explanation: The named translation table was notlocated on any currently accessed minidisk.


User or Operator Response: Verify the correcttranslate table file name has been specified, and thatthis file is present in the CMS search order. Correct anyproblems, then retry the command.


Procedure Name: OptionCheck

Use either the NOPOSTSCRIPT or POSTSCRIPToption but not both.

Severity: Warning.

Explanation: You selected both the NOPOSTSCRIPT



and POSTSCRIPT options. You can select only one ofthese options.


User or Operator Response: Correct the commandline and reissue the command.



Use either the POSTSCRIPT or LANDSCAPE optionbut not both.

Severity: Warning.

Explanation: You selected both the POSTSCRIPT and

LANDSCAPE options. You can select only one of theseoptions.


User or Operator Response: Correct the commandline and reissue the command.



LPRM MessagesThis section contains LPRM messages.


Severity: Error.

Explanation: The program could not determine theprinter name or host name.


User or Operator Response: Check the host name andprinter name before you reissue the command.

Source File: LPRM PASCAL



Severity: Error.

Explanation: The program could not find the printername on the command line or in the GLOBALV file.


User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer name.




Severity: Error.

Explanation: The default host name could not be readfrom the GLOBALV file.






Severity: Error.

Explanation: You specified an invalid option on thecommand line.





The host name is not known.

Severity: Error.

Explanation: The program could not determine thehost name.


User or Operator Response: Use the valid host namewith a command. A valid host name is one that can beresolved by the program.



The option option is ambiguous. Use a longerabbreviation.

Severity: Warning.

Explanation: The abbreviation you specified for thiscommand-line option is ambiguous.


User or Operator Response: Reissue the command



with a longer abbreviation for the intended option.



The option option was not recognized. Use the ALL,HOST, PRINTER, TRACE, TYPE or VERSIONoptions as needed.

Severity: Error.

Explanation: You specified an invalid option on thecommand line. Valid options are listed.





The printer name is not known.

Severity: Error.

Explanation: The program could not determine theprinter name.


User or Operator Response: Check the printer nameat the server machine and reissue the command with avalid printer name.



LPRM Messages


LPRM Messages


Chapter 12. Remote Procedure Call Messages

This chapter contains RPCLIB, RPCINFO, RPCGEN, and VMRPC messages.

RPC MessagesThis section contains RPCLIB and VMRPC messages. To resolve RPC problems, dothe following:v Check the system console to ensure that PORTMAP and TCPIP are running.v Check that sufficient memory is available for tasks. The required heap size

varies, but can also be the cause of the problem.

See the TCP/IP Programmer’s Reference for information about basic RPC proceduresand the requirements for RPC parameters. From this reference, you can determinethe missing or incorrect information that caused the problem.

Some RPC problems are caused by C language coding problems, including:v Bad pointers in the user source code. Pointers to invalid addresses can cause a

number of different problems, such as protection violations and overwrittenstorage.

v Pointer misspecification, such as *p, p, &p, in the user source code.v Overwriting data or program areas, (can be an unterminated string). Strings

require a null (X'00' or \0) in the last position.v Not freeing storage at the end of the job.v Unending loops that generate storage usage.v Array subscripts out of bounds.

auth_none.c - Fatal marshalling problem ReturnCode

Severity: Fatal.

Explanation: RPC encountered an error organizing anauthorization structure.



System Programmer Response: Look for memoryoverwrite, a bad pointer, or missing data. See forinformation about auth_none() and for tcperror codes.Use the tcperror code to determine the fault and correctthe usage.

Source File: auth_uni c

Procedure Name: marshal_new_auth(),xdr_opaque_auth(), xdr_enum()

authunix_create: out of memory

Severity: Fatal.

Explanation: RPC could not allocate sufficientmemory.


User or Operator Response: Remove unusedprograms from memory. Compress memory. Restart theprogram.

System Programmer Response: Check the freememory requirements for this program.

Source File: auth_uni c

Procedure Name: authunix_create()

bad auth_len gid length str length auth length

Severity: Error.

Explanation: An RPC server received authorizationcredentials of an invalid length.

System Action: Authorization is denied. The programcontinues.

User or Operator Response: Check authorizationcredentials, correct and restart program.

Source File: svc_auun c

Procedure Name: _svcauth_unix()


Broadcast select problem ReturnCode

Severity: Fatal.

Explanation: A Portmapper RPC client encountered anerror waiting for incoming packets.

System Action: Program ends.

User or Operator Response: Clear and restartPORTMAP. The Portmapper could be receiving baddata from the network.

System Programmer Response: It may be necessary tomonitor the network for the return data. See the TCP/IPProgrammer’s Reference for information about tcperrorcodes. Use the tcperror code to determine the fault andcorrect the usage.

Source File: pmap_rmt c

Procedure Name: recv_again(), select()

broadcast: ioctl (get interface broadcast address)

Severity: Error.

Explanation: A Portmapper RPC client encountered anerror obtaining the interface broadcast address.



System Programmer Response: For information aboutioctl, see the TCP/IP Programmer’s Reference.


Procedure Name: getbroadcastnets(), ioctl()

broadcast: ioctl (get interface configuration)ReturnCode

Severity: Error.

Explanation: A Portmapper RPC client encountered anerror obtaining interface configuration information.

System Action: The procedure returns.


System Programmer Response: See the TCP/IPProgrammer’s Reference for information about ioctlSIOCGIFCONF and for tcperror codes. Use the tcperrorcode to determine the fault and correct the usage.



broadcast: ioctl (get interface destination address)ReturnCode

Severity: Error.

Explanation: A Portmapper RPC client encountered anerror obtaining the interface destination address.



System Programmer Response: See the TCP/IPProgrammer’s Reference for information about ioctlSIOCGIFDSTADDR and for tcperror codes. Use thetcperror code to determine the fault and correct theusage.



broadcast: ioctl (get interface flags): ReturnCode

Severity: Error.

Explanation: A Portmapper RPC client encountered anerror obtaining interface flag settings.



System Programmer Response: See the TCP/IPProgrammer’s Reference for information about ioctlSIOCGIFFLAGS and for tcperror codes. Use thetcperror code to determine the fault and correct theusage.



can’t reassign procedure number proc

Severity: Fatal.

Explanation: An attempt was made to register aninvalid procedure number. This procedure number isreserved by RPC to represent the null procedure.

System Action: The request fails.

User or Operator Response: Examine the procedurenumber, correct, and restart, or tell the systemprogrammer about the problem.

System Programmer Response: Correct the procedurenumber. The program returns.

Source File: svc_simp c

Procedure Name: registerrpc()

Cannot create socket for broadcast rpc ReturnCode

Severity: Fatal.

Explanation: A Portmapper RPC client encountered anerror creating a socket for broadcast RPC.



System Programmer Response: Possible causes forthis message include all sockets taken and not enoughmemory. See the TCP/IP Programmer’s Reference for

RPC Messages


tcperror codes. Use the tcperror code to determine thefault and correct the usage.


Procedure Name: clnt_broadcast(), socket()

Cannot receive reply to broadcast

Severity: Fatal.

Explanation: A Portmapper RPC client encountered anerror attempting to receive a reply to a broadcast.

System Action: The program returns.


System Programmer Response: Check pointers thatcould give program check. Check errno for a returncode.

Source File: pmap_rmt c, cmiucsoc c

Procedure Name: recvfrom(), common_recv()recvfrom(), common_recv()

Cannot send broadcast packet ReturnCode

Severity: Fatal.

Explanation: A Portmapper RPC client encountered anerror sending a broadcast packet.



System Programmer Response: See the TCP/IPProgrammer’s Reference for tcperror codes. Use thetcperror code to determine the fault and correct theusage. Look for a bad pointer, overwritten storage, orbad struct or a structlength that is less than 0 or greaterthan the maximum, which is defined as 16. The tolenmust be correct for AF_INET socket struct sockaddr.

Source File: pmap_rmt c, cmiucsoc c

Procedure Name: clnt_broadcast(), sendto(),common_send()

clnt_raw.c - Fatal header serialization error. ReturnCode

Severity: Fatal.

Explanation: RPC encountered an error serializing aheader.



System Programmer Response: See the TCP/IPProgrammer’s Reference for tcperror codes. Use thetcperror code to determine the fault and correct theusage. Check for a bad pointer or overwritten data.

Source File: clnt_raw c, xdr c, rpc_prot c

Procedure Name: clntraw_create(), xdr_callhdr(),

xdr_u_long(), xdr_enum(), xdr_short(), xdr_putlong(),xdr_getlong()

clnttcp_create: out of memory

Severity: Fatal.



User or Operator Response: Clear unneededprograms. Allot more memory to the task.

System Programmer Response: Check for a badpointer, an unending loop using up storage, a programnot freeing storage at termination, too many programsin process, or an unterminated string. Move the job to ahigher memory class.

Source File: clnt_tcp c

Procedure Name: clnttcp_create(), mem_alloc()

clntudp_create: out of memory

Severity: Fatal.



User or Operator Response: Clear unneededprograms. Allot more memory to the task.

System Programmer Response: Check for a badpointer, an unending loop using up storage, a programnot freeing storage at termination, too many programsin process, or an unterminated string. Move the job to ahigher memory class.

Source File: clnt_udp c

Procedure Name: clntudp_bufcreate(), mem_alloc()

couldn’t create an rpc server

Severity: Fatal.

Explanation: A request to have RPC create a serverfailed.



System Programmer Response: See the TCP/IPProgrammer’s Reference for the listed procedures. One ormore of the listed procedures failed. Check for a badpointer. Ensure that enough storage is available for thetask. Check for unterminated string.

Source File: svc_simp c, svc_udp c

Procedure Name: registerrpc(), svcudp_create(),svcudp_bufcreate(), sock(), bind(), mem_alloc(),xdrmem_create

RPC Messages

Chapter 12. Remote Procedure Call Messages 183

couldn’t register prog number vers number

Severity: Fatal.

Explanation: A request to have RPC register thisprogram and version failed. Portmapper may not berunning. Storage may not be available.


User or Operator Response: Use PING and RPCINFOto determine whether Portmapper is running. IfPortmapper is not running, start Portmapper andrestart the program.

System Programmer Response: Determine whetherenough storage is available for the task.

Source File: svc_simp c, svc c, pmap_cln c

Procedure Name: registerrpc(), svc_register(),pmap_set(), clntudp_bufcreate(), clnt_call()

get_myaddress: ioctl (get interface configuration)ReturnCode

Severity: Fatal.

Explanation: An RPC client encountered an errorobtaining interface configuration information(SIOCGIFCONF option).

System Action: The client exits and the program exits.


System Programmer Response: See the TCP/IPProgrammer’s Reference for information about ioctlSIOCGIFCONF and for tcperror codes. Use the tcperrorcode to determine the fault and correct the usage.

Source File: pmap_cln c, cmiucsoc c

Procedure Name: get_myaddress(), ioctl()

get_myaddress: ioctl ReturnCode

Severity: Fatal.

Explanation: An RPC client encountered an errorsetting the interface configuration flags.

System Action: The client exits. The program exits.


System Programmer Response: See the TCP/IPProgrammer’s Reference for information about ioctlSIOCGIFFLAGS and for tcperror codes. Use thetcperror code to determine the fault and correct theusage.

Source File: pmap_cln c, cmiucsoc c

Procedure Name: get_myaddress(), ioctl()get_myaddress(), ioctl()

never registered prog number


Explanation: An attempt was made to communicatewith an unregistered program.

System Action: The calling program exits.

User or Operator Response: Use PING and RPCINFOto determine whether the host is up and the program isregistered. If the program is not registered, register iton the target host.


Procedure Name: universal() universal()

registerrpc: out of memory

Severity: Fatal.

Explanation: An attempt to register an RPC serverfailed because of a lack of memory.


User or Operator Response: Remove all possible tasksto clear storage for this task and restart.

System Programmer Response: Verify that there isenough storage for the task.


Procedure Name: registerrpc(), malloc()

svc.c: - Select failed ReturnCode

Severity: Fatal.

Explanation: An RPC server encountered an errorwaiting for an incoming message.



System Programmer Response: See the TCP/IPProgrammer’s Reference for tcperror codes. Use thetcperror code to determine the fault and correct theusage.

Source File: svc c, cmiucsoc c

Procedure Name: svc_run(), select(), common_select()

svc_tcp: makefd_xprt: out of memory

Severity: Fatal.

Explanation: An RPC server ran out of memory.


User or Operator Response: Remove all unneededtasks to gain storage and restart the task.

System Programmer Response: Check for badpointers. Check that storage is adequate for the task.

RPC Messages


Source File: svc_tcp c

Procedure Name: makefd_xprt(), mem_alloc()

svctcp_.c - cannot getsockname or listen ReturnCode

Severity: Fatal.

Explanation: An RPC server encountered an erroreither in obtaining a socket name or in doing a listen. Ifa socket was opened, it will be closed.



System Programmer Response: See the TCP/IPProgrammer’s Reference for information about tcperrorcodes. Use the tcperror code to determine the fault andcorrect the usage. Check for a bad pointer. Check thatstorage is sufficient for the task.

Source File: svc_tcp c, cmiucsoc c

Procedure Name: svctcp_create(), getsockname(),listen()

svctcp_.c - udp socket creation problem ReturnCode

Severity: Fatal.

Explanation: An RPC server encountered an errorcreating a TCP socket.


User or Operator Response: Remove all unneededtasks and restart the task.

System Programmer Response: See the TCP/IPProgrammer’s Reference for tcperror codes. Use thetcperror code to determine the fault and correct theusage. Check whether all sockets are already beingused. Check whether storage is available for the task.

Source File: svc_tcp c, cmiucsoc c

Procedure Name: svctcp_create(), socket()

svctcp_create: out of memory

Severity: Fatal.



User or Operator Response: Remove all unneededtasks to free storage and restart task.

System Programmer Response: Check that enoughstorage is available to run task.

Source File: svc_tcp c

Procedure Name: svctcp_create(), mem_alloc()

svcudp_create - cannot getsockname

Severity: Fatal.

Explanation: An RPC server encountered an errorgetting the name of a socket.



System Programmer Response: Check for a badpointer.

Source File: svc_udp c, cmiucsoc c

Procedure Name: svcudp_bufcreate(), getsockname()

svcudp_create: out of memory

Severity: Fatal.



User or Operator Response: Remove all unneededtasks to free storage and restart task.

System Programmer Response: Check that storage isavailable for the task.

Source File: svc_udp c

Procedure Name: svcudp_bufcreate(), mem_alloc()

svcudp_create: socket creation problem

Severity: Fatal.

Explanation: An RPC server encountered an errorcreating a socket.


User or Operator Response: Remove unneeded tasksto gain storage and restart task.

System Programmer Response: Check that sufficientstorage is available for the task. All sockets may be inuse.

Source File: svc_udp c, cmiucsoc c

Procedure Name: svcudp_bufcreate(), socket()

trouble replying to prog number

Severity: Fatal.

Explanation: An error was encountered replying to aremote procedure. The program exits.



System Programmer Response: Check for a badpointer. Check whether the task has adequate storage.

Source File: svc_simp c, svc c

RPC Messages


Procedure Name: universal(), svc_sendreply()

xdr_array: out of memory

Severity: Fatal.

Explanation: An XDR function could not allocatesufficient memory.


User or Operator Response: Remove all unnecessarytasks to reclaim storage and restart task.

System Programmer Response: Determine whetherenough storage is available for the task.

Source File: xdr_arra c

Procedure Name: xdr_array(), mem_alloc()

xdr_bytes: out of memory

Severity: Fatal.



User or Operator Response: Remove unneeded tasksto free storage and restart task.

System Programmer Response: Determine whetherthere is enough storage for the task.

Source File: xdr c

Procedure Name: xdr_bytes(), mem_alloc()

xdr_reference: out of memory

Severity: Fatal.




System Programmer Response: Determine that thereis sufficient storage for the task.

Source File: xdr_refe c

Procedure Name: xdr_reference(), mem_alloc()

xdr_string: out of memory

Severity: Fatal.





Source File: xdr_str c

Procedure Name: xdr_string(), mem_alloc()

xdrrec_create: out of memory

Severity: Fatal.





Source File: xdr_rec c

Procedure Name: xdrrec_create(), mem_alloc()

xxx


Explanation: An attempt was made to send a reply toan RPC call with a proc number of 0 (echo). Thisroutine enforces that the procnum 0 is echo convention.

System Action: The svc_sendreply() call failed. Theprogram exits.


System Programmer Response: Check for a badpointer. Check that storage is sufficient.

Source File: svc_simp c, svc c

Procedure Name: universal(), svc_sendreply()

RPCINFO MessagesThis section contains RPCINFO messages. For RPCINFO problems, PING andNETSTAT are important tools. You can use RPCINFO to check proceduresregistered on local and remote PORTMAPs. PING verifies that local and remotehosts are running with TCPIP. NETSTAT provides the status of socket connectionsand many other conditions.

RPC Messages


address { (unknown) | name }


Explanation: The indicated address responded to abroadcast. This is not an error message. A sample ofthis message is:

9.9.9.9 VMXX.RALEIGH.IBM.COM9.9.9.10 (unknown)

System Action: The program continues. The programruns to completion.


Source File: RPCINFO C

Procedure Name: reply_proc()

No remote programs registered.


Explanation: No remote programs have beenregistered on the Portmapper to be retrieved byRPCINFO.

System Action: RPCINFO continues.

User or Operator Response: Start a server thatregisters a procedure on the Portmapper.


Procedure Name: pmapdump()

program number version version ready and waiting


Explanation: The indicated program is ready.

System Action: RPCINFO continues execution.




program vers proto port


Explanation: A list of programs registered on thechosen Portmapper, with version protocol and portinformation, follows this message.





rpcinfo: broadcast failed: ReturnCode

Severity: Fatal.

Explanation: RPCINFO encountered an error issuing abroadcast.

System Action: RPCINFO exits.

User or Operator Response: Use err in the message todetermine the probable cause. There are multiple,possible return codes.


Procedure Name: brdcst(), clnt_broadcast()

rpcinfo: can’t contact portmapper: rpcinfo ReturnCode

Severity: Fatal.

Explanation: RPCINFO encountered an errorestablishing a TCP connection to Portmapper.


User or Operator Response: Correct the problemidentified in the error response. A typical error is thatthe Portmapper is not running on the host. StartPORTMAP. PING the host to determine thatPortmapper is running and available on the network.


Procedure Name: pmapdump(), clnt_call() brdcst(),clnt_broadcast()

rpcinfo: host is unknown host

Severity: Fatal.

Explanation: You specified an unrecognized host onthe RPCINFO command line. The name server may bedown. The host name may have been changed toanother net. The HOSTS LOCAL, HOSTS ADDRINFO,or HOSTS SITEINFO files may be incorrect. You mayneed to run MAKESITE.


User or Operator Response: PING the host.Determine whether the host name is correct andwhether the name server is running.

System Programmer Response: Make any necessarychanges to the HOSTS LOCAL file and run MAKESITE.


Procedure Name: get_net_address() udpping(),socket() udpping(), tcpping()

rpcinfo: service is unknown service


Explanation: The program number specified on thecommand line does not correspond to a known service.

RPC Messages



User or Operator Response: Correct the programnumber. Verify that the server is running and that itregisters the correct number. Rerun.


Procedure Name: getprognum(), getrpcbyname()

rcpinfo: socket

Severity: Fatal.

Explanation: RPCINFO encountered an error openinga UDP socket for PING.


User or Operator Response: Retry. for socket()parameters. Check for a memory constraint. Checkwhether TCPIP is running locally or remotely.


Procedure Name: udpping(), socket()

Usage: rpcinfo [ -n portnum ] -u host prognum [versnum ] rpcinfo [ -n portnum ] -t host prognum [versnum ] rpcinfo -p [ host ] rpcinfo -b prognumversnum


Explanation: The command line syntax is displayed toindicate that the user invoked RPCINFO with invalidarguments.


User or Operator Response: Reenter RPCINFO withthe correct control parameter syntax.


Procedure Name: usage()

RPCGEN MessagesThis section contains RPCGEN messages.

command: file ReturnCode

Severity: Fatal.

Explanation: RPCGEN encountered the indicated erroropening this file.

System Action: RPCGEN exits.

User or Operator Response: See the TCP/IPProgrammer’s Reference to determine the status of the filerelative to the error code; tcperror codes are shown intcperrno.h. Correct and restart.

Source File: RPCMAIN C

Procedure Name: open_input()

command: output would overwrite file

Severity: Fatal.

Explanation: The specified output file wouldoverwrite the input file. You must choose an output filename different from the input file name.


User or Operator Response: Change the output filename and restart.


Procedure Name: open_output()

command: unable to open file ReturnCode

Severity: Fatal.

Explanation: RPCGEN was unable to open the outputfile.


User or Operator Response: Determine from the errorcode why the file is unavailable. Possible reasonsinclude: missing, out of memory, and wrong pointer.


Procedure Name: open_output()

line file, line number: array declaration expected

Severity: Fatal.

Explanation: TCP/IP expected an array declaration atthis line of the source file.


User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.

System Programmer Response: Correct the program.

Source File: RPCPARSE C

Procedure Name: get_declaration()

line file, line number: constant or identifier expected

Severity: Fatal.

Explanation: TCP/IP expected a constant or identifierat this point in the source file.

RPC Messages


System Action: RPCGEN exits


Source File: RPCSCAN C

Procedure Name: scan_num()

line file, line number: definition keyword expected

Severity: Fatal.

Explanation: RPCGEN expected a definition keywordat this point in the source file.


User or Operator Response: Correct the source fileand restart.


Procedure Name: get_definition()

line file, line number: expected type specifier

Severity: Fatal.

Explanation: TCP/IP expected a type specifier at thispoint in the source file.





Procedure Name: get_type()

line file, line number: expected type specifier

Severity: Fatal.

Explanation: TCP/IP expected a type specifier at thispoint in the source file.






line file, line number: illegal argument type

Severity: Fatal.

Explanation: TCP/IP encountered an illegal argumenttype, opaque, on this line of the source file.

System Action: RPCGEN exits

User or Operator Response: Correct the source andrestart.


Procedure Name: def_program()

line file, line number: illegal character in file

Severity: Fatal.

Explanation: TCP/IP encountered an illegal characterin the source file.





Procedure Name: get_token()

line file, line number: illegal result type

Severity: Fatal.

Explanation: TCP/IP encountered an illegal resulttype, opaque, on this line of the source file.


User or Operator Response: Correct the source fileand restart.


Procedure Name: def_program()

line file, line number: no array-of-pointer declarations --use typedef

Severity: Fatal.

Explanation: TCP/IP encountered an illegalarray-of-pointer declaration at this line in the sourcefile. RPCGEN does not allow arrays of pointers, butthey can be implemented by means of typedef.


User or Operator Response: Do a typedef of thearray-of-pointers, or tell the system programmer aboutthe error.

System Programmer Response: Do a typedef of thearray-of-pointers and restart.



RPC Messages


line file, line number: preprocessor error

Severity: Fatal.

Explanation: TCP/IP encountered a preprocessor errorwhile searching for the null at the end of the numberand spaces. A non-null was found at the end of thenumber and spaces.





Procedure Name: docppline()

line file, line number: unterminated string constant

Severity: Fatal.

Explanation: TCP/IP encountered an unterminatedstring constant. The string must be terminated with anull character (\0 or X'00'). The program could beoverwriting data.



System Programmer Response: Examine the programdata for an unterminated string or a bad pointer.Correct the program.


Procedure Name: findstrconst()

line file, line number: variable-length array declarationexpected

Severity: Fatal.

Explanation: TCP/IP expected a variable-length arraydeclaration at this point in the source file.


User or Operator Response: Correct the inputprogram and restart, or tell the system programmerabout the error.

System Programmer Response: Correct the inputprogram.



line file, line number: voids allowed only inside unionand program definitions

Severity: Fatal.

Explanation: TCP/IP encountered an inappropriate

void type at this line in the source file.






too many files!

Severity: Fatal.

Explanation: The number of open files exceeds themaximum permitted. The maximum number of filesallowed is currently defined as 4. The programdepends upon C to clear the variable nfiles to zero. If Cdoes not clear nfiles to 0, the message occursunpredictably.

System Action: If the message appears, RPCGENexits.


System Programmer Response: If the compiler doesnot provide a reset to nfiles, add a software reset tonfiles.

Source File: RPCUTIL C

Procedure Name: record_open()

usage: command in_fn in_ft [in_fm] command[-c | -h | -l | -m][-o fn ft fm][in_fn in_ft [in_fm]] command[-s udp | tcp]*$& [in_fm]]


Explanation: The command line syntax was incorrect;the correct command line syntax is displayed. Commandis replaced by the name of this program, RPCGEN,unless the file name of the executable was changed.


User or Operator Response: Correct the syntax andrestart.


Procedure Name: main()

RPC Messages


Chapter 13. REXEC and REXECD Messages

This chapter contains REXEC and REXECD messages.

REXEC Messages

Command timed out

Severity: Error.

Explanation: The time-out timer has expired and theconnection has been closed.

System Action: REXEC halts.

User or Operator Response: Determine the reason thismessage was issued and correct the problem beforecontinuing.

Source File: REXEC PASCAL

Procedure Name: RECV_NOTICES

Error:

Severity: Error.

Explanation: The DataDelivered procedureencountered an error condition. This message can befollowed by a specific message output line for eachbuffer character error encountered thereafter.





Error: bad character

Severity: Error.

Explanation: The DataDelivered procedureencountered a specific error. The message lists anerroneous buffer character for each error at the end ofthe message.





Host foreignhost Unknown.

Severity: Error.

Explanation: The requested foreign host is unknownto this host. This message means that the requested

foreign host is not listed in the search table defined tothis REXEC session.


User or Operator Response: Determine the reason forthis failure, correct it, and rerun the program.


Procedure Name: UTSTARTTELNETINIT

Logon prompting disabled, quitting application.

Severity: Error.

Explanation: The -k option has disabled prompts foruser name and password values and no NETRC DATAfile entry was found that matches the host specified aspart of your command.


User or Operator Response: Ensure the NETRC DATAfile contains an entry for the target host when the -koption is used. If you wish to be prompted for a username and password, omit this option when the REXECcommand is issued.


Procedure Name: GETPARM

-p option requires one parameter: <passwd>

Severity: Error.

Explanation: An option parameter was missing fromor invalid in the -p option.


User or Operator Response: Input a valid passwordwith the -p option when you rerun the program. Donot include the angle brackets (< >) as part of yourinput.



rexec: no command given.

Severity: Error.

Explanation: The command input was null.



User or Operator Response: Input a valid REXECcommand when you rerun the program.



rexec: No foreign hostname given.

Severity: Error.

Explanation: The foreign host name input was null.


User or Operator Response: Input a valid foreign hostname when you rerun the program.



-s option requires one parameter: <port>

Severity: Error.

Explanation: An option parameter was missing fromor invalid in the -s option.


User or Operator Response: Input a valid port IDwith the -s option when you rerun the program. Do notinclude the angle brackets (< >) as part of your input.



-t option requires one parameter: <seconds>

Severity: Error.

Explanation: An option parameter was missing fromor invalid in the -t option.


User or Operator Response: Input a valid time-outwith the -t option when you rerun the program. Do notinclude the angle brackets (< >) as part of your input.



tcpwaitsend: ReturnCode

Severity: Error.

Explanation: A nonzero return code was returnedfrom a tcpwaitsend call.


User or Operator Response: Determine if a networkproblem exists before you rerun the program.


Procedure Name: REXEC_UTIL

timeout is not a valid number of seconds

Severity: Error.

Explanation: You have entered a time-out value that isnot valid. The time-out value must be a number withinthe following time-out range: greater than or equal tozero and less than or equal to 9999999.


User or Operator Response: Input a valid time-outwith the -t option when you rerun the program.



Unable to open passive port for host foreignhost

Severity: Error.

Explanation: A possible network or hardware problemexists.





Unable to open port TCP_REXEC to host foreignhost

Severity: Error.

Explanation: A possible network or hardware problemexists.





Unknown option option

Severity: Error.

Explanation: You input an invalid option, which islisted at the end of the message.


User or Operator Response: Input a valid optionwhen you rerun the program.



REXEC Messages


REXECD Messages

after 30 secs, rc ReturnCode

Severity: Warning.

Explanation: This is the second line of the messagedisplayed to warn you that the listed user ID could notbe autologged for any system. This line in the messageexplains that the 30-second time-out has expired, and itlists the CP return code reason for the time-out.


User or Operator Response: Determine the cause ofthis problem and correct it before continuing.

Source File: RXMAIN C


Cannot execute the following command; commandrc=returncode >> <command_string>

Severity: Error.

Explanation: The listed command could not beexecuted for the reason listed in the return code.




Procedure Name: FILL_CONN_STRUCT

command cannot be executed

Severity: Error.

Explanation: The listed command could not beexecuted.


User or Operator Response: Determine the reasonthat this message was issued and correct the problembefore continuing.



Diag 0x084 returns: cc=cc rc=returncodeUser ID: userid Password: passwword

Severity: Error.

Explanation: You entered an erroneous user ID orpassword combination that caused diagnose 0x084 tofail with the listed nonzero condition and return codes.


User or Operator Response: Enter a correct user IDand password.


Procedure Name: CHECK_PWD

Diag 0x08 returns: rc=returncodeFor command: command_string

Severity: Error.

Explanation: The diagnose 0x08 failed with the listednonzero return code from an attempt to issue a CPcommand.


User or Operator Response: Review the diagnosereturn code to determine why the diagnose 0x08command failed.


Procedure Name: CP

Error in TCP receive - - ReturnCode

Severity: Error.

Explanation: A call to the tcpreceive procedureresulted in a nonzero return code.

System Action: REXECD halts.

User or Operator Response: Check and correct anynetwork problems before you resubmit this taskrequest.

Source File: RXUTILS C

Procedure Name: STDREAD

Error in TCP send retcode ReturnCode

Severity: Error.

Explanation: A call to the tcpsend procedure resultedin a nonzero return code. A return code and relatedreason text are listed at the end of the message.




Procedure Name: STDWRITE

Error in TCP Wait receive - - ReturnCode

Severity: Error.

Explanation: A call to the tcpwaitreceive procedure

REXECD Messages

Chapter 13. REXEC and REXECD Messages 193

resulted in a nonzero return code.




Procedure Name: WATREAD

Error: Unknown NETSTAT command, type

Severity: Error.

Explanation: The command was not a knownNETSTAT command. The following are valid NETSTATcommands:v CP v CONNv UP v ALLCONNv DROP v CLIENTSv GATE v DEVLINKSv HOME v SOCKETv TELNET v POOLSIZEv ALL v INTERVAL


User or Operator Response: Submit a valid NETSTATcommand.


Procedure Name: NETSTAT_CMD

Error: Unknown option: option

Severity: Error.

Explanation: You made a syntax error in your input,or you requested an invalid option. The invalid optionargument is listed at the end of the message. The validoptions are: -s, -t, -e, -h, -d, -r, and -?

System Action: After this message is displayed, theprogram halts with a return code of 1.

User or Operator Response: Correct the input syntaxand try again.


Procedure Name: GET_OPTS

Failure on call to: getidentity

Severity: Error.

Explanation: This message is the first line of an errormessage that indicates that a call to the cgetidentityprocedure resulted in a nonzero return code.





Incorrect password

Severity: Error.

Explanation: You entered an incorrect password.


User or Operator Response: Enter the correctpassword for the requested user ID.



Incorrect userid/password

Severity: Error.

Explanation: You entered an incorrect user ID orpassword combination. Your logon request was denied.


User or Operator Response: Enter a correct user IDand password combination.



Invalid password

Severity: Error.

Explanation: You entered an invalid password.


User or Operator Response: Enter the valid passwordfor the requested user ID.



MSG machine name Remote Execution Daemonshutdown

Severity: Warning.

Explanation: The CP MSG facility on the host sendsthis message to warn agent machines that REXECD isshutting down.


User or Operator Response: You cannot use REXECDuntil the program is restarted.



REXECD Messages


No agent machines are available at this time.

Severity: Error.

Explanation: No agent machines are available forprocessing REXECD requests.




Procedure Name: XVM_N_SEND

REXEC port number is not valid. Using defaultREXEC port: 512

Severity: Warning.

Explanation: You entered a port number less thanzero.

System Action: The program uses the default REXECport and continues processing.




GENDELIV MODULE not accessible

Severity: Warning.

Explanation: A required part of the executables forREXECD does not reside on any of the VM minidisksaccessed by the program driver.


User or Operator Response: Ensure that theGENDELIV component is on an accessed minidiskbefore you resubmit this task request.



Received a catastrophic error from the client:OPENrejected Recycling REXECD

Severity: Error.

Explanation: The REXECD server attempted to open adata connection with a remote client, but its attemptwas rejected.

System Action: The REXECD server reinitializes itselfbecause the rejected connection can prohibit the serverfrom responding to additional client requests.




Shutting down due to notification from TCP/IP

Severity: Warning.

Explanation: The REXECD server received anotification from the TCP/IP stack server to stopprocessing because the TCPIP server itself isperforming shutdown processing.

System Action: The REXECD server performsshutdown processing.




Tcpwrite failed on conn conn

Severity: Error.

Explanation: A nonzero return code was returnedfrom a call to tcpwrite on the listed connection.


User or Operator Response: Investigate possiblenetwork problems before you resubmit the task.



WAITDEV MODULE not accessible

Severity: Warning.

Explanation: A required part of the executables forREXECD does not reside on any of the VM minidisksaccessed by the program driver.


User or Operator Response: Ensure that theWAITDEV MODULE is on an accessed minidisk beforeyou resubmit this task request.



RSH port number is not valid. Using default RSHport: 514

Severity: Warning.

Explanation: You entered a port number less thanzero.

System Action: The program uses the default RSHport and continues processing.




REXECD Messages


The -e option requires one parameter: <port_number>

Severity: Error.

Explanation: A port number was not provided withthis option.

System Action: REXECD halts with a return code of 1.

User or Operator Response: Reissue the commandproviding an appropriate port number.



The -h option requires one parameter: <port_number>

Severity: Error.

Explanation: A port number was not provided withthis option.


User or Operator Response: Reissue the commandproviding an appropriate port number.



The -s option requires one parameter: <userid>

Severity: Error.

Explanation: You made a syntax error in your input.


User or Operator Response: Correct the input syntaxfor the agent service machine and try again.



The -t option requires one parameter: <time_out>

Severity: Error.

Explanation: You made a syntax error in your input.


User or Operator Response: Correct the input syntaxfor the connection time-out value and try again.



Tcp active open failed -- rc ReturnCode

Severity: Warning.

Explanation: A call to the ctcpwatopen procedureresulted in a nonzero return code after the number ofactive connect attempts exceeded the (actlclport variable)maximum allowable value of 1024. The program halts

after the indication of this error has been echoed to theremote user. A return code and the related reason textare listed at the end of this message.


User or Operator Response: Check for and correctany network problems before resubmitting this taskrequest.


Procedure Name: ACT_OPEN

TCPCLOSE failed, rc ReturnCode

Severity: Warning.

Explanation: The listed nonzero return code wasreturned from a call to tcpclose for an activeconnection.


User or Operator Response: Investigate possiblenetwork problems before you resubmit the task.


Procedure Name: CLOSE

Tcp open failed -- rc ReturnCode

Severity: Warning.

Explanation: A call to the ctcpopen procedure resultedin a nonzero return code. A return code and relatedreason text are listed at the end of the message.




Procedure Name: PASS_OPEN

Timeout value is not valid; Using default value: 240seconds

Severity: Warning.

Explanation: You have entered a time-out value lessthan zero. In this case, the program uses the defaulttime-out value and continues processing.





REXECD Messages


Timer Expired: Connection Closed

Severity: Error.

Explanation: A timer has expired and the connectionhas been closed.





Unable to Autolog machine name

Severity: Warning.

Explanation: REXECD could not autolog the agentmachine.


User or Operator Response: Log or force off the agentmachine before continuing.



Unable to autolog user UserID

Severity: Warning.

Explanation: The listed user ID could not beautologged with the RXSNDIU EXEC for any system.





Unable to communicate with user UserID

Severity: Warning.

Explanation: The system was unable to communicatewith the listed user ID.


User or Operator Response: The remote user shoulddetermine the reason that this message was issued andcorrect the problem before continuing.



Unable to open active connection

Severity: Warning.

Explanation: There was a ctcpwatopen failure.


User or Operator Response: Check for and correctany network problems before he resubmits this taskrequest.


Procedure Name: ACT_OPEN

Unknown notification, <notice->notetype>

Severity: Error.

Explanation: This is an informational message issuedby the prtnotice procedure for the default case whennone of the other, previous valid cases were found.




Procedure Name: PRTNOTICE

REXECD Messages


REXECD Messages


Chapter 14. ROUTED Messages

This section contains the messages for the RouteD server.

DTCRTD4820I VM TCP/IP RouteD server functionlevel

Explanation: This message indicates the function levelof the RouteD server.

System Action: RouteD continues.



DTCRTD4823I Tracing debug packets actiontimestamp

Explanation: Debug packets tracing is enabled ordisabled. The packets are displayed in data format.




DTCRTD4825S name/udp

Explanation: A UDP port number for the routerservice name was not resolved in the PROFILE TCPIPfile.

System Action: RouteD ends abnormally.


System Programmer Response: Verify that a UDPport has been reserved for RouteD using the PORTstatement in PROFILE TCPIP.

DTCRTD4826S Terminating since clients require asocket

Explanation: RouteD attempted to open a socket on awell-known port (specified in the PROFILE TCPIP file)but the open was not successful, or the socket couldnot be bound to an internet address and port number.Other routers will not be able to communicate withRouteD because a socket is unavailable; Therefore,RouteD will shut down.



System Programmer Response: Verify that anotherprogram is not using RouteD’s port and that the porthas been reserved in the PORT statement of PROFILETCPIP file.

DTCRTD4827S Usage: RouteD (Input parameters)

Explanation: RouteD was passed parameters that arenot supported or were not formatted correctly.



System Programmer Response: Correct theparameters and separate them with spaces. Refer toTCP/IP Planning and Customization for moreinformation.

DTCRTD4828I Input parameter(s): parameter

Explanation: This message displays the inputparameters supplied to the RouteD server by the user.




DTCRTD4829I Waiting for incoming packets

Explanation: RouteD is waiting for datagrams toarrive from other routers. Each time RouteD finishesprocessing an event such as an incoming datagram or atimer that expires, it issues this message and waits forthe next event. These messages should occur at leastevery 15 seconds.

System Action: Processing is suspended until a timerexpires or a datagram arrives from another router.


System Programmer Response: If 6 or more of thesemessages occur consecutively, RouteD is not receivingany datagrams from other routers. Verify that anotherrouter is active on a directly connected network. If so,examine the status of the appropriate network interface.

DTCRTD4830E The main select was interrupted

Explanation: An error was detected while RouteD waswaiting for an event to occur. A subsequent messagewill be issued with more error information.



System Programmer Response: Verify that TCPIP isrunning.


DTCRTD4831I Send delayed dynamic update

Explanation: A routing update that was delayed toprevent packet storms has been transmitted. Thisoccurs 2–5 seconds after a dynamic update has beenissued.




DTCRTD4832E While receiving a packet

Explanation: An error occurred while attempting toreceive a packet from a client. The incoming packet isdiscarded. A subsequent message will be issued withmore error information.



System Programmer Response: Refer to the next errormessage issued and correct the error.

DTCRTD4833S A socket could not be created

Explanation: RouteD could not open a new socket. Asubsequent message will be issued with more errorinformation.



System Programmer Response: Verify that TCPIP isactive, that another program is not using the RouteD’sport, and that the port has been reserved in the PORTstatement of PROFILE TCPIP file.

DTCRTD4834S Broadcasting cannot be enabled onsocket socket

Explanation: RouteD cannot enable the socket forbroadcasting. RouteD must be able to broadcast overinterfaces that support broadcasting to communicatewith other routers.



System Programmer Response: Contact your IBMSoftware Support Center.

DTCRTD4835S The socket bind failed

Explanation: RouteD was unable to associate aninternet address and port number with the newlycreated socket. This might be because anotherapplication is using the port.



System Programmer Response: Verify that no otherapplication is using the router port. Use the netstatsocket command and look to see if RouteD is bound to520. You should reserve this port for RouteD’s exclusiveuse by adding an entry to the PORT statement in thePROFILE TCPIP file.

DTCRTD4836E function: socket create failed

Explanation: RouteD was unable to obtain a socket fortemporary use by function while initializing interfacesor obtaining interface information from TCPIP’sinterface tables. A subsequent message will be issuedwith more error information.




DTCRTD4837E ioctl (get interface configuration)

Explanation: RouteD encountered an error whileattempting to obtain the network interfaceconfiguration. A subsequent message will be issuedwith more error information. The most likely error isENOBUFS, which indicates an internal TCPIP problem.The interface in error is skipped.




DTCRTD4838E interface: ioctl (get interface flags)

Explanation: RouteD encountered an error whileobtaining the interface flags for interface. A morespecific message follows, which indicates the errorreturned from the ioctl. The interface is skipped.



System Programmer Response: If the error isENOENT, verify that a BSDROUTINGPARMSstatement is in the PROFILE TCPIP file.

DTCRTD4839E interface: ioctl (get destinationaddress)

Explanation: RouteD encountered an error whileattempting to obtain the destination address from thepoint-to-point interface interface. A subsequent messagewill be issued with more error information. Theinterface in error is skipped.



ROUTED Messages



DTCRTD4840E interface: ioctl (get broadcast address)

Explanation: RouteD encountered an error whileattempting to obtain the broadcast address for interfaceinterface. A subsequent message will be issued withmore error information. The interface is skipped.




DTCRTD4841E interface: ioctl (get metric)

Explanation: RouteD encountered an error whileobtaining the metric for interface interface. A subsequentmessage will be issued with more error information.The metric for the interface is set to zero.




DTCRTD4842W Ignoring incorrect metric oninterface interface

Explanation: An incorrect metric value was specifiedfor this interface in the BSDROUTINGPARMSstatement. The default metric of 0 (zero) is used.



System Programmer Response: Specify a correctmetric value in the range from 0 to 15.

DTCRTD4843E interface: ioctl (get netmask)

Explanation: RouteD encountered an error whileobtaining the subnet mask for interface. A subsequentmessage will be issued with more error information.The interface in error is skipped.




DTCRTD4844S Function function out of memory

Explanation: RouteD is unable to allocate the freestorage needed to process an interface.



System Programmer Response: Increase the VirtualMachine storage and restart RouteD.

DTCRTD4845W entry

Explanation: A warning is about to be issued for theindicated entry in the ETC GATEWAYS file. Asubsequent message will be issued with more errorinformation.



System Programmer Response: Correct the ETCGATEWAYS file.

DTCRTD4846E entry

Explanation: An error is about to be issued for theindicated entry in the ETC GATEWAYS file. Asubsequent message will be issued with more errorinformation.




DTCRTD4847W Second element ignored, changingto 'active'

Explanation: The second element in the activegateway entry was detected as not valid. This suggeststhat a configuration error might have occurred. RouteDwill assume the gateway entry is an active gateway.The second element is changed to “active”.




DTCRTD4848E Gateway type ‘type’ incorrect foractive gateway

Explanation: An active ETC GATEWAYS entry has aroute type other than “active”. ETC GATEWAYS entriesclassified as active must have a route type of “active”.The ETC GATEWAYS entry is ignored.




ROUTED Messages

Chapter 14. ROUTED Messages 201

DTCRTD4849I RouteD Server started

Explanation: RouteD has completed initialization ofnetwork interfaces with direct routes and is ready toprocess RIP packets for IP dynamic routing. Any routesdefined in the ETC GATEWAYS file have also beenprocessed.




DTCRTD4850I Processing interface interface

Explanation: The indicated interface was found inTCPIP’s interface table and is being added to RouteD’sinterface table.




DTCRTD4851E First two elements must be ‘active’for active gateway

Explanation: A ETC GATEWAYS entry for thegateway definition has a route type of “active”, but thefirst two elements are not defined as active, as requiredfor an active gateway definition. The ETC GATEWAYSentry is ignored.




DTCRTD4852E Incorrect gateway type ‘type’

Explanation: The ETC GATEWAYS entry for thegateway definition has a gateway type that is not valid.Valid gateway types are: active, external, permanentand passive. The ETC GATEWAYS entry is ignored.




DTCRTD4853E packet from unsupported addressfamily family, cmd command

Explanation: A RIP packet was received by RouteDfrom a foreign router in an unsupported address family.Only the internet address family is supported. Thepacket is ignored.



System Programmer Response: Ignore the error orlocate the foreign router that originated theunsupported RIP packet and have it stopped.

DTCRTD4854E RIP version 0 packet received fromrouter! (cmd command)

Explanation: A RIP Version 0 packet was receivedfrom the specified router. This version of RIP isobsolete and not supported by RouteD. The Version 0packet is discarded.



System Programmer Response: Correct the router thatis sending the version 0 packets.

DTCRTD4855W trace command from unknownrouter router

Explanation: A TRACEON or TRACEOFF packet wasreceived from a router that is either not directlyattached, is reached using a passive interface, or isreached using an interface that cannot handle broadcastor point-to-point traffic. The packet is discarded.



System Programmer Response: If the originatingrouter directed the packet using a passive link, anindirect path, or an interface that cannot handlebroadcast or point-to-point traffic, then correct theoriginating router.

DTCRTD4856W Incorrect packet from passiveinterface interface

Explanation: RouteD has received a response packetfrom local passive interface interface. Although RouteDreceives routing updates from a client for passiveinterfaces, it cannot produce the routing updates. Thepacket is discarded.



System Programmer Response: Locate the router thatis producing the incorrect response packet and correctthe problem.

DTCRTD4857W Packet from unknown router ipaddr(reason)

Explanation: A Routing Information Protocol (RIP)response was received from a router that is not directlyconnected by a broadcast network, point-to-point(NCST) network, or an active gateway as defined inETC GATEWAYS file. The reason is one of:

ROUTED Messages


Reason Explanation

Interface in strange state The network does notsupport broadcast orpoint-to-pointtransmissions.

Iflookup failed Not directly connected.this Link is PASSIVE! Cannot update.

The packet is discarded.



System Programmer Response: Locate and correct therouter that originated the packet.

DTCRTD4858W route from router in unsupportedaddress family family

Explanation: An incoming route from another routeris in an address family that is not supported byRouteD. Only internet addresses are supported. Theroute is ignored.



System Programmer Response: Locate and correct therouter that originated the route.

DTCRTD4859E Illegal address host in route fromrouter

Explanation: An internet address that is not valid wasreceived in an update from router router. A previousmessage indicates the nature of the problem with theaddress. The route that is not valid is discarded.



System Programmer Response: Locate and correct therouter that originated this route.

DTCRTD4860W Bad metric metric in route todestination from router

Explanation: A route was received from routercontaining a metric that was not in the range 1–16. Theroute is ignored.



System Programmer Response: Locate and correct therouter that originated this route.

DTCRTD4861I Send dynamic update

Explanation: Changes to the routing tables haveoccurred and enough time has passed since the lastupdate so RouteD is allowed to update adjacent routersimmediately rather than waiting until the nextbroadcast timer expires. Dynamic updates are not madeif they occur too soon after another update, becausenetwork performance might be affected if anotherdynamic update is pending.




DTCRTD4862I Delay dynamic update

Explanation: Changes have been made to RouteD’srouting tables, but a dynamic update cannot be madebecause another update occurred recently or ispending. When the last update was made, a timer wasset for 2–5 seconds from that time. When this timerexpires, all pending dynamic updates are sent.




DTCRTD4863I Inhibit dynamic update for numberseconds

Explanation: A dynamic update has been sent. Furtherdynamic updates will not be sent during the next 2–5seconds.




DTCRTD4864E inet_output: sendto destinationdestination

Explanation: An error occurred while attempting totransmit a packet. The packet is not sent. A subsequentmessage will be issued with more error information.



System Programmer Response: Refer to the next errormessage and correct the error.

DTCRTD4865E Trace buffers not initialized forinterface interface

Explanation: One or both of the trace buffers for thespecified interface could not be initialized. Tracing islimited.


ROUTED Messages



System Programmer Response: Increase the VirtualMachine size for RouteD and restart.

DTCRTD4866I Tracing action timestamp

Explanation: Tracing is enabled or disabled.




DTCRTD4867I Displaying internal type table

Explanation: RouteD’s internal IP routing or interfacetable is displayed for diagnosis.




DTCRTD4868I Tracing actions action timestamp

Explanation: The current tracing level of actions hasbeen either enabled or disabled. If enabled, messageswill be issued for actions such as adding, changing, ordeleting a route. Additional messages for actions suchas waiting for incoming packets and dynamic updatesare also issued.




DTCRTD4869I Tracing packets action timestamp

Explanation: The current tracing level of packets haseither been enabled or disabled. If enabled, messageswill be issued for packets sent and received, in additionto the output displayed for the actions level.




DTCRTD4870I Tracing history action timestamp

Explanation: The current tracing level of history haseither been enabled or disabled. If enabled, messageswill be issued for history tracing data on a per-interfacebasis, in addition to output displayed for the packetslevel. The history tracing data is displayed wheneveran interface becomes inactive. It shows the latest tracesof actions, packets, and packet contents before theinterface became inactive.




DTCRTD4871I Tracing packet contents actiontimestamp

Explanation: The current tracing level of packetcontents has either been enabled or disabled. Ifenabled, messages will be issued that display thecontents of packets sent or received, in addition tooutput displayed at lower tracing levels. Additionalmessages such as 4903 and 4904 are also issued.




DTCRTD4882I timestamp:

Explanation: A full time stamp is issued showing dateand time so that traces can be interpreted correctly.




DTCRTD4883I action destination destination, routerrouter, metric metric flags flags state statetimer timer

Explanation: A route to destination is added, changed,or deleted depending on the value of action. Thefollowing values for action are allowed:

Value Description

ADD: A route to destination is addedthrough router at a metric of metric.

CHANGE FROM: The route to destination is changed,the old values are displayed.

CHANGE TO: The route to destination is changed,the new values are displayed.

DELETE: The route to destination is deleted.




DTCRTD4884E rtadd: incorrect address family

Explanation: An attempt is being made to add a routeto a destination in an unsupported address family.Currently, RouteD only supports routes to Internetaddresses.

System Action: RouteD continues, the route is notadded.

ROUTED Messages



System Programmer Response: Identify the routerwhich generated this route and correct the problem.

DTCRTD4885W * Variable subnetting not supportedin TCPIP

Explanation: RouteD has been configured to usevariable subnetting (RIP version 2), but the currentTCPIP stack is not configured to support variablesubnetting.

System Action: RouteD continues

User or Operator Response: Either reconfigureRouteD to use only RIP version 1 or configure theTCPIP stack to support variable subnetting. Variablesubnetting can be enabled in the stack by addingVARSUBNETTING to the ASSORTEDPARMSstatement.

System Programmer Response: none

DTCRTD4888I Interface interface is passive

Explanation: The interface is in a passive state,meaning that RIP traffic is disabled for the it. Routingupdates will not be broadcast to the interface andincoming routing updates are ignored. This may be theresult of a RIP I/O filter option specified in the ETCGATEWAYS file.




DTCRTD4889I CHANGE metric destinationdestination, router router, from old metricto new metric

Explanation: The metric for the route to destination ischanged from old metric to new metric. RouteD willchange the metric if it has received a RIP packet fromrouter router that differs from the one in RouteD’stables. The message is also issued when a route timesout, and RouteD changes the metric value to 16(unreachable).




DTCRTD4890I toall: requested to skip interfaceinterface

Explanation: The interface interface is skipped becausethe interface has already received notification of arouting change. If a broadcast of the routing table hasnot been sent recently and a routing change hasoccurred, a dynamic routing update will be broadcast

to other interfaces to inform adjacent routers of therouting change.




DTCRTD4891I *** Packet history for interfaceinterface ***

Explanation: Tracing is set at the history level and thehistory trace data for the inactive interface is displayed.




DTCRTD4892I *** End packet history ***

Explanation: Tracing is set at the packet history leveland this message ends the history trace data for theinactivated interface.




DTCRTD4897I direction: no packets

Explanation: Either the input or output trace buffer,depending on the value of direction, is empty.




DTCRTD4898I direction trace

Explanation: Tracing is set at the history level andeither the input or output trace buffer is about to bedisplayed, depending on the value of direction.




DTCRTD4899I RIPcmd direction router -> port verversion timestamp

Explanation: A RIP datagram has been received fromor is about to be transmitted to another router,depending on the value of direction. A value of “to”indicates an outbound datagram, while a value of“from” indicates an inbound datagram. The version ofthe datagram is determined by the version. The type ofthe datagram is determined by the value of RIPcmd andone of the following:

ROUTED Messages


RIPcmd Description

REQUEST Indicates that the routing tableinformation is requested. Individualroutes or a complete routing tablemay be requested.

RESPONSE Indicates that the routing tableinformation is broadcast.

TRACEON Request to start tracing to a specifiedfile.

TRACEOFF Request to stop tracing and close thecurrent tracing file.

The value of port is either the port number on whichthe datagram came in or goes out, or if 0, indicates thatan outbound datagram will go out on the port assignedto router in the PROFILE TCPIP file.




DTCRTD4900S Bad cmd hex direction router–> portsize=size cp=cp packet=packettime=timestamp

Explanation: A malformed packet was encounteredduring tracing. The source of the packet is either routerif direction is “from”, or RouteD if direction is “to”.



System Programmer Response: If the source of thepacket is router, correct this router.

DTCRTD4901S (truncated record, len len)

Explanation: A RIP RESPONSE datagram wasreceived that did not end on a route boundary. Eitherthe packet extends beyond the last route or it has beentruncated.



System Programmer Response: Verify that theincoming packet was built correctly and can beprocessed by other routers.

DTCRTD4902I destination destination metric metric

Explanation: A route to destination with the indicatedmetric was advertised by another router or RouteD,depending on the contents of the last DTCRTD4899Imessage. A route is never advertised over the interfacefrom which it was received.




DTCRTD4903I (request for full tables)

Explanation: A request for a complete routing tablehas been sent or received, depending on the contents ofthe last DTCRTD4899I message. This request is sent byRouteD at startup over each interface so that RouteDcan obtain routing tables from all adjacent routers.




DTCRTD4904W Unknown address family (family)metric metric

Explanation: A route was found in the trace with anunknown address family.



System Programmer Response: If the route originatedfrom another router, locate that router and correct it.

DTCRTD4905I TraceOn file = file

Explanation: A TRACEON packet was received, tracedata is requested to go to file.




DTCRTD4909E Error adding route to destinationthrough router router, metric metric

Explanation: An error occurred while attempting toadd a route to destination. A subsequent message willbe issued with more error information.

System Action: RouteD continues, the route is notadded.


System Programmer Response: See DTCRTD4910E.

DTCRTD4910E function: SIOCADDRT ioctl failed

Explanation: RouteD was unsuccessful in adding anew route. The error occurred in the indicated functionand is one of the following:

Function Description

rtadd RouteD attempted to add a new routeto the TCP/IP IP routing table.

rtchange RouteD attempted to change themetric of a route in the TCPIP

ROUTED Messages


server’s IP routing table by deletingthe old route, then adding a new onewith the updated metric.

main RouteD attempted to get the TCPIPlevel during initialization.

A subsequent message will be issued with more errorinformation. Most likely the error is the result of anerror in an ETC GATEWAYS entry. Common errors are:

Error Description

EACESS RouteD is not authorized to addroutes to the TCPIP server’s IProuting table. Permission is granted toRouteD to manage the TCPIP server’sIP routing table, if the user ID of theRouteD virtual machine is specified inthe OBEY list (OBEY statement).

EEXIST The route already exists in TCP/IP’stables, because of a GATEWAYstatement, a dynamic addition by theRouteD server, or an error deletingthe route.

ENETUNREACHTCP/IP does not have a route to therouter (nexthop) for this route. Routesin the ETC GATEWAYS file musthave reachable routers.

ENOBUFS TCP/IP did not have a free IP RouteControl Block to add the route to therouting table.

ENOENT TCP/IP did not have a link interfacedefined for the route to be added to.

EINVAL An incorrect parameter has beenpassed to TCP/IP.

EOPNOTSUPP TCP/IP does not support therequested operation.

System Action: The route is not added. RouteDcontinues. If this occurs during initialization, thenRouteD ends abnormally.


System Programmer Response: These errors requirethe following responses:

Error Response

EACESS Make sure that the user ID of theRouteD virtual machine is correctlyspecified in the OBEY statement forTCP/IP configuration file (PROFILETCPIP).

EEXIST Clear the IP routing table beforerestarting the RouteD Server. AnOBEY file with the word GATEWAYremoves all routes.

ENOBUFS Increase IPROUTEPOOLSIZE inPROFILE TCPIP and restart TCP/IP.

ENETUNREACHCorrect the ETC GATEWAYS file, andeither add a route to the router orselect another router for this route.

ENOENT Define the link interface in theBSDROUTINGPARMS statement inthe PROFILE TCPIP. An obeyfile withthe BSDROUTINGPARMSdefinition(s) may be used to add thelink interface(s) to TCP/IP.

EINVAL Verify the validity of statements inthe ETC GATEWAYS file.

EOPNOTSUPP Verify that the statement“ASSORTEDPARMSVARSUBNETTING” appears in thePROFILE TCPIP.

DTCRTD4912E Error deleting route to destinationthrough router router, metric metric

Explanation: An error occurred while attempting todelete a route to destination. A subsequent message willbe issued with more error information.



System Programmer Response: Refer to theexplanations for the specific error messages displayedalong with this one.

DTCRTD4916I action route to interface interface(timed out)

Explanation: The route to interface is changed ordeleted depending on the value of action. The value“changing” indicates that interface will be deleted andthen added. The value “deleting” indicates that theroute to interface’s network or subnet will be deleted.The interface remains in RouteD’s interface list eventhough the route is deleted.




DTCRTD4918E function: SIOCDELRT ioctl failed

Explanation: RouteD was unsuccessful in deleting aroute. The error occurred in function, and is one of thefollowing:

Function Description

rtdelete RouteD attempted to delete a routefrom TCP/IP’s routing table.

rtchange RouteD needed to change a route, but

ROUTED Messages


TCP/IP does not allow routes to bechanged explicitly. Instead, RouteDattempted to delete the old route sothat a new route can be added withthe updated values.

rtdeleteall RouteD attempted to delete all routesfrom TCP/IP’s routing IP routingtable.

A subsequent message will be issued with more errorinformation. The most likely error is ESRCH, whichindicates that the route that is to be deleted does notexist in TCP/IP’s routing tables.

System Action: RouteD continues, the route is notdeleted.



DTCRTD4919I Using backup interface interface

Explanation: A primary interface became inactive anda secondary interface is serving as the backup.




DTCRTD4920I Add type route ignored, route existson interface interface

Explanation: A network, subnetwork, or destinationtype route already exists on an active interface. As ageneral rule, no more than one route can be defined toa single destination and a route is added to the firstavailable interface in the (sub)network according to theorder in the HOME statement of PROFILE TCPIP.




DTCRTD4921I Deleting route to interface interface?(timed out?)

Explanation: An interface route is being deleted eventhough the route exists in TCP/IP’s tables. Onepossible cause is that the route was deleted due to atimeout. Another reason for a deletion is if there is apassive route in the ETC GATEWAYS file when theroute is also defined in the BSDROUTINGPARMS orHOME section of PROFILE TCPIP.




DTCRTD4922I Option(s): options

Explanation: Additional RouteD options, specified inan ETC GATEWAYS file, are being processed. Refer toTCP/IP Planning and Customization for moreinformation.




DTCRTD4923E Invalid option: option

Explanation: The entry in the ETC GATEWAYS filehas an incorrect option. Although other options may beprocessed normally, the incorrect one is ignored.




DTCRTD4924I Re-installing interface interface

Explanation: The previously deleted interface is beingreinstalled because traffic has been detected over it.




DTCRTD4925I Start of ETC GATEWAYS processing

Explanation: The ETC GATEWAYS file is about to beprocessed. Processing messages may follow for theentries in the file.




DTCRTD4926I End of ETC GATEWAYS processing

Explanation: Processing has completed for the ETCGATEWAYS file.




DTCRTD4927W Specified metric not allowed,changing to metric

Explanation: In the line entry for the ETC GATEWAYSfile, the metric has a value that is not allowed. Therange of valid metric values is 0 through 15. The metricis changed to a default value of 1 if a zero was

ROUTED Messages


specified and is changed to 15 for any other value notin the valid range.




DTCRTD4928S Out of memory while processingETC GATEWAYS

Explanation: RouteD did not have enough storageavailable to process the ETC GATEWAYS file.



System Programmer Response: Increase the VirtualMachine storage size for RouteD and restart it.

DTCRTD4929I Port port assigned to name

Explanation: RouteD listens for traffic from otherrouters on the specified port number port assigned torouter service name.




DTCRTD4930I Packet from router router ignored(action)

Explanation: RouteD has been configured to ignorepackets from router router. Action action has beenapplied to its packets.



System Programmer Response: To use packets fromthe router specified, update the ETC GATEWAYS file(RIP input filter) to accept packets from this router.

DTCRTD4931W Ignoring route destination,supernetting not supported

Explanation: The route to destination received in theRIP packet is a supernet route and is ignored since thesupernetting feature is not enabled in TCPIP. Asupernet route is one whose subnet mask is less thanits network class mask.



System Programmer Response: Verify that theVARSUBNETTING option is coded in theASSORTEDPARMS statement in the PROFILE TCPIPfile.

DTCRTD4932I ****************************

Explanation: Two of these banners enclose a messagethat might need attention when viewing the output.



System Programmer Response: Read the enclosedmessage and, when necessary, resolve the indicatederror.

DTCRTD4933W Unable to open ETC GATEWAYS(filename)

Explanation: An ETC GATEWAYS file was notspecified, or could not be opened. The indicatedfilename is the one that RouteD attempted to open.



System Programmer Response: An ETC GATEWAYSfile is used to identify networks or hosts that are not ona directly connected network but are still accessiblethrough other gateways. Create an ETC GATEWAYSfile to make these routes known to the RouteD server.

Note: Only the first file in the search order that can beopened will be read to determine the gatewaystatements.

DTCRTD4934I Opening ETC GATEWAYS (filename)

Explanation: The ETC GATEWAYS file is beingopened.




DTCRTD4935S Incorrect parameter: parameter

Explanation: An incorrect parameter was passed toRouteD. The parameter could either be passed from thecommand line parameters or from the list in theDTCPARMS file.



System Programmer Response: Correct the commandline parameters or the list of parameters defined in theDTCPARMS file.

DTCRTD4936I Adding type route route destination viagateway gateway, metric metric

Explanation: The indicated route, defined in the ETCGATEWAYS file, is being added to RouteD’s routing

ROUTED Messages


table. The route to the gateway will not be replaced bya competing RIP route.




DTCRTD4937W Subnetwork mask unknown fordestination, using network route route

Explanation: The indicated subnetwork route, definedin the ETC GATEWAYS file, was explicitly coded as a“net” route type. Because the subnetwork mask for thedestination subnetwork is unknown, RouteD replacesthe subnetwork route with a network route. RouteDcurrently is not enabled for variable subnetting.




DTCRTD4938I Adding active gateway ip_addr, metricmetric

Explanation: An active gateway ip_addr with metricmetric, defined in the ETC GATEWAYS file, is beingadded to RouteD’s routing table. The route to the activegateway will be treated as a network interface.




DTCRTD4939S Trace levels exceeded maximum of 4

Explanation: The maximum number of -t’s that arepart of a valid request is 4 (-t-t-t-t). Each -t indicates anadditional level of tracing.


User or Operator Response: Specify a valid number of-t parameters for the trace request you would like.TCP/IP Planning and Customization describes the RouteDparameters.


DTCRTD4940I Point-to-point interface, usingaddrtype

Explanation: The new interface is point-to-point andthe destination address type, addrtype, can be either’dest_addr’ or ’broadaddr’. The address type isdetermined by the destaddr field definition for theinterface in the BSDROUTINGPARMS statement of thePROFILE TCPIP, which may be coded as zero ornonzero. If zero, the network or subnetwork-directedbroadcast address is used; otherwise, the unicast orhost address representing the other end of a

point-to-point link is used. This address is used forsending routing information over an interface to thedestination router or host.




DTCRTD4941I Interface interface skipped, interface ismulticast-incapable

Explanation: The interface is skipped because RouteDhas been configured with the RIP2 multicast option forthe interface, but TCPIP has reported that the interfacedoes not support multicast operation.



System Programmer Response: When permitted, usethe RIP2M supply control option to allow broadcastingRIP Version 1 packets over multicast-incapableinterfaces and multicasting Version 2 packets overmulticast-capable interfaces.

DTCRTD4942I Not an internal interface

Explanation: The new interface does not appear to beassociated with a real device. Most likely the interfaceis a pseudo-interface, created as a result of an activegateway definition in the ETC GATEWAYS file.




DTCRTD4943I Adding type route for interface

Explanation: The route using the network,subnetwork, or host type is being added to theinterface in RouteD’s routing table.




DTCRTD4944S Function function: address family isout of range. The address is address.

Explanation: The route to the destination address hasan unsupported address family. RouteD cannotdetermine the network based on the address. Therefore,it cannot determine an interface that serves the logicalnetwork.



System Programmer Response: Non-IP addresses arenot supported in this version of RouteD. Either ignore

ROUTED Messages


the message or have the router that originated the routestop sending non-IP addresses to this router. Look backthrough the output to find the last ADD or CHANGEfor this destination to obtain the IP address of therouter.

DTCRTD4945I ifwithnet: compare with value

Explanation: The route’s network address is beingcompared to one of RouteD’s interface entries for anetwork number match.




DTCRTD4946S ifwithnet: interface has bad addressfamily

Explanation: One of RouteD’s interface entries addressfamilies is not valid. RouteD cannot determine thenetwork based on the address, and cannot determinean interface that serves the logical network. AF_INET isthe valid address family for the internet domain.

System Action: TCPIP continues.


System Programmer Response: Either ignore themessage or correct the interface with a correct addressfamily. Change the address family to AF_INET. If thesocket address is in an internet addressing family, theaddressing family can be defined in the IN H headerfile.

DTCRTD4947I netmatch ipaddr1 and ipaddr2

Explanation: The network number for the first addressmatches the network address of the interface entry withthe second address.




DTCRTD4948I This interface is not point-to-point

Explanation: The interface RouteD is currentlyhandling is not a point-to-point interface. RouteD willcreate a route to the network for the interface.




DTCRTD4949I Interface interface not up

Explanation: RouteD determined that the indicatedinterface is not active. No routes will be added untilthe interface is activated or reactivated.




DTCRTD4950W Interface interface ignored

Explanation: The indicated interface address family isnot valid. The interface is ignored to prevent networkor subnetwork routes from being added.



System Programmer Response: Either ignore themessage or correct the interface with a valid addressfamily. A common cause of an interface with anincorrect address family is that the interface is omittedfrom the HOME statement in PROFILE TCPIP. Thismay be normal in the case where multiple interfacesare reserved for Offload processing but are not definedas primary interfaces (for example, thePRIMARYINTERFACE statement in PROFILE TCPIP.

DTCRTD4954I timer_value minute timer expired forroute to destination

Explanation: No Routing Information Protocol (RIP)packets have been received from RouteD for the routeto the destination destination in the last timer_valueminutes. It is assumed that the destination router is nolonger active.

System Action: Depending upon the timer_value, oneof the following actions is taken:

Value Action

3 The route will have its metric changed toinfinity for the next 2 minutes. The metricchange is necessary to alert adjacent routersthat the route to this destination isunreachable. If RouteD receives any RIPpackets from the destination router during thetwo minute interval, it will restore the routeby changing the metric to a valid one basedupon the received RIP packet.

5 The route will be deleted from RouteD’srouting table.


System Programmer Response: These actions requirethe following responses:

Value Response

3 If the route was broadcast for a while and then

ROUTED Messages


suddenly stopped, look for an adapterproblem or a problem with the physical line.

5 Examine RouteD trace output and determinewhen the broadcasting stopped for the routeto the destination router. If the route todestination was only broadcast once inresponse to RouteD’s request for full routetables, then the problem may be with the wayRIP packets are broadcast.

In these cases, determine if RouteD is receiving the RIPpackets by obtaining a UDP packet trace. This trace canalso confirm the lack of traffic for the route’s interface.Contact the IBM support center for assistance.

DTCRTD4955I Ignoring route destination, filtered out

Explanation: The specified destination route is beingfiltered out of the routing information in an outgoingRIP broadcast or a received RIP update. The destinationroute matches one of the RIP input and output filters,defined in the ETC GATEWAYS file, and is beingselected for removal from the routing information.




DTCRTD4956I Deleting interface interface_name

Explanation: RouteD is deleting the interface from itsinterface tables. The interface is unusable and may havebeen deleted via a new HOME list.




DTCRTD4957I timer_value second timer expired(reason)

Explanation: Depending upon the timer_value andreason, one of the following actions is taken:

Value Reason Action

30 broadcast Every 30 seconds, a timerexpires that indicates thatRouteD must broadcast itsrouting tables to adjacentrouters. At this time, RouteDwill send RIP responsepackets for each of itsinterfaces that allowbroadcasting to the adjacentrouters.

Value Reason Action

m rescan kernelfor interfaces

Every m seconds, a timerexpires that indicates thatRouteD must rescan theTCP/IP’s (kernel) interfacetable for any activated,reactivated, or deactivatedinterfaces. At this time,RouteD will add any newinterfaces to its interfacetable, recognize interfaceorder according to HOMEand PRIMARYINTERFACEstatements in PROFILETCPIP, or mark the interfaceas active or inactive. Inaddition, RouteD will addroutes for the activated orreactivated interfaces and ifnecessary, issue alerts(triggered updates) toadjacent routers fordeactivated interfaces toattempt routing recovery.

n poll interfacesfor status

Every n seconds, a timerexpires that indicates thatRouteD must poll TCP/IP’sinterface table for anyactivated, reactivated, ordeactivated interfaces. RouteDwill mark the interface asactive or inactive and ifnecessary, issue alerts(triggered updates) toadjacent routers fordeactivated interfaces toattempt routing recovery.




DTCRTD4958I supply destination -> port via interface

Explanation: RouteD is broadcasting a routinginformation protocol (RIP) datagram to the destinationaddress. The destination address can be either abroadcast address or a host address. If the port is zero,the current RouteD port will be used from thePROFILE TCPIP file. Otherwise, the datagram will betransmitted to the specified port over the interface tothe destination.




ROUTED Messages


DTCRTD4959I Interface interface up

Explanation: The specified interface, which was notpreviously active, is now active. The interface mighthave been inactive or re-installed.




DTCRTD4960E Incorrect host or (sub)networkaddress ‘destination’

Explanation: In the entry for the ETC GATEWAYS file,the gateway definition has an incorrect destinationaddress. The destination must be either a resolvablehost name or an IP address in dotted decimal notation.The ETC GATEWAYS entry is ignored.




DTCRTD4961E Incorrect gateway address ‘gateway’

Explanation: In the entry for the ETC GATEWAYS file,the gateway definition has a gateway address that isnot valid. The gateway address must be either aresolvable gateway name or an IP address in dotteddecimal notation. The ETC GATEWAYS entry isignored.




DTCRTD4962E Incorrect route type ‘type’

Explanation: In the entry for the ETC GATEWAYS file,the gateway definition route type is not valid.Allowable route types are host, for host route, net, fornetwork or subnetwork route, and active, for a route tobe treated as a network interface. The ETC GATEWAYSentry is ignored.




DTCRTD4963I (no ETC GATEWAYS definitions)

Explanation: The ETC GATEWAYS file does notcontain any definitions for configuring the routingtables on your host.


User or Operator Response: Include appropriatedefinitions in the ETC GATEWAYS file for configuringthe routing tables on your host before starting RouteD.


DTCRTD4964W Incorrect metric, changing to one

Explanation: In the entry for the ETC GATEWAYS file,the metric has an incorrect value. The metric is changedto 1 because the gateway internet address matches oneof the home internet addresses on the originating host.The destination host or network address is one hopaway.




DTCRTD4965I Virtual interface

Explanation: The new interface is virtual and is usedfor fault tolerance support. The virtual interface alwaysstays active and will never see a physical failure.Network and/or subnetwork virtual routes are beingadded to the interface.




DTCRTD4972E Incorrect type value: value

Explanation: In the entry for the ETC GATEWAYS file,the options definition contains an incorrect value.Although other options may be processed normally, theincorrect option is ignored.




DTCRTD4973E Unknown interface name (interface)and/or address (ip_addr)

Explanation: In the entry for the ETC GATEWAYS file,the options definition contains interface informationthat is not in RouteD’s interface table. Most likely, theinterface name is misspelled or its internet address isspecified incorrectly. Although other options may beprocessed normally, the incorrect option is ignored.




ROUTED Messages


DTCRTD4974I Issuing Kill Route Messages

Explanation: RouteD has detected an outage on aprimary or alternate adapter and is issuing an alert’Kill Route Messages’ to adjacent routers over anotherinterface providing the redundant path. This alert isused to notify adjacent routers to remove their routesto the failing adapter so that they can receive newrouting information from the new interface andperform routing switches immediately.




DTCRTD4975E Cannot establish communicationservices with the TCP/IP stack

Explanation: The BEGINtcpIPservice routine failedwhen RouteD attempted to establish a connection tothe TCP/IP stack.



System Programmer Response: Verify the TCP/IPstack is operational. If necessary, restart the TCP/IPserver.

DTCRTD4976E maxdesc returned errno: nn

Explanation: The RouteD server encountered an errorfrom maxdesc ( ) function.


System Programmer Response: Refer to maxdesc ( )in TCP/IP Programmer’s Reference to analyze the errno.Correct the error if possible and restart the RouteDserver. If this is not possible, contact your IBM supportcenter.

DTCRTD4977E getdtablesize ( ) error - tempdesc =nn, totdesc = nn; these values shouldmatch

Explanation: getdtablesize ( ) returned differentvalues.



System Programmer Response: Contact your IBMsupport center.

DTCRTD6000E SMSG Command from user_id:command

Explanation: An SMSG command request wasreceived from the indicated user ID.




DTCRTD6001E SMSG Command from user_id: usernot authorized

Explanation: The listed user ID was not found in theOBEY list. Only user IDs that are defined in the OBEYlist are authorized to issue SMSG commands to theRouteD server.


User or Operator Response: Notify the systemprogrammer about this action, if warranted.

System Programmer Response: If this user shouldhave this authority, then update the OBEY list. SeeTCP/IP Planning and Customization for moreinformation.

DTCRTD6020I SMSG SHUTDOWN commandissued by user_id

Explanation: The SMSG SHUTDOWN command wasreceived. The RouteD server will be immediatelyshutdown.

System Action: RouteD ends normally.


System Programmer Response: The RouteD serverwill be autologged by the TCP/IP stack if suitabledefinitions are present in the TCP/IP configuration file(PROFILE TCPIP). If not, then the server will have tobe manually restarted using the ROUTED command.

DTCRTD8479I Request on interface ignored, supplyis suppressed

Explanation: RouteD received a request for tables oninterface but supply has been disabled due to a filter inthe ETC GATEWAYS file. The route request will not behonored on that interface.



System Programmer Response: Check the ETCGATEWAYS file. If this is not the desired result offiltering, change the ETC GATEWAYS file and restartRouteD.

ROUTED Messages


|

||

|

|||||

|||

||

|

||

||

DTCRTD8481W Unknown next hop address ipaddressfor route destination from router router

Explanation: An unknown next hop address ipaddresswas received in a RIP packet for a route to destinationfrom router. The route is ignored.




DTCRTD8482I Address is experimental or hasnonzero port

Explanation: An incorrect internet address wasencountered, which is either in an experimental addressclass or is using an unusual port number (RoutingInformation Protocol (RIP) packets only). The address isbeing validated to ensure that a network user does notpretend to be a router in order to change the routingtable of nearby routers. The route entry is discardedsince the address is not considered a valid destinationaddress for a route.



System Programmer Response: Identify the machineor user that generated the packet in question andcorrect the problem.

DTCRTD8483W Incorrect internet address

Explanation: An internet address in an incoming routeis not a member of any defined internet address class.The route is discarded.



System Programmer Response: Locate the router thatoriginated the packet and correct the problem.

DTCRTD8484W A ’must-be-zero’ field is nonzero

Explanation: An internet address in an incoming routecontains a nonzero value in a field which must be zero.The incoming route is discarded.



System Programmer Response: Locate the router thatoriginated the packet and correct the problem.

DTCRTD8485I Response from non-router ipaddress

Explanation: A Routing Information Protocol (RIP)response packet was received with an incorrect portnumber. All routers on a network must agree on theport number used to exchange routing information, and

this port must be restricted so that other applicationscannot generate routing updates. Either a router isconfigured using the wrong port number or anapplication is issuing RIP routing updates. The RIPresponse is discarded.



System Programmer Response: Reconfigure the routerto use a correct port number and locate the applicationthat is generating the updates and correct the problem.

DTCRTD8486E Incorrect routing filter mask ’mask’

Explanation: In the entry for the RouteD ETCGATEWAYS file, the gateway definition has an invalidroute filter mask. The mask must be either a resolvablemask name or a 32-bit value in dotted decimalnotation. The gateways entry is ignored.




DTCRTD8487W Unable to open ROUTED CONFIG(config)

Explanation: A ROUTED CONFIG file was notspecified or could not be opened. This messageindicates which file the open was attempted on.



System Programmer Response: ROUTED CONFIG isa configuration file that defines how the RouteD serverwill send and receive packets (RIP version 1 and/orRIP version 2).

Note: Only the first file in the search order that can beopened will be read to determine the ROUTEDCONFIG.

DTCRTD8488I Opening ROUTED CONFIG (config)

Explanation: The specified ROUTED CONFIG file isbeing opened for processing.




DTCRTD8489S Unknown keyword (keyword) inROUTED CONFIG

Explanation: An unknown keyword was used in astatement in the ROUTED CONFIG. The statement isignored.

ROUTED Messages




System Programmer Response: Correct the ROUTEDCONFIG file.

DTCRTD8490W Unknown RIP rip_control controlvalue (value)

Explanation: The RIP control values (supply orreceive), specified on the RIP_SUPPLY_CONTROL orRIP_RECEIVE_CONTROL entry in the ROUTEDCONFIG, or specified on the options statement entryfor an interface, are incorrect. RouteD will default theRIP supply control to ’RIP1’ and the receive control to’ANY’.



System Programmer Response: Correct the ROUTEDCONFIG or ETC GATEWAYS file by specifying asupported supply or receive control value.

DTCRTD8491S RIP2 authentication key exceedsmaximum allowed or containsunsupported characters

Explanation: The RIP Version 2 authentication key,specified on the RIP2_AUTHENTICATION_KEY entryin the ROUTED CONFIG, or on the options statemententry in the ETC GATEWAYS file for an interface, isincorrect. The authentication key may containunsupported characters, exceed the maximum 16characters allowed, or not be enclosed in quotes. Theauthentication key is ignored and no authenticationcheck is performed.



System Programmer Response: Correct the ROUTEDCONFIG or ETC GATEWAYS file.

DTCRTD8492S Ignore SOURCEVIPA option cannotbe enabled on the socket

Explanation: An attempt failed to set the IBM socketoption to ignore source VIPA addresses in outbound IPdatagrams for RIP packets. VIPA addresses cannot beused as source IP addresses since adjacent routers relyon real (physical) IP addresses to determine gatewayaddresses for their routing tables; otherwise, adjacentrouters will discard the RIP packets.




DTCRTD8493I Interface interface skipped, supply issuppressed

Explanation: Broadcasting of routing information isbeing suppressed for the specified interface. For thisreason, the interface is being skipped while RouteD issupplying routing information to the list of interfaces.An interface supply option, defined in the RouteD ETCGATEWAYS file, determines whether or not RouteDsupplies routing information over an interface.




DTCRTD8494I rip_control rip_version packets fromaddress_destination on interface interfacenot allowed

Explanation: A RIP Version 1 or Version 2 packet isignored, depending on the settings of the RIP supply orreceive controls specified in the ETC GATEWAYS file orthe ROUTED CONFIG file. If there are no RIP controlsettings for an interface, RouteD will use those from theconfiguration file.



System Programmer Response: Correct the ROUTEDCONFIG or ETC GATEWAYS file.

DTCRTD8495I RIP2 packet from router router notauthorized

Explanation: A RIP Version 2 packet, received fromrouter, is ignored due to an authentication keymismatch. Authentication is enabled for RIP Version 2packets according to the interface options in ETCGATEWAYS file, or ROUTED CONFIG file. If there areno interface settings, RouteD will use the one from theconfiguration file.




DTCRTD8496E Gateway address ’address’ not arouting interface in the network

Explanation: The indicated route, defined in RouteD’sETC GATEWAYS file, referenced an unknown routinginterface based upon the gateway address. The routedefinition is ignored.



System Programmer Response: Correct the ETCGATEWAYS file. Verify that the gateway address is

ROUTED Messages


correct and a valid routing interface is defined.

DTCRTD8497I option value

Explanation: The ROUTED CONFIG has been readand the option and its associated value are displayed.




DTCRTD8498I RIP2 authentication action at levellevel (interface)

Explanation: RIP Version 2 authentication is enabledor disabled at the specified level for an interface or forall interfaces.




DTCRTD8499E Incorrect subnetwork mask ’mask’

Explanation: In the line entry for ETC GATEWAYSfile, the gateway definition has a subnet mask that isnot valid. The subnet mask must be a bit mask indotted-decimal notation. The bits must be contiguous inthe network portion of the subnet mask The ETCGATEWAYS entry is ignored.




DTCRTD8500E Config error: The RouteD servervirtual machine is not defined in theOBEY list

Explanation: This message indicates that the virtualmachine running the RouteD server is not defined inthe OBEY statement in the TCP/IP configuration file(PROFILE TCPIP).



System Programmer Response: Add the user ID ofthe RouteD server virtual machine to the OBEY list byupdating the OBEY statement in the TCP/IPconfiguration file. The TCPIP and RouteD servers mustbe restarted for this change to take effect. To avoidrestarting the TCPIP server, use the OBEYFILEcommand.

DTCRTD8501W VARSUBNETTING parameter notspecified, resetting RIP SUPPLYCONTROL: RIP1

Explanation: The RIP SUPPLY CONTROL value in theRouteD configuration file specified a RIP Version 2option, which requires the VARSUBNETTINGparameter of the ASSORTEDPARMS statement in theTCP/IP configuration file.



System Programmer Response: Add theVARSUBNETTING parameter to theASSORTEDPARMS statement in the TCP/IPconfiguration file. The TCPIP and RouteD servers mustbe restarted for this change to take effect. To avoidrestarting the TCPIP server, use the OBEYFILEcommand.

DTCRTD8502E Unable to start RouteD. A dynamicrouter is already running.

Explanation: Currently another dynamic Router isalready running with the TCP/IP stack.



System Programmer Response: Verify which dynamicrouter you wish to run and have only this one runningwith the stack.

ROUTED Messages


ROUTED Messages


Chapter 15. Site Table Configuration Messages

TESTSITE MessagesThis section contains TESTSITE messages.

No gateway named gateway

Severity: Error.

Explanation: There are no GATEWAY entries for thespecified name in the HOSTS ADDRINFO and HOSTSSITEINFO files.

System Action: The program continues and promptsthe user for the next name.

User or Operator Response: Correct the HOSTSLOCAL file and rebuild the HOSTS ADDRINFO andHOSTS SITEINFO files with MAKESITE, as necessary.This is not a fatal case.

Source File: CMTSITE PASCAL

Procedure Name: DoIt

No host named host

Severity: Error.

Explanation: There are no HOST entries for thespecified name in the HOSTS ADDRINFO and HOSTSSITEINFO files.





No net named net

Severity: Error.

Explanation: There are no NET entries for thespecified name in the HOSTS ADDRINFO and HOSTSSITEINFO files.





MAKESITE MessagesThis section contains the MAKESITE messages.

Address hash table overflow on host

Severity: Error.

Explanation: The AddrTableSize variable was exceededfor the host address hash table.

System Action: The program continues afterdisplaying this message.

User or Operator Response: Correct the problemidentified on the listed line and continue. If theproblem persists, contact the IBM Support Center.

Source File: CMMAKSI PASCAL

Procedure Name: Insert

Line LineNumber: bad address syntax

Severity: Error.

Explanation: A bad IP address was found in the inputfile. The program procedure found a value differentfrom the required IP address in dotted decimalnotation.


User or Operator Response: Correct the problemidentified on the listed line and continue.


Procedure Name: GetAddress


Line LineNumber: hash table overflow

Severity: Error.

Explanation: Data contained in the listed line numberof the input file caused a hash table overflow becausethe SiteTableSize variable was exceeded. This message isfollowed by another message indicating that this is afatal error condition.


User or Operator Response: Correct the problemidentified on the listed line and continue. If theproblem persists, contact the IBM Support Center.


Procedure Name: LookUp

Line LineNumber: no address specified

Severity: Error.

Explanation: The listed line number in the input filedid not contain one valid address.




Procedure Name: ParseLine

Line LineNumber: no name field

Severity: Error.

Explanation: The listed line number in the input filedid not contain a name field.





DTCMAK52I Size of SITE table exceeds thecapacity of MAKESITE.

DTCMAK53I Maximum size of SITE table: <xxx>DTCMAK54I Computed SITE table size: <yyy>DTCMAK58E MAKESITE Terminating

Abnormally

Severity: Error.

Explanation: These messages are issued as a group.This indicates that the HOSTS LOCAL file containedtoo many sitenames.

xxx Maximum size allowed for SITE table

yyy Computed size of SITE table

System Action: MAKESITE terminates with a returncode of 255.

System Programmer Response: Ensure that thecorrect HOSTS LOCAL file is being used and that theformat of the entries are correct. If error persists, thendecrease the number of SITE names in the HOSTSLOCAL file.


DTCMAK55I Size of ADDR table exceeds thecapacity of MAKESITE.

DTCMAK56I Maximum size of ADDR table:<xxx>

DTCMAK57I Computed ADDR table size: <yyy>DTCMAK58E MAKESITE Terminating Abnormally

Severity: Error.

Explanation: These messages are issued as a group;they indicate that the HOSTS LOCAL file contained toomany internet addresses.

xxx Maximum size allowed for ADDR table

yyy Computed size of ADDR table

System Action: MAKESITE terminates with a returncode of 255.

System Programmer Response: Ensure that thecorrect HOSTS LOCAL file is being used and that theformat of the entries are correct. If error persists, thendecrease the number of Address entries in the HOSTSLOCAL file.


Line LineNumber: no type specified

Severity: Error.

Explanation: The listed line number in the input filehad a null type field.





DTCMAK59E File mode parameter is not valid or notR/W.

Severity: Error.

Explanation: You specified a parameter that is notvalid on the MAKESITE command invocation, or you

MAKESITE Messages


specified a valid file mode, but one that is accessedread-only.

System Action: MAKESITE terminates with a returncode 255.

User or Operator Response: Specify a valid keywordor a read-write file mode as a parameter on theMAKESITE command.


Procedure Name: StartUp

DTCMAK60E Return code rc, reason code rs callingDMSQFMOD.

Severity: Error.

Explanation: The file mode supplied on theMAKESITE command invocation is not valid, or therewas another error attempting to verify the file modeletter using the DMSQFMOD CSL routine. For anexplanation of return and reason codes, see the z/VM:CMS Callable Services Reference.

System Action: MAKESITE terminates with a returncode 255.

User or Operator Response: Correct the problemdescribed by the return and reason code and retry thecommand.



Line LineNumber: only Fields fields

Severity: Error.

Explanation: The number of listed field terminatorswas less than the required minimum of three for thelisted line number in the input file.





Line LineNumber: unknown type BadType

Severity: Error.

Explanation: The listed line number in the input filewas not null and did not contain HOST, GATEWAY, orNET in the type field.





Unable to read HOSTS LOCAL *.

Severity: Error.

Explanation: TCP/IP could not find the HOSTSLOCAL file on any of the accessed minidisks.

System Action: The program halts after displaying themessage.

User or Operator Response: Rerun MAKESITE afteryou ensure that access to the HOSTS LOCAL file isavailable.



Warning: line LineNumber has too many addresses;only the first MAXsiteADDRESSES will be stored.

Severity: Warning.

Explanation: The listed line number in the input filecontained more addresses than the number allowed bythe listed MAXsiteADDRESSES variable.


User or Operator Response: Correct the problemidentified in the listed line and continue.



Warning: line LineNumber has too many names; onlythe first Number will be stored.

Severity: Warning.

Explanation: The listed line number in the input filecontained more names than the number allowed by thelisted hbound(names) variable.


User or Operator Response: Correct the problemidentified in the listed line and continue.



Warning: line LineNumber truncated to MAXlinecharacters

Severity: Warning.

Explanation: A line has been truncated because it islonger than the MaxLine constant. Comments areignored when determining the length of a line.

MAKESITE Messages

Chapter 15. Site Table Configuration Messages 221


User or Operator Response: If this truncationcondition is unacceptable, correct the problem beforecontinuing.


Procedure Name: GetLine

Warning name lost: Name

Severity: Warning.

Explanation: The listed name was lost duringprogram processing. This message is issued only if theWarnMe flag has been set to true with the WARNoption.


User or Operator Response: Determine the cause ofthe problem; correct it, if necessary, and continue.


Procedure Name: ProcessAdr

Warning name lost: Name

Severity: Warning.

Explanation: The listed name was lost duringprogram processing. This message is issued only if theWarnMe flag has been set to true with the WARNoption.


User or Operator Response: Determine the cause ofthe problem; correct it, if necessary, and continue.


Procedure Name: MergeNames

Warning: Name1 agrees with Name2 in the firstCMSwordLIMIT characters

Severity: Warning.

Explanation: This message indicates a possiblePseudoDuplicate name condition. This message isissued only if the WarnMe flag has been set to true withthe WARN option.


User or Operator Response: If this condition isunacceptable, correct the problem before continuing.



**** Fatal error: MakeSite aborted

Severity: Fatal.

Explanation: Data contained in the listed line numberof the input file caused a hash table overflow becausethe SiteTableSize variable was exceeded. This messagefollows the message that indicated the specific cause ofthe problem.

System Action: The program halts after displaying themessage.

User or Operator Response: Correct the problemidentified in the listed line and continue. If the problempersists, contact the IBM Support Center.



MAKESITE Messages


Chapter 16. SMTP Messages

This chapter contains Simple Mail Transfer Protocol (SMTP) messages, SMTP replycode messages, and SMTPRSCS messages.

SMTP Server Numbered MessagesThis section contains the numbered SMTP Server Messages.

DTCSMT1028E Invalid FileName Specification

Severity: Error.

Explanation: You entered a file name containing morethan 8 characters.

System Action: SMTP halts.

System Programmer Response: Correct the file nameso that it is 8 characters or less, and restart SMTP.

Source File: SMTP PASCAL


DTCSMT1029E Invalid FileType Specification

Severity: Error.

Explanation: You entered a file type containing morethan 8 characters.


System Programmer Response: Correct the file nameso that it is 8 characters or less, and restart SMTP.



DTCSMT1030E Invalid FileMode Specification

Severity: Error.

Explanation: You entered a file mode containing morethan 2 characters.


System Programmer Response: Correct the file modeso that it is less than two characters, and restart SMTP.



DTCSMT1031I Unable to find input file: FileNameFileType FileMode

Severity: Error.

Explanation: You entered a file name, file type, andfile mode for the SMTP configuration file that does not

exist on any accessed z/VM minidisk. Your erroneousinput is listed at the end of the message to help insyntax checking.


System Programmer Response: Verify that SMTP hasaccess to the specified file before restarting SMTP.



DTCSMT1032E Unrecognized option inconfiguration file: BadOption

Severity: Error.

Explanation: The option listed at the end of themessage is not one of the allowable valid configurationfile options. Refer to the TCP/IP Planning andCustomization for valid options.


System Programmer Response: Correct the erroneousentry in the configuration file and try again.



DTCSMT1033E Invalid LOG file destination:BadDestination

Severity: Error.

Explanation: You specified an invalid destination forthe LOG option in the configuration file. The onlydestinations are DISK and SPOOL.


System Programmer Response: Correct theconfiguration file and restart SMTP.




|

|

||

|

||

|

||

|

|

||

|

||

|

||

|

|

||

|

||

|

||

|

|

|||

|

||

|||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

|||

|

||

|

|

DTCSMT1034E Invalid Address in Restricted List:BadAddress

Severity: Error.

Explanation: SMTP found an invalid address in theRESTRICT list. Addresses must be in the formuserid@nodeid, with the asterisk character (*)representing wildcards.


System Programmer Response: Correct the erroneousentry in the configuration file and try again.



DTCSMT1035E Invalid Local Delivery Format:BadFormat

Severity: Error.

Explanation: You specified an invalid delivery formatfor the LOCALFORMAT option in the configurationfile. The only valid delivery formats are NETDATA andPUNCH.





DTCSMT1036E Invalid Rscs Delivery Format:BadFormat

Severity: Error.

Explanation: You specified an invalid option for theRSCSFORMAT option in the configuration file. Theonly valid choices for this option are NETDATA orPUNCH.



Source File: SMTPPASCAL


DTCSMT1037E Invalid Disposition in Restrictcommand: BadCommand

Severity: Error.

Explanation: The disposition specified with theRESTRICT option is not valid. Use only the validoptions of PURGE, RETURN, and TRANSFERTO withthe RESTRICT option.


System Programmer Response: Correct the erroneousentry in the configuration file and restart SMTP.



DTCSMT1038E Invalid Address for Mailer:BadAddress

Severity: Error.

Explanation: The length of the user ID for thereceiving address exceeds 8 characters, which is themaximum allowable VM user ID length for theMAILER option.


System Programmer Response: Correct the erroneousentry in the configuration file and restart SMTP.



DTCSMT1039E Invalid Max Mail Bytes: BadParameter

Severity: Error.

Explanation: The number_of_bytes parameter for theMAXMAILBYTES option is incorrect. It must be apositive integer value between 1 and 2 147 483 647.





DTCSMT1040E Invalid PostMaster Address: address

Severity: Error.

Explanation: The address specified on thePOSTMASTER configuration file statement is not valid.Additional messages will be given to indicate why theaddress is not valid.





DTCSMT1041E Invalid BadSpoolFileId Userid: userid

Severity: Error.

Explanation: The user ID specified on theBADSPOOLFILEID configuration file statement is not avalid user ID on the local system or the user ID isgreater than 8 characters.

SMTP Server Numbered Messages


|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

||

|

|||

|

||

|

|

||

|

||||

|

||

|

|

||

|

||||





DTCSMT1043E Invalid Transfer To Userid:BadUserID

Severity: Error.

Explanation: You specified a user ID that does notexist for the RESTRICT TRANSFERTO statement in theconfiguration file.


System Programmer Response: SMTP uses the CPSPOOL PUNCH TO userid command to determine ifthe user ID exists. Verify that this user ID exists, andthat SMTP is able to punch files to it. Otherwise,correct the SMTP configuration file, specifying a validuser ID, and restart SMTP. Correct any networkproblems, as necessary, before you try again.



DTCSMT1044E Invalid Mailer Option: BadOption

Severity: Error.

Explanation: The option specified on the MAILERconfiguration file statement is not valid. See TCP/IPPlanning and Customization for the valid MAILERstatement options. These options must be specified inthe correct order.





DTCSMT1050I Compiled-in. Unable to load:TranslateTableName TCPXLBIN *


Explanation: The specified translate table file couldnot be loaded. The default 7-bit translation table hasbeen loaded.

System Action: SMTP continues.

System Programmer Response: Determine why thespecified translate table could not be loaded. Mostlikely, the file could not be found.


Procedure Name: LoadTranslateTable

DTCSMT1071I Unknown Command: command

Severity: Error.

Explanation: The server received an unidentifiablecommand, which is listed at the end of the message.The allowable or known commands are:

DATA NOOP SENDEHLO QUEU SOMLEXPN QUIT TICKHELP RCPT TURNHELO RSET VERBMAIL SAML VRFY

System Programmer Response: The sender mustcorrect the syntax before resubmitting the command. Ifnecessary, the user can request online help by enteringHELP.


Source File: SMTPCMDS PASCAL

Procedure Name: NoSuchCommand

DTCSMT1093E Invalid numeric operand found:operand

Severity: Error.

Explanation: A numeric operand was expected, butthe SMTP server found the specified operand in theconfiguration file. The operand must be a number lessthan 2147483647.





DTCSMT1094E Invalid ServerPort specified: port

Severity: Error.

Explanation: An invalid port number was specified onthe PORT configuration file statement. The port mustbe a number in the range of 1 through 65535.






Chapter 16. SMTP Messages 225

|

||

|

|

|||

|

|||

|

|||||||

|

|

||

|

|||||

|

||

|

|

|||

|

|||

|

|||

|

|

||

|

|||

||||||||||||||||||||

||||

|

|

|

|||

|

||||

|

||

|

|

||

|

|||

|

||

|

|

|||

DTCSMT1097I NonExistent: ReturnCode

Severity: Error.

Explanation: The connection no longer exists for thelisted return code reason. The connection could havebeen dropped because of a software error on theremote SMTP server, or a routing or connectivityproblem in the internet network.


System Programmer Response: Normally, no action isnecessary. The mail is delivered automatically at a latertime when connectivity is restored. If the problempersists, check for a software error in the remote SMTPserver, or a problem in the piece of mail itself. Forexample, if a user tries to send a binary piece of SMTPmail, some host’s SMTP servers crash or abnormallyclose the connection.

Source File: SMTPEVNT PASCAL

Procedure Name: CloseCompletedEvent

DTCSMT1098I StoreData: entering ″discard″ mode

Severity: Warning.

Explanation: This error message is output at the localconsole to indicate that the sender’s mail file exceededthe maximum number of ASCII bytes allowed by theMAXMAILBYTES option in the configuration file. Theexcessively large mail file is flushed. This message isissued before the message that confirms the flushing ofthe file.


System Programmer Response: Tell the sender toshorten the mail file, or subdivide the file into two ormore shorter files that are within the existingMAXMAILBYTES limitation. You can increase theMAXMAILBYTES option value in the SMTP CONFIGconfiguration file, and tell the sender to try again.


Procedure Name: StoreData

DTCSMT1099I StoreData: leaving ″discard″ mode

Severity: Warning.

Explanation: SMTP sends this message to the localconsole to indicate that the sender’s mail file exceededthe maximum length specified by the MAXMAILBYTESoption in the configuration file. The mail file beingprocessed has been discarded. This message alsoverifies that an attempt was made to return a messageto the mail sender to inform the sender of aconfiguration problem on the receiving machine.


System Programmer Response: Tell the sender toshorten the mail file, or to subdivide the file into two

or more shorter files that are within the existingMAXMAILBYTES limitation. You can increase theMAXMAILBYTES option value in the SMTP CONFIGconfiguration file, and tell the sender to try again.



DTCSMT1115E Invalid Rewrite822Header Option:BadOption

Severity: Error.

Explanation: You specified an invalid option for theREWRITE822HEADER option in the configuration file.The only valid choices for this option are YES or NO.





DTCSMT1116E Option Conflict: SECURE andRESTRICT may not both be specified

Severity: Error.

Explanation: You cannot use the options SECURE andRESTRICT together because they are incompatible.





DTCSMT1117E Invalid DBCS Option: option

Severity: Error.

Explanation: An invalid option has been specified inthe SMTP CONFIG file for the DBCS statement.


User or Operator Response: Specify a valid option forthe DBCS statement and restart SMTP. See the TCP/IPPlanning and Customization for more information aboutconfiguring DBCS support for the SMTP server.



DTCSMT1118E Invalid Kanji shift-in Option: option

Severity: Error.

Explanation: An invalid shift-in option has beenspecified in the SMTP CONFIG file for the DBCSstatement. The valid shift-in options for the JIS78KJ and



||

|

|||||

|

||||||||

|

|

||

|

|||||||

|

||||||

|

|

||

|

||||||||

|

||

||||

|

|

|||

|

|||

|

||

|

|

|||

|

||

|

||

|

|

||

|

||

|

||||

|

|

||

|

|||

JIS83KJ conversion types are ASCII and JISROMAN.


User or Operator Response: Specify a valid shift-inoption for the DBCS statement and restart SMTP. Seethe TCP/IP Planning and Customization for moreinformation about configuring DBCS support for theSMTP server.



DTCSMT1119E Too Many ALTTCPHOSTNAMEstatements - limit is MaxAltOurNames

Severity: Error.

Explanation: The number of alternative TCP hostname options selected exceeds the maximum numberallowed. The maximum number allowed is listed at theend of the message; the default is 16.


System Programmer Response: Reduce the number ofALTTCPHOSTNAME statements in the configurationfile and restart SMTP, or increase the parameterMaxAltOurNames to the desired number.



DTCSMT1134I Protocol Error. I= I Bytes Received =BytesReceived

Severity: Error.

Explanation: This error message is output at the localconsole to indicate that the sender’s mail was notsuccessfully delivered because of a protocol problem.The SMTP server received the string,<CR><LF>·<CR><LF>, followed by additional data. Thestring, <CR><LF>·<CR><LF>, is used to specify the end ofthe data; thus, the client SMTP server is in error. Thedata is accepted, and the client SMTP server waits foran additional <CR><LF>·<CR><LF>.


System Programmer Response: Describe the problemto the postmaster of the SMTP server that is sendingthe incorrectly formatted mail.


Procedure Name: StoreDataTableErrors

DTCSMT1135I Reply Line too long

Severity: Warning.

Explanation: SMTP sends this message to the serverconsole to indicate that a remote SMTP server’sresponse exceeded the 512-byte limitation specified by

RFC 821. VM SMTP accepts the reply and truncates itto 512 bytes.


System Programmer Response: If the problempersists, the postmaster of the remote SMTP servershould be notified that its SMTP server is sendingreplies that are greater than the 512-byte limit.

Source File: SMTPRPLY PASCAL

Procedure Name: DoReply

DTCSMT1161E Invalid value InactivityTimeOutspecified for Inactive. Default used.

Severity: Error.

Explanation: An invalid inactivity timeout wasspecified on the INACTIVE configuration filestatement. The inactivity timeout must be a number inthe range of 1 through 86400.

System Action: SMTP continues and uses the defaultof 180 seconds.

System Programmer Response: If the defaultinactivity timeout is not appropriate, correct theconfiguration file and restart SMTP.


Procedure Name: DoInactiveState

DTCSMT1162E Invalid value FinishOpenTimeOutspecified for FinishOpen. Default used.

Severity: Error.

Explanation: An invalid finish open timeout wasspecified on the FINISHOPEN configuration filestatement. The finish open timeout must be a numberin the range of 1 through 86400.

System Action: SMTP continues and uses the defaultof 120 seconds.

System Programmer Response: If the default finishopen timeout is not appropriate, correct theconfiguration file and restart SMTP.



DTCSMT1163E Invalid value RetryAge specified forRetryAge. Default used.

Severity: Error.

Explanation: An invalid retry age was specified on theRETRYAGE configuration file statement. See TCP/IPPlanning and Customization for valid ranges for retryages specified in days, hours, or minutes.

System Action: SMTP continues and uses the defaultof 3 days.



|

|

|||||

|

|

|||

|

||||

|

||||

|

|

|||

|

|||||||||

|

|||

|

|

||

|

|||

||

|

||||

|

|

|||

|

||||

||

|||

|

|

|||

|

||||

||

|||

|

|

|||

|

||||

||

System Programmer Response: If the default retry ageis not appropriate, correct the configuration file andrestart SMTP.


Procedure Name: DoRetryInterval

DTCSMT1164E Invalid value RetryInterval specifiedfor RetryInt. Default used.

Severity: Error.

Explanation: An invalid retry interval was specifiedon the RETRYINT configuration file statement. Theretry interval must be a number in the range of 0through 1440.

System Action: SMTP continues and uses the defaultof 20 minutes.

System Programmer Response: If the default retryinterval is not appropriate, correct the configuration fileand restart SMTP.


Procedure Name: DoRetryIntState

DTCSMT1165E Invalid value ResolverRetryIntervalspecified for ResolverRetryInt. Defaultused.

Severity: Error.

Explanation: An invalid resolver retry interval wasspecified on the RESOLVERRETRYINT configurationfile statement. The resolver retry interval must be anumber in the range of 1 through 1439.

System Action: SMTP continues and uses the defaultof 20 minutes.

System Programmer Response: If the default resolverretry interval is not appropriate, correct theconfiguration file and restart SMTP.


Procedure Name: DoResolRetryInt

DTCSMT1166E Invalid value value specified forRcptResponseDelay. Default used.

Severity: Error.

Explanation: The error is caused either by an invalidvalue of less than 0 or greater than 86 400, or becauseNSInterAddr is not coded in the TCPIP DATA file.

System Action: SMTP continues and uses a default of60.

System Programmer Response: Correct the SMTPCONFIG file or TCPIP DATA file.



DTCSMT1167E Invalid value TempErrorRetriesspecified for TempErrorRetries. Defaultused.

Severity: Error.

Explanation: An invalid temporary error retry valuewas specified on the TEMPERRORRETRIESconfiguration file statement. The value must be anumber in the range of 0 through 2147483647.

System Action: SMTP continues and uses the defaultof 0 retries.

System Programmer Response: If the defaulttemporary error retry value is not appropriate, correctthe configuration file and restart SMTP.



DTCSMT1168E RcpResponseDelay value is ignoredif name servers are not used for nameresolution

Severity: Error.

Explanation: When SMTP has been configured to usethe local site tables to resolve host name addressesrather than using a domain name server, any value thatmay have been specified on the SMTPRCPTRESPONSEDELAY configuration statement isrendered meaningless and therefore ignored.


System Programmer Response: Remove theRCPTRESPONSEDELAY statement from the SMTPconfiguration file if you are not planning to use a hostdomain name server.


Procedure Name: DoRcptResponseState

DTCSMT1170E Invalid value MailHopCount specifiedfor MailHopCount.

Severity: Error.

Explanation: An invalid mail hop count was specifiedon the MAILHOPCOUNT configuration file statement.The mail hop count must be a number in the range of 5through 300.







|||

|

|

|||

|

||||

||

|||

|

|

||||

|

||||

||

|||

|

|

|||

|

|||

||

||

|

|

||||

|

||||

||

|||

|

|

||||

|

||||||

|

||||

|

|

|||

|

||||

|

||

|

|

|||

DTCSMT1171E Invalid value InactiveTime specifiedfor Inactive.

Severity: Error.

Explanation: A non-numeric inactivity timeout wasspecified on the INACTIVE configuration filestatement. The inactivity timeout must be a number inthe range of 1 through 86400.





DTCSMT1172E Invalid value FinishOpenTimespecified for FinishOpen.

Severity: Error.

Explanation: A non-numeric finish open timeout wasspecified on the FINISHOPEN configuration filestatement. The finish open timeout must be a numberin the range of 1 through 86400.





DTCSMT1173E Invalid value RetryAge specified forRetryAge.

Severity: Error.

Explanation: A non-numeric retry age was specifiedon the RETRYAGE configuration file statement. SeeTCP/IP Planning and Customization for valid ranges forretry ages specified in days, hours, or minutes.





DTCSMT1174E Invalid value RetryInt specified forRetryInt.

Severity: Error.

Explanation: A non-numeric retry interval wasspecified on the RETRYINT configuration filestatement. The retry interval must be a number in therange of 0 through 1440.





DTCSMT1175E Invalid value ResolverRetryIntspecified for ResolverRetryInt.

Severity: Error.

Explanation: A non-numeric resolver retry intervalwas specified on the RESOLVERRETRYINTconfiguration file statement. The resolver retry intervalmust be a number in the range of 1 through 1439.





DTCSMT1176E Invalid value RcptResponseDelayspecified for RcptResponseDelay.

Severity: Error.

Explanation: A non-numeric recipient response delaywas specified on the RCPTRESPONSEDELAYconfiguration file statement. The recipient responsedelay must be a number in the range of 0 through86400.





DTCSMT1177E Invalid value TempErrorRetriesspecified for TempErrorRetries.

Severity: Error.

Explanation: A non-numeric temporary error retryvalue was specified on the TEMPERRORRETRIESconfiguration file statement. The value must be anumber in the range of 0 through 2147483647.







|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

|||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

DTCSMT1178E Invalid value WarningAgeAmtspecified for WarningAge.

Severity: Error.

Explanation: An invalid warning age was specified onthe WARNINGAGE configuration file statement. SeeTCP/IP Planning and Customization for valid ranges forwarning ages specified in days, hours, or minutes.





DTCSMT1179E Invalid VERIFYCLIENT option:option

Severity: Error.

Explanation: An invalid option was specified on theVERIFYCLIENT configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe VERIFYCLIENT statement.


System Programmer Response: Correct theconfiguration file statement and restart SMTP.



DTCSMT1180E Invalid VERIFYCLIENTDELAYoption: delay

Severity: Error.

Explanation: An invalid delay value was specified onthe VERIFYCLIENTDELAY configuration file statement.The verify client delay must be a number in the rangeof 0 through 86400.





DTCSMT1191E Invalid FORWARDMAIL option:option

Severity: Error.

Explanation: An invalid option was specified on theFORWARDMAIL configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe FORWARDMAIL statement.





DTCSMT1192E Invalid SMTPCMDS option: option

Severity: Error.

Explanation: An invalid option was specified on theSMTPCMDS configuration file statement. See TCP/IPPlanning and Customization for valid options for theSMTPCMDS statement.





DTCSMT1193E Invalid TRACE option: option

Severity: Error.

Explanation: An invalid option was specified on theTRACE configuration file statement. See TCP/IPPlanning and Customization for valid options for theTRACE statement.





DTCSMT1195E Invalid SOURCEROUTES option :option

Severity: Error.

Explanation: An invalid option was specified on theSOURCEROUTES configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe SOURCEROUTES statement.





DTCSMT1196E Invalid filename for 8-bit MIMESupport: FileName

Severity: Error.

Explanation: On the 8BITMIME statement in theconfiguration file, you specified an invalid file name.



|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

||

|

||||

|

||

|

|

||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||

The name may be longer than 8 characters or it maycontain invalid characters.


System Programmer Response: Correct the SMTPconfiguration file so that the file name specified on the8BITMIME statement is a valid file name, and restartSMTP.


Procedure Name: DoMimeSupport, Error

DTCSMT1197E Unable to find 8-bit MIMEtranslation table: FileName TCPXLBIN *

Severity: Error.

Explanation: The translation table specified on the8BITMIME statement in the configuration file does notexist on any accessed VM minidisk.


System Programmer Response: Verify that this fileexists. Correct the SMTP configuration file, specifyingthe correct file name, and restart SMTP.


Procedure Name: DoMimeSupport

DTCSMT1198E Unable to load 8-bit MIMEtranslation table: FileName TCPXLBIN *

Severity: Error.

Explanation: The translation table specified on the8BITMIME statement in the configuration file could notbe loaded because the file format is incorrect.


System Programmer Response: Verify that this file isa translation table. Correct the SMTP configuration file,specifying a valid translation table, and restart SMTP.



DTCSMT1201E Terminating: Disk ’A’ is read only

Severity: Error.

Explanation: The CMS LISTFILE command resulted ina return code of 36, which means that the A-disk isaccessed as a read-only minidisk. For SMTP to performthe InitializeDeliveryQueue procedure, the A-disk mustbe accessed as a read/write minidisk.


System Programmer Response: Access the SMTP Aminidisk in read/write mode, and restart SMTP.


Procedure Name: InitializeDeliveryQueue

DTCSMT1202E Terminating: GATEWAY specifiedbut SMTPRSCS HOSTINFO file cannotbe found

Severity: Error.

Explanation: The GATEWAY statement has beenspecified in the SMTP CONFIG file but no SMTPRSCSHOSTINFO file can be found.

System Action: SMTP terminates.

System Programmer Response: Create an SMTPRSCSHOSTINFO file to define the users on the RSCS hostsfor which SMTP will accept mail for.


Procedure Name: InitializeRSCSTable

DTCSMT1204E Terminating: Unable to properlyestablish UDP connection forNameserver queries

Severity: Error.

Explanation: The server was unable to completeinitialization because it could not establish a workingUDP connection for use during Nameserver queries.


System Programmer Response: Restart the SMTPserver.



DTCSMT1205I Terminating: CP EXT received


Explanation: SMTP terminates because an externalinterrupt was received.




Procedure Name: HandleTCPIPEventNotification

DTCSMT1206E Procedure Terminating: reason

Severity: Error.

Explanation: SMTP terminates for the specified reason.


System Programmer Response: Use the specifiedreason to determine why the SMTP server shut down. Ifneeded, contact your IBM Support Center forassistance.



||

|

||||

|

|

|||

|

|||

|

|||

|

|

|||

|

|||

|

|||

|

|

||

|

|||||

|

||

|

|

||||

|

|||

|

|||

|

|

||||

|

|||

|

||

|

|

||

|

||

|

|

|

|

||

|

|

|

||||

Source File: SMTPUTIL PASCAL


DTCSMT1207E Procedure SMTP bug: reason

Severity: Error.

Explanation: A software error has occurred in theSMTP server. The reason should not occur in SMTPprocessing.


System Programmer Response: Use the specifiedreason to determine what error occurred. Contact yourIBM Support Center for assistance.



DTCSMT1208E Local Error in MakeAddrBlok RC =ReturnCode

Severity: Error.

Explanation: SMTP did not have enough free diskspace on its A-disk to store an ADDRBLOK file.


System Programmer Response: If the A-disk is full,delete old files, such as SMTP LOGs, or increase thesize of the A-disk. If the A-disk is not full, there may bea problem with the ADDRBLOK file. If the problempersists, contact the IBM Support Center for assistance.



DTCSMT1210E FileName ADDRFILE is in aninconsistent state...repairing

Severity: Warning.

Explanation: SMTP sends this message to the serverconsole to indicate a problem with the ADDRBLOKfile. SMTP attempts to rewrite the ADDRBLOK file in acorrect format.


System Programmer Response: Normally, no responseis necessary. If SMTP abends while performing thisrewrite, the ADDRBLOK may not be recoverable.Rename or discard the ADDRBLOK file to preventfurther abends of SMTP.

Source File: SMTPQUEU PASCAL

Procedure Name: EnQueueForDelivery

DTCSMT1211E Delivery of Note AddrFile.fscbfn toAddrString failed RC = ReturnCode

Severity: Warning.

Explanation: SMTP sends this message to the serverconsole to indicate that the identified note was notsuccessfully transferred to the listed addressee for thelisted return code reason. This condition can occur ifSMTP tries to punch a file to an invalid user ID, or ifSMTP tries to punch a file with a header with morethan 80 characters to a mailer running mailer old.


System Programmer Response: Determine the reasonfor this failure, correct it, and try again.

Source File: SMTPQUEU PASCAL

Procedure Name: DeliverSpoolFile

DTCSMT1214E Invalid IPMailer Address Specified:IPaddress

Severity: Error.

Explanation: The IP address specified in theIPMAILERADDRESS statement of your SMTPconfiguration file is not correct or not valid.

System Action: The SMTP server is halted until theproblem is corrected.

System Programmer Response: Verify the IP addressof the batch SMTP server, and correct theIPMAILERADDRESS statement as necessary. Fordetails, see the TCP/IP Planning and Customization.



DTCSMT1215E IPMAILERADDRESS statementconflicts with MAILER UNKNOWNstatement

Severity: Error

Explanation: The MAILER UNKNOWN statement inyour SMTP configuration file is incompatible with theIPMAILERADDRESS statement.


System Programmer Response: Remove theUNKNOWN parameter from the MAILER statement.For details, see the TCP/IP Planning and Customization.





|

|

||

|

|||

|

|||

|

|

|||

|

||

|

|||||

|

|

|||

|

||||

|

|||||

|

|

|

|||

|

|||||||

|

||

|

|

|||

|

|||

||

||||

|

|

||||

|

|||

||

|||

|

|

|||

DTCSMT1220E *SPL Error Reading Data. Spool File:Spoolid transferred to BadSpoolFileID

Severity: Error.

Explanation: SMTP encountered an error whileattempting to read the spool file using the *SPL systemservice.

System Action: SMTP continues but the spool file thatwas being processed is transferred to theBADSPOOLFILEID.

System Programmer Response: Contact your systemsupport personnel if SMTP terminates abnormally.

Source File: SMTPINTR PASCAL

Procedure Name: TransferSpool

DTCSMT1221E An unexpected Sever was receivedfrom *SPL.

Severity: Error.

Explanation: SMTP encountered an unexpected Severfrom the *SPL system service

System Action: SMTP continues processing. The spoolfile that was in process when the Sever occurred will beretried.

System Programmer Response: If this problem occursfrequently, contact your system support personnel.


Procedure Name: RetrySpool

DTCSMT1222E Error detected during CMSIUCVConnect to *SPL, RC = Return Code

Severity: Error.

Explanation: SMTP encountered an error whileattempting to Connect to the *SPL system service.

System Action: SMTP continues processing. TheConnect to *SPL will be retried.

System Programmer Response: Identify the problemwith the CMSIUCV Connect by looking up the returncode. If the problem is something that cannot becorrected, contact your system support personnel.

Source File: SMTPBTCH PASCAL

Procedure Name: ServRdrDisable

DTCSMT1223E Initial CMSIUCV Connect to *SPLfailed, RC = Return Code

Severity: Error.

Explanation: SMTP encountered an error during theinitial Connect to the *SPL system service.


System Programmer Response: Verify that the SMTPServer directory entry contains an ’IUCV *SPL’statement. If it does, identify the problem by lookingup the CMSIUCV Connect return code.


Procedure Name: Mainloop

DTCSMT1224E HNDIUCV SET failed with RC =ReturnCode, IUCV functions cannot beperformed

Severity: Error.

Explanation: SMTP encountered an error whileattempting to issue the HNDIUCV SET macro.


System Programmer Response: Identify the problemwith the HNDIUCV SET by looking up the return code.Correct the problem with HNDIUCV SET and restartthe server.


Procedure Name: Mainloop

DTCSMT1225E Unreadable spool file: Spoolidtransferred to BadSpoolFileID

Severity: Error.

Explanation: The format of the spool file read fromthe reader is invalid, the spool file is unreadable

System Action: SMTP continues but the spool fileprocessing terminates abnormally.

System Programmer Response: None


Procedure Name: HandleSPLPathWork

DTCSMT1226E Disk Almost Full. Spool File: Spoolidplaced in HOLD status

Severity: Warning.

Explanation: SMTP issues this message when theamount of free space on the server’s A-disk is lowenough that the server may not be able to completelyprocess a piece of mail. This is only applicable to mailbeing received from SMTP’s reader (batch mode). Theamount of disk space required to process a piece ofmail is between 3 and 4 times the size of the piece ofmail for large pieces of mail. The server will be able toprocess other, smaller pieces of mail.

System Action: The program continues. The spool filespoolid is placed in user hold status.

System Programmer Response: Increase the free spaceon the SMTP server’s A-disk by removing unwantedfiles or allocating a larger minidisk. Ensure that you donot destroy any files required for SMTP’s operation or



|||

|

|||

|||

||

|

|

|||

|

||

|||

||

|

|

|||

|

||

||

||||

|

|

|||

|

||

|

||||

|

|

||||

|

||

|

||||

|

|

|||

|

||

||

|

|

|

|||

|

|||||||||

||

||||

any mail files that you want delivered. Spool filesplaced in user hold status must be manually changedback to nohold status before they will be processed.



DTCSMT1227E Null Spool File: Spoolid RC=ReturnCode transferred to: PostMasterId

Severity: Error.

Explanation: SMTP sends this message to the serverconsole to indicate that the specified spool file had anull length, or contained no records. The spool file istransferred to the Postmaster for the system.


System Programmer Response: Determine the originof the null spool file and correct the problem.



DTCSMT1228E *SPL Error Reading Data. Transfer ofspool file spoolid failed, RC = rc. Spoolfile remains in reader.

Severity: Error.

Explanation: SMTP encountered an error whileattempting to read the spool file using the *SPL systemservice. The attempt to transfer the spool file to theBADSPOOLFILEID failed.


System Programmer Response: Look up the returncode from the Transfer command to determine why itfailed. Contact your system support personnel todetermine why the *SPL read failed.


Procedure Name: TransferSpool

DTCSMT1233E Unexpected return from user exitfilename filetype, RC = rc

Severity: Error.

Explanation: The SMTP server received an unknownreturn code from the specified user exit.


System Programmer Response: Determine why theuser exit gave SMTP the unknown return code.

Source File: SMTPCMDS, SMTPQUEU, SMTPRESPASCAL

Procedure Name: DoHeloOrEhlo, DoCommand,MakeAddrBlok, DeliverSpoolFile, TryFwdMail

DTCSMT1236W BSMTP spool file processing hasbeen temporarily suspended. The serverA-disk is above 90% full.

Severity: Warning.

Explanation: The SMTP A-disk is above 90% full, sospool files will not be processed until sufficient A-diskspace becomes available. This allows SMTP to delivermail that is already saved on this disk, so thatadditional space on the A-disk will again be available.When the A-disk becomes less than 90% full, spool fileprocessing will resume.

System Action: The program continues, but futurespool files are not received until additional space isavailable on the server’s A-disk.



Procedure Name: CheckDiskFull

DTCSMT1240E Callable service routine DTCXLATEis not loaded. Unable to loadTranslateTableName TCPXLBIN *

Severity: Error.

Explanation: The DTCXLATE CSL routine was notfound because an incorrect level of CMS is being used.The specified translate table could not be loaded.


System Programmer Response: Re-ipl with the correctlevel of CMS and restart the SMTP server.


Procedure Name: DoMimeSupport,LoadTranslateTable

DTCSMT1241E Callable service routine DTCXLATEfailed with RC = rc, Reason = rsc

Severity: Error.

Explanation: An error occurred when the SMTP servertried to use the DTCXLATE CSL routine to load atranslate table.


System Programmer Response: Use the return codeand reason code from the DTCXLATE CSL routine todetermine why the error occurred. Refer to the z/VM:CMS Callable Services Reference for return and reasoncodes.





|||

|

|

|||

|

||||

||

||

|

|

||||

|

||||

||

||||

|

|

|||

|

||

|

||

||

||

||||

|

|||||||

|||

|

|

|

||||

|

|||

|

||

|

||

|||

|

|||

|

|||||

|

|

|||

DTCSMT1243E Too many IP addresses configuredfor IPMAILERADDRESS statement. IPaddress address will not be used

Severity: Error.

Explanation: Only 16 IP addresses can be used on theIPMAILERADRESS statement. The specified address isignored.




Procedure Name: DoIPMailerListState

DTCSMT1244E Invalid value value specified forFilesPerConn.

Severity: Error.

Explanation: The value specified in theFILESPERCONN configuration file statement is notvalid. The FILESPERCONN value must be an integerform 1 to 1,000.


System Programmer Response: Correct theconfiguration file statement and restart the SMTPserver.



DTCSMT1245E Invalid value value specified forMaxConnPerSite.

Severity: Error.

Explanation: The value specified in theMAXCONNPERSITE configuration file statement is notvalid. The MAXCONNPERSITE value must be aninteger form 1 to 256.


System Programmer Response: Correct theconfiguration file statement and restart the SMTPserver.



DTCSMT1248E MAILER statement specifies anIMAP virtual machine that is not on thelocal RSCS node

Severity: Error.

Explanation: The MAILER statement in the SMTPconfiguration file specified a mailer format of IMAP,but a non-local RSCS node was specified for the IMAPuserid.


System Programmer Response: Correct the problemin the SMTP configuration file and restart SMTP.



DTCSMT1249E Invalid Address in SMSGAuthorization List: address

Severity: Error.

Explanation: The specified address is not valid for theSMSGAUTHLIST configuration file statement. Theaddress is a local address, but it is longer than 8characters.





DTCSMT1250E Disk Full Action Percent must be inthe range: -100..0..100 but found: percent

Severity: Error.

Explanation: The percent specified on theONDISKFULL configuration file statement is not valid.The percent must be a number in the range of -100 to100.





DTCSMT1251E Duplicate Disk Full Action PercentSpecified: percent

Severity: Error.

Explanation: The specified percent was already givenon the ONDISKFULL configuration file statement. Apercentage can only be specified once as a positive andonce as a negative percentage.







||||

|

|||

|

|

|

|

|||

|

||||

|

|||

|

|

|||

|

||||

|

|||

|

|

||||

|

||||

||

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

||

|

|

|||

DTCSMT1253E Expecting ’BEGIN’ or’ENDACTIONS’ but found: token

Severity: Error.

Explanation: The specified token was found where a’BEGIN’ or ’ENDACTIONS’ token should be whileparsing the ONDISKFULL configuration file statement.





DTCSMT1254E OnDiskFull Action must be less thanchars characters long

Severity: Error.

Explanation: An action listed on the ONDISKFULLconfiguration file statement is too long. The action mustbe less than chars characters long.


System Programmer Response: Correct theconfiguartion file statement and restart SMTP.

Source File: SMTP


DTCSMT1255E OnDiskFull Action must be a CPcommand not: action

Severity: Error.

Explanation: The action specified on theONDISKFULL configuration file statement did notbegin with ’CP’. ONDISKFULL actions must be a CPcommand.



Source File: SMTP


DTCSMT1256E Invalid Disk Full Action PercentSpecified: percent

Severity: Error.

Explanation: A non-numeric percent was specified onthe ONDISKFULL configuration file statement. Thepercent must be a number in the range of -100 to 100.



Source File: SMTP


DTCSMT1257E LOOPINGMAIL statement no longervalid. Please use the BADSPOOLFILEIDstatement

Severity: Error.

Explanation: LOOPINGMAIL is no longer a validSMTP configuration file statement. Instead, you shoulduse the BADSPOOLFILEID statement.



Source File: SMTP


DTCSMT1258E Only one POSTMASTER statementmay be specified in SECURE mode

Severity: Error.

Explanation: More than one POSTMASTERconfiguration file statement was specified when theSECURE statement was also specified. There can beonly one POSTMASTER statement if the SECUREstatement has been used.



Source File: SMTP


DTCSMT1259E Invalid POSTMASTER address:address

Severity: Error.

Explanation: A non-local address was specified on thePOSTMASTER configuration file statement while theSECURE statement was also specified. When theSECURE statement is specified, there may be only onePOSTMASTER statement which must include a user IDon the local system.



Source File: SMTP




|||

|

|||

|

||

|

|

|||

|

|||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

|||

|

||

|

|

||||

|

|||

|

||

|

|

|||

|

|||||

|

||

|

|

|||

|

||||||

|

||

|

|

|||

DTCSMT1260E In SECURE mode, POSTMASTERaddress must be a valid local userid

Severity: Error.

Explanation: A non-local address was specified on thePOSTMASTER configuration file statement while theSECURE statement was also specified. When theSECURE statement is specified, there may be only onePOSTMASTER statement which must include a user IDon the local system.



Source File: SMTP


DTCSMT1261E Expecting ’PRINT’ or ’NOPRINT’after ’REWRITE822HEADER YES’statement

Severity: Error.

Explanation: A REWRITE822HEADER YESconfiguration file statement was not followed by the’PRINT’ or ’NOPRINT’ option.



Source File: SMTP


DTCSMT1262E OLD Option of Mailer statement nolonger supported.

Severity: Error.

Explanation: The MAILER configuration file statementcontained the OLD option. This option is no longersupported. Refer to the z/VM: TCP/IP Level 430Planning and Customization for valid options.



Source File: SMTP


DTCSMT1300I Deleting Spool File fromundetermined origin

Severity: Warning.

Explanation: This message is output to the SMTPbatch log to indicate that a spool file from anundetermined RSCS origin is being deleted. SMTP doesnot accept an RSCS spool file, unless SMTP can

determine the RSCS spool file’s origin.


System Programmer Response: Determine why SMTPis receiving RSCS files without an RSCS TagUserid orTagNodeid, and correct the problem.


Procedure Name: MakeBatchSMTPErrorFile

DTCSMT1301I Deleting Spool File from UserID atNodeID

Severity: Warning.

Explanation: This warning message is output to theSMTP batch log to indicate that a spool file from thelisted UserID@NodeID origin is being deleted, becausethe user ID started with an asterisk (*) character.


System Programmer Response: Determine the originof the mail. Normally this message can be ignored.



DTCSMT1302I Rejecting Spool File Spoolid FromUserID at NodeID

Severity: Warning.

Explanation: SMTP sends this message to the SMTPbatch log to indicate that a spool file from the listeduser ID and node ID origin is being rejected, becausethe spool file is from RSCS, and the SMTP server is notconfigured to run as a mail gateway.




Procedure Name: HandleRestrictedFile

DTCSMT1302I Rejecting command line too long

Severity: Error.

Explanation: The argument string supplied after acommand keyword exceeds the maximum allowableargument string length of 512 characters.


System Programmer Response: If the problempersists, determine what host is sending the badcommand line, and correct the SMTP server.


Procedure Name: DoCommand



|||

|

||||||

|

||

|

|

||||

|

|||

|

||

|

|

|||

|

||||

|

||

|

|

|||

|

||||

|

|

|||

|

|

|||

|

||||

|

||

|

|

|||

|

|||||

|

|

|

|

||

|

|||

|

|||

|

|

|||

DTCSMT1303I Restricting Spool File Spoolid FromUserID at NodeID

Severity: Warning.

Explanation: SMTP sends this message to the SMTPbatch log to indicate that a spool file from the listeduser ID and node ID origin is being rejected, becausethe address is in the RESTRICT list.




Procedure Name: HandleRestrictedFile

DTCSMT1308I Unregistered BSMTP Spool File fromUserID@NodeID

Severity: Warning.

Explanation: SMTP sends this message to the batchjob log to indicate that an unregistered BSMTP spoolfile was received from the listed sender and cannot beprocessed. This condition exists because the sender isnot in the SMTP SECTABLE security table.


System Programmer Response: The sender shouldobtain authorization to use the secure gateway. To dothis the sender must follow instructions in theSECURITY MEMO file, which is returned from theSMTP server machine just before this batch log record.


Procedure Name: DoMail

DTCSMT1309I Unregistered BSMTP MAIL FROM:PrintPath

Severity: Warning.

Explanation: SMTP sends this message to the batchjob log to indicate that unregistered BSMTP mail wasreceived from the listed sender and cannot beprocessed. This condition exists because the sender isnot in the SMTP SECTABLE security table.


System Programmer Response: The sender shouldobtain authorization to use the secure gateway. To dothis the sender must follow instructions in theSECURITY MEMO file, which is returned from theSMTP server machine just before this batch log record.



DTCSMT1310I Unregistered RCPT TO: mailbox

Severity: Warning.

Explanation: This message is output to the SMTPbatch log to indicate that the specified address is not aregistered secure gateway user.


System Programmer Response: Update the SMTPSECTABLE security table, as required.

Source File: SMTPRES PASCAL

Procedure Name: ProcessLocal

DTCSMT1314E Rename of orphan mail filenamefailed. The file has been sent toBadSpoolFileId and has been deleted fromthe SMTP server’s A disk.

Severity: Error.

Explanation: The specified ADDRFILE does not havean associate NOTEFILE. An error occurred when theSMTP server tried to rename the ADDRFILE to a filetype of ORPHANML. The file has been sent to theBADSPOOLFILEID given in the message and has beendeleted from the SMTP server A-disk.



Source File: SMTP

Procedure Name: CheckHardenedMail

DTCSMT1317I Looping mail xxxxnnnn NOTEFILEand ADDRFILE are renamed toxxxxnnnn LOOPMAIL and LOOPADDR


Explanation: SMTP encountered a piece of mail inwhich the number of Received lines present in theheader section of a given mail item is equal to orgreater than the MAILHOPCOUNT value in effect (asspecified in the SMTP server configuration file). Toavoid a probable mail delivery loop, the indicated mailitem has been renamed and saved by SMTP; no furtherdeliver attempts are made for this piece of mail.


System Programmer Response: Examine the xxxxnnnnLOOPMAIL file to determine the reason for the loopingmail.





|||

|

||||

|

|

|

|

|||

|

|||||

|

|||||

|

|

|||

|

|||||

|

|||||

|

|

|

||

|

|||

|

||

|

|

|||||

|

||||||

|

||

|

|

||||

|

||||||||

|

|||

|

|

|||

DTCSMT1318I Looping mail xxxxnnnn NOTEFILEand ADDRFILE process (or renamefunction) failed with return code of rc


Explanation: SMTP encountered a piece of mail inwhich the number of Received lines present in theheader section of a given mail item is equal to orgreater than the MAILHOPCOUNT value in effect (asspecified in the SMTP server configuration file). Theserver attempted to rename the indicated NOTEFILEand ADDRFILE files in order to prevent furtherdelivery attempts for this mail; however, either adisk-full condition or a RENAME command failure wasencountered.


System Programmer Response: Check the SMTPserver 191 disk to determine whether a disk-fullcondition exists. Also, ensure that the xxxxnnnnNOTEFILE is not corrupted in an obvious manner, andthat corresponding xxxxnnnn LOOPMAIL andADDRLOOP files do not already exist.



DTCSMT1511I Date Time #Connection_numberDBCSEtoA Conversion Error


Explanation: A DBCS EBCDIC to ASCII conversionerror occurred when transferring mail using thespecified connection number. The body of thetransferred mail contained invalid DBCS characters.

System Action: Program execution continues. DBCScharacters in error are transmitted unconverted.

User or Operator Response: Use the connectionnumber to determine the originator and destination ofthe invalid mail. The DEBUG statement may beconfigured in SMTP CONFIG to aid in matchingconnection number to mail originator or destination.Check the mail body to see if it contains valid DBCScharacters for the DBCS conversion type configured forthe SMTP server. See the TCP/IP Planning andCustomization, and TCP/IP User’s Guide, for moreinformation about DBCS support in SMTP.

Source File: SMTPRPLY PASCAL

Procedure Name: ResumeFillingDataBuffer

DTCSMT1512E DBCS conversion specified, but noDBCS tables could be loaded

Severity: Error.

Explanation: DBCS conversion is configured for theSMTP server, but the required DBCS translation tablecould not be loaded.

System Action: Program execution continues; DBCSconversion is disabled.

User or Operator Response: Configure a valid DBCSbinary translate table dataset in the search orderhierarchy for the required DBCS translation table. Seethe TCP/IP Planning and Customization for moreinformation about the loading and customizing ofDBCS translation tables.


Procedure Name: OpenOutputStreams

DTCSMT1513I Date Time #Connection_numberDBCSAtoE Conversion Error


Explanation: A DBCS ASCII to EBCDIC conversionerror occurred when transferring mail using thespecified connection number. The body of thetransferred mail contained invalid DBCS characters.

System Action: Program execution continues. DBCScharacters in error are transmitted unconverted.

User or Operator Response: Use the connectionnumber to determine the originator and destination ofthe invalid mail. The DEBUG statement may beconfigured in SMTP CONFIG to aid in matchingconnection number to mail originator or destination.Check the mail body to see if it contains valid DBCScharacters for the DBCS conversion type configured forthe SMTP server. See the TCP/IP Planning andCustomization, and TCP/IP User’s Guide, for moreinformation about DBCS support in SMTP.


Procedure Name: DoDbcsConversion

DTCSMT2001E Invalid Record in SMTP SECTABLE(the SMTP Security Table):

Severity: Error.

Explanation: SMTP encountered a syntax error whileprocessing the security table. The next message outputis a listing of the erroneous security table record. Thismessage is followed by one or more other messagesthat describe specific syntax or logic problems with therecord.


System Programmer Response: Correct the problemsin the security table file and restart SMTP.

Source File: SMTPSEC PASCAL

Procedure Name: SecurityTableErrors



||||

|

||||||||||

|

||||||

|

|

|||

|

||||

||

||||||||||

|

|

|||

|

|||

||

||||||

|

|

|||

|

||||

||

||||||||||

|

|

|||

|

||||||

|

||

|

|

|||

DTCSMT2003I Expecting NodeId but found none.

Severity: Error.

Explanation: The nodeid parameter was omitted on thespecified line of the SMTP SECTABLE security table.The userid and nodeid parameters are required for eachentry in the security table.


System Programmer Response: Correct the SMTPSECTABLE security table and restart SMTP.



DTCSMT2004I Primary_NickName mapping must be’Y’ or ’N’ but found: TokenStrPrimary_MBox mapping must be ’Y’ or’N’ but found: BadInput

Severity: Error.

Explanation: SMTP found a character string otherthan Y or N for the Primary_NickName or Primary_MBoxfields in the SMTP SECTABLE security file. Only thecharacters, Y and N, are valid.


System Programmer Response: Correct the SMTPSECTABLE security file, and restart SMTP.



DTCSMT2008I Unexpected characters found afternickname

Severity: Error.

Explanation: SMTP found unexpected characters afteran entry in the SMTP SECTABLE security table.


System Programmer Response: Remove the extracharacters from the SMTP SECTABLE security table, ormark the characters as a comment with the asterisk (*)character.



DTCSMT2009I Duplicate Primary_NickNamemapping detected. DuplicatePrimary_MBox mapping detected.

Severity: Warning.

Explanation: A duplicate Primary_NickName orPrimary_MBox was detected in the SMTP SECTABLEfile. Only one Primary_NickName and Primary_MBoxis allowed for each different nickname in the file.


System Programmer Response: Correct the specifiednickname entries in the SMTP SECTABLE file, andrestart SMTP.



DTCSMT2013I Special characters not allowed innickname

Severity: Error.

Explanation: The specified nickname in the SMTPSECTABLE security file contained special characters.The following characters are defined as special in RFC822 and cannot be used in nicknames:

) ( < > @ , ; : \ \ " . [ ]


System Programmer Response: Correct the specifiednickname in the SMTP SECTABLE security table, sothat it does not contain any special characters.



DTCSMT2015E Error: No primary mapping ofaddress: UserID@ Nodeid has beendefined.

Severity: Error.

Explanation: This message indicates the SMTPSECTABLE security table is incorrectly configured. Oneor more nicknames were added for the specifiedRSCSuserid and RSCSnodeid without specifying aPrimary_Mailbox. Exactly one of the nicknames must bemarked as the Primary_Mailbox with the letter Y in theprimary_mbox? field.




Procedure Name: CheckSecurityTable

DTCSMT2016E Error: No primary mapping ofnickname: nickname has been defined.

Severity: Error.

Explanation: This message indicates the SMTPSECTABLE security table is incorrectly configured. Anickname was added for the specified RSCSuserid andRSCSnodeid without specifying a Primary_Nickname.Exactly one of the RSCSuserid and RSCSnodeid pairsmust be marked as the Primary_Nickname with theletter Y in the primary_mbox? field.



||

|

||||

|

||

|

|

|||||

|

||||

|

||

|

|

|||

|

||

|

||||

|

|

||||

|

||||

|

|||

|

|

|||

|

||||

|

|

|||

|

|

||||

|

|||||||

|

||

|

|

|||

|

|||||||





DTCSMT2017E Fatal Errors found in SMTP SecurityTable...Halting!

Severity: Fatal.

Explanation: The SECURE option was specified in theSMTP CONFIG configuration file but the SMTPprogram found syntax errors in the SMTP SECTABLEfile.


System Programmer Response: Correct the specifiederrors in the SMTP SECTABLE file and restart SMTP.



DTCSMT2018E Fatal Error: Unable to find SMTPSECTABLE but SECURE option wasspecified.

Severity: Fatal.

Explanation: The SECURE option was specified in theSMTP CONFIG configuration file, but the SMTPprogram did not have access to the SMTP SECTABLEfile.


System Programmer Response: Ensure that a validSMTP SECTABLE file is accessed and restart SMTP.


Procedure Name: ReadSecurityTable

SMTP Server Unnumbered MessagesThis section contains unnumbered SMTP messages. The headers will not appearhere as they would not appear when issued.

DBCS Conversion: conversion_status


Explanation: This message indicates the DBCSconversion status for the SMTP server at initializationtime. The status indicates the DBCS conversion typethat will be used when transferring mail, or “disabled”,if DBCS conversion is not configured, or if the requiredDBCS translation table could not be loaded.

System Action: Program execution continues. DBCSconversion is either enabled, or disabled, according tothe displayed status.

User or Operator Response: If the status is“disabled”, and a DBCS translation table could not beloaded, then configure a valid DBCS binary translatetable data set in the search order hierarchy for therequired DBCS translation table. See the TCP/IPPlanning and Customization for more information aboutthe loading and customizing of DBCS translation tables.



8-bit MIME Support: YES (FileName TCPXLBIN *) |NO


Explanation: This message specifies whether 8-bitMIME support is enabled or disabled. If 8-bit MIMEsupport is enabled, then the 8-bit MIME translationtable is also displayed.





Error in SMTP NAMES file:

Severity: Error.

Explanation: This message indicates a problem withthe SMTP NAMES file. Additional error messagesshould follow to further explain the error.


System Programmer Response: Use theaccompanying error messages to determine theproblem.

Source File: SMTPARSE PASCAL

Procedure Name: ReplySyntaxError

IP Mailer Address : IPaddress


Explanation: This message specifies the current IPaddress for the IPMAILERADDRESS statement in theSMTP configuration file. If only the MAILER statementis used, the IP address is shown as ″Disabled.″







|

||

|

|

|||

|

||||

|

||

|

|

||||

|

||||

|

||

|

|||

||||

|

||||||

|||

|||||||

|

|

|||

|

||||

|

|

|

|

||

|

|||

|

|||

|

|

||

|

||||

|

|

|

|

Looping Mail Transferred to LoopingMailId

Severity: Error.

Explanation: SMTP sends this message to the consoleerror log to indicate that SMTP encountered a loopingmail condition. This condition exists because thenumber of mailing attempts has exceeded the loopingmail threshold limit. The mail in question is transferredto the listed user ID.


System Programmer Response: The user shouldexamine the piece of looping mail to see which user IDis causing the error. Because this problem frequentlyoccurs between the SMTP server and a MAILER, bothshould be examined for configuration errors.



Nickname: Nickname Address: Address

Severity: Error.

Explanation: SMTP encountered a PARSEPATH syntaxerror. The error is described by previous messages. Thismessage displays the erroneous entry in the SMTPNAMES file that caused the problem.


System Programmer Response: Correct the erroneousentry in the SMTP NAMES file before you try again.

Source File: SMTPNAME PASCAL

Procedure Name: ValidateAddress

Rcpt to unknown host: host

Severity: Warning.

Explanation: An RCPT TO: command was issued tothe listed host machine, and the SMTP server receiveda negative reply from a domain name server. If theSMTP server is not using a domain name server, theserver could not find the specified host name in the sitetables.


System Programmer Response: If the host nameexists, check the domain name server or site tables forconfiguration errors, and resend the mail message.


Procedure Name: ProcessRQR

SecRecord

Severity: Error.

Explanation: This message displays the erroneoussecurity table record.





Syntax Error: args after strcmd command: CommandLine

Severity: Error.

Explanation: SMTP sends this message to the serverconsole when SMTP receives an invalid DATA, QUIT,RSET, NOOP, TURN, or QUEU command. Thismessage indicates that the arguments with thesecommands are invalid and unnecessary. The invalidargument string is listed at the end of the message.


System Programmer Response: The sender mustcorrect the syntax before resubmitting the command, orissue the HELP command.



Syntax Error. message

Severity: Error.

Explanation: An error exists in the SMTP NAMES file.This message is usually accompanied by other errormessages, such as, Error in SMTP NAMES file:.


System Programmer Response: Correct the specifiederror in the SMTP NAMES file, and restart SMTP.



Terminating: Disk ’A’ has 800 byte blocksize.

Severity: Error.

Explanation: The results of interpreting the reply froma CMS QUERY DISK A command indicate that theA-disk block size is 800 bytes. The A-disk block sizemust be other than 800 bytes for SMTP to complete theInitVars procedure.


System Programmer Response: Back up all the fileson SMTP’s A-disk, and reformat the disk with a blocksize other than 800. See the TCP/IP Planning andCustomization for more information.


Procedure Name: InitVars

SMTP Server Unnumbered Messages


||

|

||||||

|

|||||

|

|

||

|

||||

|

||

|

|

||

|

||||||

|

|||

|

|

||

|

||

|

|

|

|

||

|

||||||

|

|||

|

|

||

|

|||

|

||

|

|

||

|

|||||

|

||||

|

|

SMTP Reply Code MessagesThis section contains SMTP reply code messages. The message headers will notappear in this section as they will not appear when the messages are issued.

451 Local error in processing

Severity: Error.

Explanation: This message is returned to the mailsender from the local host when the sender’s mail wasnot successfully delivered. This message occurs whenSMTP is unable to write a mail file to its A-diskbecause the A-disk is full.


System Programmer Response: Check the SMTPconsole for additional error messages. If the A-disk isfull, remove unnecessary files, such as old SMTP LOGs,or increase the size of the disk.



500 Command Line too long

Severity: Warning.

Explanation: You entered a command line thatexceeds the maximum allowable argumentstring-length of 512 characters.


System Programmer Response: Correct the syntaxand resubmit the command. If necessary, you canrequest online help by entering HELP.



500 Unknown command, command

Severity: Error.

Explanation: Error message returned to the senderwhen an unidentifiable command is received on theserver; the command is listed at the end of themessage. The allowable or known commands are:

DATA NOOP SENDEHLO QUEU SOMLEXPN QUIT TICKHELP RCPT TURNHELO RSET VERBMAIL SAML VRFY


System Programmer Response: The sender issues acorrect and supported SMTP command. If necessary,the user can request online help by entering HELP.


Procedure Name: NoSuchCommand

501 Syntax Error. <CR> and <LF> not permitted inQuoted Text

Severity: Error.

Explanation: This message is returned to the sender toindicate that a carriage return character or a line feedcharacter was found in a quoted string of text. Carriagereturns and line feeds are not allowed in quotedstrings, as defined in RFC 821.


System Programmer Response: Correct the quotedstring, so that it does not contain carriage returns orline feeds.


Procedure Name: QText

501 Syntax Error. message

Severity: Error.

Explanation: This message is the prefix for all syntaxerrors returned to the SMTP client machine.


System Programmer Response: Examine the incorrectcommand and additional errors to determine theproblem with the command.



501 Syntax Error. <snum> expected

Severity: Error.

Explanation: This message is returned to the sender toindicate that the SMTP server expected a valid IPaddress.


System Programmer Response: Correct the syntax tospecify a valid IP address in dotted decimal notation.


Procedure Name: DotNum

SMTP Reply Code Messages


|

501 Syntax Error. <snum> must be in range 0..255

Severity: Error.

Explanation: This message is returned to the sender toindicate that an integer value, 0 through 255, isexpected in an IP address. The IP address must be invalid dotted decimal notation.





501 Syntax Error. <snum> too long

Severity: Error.

Explanation: This message is returned to the sender toindicate that SMTP expects an IP address of example 4octets long. The IP address must be in valid dotteddecimal notation.





501 Syntax Error. ’.’ expected

Severity: Error.

Explanation: This message is returned to the sender toindicate that an IP address was not separated bydecimal points. The IP address must be in valid dotteddecimal notation.





501 Syntax Error. ’[’ expected in PathName

Severity: Error.

Explanation: This message is returned to the sender toindicate that the parsing procedure expected a leftbracket ([).


System Programmer Response: Correct the commandsyntax and try again.


Procedure Name: Element

501 Syntax Error. ’:’ Expected in Path Name

Severity: Error.

Explanation: This message is returned to the sender toindicate that the parsing procedure expected a colon (:).




Procedure Name: ADLpath

501 Syntax Error. ’@’ expected

Severity: Error.

Explanation: This message is returned to the sender toindicate that the parsing procedure expected an at sign(@).




Procedure Name: MailBox

501 Syntax Error. ’@’ Expected in Source Route

Severity: Error.

Explanation: This message is returned to the sender toindicate that the parsing procedure expected an at sign(@) at this point in the source route part of the mailaddress.




Procedure Name: AtDomain

501 Syntax Error. ’″’ expected

Severity: Error.

Explanation: This message is returned to the sender toindicate that the parsing procedure expected a quotemark (″).




Procedure Name: LocalPart



501 Syntax Error. ’BODY’ parameter cannot berepeated

Severity: Error.

Explanation: This message is returned to the sender ifthere is more than one BODY parameter in the MAILFROM command.




Procedure Name: ParseSrvcExtParms

501 Syntax Error. ’BODY’ value is not valid

Severity: Error.

Explanation: This message is returned to the sender ifthe type value given for the BODY parameter is not7BIT or 8BITMIME. BODY is a parameter for the MAILFROM command.





501 Syntax Error. Domain name cannot end with ’-’

Severity: Error.

Explanation: You cannot terminate a domain namewith a hyphen (-).




Procedure Name: Name

501 Syntax Error. Domain name missing

Severity: Error.

Explanation: This message is returned to the sender asthe reply to an invalid HELO or EHLO command. Thesame message is also displayed on the server outputdevice without the 501 message prefix.


System Programmer Response: Specify a valid hostname after the HELO or EHLO command.


Procedure Name: DoHeloOrEhlo

501 Syntax Error. Domain name too long

Severity: Error.

Explanation: This message is returned to the sender asthe reply to an invalid HELO or EHLO command. Youspecified a domain name that was greater than 256characters. The same message is also displayed on theserver output device without the 501 message prefix.




Procedure Name: DoHeloOrEhlo

501 Syntax Error. Incomplete Address

Severity: Error.

Explanation: You specified a backslash mark (\),without a number between 0 and 127 following thebackslash. To specify an ASCII character, you mustenter a backslash followed by the integer between 0and 127 that indicates the ASCII character.




Procedure Name: PlainString

501 Syntax Error. Incomplete Address

Severity: Error.

Explanation: The parsing procedure did not expect anull argument at this point.





501 Syntax Error. Invalid LocalPart of Address

Severity: Error.








501 Syntax Error. Invalid Path Specification

Severity: Error.





Procedure Name: ParsePath

501 Syntax Error. Missing Domain Name

Severity: Error.

Explanation: This message is returned to the sender toindicate that a right angle bracket (>) was found beforea domain name had been defined in the parsingprocedure.





501 Syntax Error. Missing equal sign after ’BODY’keyword

Severity: Error.

Explanation: This message is returned to the sender ifthe BODY keyword for the MAIL FROM command isnot followed by an equal sign.





501 Syntax Error. Missing equal sign after ’SIZE’keyword

Severity: Error.

Explanation: This message is returned to the sender ifthe SIZE keyword for the MAIL FROM command isnot followed by an equal sign.





501 Syntax Error. Missing host name, ’@’ expected

Severity: Error.

Explanation: The parsing procedure did not find an atsign (@) before the expected host name string.





501 Syntax Error. Missing number of bytes for ’SIZE’parameter

Severity: Error.

Explanation: This message is returned to the sender ifthere is no byte value given for the SIZE parameter forthe MAIL FROM command.





501 Syntax Error. Missing value for ’BODY’ parameter

Severity: Error.

Explanation: This message is returned to the sender ifthere is no type value given for the BODY parameterfor the MAIL FROM command.





501 Syntax Error. Missing User name

Severity: Error.

Explanation: The parsing procedure did not expect anull argument for a user name at this point.







501 Syntax Error. Must use ’MAIL FROM:’

Severity: Error.

Explanation: You entered an invalid MAIL command.You must use the MAIL FROM: command.


System Programmer Response: Use the MAIL FROMcommand and try again.



501 Syntax Error. Must use ’RCPT TO:’

Severity: Error.

Explanation: You entered an invalid RCPT command.


System Programmer Response: Use the RCPT TOcommand and try again.


Procedure Name: DoRcpt

501 Syntax Error. Must use ’VERB ON’ or ’VERB OFF’

Severity: Error.

Explanation: You entered an invalid VERB command.You must use the VERB ON or VERB OFF command.ON or OFF are the only valid parameters for the VERBcommand.


System Programmer Response: Specify either VERBON or VERB OFF and try again.


Procedure Name: DoVerb

501 Syntax Error. Need args after ’MAIL’ command

Severity: Error.

Explanation: You entered an invalid MAIL FROMcommand. You must specify a valid mail address afterthe MAIL FROM command.





501 Syntax Error. Need args after ’RCPT’ command

Severity: Error.

Explanation: You entered an invalid RCPT TOcommand. You must specify a valid mail address afterthe RCPT TO command.





501 Syntax Error. Need args after Strcmd command

Severity: Error.

Explanation: You entered an invalid VRFY or EXPNcommand. You must follow the VRFY and EXPNcommands with a user ID or mailing list.




Procedure Name: DoVrfyExpn

501 Syntax Error. Need args after ’TICK’ command

Severity: Error.

Explanation: You entered an invalid TICK command.You must specify a text string after the TICK command.




Procedure Name: DoTick

501 Syntax Error. Need args after ’VERB’ command

Severity: Error.

Explanation: You entered an invalid VERB command.You must specify either ON or OFF after the VERBcommand.




Procedure Name: DoVerb



501 Syntax Error. No Args after strcmd command

Severity: Error.

Explanation: You entered an invalid DATA, QUIT,RSET, NOOP, TURN, or QUEU command. Argumentsare invalid or unnecessary with these commands.





501 Syntax Error. Non-numeric ’SIZE’ value is notvalid

Severity: Error.

Explanation: This message is returned to the sender ifa non-numeric byte value is given for the SIZEparameter for the MAIL FROM command.





501 Syntax Error. Null Recipient Invalid

Severity: Error.

Explanation: You entered an invalid RCPT TOcommand. The parameter you specified after the RCPTTO: command was null. You must specify a valid mailaddress after the RCPT TO command.





501 Syntax Error. Number Expected

Severity: Error.

Explanation: The parsing procedure expected anumber (0..9) at this point.




Procedure Name: Number

501 Syntax Error. Only ListId or Userid allowed asargument to this command

Severity: Error.

Explanation: You entered an invalid VRFY or EXPNcommand. You must enter a user ID or mailing listafter the VRFY and EXPN commands.





501 Syntax Error. Path too long

Severity: Error.

Explanation: The path you specified in a MAIL FROMor RCPT TO command exceeded the limit of 256characters.





501 Syntax Error. Quoted text is a null string

Severity: Error.

Explanation: The parsing procedure found nothingbetween two quote marks ("").




Procedure Name: Qtext

501 Syntax Error. ’SIZE’ parameter cannot be repeated

Severity: Error.

Explanation: This message is returned to the sender ifthere is more than one SIZE parameter in the MAILFROM command.







501 Syntax Error. Special chars only with Escape Char

Severity: Error.

Explanation: The parsing procedure did not expect aspecial character other than an at sign (@), right anglebracket (>), or a decimal point (.).





501 Syntax Error. Start Domain with ’a’..’z’, ’A’..’Z’, or’0’..’9’

Severity: Error.

Explanation: You entered an invalid character in adomain name. Valid host names must start with anASCII letter or number.




Procedure Name: Name

501 Syntax Error. Start Path name with ’<’

Severity: Error.

Explanation: The parsing procedure expected a leftangle bracket (<) to initiate a mail address path.





501 Syntax Error. Unexpected end of Domain Name

Severity: Error.

Explanation: You did not specify a complete and validmail address path.




Procedure Name: Element

501 Syntax Error. Unexpected Token result

Severity: Error.

Explanation: You did not specify a complete and validmail address path.





501 Syntax Error. Unterminated Quoted String

Severity: Error.

Explanation: You did not end a quoted string with therequired close quote mark (").




Procedure Name: Qtext

502 Command command not implemented yet

Severity: Error.

Explanation: This message is returned to the senderwhen a SEND, SAML, SOML, or TURN command isreceived on the server. The above commands areknown to SMTP but are not supported.


System Programmer Response: Issue a correct andsupported SMTP command. If necessary, you canrequest online help by entering HELP.


Procedure Name: NotYetImplemented

503 ’HELO’ or ’EHLO’ must be first command insession

Severity: Warning.

Explanation: You already issued a valid HELO orEHLO command, or you tried to issue a MAIL FROMor RCPT TO command before issuing a HELO orEHLO command.

System Action: This command is ignored. SMTPcontinues.

System Programmer Response: Verify that your SMTPcommands are sent in the correct order.


Procedure Name: DoMail, DoRcptTo, and DoData



503 No Recipients specified

Severity: Warning.

Explanation: You tried to enter data with the DATAcommand before you issued the RCPT command.

System Action: The DATA command is ignored;SMTP continues.



Procedure Name: DoData

503 No Sender specified

Severity: Warning.

Explanation: You tried to enter data with the DATAcommand before you issued the MAIL command.

System Action: The DATA command is ignored;SMTP continues.



Procedure Name: DoData

503 Sender already specified

Severity: Warning.

Explanation: You already issued a valid MAILcommand. You tried to issue the identical commandunnecessarily.

System Action: The MAIL command is ignored; SMTPcontinues.




503 Sender must be specified before recipients

Severity: Warning.

Explanation: You issued an RCPT command beforeyou issued the MAIL command.

System Action: The RCPT command is ignored; SMTPcontinues.




504 HELP topic unknown

Severity: Warning.

Explanation: You requested HELP on an unknowntopic.


System Programmer Response: Issue HELP for a listof the valid SMTP commands.


Procedure Name: DoHelp

550 Cannot accept mail for this host; MX records willcause loop.

Severity: Error.

Explanation: The SMTP server sends this message tothe client indicating that the local host cannot acceptmail for the local host because the CheckHomeListprocedure has determined that accepting mail exchangerecords would cause a looping mail condition.


System Programmer Response: Determine what MXrecords are stored in the domain name server, and whythey are causing a loop. Tell the domain name serveradministrator about the problem.



550 Cannot accept mail for this host; Next MX site notdefined.

Severity: Error.

Explanation: SMTP has evaluated all the possible MXrecords for the host, and eliminated all the necessaryhosts with a lower preference than this SMTP server.After this processing SMTP did not have any MXrecords remaining for this host, and did not knowwhere to deliver the mail. This is a configuration errorin either SMTP or the domain name server, so the mailis rejected.


System Programmer Response: Determine what MXrecords are stored in the domain name server, and whySMTP was unable to determine the final recipient. Tellthe domain name server administrator about theproblem.





550 Host hostname Unknown

Severity: Error.

Explanation: The SMTP server sends this message tothe client indicating that the host name in the mailaddress is unknown. SMTP determined that thisaddress is not the local host and is not an RSCS host.The mail is rejected for this mail address.


System Programmer Response: Determine why thehost name is not valid. If the address is supposed to bean SMTP host, verify that the domain name server orsite tables have the correct entries. If the address issupposed to be an RSCS host, verify that theSMTPRSCS HOSTINFO file is up-to-date and containsthe correct entries.



550 Mail forwarding not supported

Severity: Warning.

Explanation: The SMTP server sends this message tothe client indicating that the client tried to source routemail through this SMTP gateway. This gateway iscurrently in SECURE mode and does not supportsource routing.

System Action: The mail is rejected; SMTP continues.

System Programmer Response: Do not performsource routing through this gateway. Determine analternative path to deliver your mail.



550 Mailing list CommandLine Nonexistent550 MailBox CommandLine Nonexistent

Severity: Warning.

Explanation: The mailing list or mailbox yourequested does not exist on the local host.


System Programmer Response: Specify a validmailing address that exists on the local host.



550 Source routing not permitted in gateway

Severity: Warning.

Explanation: The SMTP server sends this message tothe client indicating that the client tried to source route

mail through this SMTP gateway. This gateway iscurrently in SECURE mode and does not supportsource routing.

System Action: The mail is rejected.

System Programmer Response: Do not performsource routing through this gateway. Determine analternative path to deliver your mail. SMTP continues.



550 Spool File Origin: <UserID@NodeID> does notmatch Sender’s Address: PrintPath

Severity: Warning.

Explanation: Unregistered BSMTP mail was receivedfrom the listed sender at the listed origin and cannot beprocessed.


System Programmer Response: Follow theinstructions in the SECURITY MEMO file that theSMTP server machine returned to you just prior to thismessage.



550 Unable to find A records for any MX sites for therecipient host.

Severity: Error.

Explanation: The SMTP server sends this message tothe client to indicate that the local host cannot find anA record that corresponds to an MX record for thedestination host. This is a configuration error in thedomain name server.

System Action: The mail is rejected. SMTP continues.

System Programmer Response: Determine what MXrecords are stored in the domain name server, and whySMTP was unable to find a corresponding A record forone or more of the MX records. Tell the domain nameserver administrator about the problem.



550 Unable to resolve recipient address for RetryAgeduration

Severity: Warning.

Explanation: The SMTP server sends this message tothe client to indicate that the local host was unable toresolve a recipient address for the listed duration oftime (number of days, hours, or minutes).



System Action: The mail in question is returned to thesender. SMTP continues.

System Programmer Response: Determine why theSMTP server was unable to resolve the mail address.SMTP sends this message when the name server isdown, or connectivity to the name server through theinternet is unavailable.


Procedure Name: SendRQR

550 User UserName Unknown

Severity: Error.

Explanation: The SMTP server sends this message tothe client to indicate that the listed user ID was notfound on the local host. This error is returned if theuser ID is not POSTMASTER, a user ID in the SMTPNAMES file, or a valid user ID, as determined by theCP SPOOL PUNCH TO command.


System Programmer Response: You specified a userID that is not known on the local system. Check themail address for spelling mistakes. Check the local hostto see if the user ID exists.


Procedure Name: ProcessLocal

550 User UserID@NodeID on Restricted List

Severity: Warning.

Explanation: SMTP sends this message to the client toindicate that the listed Userid and NodeId origin isrejected, because the address is in the RESTRICT list.




Procedure Name: DoRestricted

550 User RSCSUser@RSCSHost is not a registeredgateway user

Severity: Error.

Explanation: The SMTP server sends this message tothe client to indicate that the listed user ID is not aregistered secure gateway user, and is not in the SMTPSECTABLE security table.

System Action: The mail is rejected. SMTP continues.

System Programmer Response: Update the SMTPSECTABLE security table as necessary, or inform theuser that they are not authorized to use this SMTPsecure gateway.



552 Mail file too large

Severity: Error.

Explanation: The local host sends this message to thesender when the sender’s mail file exceeds themaximum length specified by the MAXMAILBYTESoption in the configuration file.


System Programmer Response: Shorten the mail file,or subdivide the long file into two or more shorter filesthat are within the existing MAXMAILBYTESlimitations. You can increase the value for theMAXMAILBYTES option in the configuration file andtry again.



552 Message size exceeds fixed maximum messagesize

Severity: Error.

Explanation: This message is returned to the sender ifthe MAIL FROM command for a piece of mail arrivingfrom a TCP connection contains a SIZE value thatexceeds the maximum length specified by theMAXMAILBYTES option in the configuration file.


System Programmer Response: Shorten the mail file,or subdivide the long file into two or more shorter filesthat are within the existing MAXMAILBYTESlimitations. You can increase the value for theMAXMAILBYTES option in the configuration file andtry again.



555 Unknown MAIL FROM parameter, parameter

Severity: Error.

Explanation: This message is returned to the sender ifthe MAIL FROM command contains an unidentifiableparameter; the parameter is listed at the end of themessage. The MAIL FROM command syntax is:MAIL FROM: <Sender_path_address> [SIZE=number_of_bytes]

[BODY=7BIT/8BITMIME]


System Programmer Response: Issue a correct MAILFROM command that contains supported parameters.





555 8-bit MIME support is not enabled

Severity: Error.

Explanation: This message is returned to the sender ifthe MAIL FROM command contains the BODYparameter and the value specified is 8BITMIME, andthe SMTP server does not have 8-bit MIME supportenabled.


System Programmer Response: Enable the 8-bitMIME support using the 8BITMIME configurationstatement.



SMTPRSCS MessagesThis section contains SMTPRSCS messages.

DTCSMR2009E Invalid FileName Specification

Severity: Error.

Explanation: The filename specified on the SMTPRSCScommand is either missing or is greater than 8characters. A filename of 8 characters or less must bespecified on the SMTPRSCS command.

System Action: SMTPRSCS halts

System Programmer Response: Reissue theSMTPRSCS command specifying a valid filename,filetype, and filemode.

Source File: SMTPRSCS

Procedure Name: VerifyVMFile

DTCSMR2010E Invalid FileType Specification

Severity: Error.

Explanation: The filetype specified on the SMTPRSCScommand is either missing or is greater than 8characters. A filetype of 8 characters or less must bespecified on the SMTPRSCS command.

System Action: SMTPRSCS halts.




DTCSMR2011E Invalid FileMode Specification

Severity: Error.

Explanation: The filemode specified on theSMTPRSCS command is greater than 2 characters. Afilemode of 2 characters or less must be specified onthe SMTPRSCS command.





DTCSMR2012E Garbage detected at end ofSMTPRSCS command.

Severity: Error.

Explanation: More than 3 parameters were specifiedon the SMTPRSCS command. The SMTPRSCScommand takes 3 parameters: a filename, filetype, andfilemode.





DTCSMR2013E Unable to find input file: FileNameFileType FileMode

Severity: Error.

Explanation: The RSCS configuration file specified onthe SMTPRSCS command could not be found on anyaccessed disk.


System Programmer Response: Ensure that the inputfile is available on an SMTP accessed disk and reissuethe SMTPRSCS command.



DTCSMR2014W Warning: Duplicate entry: Node

Severity: Warning.

Explanation: A duplicate name exists in the input filebeing processed. Both entries are added to the hashtable.

System Action: SMTPRSCS continues.

System Programmer Response: If the input file is inerror, remove the duplicate name entry.



|

|||

|

||||

|

|||

|

|

||

|

||||

|

|||

|

|

||

|

||||

|

|||

|

|

|||

|

||||

|

|||

|

|

|||

|

|||

|

|||

|

|

||

|

|||

|

||

Source File: SMTPRSCS PASCAL

Procedure Name: Insert

DTCSMR2015E Invalid system type specified:BadSysType

Severity: Error.

Explanation: You entered an optionalSpoolSystemType that was not valid. These three arethe only valid options: RSCS, JES2 and JES3.


System Programmer Response: Rerun the programwith the correct SpoolSystemType.


Procedure Name: ParseOptionalPart

DTCSMR2016E Unrecognized options: BadOption

Severity: Error.

Explanation: This error message indicates thatSMTPRSCS found additional characters in the optionstring after it found one of the valid options.


System Programmer Response: Rerun the SMTPRSCSprogram using the correct specified format. See theTCP/IP Planning and Customization for moreinformation.


Procedure Name: ParseOptionalPart

DTCSMR2022E Unrecognized parameters:BadParameter

Severity: Error.

Explanation: SMTPRSCS found a character that wasnot an open parenthesis in the input parameter stringafter the file mode.


System Programmer Response: Rerun the SMTPRSCSprogram using the correct, specified format. See theTCP/IP Planning and Customization for moreinformation.


Procedure Name: ProcessCommandLine

DTCSMR2024E Found more than MaxNodes RSCSnodes!

Severity: Error.

Explanation: SMTPRSCS found more than 10000 JES2or JES3 nodes. This exceeds the maximum allowable

number of nodes specified by the MaxNodes constant.


System Programmer Response: Increase theMaxNodes constant in SMTPRSCS PASCAL to thedesired value, recompile the source, re-link theexecutable module, and rerun SMTPRSCS.


Procedure Name: EndofGame

DTCSMR2026E Increase the constant ’MaxNodes’ inSMTPRSCS and try again.

Severity: Error.

Explanation: This message states that a code changemust be made in the SMTPRSCS PASCAL program.The MaxNodes constant must be set equal to a valuegreater than its present setting of 10000.


System Programmer Response: Increase theMaxNodes constant in SMTPRSCS PASCAL to a greatervalue, recompile the source, re-link the executablemodule, and rerun SMTPRSCS.


Procedure Name: EndofGame

DTCSMR2027W RSCS Node Name: RSCStokentruncated to: VMNodeidLen

Severity: Warning.

Explanation: Warning indication for an RSCS directoryfile entry of LOCAL, LINK or ROUTE. The RSCS nodename you specified after LOCAL, LINK, or ROUTEexceeded 8 characters and was truncated to the listedfirst 8 characters.


System Programmer Response: Correct the RSCSnode name, so that it is 8 characters or less.


Procedure Name: ParseRSCSDirectFile

DTCSMR2032E No nodes found in FileName FileTypeFileMode. SMTPRSCS HOSTINFO willnot be created.

Severity: Error.

Explanation: There were no RSCS network nodesfound in the specified input file, so the SMTPRSCSHOSTINFO file cannot be created.


System Programmer Response: Reissue theSMTPRSCS command specifying an input file thatcontains valid RSCS network nodes.

SMTPRSCS Messages


|

|

|||

|

|||

|

||

|

|

||

|

|||

|

||||

|

|

|||

|

|||

|

||||

|

|

|||

|

||

|

|

||||

|

|

|||

|

||||

|

||||

|

|

|||

|

|||||

|

||

|

|

||||

|

|||

|

|||

Source File: SMTPRSCS Procedure Name: BuildHashTable

SMTPRSCS Messages


| |

|

SMTPRSCS Messages


Chapter 17. SNALINK Messages

SNALNK001I date time : Usage SNALINK<DEBUG> tcpip_name applid < xrusize< maxsession < retry < sessiontype > >> >

Explanation: SNALINK was called with invalid ormissing invocation parameters. The correct invocationsequence is given in the text of the message. Note thatthe name of the TCPIP virtual machine and the localLU name are required parameters.

System Action: The program terminates execution.

User or Operator Response: If the invocation wasspecified from the command line, reissue the commandwith the correct parameters. If the improper orincomplete invocation string was supplied by thePROFILE GCS, make corrections as necessary in thatfile and restart the virtual machine running theSNALINK application. See the TCP/IP Planning andCustomization book for more information aboutconfiguring and operating the SNALNKA VirtualMachine.

Source File: SNALINK ASSEMBLE


SNALNK002I date time {lu} : Invalid mx RU size code

Explanation: An optional third argument to SNALINKis the maximum RU size code. This parameter wasspecified on the command line, but is not valid. Formore information, see the VTAM® Programmer’s Manual.

System Action: The program terminates execution.

User or Operator Response: Reissue the commandwith the corrected parameters.

Source File: snalink assemble


SNALNK003I date time {lu} : Can not obtain storagefor path index table

Explanation: SNALINK could not allocate memory forthe path index table.

System Action: SNALINK abends.


System Programmer Response: Ensure the SNALINKvirtual machine is defined correctly.



SNALNK004I date time {lu} : Error error in IUCVINISET

Explanation: SNALINK encountered an error issuingan IUCVINI SET request to initialize IUCV.



System Programmer Response: Check the SNALINKdefinition, and ensure that it has IUCV authority.



SNALNK005I date time {lu} : Error error IN VTAMOPEN

Explanation: SNALINK encountered an error issuing aVTAM OPEN request.


User or Operator Response: Ensure VTAM isoperational.

System Programmer Response: Contact your localVTAM administrator.


Procedure Name: main.

SNALNK008I date time {lu} : TPEND exit called withreason value

Explanation: SNALINK exits with the indicatedreason code.

System Action: SNALINK exits.


System Programmer Response: Correct the problemindicated by the reason code.



SNALNK010I date time {lu} : Can not free path indextable storage

Explanation: SNALINK encountered an error freeingmemory.

System Action: SNALINK terminates.


System Programmer Response: Check the VM systemfor system problems.




SNALNK011I date time {lu} : Unexpected iptype typereceived

Explanation: SNALINK received an IUCV interruptwith an unexpected or out-of-range type.



System Programmer Response: This error indicates aprobable TCP/IP code problem.


Procedure Name: prociucv

SNALNK012I date time {lu} : IUCV path path severed

Explanation: SNALINK received a SEVER interruptfrom TCPIP.

System Action: The indicated IUCV path is severed,and the associated VTAM session is closed.

User or Operator Response: This condition is normalif the link was stopped or TCPIP was not running.Otherwise, this condition is abnormal and is probablycaused by a problem with TCPIP.


Procedure Name: sever

SNALNK013I date time {lu} : Can’t find CONNBLOKfor severed path path

Explanation: SNALINK received a SEVER interruptfrom TCPIP, but could not find the associatedconnection in its tables.

System Action: The connection is severed, andSNALINK execution continues.


System Programmer Response: This messageindicates a probable TCP/IP code problem. Contact theIBM Support Center.


Procedure Name: sever

SNALNK014I date time {lu} : PENDCONN receivedfrom wrong TCPIP id id

Explanation: SNALINK received a ConnectionPending interrupt from a TCPIP ID other than the onespecified on the command line.

System Action: SNALINK severs the pendingconnection and continues execution.


System Programmer Response: Check Profile GCS(VM) for the correct TCPIP user ID.


Procedure Name: pendconn

SNALNK015I date time {lu} : Cannot connect to LULU_name -- No more CONNBLOKs!

Explanation: SNALINK does not have sufficient datastructures (CONNBLOKs) allocated to service apending connection.

System Action: SNALINK severs the pendingconnection and continues execution.


System Programmer Response: Increase themaximum connections allowed. If existing connectionsare later closed, resources are freed to allow SNALINKto service this connection.



SNALNK016I date time {lu} : Severing pending connbecause existing session not killed

Explanation: SNALINK received a ConnectionPending interrupt for this LU. However, a connectionalready exists for this LU.

System Action: This pending connection is severed,and SNALINK continues

User or Operator Response: No action is necessary ifthe connection you want is up; otherwise, stop andrestart SNALINK.

System Programmer Response: This error indicatesthat TCPIP is out of sync or that there is a codeproblem. execution.



SNALNK019I date time {lu} : COMPMSG showsnon-zero IUCV audit field value

Explanation: SNALINK received a Message CompleteIUCV interrupt, with a nonzero audit field, indicatingan error.

System Action: The associated connection is closed,and SNALINK continues execution.


System Programmer Response: Probable TCP/IP codeproblem.


SNALINK Messages


Procedure Name: Compmsg

SNALNK020I date time {lu} : Zero UWORD field onCOMPMSG or PENDMSG interrupt

Explanation: SNALINK received a Message Pendingor Message Complete IUCV interrupt with noassociated connection block (CONNBLOK).



System Programmer Response: This messageindicates a possible TCPIP or VTAM problem Tell yourlocal VTAM administrator.


Procedure Name: compmsg/pendmsg

SNALNK021I date time {lu} : Unexpected GENTYPEvalue found

Explanation: SNALINK encountered an invalidGENTYPE value when

System Action: SNALINK abends. processing aVTAM exit.


System Programmer Response: This error indicates apossible TCP/IP code problem.


Procedure Name: procvtam

SNALNK022I date time {lu} : Unexpected control fieldvalue IN SCIP exit

Explanation: SNALINK encountered an invalidcontrol field in an SCIP information block, whileSNALINK was either acting as an SLU for a connectionand waiting for the PLU to establish the connection, orreceiving an UNBIND request.

System Action: SNALINK ignores the SCIP exit andresumes execution.

User or Operator Response: Tell your VTAMadministrator.


Procedure Name: vtamscip

SNALNK023I date time {lu} : Rejecting bind from plu- no IUCV found

Explanation: SNALINK received a BIND request fromthe indicated Primary LU. It is rejecting the BINDrequest because it could not find an associated pendingIUCV connection in its tables.

System Action: Bind is rejected.

User or Operator Response: Use the NETSTATcommand to ensure that TCPIP started SNALINK.


Procedure Name: scipbind

SNALNK024I date time {lu} : Rejecting bind - alreadyhave receive session

Explanation: SNALINK received a BIND request foran LU on which it has already establishedcommunication.

System Action: The BIND is not accepted.

User or Operator Response: Tell your VTAMcoordinator.

System Programmer Response: This error indicates apossible VTAM problem.


Procedure Name: scipbind

SNALNK026I date time {lu} : Error in MODCB NIBfor receive session. R15 value R0 value

Explanation: SNALINK encountered an errormodifying a Network Information Block in preparationfor an OPNSEC call to accept a BIND for this LU.


User or Operator Response: See your VTAMadministrator.



Procedure Name: scipfoun

SNALNK029I date time {lu} : Zero user word in SCIPexit for UNBIND

Explanation: SNALINK encountered an user wordcontaining zero in an UNBIND request, indicating anull connection block address.

System Action: The request is not processed.


System Programmer Response: This error indicates apossible TCPIP/VTAM problem. Tell your local VTAMadministrator.


Procedure Name: scipunbd

SNALINK Messages

Chapter 17. SNALINK Messages 259

SNALNK030I date time {lu} : CID in SCIP UNBINDparm list not found

Explanation: SNALINK received an UNBIND requestthat was not associated with either the send or receivesession on its LU.

System Action: The request is not processed.


System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See theVTAM console for more information.


Procedure Name: scipunbd

SNALNK031I date time {lu} : TESTCB shows sendsession not established

Explanation: SNALINK received a VTAM OPNDSTEXIT interrupt specifying a session that has not beenestablished.

System Action: SNALINK ends the connection.


System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem.


Procedure Name: vtamopnd

SNALNK032I date time {lu} : OPNDST exit can’t findCONNBLOK. RPL addr address

Explanation: SNALINK received a VTAM OPNDSTEXIT interrupt for which it has no associatedconnection block.



System Programmer Response: This error indicates aprobable TCP/IP or VTAM code problem.


Procedure Name: vtamopnd

SNALNK034I date time {lu} : TESTCB shows receivessession not established

Explanation: SNALINK received a VTAM OPNSECEXIT interrupt specifying a session that has not beenestablished.



System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See yourlocal VTAM administrator.


Procedure Name: vtamopns

SNALNK035I date time {lu} : OPNSEC exit can’t findCONNBLOK. RPL addr address

Explanation: SNALINK received a VTAM OPNSECEXIT interrupt for which it has no correspondingconnection block. SNALINK abends.



System Programmer Response: This error indicates aprobable TCP/IP or VTAM code problem.


Procedure Name: vtamopns

SNALNK037I date time {lu} : SEND exit finds zeroRPLUSFLD

Explanation: SNALINK received a VTAM SEND EXITinterrupt with a null connection block pointer.



System Programmer Response: This error indicates aprobable TCPIP or VTAM problem.


Procedure Name: vtamsend

SNALNK038I date time {lu} : RECEIVE-ANY showsRESPOND value CONTROL ctl RH value

Explanation: SNALINK handled a RECEIVE-ANYinterrupt with the indicated fields.

System Action: SNALINK ends the connection, if oneexists;


System Programmer Response: Tell your VTAMcoordinator. otherwise, the interrupt is ignored.


Procedure Name: rcvisany

SNALNK039I date time {lu} : Chaining err: Flags flgBuffer buf Pointer ptr

Explanation: SNALINK encountered an inconsistencyin its buffer chain.




SNALINK Messages



Procedure Name: rcvchker

SNALNK040I date time {lu} : RECEIVE exit finds zeroRPLUSFLD

Explanation: SNALINK encountered a VTAMRECEIVE EXIT interrupt with a null connection blockpointer.



System Programmer Response: This error indicates aprobable TCPIP or VTAM problem.


Procedure Name: vtamrcv

SNALNK042I date time {lu} : CLSDST exit can’t findCONNBLOK. RPL addr address

Explanation: SNALINK received a VTAM CLSDSTEXIT interrupt with an invalid connection blockpointer.


User or Operator Response: Restart SNALINK



Procedure Name: vtamclsd

SNALNK043I date time {lu} : TERMSESS exit can’tfind CONNBLOK. RPL addr address

Explanation: SNALINK received a VTAM TERMSESSEXIST interrupt with an invalid connection blockpointer.




Procedure Name: vtamterm

SNALNK044I date time {lu} : LOSTERM reason valuefor receive session

Explanation: SNALINK received a VTAM LOSTERMEXIT interrupt, indicating this LU lost its receivesession for the indicated reason code.


User or Operator Response: Check your hardware orVTAM for problems.


Procedure Name: vtamlost

SNALNK045I date time {lu} : LOSTERM reason valuefor send session

Explanation: SNALINK received a VTAM LOSTERMEXIT interrupt, indicating this LU lost its receivesession for the indicated reason code.





SNALNK046I date time {lu} : Zero CONNBLOK ptr inLOSTERM exit, reason value

Explanation: SNALINK received a VTAM LOSTERMEXIT interrupt with a null connection block pointer.



System Programmer Response: This error indicates apossible VTAM or TCPIP problem. See your localVTAM administrator.



SNALNK047I date time {lu} : CID in LOSTERM parmlist not found, reason value

Explanation: SNALINK received a VTAM LOSTERMEXIT interrupt for which it has no parameter list.

System Action: SNALINK ignores the interrupt.





SNALNK048I date time {lu} : NSEXIT CLEANUPrequest for receive session

Explanation: SNALINK received a VTAM NSEXITinterrupt with a cleanup request for this LU’s receivesession.




SNALINK Messages


Procedure Name: vtamns

SNALNK049I date time {lu} : NSEXIT CLEANUPrequest for send session

Explanation: SNALINK received a VTAM NSEXITinterrupt with a cleanup request for this LU’s sendsession.






SNALNK050I date time {lu} : Zero CONNBLOK ptr inNSEXIT exit

Explanation: SNALINK received a VTAM NSEXITinterrupt with a null connection block pointer.



System Programmer Response: This error indicates apossible TCPIP or VTAM problem Tell your localVTAM administrator.



SNALNK051I date time {lu} : CID in NSEXIT parmlist not found

Explanation: SNALINK received a VTAM NSEXITinterrupt for which an associated parameter list couldnot be found.

System Action: SNALINK ignores the interrupt.





SNALNK053I date time {lu} : Error in MODCB NIBfor send session. R15 value R0 value

Explanation: SNALINK received a VTAM OPNDSTinterrupt, but encountered an error executing theOPNDST. An error indication is returned to the caller.



System Programmer Response: This error indicates apossible TCP/IP code problem


Procedure Name: dovtopnd

SNALNK054I date time {lu} : Cannot issue OPNDST -Previous OPNDST active

Explanation: SNALINK encountered an errorprocessing a VTAM OPNDST request. This error is thatthe associated request parameter list (RPL) is in use,indicating a previous OPNDST is active.

System Action: SNALINK does not process thisrequest.


System Programmer Response: Possible TCP/IP codeproblem.


Procedure Name: dovtopnd

SNALNK056I date time {lu} : Error error acceptingIUCV path path

Explanation: SNALINK encountered an error in anIUCV ACCEPT request.

System Action: SNALINK ends the current connectionand returns to its caller.




Procedure Name: doiucacp

SNALNK057I date time {lu} : Error error sending onIUCV path path

Explanation: SNALINK encountered an error sendingdata on the indicated IUCV path.

System Action: SNALINK ends the currentconnection.


System Programmer Response: This error indicates apossible system problem.


Procedure Name: doiucsnd

SNALNK058I date time {lu} : Error error receiving onIUCV path path

Explanation: SNALINK encountered an error sendingdata on the indicated IUCV path.

SNALINK Messages


System Action: SNALINK ends the currentconnection.

User or Operator Response: Ensure that TCPIP isoperational.



Procedure Name: doiucrcv

SNALNK059I date time {lu} : Error error severingIUCV path path

Explanation: SNALINK encountered an error severingthe indicated IUCV path.




Procedure Name: dosever

SNALNK060I date time {lu} : Error error in VTAMCLOSE

Explanation: SNALINK encountered an error closingan ACB.




Procedure Name: closeacb

SNALNK061I date time {lu} : Error in GENCB RPL.R15 value R0 value

Explanation: SNALINK received an error from aGENCB RPL call.

System Action: SNALINK resumes execution.


System Programmer Response: Check errorindication. More errors can result.


Procedure Name: setupcon

SNALNK062I date time {lu} : Error in GENCB NIB.R15 value R0 value

Explanation: SNALINK received an error from aGENCB NIB call.

System Action: SNALINK resumes execution.


System Programmer Response: Check the errorindication. More errors can result.


Procedure Name: setupcon

SNALNK063I date time {lu} : function err. R15 value R0value RTNCD value FDBK2 value

Explanation: SNALINK encountered an error in theindicated function. The associated sense code returnedby VTAM is displayed.

System Action: Based on the sense code, TCPIPretries, ends the session, or takes no action.


System Programmer Response: Tell your VTAMadministrator.


Procedure Name: prtrpler

SNALNK064I date time {lu} : function CHECK err. R15value R0 value RTNCD value FDBK2 value

Explanation: SNALINK encountered an error in theindicated function. The associated sense code returnedby VTAM is displayed.

System Action: Based on the sense code, TCPIPretries, ends the session, or takes no action.


System Programmer Response: Tell your VTAMadministrator.


Procedure Name: prtchker

SNALNK065I date time {lu} : function sense: SSENSEI,SSENSMU, USENSEI: value date time {lu}: SSENSE0,SSENSM0,USENSEO: value

Explanation: This message lists the sense fields from aSNALINK RPL.




Procedure Name: prtsense

SNALINK Messages


SNALINK Messages


Chapter 18. SNMP Messages

This chapter contains SNMPD, SNMPLIB, and SQESERV messages.

SNMPD MessagesThis section contains SNMPD messages.

bad privilege mask: mask

Severity: Warning.

Explanation: SNMP encountered an invalid privilegemask in a password file entry. The mask is ignored.

System Action: The data in the privilege mask field


System Programmer Response: The privilege maskfield (fourth field) in the community names file recordis currently reserved for future use. Remove the data inthis field from the record. is ignored and processingcontinues.

Source File: snmp_aut c

Procedure Name: read_pw_file

can’t create SNMP port

Severity: Fatal.

Explanation: SNMPD encountered an error creating itsTCP/IP port to accept SNMP requests.

System Action: SNMPD terminates.


System Programmer Response: This message ispreceded by error messages indicating that the socketor bind request failed. Correct the errors indicated bythose messages.

Source File: mib_t c


can’t open config file: file

Severity: Warning.

Explanation: The SNMPD trap destination file filecould not be opened.

System Action: SNMPD remains active, but no trapsare sent.


System Programmer Response: Check the trapsdestination file file to ensure that it exists and that it isaccessible to SNMPD. This file must be namedSNMPTRAP DEST and must be on a minidisk accessedby the SNMPD virtual machine.

Source File: snmp_io c

Procedure Name: read_destinations

create_DPI_port::bind tcperror

Severity: Warning.

Explanation: SNMPD encountered an error bindingthe DPI socket.



System Programmer Response: For tcperror codes, seethe TCP/IP Programmer’s Reference, and moreinformation about correcting socket problems, seeChapter 12, “Remote Procedure Call Messages” onpage 181.

Source File: snmp_dpi c

Procedure Name: create_DPI_port

create_DPI_port::socket tcperror

Severity: Warning.

Explanation: SNMP encountered an error creating theDPI socket.







create_DPI_port:getsockname tcperror

Severity: Warning.

Explanation: SNMPD encountered an error attemptingto obtain the name for the DPI socket.

System Action: Processing continues





create_SNMP_port::bind tcperror

Severity: Fatal.

Explanation: SNMP encountered an error binding asocket.





Procedure Name: create_SNMP_port

create_SNMP_port::socket tcperror

Severity: Fatal.

Explanation: SNMP encountered an error opening asocket.






decode: rc = ReturnCode

Severity: Warning.

Explanation: An error occurred decoding an SNMPrequest; the request is ignored.

System Action: SNMP ignores the request.


System Programmer Response: Either SNMPD wasnot able to allocate the storage necessary to decode therequest, or the request contained invalid data. Forstorage problems, increase the virtual storage availableto SNMPD. For invalid requests, check the clientissuing the request for errors. Processing continues withthe next request.

Source File: snmp_par c

Procedure Name: parse_snmp

DPI tcperror

Severity: Warning.

Explanation: An error occurred establishing the SNMPDPI connection with TCP/IP.

System Action: SNMPD processing continues, but theDPI connection to TCP/IP is not available.Management Information Base (MIB) variablesmaintained by the TCP/IP subagent of SNMPD are notavailable.




Procedure Name: handle_errors

Error get_snmp_socket: bind

Severity: Fatal.

Explanation: SNMPD encountered an error binding tothe MIB/TCP_routed socket.



System Programmer Response: For information abouthow to correct bind problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.


Procedure Name: get_snmp_socket

SNMPD Messages


Error get_snmp_socket: socket

Severity: Fatal.

Explanation: SNMPD could not open theMIB/RCP_routed socket.



System Programmer Response: For information abouthow to correct socket problems, see Chapter 12,“Remote Procedure Call Messages” on page 181.


Procedure Name: get_snmp_socket

make_TCP_sock::connect tcperror destination address

Severity: Warning.

Explanation: SNMP encountered an error connectingto TCP to send traps by means of TCP.

System Action: No trap is sent by means of TCP.


System Programmer Response: For tcperror codes, seethe TCP/IP Programmer’s Reference, and moreinformation about correcting socket problems, seeChapter 12, “Remote Procedure Call Messages” onpage 181. The associated socket is closed. SNMPDprocessing continues with the next request.


Procedure Name: make_TCP_sock

make_TCP_sock::socket tcperror

Severity: Warning.

Explanation: SNMP encountered an error creating asocket to send traps by means of TCP.

System Action: No trap is sent.


System Programmer Response: For tcperror codes, seethe TCP/IP Programmer’s Reference, and moreinformation about correcting socket problems, seeChapter 12, “Remote Procedure Call Messages” onpage 181. SNMPD processing continues with the nextrequest.


Procedure Name: make_TCP_sock

{ps_alloc}

Severity: Warning.

Explanation: SNMP could not allocate the memory toparse an SNMP request. SNMP ignores the currentrequest.

System Action: The current SNMP request is ignored.

User or Operator Response: If the error persists, tellthe system programmer about the problem.

System Programmer Response: Define a larger virtualstorage size for the SNMPD virtual machine. Processingcontinues with the next request.



{ps2pe failed: ps_error}

Severity: Warning.

Explanation: An error occurred allocating storage toconvert the presentation stream to a presentationelement.



System Programmer Response: Define a larger virtualstorage size for the SNMPD virtual machine. Processingcontinues with the next request.



read_pw_file: can’t open file

Severity: Warning.

Explanation: SNMP could not open the communitynames file file.

System Action: Processing continues; however,SNMPD does not accept any SNMP requests becausethere are no authorized community names.


System Programmer Response: Check the communitynames file file to ensure it exists and is accessible toSNMPD. This file must be named PW SRC and mustbe on a minidisk accessed by the SNMPD virtualmachine.



SNMPD Messages

Chapter 18. SNMP Messages 267

read_pw_file: out of memory

Severity: Warning.

Explanation: SNMPD could not allocate memory tostore an authorization record. Reading of thecommunity names file terminates.

System Action: Reading of the community names fileis terminated. SNMP agent processing continues;however, some community names are not authorized.


System Programmer Response: Define a larger virtualstorage size for the SNMPD virtual machine.



select tcperror

Severity: Fatal.

Explanation: SNMP encountered an error from aselect() call, waiting for incoming packets.





Procedure Name: handle_requests

send_SNMP_response tcperror

Severity: Warning.

Explanation: SNMP encountered an error sending aresponse to a request.

System Action: No response is sent to the currentSNMP request. SNMPD processing continues with thenext request.




Procedure Name: send_SNMP_response

send_UDP tcperror

Severity: Warning.

Explanation: SNMP encountered an error sending atrap to a client by means of UDP.

System Action: No trap is sent. SNMDP processingcontinues with the next request.




Procedure Name: send_UDP_trap

snmp_init failed

Severity: Fatal.

Explanation: SNMPD initialization failed.



System Programmer Response: This message ispreceded by an error message indicating that a socketcall or a bind failed for the SNMDP socket. Correct theerrors indicated by the preceding error message.



{str_setup: foo} {ps2pe failed: ps_error}

Severity: Warning.

Explanation: The first message indicates that the setupof the presentation stream from the packet failed. Thelast message indicates an error converting the stream toa presentation element.



System Programmer Response: Contact the IBMSupport Center. Processing continues with the nextrequest.



SNMPD Messages


unknown SNMP request type

Severity: Warning.

Explanation: SNMP received a request PDU that wasnot an SNMP Get request, an SNMP GETNext request,or an SNMP Set request.

System Action: The request is ignored. SNMPDprocessing continues with the next request.


System Programmer Response: Check the client thatsent the request for errors.



unknown socket type

Severity: Fatal.

Explanation: SNMP received a packet on an unknowntype socket.



System Programmer Response: For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.


Procedure Name: handle_requests

usage: snmpd <gated port number>

Severity: Fatal.

Explanation: SNMPD was invoked with too manyparameters; the correct command syntax is displayed.

Note: The angle brackets (< >) are literal in thismessage.


User or Operator Response: Restart SNMPD with thecorrect parameters. If SNMPD is started from aprocedure or PROFILE EXEC, ask the systemprogrammer to make the necessary corrections.

System Programmer Response: Correct the SNMPDstart parameters.



SNMPLIB MessagesThis section contains the SNMPLIB messages.

SNM010E command Invalid netmask or desirednetwork specified

Explanation: SNMP encountered an error convertingan IP address specified in a command. This messageindicates that the netmask or network specified is notvalid.

System Action: The command is ignored.

User or Operator Response: If the command wasissued at the NetView® command line, reenter thecommand with the correct network and netmaskspecified. If the command was issued from a NetViewClist, ask the system programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct network and netmask.

Source File: snmpsnmp assemble

Procedure Name: snmp

SNM011E command Invalid function: function

Explanation: An SNMP command specified an invalidfunction.


User or Operator Response: If the command was

issued at the NetView command line, reenter thecommand with the correct function. If the commandwas issued from a NetView Clist, ask the systemprogrammer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct function.



SNM012E command Function function needs at leastcount parameter(s)

Explanation: An SNMP command omitted requiredfunction parameters.

System Action: The command is aborted.

User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct parameters. If the commandwas issued from a NetView Clist, ask the systemprogrammer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct parameters.


SNMPD Messages



SNM013E command Missing function

Explanation: An SNMP command omitted therequired function specification.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct function specified. If thecommand was issued from a NetView Clist, ask thesystem programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct function.



SNM014E command Missing variable name

Explanation: An SNMP command omitted a variablename.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct variable name specified. Ifthe command was issued from a NetView Clist, ask thesystem programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct variable name.



SNM015E command Missing set value for variable

Explanation: SNMP encountered a SET function withno value specified.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct value for the set variable. Ifthe command was issued from a NetView Clist, ask thesystem programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct value for the set variable.



SNM016E command Missing or invalid destinationhost identification

Explanation: An SNMP command omitted a requiredhost ID specification.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct host ID specified. If thecommand was issued from a NetView Clist, ask thesystem programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct host ID.



SNM017E command Missing community name

Explanation: An SNMP command omitted a requiredcommunity name specification.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct community name specified.If the command was issued from a NetView Clist, askthe system programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct community name.



SNM018E command Request rejected, task task notactive

Explanation: An SNMP request was rejected becausethe referenced SNMP IUCV task was not active.

System Action: SNMP requests are rejected until theSNMPIUCV task is activated.

User or Operator Response: Start the SNMPIUCVtask first, wait for the connection with the SNMPQuery Engine, and reissue the SNMP request.




SNM019E command Request rejected, task task not(yet) connected

Explanation: An SNMP request was rejected becausethe task task had not yet established an IUCVConnection with the SNMP Query Engine.

SNMPLIB Messages


System Action: The connection is still pending. Thesystem continues operation.

User or Operator Response: Wait for the connectionto complete and reissue the SNMP request.




SNM020E command Error error on DSIGET

Explanation: SNMP encountered an error allocatingmemory for a packet.

System Action: The command aborts. The system triesto continue operation.

User or Operator Response: Retry the command. Ifthe error persists, contact the system programmer.

System Programmer Response: Use error value todetermine the reason for the error. The cause of thiserror is probably not enough storage. See NetViewCustomization: Using Assembler for DSIGET error codes.



SNM021E command Error error on DSIMQS

Explanation: SNMP encountered an error queuing apacket to the SNMP IUCV task.

System Action: The command is aborted. The systemtries to continue operation.

User or Operator Response: Retry the command. Ifthe error persists, contact the system programmer.

System Programmer Response: Use the error value todetermine the reason for the error. See NetViewCustomization: Using Assembler for DSIMQS error codes.



SNM022E command Missing or invalid trap filter id

Explanation: An SNMP command failed to specify orspecified an invalid trap filter ID.


User or Operator Response: If the command wasissued at the NetView command line, reenter thecommand with the correct trap filter ID specified. If thecommand was issued from a NetView Clist, ask thesystem programmer to correct the CLIST.

System Programmer Response: If the command wasissued from a NetView Clist, correct the NetView Clistto specify the correct trap filter ID.



SNM051E SNMP Request request from origindiscarded, MsgCompleteIPAUDIT=Xvalue

Explanation: SNMP received an IUCV MessageComplete notification, indicating the message wasdiscarded rather than received. Execution continues.The operator who issued the request is identified byorigin, and req identifies the request that this operatorissued.

System Action: The system tries to continueoperation, but discards the request that failed.

User or Operator Response: Verify that the SNMPQuery Engine is operating correctly, and reissue yourSNMP request. If the error persists, tell the systemprogrammer about the problem.

System Programmer Response: Determine why theIUCV Message was not received by the Query Engine.The IPAUDIT code can be used to determine the cause.For more information about the IPAUDIT value, see thez/VM: CP Programming Services. Correct the situation,and reissue the SNMP request.

Source File: snmptask assemble

Procedure Name: snmpiucv

SNM052E SNMP Request request from originatordiscarded, IUCV SEND error (R15)=error

Explanation: SNMP encountered the indicated error,err, while attempting an IUCV SEND. Consequently,the indicated request, req, from the indicated user,originator, could not be processed and was discarded.

System Action: The system continues to operate.

User or Operator Response: Ensure that the SNMPQuery Engine is operating correctly. Ensure that theSNMPIUCV task is connected to the SNMP QueryEngine. Reissue your SNMP request. If the errorpersists, tell the system programmer about the problem.

System Programmer Response: Determine the causeof the error by analyzing the error code. For moreinformation about the IUCV SEND, see the z/VM: CPProgramming Services. Correct the situation and reissuethe SNMP request.



SNM053E SNMP Request request from originatordiscarded, IUCV Connection Severed

Explanation: The indicated SNMP request, req, fromoperator, originator, was discarded because the SNMPIUCV connection was severed.

System Action: Because the connection was severed,

SNMPLIB Messages


no new SNMP requests are accepted until theconnection with the SNMP Query Engine isreestablished.

User or Operator Response: Reestablish the IUCVconnection with the SNMP Query Engine and reissueyour SNMP request.




SNM101W SNMP task task found Query Enginename not ready

Explanation: SNMP attempted to connect to theQuery Engine, but found the Query Engine was notready. The name identifies the user ID of the QueryEngine.

System Action: Depending on the reason that theengine is not ready, SNMP can abort this attempt tocontact the engine or continue execution. The SNMPtask task retries the connection to the Query Engine

User or Operator Response: Start the SNMP queryengine. If the Query Engine cannot be started, or if theproblem persists, tell the system programmer about theproblem.

System Programmer Response: Check the SNMPQuery Engine log for error messages. Ensure that thename corresponds to the SNMPQE parameter in theSNMPARMS parameter list. name based on the retryvalue specified in the SNMP initialization parameters.



SNM103E SNMP task task got error error onfunction sub-func

Explanation: SNMP encountered the indicated errorfrom the indicated IUCV function.

System Action: The request is aborted. If possible, thesystem continues operation.


System Programmer Response: Use the err code andfunction and sub_func values to determine the cause ofthe error. For more information about the error code onthe IUCV SEND, see the z/VM: CP ProgrammingServices. Correct the situation and retry the command.



SNM104E SNMP task task has count IUCVinterrupts pending, path severed

Explanation: SNMP received more IUCV interruptsthan it can handle with its current preallocated queue.The indicated number of IUCV interrupts are pending.The IUCV path has been severed.

System Action: The system tries to reestablish theconnection with the SNMP Query Engine and restart.

User or Operator Response: Tell the systemprogrammer about the problem. You can reissue yourSNMP requests after the connection with the SNMPQuery Engine has been reestablished.

System Programmer Response: Ensure that you donot have a CLIST that issues SNMP requests in aendless loop. If the error persists, contact the IBMSupport Center.



SNM105E SNMP task task ignored IUCV interrupt,unexpected IPTYPE type

Explanation: SNMP received an IUCV interrupt withan unexpected IPTYPE field.

System Action: The interrupt is ignored. The systemcontinues operation.


System Programmer Response: Ensure that theversion and level of SNMP Query Engine are in syncwith the version of the SNMPIUCV task.



SNM106E SNMP task task connection to QueryEngine ID now severed

Explanation: The IUCV connection between SNMPand the indicated query engine has been severed. Theconnection may be reopened.

System Action: If any requests are still outstanding,the system discards them. Execution continues.

User or Operator Response: Reestablish theconnection with the SNMP Query Engine, if SNMPrequests need to be issued.




SNMPLIB Messages


SNM107E SNMP task task received sever forpath=path

Explanation: SNMP received notification of a severedIUCV connection for the indicated path. SNMP did nothave this connection open before this notification.

System Action: The system continues operation.

User or Operator Response: If the error persists,contact the system programmer.




SNM108E SNMP task task cannot find IUCV PCnumbers in CVT.

System Action: Initialization is terminated. TheSNMPIUCV task cannot operate in this situation.

Explanation: SNMP could not locate the IUCVProgram Call numbers.


System Programmer Response: Ensure that TCP/IPhas been installed correctly on your z/VM system.



SNM120W SNMP task task got error error onDSIGET

Explanation: SNMPIUCV encountered an errorallocating memory with a DSIGET call.

System Action: During initialization, this error canprevent the startup of the SNMPIUCV task. Duringnormal operation, this error can cause one or moreSNMP requests to fail, or never receive a response.


System Programmer Response: Use the error value todetermine the reason for the error. The probable causeof the error is not enough storage. See NetViewCustomization: Using Assembler for DSIGET error codes.If the error indicates not enough storage, allocate morevirtual storage to the NetView virtual machine.



SNM121W SNMP task task incoming packet hasinvalid packet length length

Explanation: SNMP received a packet with an invalidlength.

System Action: Invalid packets are ignored.


System Programmer Response: Ensure that you havea correct level of the SNMP Query Engine that is insync with the SNMPIUCV task on NetView side.



SNM122W SNMP task task incoming packet hasinvalid character set value

Explanation: SNMP received a packet specifying aninvalid character set.

System Action: The packet is ignored. The systemcontinues operation.





SNM123W SNMP task task incoming packet hasinvalid packet type value

Explanation: SNMP received a packet with an invalidpacket type.

System Action: The packet is ignored. The systemcontinues operation.





SNM127W SNMP task task got error error onDSIDKS

Explanation: An error occurred while using DSIDKSto read the initialization parameters for SNMPIUCV.

System Action: The system continues and uses theinternal defaults as startup parameters.

User or Operator Response: Tell the system

SNMPLIB Messages


programmer about the problem.

System Programmer Response: Use the err value todetermine the reason for the error. See NetViewCustomization: Using Assembler for DSIDKS error codes.


Procedure Name: snmpicuv

SNM128W SNMP task task found missing value orinvalid value for parameter

Explanation: SNMP encountered an initializationparameter with a missing or invalid value.

System Action: The missing or invalid value isignored, and the default value is used. Initializationcontinues.


System Programmer Response: Correct the missing orinvalid value in SNMPARMS.



SNM129W SNMP task task found invalidinitialization parameter value

Explanation: SNMP encountered an invalidinitialization parameter.

System Action: The invalid initialization parameter isignored. Initialization continues and assumes thedefault value for the invalid parameter.


System Programmer Response: Correct the invalidinitialization parameter in SNMPARMS.



SQESERV MessagesThis section contains SQESERV messages

cannot open MIB description file: file

Severity: Warning.

Explanation: The SQE server could not open the MIBdescription file. The file is identified by file.

System Action: Processing continues; however, theMIB description file is not read. Descriptive variablenames (for example, sysDescr) are not accepted inSNMP commands and the SNMP SET command fails.

User or Operator Response: Ensure that the MIBdescription file is accessible to the SQESERVmodule.This file should be named MIB_DESC DATA,and should be located on a minidisk accessed by theSNMPQE ID.


Source File: snmpdesc c

Procedure Name: read_mib_desc_tbl

create_SNMP_port : : socket tcperror

Severity: Fatal.

Explanation: A socket() call failed attempting to createan SNMP port. The port could not be created.

System Action: The SQESERV module is terminated.


System Programmer Response: For tcperror codes, seethe TCP/IP Programmer’s Reference, and moreinformation about correcting socket problems, see

Chapter 12, “Remote Procedure Call Messages” onpage 181.

Source File: snmpsend c


create_SNMP_port: bind tcperror

Severity: Fatal.

Explanation: A bind() call failed attempting to createan SNMP port. The port could not be created.

System Action: The SQESERV module is terminated.



Source File: snmpsend c


make_SNMP_packet: cannot parse packet (pe2ps)

Severity: Warning.

Explanation: The SQE server could not parse anSNMP request because of an error converting apresentation element to a presentation stream.

System Action: The request is ignored. Processing

SNMPLIB Messages


continues with the next request.


System Programmer Response: Invalid data waspassed in the SNMP request. Check the applicationprogram that initiated the request. If you are using anIBM application program (for example, NetView),contact the IBM Support Center.

Source File: snmppars c

Procedure Name: make_SNMP_request

make_SNMP_packet: cannot parse packet (ps_alloc)

Severity: Warning.

Explanation: The SQE server could not allocatesufficient memory to parse a packet.

System Action: The request is ignored. Processingcontinues with the next request.


System Programmer Response: Increase the virtualstorage on the SNMPQE virtual machine.



make_SNMP_packet: cannot parse packet (str_setup)

Severity: Warning.

Explanation: The SQE server could not parse anSNMP request because sufficient memory could not beallocated.



System Programmer Response: Increase the virtualstorage on the SNMPQE virtual machine.



make_SNMP_packet: illegal SNMP request: request

Severity: Warning.

Explanation: The SQE server encountered an illegalSNMP request.






make_SNMP_packet: no MIB type defined: name

Severity: Error.

Explanation: An application has tried to issue anSNMP Set request for an object for which no MIBdescription data is known.



System Programmer Response: Add the relevant datato the MIB description file and restart SQESERV. This isthe MIB_DESC DATA file.



make_SNMP_request: illegal object identifier: id

Severity: Warning.

Explanation: The SQE server encountered an illegalobject identifier, which is ignored.



System Programmer Response: An application hasprovided an illegal object identifier. Identify theapplication and correct the error. If you are using anIBM application program (for example, NetView),contact the IBM Support Center.



out of memory in cache_object (new)

Severity: Warning.

Explanation: The SQE server could not allocatememory to add a new object to a list.

System Action: Processing continues. No caching isdone.


System Programmer Response: Increase the virtualstorage for the SNMPQE virtual machine.

Source File: sqecache c

SQESERV Messages


Procedure Name: cache_object

out of memory in cache_object name

Severity: Warning.

Explanation: The SQE server could not allocateenough memory to add an object to a list.

System Action: Processing continues. No caching isdone.



Source File: sqecache c

Procedure Name: cache_object

parse_SNMP_packet: cannot parse packet (decode)

Severity: Warning.

Explanation: The SQE server encountered an errordecoding an SNMP request.



System Programmer Response: Identify the agent thatsent the incorrect request and correct any problems atthat agent.


Procedure Name: parse_SNMP_packet

parse_SNMP_packet: cannot parse packet (ps_alloc)

Severity: Warning.







parse_SNMP_packet: cannot parse packet (ps2pe)

Severity: Warning.

Explanation: The SQE server could not parse anSNMP request because of an error converting apresentation stream to a presentation element.






parse_SNMP_packet: cannot parse packet (str_setup)

Severity: Warning.







parse_SNMP_packet: corrupted packet

Severity: Warning.

Explanation: The SNMP server encountered acorrupted packet. There is a problem with the agentthat sent the request.


User or Operator Response: Identify the SNMP agentthat sent the incorrect packet and correct any errors.




resolver not yet supported

Severity: Warning.

Explanation: The SQE server encountered aQ_RESOLVER_RESPONSE request, which is notcurrently supported.

SQESERV Messages





Source File: sqequeue c

Procedure Name: queue_entry

select failed in await_queries

Severity: Fatal.

Explanation: The SQE server encountered an errorissuing a select function call to determine if any querieswere outstanding.

System Action: The SQESERV module terminates withexit code 1.



Source File: sqeserv c

Procedure Name: await_queries

SQEE001 –– Can’t make UDP port

Severity: Fatal.

Explanation: The SQE server could not make theSNMP UDP port.



System Programmer Response: This error message ispreceded by a message indicating an error with eitherthe socket or bind request. For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.


Procedure Name: create_ports

SQEE002 –– Can’t make SNMP trap port

Severity: Fatal.

Explanation: The SQE server cannot make the SNMPtrap port because of a socket call failure or a bindfailure.


User or Operator Response: Ensure that anotherSQESERV program is not already running. Only one

SQESERV program can use the SNMP trap port. If thisis the only SQESERV program attempting to run,contact your system programmer.

System Programmer Response: Ensure the user isallowed to use the reserved port by making theappropriate PORT entries in TCPIP PROFILE. Forinformation about correcting socket problems, seeChapter 12, “Remote Procedure Call Messages” onpage 181.



SQEE003 –– Can’t do TCP listen

Severity: Fatal.

Explanation: The SQE server encountered an errorattempting a TCP listen.






SQEE004 –– Can’t do IUCV listen

Severity: Fatal.

Explanation: The SQE server encountered an errorattempting an IUCV listen.






SQEW001 –– Can’t make raw ICMP socket

Severity: Warning.

Explanation: The SQE server encountered an errormaking the PING port.

System Action: Processing continues without the rawsocket. SNMP Ping requests fail.

User or Operator Response: Ensure the user ispermitted to use RAW sockets.

SQESERV Messages


System Programmer Response: Add SNMPQE to theOBEY list of PROFILE TCPIP, if it is not already there.



store_SNMP_var: unknown MIB type: type

Severity: Warning.

Explanation: The SQE server received a responsecontaining an object with an unknown MIB type.

System Action: The request is ignored. The object isnot processed. Processing continues with the nextrequest.


System Programmer Response: Identify the agentsending the incorrect response and correct anyproblems with the agent.


Procedure Name: store_SNMP_var

unknown MIB type: type

Severity: Warning.

Explanation: The SQE server encountered anunknown type field in the MIB description file.



System Programmer Response: Correct the MIBdescription file, the MIB_DESC DATA file, and restartSQESERV.

Source File: snmpdesc c

Procedure Name: read_mib_desc_tbl

SQESERV Messages


Chapter 19. SSL Messages

This chapter contains the SSL processing messages. It also contains lists of the SSLserver return codes and reason codes.

DTCSSL001E All cipher suites have been excluded

Explanation: All of the SSL cipher suites have beenexempted (excluded from SSL processing) inDTCPARMS.

System Action: SSL processing is terminated.

System Programmer Response: Remove at least oneof the cipher suite exemptions from DTCPARMS.

DTCSSL003I SSLADMIN received: command

Explanation: The SSLADMIN command was receivedat the SSL server.

System Action: SSL processing continues.


DTCSSL004E No operands on SSLADMIN

Explanation: The SSLADMIN command was issuedwithout operands.

System Action: The SSLADMIN command isterminated.

System Programmer Response: Reissue the commandwith operands.

DTCSSL005E pthread_create() error for thread_ID

Explanation: A process thread could not be created.The message indicates whether the error was for themain SSL thread or a worker thread.

System Action: SSL processing is terminated.

System Programmer Response: Call IBM Service.

DTCSSL006E Activity received by select() was notfrom SSLADMIN

Explanation: The select() call in the SSL administrationthread was satisfied by something other than anadministration socket call.

System Action: None. The SSL server waits foranother response.

System Programmer Response: Turn trace flow on,reproduce the error, and call IBM Service.

DTCSSL008I Shutting down SSL server

Explanation: The SSL server is stopping.

System Action: The SSL server stops.


DTCSSL009E select() returned without a client orserver read

Explanation: The select() call in the SSL worker threadreturned with a response that was not from either theclient socket or the server socket.


System Programmer Response: Turn trace flow on,reproduce the problem, and call IBM Service.

DTCSSL010E Call to select() failed

Explanation: The select() call in the SSL worker threadreturned a negative return code.

System Action: This SSL client-server conversation isterminated.


DTCSSL011E No file descriptors are ready

Explanation: The select() call in the SSL worker threadreturned a zero return code.



DTCSSL014E Invalid argument: argument

Explanation: Either a DTCPARMS parameter or anSSLADMIN command operand was wrong.

System Action: If the DTCPARMS parameter waswrong, the default value was used. If the SSLADMINcommand operand was wrong, the command wasterminated.

System Programmer Response: If the DTCPARMSdefault value is not satisfactory, or if the error was on


an SSLADMIN command, correct the argument andretry.

DTCSSL015I SSL server has started

Explanation: The SSL server has started.

System Action: The SSL server starts.


DTCSSL016E Error sending data to the server[: errnoerrno]

Explanation: An error occurred in sending data fromthe client to the application server:

v If the error occurred when the SSL server receivedthe data from client, message DTCSSL202E is alsoissued.

v If the error occurred when the SSL server sent thedata to the application server, an SSL server reasoncode is displayed. For the meaning of errno values,see Table 3 on page 291.



DTCSSL017E Error sending data to the client[: errnoerrno]

Explanation: An error occurred in sending data fromthe application server to the client:

v If the error occurred when the SSL server receivedthe data from the application server, an SSL serverreason code is displayed. For the meaning of errnovalues, see Table 3 on page 291.

v If the error occurred when the SSL server sent thedata to the client, message DTCSSL202E is alsoissued.



DTCSSL022E Handshake failed rc rc

Explanation: The handshaking with a client failed. Foran explanation of the return code, see Table 2 onpage 291.


System Programmer Response: Determine the causeof the failure and retry.

DTCSSL036I Local connections will be protected bySSL

Explanation: A local connection destined for a secureport or user ID will be routed to the SSL Server.



DTCSSL037I Local connections will not be protectedby SSL

Explanation: A local connection destined for a secureport or user ID will not be routed to the SSL Server.



DTCSSL040I Trace has been turned off

Explanation: The SSLADMIN NOTRACE commandwas issued.

System Action: SSL tracing is turned off.


DTCSSL041E Out of memory at location

Explanation: A request for memory was denied.

System Action: The SSL server is shut down.

System Programmer Response: Increase the size ofthe SSL server virtual machine or reduce the maximumnumber of concurrent secure sessions it supports(MAXUSERS setting). Then restart the server.

DTCSSL042E Error errno when locking mutexmutex_name

Explanation: An error was returned when a mutexlock was requested. For the meaning of errno values,see Table 3 on page 291.



DTCSSL043E Error errno when unlocking mutexmutex_name

Explanation: An error was returned when unlocking amutex. For the meaning of errno values, see Table 3 onpage 291.



SSL Messages


DTCSSL047I Trace established

Explanation: The SSLADMIN TRACE command wassuccessful.

System Action: SSL tracing is turned on.


DTCSSL048I Trace not changed

Explanation: The SSLADMIN TRACE command wasnot successful. The existing trace setting has not beenchanged.



DTCSSL049E Invalid IP address ipaddr

Explanation: The IP address used in the SSLADMINTRACE command was in the wrong format.


System Programmer Response: Reissue the command,entering the IP address in dotted format (n.n.n.n).

DTCSSL050E connection failed with rc rc errno errno

Explanation: A socket call failed with a negativereturn code. For the meaning of errno values, seeTable 3 on page 291.

System Action: If the call was from the administrationthread or the main SSL thread, the SSL server is shutdown. If the call was from a worker thread, that SSLclient-server conversation is terminated.


DTCSSL051E Invalid connection number: number

Explanation: The connection number specified on anSSLADMIN TRACE command was not an integer. Onlyintegers are accepted for connection numbers.


System Programmer Response: Reissue the commandwith a valid connection number.

DTCSSL052E Out of memory at location: errno errno

Explanation: A memory request for a Todo blockreturned a negative return code. For the meaning oferrno values, see Table 3 on page 291.


System Programmer Response: Increase the memoryfor the SSL server virtual machine or reduce themaximum number of concurrent secure sessions itsupports (MAXUSERS setting). Then restart the server.

DTCSSL053E setsockopt() failed with rc rc errnoerrno

Explanation: A setsockopt() socket call failed. For themeaning of errno values, see Table 3 on page 291.

System Action: The SSL server is shut down, unlessthe failure occurred in a worker thread. In that case,only that SSL client-server conversation is ended.


DTCSSL055E Connection to real server failed

Explanation: The connection from the SSL server tothe application server could not be made.

System Action: That SSL client-server conversation isterminated.

System Programmer Response: Make sure theapplication server is running.

DTCSSL056I No sessions are active

Explanation: An SSLADMIN QUERY SESSIONScommand was issued, and there were no activesessions.



DTCSSL057I Input is at least input_length bytes longbut only buffer_length bytes are allowed.

Explanation: More information is being sent to theSSL server on the SSLADMIN command than thebuffer can handle.

System Action: The input length is limited to thebuffer length; SSL processing continues.

System Programmer Response: If the problempersists, call IBM Service to adjust the buffer size.

DTCSSL058E DTCPARMS are too long

Explanation: The SSL information provided inDTCPARMS is too large for the buffer.

System Action: The input length is limited to thebuffer length; SSL processing continues.

System Programmer Response: Reduce the size of theDTCPARMS information, or call IBM Service to adjustthe buffer size.

DTCSSL059E Open error on file: pathname

Explanation: The DTCPARMS file could not be read.

System Action: Default values are used; SSLprocessing continues.


SSL Messages

Chapter 19. SSL Messages 281

DTCSSL060E Mutex instruction failed

Explanation: The pthread_condition_signal() callfailed.



DTCSSL061E Cache size of requested_size is not valid;cache size is set to set_size

Explanation: The SSL cache size specified inDTCPARMS was either too low or too high.

System Action: The closest limit is used; SSLprocessing continues.

System Programmer Response: If the cache size set bySSL processing is not satisfactory, stop the SSL serverand modify the DTCPARMS file to specify a cache sizethat is within the limits. Then restart the server.

DTCSSL062E Cache life of requested_life is not valid;cache life is set to set_life

Explanation: The SSL cache life specified inDTCPARMS was either too low or too high.

System Action: The closest limit is used; SSLprocessing continues.

System Programmer Response: If the cache life set bySSL processing is not satisfactory, stop the SSL serverand modify the DTCPARMS file to specify a cache lifethat is within the limits. Then restart the server.

DTCSSL063E Port number not valid

Explanation: The port number specified on theSSLADMIN TRACE command was not an integer. Onlyintegers are accepted for port numbers.


System Programmer Response: Reissue the commandwith a valid port number.

DTCSSL072E Monitor updates failed

Explanation: The monitor records were not updated.

System Action: The SSL server keeps running, but themonitor data is unreliable.


DTCSSL073E Broken pipe

Explanation: The connection to the TCPIP stack isgone.


System Programmer Response: Check to see if theTCPIP stack is started; if not, restart it. If the SSL server

is in the AUTOLOG list, it will be restarted; if not,restart the SSL server after TCPIP comes up.

DTCSSL074E NETIUCV error

Explanation: The connection to the TCPIP stack couldnot be established.


System Programmer Response: Check that the correctTCPIP stack is being used for the connection. It isretrieved from the tcpipuserid field in the TCPIP DATAfile. If the user ID is correct, check that the stack is upand running. Then restart the SSL server.

DTCSSL080I DTCPARMS arguments:{[VMSSL_operands] [ADMINPORT port][TCPIPUSERID userid] | NONE}

Explanation: This message lists any non-defaultarguments being used to start SSL processing:

VMSSL_operandslists the non-default VMSSL operands beingused (specified in the DTCPARMS file or onthe VMSSL command). If only defaults arebeing used, this field is not displayed.

ADMINPORT portidentifies the non-default SSL administrationport being used (defined in the ETC SERVICESfile). If the default port (9999) is being used,this field is not displayed.

TCPIPUSERID userididentifies the non-default TCP/IP (stack)server being used (defined in the TCPIP DATAfile). If the default server (TCPIP) is beingused, this field is not displayed.

NONE indicates that only the default VMSSLoperands, SSL administration port, andTCP/IP (stack) server are being used.



DTCSSL092E Log file flush failed

Explanation: During the processing of the SSLADMINLOG command, the buffer could not be written to thefile on the SSL server machine.

System Action: The SSLADMIN LOG command fails.

System Programmer Response: Contact the IBMsoftware Support Center.

SSL Messages


DTCSSL093E Log file copy (cp) failed rc: rc

Explanation: During the processing of the SSLADMINLOG command, the copy function of the message logfailed. For the meaning of rc values see Table 2 onpage 291



DTCSSL094E Log file read failed rc: rc errno: errno

Explanation: During the processing of the SSLADMINLOG command, the read function of the message logfailed. For the meaning of errno values see Table 3 onpage 291. For the meaning of rc values see Table 2 onpage 291.



DTCSSL201E Internal error--GSKKM error code.

Explanation: An unexpected error occurred whileusing functions to manage certificates.


System Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.

DTCSSL202E Internal error--GSKSSL error code.

Explanation: An unexpected error occurred whileusing functions to handle the SSL protocol. For themeaning of the error code, see Table 2 on page 291.

System Action: The SSL client-server conversation isterminated.


DTCSSL203E Database setup failed.

Explanation: The SSL certificate database could not beset up. Other messages may provide more specificinformation about the cause.

System Action: The SSL server is not started.

System Programmer Response: Contact IBM Service,providing the messages that were displayed.

DTCSSL204E A memory allocation error occurred.

Explanation: The storage needed for the SSL servercould not be obtained.

System Action: The SSL server is not started; ifalready started, the server is shut down.

System Programmer Response: Increase the size ofthe SSL server virtual machine or reduce the maximumnumber of concurrent secure sessions it supports(MAXUSERS setting). Then restart the server.

DTCSSL205E An I/O error occurred.

Explanation: There was an error on a read or sendsocket call while processing an SSLADMIN command.


System Programmer Response: Retry. If the errorpersists, contact IBM Service.

DTCSSL206E Peer closed connection.

Explanation: During SSLADMIN processing, theconnection was closed by the client before thecommand completed.


System Programmer Response: Reissue theSSLADMIN command. If the condition persists, callIBM Service.

DTCSSL207E An error occurred while opening a file.

Explanation: The SSL certificate database passwordfile could not be opened.

System Action: The other message(s) provide detailsabout the system action.


DTCSSL208E An error occurred while writing datato a file.

Explanation: There was an error while writing to theSSL certificate database password file.



SSL Messages


DTCSSL209E Failed to initialize SSL server.

Explanation: An error occurred that prevented the SSLserver from starting.

System Action: The SSL server is not started.

System Programmer Response: Consult the successivemessages on the console that refer to this error. Ifneeded, contact IBM Service.

DTCSSL210E SSL server is shutting down.

Explanation: A severe error occurred and the SSLserver cannot continue.


System Programmer Response: Consult the othermessages that were displayed to understand why theserver could not be brought up. If needed, contact IBMService.

DTCSSL211E Failed to update resume or new countin monitor data for this connection:

Explanation: The resume count or new count in theSSL monitor data could not be updated.


System Programmer Response: See the messages thatfollow this message for more detail.

DTCSSL212E Failed to update cipher count inmonitor data for this connection:

Explanation: The cipher count in the SSL monitor datacould not be updated.


System Programmer Response: See the messages thatfollow this message for more detail.

DTCSSL313I CA certificate in certificate chain alreadyexists in database.

Explanation: An SSLADMIN STORE command wasissued for a certificate chain. One of the CA certificatesin the chain is already in the database. The certificate inthe chain was not stored, and the copy already in thecertificate database will be used.



DTCSSL314I CA certificate in certificate chain storedin the database. Label is: label

Explanation: An SSLADMIN STORE command wasissued for a certificate chain. A CA certificate from thechain was stored in the certificate database with theindicated label.



DTCSSL315I Server certificate in certificate chainstored in the database.

Explanation: An SSLADMIN STORE command wasissued for a certificate chain. The server certificate fromthe chain was stored in the certificate database.



DTCSSL316I New database created.

Explanation: An SSL certificate database has beencreated. This occurs the very first time the SSL server isbrought up and when an SSLADMIN REMOVEcommand is issued.



DTCSSL318I Database deleted. New database created.

Explanation: The SSL certificate database was deletedas the result of an SSLADMIN REMOVE command.

System Action: A new certificate database isimmediately created, preloaded with some Well KnownCA certificates.


DTCSSL319I Database regenerated.

Explanation: The SSL certificate database wasregenerated as a result of an SSLADMINREGENERATE command.



DTCSSL401E The label already exists in thedatabase.

Explanation: The label specified on the SSLADMINcommand is already being used.


System Programmer Response: Reissue the commandusing a unique label. To determine what labels exist inthe certificate database, issue ssladmin query cert * orssladmin query req *.

SSL Messages


DTCSSL402E No entry is found with this label.

Explanation: The label specified on the SSLADMINcommand does not exist in the certificate database.


System Programmer Response: Reissue the commandusing the correct label. To determine what labels existin the certificate database, issue ssladmin query cert *or ssladmin query req *.

DTCSSL403E No certificate request is found for thecertificate.

Explanation: An SSLADMIN STORE command wasissued for a server certificate, but there is nocorresponding certificate request with that label in thecertificate database.

System Action: The SSLADMIN command isterminated; the certificate is not stored.

System Programmer Response: Create a newcertificate request and use it to obtain anothercertificate.

DTCSSL404E A duplicate certificate exists in thedatabase.

Explanation: A certificate matching the label specifiedon the SSLADMIN STORE command already exists inthe certificate database.



DTCSSL405E There is no certificate request with thislabel.

Explanation: A certificate request matching the labelspecified on the SSLADMIN command does not exist inthe certificate database.


System Programmer Response: Make sure that thecertificate associated with this label is a SERVERcertificate (as opposed to a CA certificate).

DTCSSL406E An encoding or decoding erroroccurred. The certificate may becorrupted.

Explanation: During the processing of the SSLADMINSTORE command, an encoding or decoding erroroccurred.


System Programmer Response: Make sure that thecertificate in the CMS file is identical to the one thatwas sent to you by the CA. If the error still occurs,contact the CA that provided the certificate.

DTCSSL407E A database validation error occurred.The certifying CA may not be in thedatabase.

Explanation: The certificate being stored in the SSLcertificate database could not be validated.


System Programmer Response: If you were sentmultiple files from the CA, be sure to store the CAcertificate first before storing the SERVER certificate. Ifyou did this or did not receive any additionalcertificates from the CA, contact the CA about theproblem.

DTCSSL408E The certificate was not stored becauseit expired.

Explanation: You cannot store a certificate in thedatabase after its valid end date and time.


System Programmer Response: Check the valid enddate and time of the certificate. If the certificate is stillvalid, verify the system time. Otherwise request a newor renewed certificate from the CA.

DTCSSL409E The certificate was not stored becauseit is not valid yet.

Explanation: You cannot store a certificate in thedatabase before its valid start date and time.


System Programmer Response: Verify that the systemtime is correct. Also, the CA may have sent a certificatewith the valid start date and time set slightly ahead.Wait a few moments and reissue the command.

DTCSSL410E CA certificate in certificate chain notstored:

Explanation: The CA certificate in a certificate chainwas not stored. The reason is given in the subsequentmessage.

System Action: The SSLADMIN command isterminated. The remaining CA certificates and theserver certificate are not stored.

System Programmer Response: Check the messagethat follows this one for more information. Thecertificate chain may be corrupted. Contact the CA that

SSL Messages


sent you the certificate chain.

DTCSSL411E Server certificate in certificate chainnot stored:

Explanation: The server certificate in a certificatechain was not stored. The reason is given in thesubsequent message.


System Programmer Response: Check the messagethat follows this one for more information.

DTCSSL414E An error occurred while deleting thedatabase.

Explanation: An error occurred while using theSSLADMIN REMOVE command to delete the SSLcertificate database.

System Action: The SSLADMIN command isterminated; the database is not deleted.


DTCSSL415E Failed to regenerate database.Password not changed.

Explanation: The SSLADMIN REGENERATEcommand was issued to regenerate the SSL certificatedatabase, but the database was not regenerated. Thedatabase is usable because the internal password wasnot changed.



DTCSSL416E Failed to regenerate database. Databasemay not be usable.

Explanation: The SSLADMIN REGENERATEcommand was issued to regenerate the SSL certificatedatabase, but the database was not regenerated. Thedatabase may not be usable because the error involvedthe internal password.



DTCSSL417E An invalid password was encounteredor the database has been corrupted.

Explanation: The SSL certificate database or itsinternal password is corrupted.


System Programmer Response: Consult the previousmessages on the console that refer to this error. If thismessage appears when the SSL server is started, contactIBM Service for possible recovery of the database.

DTCSSL418E Bad password file.

Explanation: The SSL certificate database internalpassword file is corrupted. The certificates in thedatabase are not usable.


System Programmer Response: Consult the previousmessages on the console that refer to this error. Use theSSLADMIN REMOVE command to delete the database.If needed, contact IBM Service.

DTCSSL419E The password file does not exist.

Explanation: The SSL certificate database internalpassword file does not exist. The certificates in thedatabase are not usable.


System Programmer Response: Consult the previousmessages on the console that refer to this error. Use theSSLADMIN REMOVE command to delete the database.If needed, contact IBM Service.

DTCSSL420E The certificate database does not exist.

Explanation: The SSL certificate database does notexist.


System Programmer Response: Contact IBM Service.

DTCSSL421E Self-signed certificate generated but itcould not be retrieved:

Explanation: The self-signed certificate was createdand stored in the certificate database. However, thecertificate could not be stored in a CMS file becausethere was an error retrieving the certificate from thedatabase.


System Programmer Response: Consult the successivemessages on the console that refer to this error. Try

SSL Messages


using the SSLADMIN EXPORT command to retrievethe certificate. If needed, contact IBM Service.

DTCSSL501E No SERVER certificate was found withthis label.

Explanation: There is no SERVER certificate in thecertificate database with a label matching the onespecified on the PORT statement in the TCPIP profile.

System Action: The secure connection is terminated.

System Programmer Response: Correct the label onthe PORT statement in the TCPIP profile. To determinewhat certificate labels exist in the certificate database,issue ssladmin query cert *.

DTCSSL502E Certificate expired.

Explanation: The certificate could not be used for SSLauthentication because it is no longer valid. The validend date and time have passed.

System Action: The secure connection is terminated.

System Programmer Response: Check with your CAto find out how to obtain a new or renewed certificate.

DTCSSL503E No common cipher suites.

Explanation: There is no cipher suite match betweenthe client and the SSL server.


System Programmer Response: You may have toomany cipher suites exempted (excluded from SSLprocessing). Remove the cipher suite exemptions fromDTCPARMS.

DTCSSL504I Partner already closed.

Explanation: When the SSL server contacted the client,the client was already closed.



DTCSSL2400E File fn ft exists.

Explanation: The indicated CMS file cannot alreadyexist when you issue the SSLADMIN command.


System Programmer Response: Select a unique labelto be used for SSLADMIN processing.

DTCSSL2401E File fn ft does not exist.

Explanation: The specified CMS file must alreadyexist before you issue the SSLADMIN command.


System Programmer Response: Create the requiredfile and reissue the command.

DTCSSL2402E keyword keyword and value aremissing from X509INFO file.

Explanation: A required keyword and value aremissing from the X509INFO file.


System Programmer Response: Add the requiredinformation to the X509INFO file and reissue theSSLADMIN command.

DTCSSL2403I Request stored in certificate databasewith label label.

Explanation: The SSLADMIN REQUEST commandsuccessfully stored the certificate request in thecertificate database with the indicated label.



DTCSSL2404I Request saved in file fn ft fm.

Explanation: The SSLADMIN REQUEST commandsuccessfully stored the certificate request in theindicated CMS file.

System Action: The SSLADMIN command completes.


DTCSSL2405I Certificate stored in certificatedatabase.

Explanation: The SSLADMIN STORE commandsuccessfully stored the certificate in the certificatedatabase.



DTCSSL2406I {CERTIFICATE|REQUEST} deletedfrom database.

Explanation: The SSLADMIN DELETE commandsuccessfully deleted the certificate or certificate requestfrom the certificiate database.



SSL Messages


DTCSSL2407I Unknown command.

Explanation: An unsupported operand was specifiedon the SSLADMIN command.


System Programmer Response: Reissue the commandwith the correct operands.

DTCSSL2408I You have requested the deletion of thecertificate database and all its contents.Type ’YES’ to proceed.

Explanation: Using the SSLADMIN REMOVEcommand is a destructive action. Confirmation isrequired before processing can continue.

System Action: The system waits for your response.

System Programmer Response: Type ’YES’ to proceed;type anything else to stop the command.

DTCSSL2409I Command canceled.

Explanation: The SSLADMIN REMOVE commandwas canceled because you did not respond ’YES’ tomessage DTCSSL2408I.



DTCSSL2410E Error reading file fn ft fm.

Explanation: An error was encountered while tryingto read the file.



DTCSSL2412E {DATA|NODATA} is valid only forTRACE CONNections.

Explanation: This operand can be used only on theSSLADMIN TRACE CONNECTIONS command.


System Programmer Response: Reissue the commandwith the correct syntax.

DTCSSL2413E Error writing file fn ft fm.

Explanation: An error occurred while writing to aCMS file after successful completion of an SSLADMINcommand. For example, a write error may haveoccurred while trying to write a certificate to a file.

System Action: The SSLADMIN command completedsuccessfully, but the certificate or certificate request was

not written to a CMS file. However, the certificate orcertificate request does exist in the certificate database.

System Programmer Response: Determine the causeof the write error.

DTCSSL2414E No R/W disks available.

Explanation: There are no R/W disks available towhich the certificate or certificate request can bewritten.


System Programmer Response: Provide a R/W diskand reissue the command.

DTCSSL2415E Disk fm is not linked R/W.

Explanation: The file mode specified on theSSLADMIN command, to indicate the disk where acertificate or certificate request should be written, doesnot represent a R/W disk.


System Programmer Response: Reissue the command,specifying a file mode that represents a R/W disk.

DTCSSL2416I Trace started.

Explanation: The selected trace of the SSL servervirtual machine has been started.



DTCSSL2417I No sessions are active.

Explanation: At the time the SSLADMIN QUERYSESSIONS command was issued, there were no activesessions.



DTCSSL2418E Too many operands on theSSLADMIN TRACE command.

Explanation: You have provided too many operandson the SSLADMIN TRACE command.


System Programmer Response: Reissue the commandwith the correct operands.

SSL Messages


DTCSSL2419E You are not allowed to access the SSLserver.

Explanation: SSLADMIN commands can be issuedonly by privileged TCP/IP users, as identified by theTCP/IP server’s OBEY statement.


System Programmer Response: Issue the commandfrom an authorized user ID.

DTCSSL2420E The SSL server is not available.

Explanation: The SSL server is not started or is notreachable. The SSLADMIN command must be issuedon the system where the SSL server is running.


System Programmer Response: Start the SSL server.

DTCSSL2421E The connection to the SSL server wasterminated.

Explanation: While processing the SSLADMINcommand, the connection to the SSL server wasterminated.


System Programmer Response: Use the SSLADMINQUERY command to determine if any action tookplace. For example, if the connection was droppedwhile processing an SSLADMIN STORE CERTcommand, you could issue ssladmin query cert * todetermine if the certificate has been stored in thecertificate database. Determine if the SSL server needsto be restarted.

DTCSSL2422E There is a memory shortage in theSSL server.

Explanation: A memory shortage in the SSL serverwas detected during processing of the SSLADMINcommand.


System Programmer Response: Determine the reasonfor the memory shortage and take appropriate action.

DTCSSL2423E An unexpected error occurred whileprocessing the SSLADMIN command.

Explanation: An unexpected error occurred duringSSLADMIN processing.



DTCSSL2424I Incorrect operand on SSLADMINcommand: operand.

Explanation: You specified an incorrect operand onthe SSLADMIN command.


System Programmer Response: Reissue the commandwith the correct syntax.

DTCSSL2425E Label length cannot be longer thanlength.

Explanation: The label specified on the SSLADMINcommand cannot exceed the length indicated in theerror message.


System Programmer Response: Reissue the commandwith a label of the correct length.

DTCSSL2426E Disk disk is not linked.

Explanation: The SSL server cannot be started unlessthis disk is linked.

System Action: The SSL server is not started. Nofurther checks are done.

System Programmer Response: Make sure that theSSL server virtual machine has an mdisk or linkstatement for this disk.

DTCSSL2427E Disk disk is not linked R/W.

Explanation: The SSL server cannot be started unlessthis disk is linked R/W.

System Action: The SSL server is not started. Nofurther checks are done.

System Programmer Response: Make sure that theSSL server virtual machine’s mdisk or link statementlinks this disk R/W.

DTCSSL2428I Port port is used for SSLadministration.

Explanation: This is the port that will be used for SSLadministration.



SSL Messages


DTCSSL2429I VDISK will be attempted for use as203 disk.

Explanation: The SSL server virtual machine musthave a 203 disk so the DTCPARMS can be passed tothe server. No 203 disk was found, so SSL processingwill attempt to establish a VDISK. However, VDISKauthorization must be previously established or thisattempt will be unsuccessful.

System Action: The system attempts to establish aVDISK.


DTCSSL2430I Unable to use VDISK.

Explanation: The attempt to establish a VDISK failed.

System Action: Defaults are used instead of theDTCPARMS values.

System Programmer Response: If the default valuesare not satisfactory, either set up a R/W 203 disk orauthorize VDISKs for the SSL server.

DTCSSL2431I DTCPARMS are not passed to the SSLserver.

Explanation: The values specified in DTCPARMS, thestack user ID, and any change to the administrationport will not be used.

System Action: Defaults are used.

System Programmer Response: If the default valuesare not satisfactory, set up a R/W 203 disk for the SSLserver.

DTCSSL2432I 203 disk is an unsupported DASDtype of dasd_type.

Explanation: The 203 disk is not defined on one of thesupported DASD types.

System Action: The values specified in DTCPARMS,the stack user ID, and changes to the administrationport are not used.

System Programmer Response: Place the 203 disk ona 3390, 3380, or FBA device.

DTCSSL2433I command command failed.

Explanation: One of the commands used in setting upthe VDISK failed.

System Action: No VDISK is set up.

System Programmer Response: Fix the problem withyour VDISK.

DTCSSL2434I Restart SSL server to activatecertificate.

Explanation: The SSLADMIN commands work with acopy of the certificate database on disk. Starting theSSL server loads the certificate database from disk intomemory. When you store a certificate in the database,that certificate does not become active until you restartthe SSL server to reload the updated database intomemory.


System Programmer Response: Restart the SSL server.

SSL Messages


SSL Server Return CodesTable 2. SSL Server Return Codes

Code Meaning

401 The system data was set to an invalid value.

402 Neither SSLV2 nor SSLV3 is enabled.

406 An IO error occurred on a data read or write.

407 The specified label in the key file could not be found.

410 An incorrectly formatted SSL message was received from the partner.

411 The message authentication code (MAC) was not successfully verified.

412 Unsupported SSL protocol or unsupported certificate type.

416 Internal error. Report problem to service.

418 The read failed. Report this error to service.

419 The write failed. Report this error to service.



425 The handle could not be created. Report this internal error to service.

426 Initialization failed. Report this internal error to service.

428 The specified key did not contain a private key.

SSL Server Reason CodesTable 3. SSL Server Reason CodesCode Name Meaning

1 EPERM Operation not permitted

2 ENOENT No such file or directory

3 ESRCH No such process

4 EINTR Interrupted system call

5 EIO I/O error

6 ENXIO No such device or address

7 E2BIG Arg list too long

8 ENOEXEC Exec format error

9 EBADF Bad file number

10 ECHILD No child processes

11 EAGAIN Try again

12 ENOMEM Out of memory

13 EACCES Permission denied

14 EFAULT Bad address

15 ENOTBLK Block device required

16 EBUSY Device or resource busy

17 EEXIST File exists

18 EXDEV Cross-device link

19 ENODEV No such device

20 ENOTDIR Not a directory

21 EISDIR Is a directory

22 EINVAL Invalid argument

23 ENFILE File table overflow

24 EMFILE Too many open files

25 ENOTTY Not a typewriter

26 ETXTBSY Text file busy

SSL Messages


Table 3. SSL Server Reason Codes (continued)Code Name Meaning

27 EFBIG File too large

28 ENOSPC No space left on device

29 ESPIPE Illegal seek

30 EROFS Read-only file system

31 EMLINK Too many links

32 EPIPE Broken pipe

33 EDOM Math argument out of domain of func

34 ERANGE Math result not representable

35 EDEADLK Resource deadlock would occur

36 ENAMETOOLONG File name too long

37 ENOLCK No record locks available

38 ENOSYS Function not implemented

39 ENOTEMPTY Directory not empty

40 ELOOP Too many symbolic links encountered

42 ENOMSG No message of desired type

43 EIDRM Identifier removed

44 ECHRNG Channel number out of range

45 EL2NSYNC Level 2 not synchronized

46 EL3HLT Level 3 halted

47 EL3RST Level 3 reset

48 ELNRNG Link number out of range

49 EUNATCH Protocol driver not attached

50 ENOCSI No CSI structure available

51 EL2HLT Level 2 halted

52 EBADE Invalid exchange

53 EBADR Invalid request descriptor

54 EXFULL Exchange full

55 ENOANO No anode

56 EBADRQC Invalid request code

57 EBADSLT Invalid slot

59 EBFONT Bad font file format

60 ENOSTR Device not a stream

61 ENODATA No data available

62 ETIME Timer expired

63 ENOSR Out of streams resources

64 ENONET Machine is not on the network

65 ENOPKG Package not installed

66 EREMOTE Object is remote

67 ENOLINK Link has been severed

68 EADV Advertise error

69 ESRMNT Srmount error

70 ECOMM Communication error on send

71 EPROTO Protocol error

72 EMULTIHOP Multihop attempted

73 EDOTDOT RFS specific error

74 EBADMSG Not a data message

75 EOVERFLOW Value too large for defined data type

76 ENOTUNIQ Name not unique on network

77 EBADFD File descriptor in bad state

78 EREMCHG Remote address changed

SSL Messages


Table 3. SSL Server Reason Codes (continued)Code Name Meaning

79 ELIBACC Can not access a needed shared library

80 ELIBBAD Accessing a corrupted shared library

81 ELIBSCN .lib section in a.out corrupted

82 ELIBMAX Attempting to link in too many shared libraries

83 ELIBEXEC Cannot exec a shared library directly

84 EILSEQ Illegal byte sequence

85 ERESTART Interrupted system call should be restarted

86 ESTRPIPE Streams pipe error

87 EUSERS Too many users

88 ENOTSOCK Socket operation on non-socket

89 EDESTADDRREQ Destination address required

90 EMSGSIZE Message too long

91 EPROTOTYPE Protocol wrong type for socket

92 ENOPROTOOPT Protocol not available

93 EPROTONOSUPPORT Protocol not supported

94 ESOCKTNOSUPPORT Socket type not supported

95 EOPNOTSUPP Operation not supported on transport endpoint

96 EPFNOSUPPORT Protocol family not supported

97 EAFNOSUPPORT Address family not supported by protocol

98 EADDRINUSE Address already in use

99 EADDRNOTAVAIL Cannot assign requested address

100 ENETDOWN Network is down

101 ENETUNREACH Network is unreachable

102 ENETRESET Network dropped connection because of reset

103 ECONNABORTED Software caused connection abort

104 ECONNRESET Connection reset by peer

105 ENOBUFS No buffer space available

106 EISCONN Transport endpoint is already connected

107 ENOTCONN Transport endpoint is not connected

108 ESHUTDOWN Cannot send after transport endpoint shutdown

109 ETOOMANYREFS Too many references: cannot splice

110 ETIMEDOUT Connection timed out

111 ECONNREFUSED Connection refused

112 EHOSTDOWN Host is down

113 EHOSTUNREACH No route to host

114 EALREADY Operation already in progress

115 EINPROGRESS Operation now in progress

116 ESTALE Stale NFS file handle

117 EUCLEAN Structure needs cleaning

118 ENOTNAM Not a XENIX named type file

119 ENAVAIL No XENIX semaphores available

120 EISNAM Is a named type file

121 EREMOTEIO Remote I/O error

122 EDQUOT Quota exceeded

123 ENOMEDIUM No medium found

124 EMEDIUMTYPE Wrong medium type

SSL Messages


SSL Messages


Chapter 20. TCP/IP Server Messages

This chapter contains TCPIP server messages.

Unnumbered MessagesThe following message is the only unnumbered message.

Error writing file fileid on disk — output halted

Severity: Warning.

Explanation: TCPIP encountered an error writing theindicated file.

User or Operator Response: Contact the systemprogrammer.

System Programmer Response: Examine the TCPIPvirtual machine console log to determine the cause of

the error. The probable cause is that the disk ordirectory is full, in which case a CMS disk full messageshould appear immediately before this error. Erase anyunnecessary files on the disk or directory, or increase itssize or allocation limit to avoid the problem.

System Action: Output to the file terminates.

Source File: TCUTIL PASCAL

Procedure Name: ReportIoError

Numbered MessagesThis section contains the numbered messages.

DTCATM002I ATM device name: Started sense ondevice; SIOCC code

Explanation: A Sense operation was started on anATM device but received an unexpected condition code.

System Action: The device is shut down.

System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.

DTCATM003I ATM device name: Cannot get size-byteenvelope for purpose

Explanation: An envelope of size bytes was requiredto hold a datagram for the indicated purpose but noenvelopes were available.

System Action: The datagram is dropped.

System Programmer Response: Increase the TCPIPvirtual machine storage size.

DTCATM011E ATM device name: Unexpected SIOCCcode from Write IDX operation on device

Explanation: The initial write to an ATM device failedbecause of an unexpected condition code.



DTCATM012E IDX Activate failed on input deviceaddress with cause code failure

Explanation: The activation of the ATM input deviceat address was rejected with a failure code.


System Programmer Response: Report the problem tothe IBM Support Center.

DTCATM021E ATM device name: Unexpected SIOCCcode from Read IDX operation on device

Explanation: The initial read from an ATM devicefailed because of an unexpected condition code.



DTCATM022E IDX Activate failed on output deviceaddress with cause code failure

Explanation: The activation of the ATM output deviceat address was rejected with a failure code.




DTCATM041I ATM device name: PackWrites flushingEnvelopeQueue - Device status: state

Explanation: TCPIP is attempting to pack data for awrite operation, but the ATM device is either not yetinitialized or is shutting down. The outgoing packetsare discarded. If the device is in the process of beinginitialized, it will become available to TCPIP once itsinitialization is complete. If the device is in the processof being shut down, it will become unavailable toTCPIP once its shutdown is complete.

DTCATM045E ATM device dev_name: Error gettingXA subchannel id for dev_addr ordev_addr +1

Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.

System Action: TCPIP continues but the device isshutdown.

System Programmer Response: Review the deviceconfiguration areas that follow, and ensure the variousaspects for this device are in agreement:

v Ensure the indicated device is properly configured inthe z/VM Control Program (CP).

v Ensure both of the indicated device addresses areattached to the TCPIP virtual machine. Verify the:Attach tag values, as specified for this device in theDTCPARMS file, are correct.

v Review the TCP/IP server configuration file DEVICEand LINK statements that correspond to this device,and ensure that all operands have been correctlyspecified.

DTCATM050I ToAtm: OSA reports count localaddresses for device name

Explanation: More than one ATM physical address isassociated with device name.

System Action: TCPIP uses the first ATM physicaladdress.

DTCATM051I ToAtm: OSA reports local address nsapfor device name

Explanation: The ATM physical address for devicename is displayed.

DTCATM066E ATM device name: ToAtmUnpackReads: Termination failure codefailure

Explanation: OSA has terminated the operation ofATM device name because it detected a failurecondition.


System Programmer Response: Based on the failurecode, take action as follows:

Code Action

04 Ensure that the pair of real OSA-2device numbers attached to TCPIP areassociated with the same adapter andthat the even device number isattached as the virtual device numberspecified on the DEVICE statement.

10 The pair of real OSA-2 devicenumbers attached to TCPIP have beenquiesced. Correct the situation andrestart the device.

other Report the problem to the IBMSupport Center.

DTCATM069I ATM device name: ToAtm: DeferredSioCC code on device

Explanation: An I/O operation to a device received adeferred condition code.

System Action: If the code is 0, TCPIP continues withthe operation on the device. Otherwise, if the operationis to the output address, TCPIP purges the outputenvelope queue; if it is to the input address, TCPIPretries the read operation after 30 seconds.


DTCATM070I ATM device name: ToAtm: Sioreturned code on device

Explanation: An I/O operation to a device received theindicated condition code.

System Action: TCPIP continues. If the code isnonzero, other messages indicate how the condition ishandled.


DTCATM071E ToAtm: Diagnose 98 error code code

Explanation: An error code was reported by Diagnose98.


System Programmer Response: Determine the causeof the error using the information about Diag 98 errorcodes in the TCP/IP Diagnosis Guide and respond asindicated.

TCP/IP Server Messages


DTCATM073I ATM device name: Stored CSW is: csw

Explanation: TCPIP attempted to start an I/Ooperation to the device and an error occurred. TheChannel Status Word (CSW) from the I/O operation isindicated in the message.

System Action: If the operation is to the outputaddress, TCPIP purges the output envelope queue. If itis to the input address, TCPIP retries the read operationafter 30 seconds.


DTCATM079E ATM device name: Unexpected SIOCCcode from SenseId operation on device

Explanation: TCPIP was attempting to validate theATM device but received a nonzero condition code inresponse to a Sense ID operation.


System Programmer Response: Ensure that the deviceis attached to TCPIP. Verify that the OSA hardware isoperational. If the problem persists, report it to the IBMSupport Center.

DTCATM080I ATM initializing:

Explanation: TCP/IP is initializing the ATM devicedescribed in subsequent messages.

DTCATM081E Link name specifies invalid networktype net_type - ATM will not beinitialized

Explanation: A link for an ATM device is not of typeATM.


System Programmer Response: Correct the LINKstatement.

DTCATM082E ATM shutting down:

Explanation: TCP/IP is terminating the ATM devicedescribed in subsequent messages.

System Programmer Response: If the device was notterminated explicitly, examine the TCPIP console log todetermine why the device was shut down. If necessary,take corrective action as described for the messageexplaining the shut down.

DTCATM083E ATM device name: Unexpected CSWfrom SenseId command on device

Explanation: TCPIP was attempting to validate theATM device but received an unusual Channel StatusWord in response to a Sense ID operation.


System Programmer Response: Ensure that the deviceis attached to TCPIP. Verify that the OSA hardware isoperational. If the problem persists, report it to the IBMSupport Center.

DTCATM084E ATM device name: Unexpected SenseID data: sense_data on device

Explanation: TCPIP was attempting to validate theATM device but received sense_data in response to aSense ID operation.


System Programmer Response: Ensure that the deviceis an OSA-2. Verify that the OSA hardware isoperational. If the problem persists, report it to the IBMSupport Center.

DTCATM087I ATM device name: Sense data fordevice: sense_data

Explanation: In response to a Unit Check condition ondevice, TCPIP issued a Sense operation and receivedsense_data in response.



DTCATM089E ATM device name: Channel error ondevice

Explanation: TCPIP received a channel error on device.



DTCATM091E ATM device name: ReceivedDEVICEend interrupt on device --probable OSA restart

Explanation: TCPIP received an unsolicited DeviceEnd interrupt on OSA device.

System Action: The device is restarted.



Chapter 20. TCP/IP Server Messages 297

DTCATM092E ATM device name: Unit Check ondevice

Explanation: TCPIP received a Unit Check on device.



DTCATM093E ATM device name: Unit Exception ondevice

Explanation: TCPIP received a Unit Exception ondevice.



DTCATM094E ATM device name: Unknown interrupton device

Explanation: TCPIP received an unidentified interrupton device.



DTCATM111I ToAtm: Incoming requests enabled fordevice name

Explanation: Device name is accepting requests toestablish switched virtual circuits.


DTCATM112I ToAtm: Starting PVC pvc for link name

Explanation: Private Virtual Circuit pvc for link nameis being started.


DTCATM113I ToAtm: Started PVC pvc for link name

Explanation: Private Virtual Circuit pvc for link namehas been established.


DTCATM118I ToAtm: Stopping PVC pvc for linkname

Explanation: Private Virtual Circuit pvc for link nameis being stopped.


DTCATM120I ToAtm: Incoming requests disabledfor device name

Explanation: Device name is no longer acceptingrequests to establish switched virtual circuits.


DTCATM208I AtmArpIn: AddTranslation failed

Explanation: An attempt to add an entry to theaddress translation table was unsuccessful.

System Action: Traffic cannot be routed to adestination in the ATM network.

System Programmer Response: Increase the TCPIPvirtual machine storage size. If the problem persists,report it to the IBM Support Center.

DTCA22003I A220 device device_name: Cannot getenvelope error

Explanation: TCPIP attempted to get an envelope toreceive the data, but no envelopes were available. Thepacket is discarded.


User or Operator Response: Tell the systemprogrammer about the error.

System Programmer Response: Increase the envelopepool size using the ENVELOPEPOOLSIZE statement inthe PROFILE TCPIP file.

DTCA22044I A220 device dev_name: Error getting XAsubchan id for dev_addr or dev_addr+1









DTCA22009I A220 device device_name: PackWritesflushing EnvelopeQueue. Device status:status

Explanation: The HYPERchannel A220 adapter driveris flushing envelopes that are queued for outputbecause the device is not ready for output. The packetsin the envelopes are dropped and the envelopes freedto receive other data. The status in the messageindicates whether the device is currently initializing.

System Action: The queued envelopes are returned tothe free pool and device initialization continues if itwas already in progress.



DTCA22017I A220 device device_name: ToA220:Deferred SioCC rc on device device

Explanation: A deferred condition code was received.


User or Operator Response: If the condition code is 2or 3, check for hardware problems. If other problemsare indicated, you will receive more messages.


DTCA22019I A220 device device_name: ToA220: Sioreturned rc on device device

Explanation: A condition code was received.


User or Operator Response: If the condition code is 2or 3, check for hardware problems. If other problemsare indicated, you will receive more messages.


DTCA22020I A220 device device_name: ToA220: Sioreturned rc on device device Diag 98error code code

Explanation: A diagnostic call returned the indicatederror. For more information about Diag 98 error codes,see the book TCP/IP Planning and Customization.


User or Operator Response: Consult the TCP/IPDiagnosis Guide for an explanation of Diag 98 errorcodes and take the indicated action.


DTCA22021I A220 device device_name: Stored CSW is:channel_status_word

Explanation: The stored channel status word (CSW) isdisplayed.




DTCA22026I A220 device device_name: UnexpectedSIOCC rc from SenseSt operation.

Explanation: A Sense Status command wasunsuccessful. Initialization of this device stops.


User or Operator Response: Check your hardwareand the PROFILE TCPIP files for the host and theHYPERchannel A220 adapter for errors. The most likelyerror is that the device was not started.

System Programmer Response: Assist the user asnecessary.

DTCA22027I A220 initializing: device

Explanation: The HYPERchannel A220 adapter isinitializing the indicated device.




DTCA22028I Link link specifies invalid network typenetwork_type. A220 will not be initialized

Explanation: The indicated LINK statement specifies anetwork type not recognized by TCPIP. TheHYPERchannel A220 adapter is not initialized.


User or Operator Response: Check the LINKstatement for the associated device in the PROFILETCPIP file to make sure that it specifies a valid networktype.


DTCA22029E A220 shutting down:

Explanation: The HYPERchannel A220 adapter isshutting down because of an error or a user request.

System Action: TCPIP halts.

User or Operator Response: Check the other consolemessages to determine the cause of the shutdown.




DTCA22030I A220 device device_name: UnexpectedCSW from SenseStatistics command ondevice device

Explanation: A SenseStatistics command wasunsuccessful. Initialization of this device stops.


User or Operator Response: Check your hardwareand the PROFILE TCPIP files of the associated devicesfor errors.


DTCA22034I A220 device device_name: Channel erroron device device

Explanation: An unexpected channel error wasencountered. TCPIP expected to find the channel open,but the channel is closed or in use.



System Programmer Response: Check the DEVICEand LINK statements in the PROFILE TCPIP file tomake sure the device is properly configured. If thestatements are properly configured, check yourhardware for errors. For more information on DEVICEand LINK statements, see the book TCP/IP Planning andCustomization.

DTCA22037I A220 device device_name: ReceivedDEVICEend on device device --probableA220 reset

Explanation: The indicated device was interrupted,which probably means the device was reset. A messageshould follow indicating that TCPIP is attempting torestart the device.



System Programmer Response: If the device is unableto perform a restart, take it off line and consult theoperator’s manual to determine the correcttroubleshooting procedure.

DTCA22038I A220 device device_name: Unknowninterrupt on device device

Explanation: The indicated device encountered anunexpected interrupt.


User or Operator Response: Check your hardware forerrors.


DTCA22041I A220 device device_name: Droppingtoo-large output packet length_of_databytes

Explanation: The output packet exceeded the size ofthe HYPERchannel A220 adapter’s data buffer. TCPIPdropped the packet.


User or Operator Response: Check the PROFILETCPIP file for the host and the A220 device to makesure that the maximum packet sizes are compatible.

System Programmer Response: If necessary, increasethe size of the envelopes using theENVELOPEPOOLSIZE statement in the PROFILETCPIP file. For more information about theENVELOPEPOOLSIZE statement, see the book TCP/IPPlanning and Customization.

DTCA22042I A220 device device_name: Droppingpacket for host host_address -- HCHaddress not known

Explanation: The HYPERchannel A220 adapter isdropping a packet for the indicated host because thehyperchannel address of the host is not known.


User or Operator Response: Notify the systemprogrammer of the error.

System Programmer Response: Check the HOMEtable in the PROFILE TCPIP file to make sure that thereis a valid home hardware address specified for theindicated link. For more information on homehardware addresses, see the book TCP/IP Planning andCustomization.

DTCA22043I A220 device device_name: UnpackReadsdropping too-large packet, number bytes,current max maximum_packet_size

Explanation: The HYPERchannel A220 adapterreceived a datagram that was too large to fit into anenvelope. The datagram was dropped.


User or Operator Response: Notify your systemprogrammer of the error.

System Programmer Response: Increase the largeenvelope size available to the A220 device using theENVELOPEPOOLSIZE statement in the PROFILETCPIP file. For more information about theENVELOPEPOOLSIZE statement, see the book TCP/IPPlanning and Customization.



DTCA22044I A220 device device_name: Error gettingXA subchan id for input_address oroutput_address

Explanation: The device address specified on theDEVICE statement for the HYPERchannel A220 adapterin the PROFILE TCPIP file could not be converted toan XA subchannel ID. All I/O operations in XA modeare performed based on a subchannel ID. The A220device is not started.



System Programmer Response: Make sure that theindicated devices are online and connected to the A220adapter at the proper ports with the proper addressesconfigured. Also make sure that the address specifiedin the DEVICE statement in the PROFILE TCPIP filematches the actual addresses for the A220 device.

DTCA22046I Exceeded unit check retry limitmaxretries on device device

Explanation: TCPIP has exceeded the limit for thenumber of attempts to restart the specified device. Thedevice is not initialized.



System Programmer Response: Check the PROFILETCPIP file to make sure that the DEVICE and LINKstatements for the device are properly configured. If thestatements are correct, consult the operator’s manualfor the device to determine the correct troubleshootingprocedure.

DTCA22047I A220 device device_name: Sense data fordevice device: senseinfo

Explanation: This message displays sense informationfor the indicated device.




DTCCET003I ILANS device device_name: DispatchTr:Cannot process ARP packet; homehardware address not known

Explanation: The ARP packet cannot be processedbecause the IP address has not been found in the ARPcache.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make sure

that the address is valid and in the correct format. Seethe book TCP/IP Planning and Customization for moreinformation on the HOME statement.

System Programmer Response: Assist the user asneeded.

DTCCET005I ILANS device device_name:SET_NET_PARMS.confirm:

Explanation: CETI parameters are being checked. Astatus message will follow.




DTCCET006I Completion status status, ExtendedStatus status

Explanation: TCPIP completed checking the CETIparameters and is displaying status information.




DTCCET007I ILANS initialization aborted due toerror

Explanation: Initialization ended due to an error inthe network parameter check.

System Action: TCPIP halts.

User or Operator Response: Check the DEVICE andLINK statements to make sure that they are correctlyconfigured. For more information on the DEVICE andLINK statements, see the book TCP/IP Planning andCustomization.


DTCCET008I ILANS device device_name: SendingDLM_RTV_ATTRIB.request

Explanation: A request was sent to obtain thehardware address; a status message will follow inmessage DTCCET009I.




DTCCET009I ILANS device device_name:DLM_RTV_ATTRIB.confirm:Completion status status

Explanation: The hardware address is obtained andchecked, as requested (DTCCET008I) and the status isdisplayed.






DTCCET010I ILANS initialization aborted due toerror

Explanation: Initialization ended because therequested hardware address was not confirmed.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make surethat the address is valid and in the correct format. Seethe book TCP/IP Planning and Customization for moreinformation on the HOME statement.


DTCCET011I Node address: address

Explanation: This message displays the address of thenode that is currently active and adds this nodeaddress to the IP translation tables.




DTCCET012I ILANS device device_name: SendingDL_ACTIVATE_SAP.request

Explanation: A request to open the Logical LinkControl Service Access Point (LLC SAP) to send andreceive unsequenced information frames is being sent.




DTCCET013I LengthOfLinkRelated lengthAddressNotRecognized addressFrameNotCopied frame

Explanation: The length of the link and destinationaddress are displayed. The frame was not copiedbecause the specified address was not known.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make surethat the address is valid and in the correct format. Seethe book TCP/IP Planning and Customization for moreinformation on the HOME statement.


DTCCET014I TransmitStrip strip UnauthorizedApapplication UnauthorizedMf message file

Explanation: This message displays unauthorizedapplications or files.


User or Operator Response: Check the ALLOWAPPLstatement in the PROFILE TCPIP file to make sure itspecifies the application name. See the book TCP/IPPlanning and Customization for more information on theALLOWAPPL statement.


DTCCET015I SoftError error TransmitBeacon beaconIoaStatusOverrun status Framesdiscarded frames Spurious Interruptcount

Explanation: ILANS displays a message indicatingthat there is a problem with a ring, which mightrequire that the data be retransmitted. The counter forthe frequency of soft errors is incremented. IfT(soft_error_report) has expired, a Report Soft ErrorMAC frame is transmitted by the ring station, afterwhich the ring station resets the counter.


User or Operator Response: If the ring does notrecover, notify your LAN manager.


DTCCET017I FramesTxed number FramesRxednumber MacFramesTxed numberMacFramesRxed number

Explanation: Displays frames (including MAC frames)that were transmitted and received.




DTCCET018I RiFramesTxed number RiFramesRxednumber LineError error

Explanation: This message displays frames that weresent by the ring station due to an error in framesequencing.






DTCCET019I Internal Error error BurstError errorAriFciError error

Explanation: This message indicates an internal error,possibly related to another ring station. It also displaysthe number of frames that are not being received as aresult of the internal error.




DTCCET020I AbortDelimiter delimiter LostFramenumber RxCongestion congestion

Explanation: The station has not seen a startingdelimiter for a frame within a specified time. Thepossible cause is that the input buffer of the station isfull and cannot copy the frame. Since the frame is notcopied during several tries, the originating ring stationdiscards the frame when it returns. Frames that are notcopied as a result of the congestion are displayed. Thereceiver-congestion notification is sent to the LANmanager.




DTCCET021I FrameCopiedError error FrequencyErrorerror TokenError error

Explanation: The ring station has detected that theerror detected-bit is set to B’1’ indicating that a tokenneeds to be transmitted. Frames that have not beencopied as a result of this error are displayed.




DTCCET022I DmaBusError error DmaParityErrorerror AddressNotRecognized address

Explanation: The destination address was notrecognized due to an error in parity check.




DTCCET023I FrameNotCopiedError numberTransmitStripError errorUnauthorizedAp application

Explanation: This message indicates that TCPIPencountered an unauthorized application whichresulted in an error with frames being transmitted.




DTCCET024I UnauthorizedMf message file SoftErrorerror TransmitBeacon beacon

Explanation: An unauthorized message file wasdetected causing an interrupt.




DTCCET025I IoaStatusOverrun statusFramesDiscarded numberSpuriousInterrupts interrupts

Explanation: This message displays the number offrames that were discarded as a result of anunauthorized interrupt.




DTCCET026I Threshold data entry record:

Explanation: The following messages displayinformation about the threshold record:v ThresholdCounterId Idv Threshold values: valuesv Threshold counters: value




DTCCET027I ThresholdCounterId Id

Explanation: This message indicates the number offrames sent by the ring station.




DTCCET028I Threshold values: values

Explanation: This message displays the thresholdvalues.






DTCCET029I Threshold counters: value

Explanation: This message displays the thresholdcounters.




DTCCET030I Measurement data entry record:

Explanation: The following messages displayinformation about the data measurement record:v OverflowedCounterId valuev Measurement values:




DTCCET031I OverflowedCounterId value

Explanation: The threshold for the number ofattempts at passing was set at a constant value; if thecounter reached a value greater than this constant, it isdisplayed here.




DTCCET032I Measurement values:

Explanation: This message displays the message″Measurement values″ with information to follow.




DTCCET033I Beaconing information:

Explanation: The following messages displayinformation about beaconing frames, a frame sent byan adapter indicating that there is a problem with ring:v NextUpstreamNeighbor address Node addressv BeaconTypeSubvector ‘type’




DTCCET034I NextUpstreamNeighbor address Nodeaddress

Explanation: This message displays information onthe beaconing ring station’s nearest active upstreamneighbor (NAUN).




DTCCET035I BeaconTypeSubvector ‘type’

Explanation: This message displays the beacon typesubvector. The subvector provides information as to thereason why the ring station is beaconing.




DTCCET036I ILANS device device_name:DLM_STATUS.indication received:

Explanation: Information about error status check isdisplayed in the next message (StatusIdentifier ‘status’StatusCode ‘code’ ExtendedStatus ‘status’)




DTCCET037I StatusIdentifier ‘status’ StatusCode‘code’ ExtendedStatus ‘status’

Explanation: This message displays statusinformation.




DTCCET038I Unknown DataFormatType ‘type’

Explanation: This message indicates that TCPIP hasencountered a data type it does not recognize.




DTCCET039I ILANS device device_name:DL_STATUS.indication received:

Explanation: The following messages displayinformation about the status of the data error:

DataLength length



StatusType ‘type’ StatusIdentifier ‘identifier’StatusCode ‘code’ OriginalError ‘error’




DTCCET040I DataLength length

Explanation: This message displays the length of thedata information.




DTCCET041I StatusType ‘type’ StatusIdentifier‘identifier’ StatusCode ‘code’ OriginalError‘error’

Explanation: This message displays the status of checkon data.




DTCCET044I ILANS device device_name:DL_ACTIVATE_SAP.confirm:Completion status status, PSapId ‘id’

Explanation: This message displays the status of therequest to update control blocks. It also displays theservice access point ID.




DTCCET045I ILANS initialization aborted due toerror.

Explanation: ILANS initialization was stopped,possibly because a request to update control blocks wasnot completed.




DTCCET046I ILANS device device_name:DL_MSG.confirm: Completion statusstatus

Explanation: This message displays the status of theupdating control blocks operation.




DTCCET047I ILANS device device_name: UnknownLLC primitive type

Explanation: TCPIP cannot update control blocksbecause of an unknown primitive type.




DTCCET049I ILANS device device_name: UnknownMAC primitive type

Explanation: For the MsgType MTYP_MAC, there is aprimitive type other than DLMrtvATTRconf orDLMstatusIND.




DTCCET050I ILANS device device_name: UnknownCeti Message

Explanation: The MsgType and primitive type areunknown.




DTCCET051I ILANS device device_name:IlansSetExheader: No PSapId, cannot setheader.

Explanation: The PSapId is not valid, possibly becauseinitialization was not completed. The SAP numbers arepreassigned codes that indicate which subprotocol isused in the rest of the frame. TCPIP discards theenvelope.




DTCCET053I ILANS device device_name: Droppingpacket on link name for first hop address-- ARP resent packet but address nogood.

Explanation: The address received from the AddressResolution Protocol (ARP) tool for the indicated packetwas incorrect, so TCPIP drops the packet.




User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make surethat the address is valid and in the correct format.Check the book TCP/IP Planning and Customization formore information on the HOME statement.


DTCCET054I ILANS device device_name:SetExHeader: Cannot send ARP packet;home hardware address not know.

Explanation: The ARP packet cannot be sent to itsdestination because the home address is not known.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make surethat the address is valid and in the correct format.Check the book TCP/IP Planning and Customization formore information on the HOME statement.


DTCCET056I ILANS device device_name: SendingSET_NET_Parms.request

Explanation: CETI sends a request to set networkparameters for Level 2 initialization. TCPIP sets thereturn code equal to CETIok.




DTCCET057I ILANS device device_name: Droppingtoo large input, length bytes, max size

Explanation: The data is too large for the envelopeprovided. The message length and size are displayed.


User or Operator Response: Increase the envelopesize available to the CETI device using theENVELOPEPOOLSIZE statement in the PROFILETCPIP file. For more information about theENVELOPEPOOLSIZE statement see the book TCP/IPPlanning and Customization.


DTCCE1003I device_type device_name: CETI: Badinterrupt on device, [device_name] InitState [device_status]

Explanation: This message displays an unexpectedinterrupt on the CETI device. The interrupt is ignored.




DTCCE1010I CETI device_type device_name: CetiInitialization Failure

Explanation: The I/O operation was not startedresulting in an unsuccessful initialization of the device.TCPIP logs the error.


User or Operator Response: Investigate the reason forthe interrupt that caused failure to initialize CETI. Apossible resolution could be found in the followingerror message. If unable to resolve and restartinitialization, inform the system programmer about theerror.

System Programmer Response: Usually duringinitialization, interrupts cause the next I/O operation inthe startup sequence to be initiated. The interrupt thatcaused an unsuccessful initialization is an incorrect one.Evaluate the interrupt and restart initialization of CETI.

DTCCE1011I Device error on Start Io operation.Device device SIOCC rc Ceti State status

Explanation: A device error was detected for I/Ooperation. The device type is displayed, its status andthe status of the I/O ports are displayed.




DTCCE1012I Stored CSW: csw

Explanation: The channel status word (CSW) providesinformation about the termination of I/O operation. Inthis message, CSWStored provides information as towhether data is forthcoming.




DTCCE1013I Sense data for device device

Explanation: Displays status on check of whetherthere is data waiting for the CETI device.






DTCCE1014I CETI UNIT CHECK: device device SenseData SFLG: sflg STAT: status OTHR: otherACK: ack

Explanation: The following table contains informationpertaining to the sense data of the CETI device.

Message DescriptionCETI UNIT CHECK

sense data status for the device.Sense Data SFLG

sets flag for the sense data.STAT status of the sense data flag.OTHR if no data has been sensed.ACK acknowledgment of information.




DTCCE1018E CETI shutting down:

Explanation: The CETI device has shut down. Storagefor data port buffers and channel control words (CCW)is discarded.

System Action: CETI halts. TCPIP continues.

User or Operator Response: Inform the systemadministrator.

System Programmer Response: Check the reason forthe error, clear I/O buffers, and start the reinitializationprocedure for CETI.

DTCCE1020I SendCetiMessage rejecting too-longmessage. Length DataLen, Max lengthMaxMsgLen

Explanation: The message was rejected because it islarger than allowed by this adapter.


User or Operator Response: Increase the buffer sizeby changing the size set in theDATABUFFERPOOLSIZE statement in the PROFILETCPIP file. For more information about theDATABUFFERPOOLSIZE statement, see the bookTCP/IP Planning and Customization.

System Programmer Response: Assist the user asneeded.

DTCCE1031I CETI device initializing.

Explanation: The CETI device is in the process ofinitialization.




DTCCE1032I Dcb invalid for ELANS -- must haveone link of type ETHERNET,ETHERor802.3, or 802.3.

Explanation: The data format is not valid for thisELANS device; it should be in either the ETHERNET,ETHERor802.3, or 802.3 format.


User or Operator Response: Check the DEVICE andLINK statements to make sure that they are correctlyconfigured. Check the book TCP/IP Planning andCustomization about the DEVICE and LINK statements.


DTCCE1033I DCB invalid for ILANS -- must haveone link of type IBMTR

Explanation: The data format is not valid for thisILANS device; it should be in the IBM token ringformat.




DTCCE1034I DCB invalid for X25ICA -- must haveone link of type X25ICA

Explanation: The data format is not valid for thisX25ICA device; it should be in the X25ICA format.




DTCCE1037I CETI device_type device_name: Ceti:Flushing output queue; state is devicestatus

Explanation: The output queue is being emptied; theenvelopes are being freed.






DTCCE1038I Ceti driver will set PDSM flag

Explanation: The port data status flag (PDSF) is set bythe CETI driver. This flag defines the state of theinbound and outbound ports.




DTCCE1039I Error getting XA subchan id fordev_addr+1 or dev_addr or dev_addr+3 ordev_addr+2

Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one of thelisted addresses for the indicated device.






DTCCE2001I ELANS device name:

Explanation: This message displays the name of theEthernet device.




DTCCE2003I Bad Ethernet trailer packet Type wastype length length

Explanation: The datagram within the envelope wasfound to be in the trailer format; in this type of format,the protocol headers follow the data. The packet typeand length are displayed. The format is changed to thenormal format where the protocol header precedes thedata.




DTCCE2005I DispatchEther: Cannot process ARPpacket; home hardware address notknown.

Explanation: The ARP packet cannot be processedbecause the IP address has not been found in the ARPcache.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file to make surethat the Ethernet address is valid and in the correctformat. Check the book TCP/IP Planning andCustomization for more information on the HOMEstatement.


DTCCE2007I Net parms record:

Explanation: The network parameters are checked andthe status is displayed in the following message(DTCCE2008I).




DTCCE2008I Version version Revision revision NetTypetype Flags flags

Explanation: This message displays information aboutthe network parameters. This message followsDTCCE2007I.




DTCCE2009I Ethernet Address: address

Explanation: This message displays the Ethernetaddress of the message. The Ethernet address is addedto the IP translation table.




DTCCE2010I Ceti Ethernet Statistics record

Explanation: These messages display the Ethernetstatistics record on the normal logging file. Thestatistics record is normally produced due tounsuccessful hardware. However, it can be informativeas well, if the operator needs to know whether certaincounters are set in the statistics record.






DTCCE2011I Frames in number Frames Out numberFrames Lost number





DTCCE2012I Runt Frames number CRC Errors numberCollisions number





DTCCE2013I Multicast In value Broadcast In value





DTCCE2014I Unaddressed frames numberUnaddressed Multi number





DTCCE2015I Excess Collisions number Out of windowCollisions number





DTCCE2016I Alignment errors number ShortedEthernet value





DTCCE2017I Time Delay Reflectometer value Too-longpackets value

Explanation: These messages display the Ethernetstatistics record on the normal logging file. Thestatistics record is normally produced due tounsuccessful hardware, however, it can be informativeas well, if the operator needs to know whether certaincounters are set in the statistics record.




DTCCE2018I Ceti Level 2 Error Record

Explanation: These messages display informationfrom the CETI Level 2 Error Record.




DTCCE2019I Output stat number, ZeroField value,SeqNo number







DTCCE2020I FlushedSrcEther value,FlushedSetNetParms value,FlushedQueryNetParms value





DTCCE2021I FlushedQueryNetStats valueFlushedOther value





DTCCE2023I Unknown Ceti Message:

Explanation: The message type is a type unknown toCETI. The following are valid settings for messagetypes:

MTYP_SRCether = 1; (ELANS)MTYP_MAC = 2; (ILANS)MTYP_LLC = 4; (ILANS)MTYP_DLC = 5; (X.25)MTYP_PLC = 6; (X.25)MTYP_ERRORmessage = 128; (ELANS)MTYP_SETnetPARMS = 129; (ALL CETI parameters)MTYP_QUERYnetPARMS = 130; (ELANS)MTYP_QUERYnetSTATS = 131; (ELANS)


User or Operator Response: Reissue the messageusing a valid message type.

System Programmer Response: Assist the operator asrequired.

DTCCE2025I Dropping packet on link link for firsthop address - ARP resent packet butaddress no good

Explanation: An Address Resolution Protocol (ARP)packet was generated based on the type of link(Ethernet or 802.3). The link is displayed as well as theinternet address of the first hop. The packet is droppedbecause the address is not valid. TCPIP increments theerror counter.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file and make sure

that the address is valid and in the correct format. Seethe book TCP/IP Planning and Customization for moreinformation on the HOME statement.


DTCCE2026I SetExHeader: Cannot send ARP packet;home hardware address not known

Explanation: The ARP packet cannot be processedbecause the home hardware address is not known.


User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file and make surethat the Ethernet address is valid and in the correctformat. Check the book TCP/IP Planning andCustomization for more information on the HOMEstatement.


DTCCE2028I Reading ELANS flags from file name

Explanation: The ELANS flags are read from a file.The file name is displayed.




DTCCE2029I Using Ethernet flags ‘flags’

Explanation: This message displays Ethernet flags.




DTCCE2030I Dropping too-large input, length bytes,max size

Explanation: TCPIP received the next pendingmessage from the input buffer of the specified datacontrol block (DCB). However, the message length islarger than the envelope size. The message length andthe datagram size + size of {Ether8022 | Ether8023}header are displayed. The packet is not sent.


User or Operator Response: Increase the largeenvelope size available to the CETI device using theENVELOPEPOOLSIZE statement in the PROFILETCPIP file. For more information about theENVELOPEPOOLSIZE statement, see the book TCP/IPPlanning and Customization.




DTCCLW004E CLAW device dev_name: Error gettingXA subchan id for dev_addr ordev_addr+1







DTCCLW044E CLAW device name: Claw linkclaw_link_num has no associated LCB

Explanation: A CLAW frame was read and the linknumber associated with the CLAW frame is notassigned to any LINK.



System Action: The frame, and the IP datagram in theframe, is discarded.

DTCCLW082E Claw shutting down:

Explanation: The CLAW device is shutting down. Thisis a normal response to a stop command for the deviceor for TCPIP.

User or Operator Response: If a command was notissued to stop the device, use the OBEYFILE commandto restart it.


System Action: The device is stopped.

DTCCLW108E Claw device claw_name: Incorrect PCAmicrocode version version_num.

Explanation: An incorrect version of the microcodehas been loaded onto the PCA adapter in the RISCSystem 6000.


System Programmer Response: Obtain the correctlevel of the PCA microcode and restart the PCA

adapter. Then use the OBEYFILE command to restartthe CLAW device.


DTCCLW109E Claw device claw_name: Received hostname host_name adapter nameadapter_name, Expected host namehost_name adapter name adapter_name

Explanation: The CLAW device parameters do notmatch the RISC System 6000 PCA adapter configurationparameters.


System Programmer Response: Correct the host andadapter name parameters on either the PCA adapterconfiguration or the CLAW DEVICE statement. Thenuse the OBEYFILE command to restart the CLAWdevice.


DTCCLW110E Claw device claw_name: PCA receivesize of recv_value is smaller thantransmit size of trans_value.

Explanation: The CLAW device parameters do notmatch the RISC System 6000 PCA adapter configurationparameters. The CLAW write buffer size on theDEVICE statement is larger than the PCA adapterreceive buffer size, causing data truncation.


System Programmer Response: Correct the buffer sizeon either the PCA adapter configuration or the CLAWDEVICE statement. Then use the OBEYFILE commandto restart the CLAW device.


DTCCLW111E Claw device claw_name: PCA transmitsize of trans_value is greater than receivesize of recv_value.

Explanation: The CLAW device parameters do notmatch the RISC System 6000 PCA adapter configurationparameters. The CLAW read buffer size on the DEVICEstatement is larger than the PCA adapter transmitbuffer size, causing data truncation.


System Programmer Response: Correct the buffer sizeon either the PCA adapter configuration or the CLAWDEVICE statement. Then use the OBEYFILE commandto restart the CLAW device.




DTCCLW115E Claw device claw_name: Confirm linklinkid does not match response link linkid

Explanation: The CLAW link establishment protocol isa three-step process:

v An application makes a connection request to theadapter.

v The adapter responds with a connection response,defining the link between a pair of applications.

v The other application accepts the connection requestby issuing a confirm request.

This message indicates that the link ID in the confirmmessage was not valid.

User or Operator Response: The system action canresult in the CLAW device remaining in the startedstate with no data flowing. It may be necessary toSTOP and START the device with OBEYFILEcommands.


System Action: The invalid link is disconnected.

DTCCTC002E CTCA device device: Started sense ondevice device. SIOCC value

Explanation: TCPIP received a unit check and starteda sense channel control word (CCW) to get the senseinformation.




DTCCTC004E CTC packet too big:bytestomove=number

Explanation: The CTC packet received is larger thanthe large envelope size.



System Programmer Response: Either decrease themaximum transmission unit (MTU) size on the remotemachine or increase the large envelope size in the thePROFILE TCPIP file. Use theLARGEENVELOPEPOOLSIZE statement to increase thelarge envelope pool size. See the book TCP/IP Planningand Customization for more information about theLARGEENVELOPEPOOLSIZE statement.

DTCCTC008E CTCA device device: UnpackReads:Incorrect block header nnnn at inputposition nnnn, packet length nnnn -discarding remainder of block

Explanation: TCPIP found an error in the packetwhile attempting to unpack the data received.



System Programmer Response: Check for aprogramming error on the sending side.

DTCCTC045E CTCA device dev_name: Error gettingXA subchan id for dev_addr ordev_addr+1







DTCCTC058E CTCA device device: UnexpectedNetwork type: type at positioninput_position

Explanation: The system encountered an unexpectednetwork type as the result of a configuration error.



System Programmer Response: Check the networkconfiguration statements in the PROFILE TCPIP file tomake sure that they correspond to the actual networkconfiguration. For more information see the bookTCP/IP Planning and Customization.

DTCCTC059E Error: Possible configuration error inlink statement, retrying

Explanation: A possible configuration error occurredin the LINK statement; the system is retrying the link.The LINK adapter address value might not be valid.



System Programmer Response: Check the LINKstatement on both sides of the transmission. Validvalues for the LINK statement adapter address are 0and 1. For more information about the LINK statement,see the book TCP/IP Planning and Customization.



||||

||

|

|

||

DTCCTC060E Error in initialization, no LCB found

Explanation: An error occurred during initialization.No link control block (LCB) was found. This error canbe caused when the LCB contains an incorrect name ormultiple links to the CTC device are defined in thePROFILE TCPIP file.

System Action: CTC initialization halts. TCPIPcontinues.


System Programmer Response: Check the PROFILETCPIP file and make sure an LCB is specified in theLINK statement correctly. For more information aboutthe LINK statement, see the book TCP/IP Planning andCustomization.

DTCCTC069I CTCA device device: ToCTCA: DeferredSioCC rc on device device

Explanation: A deferred SIO condition code wasreceived.


User or Operator Response: If the condition code is 2or 3, check for hardware problems.


DTCCTC070I CTCA device device: ToCTCA: Sioreturned rc on device device

Explanation: A condition code was received.


User or Operator Response: If the condition code is 2or 3, check for hardware problems.


DTCCTC071E CTCA device device: Diag 98 errorcode code

Explanation: A diagnostic call caused the indicatederror.


User or Operator Response: Check for aprogramming problem.


DTCCTC073I CTCA device device: Stored CSW is:csw

Explanation: This message precedes the display of astored channel status word (CSW).




DTCCTC079E CTCA device device: UnexpectedSIOCC rc from SenseId operation ondevice device

Explanation: The procedure SenseId, which is used byCTC to determine the ID of a device to be initialized,was unsuccessful. The reason is indicated by the SIOCCdisplayed in this message. Initialization of this devicehalts.


User or Operator Response: Check the PROFILETCPIP file of the indicated device for errors. Correct theerrors and restart the device. For more informationabout the PROFILE TCPIP file, see the boo TCP/IPPlanning and Customization.


DTCCTC080I CTCA initializing:<

Explanation: CTCA is starting to initialize.




DTCCTC082E CTCA shutting down: Address:device_address

Explanation: The channel to channel adapter (CTCA)is shutting down the device at the indicated address.The connection to the device is closed.



System Programmer Response: Reinitialize the deviceat the indicated address.

DTCCTC083E CTCA device device: Unexpected CSWfrom SenseId command on device device

Explanation: The procedure SenseId, which is used byCTC to determine the ID of a CTC device, wasunsuccessful due to an unexpected channel status word(CSW) The CSW is displayed following this message.Initialization of the device halts.


User or Operator Response: Check the PROFILETCPIP file of the device being initialized for errors.Correct the errors and restart the device. For moreinformation about the PROFILE TCPIP file, see thebook TCP/IP Planning and Customization.




DTCCTC087I CTCA device device: Sense data fordevice device: sense data

Explanation: Sense information was received for thespecified device as the result of a unit check.



System Programmer Response: See S/360 S/370™

S/390® I/O Interface Channel to Channel Control UnitOEMI for an explanation of the sense information. Ifthe problem persists, check for a hardware problem.

DTCCTC089E CTCA device device: Channel error ondevice device

Explanation: An unexpected channel error wasencountered.




DTCCTC091E CTCA device device: ReceivedDEVICEend interrupt on device device --probable CTCA restart

Explanation: The indicated device was interrupted,which probably means the device was reset.




DTCCTC092E Unit Check on device device

Explanation: A unit check occurred.


User or Operator Response: Check the unit checkcode. Check your hardware if needed. Correct theerrors and restart the device.


DTCCTC093E Unit Exception on device device

Explanation: A unit exception occurred on theindicated device.


User or Operator Response: Check your hardware forerrors. Check that the opposite side is not out of sync.


DTCCTC094E Unknown interrupt on device device

Explanation: The indicated device encountered anunexpected interrupt.




DTCCTC095E Sense ID: value for device device

Explanation: Data is returned from a Sense ID, andany unexpected data is flagged.




DTCDIP006E Diag 98 error locking page: CondCodecode, Return code: rc

Explanation: The lock attempt was unsuccessful. Thismessage displays the condition code and the returncode for this procedure. Ry+1 is the real address of theuser’s page if the lock attempt was successful or areturn code if the locking operation was unsuccessful(indicated by condition code 3). The following tabledescribes the condition and return codes.

Conditioncode

Return Code inRY+1

Meaning

3 1(X‘01’) User is runningvirtual=real

3 2(X‘02’) Invalid virtual address3 3(X‘03’) Page unavailable in

dynamic page area3 4(X‘04’) Page already locked.



System Programmer Response: Respond as indicatedby the return code given in the message.

DTCDIP077I Discarding IDAW pointer pointer: crossespage boundary

Explanation: The procedure AllocIdaw, whichallocates storage for an indirect data address block andlocks its page, obtained storage that could not be usedbecause it crosses a page boundary. The storage ispermanently held, so as not to cause a similar problemin the future, and the storage allocation process isrepeated until a suitable block of storage is obtained.






DTCDIP078I Discarding CCW pointer pointer: crossespage boundary

Explanation: The procedure AllocCcwString, whichallocates storage for a channel program and locks itspage, obtained storage that could not be used becauseit crosses a page boundary. The storage is permanentlyheld, so as not to cause a similar problem in the future,and the storage allocation process is repeated until asuitable block of storage is obtained.




DTCFPM001E Insufficient CMS storage available forFPSM

Explanation: The Fixed Page Storage Manager isunable to allocate a sufficient amount of CMS storageto satisfy a network request or the fpsbs operand of theFIXEDPAGESTORAGEPOOL statement.

By default, the TCP/IP server manages the FPSMstorage pool to utilize up to 90 percent of availableCMS storage within the TCP/IP virtual machine. Eitherthe 90 percent threshold was attained or the limitspecified by the Queued Direct I/O Pool Statement wasreached.

System Action: Processing continues, but IPDatagrams may be lost.

System Programmer Response: Increase the storagesize of the TCP/IP server virtual machine and/ormodify the Queued Direct I/O pool statementappropriately.

DTCFPM004I FPSM is available with number pagesallocated

Explanation: The Fixed Page Storage Manager savailable for use by high speed data transfer functionswithin the stack. The number of pages that arecurrently allocated within the storage pool are returnedin number. The value for number will be the numberspecified either on the fpsb operand of theFIXEDPAGESTORAGEPOOL Statement or zero if thestatement wasn’t specified.

The primary function of the FPSM is to provide a cacheof CP locked pages for fast I/O buffer management tosupport the Queued Direct I/O Hardware Facility.Since the typical QDIO data transfer is faster thentraditional I/O, the active life of a data buffer is shortlived; thereby causing the same buffers to be quicklyreused for the next data transfer. The FPSM is used toreduce the high overhead required to constantly lock orunlock pages within CP storage.



DTCFPM005I FPSM may allocate an additional xpages out of y

Explanation: Specifies the amount of storage (x) whichmay be allocated by the Fixed Page Storage Managerfor caching CP locked pages to be used by the QueuedDirect I/O Hardware Facility. The FPSM will populatethe storage pool with available CMS free storage ″asneeded″ based on network traffic. The page limit forthe storage pool is determined by either the storagesize of the TCP/IP Service Machine and/or theoptional FIXEDPAGESTORAGEPOOL Statement. Thevalue specified by y is the total number of free pageswithin the CMS storage pool.



DTCFPM007E FPSM encountered a Diag 98 errorlocking/unlocking pages: Global RC rc

Explanation: An unexpected global return code wasreceived when the Fixed Page Storage Manager (FPSM)was locking or unlocking pages within CP’s storage viaBlock Diagnose 98 Request (subfunction X'10'). Thefollowing is a table of return codes that may bereturned:

Code Reason / Action

002 Subfunction is not required for this virtualmachine. The virtual machine is either aV=R or V=F machine whose pages arealready fixed within CP storage.

Action

The TCP/IP virtual machine cannot beconfigured as a preferred guest to use theFPSM. Remove OPTION V=R or OPTIONV=F from the TCP/IP virtual machine’ssystem directory entry.

003 Subfunction is not supported when issuedin 24-bit addressing mode.

Action

Contact IBM.004 Subfunction is not supported when issued

from a 370 virtual machine.

Action

The TCP/IP virtual machine can’t beconfigured as a 370 virtual machine to usethe FPSM. Change MACHINE 370 toMACHINE XC in the TCP/IP virtualmachine’s system directory entry.



Code Reason / Action

005 Invalid value specified in the Diagnose 98Multiple Request Block DIAG field.

Action

Contact IBM.006 Invalid value specified in the Diagnose 98

Multiple Request Block FCN field.

Action

Contact IBM.007 Invalid value specified in the Diagnose 98

Multiple Request Block LEGNTH field.

Action

Contact IBM.

System Action: Processing continues, but may berunning degraded.

System Programmer Response: Perform theappropriate action from the above table.

DTCFPM010E Received Diag 98 return code rcprocessing page page

Explanation: An unexpected return code was receivedwhen the Fixed Page Storage Manager (FPSM) waslocking or unlocking a specific page within CP’sstorage via Block Diagnose 98 Request (subfunctionX'10')


System Programmer Response: Contact IBM.

DTCIPI001S Insufficient virtual memory availablefor TCP-IP

Explanation: TCPIP has run out of virtual memory.

System Action: TCPIP halts execution.


System Programmer Response: Configure the TCPIPvirtual machine for more virtual storage.

DTCIPI007E Cannot open a profile file

Explanation: TCPIP could not open its PROFILE file.It first tried to find node_name TCPIP *, then PROFILETCPIP *, but could find neither file. The profile filespecifies TCPIP configuration information. See theTCP/IP Planning and Customization book for moreinformation.

System Action: TCPIP initializes with default valuesand tries to run.

User or Operator Response: Ensure that the PROFILEis properly installed. Reinitialize TCPIP.

DTCIPI010I Diagnose 98 real channel programsupport NOT available

Explanation: The OPTION DIAG98 was not specifiedin TCPIP’s CP directory entry. This condition willrestrict or prevent some TCP/IP processes. The effect ofthis will be most prevalent in the device drivers and isfurther explained through subsequent messages thatmay be issued.


System Programmer Response: None..

DTCIPI011I LCS devices will use virtual channelprograms via SIOF

Explanation: The OPTION DIAG98 was not specifiedin TCPIP’s CP directory entry. This causes the LCSdevice driver to incur additional overhead by forcingCP to perform channel program translation.



DTCIPI028W Not forcing you because you’reconnected

Explanation: The user ID that receives this message islisted in a PROFILE file AUTOLOG statement,indicating it should be autologged. AUTOLOG user IDsthat are logged on when the AUTOLOG is executed arenormally forced before being autologged. However,because this user ID is logged on connected, it is notforced or autologged.

System Action: TCPIP execution continues.


DTCIPI034S Fatal initialization configuration errordetected, terminating processing

Explanation: A configuration error has occurred thathas prevented the TCPIP stack from initializing. Theprevious messages will indicate the nature of the errorthat was encountered.

System Action: TCPIP will halt the initializationprocess and stop the TCPIP stack.

User or Operator Response: Notify the systemprogrammer.

System Programmer Response: Determine the natureof the error and correct it. When the error is corrected,the TCPIP stack can be started



DTCIPI040S IDENTIFY cannot determine localsystem node name; terminating sinceTCP/IP services may not function

Explanation: The IDENTIFY command cannotdetermine the node name of the local system. As aresult, various TCP/IP services will not be able tofunction correctly.

System Action: TCP/IP terminates.

System Programmer Response: Update the SYSTEMNETID file on the CMS S-disk so that the local systemnode name is associated with the CPU identifier(s) ofthe processor where TCP/IP is running. After updatingthe file and resaving the CMS NSS, restart TCP/IP.

DTCIPI041I Diagnose 98 block request support NOTavailable

Explanation: TCP/IP is running on a level of z/VMwhich does not support a Block Diagnose 98 Request(Diagnose 98 subfunction X'10). Support for a BlockDiagnose 98 Request is available in z/VM Version 4Release 3.0 or later. Without support for a BlockDiagnose 98 request, some TCP/IP functions may notbe available.



DTCIPI042E TCP/IP will no longer attempt to restartuser: MaxRestart attempts have beenmade.

Explanation: The user specified in the message texthas been restarted MAXRESTART times. The TCP/IPserver will notify the INFORM list and will stopautologging the user. For more information see theMAXRESTART statement in TCP/IP Planning andCustomization

System Action: TCP/IP processing continues.

System Programmer Response: Determine why theuser is being restarted. If the problem with the user hasbeen resolved and you would like the TCP/IP server toresume monitoring the user, dynamically specify theuser’s PORT statement without the NOAUTOLOGoperand.

DTCIPI053I IgmpHandle: Cannot get envelope topass IGMP to raw client

Explanation: TCPIP attempted to get an envelope topass an IGMP datagram to a raw client, but noenvelopes were available. The IGMP datagram is notpassed to the raw client(s).



System Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.

DTCIPU086I A denial-of-service attack has beendetected

Explanation: A condition has been detected thatindicates a potential denial-of-service attack.

System Action: Processing continues. Packets may bediscarded to prevent system resources from beingdepleted.

User or Operator Response: Issue the NETSTAT DOScommand to determine the specific type of attack andthe IP address from which the attack was potentiallylaunched or, in the case of a Smurf-IC, Smurf-OB,Smurf-RP, or Fraggle attack, the IP address of thevictim of the attack.

DTCIUC003I device type device name: Error in IUCVoperation code, cc: condition_code, iprcode:IP_request_code, pathid: pathid


Explanation: This message indicates that the inter-usercommunication vehicle (IUCV) encountered an errorwhile trying to process the indicated request. For moreinformation about the IUCV codes, see the TCP/IPProgrammer’s Reference.

System Action: TCP/IP continues.

User or Operator Response: Notify the systemsprogrammer.

System Programmer Response: Check the TCPIPconfiguration file to ensure that valid DEVICE andLINK statements exist for the indicated IUCV link. Ifthe statements are valid, make sure that the device isstarted and online. If this is a PVM IUCV connection,ensure that the other side of the connection is enabled.If all of these are in order, consult the operator’smanual for the indicated device to determine thecorrect trouble shooting procedure.

DTCIUC008E IUCV device device: UnpackReads:Incorrect block header nnnn from inputposition nnnn, last block header nnnn -discarding remainder of block

Explanation: TCPIP found an error in the packetwhile attempting to unpack the data received.



System Programmer Response: Check for aprogramming error on the sending side.



||||

||||||

|

||||||

||||||

||||

||

|

|

||

DTCLDS116I Specific device address for LDSFINITIATE is invalid

Explanation: The LDSF (DIAGNOSE X'7C') Initiatefunction was rejected with condition code 3 return code4.

System Action: The incoming Telnet connection isterminated.


System Programmer Response: The logical deviceaddress used by TCPIP on the LDSF initiate functionwas not valid. Ensure the LDEVRANGE value specifiedwith the INTERNALCLIENTPARMS statement containsvalid logical device addresses. Note that currently,z/VM supports a range up to X'FFFF'.

DTCLDS117I Specific device address for LDSFINITIATE is in use

Explanation: The LDSF (DIAGNOSE X'7C') Initiatefunction was rejected with condition code 3 return code5.



System Programmer Response: Determine the causeof the LDSF initiate failure and take appropriate action.See the Diagnose X'7C' section of the z/VM: CPProgramming Services book for more information. Checkto ensure that no other service machines are using thesame device addresses as those assigned to TCPIP.

DTCMON028W Scheduled restart due to reasonbypassed because you restarted yourself

Explanation: The user who receives this message is inthe AUTOLOG list and was scheduled to be restartedfor the indicated reason. However, when the time cameto perform the restart, the virtual machine hadreinitialized itself, making a second restart unnecessary.

System Action: Operation continues.


DTCOCP086I Telnet server: Conn n: The TCP datathat was delivered during commandsimulation was ignored.

Explanation: This message indicates that TCP datawas delivered, and ignored, during commandsimulation. All TCP data is ignored during commandsimulation.



DTCOCP092I Conn n: LU Name LuName LDEVLdevNumber has been dropped becauseTN3270E data string is too long


Explanation: A TN3270E message was found to befragmented and was saved in a temporary buffer untilremaining data could be obtained. However, the lengthof the data obtained from an ensuing packet, combinedwith that from the still unprocessed TN3270E message,exceeded the size of the buffer used for processing suchdata. The buffer size in question is defined by theDATABUFFERPOOLSIZE statement within the TCP/IPserver configuration file. Within this message:

nnn represents a connection IDLuName is the name of the logical device that

represents the clientldevnumberis the hexadecimal number of the Logical

device that represents the client

System Action: The offending client is disconnected.

User or Operator Response: Check the client for a bademulator level.

Source File: CopyBuffers () PASCAL

DTCOSD011E OSD device name: Unexpected SIOCCCondition Code from Write IDX operationon device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction during the OSDdriver initialization sequence.

System Action: The device is shutdown

System Programmer Response: Verify OSA hardwareis operational. If the problem persists, record thedisplayed error status and report it to the IBM SupportCenter.

DTCOSD012E IDX Activate failed on input devicedevice with cause code failure

Explanation: The activation of the OSD input deviceat address was rejected with a failure code.



DTCOSD020E OSD device name: Unexpected SIOCCCondition Code from Read operation ondevice

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction on a Readoperation during the OSD driver initializationsequence.


System Programmer Response: Verify that the OSA



hardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.

DTCOSD021E OSD device name: Unexpected SIOCCCondition Code from Read IDX operationon device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction on a Read IDXoperation during the OSD driver initializationsequence.


System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.

DTCOSD022E IDX Activate failed on output devicedevice with cause code failure

Explanation: The activation of the OSD output deviceat address was rejected with a failure code.



DTCOSD025E OSD Device name: Device device is notavailable.

Explanation: TCP/IP was attempting to acquire theUnit Address for the device and was unable to find thedevice in the I/O configuration.

System Action: The device is shutdown.

System Programmer Response: Ensure that the OSDdevice is attached to the TCPIP virtual machine.

DTCOSD045E OSD Device name: Error getting XAsubchannel id for device device

Explanation: TCPIP could not determine thesubchannel identifier for the indicated OSD device.



v Ensure the indicated device is properly configured inthe z/VM Control Program (CP) and the processorIOCDS.

v Ensure the appropriate device addresses are attachedto the TCPIP virtual machine. Verify the :Attach tagvalues, as specified for this device in the DTCPARMSfile, are correct.


DTCOSD046E OSD Device name: UnexpectedSTSCH CC code for device device

Explanation: Initial Store Subchannel failed withunexpected condition code.



DTCOSD047E OSD Device name: Device device is notQDIO capable.

Explanation: The initialization process has found thatthe OSD device is not configured to an adapter thatsupports the Queued Directed I/O (QDIO) HardwareFacility.


System Programmer Response: Ensure that the OSDdevice is configured to a QDIO capable adapter.

DTCOSD048E OSD Device name: Device device is nota valid device.

Explanation: The initialization process has found thatthe OSD device is not valid. This condition is causedby not having a physical device associated with thesubchannel.


System Programmer Response: Ensure that the OSDdevice is configured to a QDIO capable adapter.

DTCOSD049E OSD Device name: Device device doesnot have any available CHPIDs

Explanation: The initialization process has found thatthe OSD device is not configured with availableCHPIDs (Channel Paths). The device is unusable.


System Programmer Response: Ensure that the OSDdevice is configured with a valid and available CHPIDin the IOCDS.

DTCOSD050E OSD Device name: Unexpected MSCHCC code for device device

Explanation: Initial Modify Subchannel instructionfailed with unexpected condition code. TCPIP wasattempting to enable this OSD device for I/Ooperations.





DTCOSD051E Invalid OSD device group

Explanation: The specified device group from theDEVICE STATEMENT, device_addr,device_addr+1, anddevice_addr+2 does not contain a sequentialEVEN/ODD pair of unit address. An OSD devicegroup requires that there be a sequential EVEN/ODDpair of unit address within the group.


System Programmer Response: Ensure that the OSDdevice group contains a sequential EVEN/ODD unitaddress pairing. This can be achieved by attaching acontiguous range of device address to the TCPIPvirtual machine.

DTCOSD052E OSD Device name: OSD groupdevices device and device are notconfigured to the same QDIO adapter.

Explanation: The specified device group from theDEVICE STATEMENT, device_addr,device_addr+1, anddevice_addr+2 are not all configured to the samephysical QDIO adapter. Each device in the OSD groupmust be configured with the CHPID of the same QDIOadapter.


System Programmer Response: Ensure that the eachdevice in the OSD device group is configured with theCHPID of the same QDIO adapter. This can beachieved by attaching a contiguous range of deviceaddresses on the same adapter to the TCPIP virtualmachine.

DTCOSD053E OSD Device name: Unexpected CSCHCC code for device device

Explanation: Initial Clear Subchannel failed withunexpected condition code. TCPIP was attemptingquiesce this OSD device for future I/O operations.



DTCOSD054E QDIO queue format is not supported

Explanation: The QDIO hardware adapter supports aqueue format that is currently not supported by thisrelease of z/VM TCP/IP.


System Programmer Response: Remove the DEVICEand LINK statement from the TCP/IP configuration filefor this device.

DTCOSD055E The amount of input and or outputqueues supported by this adapter isinsufficient for TCP/IP

Explanation: The QDIO hardware adapter supportsless that one input and or one output queue. z/VMrequires at least this amount to use the device.


System Programmer Response: Configure thehardware adapter to support at least the minimumamount of queues required by TCP/IP.

DTCOSD066E ToOsd: ProcessReadBuffer:Termination failure code failure

Explanation: TCP/IP has received a fatal failure codefrom the adapter during control data exchange.


System Programmer Response: Report the problem tothe IBM Support Center

DTCOSD071E ToOsd: Diagnose 98 error code code

Explanation: An error code was reported by Diagnose98

System Action: The operation will be retried one time.

System Programmer Response: If retry isunsuccessful, determine the cause of the error using theinformation about Diag 98 error codes in the TCP/IPDiagnosis Guide and respond as indicated.

DTCOSD079E OSD device name: Unexpected SIOCCcode from Sense ID operation on device

Explanation: TCPIP was attempting to validate theOSD device but a nonzero condition code in response toa Sense ID operation.


System Programmer Response: Ensure that the OSDdevice is attached to TCPIP. Verify that the OSAExpress adapter is operational. If the problem persists,report it to the IBM Support Center.

DTCOSD080I dev_type Initializing:

Explanation: TCPIP is initializing a network devicedescribed in subsequent messages.

DTCOSD081E Link name specifies invalid networktype net_type. dev_type will not beinitialized

Explanation: A link for the specified device is not asupported link type.

System Action: The device not initialized.



System Programmer Response: Correct the LINKstatement.

DTCOSD082E dev_type shutting down:

Explanation: TCP/IP is terminating the networkdevice described in the subsequent messages.

System Programmer Response: If the device was notterminated explicitly, examine the TCPIP console log todetermine why the device was shutdown. If necessary,take corrective action as described for the messageexplaining the shutdown.

DTCOSD083E OSD device name: Unexpected CSWfrom a Sense ID command on device

Explanation: TCPIP was attempting to validate theOSD device but received unusual status in response to aSense ID operation. The status will be displayed in asubsequent message.


System Programmer Response: Ensure that the OSDdevice is attached to TCPIP. Verify that the OSA isoperational. If the problem persists, report it to the IBMSupport Center.

DTCOSD084E dev_type device name: UnexpectedSense ID data: sense_data on device

Explanation: TCPIP was attempting to validate thenetwork device but received incorrect senseid_data inresponse to a Sense ID operation.


System Programmer Response: Ensure that thenetwork device that is configured in the TCPIPconfiguration file for device name is the correct physicaldevice.

DTCOSD089E Channel error on device

Explanation: TCPIP received a channel error on device

System Action: The operation will be retried 6 times.If the channel error persists the device will beshutdown.

System Programmer Response: Ensure that the OSDhardware is operational. If the problem persists, reportit to the IBM Support Center.

DTCOSD090E OSD device name: Unexpected devicestatus from I/O interrupt on device

Explanation: TCPIP received an unexpected device orchannel status on its I/O request. If the status indicateda Unit Check, then a sense operation will be issued andthe sense data will be displayed.


System Programmer Response: Ensure that the OSDdevice is an OSA Express adapter. Verify that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.

DTCOSD091E OSD device name: ReceivedDEVICEend interrupt on device --probable OSA restart

Explanation: TCPIP received an unsolicited DeviceEnd interrupt on OSD device



DTCOSD092E OSD device name: Unit Check ondevice

Explanation: TCPIP received a Unit Check on device


System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists,capture the displayed sense data then report it to theIBM Support Center.

DTCOSD093E OSD device name: Unit Exception ondevice

Explanation: TCPIP received a Unit Exception ondevice

System Action: TCPIP will retry the operation 5 timesbefore the device driver is shutdown. The setting in theAUTORestart specification determines whether thedevice driver is to be restarted.


DTCOSD094E OSD device name: Unknown Interrupton device

Explanation: TCPIP received an unknown interrupt ondevice

System Action: TCP will retry the operation 5 timesbefore the device driver is shutdown. The setting in theAUTORestart specification determines if the devicedriver is to be restarted.




DTCOSD100I Insufficient Fixed Page Storage Poolstorage

Explanation: The OSD device driver was attemptingto acquire or invoking a function that was attemptingto acquire Fixed Page Storage Pool block(s) and therequest was unsuccessful. This condition is caused bythe storage pool being exhausted of all available blocks(fpsbs).


System Programmer Response: Make more FPSPblocks available by raising the limit fpsb_limit and/orincreasing the virtual machine storage of the TCP/IPvirtual machine.

DTCOSD101I Resetting Event received. Automaticrestart initiated.

Explanation: TCPIP is attempting to restart the OSDdevice after an error was detected that caused thedevice to be shutdown. This action is being initiatedbecause an ESCON Reset Event was detected duringdriver START (initialization) processing.


DTCOSD102I OSD device name: Restarting devicedevice through AUTORESTART

Explanation: TCPIP is attempting to restart the OSDdevice after an error was detected that caused the deviceto be shutdown. This action is being initiated asrequested by the AUTORestart operand on the DEVICEstatement for this device.


System Programmer Response: Examine the TCPIPconsole log to determine the cause of the original error.

DTCOSD104E Primary routing node already defined

Explanation: TCPIP is presented with this return codefrom the OSA Express adapter when attempting to setthe device as the Primary routing node. Only oneprimary routing node may be defined per physicaladapter.


System Programmer Response: This device iscurrently defined as PRIRouter in the TCPIPconfiguration file. Change the OSD DEVICE statementfor this device in the TCPIP configuration file to eitherSECRouter or NONRouter (default) and restart thedevice.

DTCOSD105E Secondary routing node alreadydefined

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to set the deviceas the Secondary routing node. Only one secondaryrouting node may be defined per physical adapter.


System Programmer Response: This device iscurrently defined as SECRouter in the TCPIPconfiguration file. Change the OSD DEVICE statementfor this device in the TCPIP configuration file to eitherPRIRouter or NONRouter (default) and restart thedevice.

DTCOSD106E OSA Multicast address table is full

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to register aMulticast address.

System Action: The address is not registered, TCPIPcontinues.

System Programmer Response: The adapter will notaccept any additional requests until such time whensufficient Multicast addresses have been unregistered.Verify that all applications that are currently connectedto TCPIP are functioning properly.

DTCOSD107E Multicast address is invalid or alreadyregistered

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to register aMulticast address.

System Action: The address is not registered, TCPIPcontinues.

System Programmer Response: Verify that allapplications that are currently connected to TCPIP arefunctioning properly.

DTCOSD108E IP address is invalid or already in useby the adapter

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to add an IPaddress to the adapter’s IP address table. The IPaddress either has already been added to the list or isnot a valid address

System Action: The address is not registered, TCPIPcontinues

System Programmer Response: Verify the HOME listin the TCPIP configuration file.



DTCOSD109E Adapter IP address table is full

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to add an IPaddress to the adapter’s IP address table.

System Action: TCPIP continues

System Programmer Response: Verify that all the IPaddresses that are in the home list of the TCPIPconfiguration file are required. Remove any IPaddresses that are not required. These changes can bemade using the OBEYFILE command.

DTCOSD110E IP address was not found



System Programmer Response: Correct or remove thefailing IP address from the home list in the TCPIPconfiguration file. These changes can be made using theOBEYFILE command.

DTCOSD111E IP address already in use by anotherIP connection



System Programmer Response: Correct or remove thefailing IP address from the home list in the TCPIPconfiguration file. These changes can be made using theOBEYFILE command.

DTCOSD113E ToOsd: Unable to set the requestedToken Ring broadcast mode

Explanation: TCP/IP recieved an error indication fromthe adapter when it attempted to set theLOCALRINGBCAST broadcast mode.



DTCOSD114E ToOsd: Unable to set the requestedToken Ring addressing mode

Explanation: TCP/IP recieved an error indication fromthe adapter when it attempted to set the CANONICALaddressing mode.



DTCOSD199I OSD device name: ToOsd: Receivedunexpected control data from theadapter for device device

Explanation: TCPIP received an unexpected controldata packet from the OSA Express adapter.

System Action: The packet is discarded, TCPIPcontinues processing.

System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.

DTCOSD204E OSD device name: ToOsd: Error statusestablishing a CM-CM connection fordevice device

Explanation: TCPIP received a connection error statusduring its OSD driver initialization sequence.



DTCOSD210E ToOsd: Unexpected status on deviceestablishing CM-CM connection fordevice device_name

Explanation: TCPIP received an unexpected I/Ostatus attempting to establish a CM-CM connectionduring the OSD driver initialization sequence.



DTCOSD211E OSD device name: Unexpected SIOCCCondition Code from ENABLE operationon device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction whenattempting an ENABLE operation during the OSDdriver initialization sequence.





DTCOSD212E OSD device name: Unexpected SIOCCCondition Code from SETUP operation ondevice

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSETUP operation during the OSD driver initializationsequence.



DTCOSD213E ToOsd: Unexpected status on deviceestablishing USER-USER connection fordevice device_name

Explanation: TCPIP received unexpected I/O statusattempting to establish a USER-USER connectionduring the OSD driver initialization sequence.



DTCOSD217E OSD device name: Unexpected SIOCCCondition Code from an ACTIVATEoperation on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting anACTIVATE operation during the OSD driverinitialization sequence.



DTCOSD218E ToOsd: Unexpected status on deviceactivating a USER connection fordevice_name

Explanation: TCPIP received unexpected I/O statusattempting to activate a USER connection during theOSD driver initialization sequence.



DTCOSD221E OSD device name: Unexpected SIOCCCondition Code from a START LANoperation on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSTART LAN operation during the OSD driverinitialization sequence.



DTCOSD222E ToOsd: Unexpected status on devicestarting a lan port for device device_name

Explanation: TCPIP received an unexpected I/Ostatus attempting to start a lan port during the OSDdriver initialization sequence.



DTCOSD223E OSD device name: ToOsd: Receivedreturn code Return Code from a IPAcmdcommand

Explanation: TCPIP receives this return code from theOSA Express adapter when attempting to issue thespecified command.

System Action: Based on the severity of the error, thedevice may or may not be shutdown.

System Programmer Response: An accompanyingmessage may follow this message providing moredetail on the cause of the error condition. If nosubsequent message is presented, then report it to theIBM Support Center.

DTCOSD225E ToOsd: Attempt to allocate queues fordevice_name failed with with Return coderc

Explanation: This message will be displayed if therewas insufficient storage available in the Fixed PageStorage Manager. or an internal error occurred whileestablishing the QDIO queues.


System Programmer Response: Examine the TCPIPconsole to determine if a low FPSB condition exists.Increase the amount of storage available for the FixedPage Storage Manager. Otherwise record the displayedreturn code and report it to the IBM Support Center.



||

DTCOSD226E ToOsd: Attempt to start queues fordevice_name failed with with Return coderc

Explanation: This message will be displayed if therewas insufficient storage available in the Fixed PageStorage Manager or an internal error occurred whileactivating the QDIO queues.


System Programmer Response: Examine the TCPIPconsole to determine if a low FPSB condition exists.Increase the amount of storage available for the FixedPage Storage Manager. Otherwise record the displayedreturn code and report it to the IBM Support Center.

DTCOSD228E OSD device name: Unexpected SIOCCCondition Code from a query IP assistoperation on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aQUERY IP ASSIST operation during the OSD driverinitialization sequence.



DTCOSD230E OSD device name: Unexpected SIOCCCondition Code from a SET IP assistoperation on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET IP assist operation during the OSD driverinitialization sequence.



DTCOSD231E ToOsd: Unable to set assist assist fordevice_name Return code rc

Explanation: TCPIP received an error return codewhile attempting to set an assist during the OSD driverinitialization sequence.

System Action: The device driver may be shutdown ifit is determined that the assist is required.

System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error return code and report it to the IBMSupport Center.

DTCOSD233E OSD device name: Unexpected SIOCCCondition Code from a SET IP operationon device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting a setIP operation during the OSD driver initializationsequence.


System Programmer Response: Verify that the OSDhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.

DTCOSD236E OSD device name: Unexpected SIOCCCondition Code from a SET RTGoperation on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET RTG operation during the OSD driver initializationsequence.

System Action: The device shutdown.


DTCOSD240E OSD device name: Unexpected SIOCCCondition Code from an IPM operation ondevice

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET IPM operation during the OSD driver initializationsequence.



DTCOSD243E OSD device name: Unexpected SIOCCCondition Code attempting to retry aWrite I/O request on device

Explanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting toretry a WRITE operation that previously received anon-critical channel error.





DTCOSD245I Multicast group address MulticastAddress is not registered

Explanation: TCPIP was unable to register thespecified Multicast Address.


System Programmer Response: View the previouslydisplayed messages to determine the actual failure thatmight have prevented the address from beingregistered.

DTCOSD246I Assigned IP address IpAddress

Explanation: A successful request has been made toset the IpAddress in the OSA Express adapter’s IPaddress table.



DTCOSD247I Unassigned IP address IpAddress

Explanation: A successful request has been made toremove the IpAddress from the OSA Express adapter’sIP address table.



DTCOSD248E Error processing IP address IpAddress

Explanation: TCP/IP was unsuccessful in setting theUnicast or Multicast address into the adapter’s IPaddress table.

System Action: If the failing IP address is assigned tothe link for the device being initialized, then the deviceis shut down. In all other cases, TCP/IP continues.

System Programmer Response: Examine the TCP/IPconsole for subsequent messages that further define theactual error condition and recommended response.

DTCOSD254I ToOSD: Token Ring Link name modemode is now set to mode_ attribute.

Explanation: The OSD Token Ring broadcast oraddressing mode has been set in accordance to whatwas specified in the OSD Token Ring Link statement.



DTCOSD305I Waiting for adapter-initiated Start Lan

Explanation: TCP/IP device initialization received aresponse from the device indicating the device is notready. This message can also be seen during an attemptto restart the device in the event of a device failure if

AUTORESTART was specified on the DEVICEstatement.

System Action: TCP/IP waits for the device to send aStart Lan indication.

System Programmer Response: Use a STOP statementin an obey file to stop the device if you wish toterminate the wait.

DTCOSD306I Received adapter-initiated Start Lan

Explanation: TCP/IP received a response from adevice indicating that the device is now ready.

System Action: TCP/IP continues initializationprocessing for the device.


DTCOSD307E MULTICAST not supported fordevice device

Explanation: The device does not support multicast,but the MULTICAST option was either specified ordefaulted on the LINK statement.

System Action: The device is not intialized.

System Programmer Response: Correct the LINKstatement to specify the UNICAST keyword on theHiperSockets LINK statement.

DTCOSD309W Received adapter-initiated Stop Lan

Explanation: TCP/IP received a response from thedevice indicating that the device is not ready. This canoccur when the device is unplugged, for example, orwhen a CP UNCOUPLE command is issued todisconnect a virtual network adapter from a VM LANsegment.

System Action: TCP/IP continues processing, but thedevice is not functional.

System Programmer Response: Reconnect the device,or issue the CP COUPLE command for a virtualnetwork adapter.

DTCOSD310E Missing required port name

Explanation: TCP/IP device initialization did not findthe port name that is required on a DEVICE statementof type OSD or HIPERS.

System Action: TCP/IP continues processing, but thedevice is not functional.

System Programmer Response: Correct the DEVICEstatement in the TCP/IP configuration file to specify aport name.



|

|||

|||

|||

|

||||

||

||

|||

|

||

||

|

||

|||

|

|||

|

||||||

||

|||

|

|||

||

|||

DTCOSD311E Error in initialization, no LCB found

Explanation: An error occurred during initialization.No link control block (LCB) was found. This error canoccur when there is an error in the DEVICE or LINKstatements defined in the PROFILE TCPIP file.

System Action: Device initialization halts. TCPIPcontinues.


System Programmer Response: Check the serverconsole log for errors specifying the DEVICE or LINKstatement, such as ″Invalid OSD device parameter″.Check the PROFILE TCPIP file and make sure theDEVICE and LINK statements are coded correctly. Formore information, see TCP/IP Planning andCustomization.

DTCOTC038E Telnet server: Conn n: UnrecoverableConnectExit error detected.

Explanation: This message indicates that anunrecoverable ConnectExit error has occurred. Thismessage will be followed by another message thatdescribes the error.



System Programmer Response: The action requireddepends on the next message that describes the error.

DTCOTC039E Telnet server: Conn n: ConnectExitreturned an unsupported return code, Rc=returncode

Explanation: This message indicates that theConnectExit returned an unsupported return code.

System Action: The session is terminated.


System Programmer Response: Update theConnectExit to always return a valid return code.

DTCOTC040E Telnet server: Conn n: ConnectExitrequested command simulation for anon-transparent mode connection.

Explanation: This message indicates that theConnectExit returned a return code requestingcommand simulation for a non-transparent modeconnection. Command simulation is not supported fornon-transparent mode connections.



System Programmer Response: Update theConnectExit to never request command simulation for anon-transparent mode connection.

DTCOTC041E Telnet server: Conn n: Unrecoverablecommand simulation error has occurred.

Explanation: This message indicates that anunrecoverable command simulation error occurred.This message is followed by another message that willdescribe the error.



System Programmer Response: The action requireddepends on the next message that describes the error.

DTCOTC042E Telnet server: Conn n: Skeleton useridissued a non-write CCW after thesimulated command was sent to CP.

Explanation: This message indicates that a CPskeleton user id issued a non-write CCW after thesimulated command was sent to CP.




DTCOTC043E Telnet server: Conn n: Skeleton useridI/O data was received from CP in a splitbuffer chain.

Explanation: This message indicates CP skeletonuserid I/O data was received from CP in a split bufferchain.




DTCOTC050I ConnectExit is [disabled|enabled] forTN3270E sessions.

Explanation: Indicates whether theTN3270ENOSCEXIT option has been activated either asa parameter of the INTERNALCLIENTPARMSstatement in the configuration file or via the OBEYFILEcommand. Used exclusively with telnet printersessions, the TN3270ENOSCEXIT option will disablethe TN3270 session connection exit if it has beenloaded.

User or Operator Response: Remove this parameter ifyou wish to enable the session connection exit forTN3270E sessions. Or use OBEYFILE command todynamically remove it from your TCP/IP configurationso as to re-enable session connection exits.



|

||||

||

|

|||||||

DTCPAR123I Several variations of this message exist

Explanation: This message indicates that an error wasdetected during TCP/IP initialization. The message isself explanatory.


User or Operator Response: Correct the problem inthe TCP/IP server configuration file and restart theTCP/IP server.

System Programmer Response: Assist the operator asrequired.

DTCPAR129I BSDROUTINGPARMS omitted or inerror; using default routing for all links

Explanation: Either no BSDROUTINGPARMSstatement was encountered in the configuration file orthe statement was found but a specification was inerror, causing the statement to be ignored. In eithercase, the subnet masks for all links are set based on theclass of the network they are connected to.


User or Operator Response: Ensure that routing willbe performed correctly using default subnet masks.

DTCPC3002I PCCA3 device name: Started sense ondevice device. SIOCC code

Explanation: TCPIP issued a SENSE command to thedevice as the result of a Unit Check. The code indicatesthe condition code from the System Input/Output(SIO)message. If the SIO condition code is zero, the deviceshould return sense data to TCPIP indicating the causeof the Unit Check. TCPIP prints the sense data in asubsequent message. After the sense data has beenreturned, the device is shut down.


User or Operator Response: If the SIO condition codeis zero, use the sense data in the subsequent messageand the operator’s manual for the device to determinethe troubleshooting procedure. If the SIO conditioncode is not zero, this can indicate a problem accessingthe device.


DTCPC3003I PCCA3 device name: Cannot getenvelope string

Explanation: TCPIP attempted to get an envelope toreceive the data but no envelopes were available.TCPIP discards the packet.



System Programmer Response: Increase the envelopepool size. See the book TCP/IP Planning andCustomization for more information on increasing thepoolsize.

DTCPC3041I PCCA3 device name: PackWrites flushingEnvelopeQueue. Device status: status

Explanation: TCPIP is attempting to pack data for awrite operation, but the device is either not yetinitialized or is shutting down. The outgoing packetsare discarded. If the device is in the process of beinginitialized, it should become available to TCPIP once itsinitialization is complete. If the device is in the processof being shut down, it will become unavailable toTCPIP once its shutdown is complete.




DTCPC3044I PCCA3 device name: FindLinkNumberfails for NetType type Adapternumbernumber

Explanation: TCPIP cannot identify the link associatedwith an incoming packet. The NetType andAdapterNumber from the PCCA header of theincoming packet and those configured for this devicedo not match. This can indicate one of the following:v A configuration error.v The link has not been started.v A problem with the device.

Valid NetType values are:

Value Description0 The PCCA control function1 Ethernet2 Token-Ring7 FDDI


User or Operator Response: Check the configurationto make sure that the NetType (corresponding to thethird keyword parameter on the LINK statement) andAdapterNumber (corresponding to the link_number onthe LINK statement) are properly specified. Make surethe link has been started. If the configuration appearsto be correct, see the appropriate operator’s manual forthe device to determine the troubleshooting procedure.See the book TCP/IP Planning and Customization formore information on LINK statements.




DTCPC3045E PCCA3 device dev_name: Error gettingXA subchan id for dev_addr ordev_addr+1







DTCPC3046I No link found for count consecutivepackets and no packet received fordefined links - check link configuration

Explanation: Packets are being received on the deviceidentified in the message preceding this one but theyare for a link number that is not included in the LCSconfiguration.


User or Operator Response: Ensure that the linknumbers in the LINK statements for the LCS device arecorrect. If no problem can be identified and the errorpersists, contact IBM software support.

DTCPC3053E PCCA3 device name: ToPcca3: Incorrectblock header nnnn from input positionnnnn, last block header nnnn -discarding remainder of block

Explanation: TCPIP encountered an incorrect blockheader on the indicated device. The link on which theerror occurred is unknown. TCPIP drops the block.


User or Operator Response: If this error occursfrequently, it can indicate a problem with the device.See the appropriate operator’s manual for the device.


DTCPC3066E PCCA3 device name: Unknown nettype from PCCA: type

Explanation: The NetType field in the PCCA header ofan incoming packet is not valid. TCPIP discards thepacket.

Valid NetType values are:

Value Description0 The PCCA control function1 Ethernet2 Token-Ring7 FDDI


User or Operator Response: See the appropriateoperator’s manual for the device to determine thetroubleshooting procedure.


DTCPC3069I PCCA3 device name: ToPcca3: DeferredSioCC rc on device device

Explanation: The SIO or SSCH to the device containeda deferred condition code. If the value for rc is 0,TCPIP continues with the operation on the device asnormal. If rc is not 0, and the operation is to the outputaddress, TCPIP purges the output envelope queue. If rcis not 0, and the operation is to the input address, thenTCPIP retries the read operation after 30 seconds.


User or Operator Response: See the operationsmanual for the system to determine the troubleshootingprocedure.


DTCPC3070I PCCA3 device name: ToPcca3: Sioreturned rc on device device

Explanation: TCPIP has issued a SIO or SSCH to thedevice. The return code indicated in the messageshould be 0. Possible values for the return code are:

Value Description0 SIO completed successfully.1 CSW stored.2 Device busy.3 Device error

If rc is not 0, other messages follow containingadditional information.


User or Operator Response: If rc is not 0, use thesubsequent messages to determine the troubleshootingprocedure.



||||


DTCPC3071E PCCA3 devicename: Diag 98 error codeerrorcode

Explanation: The Diag 98 routine generated theindicated error code while performing a diagnosticcheck on the PCCA device.



System Programmer Response: Determine the causeof the error using the information about Diag 98 errorcodes in the TCP/IP Diagnosis Guide, and respond asindicated.

DTCPC3073I PCCA3 device name: Stored CSW is: csw

Explanation: TCPIP issued a SIO or SSCH to thedevice and an error occurred. The Channel Status Word(CSW) from the I/O operation is indicated in themessage. If the error occurred on the output address ofthe PCCA, TCPIP purges the output envelope queue. Ifthe error occurred on the input address, TCPIP retriesthe read operation after 30 seconds.


User or Operator Response: See the Principles ofOperation Manual for the system to determine thetroubleshooting procedure.


DTCPC3079E PCCA3 device name: UnexpectedSIOCC code from Senseld operation ondevice device

Explanation: The indicated device returned anunexpected condition code. TCPIP halts deviceinitialization; the device is no longer available to TCPIP.


User or Operator Response: See the operator’s guidefor the device to determine the troubleshootingprocedure.


DTCPC3080I PCCA3 initializing:

Explanation: TCPIP is initializing the Lan ChannelStation (LCS).




DTCPC3081E Link name specifies invalid networktype networkname. PCCA will not beinitialized

Explanation: The networkname specified on a LINKstatement for this device in the PROFILE TCPIP filewas not valid. The device is not initialized.

Valid values on the LINK statement are:v 802.3v ETHERNETv ETHERor802.3v FDDIv IBMTR


User or Operator Response: Correct the LINKstatement. See the book TCP/IP Planning andCustomization for information on specifying the networkname in the LINK statement.


DTCPC3082E PCCA3 shutting down:

Explanation: The indicated Lan Channel Station (LCS)is shutting down. TCPIP will not use this device.



System Programmer Response: Check the owner’smanual for the indicated device to determine thecorrect troubleshooting procedure.

DTCPC3083E PCCA3 device name: Unexpected CSWfrom SenseId command on device device

Explanation: TCPIP received an unexpected channelstatus word (CSW) from the indicated device. Thedevice shuts down.


User or Operator Response: See the operator’smanual for the device to determine the troubleshootingprocedure.


DTCPC3087I PCCA3 device name: Sense data fordevice device: data

Explanation: TCPIP received the indicated sense datafor this device, as a result of a unit check. The deviceshuts down.


User or Operator Response: See the operator’smanual for this device to determine the troubleshootingprocedure.




DTCPC3089E PCCA3 device name: Channel error ondevice device

Explanation: TCPIP issued a SIO or SSCH to thedevice and the Subchannel Status field of the ChannelStatus Word (CSW) was not zero. If the error occurredon the output address of the PCCA, TCPIP purges theoutput envelope queue. If the error occurred on theinput address, TCPIP retries the read operation after 30seconds. The CSW for the device is printed in themessages following this one.


User or Operator Response: See the Principles OfOperation Manual for the system to determine thetroubleshooting procedure.


DTCPC3091E PCCA3 device name: ReceivedDEVICEend interrupt on device device --probable PCCA restart

Explanation: TCPIP received a DeviceEnd interruptfrom the device. ChannelEnd was not included withDeviceEnd in the status. This might indicate that thedevice was reset. If the DeviceEnd interrupt occurredon the output address of the PCCA, TCPIP checks itsoutput envelope queue for the device and sends anypackets that are ready. If the DeviceEnd interruptoccurred on the input address, TCPIP issues a readoperation on the input address of the PCCA after 30seconds.



System Programmer Response: If the device has beenrestarted, the read operation will be successful and nointervention is necessary. Otherwise, determine thecause of the shutdown and respond as indicated by theoperator’s manual for the indicated device.

DTCPC3092E PCCA3 device name: Unit Check ondevice device

Explanation: TCPIP received a unit check unit statusfor the indicated device. The device shuts down.


User or Operator Response: See the operator’smanual for the device to determine the troubleshootingprocedure.


DTCPC3093E PCCA3 device name: Unit Exception ondevice device

Explanation: TCPIP received a unit exception. Unitstatus was received for the indicated device. TCPIPpurges the output queue, if appropriate, and continuesusing the device.


User or Operator Response: If this error occursfrequently, it can indicate a problem with the device.See the operator’s guide for this device to determinethe troubleshooting procedure.


DTCPC3094E PCCA3 device name: Unknowninterrupt on device device

Explanation: TCPIP received an unrecognizedinterrupt from the indicated device. TCPIP continuesusing the device.


User or Operator Response: If this error occursfrequently, it can indicate a problem with the device.See the operator’s guide for this device to determinethe troubleshooting procedure.


DTCPDO036I ProcessIpOptions: unknown option:option source: address

Explanation: While processing an IP datagram, TCPIPdetected an IP option it does not recognize.



System Programmer Response: This messageindicates a host is using an IP option that is notsupported by the VM TCP/IP stack. You may want toinvestigate why the option is being used. If no otherproblems are noted, the message can be safely ignored.

DTCPDO077I FindRoute found route_type for addresson interface link_name

Explanation: The FindRoute routine found a route forlink_name in the route table that was a match foraddress. The route is of type route_type, where route_typeis one of the following:

route_type Description

DefaultRTE Default Routing Table Entry

HostRTE Host Routing Table Entry

NetworkRTE Network Routing Table Entry



SubnetFound Subnetted Routing Table Entry

SupernetFound Supernet Routing Table Entry

This message is displayed when IPDOWN tracing isactive.

System Programmer Response: If this result is not asexpected review the HOME and GATEWAY statementsin the PROFILE TCPIP to see the routing information.Also see the NETSTAT GATE command in the TCP/IPUser’s Guide.

DTCPDO078I FindRoute did not find a route foraddress

Explanation: The FindRoute routine did not find aRouting Table entry for address.

System Programmer Response: View the HOME andGATEWAY statements in the PROFILE TCPIP to verifythe routing information. Also see the NETSTAT GATEcommand in the TCP/IP User’s Guide.

DTCPDO079I TreeVisit found route_type for addresson interface link_name

Explanation: The TreeVisit routine found a subnetroute on link_name in the route table that was a matchfor address. The route is of type route_type, whereroute_type is one of the following:

route_typeDescription

SubnetRTESubnetted Routing Table Entry

SupernetRTESupernetted Routing Table Entry

This message is displayed when IPDOWN tracing isactive.

System Programmer Response: View the HOME andGATEWAY statements in the PROFILE TCPIP to verifythe routing information. Also see the NETSTAT GATEcommand in the TCP/IP User’s Guide.

DTCPDO080I FindRoute looking for route for:address

Explanation: The FindRoute routine has been called tolocate a route to address.

DTCPDO081E SOURCEVIPA parameter is notsupported by the current RouteD server

Explanation: An unsupported configuration has beendetected. The RouteD server in use does not supportthe SOURCEVIPA parameter specified in theASSORTEDPARMS statement. This message is onlyissued for the first five detections of this

incompatibility. The counter is reset when the RouteDserver is recycled.

System Programmer Response: If the SOURCEVIPAoption coded in the ASSORTEDPARMS statement isnot in error, the RouteD server code must be replaced,so that TCP/IP Function Level 320 (or later) software isin use; SOURCEVIPA is not supported by prior levels.If the SOURCEVIPA option was coded in error, use theOBEYFILE command to correct the ASSORTEDPARMSstatement and restart the RouteD server.

DTCPDO082I Shutting down RouteD server name

Explanation: The RouteD server has been shut downdue to a configuration error; this problem is indicatedby message DTCPDO081E.

System Programmer Response: Restart the RouteDserver after making necessary changes.

DTCPDO084I Cannot get envelope to loopbackmulticast datagram

Explanation: TCPIP attempted to get an envelope toloopback a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent to theinternal loopback.




DTCPDO105I The known networks:

Explanation: The list of routes known by TCPIP isdisplayed after this message.



DTCPDO107I MPRoute server active; equal-costmultipath support enabled

Explanation: The EQUALCOSTMULTIPATHparameter was not specified in the ASSORTEDPARMSstatement, but MPROUTE does exploit equal-costmultipath support, so that support has been enabled.



DTCPDO108I RouteD server active; equal-costmultipath support disabled

Explanation: The ROUTED server does not supportthe EQUALCOSTMULTIPATH parameter specified in



|

||

|

|

||

||||

|

|

||

||

the ASSORTEDPARMS statement, so the support hasbeen disabled.



DTCPDO089I SendIGMP: Cannot get envelope tosend IGMP report

Explanation: The routine SendIGMP is unable to getan envelope to send out an IGMP membership report.The IGMP membership is not sent.




DTCPKT048E PCCA3 device devicename: Error nn ingetting home hardware address forlinkname number linknumber

Explanation: The indicated LCS device did not returnthe adapter address in response to the Get Lan Statscontrol command. This message usually results due toone of the following conditions:v an adapter configured in TCPIP but not in the LCS.v an incorrect relative link/adapter number specified

in PROFILE TCPIP.v a subchannel address pair mismatch.v a hardware error (faulty adapter).


User or Operator Response: Review the LCSconfiguration for the indicated device, as well as theassociated DEVICE and LINK statements in the TCP/IPconfiguration file (PROFILE TCPIP). Verify thecorresponding information is correct. If thesedefinitions are correct and in agreement, verify that allhardware connections for the device are correct.

DTCPKT053W WARNING PCCA report homehardware address MAC address for linedevice-name

Explanation: The indicated device reported a MACaddress of 000000000000.


User or Operator Response: In the case of an 8322,000000000000 is valid. However, with some otherdevice(s), a configuration problem in the PROFILETCPIP file may have occurred. For example, a device ispossibly configured with an incorrect link_number in theLINK statement. See the TCP/IP Planning andCustomization book and the hardware informationmanual for configuration specifications on theparticular device.

DTCPKT089E Device devicename : LAN task net typetype adapter number number hasterminated

Explanation: The indicated device has supplied acontrol packet which indicates that a running LAN taskhas stopped. A timer is set within TCP/IP to attempt arestart of this task in 5 seconds.


User or Operator Response: Stop and restart thedevice. Verify that the hardware is functioning correctly.

DTCPKT100E Device devicename : Error nn in settingmulticast address for linkname numberlinknumber

Explanation: The indicated device was unable to setthe multicast address with the Set IP Multicastcommand. The device will not receive datagramsdestined for this multicast address.


User or Operator Response: Review the LCSconfiguration for the indicated device, as well as theassociated DEVICE and LINK statements in the TCP/IPconfiguration file (PROFILE TCPIP). Verify thecorresponding information is correct. If thesedefinitions are correct and in agreement, verify that allhardware connections for the device are correct, andverify that the device is multicast capable.

DTCPKT101E Device devicename : Error nn indeleting multicast address for linknamenumber linknumber

Explanation: The indicated device was unable todelete the multicast address with the Delete IPMulticast command.


User or Operator Response: Review the LCSconfiguration for the indicated device, as well as theassociated DEVICE and LINK statements in the TCP/IPconfiguration file (PROFILE TCPIP). Verify thecorresponding information is correct. If thesedefinitions are correct and in agreement, verify that allhardware connections for the device are correct, andverify that the device is multicast capable.

DTCPKT102I Received QIP assist packet

Explanation: A response was received for the QueryIP Assist command.






||

|

|

|||

||||

|

||

DTCPKT103I Received set ipm packet

Explanation: A response was received for the Set IPMulticast command.




DTCPKT104I Received delete ipm packet

Explanation: A response was received for the DeleteIP Multicast command.




DTCPKT105E Device devicename: No control packetreceived in response to Start LanCommand

Explanation: The indicated device did not return acontrol packet in response to the Start Lan controlcommand.

System Action: The device is shutdown, althoughTCPIP continues.

User or Operator Response: See the operator’smanual for the device to determine the troubleshootingprocedure..


DTCPRS003E Line line: Device already started

Explanation: The device_name specified in a STARTstatement has already been started.

System Action: TCPIP ignores the START statement;execution continues.


DTCPRS004E Line line: Unable to accept furtherclient names

Explanation: TCPIP could not allocate another ClientControl Block (CCB) while processing a PORTstatement. You can expand the CCB pool by modifyingthe CCBPOOLSIZE statement in the configuration file.

System Action: TCPIP ignores the PORT statement.

User or Operator Response: Specify a larger CCB poolwith the CCBPOOLSIZE statement.

DTCPRS006E Line line: Unable to accept further portreservations

Explanation: TCPIP could not allocate another SocketControl Block (SCB) while processing a PORTstatement. You can expand the SCB pool by modifyingthe SCBPOOLSIZE statement in the configuration file.


User or Operator Response: Reduce the number ofPORT statements or increase the SCB pool size in theSCBPOOLSIZE statement.

DTCPRS008E Line line: Unable to accept furtherhome addresses

Explanation: TCPIP cannot add an entry to its homeaddress list. This error occurred while processing aHOME statement in the configuration file.

System Action: TCPIP ignores the HOME statement.

User or Operator Response: Reduce the number ofhome address list entries in the HOME statement.

DTCPRS010I Line line: No such userid: UserID

Explanation: You specified an invalid user_id in aPORT statement.


User or Operator Response: Correct the PORTstatement to specify a valid user_id field.

DTCPRS011E Line line: Unexpected end of input

Explanation: TCPIP unexpectedly encountered the endof its configuration file.


User or Operator Response: A statement within theconfiguration file was not complete. Check the syntaxof configuration file statements and identify thestatements that are incomplete. Correct the errors.

DTCPRS012E Line line: Invalid hex character indevice address

Explanation: TCPIP encountered a non-hexadecimalcharacter in a device address specification. Validcharacters are: 0 through 9, and A through F.

System Action: TCPIP ignores this statement.

User or Operator Response: Correct the entry.

DTCPRS014E Line line: Invalid driver process inGATEWAY command

Explanation: The link_name specified in a GATEWAYstatement is not valid. Links specified in a GATEWAYstatement must be defined in a LINK statement.





DTCPRS016E Line line: Gateway not directlyaccessible in GATEWAY command

Explanation: The gateway specified as the first_hop ina GATEWAY statement within the PROFILE file is notdirectly accessible. The first_hop must specify a gatewayon the same network as this node.

System Action: TCPIP ignores the GATEWAYstatement.

User or Operator Response: Correct the GATEWAYstatement to specify an accessible first_hop address. Forassistance if necessary, see the network administrator.

DTCPRS017E Line line: Routing loop in GATEWAYcommand

Explanation: TCPIP has encountered a routing loop ina GATEWAY statement.

System Action: The GATEWAY statement is ignored.TCPIP ignores the GATEWAY statement.

User or Operator Response: Correct the GATEWAYstatement.

DTCPRS018E Line line: Overflow of routing table inGATEWAY command

Explanation: TCPIP has experienced a routing tableoverflow while processing a GATEWAY statement.


User or Operator Response: Reduce the number ofGATEWAY statements in the configuration file orincrease the size of the IP routing table in theIPROUTEPOOLSIZE statement.

DTCPRS019E Line line: Unknown network forgateway in GATEWAY command

Explanation: TCPIP did not recognize the networkspecified in a GATEWAY statement.



DTCPRS020E Line line: Subnet mask conflicts withprev instance of net # in GATEWAYcommand

Explanation: The subnet_mask specified in aGATEWAY statement conflicts with a previouslyspecified network number.

System Action: TCPIP ignores this GATEWAYstatement.

User or Operator Response: Correct the GATEWAYstatement

DTCPRS021E Line line: Zero internet addressspecified in TRANSLATE

Explanation: You specified zero as the internet_addressin a TRANSLATE statement.

System Action: TCPIP ignores the TRANSLATEstatement.

User or Operator Response: Correct theinternet_address specification in this TRANSLATEstatement.

DTCPRS022E Line line: No more room inTRANSLATE table

Explanation: The TCPIP translate table is full; youcannot insert any additional entries.


User or Operator Response: Reduce the number ofTRANSLATE statements in the configuration file. If thisis not practical, use theADDRESSTRANSLATIONPOOLSIZE statement toincrease the translation table pool size.

DTCPRS023E Line line: Invalid numbufs field forport port

Explanation: You specified an invalidnumber_of_buffers in a DEVICE statement.

System Action: TCPIP ignores the DEVICE statement.

User or Operator Response: Correct the DEVICEstatement.

DTCPRS024E Line line: Invalid threshold field forport port

Explanation: The threshold specification in a DEVICEstatement is not valid.



DTCPRS025E Line line: Invalid MyMsgGap field forport port

Explanation: You specified an invalid MyMsgGap in aDEVICE statement.


User or Operator Response: Correct the MyMsgGapfield in this statement



DTCPRS026E Line line: Invalid YrMsgGap field forport port

Explanation: You specified an invalid YrMsgGap in aDEVICE statement.



DTCPRS027E Line line: Missing name field

Explanation: You did not specify a device_name in aDEVICE statement.



DTCPRS028E Line line: Missing type field

Explanation: You did not specify a device type in aDEVICE statement.



DTCPRS029E Line line: Invalid type field

Explanation: You specified an invalid device type in aDEVICE statement. Valid types are:v LCS v DDN1822v PVMIUCV v IUCVv SNAIUCV v X25NPSIv ELANS v ILANSv X25ICA v HCHv SHALU62 v HIPPIv CLAW v CTC



DTCPRS030E Line line: Missing device address field

Explanation: You did not specify a device address inthe DEVICE statement. This field is required fordevices of type: LCS, DDN1822, and HCH.



DTCPRS031E Line line: Remote PVM nodeid missing

Explanation: You did not specify a rmt_pvm_node in aDEVICE statement. This field is required for devices oftype PVMIUCV.



DTCPRS032E Line line: SNALINK program namemissing

Explanation: You did not specify the program nameSNALINK, in a DEVICE statement. This field isrequired for devices of type SNAIUCV.



DTCPRS033E Line line: Remote TCPIP vmid missing

Explanation: You did not specify a rmt_tcpip_vmid in aDEVICE statement. This field is required for devices oftype PVMIUCV.



DTCPRS034E Line line: Remote LU name missing

Explanation: You did not specify a remote_lu_name in aDEVICE statement. This field is required for devices oftype SNAIUCV.



DTCPRS035E Line line: PVM VM id missing

Explanation: You did not specify a local_pvm_vmid in aDEVICE statement. This field is required for devices oftype PVMIUCV.



DTCPRS036E Line line: SNALINK VM id missing

Explanation: You did not specify the snalink_vmid in aDEVICE statement. This field is required for devices oftype SNAIUCV.



DTCPRS037E Line line: Local PVM nodeid missing

Explanation: You did not specify a local_pvm_node in aDEVICE. statement. This field is required for devices oftype PVMIUCV.





DTCPRS038E Line line: Missing base device addressfield

Explanation: You did not specify a base_device_addr ina DEVICE statement. This field is required for devicesof type: ELANS, ILANS and X25ICA.



DTCPRS039E Line line: Invalid WaitTime field

Explanation: You specified an invalid wait_time in aDEVICE statement.


User or Operator Response: Correct the DEVICEstatement

DTCPRS042E Line line: LINK statement: missingname field

Explanation: You did not specify a link_name in aLINK statement.

User or Operator Response: Correct the LINKstatement.

System Action: TCPIP ignores the LINK statement.

DTCPRS043E Line line: LINK statement: Missingtype field

Explanation: You did not specify a link type in aLINK statement.



DTCPRS044E Line line: LINK statement: Invalid typefield

Explanation: You specified an invalid link type in aLINK statement. Valid types are:

PRONET IUCVETHERNET HCHETHEROR802.3 HIPPI802.3 IPIBMTR OFFLOADLINK1FDDI OFFLOADAPIBROADDDN1822 OFFLOADAPIPPX25ICA OFFLOADOTHER



DTCPRS045E Line line: LINK statement: Invalid netnumber field

Explanation: You specified an invalid link_number in aLINK statement.



DTCPRS046E Line line: LINK statement: Missingdevice name field

Explanation: You did not specify a device_name in aLINK statement.



DTCPRS047E Line line: LINK statement: Duplicatelink name

Explanation: The link_name you specified in a LINKstatement has already been used. You must specifyanother, unique name.



DTCPRS048E Line line: LINK statement: Specifieddevice name not found

Explanation: The device_name specified in a LINKstatement does not match the device_name field in anyDEVICE statements. Each device referenced in a LINKstatement must be defined in a DEVICE statement.


User or Operator Response: Correct the configurationfile to ensure every LINK statement has acorresponding DEVICE statement with a matchingdevice_name field.

DTCPRS049E Line line: LINK statement: Too manylinks on specified device

Explanation: The device specified in a LINK statementcannot accept additional links.


User or Operator Response: Remove one of the LINKstatements for the device specified in this LINKstatement.



DTCPRS050E Line line: Unknown link name inGATEWAY cmd

Explanation: The link_name specified in a GATEWAYstatement was not defined by a LINK statement.


User or Operator Response: Ensure the link_name isspelled correctly. If it is, specify a corresponding LINKstatement in the configuration file.

DTCPRS051E Line line: Invalid packet size inGATEWAY command: value

Explanation: You specified an invalid max_packet_sizein a GATEWAY statement. The size must be a positiveinteger no larger than EnvLargeDatagramSize.



DTCPRS052E Line line: Subnet mask not compatiblewith network address

Explanation: A GATEWAY statement contains asubnet_mask specification that is incompatible with thenetwork specified.



DTCPRS053E Line line: Subnet value not compatiblewith subnet mask

Explanation: A GATEWAY statement contains asubnet_value specification that is incompatible with thesubnet_mask specified.



DTCPRS054E Line line: Pool size omitted

Explanation: You did not specify a number_of_xxxs ina xxxPOOLSIZE statement.

System Action: TCPIP ignores the statement.

User or Operator Response: Correct the statement.

DTCPRS062E Line line: Unexpected Boolean: word

Explanation: TCPIP expected a command rather thanthe referenced Boolean expression.

System Action: TCPIP ignores this configuration filestatement.

User or Operator Response: Correct the syntax of thisconfiguration file statement.

DTCPRS063E Line line: Pool size specifications mustappear before any other commands.Command ignored

Explanation: A pool size specification wasencountered after other configuration file commands.Pool size specifications must appear in theconfiguration file before any other commands. Thispool size specification has been ignored.

System Action: TCPIP ignores the pool sizespecification.

User or Operator Response: Move the pool sizespecification to the top of the configuration file.

DTCPRS064E Line line: Internal client name notvalid in AUTOLOG command

Explanation: The user_id specified in an AUTOLOGstatement represents an internal client of TCPIP. UserIDs of internal clients are not valid in AUTOLOGstatements, because the internal clients’ virtual machinehas already been started.

System Action: TCPIP ignores the AUTOLOGstatement.

User or Operator Response: Correct the AUTOLOGstatement within the PROFILE file or the OBEYFILE inwhich this statement occurs.

DTCPRS065E Line line: Missing userid inCLIENTPERFOPTIONS command

Explanation: You did not specify a user ID in aCLIENTPERFOPTIONS statement.

System Action: TCPIP ignores theCLIENTPERFOPTIONS statement.

User or Operator Response: Correct theCLIENTPERFOPTIONS statement.

DTCPRS066E Line line: Internal client name notvalid in CLIENTPERFOPTIONScommand

Explanation: The user ID specification in aCLIENTPERFOPTIONS represents an internal client ofTCPIP. Internal clients cannot be specified in aCLIENTPERFOPTIONS statement.

System Action: TCPIP ignores the



CLIENTPERFOPTIONS statement.

User or Operator Response: Correct theCLIENTPERFOPTIONS statement in the PROFILEconfiguration file.

DTCPRS067E Line line: CLIENTPERFOPTIONSstring too long, ignored

Explanation: The command string specified in aCLIENTPERFOPTIONS statement was too long.

System Action: TCPIP ignores theCLIENTPERFOPTIONS statement; execution continues.

User or Operator Response: Correct theCLIENTPERFOPTIONS statement on the commandline, if specified there, or in the PROFILE configurationfile, then restart TCPIP.

DTCPRS068E Line line: Per cent to drop omitted

Explanation: The percentage specification was invalidor missing in a DROP statement.

System Action: TCPIP ignores the DROP statement;packets are not dropped.

User or Operator Response: Correct the DROPstatement.

DTCPRS069I Line line: DROP has been disabled atcompilation

Explanation: The DROP statement was encountered inthe configuration file, but the DROP function wasdisabled when TCP/IP was compiled. To re-enable thisfunction, TCP/IP must be recompiled with theappropriate DEBUG options. The DROP function is adebugging tool that drops random packets to testrecovery from lost packets.

System Action: TCPIP ignores the DROP statement;execution continues.


System Programmer Response: If you want to enablethe DROP function and you have the appropriatesource code release, recompile TCPIP with theappropriate debugging flags (DEBUGtrace) set.

DTCPRS072E Line line: Invalid file identifier in FILEcommand

Explanation: You specified an invalid file name in aFILE statement.

System Action: TCPIP ignores the FILE statement.

User or Operator Response: Correct the FILEstatement in the PROFILE configuration file.

DTCPRS073E Line line: Missing fields in HOMEcommand

Explanation: You did not specify one or moreparameters in a HOME statement.


User or Operator Response: Correct the HOMEstatement.

DTCPRS074E Line line: Unknown link name inHOME cmd

Explanation: The link_name specified in a HOMEstatement was not defined by a LINK statement.


User or Operator Response: Ensure the link_name isspelled correctly. If it is, specify a corresponding LINKstatement in the configuration file.

DTCPRS075E Line line: Internal client name notvalid in INFORM, OBEY, or RESTRICTcommand

Explanation: The user_id specified in an INFORM,OBEY, or RESTRICT statement represents an internalclient. Internal clients are not valid parameters for thesestatements.

System Action: The statement is ignored.

User or Operator Response: Correct the appropriatestatement in the PROFILE configuration file.

DTCPRS076E Line line: Invalid port number inPORT command: port

Explanation: You specified an out-of-rangeport_number in a PORT statement.


User or Operator Response: Correct the PORTstatement in the PROFILE configuration file.

DTCPRS077E Line line: The PORT command ismissing a protocol

Explanation: You did not specify a protocolspecification in a PORT statement.


User or Operator Response: Correct the PORTstatement.

DTCPRS078E Line line: Unknown protocol for PORTcommand

Explanation: You specified an unknown protocol in aPORT statement. Valid protocols are UDP and TCP.





DTCPRS079E Line line: The PORT command ismissing a userid

Explanation: You did not specify a user_id in a PORTstatement.


User or Operator Response: Correct the PORTstatement

DTCPRS080E Line line: No integer specified forSEED command

Explanation: You did not specify arandom_number_seed in a SEED statement.

System Action: TCPIP ignores the SEED statementand uses a seed based on the low-order bits of ahardware clock.

User or Operator Response: Correct the SEEDstatement.

DTCPRS081E Line line: Missing device name

Explanation: You did not specify a device_name in aSTART statement.

System Action: TCPIP ignores the START statement.

User or Operator Response: Correct the STARTstatement.

DTCPRS082E Line line: Device not found

Explanation: The device_name specified in a START orSTOP statement of the PROFILE configuration file orOBEYFILE has not been defined in a DEVICEstatement in the PROFILE. Each device_name specifiedin a START or STOP statement must have acorresponding DEVICE statement in the PROFILE.

System Action: TCPIP ignores the START or STOPstatement; execution continues.

User or Operator Response: Add the appropriateDEVICE statement to the PROFILE file. See TCP/IPPlanning and Customization for more information aboutthe DEVICE statement.

DTCPRS084E Line line: Error starting device. SeeTCPIP console for details

Explanation: An error occurred starting a device. Thedevice error message is on the TCPIP console.

System Action: The device could not be started;execution continues.

User or Operator Response: Note the error message.

See the appropriate device documentation fortroubleshooting procedures.

System Programmer Response: Assist the user indetermining and correcting the cause of the devicefailure.

DTCPRS086E Line line: Device not started

Explanation: The device_name specified in a STOPcommand within the OBEYFILE has not been started.

System Action: TCPIP ignores the STOP command;execution continues.

User or Operator Response: Determine if the deviceshould be started. If so, see the TCP/IP Planning andCustomization book for more information about theSTART statement.

DTCPRS087E Line line: Missing X25 address

Explanation: You did not specify a net_address in aTRANSLATE statement, with address type X25ICA.


User or Operator Response: Correct the TRANSLATEstatement.

DTCPRS088E Line line: Missing pronet address

Explanation: You did not specify a net_address in aTRANSLATE statement, with address type PRONET.



DTCPRS089E Line line: Invalid pronet address

Explanation: The net_address specified in aTRANSLATE statement, with address type PRONET, isan invalid Pronet address.



DTCPRS090E Line line: Missing Ethernet, 802.3 orToken Ring address

Explanation: You did not specify a net_address in aTRANSLATE statement, with address type ETHERNET,IBMTR, FDDI, or HCH.





DTCPRS091E Line line: Invalid network inTRANSLATE command: network

Explanation: You specified an invalid network in aTRANSLATE statement. Valid networks are:v X25ICAv PRONETv ETHERNETv IBMTRv FDDIv HCHv HIPPI


User or Operator Response: Correct the networkspecification in the TRANSLATE statement.

DTCPRS092E Line line: Unimplemented command:command

Explanation: The referenced command is not animplemented configuration file statement.

System Action: TCPIP ignores this command.

User or Operator Response: Remove the command onthis line of the configuration file.

DTCPRS093E Line line: Unexpected number: number

Explanation: TCPIP does not expect the referencednumber at this point in the configuration file.

System Action: TCPIP ignores the statement on thisline of the configuration file.

User or Operator Response: Correct the syntax of thisline in the configuration file.

DTCPRS094E Line line: Unknown command:command

Explanation: The referenced command is not a knownconfiguration file statement.

System Action: TCPIP ignores this statement.

User or Operator Response: Remove or correct thisstatement to specify a valid configuration filestatement.

DTCPRS115E Line line: Invalid entry following LUkeyword

Explanation: You specified an invalid entry after thekeyword LU on this line of the configuration file.

System Action: TCPIP ignores this configuration fileline.

User or Operator Response: Correct the appropriateline in the PROFILE configuration file.

DTCPRS116E Line line: Invalid format of UseridUserID

Explanation: The user ID specified on this line of theconfiguration file is in an invalid format.


User or Operator Response: Correct the user IDspecification on this line of the PROFILE configurationfile.

DTCPRS117E Line line: Invalid format of LU namename

Explanation: You specified an invalid LU name onthis line of the configuration file.

System Action: TCPIP ignores this line of theconfiguration file.

User or Operator Response: Correct the LU namespecified on the indicated line of the PROFILEconfiguration file.

DTCPRS120E Line line: Invalid entry typeencountered in VTAM parameterprocessing

Explanation: TCPIP encountered an invalid entry typebetween BeginVTAM and EndVTAM statements in theconfiguration file.

System Action: TCPIP ignores the statement.

User or Operator Response: Correct the entry in thePROFILE configuration file.

DTCPRS121E Line line: Invalid entry followingdevice type type

Explanation: You specified an invalid entry followingthis device type on this line of the configuration file.

System Action: TCPIP ignores this line of thePROFILE file.

User or Operator Response: Correct the appropriateline of the PROFILE configuration file.

DTCPRS122E Line line: Invalid format of ModeTable Name name

Explanation: This mode table name entry in theconfiguration file is too long.

System Action: TCPIP ignores the mode table nameentry.

User or Operator Response: Correct the mode tablename entry in the PROFILE configuration file



DTCPRS123E Line line: Unrecognized keyword wordprocessing VTAM parameters.

Explanation: You referenced an invalid keyword as aVTAM parameter specification.


User or Operator Response: Correct the VTAMparameter specification.

DTCPRS124E Line line: Invalid entry followingDEFAULTAPPL keyword

Explanation: The entry following a DEFAULTAPPLkeyword is not valid.

System Action: TCPIP ignores the DEFAULTAPPLstatement.

User or Operator Response: Correct theDEFAULTAPPL entry in the PROFILE configurationfile.

DTCPRS125E Line line: Invalid format of DefaultApplication Name name

Explanation: A DEFAULTAPPL statement in thePROFILE configuration file specified a defaultapplication name in an invalid format.

System Action: TCPIP ignores the DEFAULTAPPLstatement.

User or Operator Response: Correct theDEFAULTAPPL statement in the PROFILEconfiguration file.

DTCPRS127E Line line: Invalid format of TelnetApplication Name name

Explanation: The specified TELNET application nameencountered in the PROFILE configuration file is in aninvalid format.

System Action: TCPIP ignores this configuration fileentry.

User or Operator Response: Correct the PROFILEconfiguration file entry.

DTCPRS131E CLAW host name missing

Explanation: The CLAW host name is missing fromthe DEVICE statement.


System Programmer Response: Update the PROFILETCPIP file to add the CLAW host name to the DEVICEstatement and either restart TCP/IP or use OBEYFILEto process the new configuration file.

System Action: The CLAW device is not defined toTCPIP.

DTCPRS132E CLAW adapter name missing

Explanation: The CLAW adapter name is missingfrom the DEVICE statement.


System Programmer Response: Update the PROFILETCPIP file to add the CLAW adapter name to theDEVICE statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.


DTCPRS133E CLAW may only be used with realchannel programs

Explanation: CLAW requires the use of theDIAGNOSE X'98' interface and does not run unless theTCPIP virtual machine us authorized to use theinterface.


System Programmer Response: Add an OPTIONDIAG98 statement to the VM directory for the TCPIPuser ID. To restart TCPIP with the new capability, logthe TCPIP user ID off and then on again.


DTCPRS134E Invalid CLAW read buffer count

Explanation: The CLAW read buffer count is notvalid. It must be a positive decimal number.


System Programmer Response: Update the PROFILETCPIP file to correct the CLAW read buffer count onthe DEVICE statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.


DTCPRS135E Invalid CLAW write buffer count

Explanation: The CLAW write buffer count is notvalid. It must be a positive decimal number.


System Programmer Response: Update the PROFILETCPIP file to correct the CLAW write buffer count onthe DEVICE statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.




DTCPRS136E Invalid CLAW read buffer size

Explanation: The CLAW read buffer size is not valid.It must be one of the following positive decimalnumbers: 1024, 2048, 3172, or 4096.


System Programmer Response: Update the PROFILETCPIP file to correct the CLAW read buffer size on theDEVICE statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.


DTCPRS137E Invalid CLAW write buffer size

Explanation: The CLAW write buffer size is not valid.It must be one of the following positive decimalnumbers: 1024, 2048, 3172, or 4096.


System Programmer Response: Update the PROFILETCPIP file to correct the CLAW write buffer size on theDEVICE statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.


DTCPRS138E Packet size in GATEWAY commandgateway_stmt is larger than CLAW writebuffer size.

Explanation: The packet size on the GATEWAYstatement is smaller than the CLAW write buffer size.This controls the IP datagram size. IP datagrams maynot be split between CLAW buffers, so the packet sizein the GATEWAY statement may not be larger than thewrite buffer size.


System Programmer Response: Update the PROFILETCPIP file to correct the maximum packet size on theGATEWAY statement and either restart TCP/IP or useOBEYFILE to process the new configuration file.

System Action: The specific routing is ignored.

DTCPRS145E Invalid IP address (address) in TN3270Estatement

Explanation: The address specified in a TN3270Eprinter definition in the TCP/IP configuration file is nota valid IP address.


User or Operator Response: Correct the TN3270Estatement in error.

DTCPRS146E Invalid LU name (LUname) in TN3270Estatement

Explanation: The LUname specified in a TN3270Eprinter definition in the TCP/IP configuration file is notan identifier of eight or fewer characters in length.



DTCPRS147E Invalid user identifier (userid) inTN3270E statement

Explanation: The userid specified in a TN3270E printerdefinition in the TCP/IP configuration file is not anidentifier of eight or fewer characters in length.



DTCPRS148I Line nnnn:LARGEENVELOPEPOOLSIZE andENVELOPEPOOLSIZE size valuesconflict.

Explanation: TCP/IP has detected an envelope poolconfiguration error. The size specifications for theLARGEENVELOPEPOOLSIZE andENVELOPEPOOLSIZE statements are not acceptable.The size specified for large envelopes must equal orexceed that specified for regular-sized envelopes.

System Action: TCP/IP initialization stops.


System Programmer Response: Review the TCP/IPserver configuration file and ensure appropriate valuesare specified for the LARGEENVELOPEPOOLSIZE andENVELOPEPOOLSIZE statements, then restart theTCP/IP server. If necessary, consult TCP/IP Planningand Customization for more information about valuesthat can be specified for these statements.

DTCPRS150I Line nnnn: DATABUFFERPOOLSIZEbuffer size is not valid.

Explanation: The data buffer size specified for theDATABUFFERPOOLSIZE statement is not valid. Adefault data buffer size of 8192 bytes is used in place ofthe value found to be in error.

System Action: TCP/IP initialization continues.


System Programmer Response: Specify a valid buffersize for the DATABUFFERPOOLSIZE statement, thenrestart the TCP/IP stack. Acceptable buffer size valuesare listed in TCP/IP Planning and Customization.



DTCPRS151I Line nnnn:SMALLDATABUFFERPOOLSIZE buffersize is not valid.

Explanation: The data buffer size specified for theSMALLDATABUFFERPOOLSIZE statement is not valid.A default data buffer size of 2048 bytes is used in placeof the value found to be in error.



System Programmer Response: Specify a valid buffersize for the SMALLDATABUFFERPOOLSIZE statement,then restart the TCP/IP stack. Acceptable buffer sizevalues are listed in TCP/IP Planning and Customization.

DTCPRS152I Line nnnn:LARGEENVELOPEPOOLSIZE size isnot valid.

Explanation: The envelope size specified for theLARGEENVELOPEPOOLSIZE statement is notacceptable. A default envelope datagram size of 8192 isused in place of the value found to be in error.



System Programmer Response: Specify a validenvelope size for the LARGEENVELOPEPOOLSIZEstatement, then restart the TCP/IP stack. Acceptableenvelope size values are listed in TCP/IP Planning andCustomization.

DTCPRS153I Line nnnn: ENVELOPEPOOLSIZE sizeis not valid.

Explanation: The envelope size specified for theENVELOPEPOOLSIZE statement is not acceptable. Adefault envelope datagram size of 2048 is used in placeof the value found to be in error.



System Programmer Response: Specify a validenvelope size for the ENVELOPEPOOLSIZE statement,then restart the TCP/IP stack. Acceptable envelope sizevalues are listed in TCP/IP Planning and Customization.

DTCPRS160E Missing NSAP address

Explanation: A 40-hexadecimal-digit physical ATMnetwork address is required on a TRANSLATEstatement.

System Action: The TRANSLATE statement isignored.

System Programmer Response: Supply the missingaddress.

DTCPRS173E MaxRestart value is missing or is notvalid

Explanation: The value for the MAXRESTARTstatement was either missing or was not a numberbetwen 0 and 2,147,483,647.

System Action: The MAXRESTART statement isignored.

System Programmer Response: Correct the value inthe MAXRESTART statement.

DTCPRS200E LINK statement: Device and link typesare not consistent

Explanation: The device types specified for a DEVICEstatement and its corresponding LINK statement do notmatch. The device type for one of these statements isspecified as VIRTUAL, while the other is not.

System Programmer Response: Correct the DEVICEand LINK statements in PROFILE TCPIP and makesure both device types are specified as VIRTUAL.

DTCPRS201E Virtual link not valid for GATEWAY

Explanation: A virtual link was encountered whileprocessing a GATEWAY statement. This is notsupported.

System Programmer Response: Correct or remove theGATEWAY statement in PROFILE TCPIP.

DTCPRS202E Virtual device not valid for START orSTOP

Explanation: The START or STOP command wasissued for a VIRTUAL device. This is not supported.

System Programmer Response: Remove the START orSTOP statement for the virtual device from PROFILETCPIP or your obey file.

DTCPRS203E VARSUBNETTING parameter requiresASSORTEDPARMS to be placed beforethe GATEWAY andBSDROUTINGPARMS statements

Explanation: The VARSUBNETTING parameter wasfound in the ASSORTEDPARMS statement. Thus, thevariable-length subnet masks coded in both theGATEWAY and BSDROUTINGPARMS statements maynot have been processed correctly.

System Action: The subnet masks in the GATEWAYstatement may be flagged with errors while those inthe BSDROUTINGPARMS statement are changed tofixed length subnet masks.

System Programmer Response: Move theASSORTEDPARMS statement in PROFILE TCPIP beforeboth the GATEWAY and BSDROUTINGPARMSstatements. This will ensure correct processing of



||

|||

||

||

variable length subnet masks.

DTCPRS204E Subnet masks changed due to conflictsin the BSDROUTINGPARMS statement

Explanation: The variable length subnet masksspecified in the BSDROUTINGPARMS statement arenot supported. These are forced to fixed length subnetmasks so that subnet masks of the same length aredefined for each network.

System Programmer Response: Specify theVARSUBNETTING parameter in theASSORTEDPARMS statement to enable variablesubnetting support. Otherwise, correct the subnetmasks in the BSDROUTINGPARMS statement.

DTCPRS205I Subnet mask subnet_mask is not valid; 0is used

Explanation: While processing the GATEWAYDEFAULTNET statement, a nonzero subnet mask wasencountered.

System Action: A subnet mask of 0 is used and thesubnet value is ignored.

System Programmer Response: Correct theGATEWAY DEFAULTNET statement. Use 0 for thesubnet mask and do not specify a subnet value.

DTCPRS206W Link PrimaryLink moved to the top ofthe HOME list; consider making it thefirst HOME entry

Explanation: A PRIMARYINTERFACE statement wasfound in PROFILE TCPIP. While this statement issupported and correct, its use is no longer preferred. Itcan be removed if the entry for the link_name is placedfirst in the HOME list.

System Action: The link_name is placed at the top ofthe HOME list.

System Programmer Response: Suppress this messageby placing the link_name first in the HOME list.

DTCPRS207E Missing PVC name in ATMPVCstatement

Explanation: An ATMPVC statement does not includethe name of the PVC.

System Action: The ATMPVC statement is ignored.

System Programmer Response: Supply the missingone- to eight-character PVC name. It must correspondto the PVC name defined in the OSA configuration.

DTCPRS208E Duplicate PVC name name

Explanation: An ATMPVC statement specifies thename of a PVC that is already defined.

System Action: The duplicate ATMPVC statement isignored.

System Programmer Response: Correct the PVC nameor remove the duplicate PVC definition.

DTCPRS209E Missing link name

Explanation: An ATMPVC statement does not includethe name of the link with which the PVC is associated.

System Action: The ATMPVC statement is ignored.

System Programmer Response: Supply the missingone- to 16-character ATM link name.

DTCPRS210E Line line: EQUALCOSTMULTIPATHparameter requires ASSORTEDPARMSto be placed before the GATEWAYstatement

Explanation: The EQUALCOSTMULTIPATHparameter was found in the ASSORTEDPARMSstatement. Thus, the routes coded in the GATEWAYstatements may not have been been processed correctly.

System Action: Some of the GATEWAY statementsmay have been ignored.

System Programmer Response: Move theASSORTEDPARMS statement in the PROFILE TCPIPbefore the GATEWAY statement. This will ensurecorrect processing of routes.

DTCPRS212E ATM ARP server name missing

Explanation: An ATMARPSERVER statement does notinclude the name of the ATMARP server.

System Action: The ATMARPSERVER statement isignored.

System Programmer Response: Supply the missingone- to 16-character ATMARP server name.

DTCPRS213E Duplicate ATM ARP server name name

Explanation: An ATMARPSERVER statement specifiesthe name of an AMTARP server that is already defined.


System Programmer Response: Correct the ATMARPserver name or remove the duplicate server definition.



||||

||||

||

||||

DTCPRS214E ATMLIS name missing

Explanation: An ATMARPSERVER statement does notinclude the name of the logical IP subnet (defined byan ATMLIS statement) with which the ATMARP serveris associated.


System Programmer Response: Supply the missingone- to 16-character logical IP subnet name.

DTCPRS216E Missing ATM ARP server connectionspecification

Explanation: An ATMARPSERVER statement does notspecify the connection to the ATMARP server.


System Programmer Response: Supply the missinginformation, in the form of either the word SVCfollowed by an IP address and the word NSAPfollowed by the ATMARP server ATM physical address(for an SVC connection) or the word PVC followed bya PVC name (for a PVC connection).

DTCPRS217E Missing PVC name

Explanation: An ATMARPSERVER statement does notinclude the name of the PVC that connects to it.


System Programmer Response: Supply the one- toeight-character name of the PVC connection to theATMARP server.

DTCPRS219E Missing ATM ARP server IP address

Explanation: An ATMARPSERVER statement does notinclude the IP address of the ATMARP server.


System Programmer Response: Supply the IP addressof the ATMARP server.

DTCPRS220E Missing ’NSAP’

Explanation: An ATMARPSERVER statement does notinclude the word NSAP after the IP address for an SVCconnection.


System Programmer Response: Supply the wordNSAP followed by the ATM physical address of theATMARP server.

DTCPRS221E Missing NSAP address

Explanation: An ATMARPSERVER statement does notinclude the ATM physical address of the ATMARPserver.


System Programmer Response: Supply the ATMphysical address of the ATMARP server.

DTCPRS222E Invalid NSAP address

Explanation: An ATMARPSERVER statement specifiesan invalid ATM physical address for the ATMARPserver.


System Programmer Response: Supply the valid ATMphysical address of the ATMARP server.

DTCPRS223E Invalid ATM ARP server connectionspecification

Explanation: An ATMARPSERVER statement specifiesan unrecognized form of ATMARP server connection.


System Programmer Response: Supply the connectionspecification in the form of either the word SVCfollowed by an IP address and the word NSAPfollowed by the ATMARP server ATM physical address(for an SVC connection) or the word PVC followed bya PVC name (for a PVC connection).

DTCPRS224E Missing ATMLIS name

Explanation: An ATMLIS statement does not includethe name of the logical IP subnet.

System Action: The ATMLIS statement is ignored.

System Programmer Response: Supply the one- to16-character name of the logical IP subnet.

DTCPRS225E Duplicate ATMLIS name

Explanation: An ATMLIS statement specifies the nameof a logical IP subnet that is already defined.


System Programmer Response: Correct the logical IPsubnet name or remove the duplicate logical IP subnetdefinition.



DTCPRS226E Missing or invalid subnet value

Explanation: An ATMLIS statement contains a subnetvalue that is not valid.


System Programmer Response: Supply thedotted-decimal subnet value.

DTCPRS227E Missing or invalid subnet mask

Explanation: An ATMLIS statement contains a subnetmask that is not valid.


System Programmer Response: Supply thedotted-decimal subnet mask.

DTCPRS228E Subnet mask incompatible withnetwork address

Explanation: An ATMLIS statement specifies a subnetmask that is incompatible with the network address.


System Programmer Response: Correct the subnetmask so that it includes all of the bits in the networkclass mask. For a Class A network, use a mask of255.0.0.0 or greater. For a Class B network, use a maskof 255.255.0.0 or greater. For a Class C network, use amask of 255.255.255.0 or greater.

DTCPRS229E Subnet value incompatible withsubnet mask

Explanation: An ATMLIS statement specifies a subnetmask and a subnet value that are incompatible.


System Programmer Response: Either change thesubnet mask so that it includes all of the bits in thesubnet value or change the subnet value so that it onlyuses bits in the subnet mask.

DTCPRS230E PORTNAME keyword missing

Explanation: A DEVICE statement for an ATM devicedoes not include the word PORTNAME.

System Action: The DEVICE statement is ignored.

System Programmer Response: Supply the wordPORTNAME followed by the OSA port name.

DTCPRS231E Missing ATM port name

Explanation: A DEVICE statement for an ATM devicedoes not specify the OSA port name.


System Programmer Response: Supply the OSA port

name. It must correspond to the port name defined inthe OSA configuration.

DTCPRS232E Invalid ATM device parameter

Explanation: A DEVICE statement for an ATM devicespecifies an unrecognized parameter.


System Programmer Response: Correct or remove theparameter in error.

DTCPRS236E Unknown ATMLIS name lis referencedby ATMARP server server

Explanation: An ATMAPRSERVER statement forATMARP server server refers to an undefined logical IPsubnet named lis.

System Action: The ATMARP server is unusable.

System Programmer Response: Correct theATMARPSERVER or ATMLIS statement in error orsupply the missing ATMLIS statement to define thelogical IP subnet.

DTCPRS237E Unknown ATMPVC name pvcreferenced by ATMARP server server

Explanation: An ATMARPSERVER statement forATMARP server server refers to an undefined PVCnamed pvc.

System Action: The ATMARP server is unusable.

System Programmer Response: Correct theATMARPSERVER or ATMPVC statement in error orsupply the missing ATMPVC statement to define thePVC.

DTCPRS238E PVC pvc refers to unknown link namelink

Explanation: An ATMPVC statement for the PVCnamed pvc refers to an undefined LINK named link.

System Action: The PVC is unusable.

System Programmer Response: Correct the ATMPVCor LINK statement in error or supply the missing LINKstatement to define the link.

DTCPRS239E PVC pvc refers to link link, which isnot an ATM link

Explanation: An ATMPVC statement for the PVCnamed pvc refers to a LINK statement named link.However, the LINK does not define an ATM link.

System Action: The PVC is unusable.

System Programmer Response: Correct the ATMPVCor LINK statement in error.



DTCPRS240E Platform services deficient for OSDdevice

Explanation: These services include the use of theDIAGNOSE X’98’ interface and CP enhancements thatexist in z/VM 3.1.0 and above.

System Action: The OSD device is not defined toTCP/IP.

System Programmer Response: Add an OPTIONDIAG98 statement to the VM directory for the TCPIPuserid. Verify the release of VM that this TCPIP moduleis running on, is z/VM 3.1.0 or later.

DTCPRS241E Invalid OSD device parameter

Explanation: A DEVICE statement for an OSD devicespecifies an unrecognized parameter.

System Action: The device statement is ignored.

System Programmer Response: Correct or remove theparameter in error.

DTCPRS242E FPSBs fpsbs exceeds the specifiedFPSB_LIMIT fpsb_limit

Explanation: The FPSB_LIMIT specifies the maximumFPSBs that may be allocated for this virtual machine.This value must be at least equal to or greater than thevalue specified for FPSBs.

System Action: The FIXEDPAGESTORAGEPOOLstatement is ignored.

System Programmer Response: Increase theFBSB_LIMIT or decrease the FBSBs on theFIXEDPAGESTORAGEPOOL statement in the TCPIPconfiguration file.

DTCPRS245E Missing OSD port name

Explanation: A DEVICE statement for an OSD devicedoes not specify the OSD port name.


System Programmer Response: Supply the OSD portname. If this adapter is being shared, then use thename that is currently defined for the adapter.

DTCPRS246E PORTNAME keyword missing forOSD DEVICE statement

Explanation: A DEVICE statement for an OSD devicedid not include the word PORTNAME.


System Programmer Response: Supply the wordPORTNAME followed by the OSD port name.

DTCPRS247E Platform services deficient for OSDdevice support

Explanation: Either the OPTION DIAG98 was notspecified in TCPIP’s CP directory entry or TCP/IP isrunning on a level of z/VM which does not support aBlock Diagnose 98 Request (Diagnose 98 subfunctionX'10).

System Action: OSD Device initialization isterminated.

System Programmer Response: Ensure that theOPTION DIAG98 is set in the TCPIP CP directory entryand that the level of z/VM is either Version 4, Release3, Modification 0 or later.

DTCPRS248E Certificate label not provided afterSECURE keyword on PORT statement

Explanation: The label associated with the certificateto be used for secure connections on this port must bespecified.

System Action: The PORT statement is ignored.

User or Operator Response: Supply the certificatelabel after the SECURE keyword.


DTCPRS249E SECURE keyword not valid with UDPprotocol

Explanation: SSL can be used only with TCP protocol.




DTCPRS250E SECURE keyword must be specifiedwith port number ’*’

Explanation: A port number of ’*’ indicates a secureuser ID, and the SECURE keyword must be used.


User or Operator Response: Provide the SECUREkeyword and a certificate label on the PORT statement.

System Programmer Response: NONE.

DTCPRS255E Missing HIPERS port name

Explanation: A DEVICE statement for a HIPERSdevice does not specify the HIPERS port name


System Programmer Response: Supply the HIPERSport name. If this adapter is being shared, then use thename that is currently defined for the adapter.



DTCPRS256E PORTNAME keyword missing forHIPERS DEVICE statement

Explanation: A DEVICE statement for a HIPERSdevice did not include the word PORTNAME.


System Programmer Response: Supply the wordPORTNAME followed by the HIPERS port name.

DTCPRS257E Invalid PORTNAME specification indevice DEVICE statement

Explanation: The PORTNAME parameter is invalid.For example, the port_name specified may be more thaneight characters in length.


System Programmer Response: Correct the DEVICEstatement to specify a valid port_name.

DTCPRS258E Duplicate route ignored

Explanation: This route is a duplicate of one that hasalready been added to the routing tables.

System Action: The GATEWAY statement is ignored.

User or Operator Response: Remove the Gatewaystatement.

DTCPRS259E Equal-cost route has an incorrect MTUsize; route ignored

Explanation: The MTU size must be the same acrossall multipath routes to one destination.


User or Operator Response: Correct the MTU size inthis GATEWAY statement.

DTCPRS260E Maximum number of equal-cost routesis exceeded; route ignored

Explanation: The maximum number of equal-costroutes allowed to one destination is four. Additionalpaths to this destination are ignored.


User or Operator Response: Remove the Gatewaystatement.

DTCPRS291I Telnet server: TN3270E disabled

Explanation: TN3270E support is disabled because theNOTN3270E option was specified on theINTERNALCLIENTPARMS statement in the TCP/IPconfiguration file.

System Action: TN3270E sessions are not allowed.


DTCPUP039I XeroxAll failed for foreign internetaddress xx.xx.xx.xx. Setting TextLengthto nn

Explanation: The procedure XeroxAll, which copiestext from a segment into a storage buffer, was unable tocopy this text because the buffer lacks sufficient space.TCPIP attempts to compensate for this problem bysetting the segment length for future segments to theindicated value.


User or Operator Response: If this message isrepetitively issued, notify the system programmer ofthe error.

System Programmer Response: Notify theadministrator of the offending host that a windowingsize mismatch is repeatedly occurring for connectionsestablished with this z/VM host.

DTCPUP091I Unexpected EOF received from Offloadwhile inSendingOnly/ConnectionClosing State

Explanation: An Offload EOF notification has beenreceived while in SendingOnly, ClosingConnection stateand an Offload EOF was not pending.



System Programmer Response: If no other relatedOffload error messages occur in conjunction with thisthen it was probably a timing related problem and canbe ignored. Otherwise, refer to the associated messagesto determine what caused the problem.

DTCPUP098I Invalid length of nn for unrecognizedTCP option option from IP addressxx.xx.xx.xx; connection reset

Explanation: The option is unsupported, and theoption length is either less than the minimum legalvalue of two, or is too large to fit in the remainingoption area.

System Action: The connection is reset.

User or Operator Response: Contact your systemprogrammer.

System Programmer Response: Use diagnostics forthe source node to determine if it is generating theillegal option length. If not, use network diagnostics todetermine where the illegal option length is beingcreated.



||

|||

|

||

|

||

|

||

||

||

|

||

||

|||

|

||

DTCPUP099I Unrecognized TCP option option fromIP address xx.xx.xx.xx is ignored

Explanation: An unsupported TCP option has beenreceived.

System Action: The unsupported option is ignored;processing continues with the next option.



DTCQIO006E Insufficient FPSM storage is availableto allocate buffers for the QDIOHardware Facility

Explanation: TCP/IP was unable to allocate storagefrom the Fixed Page Storage Manager for buffers to beused for transferring data to or from the Queued DirectI/O Hardware Facility.

System Action: Processing continues, but IPDatagrams may be lost.

System Programmer Response: Increase the amountof storage in the Fixed Page Storage Manager.

DTCQIO007I Device nnnn is enabled/disabled forQDIO data transfers

Explanation: The specified device number eitherstarted or stopped using the Queued Direct I/OHardward Facility.



DTCQUE074I SnapPushPullQueue Don’t know whatqueue - should not be here

Explanation: One of TCPIP’s internal data structureshas been corrupted. The program variable FreeAcbPoolhas been overwritten with an invalid value.


User or Operator Response: Tell the systemprogrammer.

System Programmer Response: Determine if anyconditions exist that could cause corruption of virtualstorage. If any exist, correct them. Otherwise, contactthe IBM Support Center.

DTCRRQ019I RawSendTheDatagram: Cannot getenvelope to send multicast datagram

Explanation: TCPIP attempted to get an envelope tosend out a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent.



programmer about the error.


DTCSHU003E No clients are active, so I’ll shutdown at once

Explanation: TCPIP is shutting down. Because TCPIPhas no active clients, it shuts down immediately.

System Action: TCPIP shuts down.


DTCSHU004E count active client{s}, with countconnection{s} in use.

Explanation: TCPIP is shutting down. TCPIP has theindicated number of active clients, with the indicatednumber of open connections. These clients are notifiedof the shutdown and given time to close theirconnections.

System Action: TCPIP notifies its clients, gives themtime to close their open connections, closes anyconnections clients left open, and shuts down.


DTCSHU010E I will delay shutting down for countseconds, so that RSTs and shutdownnotifications may be delivered. If youwish to shutdown immediately, withoutwarning, type #CP EXT again.

Explanation: To enable clients to shut down cleanly,TCPIP notifies its clients and delays the indicated timeto allow the notifications to be received and actedupon. To avoid the delay, type #CP EXT. This action canprevent clients from receiving the proper notification.

System Action: If the operator does not typeanything, TCPIP pauses to allow its clients to handlethe notification of TCPIP shutdown. Then TCPIP shutsdown. If the operator types #CP EXT, TCPIPimmediately shuts down. Because clients may not havetime to prepare for shutdown, the results areunpredictable.

User or Operator Response: Generally, you shouldwait until the shutdown process completes. However, ifyou wish to shut down immediately, without waitingfor TCPIP client users to recover cleanly, you can type#CP EXT.

DTCSNM001W Netman Request : Adapter notassociated with subchannel, deviceaddress

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that was



received from the 3172 indicated that theadapter/subchannel pair specified in the request is notvalid.

This message could also appear if the device that theNETMAN request was sent to was an 8232 instead of a3172.

System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.


System Programmer Response: If the command wassent to an 8232, check the device definitions in thePROFILE TCPIP file and remove the NETMANkeyword from the device definitions. If the commandwas sent to a 3172, contact your IBM servicerepresentative.

DTCSNM002W Netman Request : Invalid AttributeIndex attribute received, device address

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 indicated that the attributeindex number, attribute, contained in the request wasnot valid. See the TCP/IP User’s Guide for a list of the3172 Attribute Index values.




DTCSNM003W Netman Request : Invalid Operationoperation requested, device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 indicated that the operationfield operation of the request was not valid.




DTCSNM004W Netman Request : Unable to retrieverequested data attribute, device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 indicated that the 3172 wasunable to retrieve the data for the requested attributeattribute. This indicates a potential problem with the3172. See the TCP/IP User’s Guide for a list of the 3172Attribute Index values.


User or Operator Response: Check the 3172 for errors.

System Programmer Response: If the error persists,Contact the IBM Support Center.

DTCSNM005W Netman Request : Previouscommand pending, device addr.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 indicated that there was alreadyan outstanding request for this subchannel. This couldoccur if the SNMP subagent issued a request to the3172 for the interface at the same time that the interfacewas being activated, or if 2 requests for 3172 variableswere received close enough together that the 3172 hadnot responded to the first request when the second onewas received. Otherwise, this could be an error eitherin the TCPIP program or in the 3172.


User or Operator Response: Reissue the request. If theproblem persists, contact the system programmer.


DTCSNM006W Netman Request : Invalid countfield count, device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 indicated that the data count inthe count field of the request was not valid.






DTCSNM007W Netman Request : Unknown ReturnCode returncode, device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that wasreceived from the 3172 contained an unknown returncode returncode.




DTCSNM008W Netman Request : Request / ReplyAttribute Index mismatch : attribute1,attribute2, device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The attribute indexattribute2 in the response that was received from the3172 did not match the attribute index attribute1 of therequested variable. See the TCP/IP User’s Guide for a listof the 3172 Attribute Index values.




DTCSNM009W Netman Request : no responsereceived from device address.

Explanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. No Reply was receivedfrom the 3172. This is caused by one of the followingconditions:

1. A hardware problem that makes the 3172 physicallyunavailable

2. Heavy network traffic that causes the 3172 to notrespond before the NETMAN request timed out

3. The NETMAN request was sent to a device whichdoes not actually support the NETMAN request.


User or Operator Response: Check the 3172 forhardware problems. Issue the NETSTAT DEVLINKScommand to verify that this device is available toTCP/IP.

System Programmer Response: Verify that thePROFILE TCPIP file does not specify the optionalkeyword NETMAN for any LCS devices which do notactually support the 3172 Enterprise specific variables.

DTCSTM117I Conn connection: Telnet server:NoVacancy: Passive open failed.

Explanation: An attempt to establish a Telnetconnection by a passive open has failed, possibly dueto resource constraints. An accompanying DTCSTM118Imessage provides additional information about thisfailure. For more information about possible causes forthis failure, see the descriptions of the TcpOpen andTcpWaitOpen procedure calls in the Pascal LanguageAPI section of the TCP/IP Programmer’s Reference.



DTCSTM118I descriptive return code text

Explanation: This message provides supplementaryinformation for message DTCSTM117I. Descriptive textis displayed which corresponds to a numeric Pascalreturn code that is produced from an attempt to initiatea TCP connection. Thus, the text of this message canvary, depending on the specific return code obtainedfrom such attempts. See Appendix A of the TCP/IPProgrammer’s Reference for more information aboutpossible Pascal return codes and their correspondingdescriptive text.



DTCSTM256I Telnet server: Line-mode terminalnames will be prefixed with ’ccccc’

Explanation: During Telnet server functioninitialization, the CCSTERMNAME parameter wasdetected while processing the configuration file. Thecharacter string identified in the text of the messagewas extracted from the file and will be used as theprefix for terminal names of all line-mode Telnetsessions established on the system.

System Action: TCP/IP continues with theinitialization of the TCPIP virtual machine.

User or Operator Response: None required;informational message only.

System Programmer Response: None required;informational message only.



DTCSTM257E Telnet server: Invalid or missingvalue for CCSTERMNAME. Maximumlength is 5.

Explanation: During Telnet server functioninitialization, the CCSTERMNAME parameter wasdetected while processing the configuration file.However, the parameter either lacked a value or thevalue supplied exceeded 5 characters in length.

System Action: TCP/IP continues with theinitialization of the TCPIP virtual machine. TheCCSTERMNAME specification is ignored. The string’TCPIP’ is used as a prefix for terminal names ofline-mode Telnet sessions established on the system.


System Programmer Response: Either delete theCCSTERMNAME parameter specification from theINTERNALCLIENTPARMS statement in theconfiguration file or supply a valid character string tobe used as a terminal name prefix.

DTCSTM258E Conn connection: LdsfInitiate returnedcode

Explanation: The LDSF INITIATE presented by theTelnet server returned a bad return code.


User or Operator Response: None required.

System Programmer Response: Determine the causeof the LDSF failure and take appropriate action. See theDiagnose X'7C' section of the z/VM: CP ProgrammingServices book for more information.

DTCSTM259E Conn connection: LdsfInitiate returnedcode

Explanation: The LDSF INITIATE presented by theTelnet server returned a bad return code.



System Programmer Response: Determine the causeof the LDSF Initiate failure and take appropriate action.See the Diagnose X'7C' section of the z/VM: CPProgramming Services book for more information.

DTCSTM260E Conn connection: Ldev number numberis outside allowed range

Explanation: The Logical device number to be usedfor this Telnet connection exceeds the maximum rangespecified in the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement.



System Programmer Response: Increase the range oflogical device numbers that TCP/IP can use bymodifying the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement in PROFILETCPIP.

DTCSTM261E Conn connection: Ldev number numberis outside allowed range

Explanation: The Logical device number to be usedfor this Telnet connection exceeds the maximum rangespecified in the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement.



System Programmer Response: Increase the range oflogical device numbers that TCP/IP can use bymodifying the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement in PROFILETCPIP.

DTCSTM262E Telnet server: Invalid or out-of-rangevalues specified for LDEVRANGE.

Explanation: The additional parameters of theLDEVRANGE parameter contain erroneous values

System Action: LDEVRANGE parm is ignored.


System Programmer Response: Correct the valuesspecified on the LDEVRANGE parameter in PROFILETCPIP. Ensure that the upper limit is greater than thelower limit. Also, ensure that the upper limit is lessthan X'FFFF'.

DTCSTM263I Telnet server: Will use logical deviceaddresses in the range base through limit

Explanation: The Telnet server initialization detectedthe presence of the LDEVRANGE parameter on theINTERNALCLIENTPARMS statement. Logical devicerange has been set to the values that are indicated inthe message.



DTCSTM267E Telnet server: Conn n: Unable toallocate a data buffer, sessionterminated.

Explanation: This message indicates that Telnet wasunable to allocate a data buffer.





System Programmer Response: Increase the size ofthe TINYDATABUFFERPOOLSIZE in the TCPIPconfiguration file.

DTCSTM268E Telnet server: Invalid or missingvalue for ConnectExit. Maximum lengthis 8.

Explanation: This message indicates that the name ofthe ConnectExit that was specified on theINTERNALCLIENTPARMS statement was not valid.



System Programmer Response: Correct theConnectExit parameter of theINTERNALCLIENTPARMS statement the the TCPIPconfiguration file.

DTCSTM271E Telnet server: Load of ConnextExitfilename failed, Rc =returncode

Explanation: This message indicates that theConnectExit specified on theINTERNALCLIENTPARMS statement could not beloaded.



System Programmer Response: The action requireddepends on the return code received from the LOADmacro that was used to load the ConnectExit. See thez/VM: CMS Macros and Functions Reference forinformation on the LOAD macro.

DTCSTM272I Telnet server: ConnectExit filename isactive at loadaddress

Explanation: This message indicates that aConnectExit is active.




DTCSTM273I Telnet server: ConnectExit filename isnow inactive, RC=nn

Explanation: The session connection exit returned toTCP/IP with return code 12, 16, or 20. The exit will notbe called again. To re-enable the exit, TCP/IP must berestarted.



DTCSTM277I Conn connection: inSendDeviceTypeReject, ReasonReasonCode.

Explanation: TN3270E device type negotiations werein progress for TCP/IP connection connection and theyfailed. The value of ReasonCode indicates the nature ofthe failure. These values are defined and described inRFC 1647, “TN3270 Enhancements” in the section 7.1.6titled “REJECT Command”

User or Operator Response: You may need to definethe device type your TN3270 session is emulating to adevice type that is supported by the telnet server towhich you are connecting.

System Programmer Response: This message isdisplayed only when TCPIP diagnostic tracing is active.Examination of the reason code and other diagnosticmessages should indicate the cause of the REJECT.

DTCSTM292E Telnet server: Load of Tn3270eExitname failed, Rc = code

Explanation: The printer management exit could notbe loaded.

System Action: The printer management is notinvoked when TN3270 sessions start and end.

User or Operator Response: Ensure that the exit nameis specified correctly on the TN3270EEXIT parameter ofthe INTERNALCLIENTPARMS statement in theTCP/IP configuration file. Verify that the exit resides ina LOADLIB, TEXT file, or TXTLIB on a disk that isaccessed by the server.

DTCSTM293I Telnet server: Load of Tn3270eExitexitname is active at address

Explanation: The printer management exit calledexitname is loaded at the designated address.

System Action: The printer management is invokedwhen TN3270 sessions start and end.


DTCSTM294W Telnet server: Load of Tn3270eExitname is now inactive, Rc = code

Explanation: The printer management exit returned areturn code value specifying that it should bedeactivated.

System Action: The printer management is notinvoked when TN3270 sessions start and end.

User or Operator Response: Ensure that the exitdeactivated itself for an appropriate reason. Toreactivate the exit, TCP/IP must be restarted.



DTCSTM295I Telnet server: Erase All Unprotected(EAU) data will be ignored

Explanation: The Telnet server will modify the 3270data stream for the Erase All Unprotected (EAU)command before it is passed on to a Telnet client. Anydata received as part of a system-generated EAUcommand (X'0F') will be discarded. The message isdisplayed because the IGNOREEAUDATA parameterwas specified on the INTERNALCLIENTPARMSstatement in the TCPIP PROFILE.

System Action: Any data received as part of asystem-generated EAU command (X'0F') will bediscarded.


DTCSTM297I Telnet server: Line mode input will bepresented immediately

Explanation: The ASYNCHRONOUSINPUT optionhas been specified for the Telnet server in a TCP/IPconfiguration file. This could be either the initialconfiguration file or one designated using theOBEYFILE command.

System Action: For Telnet line-mode connections,causes the Telnet server to signal an attention interruptto the associated virtual machine when input isreceived from the client and the virtual machine hasnot issued a read. This will usually cause the virtualmachine to issue a read, allowing user input to bepresented.



DTCSTM298I Telnet server: Line mode input will bepresented when requested

Explanation: The ASYNCHRONOUSINPUT optionhas not been specified for the Telnet server in a TCP/IPconfiguration file.

System Action: The Telnet server will hold clientinput to the associated virtual machine until it issues aread. This is the server’s default mode of operation.Refer to the TCP/IP Planning and Customization book fora description of the ASYNCHRONOUSINPUTparameter of the INTERNALCLIENTPARMS statementto learn more about how to alter this behavior.



DTCSTM299I Telnet server: EOJTIMEOUT is valueseconds

Explanation: The INTERNALCLIENTPARMSconfigured value, in seconds, which determines howlong the Telnet server will wait before attempting to

send an EOJ to the TN3270E printer.



DTCSTM300I Telnet server: EOJTIMEOUT valuennn is out of range (1 – 99,999,999);EOJTIMEOUT set to default of 120seconds


Explanation: The number of seconds specified for theEOJTIMEOUT operand is not within the indicatedrange of accepted values. Therefore, the stated defaultvalue is in effect.



System Programmer Response: Check theINTERNALCLIENTPARMS statement (within theTCP/IP server configuration file in use) and verify theEOJTIMEOUT operand value has been correctlyspecified. Make any necessary changes, and then restartthe TCP/IP server.

DTCSTM301I Telnet server: INACTIVE value nnn isout of range (0 – 99,999,999); INACTIVEset to default of zero (0) seconds


Explanation: The number of seconds specified for theINACTIVE operand is not within the indicated range ofaccepted values. Therefore, the stated default value isin effect.



System Programmer Response: Check theINTERNALCLIENTPARMS statement (within theTCP/IP server configuration file in use) and verify theINACTIVE operand value has been correctly specified.Make any necessary changes, and then restart theTCP/IP server.

DTCSTM302I Telnet server: TIMEMARK value nnnis out of range (0 – 99,999,999);TIMEMARK set to default of 600seconds


Explanation: The number of seconds specified for theTIMEMARK operand is not within the indicated rangeof accepted values. Therefore, the stated default valueis in effect.





System Programmer Response: Check theINTERNALCLIENTPARMS statement (within theTCP/IP server configuration file in use) and verify theTIMEMARK operand value has been correctlyspecified. Make any necessary changes, and then restartthe TCP/IP server.

DTCTUD026I UdpSendTheDatagram: Cannot getenvelope to send multicast datagram

Explanation: TCPIP attempted to get an envelope tosend out a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent.




DTCUTI001E Serious problem encountered: date time

Explanation: A serious problem was encounteredwhich will be further explained in messageDTCUTI002.



System Programmer Response: The action requireddepends on the next message which will describe theerror.

DTCUTI002E Several variations of this message exist

Explanation: This message describes the problemencountered in message DTCUTI001E and in mostcases is self explanatory. Some variations of thismessage produce information that relates to the internaloperation of the TCP/IP server and is of value whenreporting problems to IBM.



System Programmer Response: If the problempersists, record the text of the error message andcontact the IBM Support Center.

DTCUTI003E Several variations of this message exist

Explanation: This message augments the DTCUTI001Eand DTCUTI002E messages proeviously encounteredand is self explanatory.



System Programmer Response: If the problempersists, record the text of the error message andcontact the IBM Support Center.

DTCUTI043I Diagnose DC error code code

Explanation: TCPIP received the indicated error returncode in response to a Diagnose X'DC' issued to producea monitor record. If the error code is 5, the TCPIPvirtual machine is not authorized to produce monitordata.

System Action: TCPIP does not produce monitorrecords.


System Programmer Response: If the error code is 5,ensure that the TCPIP virtual machine’s user directoryentry includes an OPTION APPLMON statement.Otherwise, contact your IBM Support Center.

DTCVMS002E Error code in command command

Explanation: An error occurred executing a commandspecified in a Performance Option command. APerformance Option command is specified in theCLIENTPERFOPTIONS statement in the PROFILE file.A CP command in this statement encountered an error.


User or Operator Response: Check the commandsspecified in the CLIENTPERFOPTIONS statement inthe PROFILE file for syntax errors. If syntax errors arenot present, troubleshoot each command individually,by placing each command in a separateCLIENTPERFOPTIONS statement. Delete one statementand reinitialize TCPIP. Continue this process until thewarning message does not appear. When the warningmessage no longer appears, the last statement deletedcontains the command in error. Correct the commandand reinitialize TCPIP.

DTCVMS003E I tried to spool a file to an invaliduserid: ID

Explanation: An attempt by TCPIP to spool a file to auser failed. The possible causes are:

v The user ID contains more than eight characters.

v The user ID is either missing or is not recognized;that is, the user ID is not in the system directory.

v TCPIP does not have authorization to send data tothe user, if your system has RACF installed.

v The user ID has a password of NOLOG.


User or Operator Response: First, determine if theuser ID contains more than eight characters, is missing,or is not in the system directory. If one of thesealternatives is true, a statement in the PROFILE file



specified an incorrect user ID. Suspect PROFILEstatements include:v AUTOLOGv CLIENTPERFOPTIONSv INFORMv OBEYv PORT

Check each of these statements in the PROFILE todetermine if any specify the user ID contained in themessage. If any do specify this user ID, correct thePROFILE statements to specify a valid user ID. RestartTCPIP.

If the user ID does not contain more than eightcharacters, is not missing, and is in the systemdirectory, two problems are indicated. First, if yoursystem has RACF installed, the TCPIP virtual machinemay not have RACF authorization to send data to thespecified user. See your RACF administrator todetermine if this is the case and to arrangeauthorization, if necessary. If this is not the cause, theuser ID may have a password of NOLOG. Contact yoursystem administrator to establish a valid password forthis user ID.



Chapter 21. TCP/IP Utilities

This chapter contains CONVXLAT, FTPPERM and NFSPERM, HOMETEST,IFCONFIG, IPWIZARD, OBEYFILE, and TCPRUN messages.

CONVXLAT MessagesThis section contains the CONVXLAT messages.

DTCCNX001E Usage: CONVXLAT InFileName-OutFileName- (KANJI|HANGEUL|TCHINESE-CODEFILE-

Severity: Error.

Explanation: Invalid syntax was specified for theCONVXLAT command.

System Action: Program execution halts. No outputfile is produced.

User or Operator Response: Re-enter the commandusing valid syntax. See TCP/IP Planning andCustomization for more information about customizingDBCS/SBCS translation tables using CONVXLAT.

Source File: CMCONVXL PASCAL

Procedure Name: GetParameters,DoIt

DTCCNX002E Input file file not found

Severity: Error.

Explanation: The CONVXLAT command specified aninput file that does not exist.

System Action: Program execution halts. No outputfile is produced.

User or Operator Response: Re-enter the commandspecifying an existing file for the InFileNameparameter. Ensure the file contains valid translationtables. See the TCP/IP Planning and Customization formore information about customizing DBCS/SBCStranslation tables using CONVXLAT.



DTCCNX003E Premature EOF on input file file

Severity: Error.

Explanation: The CONVXLAT command specified anSBCS input file that ended prematurely, before theoutput translation table was completed.

System Action: Program execution halts. An invalidoutput file is produced.

User or Operator Response: Re-enter the commandspecifying a valid file for the InFileName parameter.Ensure the file contains valid SBCS translation tables.See TCP/IP Planning and Customization for moreinformation about customizing DBCS/SBCS translationtables using CONVXLAT.


Procedure Name: DoOneTable

DTCCNX004E Error in input line: ″input_record″

Severity: Error.

Explanation: The CONVXLAT command specified anSBCS input file that contained a data error in thespecified line. The line did not contain validhexadecimal codes.


User or Operator Response: Re-enter the commandspecifying a valid file for the InFileName parameter.Ensure the file contains valid SBCS translation tables.See the TCP/IP Planning and Customization book formore information about customizing DBCS/SBCStranslation tables using CONVXLAT.



DTCCNX005E Input contains wrong number ofbytes: ″input_record″

Severity: Error.

Explanation: The CONVXLAT command specified anSBCS input file that contained a data error in thespecified line. The line did not contain 16 validhexadecimal codes.


User or Operator Response: Re-enter the commandspecifying a valid file for the InFileName parameter.Ensure the file contains valid SBCS translation tables.See the TCP/IP Planning and Customization book formore information about customizing DBCS/SBCS


translation tables using CONVXLAT.



DTCCNX006E Error in SBCS input data. Incorrectnumber of code point mappings.

Severity: Error.

Explanation: The input file for the CONVXLATcommand did not contain 256 single byte code pointmappings.

System Action: Program execution halts. An outputfile is produced but is not valid.

User or Operator Response: The SBCS translationdata must contain exactly 256 code point mappingswhen using CONVXLAT options KANJI, HANGEUL orTCHINESE. Ensure that the input file has the correctnumber of single byte code point mappings. See theTCP/IP Planning and Customization book for moreinformation about customizing DBCS/SBCS translationtables for use by CONVXLAT.


Procedure Name: DoDbcsBinFile, DoCodeFiles

DTCCNX008W DBCS code is defined more thanonce - code_index. Continuing ...

Severity: Warning.

Explanation: The error occurred during processing ofDBCS translation data from the input file. A DBCS codeindex was defined more than once.

System Action: Program execution continues. TheDBCS code defined more than once will have the valuefirst assigned to it in the input file.

User or Operator Response: Ensure that all DBCScodes in the file are defined only once. See the TCP/IPPlanning and Customization book for more informationabout customizing DBCS/SBCS translation tables foruse by CONVXLAT.



DTCCNX009W DBCS code index - code_index - out oforder. Continuing...

Severity: Warning.

Explanation: The error occurred during processing ofDBCS translation data from the input file. A DBCS codeindex was found that was numerically less than theprevious code index.

System Action: Program execution continues. Theoutput file may contain unpredictable results andshould not be used.

User or Operator Response: Ensure that all DBCScodes in the file are defined in numerical order fromthe lowest value to the highest. See TCP/IP Planningand Customization for more information aboutcustomizing DBCS/SBCS translation tables for use byCONVXLAT.



DTCCNX010I Current code set is - code_file


Explanation: This message is displayed when theCODEFILE option of CONVXLAT is used. It indicateswhich codefile is currently being generated.




Procedure Name: DoCodeFiles

DTCCNX011W SBCS code is defined more than once- code_index. Continuing ...

Severity: Warning.

Explanation: The error occurred during processing ofSBCS translation data from the input file. An SBCScode index was defined more than once.

System Action: Program execution continues. TheSBCS code defined more than once will have the valuefirst assigned to it in the input file.

User or Operator Response: Ensure that all SBCScodes in the file are defined only once. See the TCP/IPPlanning and Customization book for more informationabout customizing DBCS/SBCS translation tables foruse by CONVXLAT.



DTCCNX012W SBCS code index - code_index - out oforder. Continuing...

Severity: Warning.

Explanation: The error occurred during processing ofSBCS translation data from the input file. An SBCScode index was found that was numerically less thanthe previous code index.

System Action: Program execution continues. Theoutput file will contain unpredictable results andshould not be used.

User or Operator Response: Ensure that all SBCScodes in the file are defined in numerical order fromthe lowest value to the highest. See the TCP/IP Planningand Customization book for more information about

CONVXLAT Messages


customizing DBCS/SBCS translation tables for use byCONVXLAT.



DTCCNX013I No SBCS input data in input file file

Severity: Error.

Explanation: The input file contained only DBCS codepoint mappings and did not contain the associatedSBCS data.

System Action: Program execution halts. The outputfile will not be complete and should not be used.

User or Operator Response: Ensure that the input filecontains appropriate SBCS code point mappings. Seethe TCP/IP Planning and Customization book for moreinformation about customizing DBCS/SBCS translationtables for use by CONVXLAT.



DTCCNX015I Error in first line of translation data:input_record

Severity: Error.

Explanation: The first line of translation data in theinput file was in error. This error may be caused by anincorrect number of translation data columns or byincorrect (for example, too long, too short, not hex data,and so forth) data in the columns. The first line of datamust contain correct and complete data for processingto continue.

System Action: Program execution halts. The outputfile will be empty.

User or Operator Response: Ensure that the input filecontains the appropriate translation data in the first lineof uncommented data. See TCP/IP Planning andCustomization for more information about customizing

DBCS/SBCS translation tables for use by CONVXLAT.



DTCCNX016I Error in DBCS input line: input_record

Severity: Error.

Explanation: An error was found processing a line ofDBCS translation data from the input file. Incorrectdata was found in one of the columns of the input line.

System Action: Program execution halts. The outputfile will contain invalid data and should not be used.

User or Operator Response: Ensure that the input filecontains valid translation data in all DBCS data lines.See TCP/IP Planning and Customization for moreinformation about customizing DBCS/SBCS translationtables for use by CONVXLAT.



DTCCNX017I Error in SBCS input line: input_record

Severity: Error.

Explanation: An error was found processing a line ofSBCS translation data from the input file. Incorrect datawas found in one of the columns of the input line.

System Action: Program execution halts. The outputfile will contain invalid data and should not be used.

User or Operator Response: Ensure that the input filecontains valid translation data in all SBCS data lines.See TCP/IP Planning and Customization for moreinformation about customizing DBCS/SBCS translationtables for use by CONVXLAT.



FTPPERM and NFSPERM MessagesThis section contains FTPPERM and NFSPERM messages.

0010 You do not have a RACF VMBATCHprofile, so you do not need to useprogram_name

Severity: Error.

Explanation: You have attempted to give the FTP orNFS server the authority needed to act on your behalf,but a discrete VMBATCH profile was never created foryou. However, the FTP or NFS server may have beengiven access to the generic VMBATCH profile.


User or Operator Response: Go ahead and attempt touse the server. If you receive:

530-FTP Server lacks Alternate Useridpermission to act on behalf of userid,returned 12

for FTP, or if you receive an NFS mount failure, contactyour system support personnel.

The server must be given CONTROL access to thegeneric VMBATCH profile, or a discrete VMBATCHprofile must be created for you and you must retry thecommand.

CONVXLAT Messages

Chapter 21. TCP/IP Utilities 361

Source File: FTPPERM EXEC, NFSPERM EXEC

0011 User userid does not have a RACFVMBATCH profile

Severity: Error.

Explanation: You have attempted to give the FTP orNFS server the authority needed to act on behalf of thespecified user, but a discrete VMBATCH profile doesnot exist for that user.


User or Operator Response: Create a VMBATCHprofile for the user and try the command again, or giveeach FTP or NFS server CONTROL access to thegeneric VMBATCH profile.

Source File: NFSPERM EXEC, FTPPERM EXEC

0012 Syntax Error


Explanation: You have issued the NFSPERM or

FTPPERM command incorrectly.


User or Operator Response: Correct the syntax andreissue the command. The for_userid parameter is usedonly by a RACF system administrator to issue thiscommand on behalf of another user.


0013 A RACF/VM error was encountered;ensure filemode A is accessed read/write

Severity: Error.

Explanation: The RACF command used by FTPPERMand NFSPERM use file mode A to hold temporary data,but file mode A is currently accessed read only.


User or Operator Response: Access file mode A inread/write mode.


HOMETEST MessagesThis section contains the HOMETEST messages.

Cannot issue CP Query Userid Command

Severity: Error.

Explanation: The READtcpipDATAfile procedureissued a nonzero return code.


User or Operator Response: Determine the nature ofthe problem, correct it, and try again. If the problempersists, contact the IBM Support Center.

Source File: HOMETEST PASCAL

Procedure Name: Test

Cannot use TCP/IP: ReturnCode

Severity: Error.

Explanation: TCPIP is not available because of thelisted reason.


User or Operator Response: Determine the nature ofthe problem, correct it, and try again.



Error: Address is not in the HOME List

Severity: Error.

Explanation: The listed IP address could not be foundin the HOME list.


User or Operator Response: Correct the IP address inthe HOME list, the name server, or the site tables, andrerun HOMETEST.



Error: Found no IP addresses corresponding to TCPHost Name: Name

Severity: Error.

Explanation: The listed TCP host name could not beresolved because there are no corresponding IPaddresses.


User or Operator Response: Correct the HOSTNAMEvariable in the TCPIP DATA file, or the records in thename server or sites tables, and rerun HOMETEST.



FTPPERM and NFSPERM Messages


Error: Name resolution through Nameserver wasunsuccessful. Reason: ReturnCode

Severity: Error.

Explanation: The TCP host name could not beresolved using the name server for the listed reason.


User or Operator Response: Determine whyHOMETEST cannot communicate with the name server,and rerun HOMETEST.



InitEmulation failed, try again with ECMODE ON

Severity: Error.

Explanation: TCPIP emulation testing was notsuccessful.


User or Operator Response: Issue the command "#CPSET ECMODE ON", then re-IPL CMS. If the program failsagain, try to determine the reasons for the failurebefore a third attempt.



IFCONFIG MessagesThis section contains the IFCONFIG messages.

DTCIFC2601E Unexpected return code fromcommand; RC=rc

Explanation: The requested function could not becompleted because of an unexpected return code fromthe indicated command.

System Action: Command processing stops.

User or Operator Response: Consult the relevantcommand reference to determine the cause of theproblem. After correcting the condition, try entering thecommand again.

DTCIFC2601W Unexpected return code fromcommand; RC=rc



User or Operator Response: Consult the relevantcommand reference to determine the cause of theproblem and attempt to correct the condition.

DTCIFC2602E A program error occurred in functionname

Explanation: The IFCONFIG command hasencountered an unexpected condition.


User or Operator Response: Contact the IBM SupportCenter.

DTCIFC2603E A read/write minidisk is required touse this function

Explanation: IFCONFIG requires you to have aminidisk accessed read/write so that it can create a

temporary file used by the TCP/IP OBEYFILEcommand.


User or Operator Response: Access a minidisk inread/write mode. SFS directories and temporaryminidisks (TDISKs) cannot be used.

DTCIFC2604E TCP/IP OBEY authority is required toperform this function

Explanation: You can add or modify TCP/IPinterfaces only if your user ID is listed on the OBEYstatement in the configuration profile used by theTCP/IP stack virtual machine.


User or Operator Response: Update the OBEYstatement and try the command again.

DTCIFC2605E TCP/IP stack userid is not available

Explanation: The target TCP/IP stack virtual machineis not logged on.


User or Operator Response: Start the indicated virtualmachine and try the command again.

DTCIFC2606E operand cannot be {specified |changed} for this interface

Explanation: Either the indicated operand is not validor cannot be changed for this type of interface. Forexample, POINTOPOINT may not be used on LANinterfaces, and once specified, a PORTNUMBER for aninterface cannot be changed.


User or Operator Response: Correct the condition andtry the command again.

HOMETEST Messages


|

||||

|||

|

||||

|||

|||

|

|||

|||

||

|

||

|||

||

||

|

|||

|||

||||

|

||

||

||

|

||

|||

|||||

|

||

DTCIFC2607E {operand | Home IP address} can bespecified only once

Explanation: The indicated operand or home IPaddress appears more than once in the command thatwas entered.



DTCIFC2608E The type interface specification is notcomplete

Explanation: Required information on the interfacespecification has not been provided.


User or Operator Response: Consult the commandreference documentation and try the command again,providing all of the required information.

DTCIFC2609E No value has been specified for the{operand operand | option option | homeIP address}

Explanation: Either an operand or option wasprovided, but its corresponding value is missing, or nohome IP address was specified.



DTCIFC2610E The {operand | operand1 or operand2}operand is required, but {has not beenspecified | neither has been specified}

Explanation: A required operand is missing.



DTCIFC2611E Interface name already exists

Explanation: The specified name is already assignedto another interface.


User or Operator Response: Choose another nameand try the command again.

DTCIFC2612E Unknown interface: name

Explanation: The specified interface does not exist.



DTCIFC2613E Device {number devno does | numbersdevno1–devno2 do} not exist

Explanation: The specified devices do not exist.


User or Operator Response: Ensure that the correctdevice numbers have been specified and that alldevices are available to the z/VM system. If necessary,use the CP VARY ON command to bring the devicesonline.

DTCIFC2614E ″text″ is not a valid operand or option

Explanation: The indicated value is not a recognizedIFCONFIG operand or option.



DTCIFC2615E ″text″ is not a valid CLAW adaptername

Explanation: The specified CLAW adapter name is toolong. The name is limited to 16 characters.



DTCIFC2616E ″text″ is not a valid IP address

Explanation: The specified value is not a valid IPaddress. The IP address must be in the range 0.0.0.1 to223.255.255.255.



DTCIFC2617E ″text″ is not a valid CLAW host name

Explanation: The specified CLAW host name is toolong. The name is limited to 8 characters.



DTCIFC2618E ″text″ is not a valid LAN name

Explanation: The specified guest LAN name is toolong. The name is limited to 8 characters.



IFCONFIG Messages


|||

|||

|

||

|||

||

|

|||

||||

|||

|

||

||||

|

|

||

||

||

|

||

||

|

|

||

|||

|

|

|||||

||

||

|

||

|||

||

|

||

||

|||

|

||

||

||

|

||

||

||

|

||

|||

DTCIFC2619E ″text″ is not a valid minidiskpassword

Explanation: The specified password is too long. Thepassword is limited to 8 characters.



DTCIFC2620E ″text″ is not a valid MTU size

Explanation: The value specified for the MaximumTransmission Unit (MTU) size must be from 576 to65535, unless the interface is virtual ethernet. The MTUsize specified for a virtual ethernet interface cannot begreater than 8092.


User or Operator Response: Consult the device orproduct documentation to determine the correct value.

DTCIFC2621E ″text″ is not a valid interface name

Explanation: The indicated interface name is not valid.An interface name cannot begin with a dash (—), endwith a colon (:), or contain a semicolon (;).


User or Operator Response: Try the command againspecifying a valid interface name.

DTCIFC2624E ″text″ is not a valid port name

Explanation: The specified value is not a valid IBMOpen Systems Adapter port name. The port name islimited to 8 characters.



DTCIFC2625E ″text″ is not a valid port number

Explanation: The specified value is not a valid portnumber.v For Channel-to-Channel connections, specify 0 or 1.v For IBM Open Systems Adapters operating in LCS

mode, specify 0 or 1.v For all other LCS devices, specify a number in the

range 0-255.v Do not specify a port number for other device types.



DTCIFC2626E ″text″ is not a valid device number

Explanation: The specified value is not a valid devicenumber. A device number is a hexadecimal number inthe range 0-FFFE. For HiperSockets and QDIO devices,valid device numbers range from X'0001' to X'FFFD'.For channel-to-channel, CLAW and LCS devices, validdevice numbers range from X'0001' to X'FFFE'.



DTCIFC2627E ″text″ is not a valid user ID

Explanation: The VM user ID that was specified islonger than 8 characters or contains a semicolon (;) oran asterisk (*).



DTCIFC2628E operand1 and operand2 are conflictingoperands

Explanation: The indicated operands cannot bespecified at the same time on the IFCONFIG command.



DTCIFC2629E IP address (ipaddr) cannot be abroadcast address

Explanation: The indicated IP address is a broadcastIP address. All of the host bits in the IP address, asdefined by the subnet mask, are ″on.″



DTCIFC2630E IP address (ipaddr) cannot be the sameas the peer IP address

Explanation: The home and peer IP addresses areidentical.



DTCIFC2631E ″mask″ is not a valid subnet mask

Explanation: The indicated subnet mask does notconform to the rules for subnet masks. The mask mustbe in the range 255.0.0.0 to 255.255.255.255, and all″one″ bits must be to the left of all ″zero″ bits.

IFCONFIG Messages


|||

||

|

||

||

|||||

|

||

||

|||

|

||

||

|||

|

||

||

||||||||

|

||

|

||

||||||

|

||

||

|||

|

||

|||

||

|

||

|||

|||

|

||

|||

||

|

||

||

||||



DTCIFC2632E IP address (ipaddr) cannot be the sameas the subnet value

Explanation: The indicated IP address is the same asthe subnet value. All of the host bits in the IP address,as defined by the subnet mask, are ″off.″



DTCIFC2633E MTU size mtu is larger than thatallowed for the corresponding maximumframe size (mfs) for the adapter

Explanation: The MTU size is limited to the maximumframe size (MFS) of the HiperSocket adapter, minus 8K.The largest MFS that can be defined is 64K (65536)giving a corresponding maximum MTU of 56K (57344).

The MFS for real HiperSocket adapters is controlled bythe IOCDS. The MFS for virtual HiperSocket adaptersis controlled by the CP DEFINE NIC command.



DTCIFC2634E Port number must be 0 or 1

Explanation: The port number for this device must bespecified as 0 or 1.



DTCIFC2635E Port number is not within the range0-255

Explanation: The port number for this device must bewithin the range 0-255.



DTCIFC2636E An unexpected error was encounteredwhile attempting to modify the activeTCP/IP configuration: message

Explanation: The requested function could not becompleted because of an unexpected response from theOBEYFILE command.

System Action: The interface is not defined.Command processing stops.

User or Operator Response: Follow the instructionsprovided at the end of this message. After correctingthe condition, try entering the command again.

DTCIFC2636W An unexpected error was encounteredwhile attempting to modify the activeTCP/IP configuration: message

Explanation: The requested function could not becompleted because of an unexpected response from theOBEYFILE command.


User or Operator Response: Follow the instructionsprovided at the end of this message. After correctingthe condition, try entering the command again.

DTCIFC2637E IP address (ipaddr) and subnet mask(mask) imply a subnet value of 0

Explanation: All of the network bits in the indicatedIP address, as defined by the subnet mask, are zero.



DTCIFC2638E Devices devno1–devno2 must be on thesame CHPID

Explanation: All of the device numbers for this devicemust reference the same real device.


User or Operator Response: Correct the problem orspecify the -FORCE option and try the command again.

DTCIFC2639E Device devno is not of type type

Explanation: You have specified a device that is notcompatible with the type of interface you are trying todefine. For example, attempting to define an IBM OpenSystems Adapter as a channel-to-channel interface willresult in this error message.

System Action: The interface is not defined andcommand processing stops.

User or Operator Response: Correct the problem orspecify the —Force option of the IFCONFIG command,and then try the command again.

DTCIFC2639W Device devno is not of type type

Explanation: You have specified a device that is notcompatible with the type of interface you are trying todefine. For example, attempting to define an IBM OpenSystems Adapter as a channel-to-channel interface willresult in this error message.

System Action: The interface is defined and started,

IFCONFIG Messages


|

||

|||

|||

|

||

||||

||||

|||

|

||

||

||

|

||

|||

||

|

||

||||

|||

||

|||

||||

|||

|

|||

|||

||

|

||

|||

||

|

||

||

|||||

||

|||

||

|||||

|

but no communication takes place. An error file fromz/VM TCP/IP is returned.

User or Operator Response: Correct the problem andstart the device.

DTCIFC2640E Network mask 255.255.255.255 is validonly for point-to-point interfaces

Explanation: The indicated subnet mask does notconform to the rules for subnet masks for interfacesthat are not point-to-point.



DTCIFC2641W Connection cannot be established;user userid is not logged on

Explanation: The connection cannot be establishedbecause the indicated VM user is not logged on.

System Action: The interface is defined and started,but no communication takes place. An error file fromz/VM TCP/IP is returned.

User or Operator Response: The indicated user mustestablish the connection.

DTCIFC2642W Connection cannot be established;virtual CTC devices devno1–devno2 arenot all defined on user userid

Explanation: The indicated VM user has not defined avirtual channel-to-channel (CTC) on the indicateddevice numbers. Therefore, the connection cannot beestablished.


User or Operator Response: The indicated user mustdefine a virtual CTC device for the specified devicenumbers to establish the connection.

DTCIFC2643W Connection cannot be established;device devno is busy on user userid

Explanation: A temporary busy condition has beendetected while trying to establish a virtualchannel-to-channel connection.


User or Operator Response: The devices must bemanually connected using the CP COUPLE command.

DTCIFC2644W Connection cannot be established

Explanation: An unexpected condition wasencountered while trying to establish the requestedconnection. This message is followed by messageDTCIFC2601W.


User or Operator Response: Examine messageDTCIFC2601W to determine the cause of the problem.

DTCIFC2645E Virtual interface cannot be created

Explanation: An unexpected error was encounteredwhile creating a needed virtual device. This message isfollowed by message DTCIFC2601E.


User or Operator Response: Examine messageDTCIFC2601E to determine the cause of the problem.

DTCIFC2646E Devices devno1–devno2 are not allattached to user userid

Explanation: Some but not all of the real devices thatare needed are attached to the indicated user.


User or Operator Response: Either attach or detach allof the devices that are needed to or from the indicateduser and try the command again.

DTCIFC2647E Devices devno1–devno2 must all be ofthe same type

Explanation: One or more real devices in the indicatedrange are not of the same type. Probably the devicetype is incorrect or the wrong device number wasspecified on the command.



DTCIFC2648E Interface type (type) is not supportedby IFCONFIG

Explanation: You have attempted to display or modifya TCP/IP interface not support by IFCONFIG.


User or Operator Response: Use the OBEYFILEcommand to change the settings of this interface. Usethe NETSTAT command to display details about theinterface.

IFCONFIG Messages


||

||

|||

|||

|

||

|||

||

|||

||

||||

||||

|||

|||

|||

|||

|||

||

|

||

||||

|

||

||

|||

|

||

|||

||

|

|||

|||

||||

|

||

|||

||

|

||||

|||

DTCIFC2649E Device numbers devno1–devno2 areattached to user userid withdiscontiguous virtual device numbers

Explanation: All of the listed devices have beenattached to the indicated user, but they are not attachedin a contiguous range of virtual device numbers.


User or Operator Response: Detach all of the devicesfrom the indicated user and try the command again.

DTCIFC2650E Device number devno is offline

Explanation: The indicated device is defined to thesystem, but is not online.


User or Operator Response: Choose another device oruse the CP VARY ONLINE command to bring thedevice online and try the command again.

DTCIFC2651E Device number devno is already in use

Explanation: The indicated device is already in use bysome other user or by the system.


User or Operator Response: Choose a different deviceor make the device available, and try the commandagain.

DTCIFC2652E Device devno cannot be attached touser userid

Explanation: An unexpected error was encounteredwhile attempting to attach the indicated real device.This message is followed by DTCIFC2601E.


User or Operator Response: Examine messageDTCIFC2601E to determine the cause of the problem.

DTCIFC2652W Device devno cannot be attached touser userid

Explanation: An unexpected error was encounteredwhile attempting to attach the indicated real device.This message is followed by DTCIFC2601W.


User or Operator Response: Examine messageDTCIFC2601W to determine the cause of the problem.

DTCIFC2653E Device devno is attached to user userid

Explanation: The indicated device is already attachedto another user.


User or Operator Response: Choose a different deviceor free up the indicated device and retry the command.

DTCIFC2654E userid is unable to link to your vaddrminidisk which is currently accessed asfile mode filemode

Explanation: The z/VM TCP/IP stack virtual machinecannot link to the minidisk which contains thetemporary obey file created by IFCONFIG.


User or Operator Response: Retry the command withthe —Mdiskpw option specified. If minidisks areprotected by an external security manager, such asRACF, then give the user READ permission to theminidisk.

DTCIFC2655E Connection cannot be established;user userid does not exist

Explanation: The requested connection cannot beestablished because you specified a user ID that is notdefined to the system.



DTCIFC2656E Device devno is not available

Explanation: The indicated device did not respond.


User or Operator Response: Determine the status ofthe device. Correct the condition or choose anotherdevice and try the command again.

DTCIFC2657E LAN name name is of type type

Explanation: The indicated LAN type does not matchthe requested interface type.


User or Operator Response: Choose another LAN oranother interface type and try the command again.

DTCIFC2658E Cannot determine device type fordevice devno

Explanation: IFCONFIG cannot verify that yourrequest is valid because the indicated device did notidentify itself to the system.


User or Operator Response: Choose another device,or try the command again with the —Force optionspecified.

IFCONFIG Messages


||||

|||

|

||

||

||

|

|||

||

||

|

|||

|||

|||

|

||

|||

|||

|

||

||

||

|

||

||||

|||

|

|||||

|||

|||

|

||

||

|

|

|||

||

||

|

||

|||

|||

|

|||

|||

DTCIFC2659E No suitable virtual device numbersare available for use

Explanation: There are no usable virtual devicenumbers available on the z/VM TCP/IP stack virtualmachine. You cannot define anymore TCP/IPinterfaces.


User or Operator Response: Delete unneeded virtualdevices from the TCP/IP stack virtual machine and trythe command again.

IPWIZARD MessagesThis section contains the IPWIZARD messages.

DTCIPW0000E Message repository DTCUME TEXTcannot be loaded

Explanation: The TCP/IP message repository file(DTCUME TEXT) is required so messages can be issuedby this program, but this file was not found in the CMSsearch order.


User or Operator Response: Verify that the TCP/IP“Client” code minidisk (TCPMAINT 592, by default) islinked and accessed before the program that issued thismessage is called again. If this problem persists, informthe system administrator.

System Programmer Response: This error indicates anincorrect or incomplete product installation. Verify thatthe listed file exists on the TCP/IP “Client” codeminidisk. If the file exists, it is possible that this diskcontains an older level of TCP/IP.

DTCIPW2502I Configuration files created. Operationcancelled by userid; TCP/IP has not beenrestarted.

Explanation: The TCP/IP stack needs to be restartedfor the configuration changes to take effect. You chosenot to have the stack restarted.

System Action: This message is followed byDTCIPW2512E.


DTCIPW2503E {Pipe command | Command} cmdfailed with return code RC=rc



User or Operator Response: Consult the relevantcommand reference to determine the cause of theproblem. After correcting the condition, enter thecommand again.

DTCIPW2504E Error attempting to FORCE userid

Explanation: An error occurred while attempting toFORCE the specified user ID. The CP FORCEcompleted without error, but the user ID was notsuccessfully logged off.


User or Operator Response: Manually restart thestack and verify its connectivity.

DTCIPW2505E Error reading data file: datafile

Explanation: An error occurred while attempting toread the specified file, which provides informationnecessary for creating configuration files for yourinstallation.


User or Operator Response: Verify that the listed fileis accessible and readable.

DTCIPW2506E Configuration files created. Cannotverify connectivity because interfaceinterface did not start properly.

Explanation: Configuration files that incorporate yourvalues have been created successfully. However, thespecified interface was not in READY mode when theTCP/IP stack was restarted, so network connectionscannot be tested and validated.


User or Operator Response: Consult the TCP/IPserver console log to determine the reason for the error.

DTCIPW2507E Error linking TCP/IP 198 and 592disks

Explanation: An error occurred while attempting tolink the TCP/IP 198 or 592 disk.


User or Operator Response: Verify that you canestablish write access to the TCP/IP 198 and 592 disks,and try the command again.

IFCONFIG Messages


|||

||||

|

|||

||

||||

||||

|

|||||

|||||

||||

|||

||

|

|||

|||

||

||||

||

||||

||

||

||

||||

||

||

||||

|||||

||

||

|||

||

|

|||

DTCIPW2508I execname is attempting to create thenecessary configuration files.

Explanation: Indicates the program has startedcommand processing.

System Action: Command processing begins.


DTCIPW2509E Unexpected error encountered byexecname

Explanation: An unexpected error occurred duringcommand processing.


User or Operator Response: Review the descriptionsof all messages that have been issued in conjunctionwith this message, and correct the problem. Then, enterthe command again.

DTCIPW2510E Operation cancelled by execname; theSYSTEM NETID file is not properlyconfigured.

Explanation: A CP IDENTIFY command returned anasterisk in the node name field, which indicates thatthe SYSTEM NETID file has not yet been configured orhas been improperly configured.


User or Operator Response: Correct the configurationof the SYSTEM NETID file, and enter the commandagain.

DTCIPW2512I Operation cancelled; {existingconfiguration is maintained | newconfiguration has been created |configuration incomplete}

Explanation: You chose to cancel command processingeither because a previous configuration was found orbecause the TCP/IP stack was logged on.



DTCIPW2513E Error creating file fn ft fm

Explanation: An error occurred while attempting towrite the specified file to disk.


User or Operator Response: Verify write access to thespecified disk, and enter the command again.

DTCIPW2517E Connectivity verification was notsuccessful

Explanation: Configuration files have been created butone or more of the connectivity verification tests failed.


User or Operator Response: Modify the data, and trythe command again.

DTCIPW2518W Configuration files created;connectivity has not been verified

Explanation: Configuration files for your installationhave been created, but one or more of the connectivityverification tests failed. Following this, you chose to notfurther modify your values or to attempt theconnectivity verification tests again.



DTCIPW2519I Configuration complete; connectivityhas been verified

Explanation: Configuration files for your installationhave been created, and connectivity verification wassuccessful.



IFCONFIG Messages


|||

||

|

|

|||

||

|

||||

||||

||||

||

|||

|||||

|||

|

|

||

||

||

||

|

|||

||

|

||

|||

|||||

|

|

|||

|||

|

|

OBEYFILE MessagesThis section contains the OBEYFILE messages.

Invalid mode: mode

Severity: Error.

Explanation: You input an incorrect file mode. TCP/IPassumes that the user intended a file mode of A, butforgot to type the letter A before the password.


User or Operator Response: The user should input afile name, file type, and a file mode before entering thepassword.

Mode mode is not a minidisk

Severity: Error.

Explanation: You specified a file that resides on a SFSor BFS directory, not a minidisk. OBEYFILE can onlyprocess files that are stored on minidisks.


User or Operator Response: Copy the obey file to aminidisk and re-issue the OBEYFILE command.

TCPRUN MessagesThis section contains TCPRUN messages.

1001 "command" failed with return code rc

Severity: Error.

Explanation: The indicated CP or CMS commandfailed. Its successful completion is required in order forthe server to run. This message is preceded by errortext.


User or Operator Response: Correct the error.

Source File: TCPRUN EXEC

1002 File file was not found on any accesseddisk or directory

Severity: Warning or Error.

Explanation: The listed file was not found on anyaccessed minidisk or directory. For error conditions,this file is required and should reside on a specificTCP/IP minidisk (TCPMAINT 591, 592, or 198). Forwarning conditions, the file should exist on one ofthese same disks. Note that the absence of such a filecan lead to unexpected errors during serverinitialization or later server operations.

System Action: For a warning condition, serverinitialization continues; for error conditions, serverinitialization stops.

User or Operator Response: The receipt of thismessage indicates an incorrect or incompleteenvironment, after having installed TCP/IP. Forexample, the (non-customized) IBM DTCPARMS file isa required file that should exist on the TCPMAINT 591minidisk, whereas certain customized files such as theTCPIP DATA file (commonly referenced by bothTCP/IP servers and clients) should reside on theTCPMAINT 592 minidisk.

Ensure the correct TCP/IP minidisks are linked and

accessed. It is also possible that one or more accesseddisks contain an older version (level) of TCP/IP. Forinformation about where specific files should resideconsult the TCP/IP Planning and Customization or theappropriate TCP/IP Program Directory.


1003 :tagname.value specified in fn ft is notvalid

Severity: Error.

Explanation: The indicated tag does not have a validvalue.


User or Operator Response: Update the file or exec toprovide a valid value for the tag.


1004 Missing value for tag :tag. in fn ft

Severity: Error.

Explanation: A value for the indicated tag is required,but was not provided. The file name and file type mayrefer to a DTCPARMS file or to an exit exec.


User or Operator Response: Update the DTCPARMSfile or exit exec to include a value for the indicated tag.


1005 Required tag :tag. was not found in fn1ft1 [or fn2 ft2]

Severity: Error.

Explanation: The indicated tag was not included in

OBEYFILE Messages


|

|||

|

||||||||

|||

|||||||||

|

|||||

|

the indicated DTCPARMS file or exit exec, but isrequired.

User or Operator Response: Update the DTCPARMSfile or exit exec to include the indicated tag and tagvalue.



1006 Filemode fm is not read/write, but wasspecified on :Diskwarn. in fn ft

Severity: Warning.

Explanation: The :Diskwarn. tag has been specifiedbut the file mode is accessed read only. This usuallyapplies to file mode A, but may apply to any accessedfile mode.


User or Operator Response: Access the indicated filemode read/write.


1007 One or more required libraries were notfound

Severity: Error.

Explanation: The C or Pascal runtime library,SCEERUN or TCPRTLIB LOADLIB, respectively, wasnot found on any accessed disk or directory.


User or Operator Response: This error indicates anincorrect or incomplete installation. TCPRTLIBLOADLIB should be on the TCP/IP client disk (bydefault, TCPMAINT 592), and SCEERUN LOADLIBshould be on the Y-disk (by default, MAINT 19E).


1008 Server [class] name is not defined inuserid, nodeid, SYSTEM or IBMDTCPARMS file

Severity: Error.

Explanation: The server’s user ID or class name couldnot be found in a DTCPARMS file.

System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.

User or Operator Response: If a locally defined userID is being used, ensure that a DTCPARMS file:Type.Server entry has been created to define the server.If a reference is being made to a locally defined class,then that class must also be defined in DTCPARMS.

If the server was provided by IBM, ensure that anyrequisite service to VM TCP/IP has been applied andthat all installation steps have been performed.


1009 Server cannot run in a 370-mode virtualmachine

Severity: Error.

Explanation: An attempt was made to start the serverin a 370-mode virtual machine. This configuration isnot supported.


User or Operator Response: Ensure the server has aMACHINE XA or MACHINE XC statement in its VMdirectory entry.


1010 userid is not authorized to issue thecommand command

Severity: Error.

Explanation: The server must be able to issue theindicated CP command, but does not have the correctCP privilege class.


User or Operator Response: Give the server thenecessary privilege class.


1011 Server started at time on date (weekday)Running "program"


Explanation: The server program is starting.




1012 Password validation routine name couldnot be found

Severity: Error.

Explanation: The program specified on the:ESM_Validate. tag in DTCPARMS could not be found.The program must be a relocatable MODULE file.


User or Operator Response: Ensure the tag value iscorrect and that the program is on a disk accessed bythe server. Server profile exits are called with call typeADMIN.


TCPRUN Messages


1013 RACROUTE security manager interfacename could not be found

Severity: Error.

Explanation: The program specified on the:ESM_Racroute. tag in DTCPARMS could not be found.


User or Operator Response: Ensure the tag value iscorrect and that the program is on a disk accessed bythe server.


1014 Server ended normally at time on date(weekday)


Explanation: The server ended with return code zero.

System Action: Processing continues. Server profileexits are called with call type END.



1015 Server ended with RC=rc at time on date(weekday)


Explanation: The server ended with a nonzero returncode.


System Action: Processing continues. Server profileexits are called with call type END.


1016 Attempting to define the requiredminimum of {nnK | nnM} of virtualstorage


Explanation: The current virtual machine size is lessthan the amount specified on the :Memory. tag inDTCPARMS. An attempt will be made to increase theamount of virtual storage.

User or Operator Response: Change the CP directoryentry for this server to specify a default virtual storagesize greater than or equal to the value on the :Memory.tag.

System Action: If the virtual machine is authorized touse the indicated amount of memory, the server will berestarted. Otherwise, server initialization stops.


1017 Filemode fm is nn% full

Severity: Warning.

Explanation: The :Diskwarn. tag has been specified inDTCPARMS and the indicated file mode has reached orexceeded the specified capacity threshold.

User or Operator Response: Be prepared to providemore space, or reduce the space requirements (such asthat used for tracing)



1018 No rexec agents found for userid -anonymous rexec not allowed

Severity: Warning.

Explanation: No DTCPARMS entry with :type.server,:class.rexec_agent, and :for.userid could be found.

System Action: Processing continues. The server willrefuse connections from anonymous rexec clients.

User or Operator Response: If anonymous rexec isdesired, define at least one rexec agent in DTCPARMS.


1019 Server will not be logged off becauseyou are connected


Explanation: When you are logged on to the servervirtual machine, server termination will not perform aCP LOGOFF.




1020 :Exit.name specified in fn ft does notexist

Severity: Error.

Explanation: The indicated server profile exit, nameEXEC, could not be run because it does not exist.


User or Operator Response: Server profile exitsshould be placed on TCPMAINT 198. Alternatively,remove the :Exit. tag from the DTCPARMS file.


TCPRUN Messages


1021 To cancel server startup, type anynon-blank character and press ENTER.To continue startup, just press ENTER

Severity: Response required.

Explanation: This message is displayed whenever aserver is manually started; that is, when started with aconnected virtual console. An option is provided tocancel server initialization.

System Action: If ENTER is pressed without firsttyping a non-blank character, server initialization stops.The execution environment has been established, soyou can start the server manually by entering theserver command name, along with any desiredparameters, at the CMS ready message. Otherwise,initialization continues.

User or Operator Response: Type a non-blankcharacter if desired, and then press ENTER.


1022 Console log will be sent to user userid


Explanation: A server console log will be generatedand sent to the indicated user ID.




1023 Console log has been cancelled


Explanation: A blank :Owner. tag has been specifiedin DTCPARMS.

System Action: Processing continues. No console logis created; any partial console log is purged.



1024 Unable to send console log to user userid


Explanation: userid does not exist or may nototherwise receive spool files from this server.

System Action: Processing continues. The console logwill be sent to the server’s own virtual reader.

User or Operator Response: Specify a valid user id onthe :Owner. tag. in DTCPARMS.


1025 Server program name could not be found

Severity: Error.

Explanation: The command defined on the:Command. tag in DTCPARMS could not be found andthe server could not be started.


User or Operator Response: Ensure the correct disksare accessed and that the server program is available.


1026 fn EXEC {SETUP | BEGIN} returned"data"


Explanation: A server profile exit SETUP or BEGINprocessor has returned DTCPARMS override data.




1027 Server will use TcpipUserid userid


Explanation: The TCPIP DATA file used by this servercontains a TcpipUserid statement specifying a TCP/IPstack user ID other than the default, TCPIP.


User or Operator Response: If userid is correct, thismessage may be suppressed by specifying :Stack.useridin DTCPARMS. If userid is not correct, ensure that thecorrect 592 (TCP/IP client) disk is linked and that thereare no extraneous TCPIP DATA files in the searchorder.


1028 :Stack.userid1 specified in fn ft does notmatch "TcpipUserid userid2" in theTCPIP DATA file

Severity: Error.

Explanation: A stack mismatch has been detected. TheTCPIP DATA file available to this server indicates thatthis server will use userid2 as its TCP/IP server, butDTCPARMS specifies that userid1 is intended.


User or Operator Response: If userid2 is correct,change DTCPARMS to specify :Stack.userid2. If userid2is not correct, ensure that the correct 592 (TCP/IPclient) disk is linked and that there are no extraneousTCPIP DATA files in the search order.

TCPRUN Messages



1029 :tagname option value specified in fn ftfm is not valid

Severity: Error.

Explanation: The indicated option is not valid for thespecified tag.


User or Operator Response: Update the DTCPARMSfile or exit exec to include a valid option and restart theserver. :


1030 The format of the :tag specified in fn ftis not valid. :tagname.value must bespecified before the option.

Severity: Error.

Explanation: The indicated tag does not have a validformat. The option must be specified last on the tag.


User or Operator Response: Update the DTCPARMSfile or exit exec to correct the format of the tag andrestart the server.


1097 Server startup cancelled by fn EXEC,RC=rc


Explanation: A server profile exit (SETUP or BEGINprocessing) returned a nonzero return code, signallingthat the server should not be started.


User or Operator Response: Determine why theserver profile exit returned a nonzero return code and,if necessary, correct the problem and restart the server.In some installations this may be used to prevent theaccidental initialization of certain TCP/IP services.


1098 Server startup cancelled at user request


Explanation: The user at the virtual console entered anon-blank value in response to message DTC1021R.




1099 Server not started - correct problem andretry

Severity: Error.

Explanation: This message is preceded by one or moremessages that indicate the reason the server was notstarted.


User or Operator Response: Correct the indicatedproblem and restart the server.


TCPRUN Messages


TCPRUN Messages


Chapter 22. TFTP Messages

Cannot load translate table@SayFileName(TranslateTableSpec) : ReturnCode

Severity: Warning.

Explanation: Possible user input or system problem.The requested translation table cannot be found.


User or Operator Response: Check the requestedtranslation table file name, and the ReturnCode. Correctyour input and try again.

Source File: TFTP PASCAL


Command Command not known.

Severity: Warning.

Explanation: You input a command that is unknownto TFTP.


User or Operator Response: Examine your input forerrors and resubmit file transfer request.

Source File: TFPARSE PASCAL

Procedure Name: Help

File transfer aborted.

Severity: Warning.

Explanation: The requested file transfer wasunsuccessful.


User or Operator Response: If other messages are notdisplayed, try the file transfer again. If other messagesfollow this message, take appropriate actions.


Procedure Name: TFTP

Invalid option word ignored

Severity: Warning.

Explanation: TFTP did not understand the listedoption you specified.





Missing parm after TRANSLATE

Severity: Warning.

Explanation: You did not specify a TRANSLATEparameter in the TFTP command.





Not Connected

Severity: Warning.

Explanation: You have not established a connectionwith a foreign host. TFTP file transfers are not possiblewith an unconnected system.


User or Operator Response: Check to see if the serveron the foreign host is active. Resubmit your TFTPrequest again with a host name.



TFTP: bad packet count - packet count remains:MaxBlockResent

Severity: Warning.

Explanation: The parameter you specified with theMAXPKT command is not valid.


User or Operator Response: Check the value youspecified with the MAXPKT command and try again.



TFTP: bad rexmit interval - rexmit interval remains:RexmitInterval

Severity: Warning.

Explanation: The parameter you specified with theMAXPKT command is not valid.


User or Operator Response: Check the value you


specified with the MAXPKT command and try again.



TFTP: Host address not known.

Severity: Warning.

Explanation: The requested foreign host address is notin the host ID table.





TFTP: Host Host not known.

Severity: Warning.

Explanation: The requested foreign host name is notin the host ID table.





TFTP: Message

Severity: Error.

Explanation: This informational message precedesTFUTIL messages.



Source File: TFUTIL PASCAL


TFTP: Unknown mode.

Severity: Warning.

Explanation: The transfer mode you specified isunknown to TFTP.


User or Operator Response: Ensure that you specifiedeither ASCII or OCTET mode; these are the only validmodes.



UdpSend: ReturnCode

Severity: Error.

Explanation: This message displays any nonzeroreturn code from the file transfer procedure.




Procedure Name: Dispatch

Unknown tftp command.

Severity: Error.

Explanation: You input an unknown command.


User or Operator Response: Examine your input forerrors and resubmit the command.



WhereBlock Number = BlockNumber

Severity: Error.

Explanation: This message displays the packet in thespecified file where an error caused the file transfer tofail.


User or Operator Response: Use this message todebug your file transfer request.


Procedure Name: PrintPacket

WhereBufsize: bufsize Recfm: recfm

Severity: Error.

Explanation: This message displays the buffer sizeand record format of the file in which the transferfailed.




Procedure Name: PrintFscb

WhereBytecount: bytecount Longpos: longpos

Severity: Error.

Explanation: This message displays whether a valuewas specified for longpos and what that value was.

TFTP Messages






WhereCommand: command Filename: filename Filetype:filetype

Severity: Error.

Explanation: This message displays the file name andfile type of the file in which the transfer failed.





WhereError Code = ErrorCode

Severity: Error.

Explanation: Displays the error code at the time thefile transfer failed.





WhereFilemode: filemode(.1.) filemode(.2.)

Severity: Error.

Explanation: Displays the minidisks that were linkedwhen the file transfer failed.





WhereFlag: flag ShortRecCount: ShortRecCount

Severity: Error.

Explanation: This message displays the value of theShortRecCount parameter.





WhereLongRecCount: LongRecCount

Severity: Error.

Explanation: This message displays the value of theLongRecCount parameter.





WhereShortpos: shortpos

Severity: Error.

Explanation: This message displays the value of theUnsignedHalfWordType parameter.





WhereUnknown packet type

Severity: Error.

Explanation: Trace did not find the block number.





WhereWriteptr: writeptr Readptr: readptr

Severity: Error.

Explanation: Displays the position of the read andwrite pointers at the time the file transfer failed.





TFTP Messages

Chapter 22. TFTP Messages 379

TFTP Messages


Chapter 23. TFTPD Messages

This section contains TFTPD messages. Follow the User response, as appropriatewithin each message area, to resolve the problem.

Creation path was specified as a relative path.Absolute path name will be determined as eachrequest is handled.


Explanation: The creation path was specified as arelative path instead of an absolute path. Relative pathsrequire that the absolute path be determined byappending the relative path name to the currentworking directory.

System Action: The server constructs the absolutepath name when each write or read request begins.


Source File: TFTCMD PLX

Option option requires a value.

Severity: Error.

Explanation: An option keyword was specifiedwithout the required option value.


User or Operator Response: Reissue the TFTPDcommand with the option value included.


Pathname specified for CREATION is not valid

Severity: Error.

Explanation: The pathname specified with theCREATION option is not valid. This problem can becaused by specifying:

the pathname as a fully qualified Byte File Systempathname,a pathname that does not exist,a pathname that the server is not permitted toaccess.

System Action: The command or subcommand ends.

User or Operator Response: Reissue the command orsubcommand with the pathname specified correctly.

Source File: TFTCMD PLX and TFTCON PLX

RC=rc RE=re opening file

Severity: Error.

Explanation: An unexpected return code and reason

code was encountered when attempting to open theindicated file.

System Action: The command or subcommand ends.

User or Operator Response: See z/VM: CMS CallableServices Reference for information on the possible returncodes and reason codes. Correct the cause of the errorand reissue the command or subcommand.

Source File: TFTHLP PLX, TFTPFL PLX, and TFTUIDPLX

RC=rc starting APPLDATA monitoring


Explanation: APPLDATA monitoring was not begunbecause of the indicated return code. This is normal ifyou have not set up the server to collect APPLDATAinformation.

System Action: The server comes up.

User or Operator Response: See z/VM: CPProgramming Services for more information onDIAGNOSE X'DC'.

Source File: TFTINI PLX

Syntax: CREATION NO or pathname


Explanation: The CREATION subcommand wasspecified with an incorrect number of operands.

System Action: The subcommand ends.

User or Operator Response: Reissue the subcommandwith the correct number of subcommands.

Source File: TFTCON PLX

Syntax: DROPFILE pathname

Severity: Error.

Explanation: The DROPFILE subcommand wasspecified with an incorrect number of operands orincorrect operands.

System Action: The DROPFILE subcommand ends.

User or Operator Response: Reissue the DROPFILEsubcommand with the operand specified correctly.



Syntax: subcommand

Severity: Error.

Explanation: The indicated subcommand wasspecified with additional operands. The subcommandshould have no operands.


User or Operator Response: Reissue the subcommandwithout specifying operands.


Syntax: XFERMODE OCTET or RESPECT


Explanation: An incorrect number of operands or anincorrect operand was specified on the XFERMODEsubcommand.


User or Operator Response: Reissue the XFERMODEsubcommand with the operands specified correctly.


Unrecognized operand operand -- continuing

Severity: Error.

Explanation: An unrecognized operand wasencountered on the TFTPD command line.


User or Operator Response: Reissue the TFTPDcommand with the operands specified correctly.


Unrecognized option option - continuing

Severity: Error.

Explanation: An option was entered on the commandline that was not recognized.

System Action: The server comes up and the option isignored.

User or Operator Response: Reissue the TFTPDcommand with the option specified correctly.


Unrecognized port number.

Severity: Error.

Explanation: An invalid port number was specified.


User or Operator Response: Reissue the TFTPDcommand with the port number specified correctly.


Unrecognized value for option operand

Severity: Error.

Explanation: The value specified for the indicatedoption is not valid.

System Action: The TFTPD server ends.

User or Operator Response: Reissue the TFTPDcommand with the option value specified correctly


TFTPD Messages


Chapter 24. UFTD Messages

This chapter contains UFTD messages. Follow the User Response, as appropriate,within each message area to resolve the problem.

UFT1200E Code level mis-match: expected level1but found level2

Explanation: The UFT protocol version level specifiedin the UFTD EXEC and GLOBALV group UFTD doesnot match the level specified in UFTD REXX. There isprobably an install or build problem that has causeddifferent server or release levels of UFTD to be presenton your system.


User or Operator Response: Correct the levelmismatch and restart UFTD.

Source File: UFTD EXEC

UFT8387E Missing value for statement statement

Explanation: A value required on the UFTDconfiguration file statement is missing.


User or Operator Response: Correct the configurationfile statement and restart UFTD.

Source File: TCPSHELI EXEC

UFT8388E Invalid statement: statement

Explanation: The UFTD configuration file statement isunknown or incorrect.




UFT8389E Invalid operand: operand

Explanation: An invalid operand was encounteredwhen this command was entered.

System Action: The command is not executed, serveroperation continues.

User or Operator Response: Correct the operand andenter the command again.

Source File: TCPSHELL EXEC

UFT8390E Invalid value value for statementstatement

Explanation: The UFTD configuration file statementcontains an incorrect value.




UFT8391E Missing keyword: keyword for statementstatement

Explanation: The UFTD configuration file statement ismissing a required keyword.




UFT8560I This UFTD server is not defined inTCPIP DATA

Explanation: The TCPIP DATA file that is the highestin the file mode search order for the UFTD server doesnot contain a UFTSERVERID statement with this UFTDserver’s user ID.

System Action: Server operation continues.

User or Operator Response: Add the necessaryUFTSERVERID statement to the TCPIP DATA file. Thiswill allow CMS productivity aids such as RDRLIST andRECEIVE to see files originated by UFTD as networkserver files. This will then allow the productivity aidsto present true file origin information to CMS users.

Source File: UFTD EXEC

UFT8564E CONFIGURATION file: filename filetypenot found

Explanation: The UFTD configuration file UFTDCONFIG was not found on any available file mode.


User or Operator Response: Locate or create theUFTD CONFIG file and make it available on a UFTDserver visible file mode.


Source File: TCHSHELI EXEC

UFT8564E TRANSLATE file: filename filetype notfound

Explanation: The translation file’s file name and filetype specified by the TRANSLATE statement in theUFTD configuration file was not found on anyavailable file mode.


User or Operator Response: Correct the configurationfile TRANSLATE statement and restart UFTD.

Source File: TCHSHELI EXEC

UFT8565E Error from command command RC=rc

Explanation: The specified CP or CMS commandissued internally by the UFTD server failed withunexpected return code.

System Action: The server continues operation.

User or Operator Response: Determine why thenamed command failed using the z/VM: CMS Commandand Utility Reference or the z/VM: CP Command andUtility Reference for more information and correct theproblem.

Source File: TCPSHELL EXEC, TCPSHELI EXEC,UFTD EXEC and UFTD REXX

UFT8566E User exit filename EXEC not found

Explanation: The user exit file name specified on theUFTD configuration file statement or entered from theconsole as an UFTD command was not found on anyUFTD visible file space.

System Action: When the failure occurs on an UFTDconfiguration file statement, the server shuts down.When the failure occurs from an UFTD command, thecommand is not executed and the server continuesoperation.

User or Operator Response: If the exec was enteredincorrectly on an UFTD configuration statement, correctthe statement and restart the server. If it was enteredincorrectly on an UFTD command, correct the file nameand enter the command again. If it was enteredcorrectly, make sure the file has a file type of EXEC andthat it is available on UFTD visible file space, and tryagain.

Source File: TCPSHELL EXEC and TCPSHELI EXEC

UFT8567E Unexpected return from user exitfilename EXEC, RC=rc

Explanation: A system administrator-supplied UFTDexit exec has returned a return code that is not definedas a valid return code.

System Action: Server processing continues and theexit remains enabled.

User or Operator Response: Correct the exit exec andre-enable the exit. While the exec is being corrected,you may want to disable the exit, see the NSLOOKUPand UFTCMDS commands in the TCP/IP Planning andCustomization manual.

Source File: TCPSHELL EXEC and UFTD REXX

UFT8568E Unknown UFTD command

Explanation: A command has been entered from theUFTD console which is unknown both to UFTD’scommand processor and to CMS.

System Action: The command is not executed andserver processing continues.

User or Operator Response: Correct the commandand enter it again.


UFT8569E Unable to establish the Event MonitorEnvironment

Explanation: An error prevented the enablement ofthe event monitor environment.


User or Operator Response: IPL CMS and restart theserver.


UFT8570I exit-type exit name has turned off exit-typefunction

Explanation: A system administrator-suppliedNSLOOKUP exit or UFTCMDS exit has exited with areturn code indicating the exit function should beturned off.

System Action: UFTD continues normal operation, butthe exit is no longer called.

User or Operator Response: Inform the administrator,and determine what condition(s) might cause the execto request the exit be turned off. Correct that conditionand reactivate the exit as desired.

Source File: UFTD REXX

UFT9002I File (*UFT) spooled to userid1 -- origindomain(userid2) date time timezone

Explanation: A file has been successfully receivedfrom one user ID at the specified domain and spooledto another user ID on the local system.

System Action: Operation continues.


UFTD Messages


Source File: UFTD REXX

UFTD Messages

Chapter 24. UFTD Messages 385

UFTD Messages


Chapter 25. X.25 Messages

X25IPIC -- Prior command pending

Severity: Warning.

Explanation: An attempt to post a command to a taskfailed because a previous command is active. When theprevious command completes, the command can bereissued.


User or Operator Response: Wait for the previouscommand to complete, and reissue the command.

Source File: xnx25cmd assemble

Procedure Name: None.

X25IPIC -- Program name must be specified

Severity: Error.

Explanation: An entry point name for the interfacetask to be started was not specified.

System Action: The START command is ignored.

User or Operator Response: Reissue the STARTcommand including the entry point name.



X25IPIC -- Task has not been started

Severity: Error.

Explanation: An attempt to send a command to a taskfailed or an attempt to cancel a task failed. In eithercase, the failure occurred because the specified task isnot active.


User or Operator Response: Issue the STARTcommand before other commands.



X25IPIC -- Task has terminated, user=usersystem=system

Severity: Fatal.

Explanation: An attempt to post a command to a taskfailed, because the task had terminated. The taskcompletion codes are reported.


User or Operator Response: The task must berestarted.

System Programmer Response: Use the completioncodes to determine the cause of termination.



X25IPIC -- Task is already started

Severity: Error.

Explanation: This interface task is still active; anothertask cannot run until the current task terminates.


User or Operator Response: Terminate the previoustask before starting a new one.



X25IPI099T WTO text overflow

Explanation: XNX25IPI encountered an overflow inthe Write To Operator (WTO) area, which is used todisplay informational and error messages.

System Action: The program abends with an ABENDX'099' message.


System Programmer Response: Determine the causeof the overflow and submit the ABEND dump to theIBM Support Center.

X25IPI911W Refusing IUCV connection

Explanation: XNX25IPI is refusing an IUCVconnection, because the caller does not have the correctuser ID or is already connected.

System Action: The IUCV connection is refused.


System Programmer Response: Verify the TCPIP userID entry in the TCPIP DATA file, and check that only asingle X25NPSI device is defined in the PROFILETCPIP file with the user ID of this X25IPI virtualmachine or address space.


X25IPI921I Logon exit refusing session

Explanation: XNX25IPI is refusing a logon sessionbecause:

v The logon was not initiated by X.25 NPSI

v For an MCH with LOGAPPL coded, the MCH is notdefined by a LINK entry, or the MCH is not in astate where a logon is expected

v A virtual circuit is not in a state where a logon isexpected, possibly because a call request wasunsuccessful.

System Action: The NPSI LU session logon is refused.

User or Operator Response: Notify the systemprogrammer if the message is issued frequently, andconnections are failing.

System Programmer Response: Check the source ofthe logons; determine the reason for the call requestfailure.

X25IPI931E Network services exit: Unrecognizedrequest type

Explanation: XNX25IPI received an unrecognizedNetwork Services RU from VTAM. The supported RUare:v Cleanup Session (X'810629')v NS Procedure Error (X'010604')v Notify (X'810620')

System Action: VTAM is notified that the NS RU wasnot handled.


System Programmer Response: Obtain a VTAM traceto determine the Network Services RU type.

X25IPI932I Network services exit: Cleanup sessionnotification posted

Explanation: A VTAM Cleanup Session RU wasreceived.

System Action: The VTAM session is terminated.

User or Operator Response: None. A failure messagefor the MCH or virtual circuit (VC) session follows.

X25IPI933W Network services exit: Session initiationfailure notification posted

Explanation: A VTAM Session initiation failure RUwas received.

System Action: The VTAM session is terminated.

User or Operator Response: None. A failure messagefor the MCH or VC session can follow.

X25IPI941T Session control exit: Unrecognized orunexpected request type

Explanation: An unexpected VTAM Session ControlRU was received.

System Action: X25IPI abends with an ABEND X'941'message.


System Programmer Response: Determine the sourceof VTAM session control request. Submit the ABENDdump to the IBM Support Center.

X25IPI942I Session control exit: UNBINDnotification posted

Explanation: A VTAM Session Control RU of typeUNBIND was received.

System Action: The VTAM session is terminated. Afailure message for the MCH or VC session can follow.


X25IPI981E VTAM terminating, reason unknown

Explanation: A VTAM Shutdown notification wasreceived. The cause is unknown. This rules out astandard shutdown, HALT QUICK, INACT, or HALTCANCEL reason codes.

System Action: X25IPI terminates.


System Programmer Response: Determine the sourceof the Shutdown notification.

X25IPI982I VTAM HALT issued, drain flag set

Explanation: A VTAM HALT request was issued.

System Action: X25IPI terminates after currentconnections are closed; new connections are refused.

User or Operator Response: Restart X25IPI, ifappropriate, after VTAM resumes.

X25IPI988I VTAM HALT QUICK or VARY INACT,application issued

Explanation: A VTAM HALT QUICK or VARY INACTrequest was issued.



X.25 Messages


X25IPI989I VTAM HALT CANCEL issued

Explanation: A VTAM HALT CANCEL request wasissued.



X25IPI002E Unrecognized command: command

Explanation: X25IPI encountered an unrecognizedcommand in the console input.


User or Operator Response: Enter the desiredcommand correctly. See the TCP/IP Planning andCustomization for the X25IPI command syntax.

X25IPI003R program name {VM} update level level

Explanation: The version of X25IPI currently runninghas the indicated program name (usually X25IPI) andthe indicated update level.



System Programmer Response: Use the update levelwhen reporting problems.

X25IPI011R IP VM userid state state

Explanation: The IUCV connection between theX25IPI and the TCPIP virtual machines has theindicated status. In status fields, bit 1 indicates anIUCV connection pending and bit 0 indicates an IUCVconnection complete.



System Programmer Response: Use the status inproblem determination.

X25IPI011R MCH lu state link_state session_state

Explanation: X25IPI status for the indicated MCH isdisplayed. Link_state fields are:

Field DescriptionX'00' Restart neededX'10' ReadyX'20' Restart request sentX'30' Restart indication received

VTAM session_state fields are:

Field DescriptionX'20' Enabled for LOGAPPL logonX'30' logon pendingX'40' Opening

X'50' Open (ready)X'60' ClosingX'70' Failed




X25IPI011R VC vc LU lu DTE address state call_statesession_state

Explanation: X25IPI status for the indicated virtualcircuit is displayed. The call_state fields are:

Field DescriptionX'00' Waiting for restart on MCHX'10' Available for connectionsX'20' Call request sentX'30' Call request receivedX'40' Ready for data transferX'41' Reset request sentX'42' Reset request receivedX'43' Interrupt request sentX'44' Interrupt request receivedX'50' Call collisionX'60' Clear request sentX'70' Clear request received

The VTAM session_state fields are:

Field DescriptionX'00' Disabled until restart on MCHX'10' Available for connectionsX'20' Enabled for NPSI LU logonX'30' Logon pendingX'40' OpeningX'50' Open (ready)X'60' ClosingX'70' Failed




X25IPI012R MCH lu SDA at address

Explanation: The contents of the session data area(SDA) for this MCH are dumped.



System Programmer Response: Use the data forproblem determination.

X.25 Messages

Chapter 25. X.25 Messages 389

X25IPI012R VC vc SDA at address

Explanation: The contents of the session data area(SDA) for this VC are dumped.




X25IPI013R MCH lu RC: name IP: name SN: name TX:name

Explanation: In response to an EVENTS command,the internal subroutine names handling eventsassociated with this MCH are displayed.

Subroutine DescriptionRC VTAM request completeIP VTAM input pendingSN VTAM session notificationTX Timer expiry




X25IPI013R VC vc RC: name IP: name SN: name TX:name

Explanation: In response to an EVENTS command,the internal subroutine names handling eventsassociated with this virtual circuit is displayed.

Subroutine DescriptionRC VTAM request completeIP VTAM input pendingSN VTAM session notificationTX Timer expiry




X25IPI014R MCH lu

Explanation: The following X25IPI014R VC messagesapply to virtual circuits on this MCH.



X25IPI014R VC vc DTE_address S send_count Rreceive_count D drop_count Q queue_size

Explanation: The traffic counts for this virtual circuitare displayed.



X25IPI014R IP VM user_id S send_count Rreceive_count D drop_count Q queue_size

Explanation: The traffic counts on the IUCVconnection to the TCPIP virtual machine are displayed.



X25IPI021R MCH lu restarting

Explanation: X25IPI is restarting this MCH, inresponse to a RESTART command.

System Action: A VTAM session is initiated for theNPSI MCH LU.


X25IPI022E MCH lu unavailable

Explanation: X25IPI could not restart this MCH,because it is unavailable for logon.

System Action: The MCH session is left available forinitiation by LOGAPPL.

User or Operator Response: Activate the MCH LUthrough VTAM.

System Programmer Response: Determine the reasonwhy VTAM refused session initiation.

X25IPI023E MCH lu already started

Explanation: X25IPI could not restart this MCH,because it is already active.



X25IPI031E MCH mch unknown

Explanation: An attempt was made to send a callrequest for an unknown MCH.

System Action: The request is ignored.

User or Operator Response: Determine the correctMCH name and reissue the CERTCALL command. TheCERTCALL command is refused.

X25IPI077E Posted ECB at address had no handler

Explanation: The X25IPI event control block at thisaddress did not specify an event handler routine.



X.25 Messages


System Programmer Response: If the error recurs,obtain a dump of the X25IPI virtual machine.

X25IPI085I HALT notice accepted type type

Explanation: X25IPI received a VTAM HALTnotification or a HALT console command and isshutting down execution.

System Action: VTAM LU sessions are closed, and theIUCV connection to the TCPIP virtual machine issevered.


X25IPI088I Terminating

Explanation: X25IPI is terminating its execution andshutting down.

System Action: The VTAM ACB is closed.


X25IPI090I Ended

Explanation: X25IPI has finished execution.

System Action: The X25IPI program exits.


X25IPI091T Stack overflow at frame address

Explanation: X25IPI encountered a stack overflow atthe indicated address.

System Action: X25IPI abends with an ABEND X'091'message.


System Programmer Response: Determine the causeof overflow and submit the ABEND dump to the IBMSupport Center.

X25IPI092T Buffer released twice at address in routine(address)

Explanation: X25IPI encountered a consistency errorin its buffer allocation pool. A buffer was releasedtwice. This indicates a programming error.

System Action: X25IPI abends with return code X'92'.


System Programmer Response: Determine the causeof the consistency failure and submit the ABEND dumpto the IBM Support Center.

X25IPI093S NPSI SEND completion, pending packet= packet number

Explanation: A program flag indicating a deferredcontrol packet to be sent has an unacceptable value.

System Action: The pending condition is reset.



X25IPI101E Unable to open configuration file,DDNAME=X25IPI

Explanation: X25IPI encountered an error opening itsconfiguration file.

System Action: X25IPI does not start.


System Programmer Response: Correct the FILEDEFor DD for the X25IPI configuration file.

X25IPI102E Unrecognized configuration entry:keyword

Explanation: X25IPI encountered an unrecognizedentry in its configuration file. This configuration recordis skipped and X25IPI continues with the next entry.

System Action: The configuration record is skipped;further configuration errors can result.


System Programmer Response: Correct the entry inthe X25IPI CONFIG file.

X25IPI103E Missing configuration entry: LINK

Explanation: X25IPI could not find a Link entry in itsconfiguration file. You must have at least one Linkentry defining a NPSI MCH in the file.



System Programmer Response: Add a Link definitionto the configuration file for each NPSI MCH to be usedfor TCP/IP traffic.

X25IPI103E Missing configuration entry: VTAM

Explanation: X25IPI could not find a VTAM entry inits configuration file. You must have one VTAM entryto specify the VTAM application ID and password.


X.25 Messages



System Programmer Response: Add a Link definitionto the configuration file for each NPSI MCH to be usedfor TCP/IP traffic.

X25IPI104E Buffer storage not available (count bytesrequired)

Explanation: X25IPI could not allocate sufficientstorage during initialization.



System Programmer Response: Increase the X25IPIregion or virtual machine memory size by cnt bytes.

X25IPI106I Unable to open TCPIP DATA file,DDNAME=X25IPITD; default TCPIPuserid used

Explanation: X25IPI encountered an error opening theTCPIP DATA file; X25IPI uses the default TCPIP userID.

System Action: The user ID of the TCPIP virtualmachine defaults to TCPIP.

User or Operator Response: If TCP connectionscannot be made, notify the system programmer.

System Programmer Response: If the user ID of theTCPIP virtual machine is not TCPIP, define a FILEDEFor DD for X25IPITD referencing the TCPIP DATA file.

X25IPI108E IUCV Declare program X25IPI failedR15=value

Explanation: X25IPI encountered an error issuing aGCS IUCVINI SET macro.



System Programmer Response: Check the VM userdirectory entry for the X25IPI virtual machine.

X25IPI109T Programming error: not enough buffersallocated

Explanation: The calculation of the number of buffersto allocate was incorrect.



System Programmer Response: Notify the IBMSupport Center.

X25IPI111E Unrecognized trace level: level

Explanation: The trace level specified in the X25IPICONFIG file, or on the TRACE command is not correct.

System Action: The trace level is set to off.

User or Operator Response: Reissue the TRACEcommand with valid trace level.

System Programmer Response: Correct the Traceentry in the configuration file.

X25IPI201I VTAM ACB application openedsuccessfully

Explanation: X25IPI successfully opened the VTAMACB.



X25IPI121E Repeated VTAM record ignored: record

Explanation: X25IPI encountered more than oneVTAM entry in the configuration file.

System Action: The repeat VTAM record is skipped;initialization continues.


System Programmer Response: Remove the repeatVTAM record.

X25IPI122E VTAM application name missing

Explanation: The VTAM application ID is missing onthe VTAM entry in the configuration file.



System Programmer Response: Specify the VTAMapplication ID and password on the VTAM entry.

X25IPI123E VTAM application password missing

Explanation: The VTAM application password ismissing on the VTAM entry in the configuration file.



System Programmer Response: Specify the VTAMapplication password on the VTAM entry.

X.25 Messages


X25IPI129E VTAM ACB application open failed

Explanation: X25IPI encountered an error opening theVTAM ACB. This message is preceded by a X25IPI201Eor X25IPI202E message reporting the VTAM error code.


User or Operator Response: Activate the X25IPIapplication in VTAM.

System Programmer Response: Use the VTAM errorcode from the X25IPI201E or X25IPI202E message todetermine the reason for the failure of the VTAM ACBOPEN macro.

X25IPI131E DDN and non-DDN links cannot bemixed

Explanation: X25IPI encountered Link statements inits configuration file specifying both DDN andnon-DDN links.

System Action: The Link entry is discarded; furthererrors can result.


System Programmer Response: DDN and non-DDNlinks must be segregated into two X25IPI virtualmachines.

X25IPI132E Link LU name missing

Explanation: The NPSI MCH LU name is missing onthe Link entry in the configuration file.



System Programmer Response: Complete the Linkentry. See TCP/IP Planning and Customization for theformat of the Link definition.

X25IPI133E Link DTE address missing

Explanation: X25IPI encountered a Link statementwithout a DTE address specified. This field is requiredfor all non-DDN links.




X25IPI134E Link window size missing or notnumeric

Explanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericdefault window size specification.



System Programmer Response: Correct the windowsize. See TCP/IP Planning and Customization for theformat of the Link definition.

X25IPI135E Link window size not in range 1..7 or1..127

Explanation: X25IPI encountered a Link statement inits configuration file with an invalid default windowsize specification. The window size must be in therange 1—7 or 1—127.



System Programmer Response: Correct the windowsize.

X25IPI136E Link packet size missing or not numeric

Explanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericdefault packet size.



System Programmer Response: Correct the packetsize. See TCP/IP Planning and Customization for theformat of the Link definition.

X25IPI137E Link packet size unacceptable

Explanation: X25IPI encountered a Link statement inits configuration file with an invalid default packet sizespecification. The size must be 32, 64, 128, 256, 512,1024, 2048, or 4096.



System Programmer Response: Correct the packetsize.

X.25 Messages


X25IPI138E Link logical channel count missing ornot numeric

Explanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericlogical channel count field.



System Programmer Response: Correct the channelcount. See TCP/IP Planning and Customization for theformat of the Link definition.

X25IPI139E Link logical channel count not in range1..1023

Explanation: X25IPI encountered a Link statement inits configuration file with an invalid logical channelcount field. The count must be in the range 1—1023.



System Programmer Response: Correct the channelcount.

X25IPI140E Link reserved channel count missing ornot numeric

Explanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericreserved channel count.



System Programmer Response: Correct the reservedchannel count. See TCP/IP Planning and Customizationfor the format of the Link definition.

X25IPI141E Link reserved channel count not inrange 1..LCC

Explanation: X25IPI encountered a Link statement inits configuration file with an invalid reserved channelcount. The count must be in the range 1—number oflogical channels that have been defined.



System Programmer Response: Correct the reservedchannel count. See TCP/IP Planning and Customization

for the format of the Link definition.

X25IPI142E Link data network code missing

Explanation: X25IPI encountered a Link statement inits configuration file that omitted a data networkidentifier code (DNIC). DNICs must be specified for allnetworks (use DDN for DDN nets).




X25IPI143E Data network identifier code notdecimal

Explanation: X25IPI encountered a Link statement inits configuration file that specified a nondecimal datanetwork identifier code (DNIC). The DNIC must bedecimal.



System Programmer Response: Correct the DNICnumber. See TCP/IP Planning and Customization for theformat of the Link definition.

X25IPI144E Link DTE address not decimal

Explanation: X25IPI encountered a Link statement inits configuration file that contained a nondecimal DTEaddress.



System Programmer Response: Correct the DTEaddress.

X25IPI151E Dest record not preceded by Link record

Explanation: X25IPI encountered a Dest record in itsconfiguration file before any Link record. The Destrecord must follow the corresponding Link record inthe configuration file.

System Action: The Dest entry is skipped.


System Programmer Response: Move the Dest recordafter the corresponding Link record.

X.25 Messages


X25IPI152E Dest IP address missing

Explanation: X25IPI encountered a Dest record in itsconfiguration file that did not specify an IP address.

System Action: The Dest entry is discarded.


System Programmer Response: Complete the Destentry. See TCP/IP Planning and Customization for theformat of the Dest record.

X25IPI153E Dest IP address must be decimal

Explanation: X25IPI encountered a Dest record in itsconfiguration file specifying a nondecimal destinationaddress. The destination address must be indotted-decimal form.



System Programmer Response: Correct the IPaddress. See TCP/IP Planning and Customization for theformat of the Dest record.

X25IPI154E Dest DTE address missing

Explanation: X25IPI encountered a Dest record in itsconfiguration file, which omitted the destination X.25DTE address specification. The destination X.25 DTEaddress specification is required on non-DDNnetworks.



System Programmer Response: Complete the Destrecord with the X.25 DTE address. See TCP/IP Planningand Customization for the format of the Dest record.

X25IPI155E Dest DTE address must be decimal

Explanation: X25IPI encountered a Dest record in itsconfiguration file that had a nondecimal destinationX.25 DTE address specified. The destination X.25 DTEaddress must be decimal.



System Programmer Response: Correct the DTEaddress.

X25IPI156E Dest call user data must be hexadecimal

Explanation: X25IPI encountered a Dest record in itsconfiguration file specifying nonhexadecimal call userdata (CUD) protocol ID. The CUD must behexadecimal.



System Programmer Response: Correct the call userdata.

X25IPI161E Datagram size limit missing or notnumeric

Explanation: X25IPI encountered a Buffers record inits configuration file that had a missing or nonnumericbuffer size specification.

System Action: The Buffers record is ignored; thedefault values are applied.


System Programmer Response: Complete the Buffersrecord with the datagram size limit. See TCP/IPPlanning and Customization for the format of the Destrecord.

X25IPI162E Datagram size limit not in range576...2048

Explanation: X25IPI encountered a Buffers record inits configuration file with an invalid buffer sizespecification. The buffer size must be in the range 576— 2048.

System Action: The Buffers record is ignored; thedefault values are applied.


System Programmer Response: Correct the datagramsize limit.

X25IPI163E Extra buffer count missing or notnumeric

Explanation: X25IPI encountered a Buffers record inits configuration file that had a missing or nonnumericbuffer count field.

System Action: The extra buffer count is ignored.


System Programmer Response: Correct the buffercount.

X.25 Messages


X25IPI164E VC send queue limit missing or notnumeric

Explanation: X25IPI encountered a Buffers record inits configuration file that had a missing or nonnumericsend queue limit.

System Action: The send queue limit defaults to 8.


System Programmer Response: Correct the queuelimit.

X25IPI171E Inactivity timeout missing or notnumeric

Explanation: X25IPI encountered a Timers record in itsconfiguration file that had a missing or nonnumericinactivity time-out value.

System Action: The Timers record is ignored; thedefault values are applied.


System Programmer Response: Complete the Timersrecord with the inactivity time-out. See TCP/IP Planningand Customization for the format of the Dest record.

X25IPI172E Minimum call timer missing or notnumeric

Explanation: X25IPI encountered a Timer record in itsconfiguration file that had a missing or nonnumericminimum time field. This Timer record is ignored.

System Action: The minimum call time defaults to 60seconds.


System Programmer Response: Correct the minimumcall time.

X25IPI181E Options record not preceded by Linkrecord

Explanation: X25IPI encountered an Options record inits configuration file before any Link record. TheOptions record must follow the associated Link record.

System Action: The Options record is ignored.


System Programmer Response: Move the Optionsrecord after the corresponding Link record.

X25IPI182E Option name not recognized name

Explanation: X25IPI encountered an Options record inits configuration file with an unrecognized optionname.

System Action: The remainder of the Options recordis skipped.


System Programmer Response: Correct the optionname. See TCP/IP Planning and Customization for theformat of the Options record.

X25IPI183E Option packet size missing or notnumeric

Explanation: X25IPI has encountered an Optionsstatement in its configuration file that has a missing ornonnumeric packet size specification.




X25IPI184E Option packet size unacceptable

Explanation: X25IPI encountered an Options record inits configuration file that specified an unacceptablepacket size. The size must be 32, 64, 128, 256, 512, 1024,2048, or 4096.




X25IPI185E Option window size missing or notnumeric

Explanation: XNX25IPI encountered an Optionsstatement in its configuration file that had a missing ornonnumeric window size.




X.25 Messages


X25IPI186E Option window size not in range 1..7 or1..127

Explanation: XNX25IPI encountered an Optionsstatement in its configuration file that specified aninvalid window size. The window size must be in therange 1—7 or 1—127.




X25IPI201E VTAM GENCB failed, R15=valueR0=value

Explanation: A VTAM GENCB call failed, with theindicated R15 and R0 values.



System Programmer Response: Reassemble X25IPIwith the most recent VTAM macro library.

X25IPI202E VTAM ACB OPEN failed, R15=valueACBERFLG=value

Explanation: A VTAM OPEN request failed, with theindicated R15 and ACBERFLG values.


User or Operator Response: Activate the X25IPIapplication in VTAM.

System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB OPEN macro.

X25IPI215E VTAM SETLOGON QUIESCE failed,RTNCD=value FDB2=value

Explanation: A VTAM SETLOGON QUIESCE requestfailed with the indicated return code and FDB2 values.

System Action: X25IPI termination continues.


System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM SETLOGON macro.

X25IPI221E VTAM ACB CLOSE failed, R15=valueACBERFLG=value

Explanation: A VTAM CLOSE request failed with theindicated return values.

System Action: X25IPI termination continues.


System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM CLOSE macro.

X25IPI241E VTAM CLSDST RELEASE lu failed,RTNCD=value FDB2=value

Explanation: A VTAM CLSDST RELEASE failed withthe indicated return code and FDB2 values.

System Action: Execution continues. The virtualcircuit can become unusable.


System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM CLSDST macro. Determine the state of the NPSILU using the VTAM DISPLAY command. HALT andrestart the X25IPI application, if all virtual circuitsbecome unusable.

X25IPI241E VTAM OPNDST ACCEPT lu failed,RTNCD=value FDB2=value

Explanation: A VTAM OPNDST ACCEPT failed withthe indicated return code and FDB2 values.

System Action: Execution continues. The virtualcircuit can become unusable.


System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM OPNDST macro. Determine the state of theNPSI LU using the VTAM DISPLAY command. HALTand restart the X25IPI application, if all virtual circuitsbecome unusable.

X25IPI241E VTAM OPNDST ACQUIRE lu failed,RTNCD=value FDB2=value

Explanation: A VTAM OPNDST ACQUIRE failed for aNPSI MCH LU, with the indicated return code andFDB2 values.

System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for

User or Operator Response: Activate the NPSI MCHin VTAM. Use the X25IPI RESTART command toreacquire the MCH LU.

X.25 Messages


System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB OPNDST macro. manual restart.

X25IPI241E VTAM RECEIVE lu failed,RTNCD=value FDB2=value

Explanation: A VTAM RECEIVE failed with theindicated return code and FDB2 values.

System Action: If the error occurred on a NPSI MCHsession, the MCH is shut down. If the error occurredon a VC session, the connection is closed.

User or Operator Response: If the error occurred on aNPSI MCH session, activate the NPSI MCH in VTAMand use the X25IPI RESTART command to reacquirethe MCH.

System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB RECEIVE macro.

X25IPI241E VTAM SEND lu failed, FDB2=value

Explanation: A VTAM SEND REQ failed with theindicated FDB2 value.



System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB SEND macro.

X25IPI241E VTAM SEND RESP EX lu failed,RNTCD=value FDB2=value

Explanation: A VTAM SEND RESP EX failed with theindicated return code and FDB2 values.




X25IPI241E VTAM SEND RESP NEX lu failed,RTNCD=value FDB2=value

Explanation: A VTAM SEND RESP NEX failed withthe indicated return code and FDB2 values.




X25IPI255E VTAM request failed for lu REQ=requestRNTCD=value FDB2=value sense=value(caller)

Explanation: The indicated VTAM request failed, withthe indicated return code, FDB2, and sense values. Thecaller field specifies the routine that issued the request.The request codes are:

Request Code DescriptionX'17' OPNDSTX'1F' CLSDSTX'22' SENDX'23' RECEIVE



System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB OPEN macro.

X25IPI313I MCH lu restarting

Explanation: An X.25 restart exchange has beenstarted on the NPSI MCH.



X25IPI315E MCH lu open failed

Explanation: X25IPI encountered an error opening theindicated NPSI MCH. This message is preceded by aX25IPI241E or X25IPI255E message reporting a VTAMerror code.

System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for manual restart.

X.25 Messages


User or Operator Response: Activate the NPSI MCHin VTAM and use the X25IPI RESTART command toreacquire the MCH.

System Programmer Response: Use the VTAM errorcode from the X25IPI241E or X25IPI255E message todetermine the reason for the failure of the MCHOPNDST.

X25IPI316E MCH lu OPNDST did not complete

Explanation: An VTAM OPNDST request on a NPSIMCH LU was posted complete, but the NIB is notmarked open. The contents of the session data area(SDA) for this MCH are dumped.


User or Operator Response: Activate the NPSI MCHin VTAM and use the X25IPI RESTART command toreacquire the MCH.

System Programmer Response: Determine the state ofthe NPSI MCH LU using the VTAM DISPLAYcommand.

X25IPI320I MCH lu packet level ready

Explanation: X25IPI has initialized this MCH forconnections.



X25IPI322I MCH lu discarded packet during restart

Explanation: X25IPI received an invalid packet whilerestarting this MCH.

System Action: The invalid packet is dumped anddiscarded.


X25IPI323I MCH lu restart indication, cause=valuediagnostic=value

Explanation: X25IPI received an X.25 restart indicationfor this MCH during the restart procedure, with theindicated cause and diagnostic bytes. The X.25 networkinterface has been reinitialized. See X.25 NetworkControl Program Packet Switching Interface Diagnosis,Customization, and Tuning Version 3 for a list of X.25cause and diagnostic codes. See the provider of theX.25 network service for documentation that listsadditional diagnostic codes.

System Action: Virtual circuit connections on theMCH are closed, and the X.25

User or Operator Response: None. restart procedureis used to place the MCH back in operation.

X25IPI324I MCH lu restart confirmation

Explanation: X25IPI received a restart confirmation forthis MCH.

System Action: The MCH is marked ready for newconnections.


X25IPI330I MCH lu restart complete

Explanation: X25IPI has completed terminating virtualcircuits on an MCH undergoing restart.

System Action: An X.25 restart confirmation is sent tocomplete the restart procedure.


X25IPI331I MCH lu restart indication, cause=cause,diagnostic=diagnostic

Explanation: X25IPI received a restart indication onthis MCH, with the indicated cause and diagnosticbytes. The X.25 network interface has been reinitialized.See X.25 Network Control Program Packet SwitchingInterface Diagnosis, Customization, and Tuning Version 3for a list of X.25 cause and diagnostic codes. See theprovider of the X.25 network service for documentationthat lists additional diagnostic codes.

System Action: Virtual circuit connections on theMCH are closed, and the X.25 restart procedure is usedto place the MCH back in operation.


X25IPI332I MCH lu restart confirm packet sent

Explanation: X25IPI transmitted a restart confirmationpacket for this MCH.

System Action: The restart confirmation packet isdumped.


X25IPI334I MCH lu restarting

Explanation: X25IPI is restarting the indicated MCH.

System Action: X25IPI waits to receive a restartconfirmation on the MCH.


X25IPI342I MCH lu diagnostic packet

Explanation: X25IPI received an X.25 diagnosticpacket on this MCH.

System Action: The diagnostic packet is dumped anddiscarded.


X.25 Messages


System Programmer Response: Use the diagnosticpacket to obtain additional information about X.25network problems.

X25IPI342I MCH lu orphan packet received

Explanation: X25IPI received a packet for which itcould find no associated connection.

System Action: An X.25 clear request is sent on thevirtual circuit.


X25IPI343I MCH lu clear request sent

Explanation: X25IPI sent a clear request on theindicated MCH, to recover from an error situation.



X25IPI345E MCH lu no free path available forincoming call 345I MCH lu checknumber of logical channels on Linkrecord

Explanation: X25IPI received an incoming call, but hasno session areas available to handle it. This indicatesthat there are more virtual circuits subscribed thanwere specified on the LINK record in the configurationfile.

System Action: The incoming call is cleared.


System Programmer Response: Increase the virtualcircuit count on the Link record to match the numberof virtual circuits defined in the NPSI configuration.

X25IPI347W MCH lu orphan packet discarded

Explanation: X25IPI received a packet that it could notassociate with any connection.

System Action: The packet is dump and discarded.


System Programmer Response: Determine the type ofX.25 packet from the dump. A clear confirmation (X'17')can be discarded harmlessly.

X25IPI349E MCH lu unrecognized packet received

Explanation: X25IPI did not recognize the type codein a packet received from NPSI.

System Action: The unrecognized packet is dumpedand discarded.



System Programmer Response: Determine the packettype from the dump; notify the IBM Support Center.

X25IPI350I MCH lu terminating

Explanation: X25IPI is terminating this MCH session,in response to an error condition or a HALT command.

System Action: Connections on virtual circuitsassociated with the MCH are terminated, and the MCHsession is closed.


X25IPI355I MCH lu closed

Explanation: X25IPI received a CLSDST completionindication for this MCH, indicating that this MCH hasclosed.



X25IPI365E MCH lu session loss code code

Explanation: X25IPI received the indicated MCHstatus change code while the MCH was notoperational. See message X25IPI391E for the loss codes.



X25IPI367I VC vc packet discarded on failedsession

Explanation: X25IPI discarded a packet received aftera session was closed.

System Action: The packet is dumped and discarded.


X25IPI371E MCH lu unexpected request completion

Explanation: X25IPI received a VTAM requestcompletion notification for this MCH. This indicates aprogram error, because MCH sends are donesynchronously.

System Action: The notification is ignored.



X.25 Messages


X25IPI381I MCH lu DATE error reportcommand=command error=error

Explanation: X25IPI received a NPSI Dedicated Accessto X.25 Transport Extension (DATE) error report, for theindicated command and error. See X.25 Network ControlProgram Packet Switching Interface Host Programming forthe error codes.

System Action: X25IPI attempts to recover from theerror.


X25IPI389E MCH lu DATE error reportcommand=command error=error

Explanation: X25IPI encountered a DATE errorbecause of an incorrect logical channel number. SeeNPSI Host Programming for the error codes.

System Action: X25IPI discards the error indication.


X25IPI391E MCH lu session loss code code

Explanation: X25IPI received a session statusnotification, with the indicated session loss code, forthis MCH.

Code Description

Less than 50 VTAM LOSTERM exit codes

50 VTAM SCIP exit UNBIND

64000 VTAM NS exit CLEANUP

64001 VTAM NS exit session initiationfailure

64002 VTAM NS exit session initiationnegative response.


User or Operator Response: Reactivate the NPSIMCH in VTAM. Use the X25IPI RESTART command toreacquire the MCH LU.

System Programmer Response: Use the VTAM errorcode to determine the reason for the session failure.

X25IPI460I VC vc call to address refused, cause=causediagnostic=diagnostic

Explanation: An outgoing call on this virtual circuit tothe indicated address was refused by the X.25 network,with the indicated cause and diagnostic bytes. See X.25Network Control Program Packet Switching InterfaceDiagnosis, Customization, and Tuning Version 3 for a listof X.25 cause and diagnostic codes. See the provider ofthe X.25 network service for documentation that listsadditional diagnostic codes.

System Action: Datagrams queued for the remotesystem are discarded. A new call is attempted when theTCP acknowledgement timer expires, or when a newconnection is requested to the destination. TCPconnections to the destinations handled by the remotesystem fail, if calls are not accepted within the initialconnection time-out.

User or Operator Response: Check that the remotesystem and the X.25 network is operational.

X25IPI411I VC ID incoming call from address userdata value

Explanation: X25IPI has received an incoming call onthis virtual circuit from the indicated address, with theindicated user data (protocol ID).

System Action: The call is accepted or refused.


System Programmer Response: Use the address todetermine the source of the connection.

X25IPI414I VC vc call collision

Explanation: X25IPI detected a call collision on thisvirtual circuit.

System Action: The X.25 call collision procedure isinitiated.


X25IPI415W VC vc incoming call cleared: caller notknown

Explanation: X25IPI received a call on this virtualcircuit from an address not present in the Dest entriesfor the associated MCH.



System Programmer Response: Determine the identityof the remote system initiating the call request, and addthe address to the Dest list if the connection isauthorized. The X.25 address of the calling system wasnoted in the preceding X25IPI411I message for the VCID.

X25IPI416W VC vc incoming call cleared: draining

Explanation: X25IPI cleared an incoming call becausea VTAM HALT request has been issued to terminatecommunication.

System Action: Incoming calls are refused once theVTAM HALT command is issued.

User or Operator Response: Shutdown and restartX25IPI when VTAM is restarted.

X.25 Messages


X25IPI417E VC vc incoming call cleared: reason

Explanation: X25IPI cleared an incoming call on thisvirtual circuit because of an error in the format of theX.25 call request packet:v Called address is not decimalv Calling address is not decimalv CUD field is too longv CUD field not acceptablev Duplicate addressv The address duplicated that of another connectionv Facilities not acceptablev Reverse charging refusedv Reverse charging was specified in the callv Reverse charging has not been enabled on the

associated Link



System Programmer Response: Correct the remotesystem that is generating the invalid calls. The X.25address of the calling system was noted in thepreceding X25IPI411I message for the VC ID.

X25IPI431I VC vc outgoing call to address

Explanation: X25IPI is placing an outgoing call to thisindicated address on this virtual circuit.

System Action: Queued datagrams are sent on theconnection after the call is accepted by the remotesystem.


System Programmer Response: Use the address todetermine the destination of the connection.

X25IPI445W VC vc call timer expired

Explanation: The remote system has not responded toa call request within 200 seconds.

System Action: The call is terminated and queueddatagrams are discarded.

User or Operator Response: Check the status of theremote system and the X.25 network. The X.25 addressof the calling system was noted in the precedingX25IPI431I message for the VC ID.

X25IPI451I VC vc call accepted by address user datavalue

Explanation: An outgoing call on this virtual circuitwas accepted by the remote system at the indicatedaddress with the indicated user data (protocolspecifier).

System Action: Queued datagrams are sent.


System Programmer Response: Use the address todetermine the destination of the connection.

X25IPI455I VC vc retrying call with packet size size

Explanation: The packet size for this virtual circuitwas reduced by the network or responder. NPSI DATEcannot handle this negotiation, thus the call is clearedand placed again with the smaller packet size.

System Action: The call is cleared and placed againwith the reduced packet size.

User or Operator Response: Tell the systemprogrammer if this message recurs frequently.

System Programmer Response: Add or change anOPTIONS PACKETSIZE entry on the associated Linkspecifying the smallest packet size used by othersystems on the X.25 network. Consider using the NPSIGATE facility rather than DATE. GATE can handle thereduced packet size without the call to be repeated.

X25IPI456E VC vc outgoing call cleared: reason

Explanation: X25IPI cleared an incoming call on thisvirtual circuit because of an error in one of thefollowing formats:v The X.25 call accept packetv Accepting user data is too longv Called address is not decimalv Calling address is not decimalv Facilities not acceptable

System Action: The outgoing call is cleared.


System Programmer Response: Correct the remotesystem that is generating the invalid calls. The X.25address of the called system was noted in thepreceding X25IPI431I message for the VC ID.

X25IPI471I VC vc NPSI logon LU lu

Explanation: NPSI generated a VTAM session logonfrom the indicated LU for the virtual circuit.

System Action: The NPSI LU logon is accepted.


System Programmer Response: Use the LU name forNPSI problem determination.

X25IPI472E VC vc session loss code code

Explanation: X25IPI received a session statusnotification, with the indicated session loss code, forthis virtual circuit while waiting for logon of the NPSIVC LU. See message X25IPI581E for the loss codes.



X.25 Messages


X25IPI482E VC vc OPNDST did not complete

Explanation: A VTAM OPNDST request on a NPSIVC LU was posted complete, but the NIB is notmarked open. The contents of the session data area(SDA) for this VC are dumped.

System Action: The virtual circuit call is cleared.


System Programmer Response: Determine the state ofthe NPSI VC LU using the VTAM DISPLAY command.

X25IPI483I VC vc LU lu ready

Explanation: The virtual circuit LU session is readyfor data transfer.



X25IPI511I VC vc facilities: facilities

Explanation: A list of facilities for this virtual circuitfollows. Facilities codes that can be noted are:

Codes Description

priority Priority handling and charging isapplied

revchg Reverse charging is applied

pkt The noted packet size is used

wdw The noted window size is used

standard DDN standard service is used

precedence The noted DDN precedence is applied

System Action: The noted facilities are applied to theconnection.


System Programmer Response: Use the informationto determine the X.25 network facilities being used onthe connection.

X25IPI515E VC vc facilities field unacceptable atoffset offset

Explanation: X25IPI encountered an invalid X.25 callfacilities field from a remote system for this virtualcircuit.

System Action: The X.25 call facilities field isdumped, and the call is cleared.


System Programmer Response: Correct the remotesystem that is generating the invalid facilities. The X.25address of the remote system was noted in the

preceding X25IPI411I or 431I message for the VC ID.

X25IPI521I VC vc call complete

Explanation: The virtual circuit connection is ready fordata transfer.

System Action: Data transfer begins.


X25IPI548E VC vc oversize data packet received,length=length

Explanation: A datagram was received on this virtualcircuit that had a length exceeding the buffer sizespecified in X25IPI CONFIG. Either the local or remotesystem is misconfigured.

System Action: The packet is dumped, and theconnection is cleared.


System Programmer Response: Check the buffer sizeon the Buffers record in X25IPI CONFIG. The buffersize must be large enough to hold the maximum IPdatagram permitted by the usage agreements of theX.25 network. The X.25 address of the remote systemwas noted in the preceding X25IPI411I or X25IPI431Imessage for the VC ID.

X25IPI549E VC vc unrecognized packet received

Explanation: X25IPI did not recognize the type codein a packet received from NPSI GATE.

System Action: The unrecognized packet is dumpedand discarded.


System Programmer Response: Determine the packettype from the dump; notify the IBM Support Center.

X25IPI551I VC vc call reset, cause=causediagnostic=diagnostic

Explanation: A call reset was received for this virtualcircuit, with the indicated cause and diagnostic bytes.See X.25 Network Control Program Packet SwitchingInterface Diagnosis, Customization, and Tuning Version 3for a list of X.25 cause and diagnostic codes. See theprovider of the X.25 network service for documentationthat lists additional diagnostic codes.

System Action: The reset is confirmed and datatransfer continues.


X.25 Messages


X25IPI552I VC vc reset collision

Explanation: A reset collision occurred on this virtualcircuit.

System Action: Data transfer resumes on the virtualcircuit.


X25IPI553I VC vc reset confirmed

Explanation: A reset on this virtual circuit wasconfirmed by the remote system.

System Action: Data transfer resumes on the virtualcircuit.


X25IPI554W VC vc qualified data packet discarded

Explanation: A qualified data packet was received onan IP connection. Qualified data packets are notspecified for use on IP connections.

System Action: The qualified data packet is dumpedand discarded.


System Programmer Response: Correct the remotesystem that is sending qualified data packets. The X.25address of the remote system was noted in thepreceding X25IPI411I or X25IPI431I message for the VCID.

X25IPI555W VC vc interrupt indication received

Explanation: An interrupt indication was received forthis virtual circuit. Interrupt packets are not specifiedfor use on IP connections.

System Action: The interrupt packet is dumped, andan interrupt response is sent.


System Programmer Response: Correct the remotesystem that is sending interrupt packets. The X.25address of the remote system was noted in thepreceding X25IPI411I or X25IPI431I message for the VCID.

X25IPI556E VC vc interrupt confirmed

Explanation: An interrupt was confirmed for thisvirtual circuit. Interrupt packets are not specified foruse on IP connections.

System Action: The virtual circuit is reset, and datatransfer continues.




X25IPI561E VC vc DATE error reportcommand=command error=error

Explanation: X25IPI received a NPSI DATE errorreport for the indicated command and error. See X.25Network Control Program Packet Switching Interface HostProgramming for the error codes.



X25IPI566E VC vc GATE error reportcommand=command error=error

Explanation: X25IPI received a NPSI GATE errorreport for the indicated command and error. See X.25Network Control Program Packet Switching Interface HostProgramming for the error codes.



X25IPI571I VC vc call cleared, cause=causediagnostic=diagnostic

Explanation: A call was cleared on this virtual circuitwith the indicated cause and diagnostic bytes. See X.25Network Control Program Packet Switching InterfaceDiagnosis, Customization, and Tuning Version 3 for a listof X.25 cause and diagnostic codes. See the provider ofthe X.25 network service for documentation that listsadditional diagnostic codes.

System Action: A clear confirmation is sent, and thevirtual circuit connection is closed.


System Programmer Response: Use the cause anddiagnostic codes to determine the reason the call wascleared.

X25IPI581E VC vc session loss code value on LU lu

Explanation: A session loss status notification wasreceived for this virtual circuit, with the indicated losscode.

Code Description

Less than 50 VTAM LOSTERM exit codes

50 VTAM SCIP exit UNBIND

64000 VTAM NS exit CLEANUP

64001 VTAM NS exit session initiationfailure

X.25 Messages


64002 VTAM NS exit session initiationnegative response

System Action: The virtual circuit connection isclosed.


System Programmer Response: Use the VTAM errorcode to determine the reason for the session failure.

X25IPI591I VC vc inactivity timer expired

Explanation: The inactivity time for this virtual circuitpassed with no data transferred.

System Action: The virtual circuit connection isclosed.


X25IPI610I VC vc connection terminated for address:sent count received count dropped count

Explanation: The number of datagrams sent, receivedand dropped on the virtual circuit to the remote systemwith the indicated X.25 address are shown when theconnection is terminated.

System Action: The VC LU session is closed.


X25IPI611I VC vc closed

Explanation: The call on the virtual circuit wascompletely terminated.

System Action: The virtual circuit is reused for newcalls.


X25IPI615I VC vc close pending

Explanation: A close of this virtual circuit is partiallycompleted.

System Action: X25IPI waits for the remaining closeevents to occur.


X25IPI616W VC vc unable to clear GATE call in stateP2

Explanation: X25IPI needed to clear a NPSI GATE callwhile the call was pending. The NPSI GATEprogramming interface does not allow a call to becleared in this state.

System Action: X25IPI waits for action by the X.25network.


System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe call request.

X25IPI618E VC vc clearing limit exceeded

Explanation: No clear response was received from theremote system after four clear requests.

System Action: The virtual circuit is marked ascleared.


System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe clear request.

X25IPI621I VC vc clear confirmed


Explanation: The remote system responded to a clearrequest on this virtual circuit.

System Action: Virtual circuit termination continues;message X25IPI611I should follow.


X25IPI631I VC vc discarded packet packet in statestate

Explanation: The indicated packet was discarded onthis virtual circuit to accomplish error recovery. Seemessage X25IPI011R VC for the call state codes.

System Action: Virtual circuit error recovery iscompleted.


X25IPI632E VC vc received packet packet invalid instate state

Explanation: The indicated received packet wasinvalid for the current virtual circuit state. See messageX25IPI011R VC for the call state codes.

System Action: The virtual circuit is reset or cleared.


System Programmer Response: Determine the reasonthe X.25 network or remote system sent the invalidpacket.

X25IPI641W VC vc clearing timer expired

Explanation: The remote system did not respond to aclear request within 180 seconds.

System Action: The clear request is retried four times.


X.25 Messages



System Programmer Response: Determine the reasonthe remote system did not respond to the clear request.

X25IPI648E VC vc clearing limit exceeded

Explanation: No clear response was received from theremote system after four clear requests.

System Action: The virtual circuit is marked ascleared.


System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe clear request.

X25IPI651I VC vc clear confirmation sent

Explanation: A clear request from the remote systemwas confirmed on this virtual circuit.



X25IPI652I VC vc clear sent

Explanation: A clear request was sent on this virtualcircuit.



X25IPI680I VC vc reuse delay ended

Explanation: The timer expired for NPSI cleanup forthis virtual circuit. A new call can now be made on thisvirtual circuit.

System Action: The virtual circuit is used for a newcall.


X25IPI681I VC vc retry busy call

Explanation: X25IPI retries a call that previouslyreceived a busy indication from NPSI.

System Action: An outgoing call request is repeated.

User or Operator Response: If the error recurs, notifythe system programmer.

System Programmer Response: If the error recurs,check the number of virtual circuits specified on theLink record in X25IPI CONFIG against the numberdefined in the NPSI configuration. Use the VTAMDISPLAY command to determine the state of the NPSIswitched VC LUs.

X25IPI682E VC vc inactive: VTAM requestcompletion REQ=request

Explanation: A VTAM request has completed for thisvirtual circuit after the connection has been terminated.



X25IPI683E VC vc inactive: session loss code code

Explanation: X25IPI received a session statusnotification, with the indicated session loss code, forthis virtual circuit after the connection was terminated.See message X25IPI581E for the loss codes.

System Action: The notification is ignored.


Source File: xnx25ipi assemble

X25IPI684I VC vc inactive: session cleanup

Explanation: Session cleanup is in progress for thisinactive virtual circuit.

System Action: The VC LU session is closed.


X25IPI685E VC vc inactive: VTAM logon refused

Explanation: A late logon from a NPSI VC LU wasrefused after a call was cleared.

System Action: The logon is rejected.


X25IPI686I VC vc packet discarded on deadconnection

Explanation: A packet was received on this virtualcircuit after the connection was terminated.



X25IPI700I IP VM path accepted for userid UserID

Explanation: An IUCV connection from the TCPIPvirtual machine was accepted.

System Action: IP datagrams are transferred.


X25IPI701E Unexpected IUCV interrupt type=type

Explanation: An unexpected type code was found onan IUCV interrupt before the connection to the TCPIPvirtual machine was established.

System Action: The interrupt is ignored.

X.25 Messages




X25IPI702I IP VM UserID path refused for useridUserID, draining

Explanation: An IUCV connection from the TCPIPvirtual machine was refused because a VTAM HALTcommand had been issued.

System Action: The IUCV connection is refused.

User or Operator Response: HALT and restart theX25IPI application when VTAM is restarted.

X25IPI711E Unexpected IUCV interrupt type=type

Explanation: An unexpected type code was found onan IUCV interrupt.

System Action: The IUCV interrupt area is dumpedand the IUCV connection to the TCPIP virtual machineis severed.



X25IPI712E Destination address address notconfigured

Explanation: An IP datagram was received fromTCPIP for transmission to the indicated address, whichis not listed in the Dest entries in X25IPI CONFIG.

System Action: The IP datagram is discarded.


System Programmer Response: Add a Dest record tothe X25IPI CONFIG file for the IP address or network.Check the GATEWAY entries in PROFILE TCPIP for amisrouted network number.

X25IPI713E IP VM userid rejected message:parameter list data 713E IP VM useridrejected message: two-way

Explanation: An IUCV message was received from theTCPIP virtual machine with unexpected messageoption flags.

System Action: The message is rejected.



X25IPI714E IP VM UserID rejected message: toolong714E IP VM UserID rejected message:too short

Explanation: An IUCV message was received from theTCPIP virtual machine that was too long or too short.




X25IPI715E IP VM UserID rejected message:blocking error

Explanation: An IUCV message was received from theTCPIP virtual machine that contained inconsistentlength fields.




X25IPI716W IP VM UserID discarded empty message

Explanation: An empty IUCV message was receivedfrom the TCPIP virtual machine.

System Action: The message is discarded.



X25IPI749T IP VM UserID programming error onIPVMSNDT

Explanation: An IUCV send completion interrupt wasreceived, but the IUCV send queue is empty.

System Action: The program abends with an ABENDX'749' message.



X25IPI750I IP VM UserID disconnected: sent countreceived count dropped count

Explanation: The number of datagrams sent, received,and dropped on the IUCV connection to the TCPIPvirtual machine are shown when the connection isterminated.

X.25 Messages


System Action: The IUCV connection is severed andX25IPI terminates.


X25IPI760E IP VM UserID inactive: IUCV functioncompletion

Explanation: An IUCV completion interrupt wasreceived after the path has been severed.

System Action: The interrupt is ignored.



X25IPI780E IUCVCOM function failed R15=value

Explanation: The indicated IUCV function failed withthe return code in R15. See the z/VM: Group ControlSystem book for information about the IUCVCOMreturn codes.

System Action: The IUCV connection to the TCPIPvirtual machine or address space is severed.

User or Operator Response: Restart the TCPIPX25NPSI device to reestablish the IUCV path.

System Programmer Response: Determine the reasonfor the IUCV error.

X25IPI781E IUCVCOM function failed: reason

Explanation: The indicated IUCV function failed forthe indicated reason.

System Action: The IUCV connection to the TCPIPvirtual machine or address space is severed.



X25IPI782E IUCV function failed, audit flags=flags

Explanation: The indicated IUCV function failed, withthe indicated audit flag value. See the z/VM: CPProgramming Services book for the IUCV audit flags.

System Action: The IUCV function parameter area isdumped, and the IUCV connection to the TCPIP virtualmachine is severed.



X.25 Messages


Chapter 26. Miscellaneous Messages

This chapter contains miscellaneous DTC messages that are common to all TCP/IPclients and servers.

Common MessagesThis section contains messages that are common to TCP/IP.

0001 TCP/IP installation error: DTCUMETEXT not found

Severity: Error.

Explanation: The TCP/IP message repository isrequired, but was not found.


User or Operator Response: This error indicates anincorrect or incomplete product installation. Ensure thatthe correct 591 disk is linked and accessed; it is possiblethat the 591 disk contains an older version of TCP/IP.

0002 Module not linked with VSPASCAL orCEESTART

Severity: Error.

Explanation: This error indicates that the programmodule file was not built correctly.

System Action: Program execution stops.

User or Operator Response: Contact your systemsupport personnel or the IBM Support Center.

Source File: DTCINI

0003 One or more required libraries notfound

Severity: Error.

Explanation: The C or Pascal runtime library,

SCEERUN or TCPRTLIB LOADLIB, respectively, wasnot found on any accessed disk or directory.

System Action: Program execution stops.

User or Operator Response: Contact your systemsupport personnel. This error indicates an incorrect orincomplete installation. TCPRTLIB LOADLIB should beon the TCP/IP client disk (by default, TCPMAINT 592),and SCEERUN LOADLIB should be on the Y-disk(MAINT 19E).

Source File: DTCINI

0004 Abend detected by DTCINI

Severity: Severe.

Explanation: The VM TCP/IP client program hasended abnormally.

User or Operator Response: If accompanied byadditional messages, correct the problem and retry theoperation. If the problem persists, contact your localsupport personnel or the IBM Support Center.

Source File: DTCINI

COMMTXT Messages

Error code from command. Execution cannot proceedwithout ECMODE ON.

Severity: Error.

Explanation: An error occurred loading theEMULSTSM emulation module. TCPIP requires thismodule be loaded.

System Action: The error flag is set to true andprogram control is returned to the caller. Programexecution continues.

User or Operator Response: See the z/VM: CMS

Command and Utility Reference for information about theNUCXLOAD command to determine thetroubleshooting procedure. This message is notgenerated when Return Code 28 (module not found) isreturned.

System Programmer Response: Assist the user asnecessary to troubleshoot problem.

Source File: CMEMULP PASCAL

Procedure Name: InitEmulation


emulator MODULE not found. Execution cannotproceed without ECMODE ON.

Severity: Error.

Explanation: This module could not be loaded.TCP/IP requires this emulator to be loaded, with SETECMODE ON in effect.

System Action: The error flag is set to true andprogram control is returned to the caller. Programexecution continues.

User or Operator Response: See the appropriate CMSCommand Reference for the command NUCXLOAD todetermine the troubleshooting procedure.

Note: This message is generated when Return Code 28(module not found) is returned.

System Programmer Response: Assist the operator asnecessary to troubleshoot the problem.

Source File: CMEMULP PASCAL

Procedure Name: InitEmulation

File not found, or file cannot be read

Severity: Error.

Explanation: The file used by the operation was notfound or could not be read. For example, the file mayhave a file mode letter of 0.

System Action: An error message is returned and theoperation continues.

User or Operator Response: Correct the name of thefile used on the operation, create the file, or rename thefile so it is not a file mode 0 file.

Source File: CMPRCOM

Procedure Name: SayCalRe

Had a rejected message completion, msg lost

Severity: Warning.

Explanation: An IUCV Message Complete ExternalInterrupt was received with an IPAUDIT fieldindicating a possible asynchronous IUCV errorcondition. The Interrupt was of type incoming prioritymessage completion (06) or incoming non-prioritymessage completion (07). The message could not bereceived.

System Action: TCPIP continues execution.

User or Operator Response: See the systemprogrammer.

System Programmer Response: See the z/VM: CPProgramming Services book for information about IUCVerrors and audit field values. Troubleshoot the IUCVerror. The saveaudit field contained IPADRJCT,indicating the message was rejected. This can indicate

that all IUCV read buffers are full.

Source File: CMIUCSOC C

Procedure Name: descarray_save_iucvbuf

in nextbuf with type type

Severity: Error.

Explanation: An internal program error has occurred.


User or Operator Response: Contact systemprogrammer.

System Programmer Response: The functiondescarray_nextbuf() has been called with an invalidvalue in the parameter type. This indicates the programhas been incorrectly modified. If you have the TCPIPsource distribution and have modified the source code,you should check every call to descarry_nextbuf() todetermine which call specifies the invalid typeparameter; valid types are:v NEXTBUF_RECEIVE (0)v NEXTBUF_SEND (1)v NEXTBUF_READ (2)v NEXTBUF_ACCEPT (3)v NEXTBUF_WRITE (4)

If you have not modified the source code, contact theIBM Support Center.


Procedure Name: descarray_nextbuf

Invalid keyword in file file: token

Severity: Error.

Explanation: The indicated TCPIP DATA file containsan invalid keyword. See the TCP/IP Planning andCustomization for more information about this file.

System Action: The keyword is ignored and executioncontinues.

User or Operator Response: See the TCP/IP Planningand Customization, if necessary. Correct any misspelledor invalid keywords and reinitialize TCPIP.

Source File: CMHOSTN PASCAL

Procedure Name: ReadTCPIPdataFILE

Invalid or missing parameter for statement orprevious statement

Severity: Error.

Explanation: The value for a parameter for aconfiguration statement is invalid, or it appears invalidbecause it is missing, and the next word in theconfiguration file is being used as a value. Additionalmessages should indicate the approximate location of

COMMTXT Messages


the error in the configuration file.

System Action: Execution continues. The statementwith the invalid value will be ignored. The value usedwill be the default or a previously specified value.Other statements may also be incorrectly processed,until the configuration processing can identify the validstart of a statement.

User or Operator Response: Determine whichstatement and value is causing the message. It ispossible the error can be the result of a missing valuein an earlier statement. Correct the configuration file. Itmay be necessary to contact your system programmerto determine the correct value for the configurationstatement.

System Programmer Response: Assist the user withproblem resolution, as required.



Message Complete audit field: value value value

Severity: Warning.

Explanation: An IUCV Message Complete ExternalInterrupt was received with an IPAUDIT fieldindicating a possible asynchronous IUCV errorcondition. The contents of the IPAUDIT field aredisplayed. The IUCV interrupt was of type incomingpriority message completion (06) or incomingnon-priority message completion (07). The messagecould not be received.

System Action: TCPIP continues execution; themessage is lost.


System Programmer Response: See the z/VM: CPProgramming Services book for information about IUCVerrors and audit field values. Troubleshoot the IUCVerror.


Procedure Name: check_audit

program: illegal option -- option

Severity: Error.

Explanation: The indicated command line option isillegal.


User or Operator Response: You must supply a validcommand line option. See the TCP/IP User’s Guide forinformation about correct usage of command lineoptions and their argument requirements.

Source File: getopt c

Procedure Name: getopt

program: option requires and argument -- option

Severity: Error.

Explanation: This option requires an argument, butnone was found on the command line.


User or Operator Response: You must supply a validcommand line option argument. See the TCP/IP User’sGuide for information about the correct usage ofcommand line options and their argumentrequirements.

Source File: getopt c

Procedure Name: getopt

Rc=code on IUCV_function to user, fd=fd, path=path,iprcode=code, iucvname=name

Severity: Error.

Explanation: An error occurred executing an IUCVfunction. The IUCV return code, function name, IUCVuser ID, IUCV path ID, type and IUCV socket name aredisplayed.

System Action: TCPIP continues execution.

User or Operator Response: Record the informationgiven and tell the system programmer about theproblem.

System Programmer Response: See the z/VM: CPProgramming Services book for information about IUCV.Determine and correct the cause of the error.


Procedure Name: doiucv

ReadKanjiTable : Invalid char was read.: index, indexReadKanjiTable : c1, c2 : c1, c2

Severity: Error.

Explanation: An invalid character in a Kanjitranslation table was encountered while reading thetranslation file. The character tuple in error is displayedand is located in the table at the indicated indices.

System Action: The translation table is not read.Program execution continues.

User or Operator Response: An error has beenintroduced to the translation file, at the indicatedindices within the translation table. Correct the error orreload the file from archives or the distribution tape.

Source File: kjxlate pascal

Procedure Name: ReadKanjiTable

COMMTXT Messages

Chapter 26. Miscellaneous Messages 411

ReadKanjiTable: Invalid End of File.

Severity: Error.

Explanation: A premature end of file was encounteredreading the Kanji conversion file. The conversion tablecould not be loaded.

System Action: The Kanji conversion table is notloaded. Program execution continues.

User or Operator Response: Restore the Kanjiconversion file from archives or the distribution tape.Run the program again.

Source File: kjxlate pascal

Procedure Name: ReadKanjiTable

Sever Pending Connection from user, for reason

Severity: Warning.

Explanation: A pending connection from this user wassevered for the indicated reason.

System Action: Execution continues. The listedpending connection has been severed.

User or Operator Response: The most likely reasonfor this message is, there are too many pendingconnections. Ask the system programmer for assistance.

System Programmer Response: Troubleshoot theproblem.



Should not be in sock_request_iucv for function

Severity: Error.

Explanation: The function sock_request_iucv wascalled with an inappropriate function request.

System Action: Execution continues. After theparameter error flag is set to EBADF, control is restoredto the caller with a return code of -1.

User or Operator Response: Contact the IBM SupportCenter.

Source File: cmiucsoc c

Procedure Name: sock_request_iucv

Syntax errors found in file file, continuing.

Severity: Error.

Explanation: Syntax errors were found in the listedfile.

System Action: The parser State is set to IgnoreState,and program operation continues.

User or Operator Response: This message is issued

when the parser did not find one of the followingexpected strings:

HOSTNAME RESOLVERTIMEOUTDOMAINORIGIN OPENTIMEOUTTCPIPUSERID RESOLVERUDPRETRIESNSINTERADDR MAXUDPRETRYSNSPORTADDR NSUSERIDRESOLVEVIA TRACECOMMUNICATEVIA

The operator should ensure that the configuration filecontains the correct syntax and valid information.Correct the input file to ensure correct programoperation.

System Programmer Response: Assist the user withproblem resolution, as required.



TCPHOS012E No Valid Dbcs Option forLOADDBCSTABLES in file

Severity: Error.

Explanation: The indicated FTP DATA file contains aLOADDBCSTABLES statement with no valid parameterspecified.

System Action: The command is ignored andexecution continues.

User or Operator Response: Specify a valid parameterfor the LOADDBCSTABLES statement. See TCP/IPPlanning and Customization for more information aboutconfiguring the LOADDBCSTABLES statement in FTPDATA.



TCPDBC000I DbcsEtoA : First Double ByteCharacter Invalid ord(firstchar)


Explanation: EBCDIC double-byte characters are beingconverted to ASCII. The first character of a double-bytecharacter, with the specified ordinal value, is not in thevalid range for EBCDIC double-byte characters.

System Action: The data in error is transmittedunconverted, and execution continues.

User or Operator Response: Check the contents of thedata being transmitted, to see if it contains validdouble-byte characters. EBCDIC double-byte charactersare enclosed within shift-out X'0E' and shift-in X'0F'characters.

Source File: CMDBCSCV PASCAL

COMMTXT Messages


Procedure Name: DbcsEtoA

TCPDBC001I DbcsEtoA : Second Double ByteCharacter Invalid ord(firstchar)ord(secondchar)


Explanation: EBCDIC double-byte characters are beingconverted to ASCII. The second character of adouble-byte character, with the specified ordinal value,is not in the valid range for EBCDIC double-bytecharacters.


User or Operator Response: Check the contents of thedata being transmitted, to see if it contains validdouble-byte characters. EBCDIC double-byte charactersare enclosed within shift-out X'0E' and shift-in X'0F'characters.


Procedure Name: DbcsEtoA

TCPDBC002I DbcsAtoE : Character after ESCAPEInvalid ord(AsciiEscape) ord(nextchar)


Explanation: ASCII JIS Kanji double-byte charactersare being converted to EBCDIC. ASCII JIS Kanjidouble-byte characters are enclosed within the shift-outescape sequence ESC $ @ or ESC $ B, and the shift-inescape sequence ESC ( B or ESC ( J. The character afterthe ESCAPE, with the specified ordinal value, is notvalid for a JIS Kanji shift-out or shift-in sequence.

System Action: The invalid escape sequence isignored and is transmitted unconverted. Executioncontinues.

User or Operator Response: Check the contents of thedata being transmitted, to see if it contains valid JISKanji double-byte characters and escape sequences forthe selected conversion type.


Procedure Name: DbcsAtoE

TCPDBC003I DbcsAtoE : Character after $ Invalidord(AsciiEscape) ord(AsciiDollar)ord(nextchar)


Explanation: ASCII JIS Kanji double-byte charactersare being converted to EBCDIC. ASCII JIS Kanjidouble-byte characters are enclosed within the shift-outescape sequence ESC $ @ or ESC $ B, and the shift-inescape sequence ESC ( B or ESC ( J. The character afterthe $, with the specified ordinal value, is not valid for aJIS Kanji shift-out sequence.





TCPDBC004I DbcsAtoE : Character after ( Invalidord(AsciiEscape) ord(AsciiBraceL)ord(nextchar)


Explanation: ASCII JIS Kanji double-byte charactersare being converted to EBCDIC. ASCII JIS Kanjidouble-byte characters are enclosed within the shift-outescape sequence ESC $ @ or ESC $ B, and the shift-inescape sequence ESC ( B or ESC ( J. The character afterthe (, with the specified ordinal value, is not valid for aJIS Kanji shift-in sequence.





TCPDBC005I DbcsAtoE : Second Double ByteCharacter Invalid ord(firstchar)ord(secondchar)


Explanation: ASCII double-byte characters are beingconverted to EBCDIC. ASCII double-byte characters areindicated when the first character is in the range forASCII double-byte characters. The second character of adouble-byte character, with the specified ordinal value,is not in the valid range for the second byte ofdouble-byte characters.


User or Operator Response: Check the contents of thedata being transmitted, to see if it contains valid ASCIIdouble-byte characters for the selected conversion type.



COMMTXT Messages

Chapter 26. Miscellaneous Messages 413

TCPDBC006I DbcsAtoE : First Double ByteCharacter Invalid ord(firstchar)


Explanation: ASCII JIS Kanji double-byte charactersare being converted to EBCDIC. ASCII JIS Kanjidouble-byte characters are enclosed within the shift-outescape sequence ESC $ @ or ESC $ B, and the shift-inescape sequence ESC ( B or ESC ( J. The first characterof a double-byte character, with the specified ordinalvalue, is not in the valid range for JIS Kanjidouble-byte characters.





TCPDBC010E Invalid Data in file : Loading Stopped.

Severity: Error.

Explanation: Binary DBCS translation tables are beingloaded from the indicated data set. The file does notcontain data in the required format for DBCS binarytranslate tables.

System Action: Loading of the indicated file stops,and program execution continues.

User or Operator Response: Configure a valid DBCSbinary translate table file in the search order hierarchyfor the required DBCS translation table. See TCP/IPPlanning and Customization for information about theloading and customizing of DBCS translation tables.


Procedure Name: ExitError

Unable to allocate/open file file, continuing.

Severity: Error.

Explanation: TCP was unable to open the indicatedTCPIP DATA file. The OpenText procedure failed witha LastError code of 41. This indicates that the requestedfile was not found, or could not be opened in thecorrect access mode.

System Action: The client record parameter is setequal to the client record data for return, and programoperation continues.

User or Operator Response: Ensure that the file iscorrectly accessed before continuing.

System Programmer Response: Assist the operator

with problem resolution, as required.



user severed IUCV path.

Severity: Warning.

Explanation: You severed an IUCV path.

System Action: Execution continues without an IUCVpath to the listed user.

User or Operator Response: This message is listed asa warning in cases where such an occurrence isunexpected. It does not indicate that the user causedthe condition. If this message is unexpectedly output,the operator should determine what effects such acondition can have before proceeding.

System Programmer Response: Assist the user asnecessary to troubleshoot the problem.



user severed IUCV path. Reason reason

Severity: Warning.

Explanation: You severed an IUCV path for theindicated reason.

System Action: Execution continues without an IUCVpath to the listed user.

User or Operator Response: If this message does notprovide sufficient information in the reason codes toresolve the situation, contact your system programmerfor assistance.

System Programmer Response: Assist the operator orresolve network problems, as required.



COMMTXT Messages


Notices

IBM may not offer the products, services, or features discussed in this document inall countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10594-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationMail Station P3002455 South RoadPoughkeepsie, NY 12601-5400U.S.A.Attention: Information Request

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements, or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility, or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information may contain examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information may contain sample application programs in source language,which illustrates programming techniques on various operating platforms. Youmay copy, modify, and distribute these sample programs in any form withoutpayment to IBM, for the purposes of developing, using, marketing, or distributingapplication programs conforming to IBM’s application programming interfaces.These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms.


TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, or other countries, or both:

BookManager DATABASE 2DB2 DFSMS/VMDirMaintIBM IBMLinkLanguage Environment MVSNetView OpenEdition/VMOS/390 OpenExtensionsSP S/370S/390 System/370System/390 TivoliVTAM VM/ESAz/VM zSeries

Other company, product, and service names may be trademarks or service marksof others.

Notices 417

Bibliography

This bibliography lists the IBM publications thatprovide information about your z/VM system.The z/VM library includes z/VM basepublications, publications for additional facilitiesincluded with z/VM, and publications for z/VMoptional features. For abstracts of z/VMpublications and information about currenteditions and available publication formats, seez/VM: General Information.

z/VM Internet LibraryThe latest editions of most z/VM publications areavailable in Adobe Portable Document Format(PDF) and IBM BookManager® format from thez/VM Internet Library:http://www.ibm.com/eserver/zseries/zvm/library/

The z/VM Internet Library also provides otherinformation about z/VM, such as:v Program directoriesv Data areas and control blocksv Monitor records

VM Collection CD-ROMThe Online Library Omnibus Edition: VM Collection,SK2T-2067, contains libraries in BookManagerformat for current IBM VM system products andIBM licensed programs that run on VM. It alsocontains PDF versions of many of these books.

Note: Only unlicensed publications are included.

z/VM Base Publications

Evaluationz/VM: General Information, GC24-5991z/VM License Information, GC24-6033z/VM: Migration Guide, GC24-5996

Installation and Servicez/VM: Installation Guide, GC24-5992z/VM: Service Guide, GC24-5993z/VM: VMSES/E Introduction and Reference,GC24-5994

Planning and Administrationz/VM: CMS File Pool Planning, Administration,and Operation, SC24-5949z/VM: CMS Planning and Administration,SC24-6042VM/ESA: Connectivity Planning, Administration,and Operation, SC24-5756z/VM: CP Planning and Administration,SC24-6043z/VM: Dynamic I/O Configuration Planning andAdministration, SC24-6044z/VM: Group Control System, SC24-5998z/VM: Performance, SC24-5999z/VM: Running Guest Operating Systems,SC24-5997z/VM: Saved Segments Planning andAdministration, SC24-6056z/VM: System Administration Facility, SC24-6034

Customizationz/VM: CP Exit Customization, SC24-5953

Operationz/VM: System Operation, SC24-6000z/VM: Virtual Machine Operation, SC24-6036

Application Programmingz/VM: CMS Application Development Guide,SC24-6002z/VM: CMS Application Development Guide forAssembler, SC24-6003z/VM: CMS Application Multitasking, SC24-5961z/VM: CMS Callable Services Reference,SC24-6004z/VM: CMS Macros and Functions Reference,SC24-6005z/VM: CP Programming Services, SC24-6001VM/ESA: CPI Communications User’s Guide,SC24-5595z/VM: Enterprise Systems Architecture/ExtendedConfiguration Principles of Operation, SC24-5965z/VM: OpenExtensions Advanced ApplicationProgramming Tools, SC24-5979


http://www.ibm.com/eserver/zseries/zvm/library/

z/VM: OpenExtensions Callable Services Reference,SC24-6007z/VM: OpenExtensions Command Reference,SC24-6006z/VM: OpenExtensions POSIX ConformanceDocument, GC24-5976z/VM: OpenExtensions User’s Guide, SC24-6053z/VM: Program Management Binder for CMS,SC24-6057VM/ESA: Programmer’s Guide to theServer-Requester Programming Interface for VM,SC24-5455z/VM: Reusable Server Kernel Programmer’sGuide and Reference, SC24-5964VM/ESA: REXX/VM Primer, SC24-5598z/VM: REXX/VM Reference, SC24-6035z/VM: REXX/VM User’s Guide, SC24-5962Common Programming Interface CommunicationsReference, SC26-4399Common Programming Interface ResourceRecovery Reference, SC31-6821Debug Tool User’s Guide and Reference,SC09-2137OS/390: DFSMS Program Management,SC27-0806

End Usez/VM: CMS Command and Utility Reference,SC24-6010z/VM: CMS Pipelines Reference, SC24-5971z/VM: CMS Pipelines User’s Guide, SC24-5970VM/ESA: CMS Primer, SC24-5458z/VM: CMS User’s Guide, SC24-6009z/VM: CP Command and Utility Reference,SC24-6008z/VM: Quick Reference, SC24-6011z/VM: XEDIT Command and Macro Reference,SC24-5973z/VM: XEDIT User’s Guide, SC24-5972CMS/TSO Pipelines: Author’s Edition, SL26-0018

Diagnosisz/VM: Diagnosis Guide, GC24-6039z/VM: Dump Viewing Facility, GC24-5966z/VM: System Messages and Codes - CMS,GC24-6031z/VM: System Messages and Codes - CP,GC24-6030

z/VM: System Messages and Codes - OtherComponents, GC24-6032z/VM: VM Dump Tool, GC24-6037

Publications for z/VM AdditionalFacilities

DFSMS/VM®

z/VM: DFSMS/VM Function Level 221Customization, SC24-6047z/VM: DFSMS/VM Function Level 221 DiagnosisGuide, GC24-6046z/VM: DFSMS/VM Function Level 221 Messagesand Codes, GC24-6048z/VM: DFSMS/VM Function Level 221 PlanningGuide, SC24-6049z/VM: DFSMS/VM Function Level 221Removable Media Services, SC24-6050z/VM: DFSMS/VM Function Level 221 StorageAdministration, SC24-6051

Language Environment®

z/VM: Language Environment 1.8 C Run-TimeLibrary Reference, SC24-6038Language Environment for OS/390 & VM:Concepts Guide, GC28-1945Language Environment for OS/390 & VM:Debugging Guide and Run-Time Messages,SC28-1942Language Environment for OS/390 & VM:Programming Guide, SC28-1939Language Environment for OS/390 & VM:Programming Reference, SC28-1940Language Environment for OS/390 & VM:Run-Time Migration Guide, SC28-1944Language Environment for OS/390 & VM:Writing Interlanguage CommunicationApplications, SC28-1943

OSA/SFVM/ESA: Open Systems Adapter Support FacilityUser’s Guide for OSA-2, SC28-1992S/390: Open Systems Adapter-Express Customer’sGuide and Reference, SA22-7403S/390: Planning for the S/390 Open SystemsAdapter (OSA-1, OSA-2) Feature, GC23-3870zSeries 900: Open Systems Adapter-ExpressCustomer’s Guide and Reference, SA22-7476


zSeries 900: Planning for the Open SystemsAdapter-2 Feature, GA22-7477

TCP/IP for z/VMz/VM: TCP/IP Level 430 Diagnosis Guide,GC24-6023z/VM: TCP/IP Level 430 Messages and Codes,GC24-6022z/VM: TCP/IP Level 430 Planning andCustomization, SC24-6019z/VM: TCP/IP Level 430 Programmer’s Reference,SC24-6021z/VM: TCP/IP Level 430 User’s Guide, SC24-6020

Publications for z/VM OptionalFeatures

DirMaint™

z/VM: Directory Maintenance Facility FunctionLevel 410 Command Reference, SC24-6025z/VM: Directory Maintenance Facility FunctionLevel 410 Messages, GC24-6026z/VM: Directory Maintenance Facility FunctionLevel 410 Tailoring and Administration Guide,SC24-6024

PRFz/VM: Performance Reporting Facility FunctionLevel 410, SC24-6027

RTMz/VM: RealTime Monitor Function Level 410,SC24-6028

RACF® for VMRACF: Auditor’s Guide, SC28-1342RACF: Command Language Reference, SC28-0733RACF: Command Language Reference Summary,SX22-0014RACF: Diagnosis Guide, GY28-1016RACF: General Information, GC28-0722RACF: General User’s Guide, SC28-1341RACF: Macros and Interfaces, SC28-1345RACF: Messages and Codes, SC38-1014RACF: Migration and Planning, GC23-3054RACF: Security Administrator’s Guide,SC28-1340RACF: System Programmer’s Guide, SC28-1343

External Security Interface (RACROUTE) MacroReference for MVS and VM, GC28-1366

Other TCP/IP RelatedPublicationsThis section lists other publications, outside thez/VM 4.3.0 library, that you may find helpful.v TCP/IP Tutorial and Technical Overview,

GG24-3376v TCP/IP Illustrated, Volume 1: The Protocols,

SR28-5586v Internetworking with TCP/IP Volume I: Principles,

Protocols, and Architecture, SC31-6144v Internetworking With TCP/IP Volume II:

Implementation and Internals, SC31-6145v Internetworking With TCP/IP Volume III:

Client-Server Programming and Applications,SC31-6146

v DNS and BIND in a Nutshell, SR28-4970v "MIB II Extends SNMP Interoperability," C.

Vanderberg, Data Communications, October 1990.v "Network Management and the Design of SNMP,"

J.D. Case, J.R. Davin, M.S. Fedor, M.L.Schoffstall.

v "Network Management of TCP/IP Networks:Present and Future," A. Ben-Artzi, A. Chandna,V. Warrier.

v "Special Issue: Network Management andNetwork Security,"ConneXions-TheInteroperability Report, Volume 4, No. 8, August1990.

v The Art of Distributed Application: ProgrammingTechniques for Remote Procedure Calls, John R.Corbin, Springer-Verlog, 1991.

v The Simple Book: An Introduction to Managementof TCP/IP-based Internets, Marshall T Rose,Prentice Hall, Englewood Cliffs, New Jersey,1991.

Bibliography 421

Index

BBOOTPD

messages 1

CCMSRESOLV messages 15Common Messages 409Commtxt messages 409CONVXLAT messages 359

DDHCPD

messages 1Domain Name Server messages 15

FFile Transfer Protocol (FTP) messages 33FTPPERM messages 361

GGDDMXD/VM

abend codes 83messages 83

HHOMETEST messages 362

IIFCONFIG messages 363Internet Message Access Protocol (IMAP)

messages 85IPWIZARD messages 369

LLPD messages 161LPQ messages 168LPR messages 170LPRM messages 178LPRSET messages 170

MMiscellaneous messages 409MPROUTE

messages 99

NNETSTAT

messages 119Network File System (NFS)

messages 125NFSPERM messages 361

OOBEYFILE messages 371

PPING messages 155PORTMAP

messages 159

RRemote Printing messages 161

LPD 161LPQ 168LPR 170LPRM 178LPSET 170

Remote Procedure Call messagesRPCGEN messages 188RPCILIB messages 181RPCINFO messages 186

REXEC messages 191REXECD messages 193ROUTED

messages 199

SSecure Socket Layer (SSL)

messages 279SSL Return Codes 291SSL Server Reply Codes 291, 292, 293

Simple Mail Transfer Protocol (SMTP)Reply Code messages 243Server messages 223SMTPRSCS messages 253

Simple Network Management Protocol(SNMP)

SNMPD messages 265SNMPLIB messages 269SQESERV messages 274

SNALINKmessages 257

TTCP/IP

server messages 295TCP/IP Utilities messages

CONVXLAT messages 359

TCP/IP Utilities messages (continued)FTPPERM messages 361HOMETEST messages 362IFCONFIG messages 363IPWIZARD messages 369NFSPERMmessages 361OBEYFILE messages 371TCPRUN messages 371

TCPRUN messages 371Trivial File Transfer Protocol (TFTP)

messages 377Trivial File Transrer Program (TFTP)

TFTPD messages 381

UUniversal File Transfer (UFT)

UFTD messages 383

XX.25

messages 387


Readers’ Comments — We’d Like to Hear from You

z/VM™

TCP/IP Level 430Messages and CodesVersion 4 Release 3.0

Publication No. GC24-6022-02

Overall, how satisfied are you with the information in this book?

Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfied

Overall satisfaction h h h h h

How satisfied are you that the information in this book is:

Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfied

Accurate h h h h h

Complete h h h h h

Easy to find h h h h h

Easy to understand h h h h h

Well organized h h h h h

Applicable to your tasks h h h h h

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? h Yes h No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in anyway it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.

Readers’ Comments — We’d Like to Hear from YouGC24-6022-02

GC24-6022-02

��Cut or FoldAlong Line

Cut or FoldAlong Line

Fold and Tape Please do not staple Fold and Tape

Fold and Tape Please do not staple Fold and Tape

NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES

BUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CorporationInformation DevelopmentDepartment G60G1701 North StreetEndicott, New York13760-5553

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

__

_

��

File Number: S370/4300/30XX-50Program Number: 5739-A03

Printed in U.S.A.

GC24-6022-02

Spin

ein

form

atio

n:

��

�z/

VM

TC

P/I

PM

essa

ges

and

Code

sVe

rsio

n4

Rel

ease

3.0

z/VM: TCP/IP Messages and Codes · Preface z/VM: TCP/IP Level 430 Messages and Codes is intended to...

Documents

Transcript of z/VM: TCP/IP Messages and Codes · Preface z/VM: TCP/IP Level 430 Messages and Codes is intended to...