z/VM: TCP/IP Messages and Codes - z/VM - IBM

z/VM TCP/IP Level 430Messages and CodesVersion4Release3.0GC24-6022-02

z/VM TCP/IP Level 430Messages and CodesVersion4Release3.0GC24-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.

OBEYFILE Messages . . . . . . . . . . . 371TCPRUN Messages . . . . . . . . . . . 371Chapter 22. TFTP Messages . . . . . 377Chapter 23. TFTPD Messages . . . . 381Chapter 24. UFTD Messages . . . . . 383Chapter 25. X.25 Messages . . . . . 387Chapter 26. Miscellaneous Messages 409Common Messages . . . . . . . . . . . 409COMMTXT Messages . . . . . . . . . . 409Notices . . . . . . . . . . . . . . 415Trademarks . . . . . . . . . . . . . . 417Bibliography. . . . . . . . . . . . 419z/VM Internet Library . . . . . . . . . . 419VM Collection CD-ROM. . . . . . . . . . 419z/VM Base Publications . . . . . . . . . . 419Evaluation . . . . . . . . . . . . . 419Installation and Service . . . . . . . . . 419Planning and Administration . . . . . . . 419Customization . . . . . . . . . . . . 419Operation . . . . . . . . . . . . . 419Application Programming . . . . . . . . 419End Use . . . . . . . . . . . . . . 420Diagnosis. . . . . . . . . . . . . . 420Publications for z/VM Additional Facilities . . . 420DFSMS/VM ® . . . . . . . . . . . . 420Language Environment ® . . . . . . . . 420OSA/SF . . . . . . . . . . . . . . 420TCP/IP for z/VM . . . . . . . . . . . 421Publications for z/VM Optional Features . . . . 421DirMaint . . . . . . . . . . . . . 421PRF . . . . . . . . . . . . . . . 421RTM . . . . . . . . . . . . . . . 421RACF ® for VM. . . . . . . . . . . . 421Other TCP/IP Related Publications . . . . . . 421Index . . . . . . . . . . . . . . . 423ivz/VM: TCP/IP Messages and Codes

PrefaceWho Should Read This Bookz/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.This 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 BookWhat This Book ContainsBefore 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.This 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/vvThere you will find the feedback page where you can enter and submit yourcomments.Send your comments by electronic mail to one of the following addresses:Internet: vmpub@us.ibm.comIBMLink : GDLVME(PUBRCF)Fill out the Readers’ Comments form at the back of this book and return it bymail, 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-5553USAUnderstanding Message Text FormatThis section describes general concepts needed to define and configure the virtualmachines, servers, and applications in TCP/IP.viz/VM: TCP/IP Messages and Codes

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 BookTCP/IP Message FormatThe following describes how numbers are used in this book:v Numbers over four digits are represented in metric style. A space is used ratherthan 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.Some 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###eorxxxmmm####eThis message format consist of four fields:xxxThree 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.Prefacevii

eThe 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 CodesSeverityCode MeaningIWESRTInformation onlyWarningErrorSevere errorCommand responseTermination messageviiiz/VM: TCP/IP Messages and Codes

Summary of ChangesThis 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/IPServer 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 newChapter 19, “SSL Messages”This edition also contains minor editorial and technical changes, along withmiscellaneous service APAR changes.xz/VM: TCP/IP Messages and Codes

Chapter 1. BOOTPD and DHCPD MessagesThis chapter contains BOOTPD and DHCPD messages. Follow the User Response,as appropriate, within each message area to resolve the problem.TCP0001EExplanation:Machine File was not specifiedThe 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 TCPDHCTCP0001EExplanation:Configuration File was not specifiedThe 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0003EToo many operands on the subcommandlineExplanation: Too many operands were specified onthe subcommand line.System Action:terminated.Execution of the subcommandUser or Operator Response: Reissue the subcommandwith the correct number of operands.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0003EToo many operands on the statementlineExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0004EUnrecognized option option - continuingExplanation: An unrecognized option wasencountered on the command line. Processing of thecommand continued.System Action: Execution of the command completedwith the unrecognized optionUser or Operator Response: If necessary, reissue thecommand with the correct option specified. beingignored.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0005EUnrecognized subcommand or statementname - continuingExplanation: The specified subcommand or statementwas not recognized.System Action:not processed.The statement or subcommand wasUser 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0006EUnrecognized operand - operandExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHC© Copyright IBM Corp. 1987, 2002 1

BOOTPD and DHCPD MessagesTCP0007IPrior error message refers to line line infileExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0103EUnable to establish the Event MonitorEnvironmentExplanation: An error prevented the enablement ofthe event monitor environment.System Action:User or Operator Response:server.The server shuts down.IPL CMS and restart theSource File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0007IPrior error message refers to statementstmtnumb in file. The statement in erroris: stmtExplanation: The preceding error message indicatedan error in a machine file or configuration file. Thismessage identifies the statement that caused the error.System Action:None.User or Operator Response:None.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0101ERC=rc loading Machine file: fn ft fmExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0106EUnable to read file: fileExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0107EUnable to start cyclic timer: timer token,RC=return code, RE=reason codeExplanation: An error occurred while attempting tostart a cyclic timer used by the server.System Action:The server shuts down.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 EXECTCP0102ERC=rc trying to start communicationsExplanation: An error prevented the activation orreactivation of the UDP environment.System Action: If STAYUP mode is active, the serverwill wait a period ofUser 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0110EUnable to write file: file Pipe rc=rcExplanation: 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.Source File:DHCPD EXEC2 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesTCP0110EUnable to write file: file Copyfile rc=rcExplanation: 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.Source File:TCP0200EDHCPD EXECIncorrect CMS level. CMS 11 or later isrequiredExplanation: The server was attempted to be run on alevel of CMS that does not support all of the requiredfunctions used by the server.System Action:User or Operator Response:correct level of CMS.The server shuts down.Run the server on theSource File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0205EError encountered while attempting toNUCXLOAD RXSOCK13, rc=retcodeExplanation: An error was encountered when theNUCXLOAD command was issued to load RXSOCK13.System Action:The server shuts down.User or Operator Response: See z/VM: CMS Commandand Utility Reference for more information on the CMSNUCXLOAD command and how to correct theproblem.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0300E 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0400EUnable to determine IP address foripaddr Will not answer htype=htypechaddr=chaddrExplanation: 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:TCP0401EBOOTPD EXECIP address for tag is not valid Will notanswer htype=htype chaddr=chaddrExplanation: 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.Source File:TCP0402EBOOTPD EXECtag tag value of tagval for entry is not avalid IP address. The tag will beignoredExplanation: 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.Source File:TCP0403EBOOTPD EXECClient IP address is not valid: operandExplanation: 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

BOOTPD and DHCPD MessagesSource File:TCP0404EDHCPD EXECBoot Strap Server IP address is notvalid: operandExplanation: An invalid IP address specified on theBOOTSTRAPSERVER statement.System Action:ignored.The BOOTSTRAPSERVER statement isUser or Operator Response: Correct theBOOTSTRAPSERVER statement and reload themachine file.Source File:TCP0500EDHCPD EXECUnrecognized Adapter IP Address:operandExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0500EExplanation:Gateway.Unrecognized Gateway IP Address:operandAn invalid IP address was specified for aSystem 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0500EUnrecognized Subnet IP Address:operandExplanation: 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.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.Source File:TCP0500EBOOTPD EXECUnrecognized target IP Address: operandExplanation: An IP address specified on asubcommand or statement was not recognized as avalid address.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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0502EExplanation:Target IP Address is missingA target IP address was not specified.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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP0510EAddress range specified on the SUBNETstatement overlaps a previouslyspecified SUBNET rangeExplanation: A SUBNET statement specified a rangeof addresses that overlaps a range specified by apreceding SUBNET statement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXEC4 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesTCP0511EIP address specified on the CLIENTstatement is the same as a previouslyspecified CLIENT IP addressExplanation: A CLIENT statement specified an IPaddress that is already reserved by a previous CLIENTstatement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0520EExplanation:specified.DHCPD EXECIP address is missingAn IP address was expected but notSystem 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.Source File:TCP0521EExplanation:DHCPD EXECHardware type is missingThe 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.Source File:TCP0522EExplanation:DHCPD EXECClient ID is missingThe client ID was not specified.System Action: Processing of the statement orsubcommand terminates.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.Source File:DHCPD EXECTCP0523EExplanation:Class name is missingThe class name was not specified.System Action: Processing of the statement orsubcommand terminates.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.Source File:TCP0524EExplanation:DHCPD EXECVendor name is missingThe vendor name was not specified.System Action: Processing of the statement orsubcommand terminates.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.Source File:TCP0530EExplanation:DHCPD EXECIP address is not validAn IP address was incorrectly specified.System Action: Processing of the statement orsubcommand terminates.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.Source File:TCP0531EDHCPD EXECHardware type is not validExplanation: The hardware type was incorrectlyspecified. The value must be an integer between 0 and255, inclusive.System Action: Processing of the statement orsubcommand terminates.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.Source File:DHCPD EXECChapter 1. BOOTPD and DHCPD Messages 5

BOOTPD and DHCPD MessagesTCP0532EExplanation:Client ID is not validThe specified client ID is not valid.System Action: Processing of the statement orsubcommand terminates.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.Source File:TCP0600EDHCPD EXECStarting brace is not validExplanation: A starting brace "{" was encounteredwhere one was not expected.System Action:terminates.Processing of the statementUser or Operator Response: Correct the machine fileand reenter the command or subcommand that readthe file.Source File:TCP0601EDHCPD EXECEnding brace is not validExplanation: An ending brace "}" was encounteredwhere one was not expected.System Action:terminates.Processing of the statementUser or Operator Response: Correct the machine fileand reenter the command or subcommand that readthe file.Source File:TCP0602EDHCPD EXECOption number operand is not validExplanation: An option number was specified that isnot valid. Option numbers must be integers between 0and 255, but not including 0 and 255System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0603EDHCPD EXECOption number operand is missing anoption valueExplanation: An option value was not specified on theOPTION statement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0610EDHCPD EXECstmt1 is not valid inside stmt2 statementsExplanation: stmt1 was specified within a level (stmt2)that does not allow such statements.System Action:terminates.Processing of the statementUser or Operator Response: Correct the machine fileand reenter the command or subcommand that readthe file.Source File:TCP0620EDHCPD EXECToo few operands specifiedExplanation: The statement or subcommand endedbefore the specification of all required operandsSystem Action:not processed.The statement or subcommand wasUser 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.Source File:TCP0621EDHCPD EXECAddress range is missing or not validExplanation: An address range on a statement orsubcommand was either not specified or specifiedincorrectly.System Action:not processed.The statement or subcommand wasUser 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.Source File:TCP0622EDHCPD EXECLabel name is missing or not validExplanation: A label name was either not specified orspecified incorrectly.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.6 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesSource File:TCP0623EExplanation:integer.System Action:terminates.DHCPD EXECPriority operand is not validThe specified priority value is not a validProcessing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0624EDHCPD EXECCLASS name is missing or not validExplanation: A class name was either not specified orspecified incorrectly.System Action:not processed.The statement or subcommand wasUser 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.Source File:DHCPD EXECTCP0627EExplanation:valid.System Action:terminates.HEX value is not a valid hexadecimalstringA specified hexadecimal value is notProcessing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0628EDHCPD EXECOption statements are not allowed whenVENDOR statement contains the HEXkeywordExplanation: 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.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXECTCP0625EAn IP address range is not allowed on astmt statement at the global levelExplanation: A single IP address is required for thestatement at the global level.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXECTCP0629EOption operand was already specifiedExplanation: An OPTION statement for the specifiedoption was specified more than once at the currentlevel.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXECTCP0626EExplanation:incorrectly.System Action:not processed.VENDOR name is missing or not validA VENDOR name is missing or specifiedThe statement or subcommand wasUser 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.Source File:DHCPD EXECTCP0630EOption value is not a valid stringExplanation: 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.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXECChapter 1. BOOTPD and DHCPD Messages 7

BOOTPD and DHCPD MessagesTCP0631EType value 'value' is not recognized foruser defined option type optionExplanation: The value specified for the indicatedoption is not a recognized option value.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0631EDHCPD EXECType value 'value' is not recognized forinternally defined option type optionExplanation: 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.Source File:TCP0632EDHCPD EXECOption operand value is not valid Optionoperand value is not valid: valueExplanation: The value specified for the indicatedoption is not valid.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0635EDHCPD EXECThe specified client is not associatedwith an addressExplanation: 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:terminates.Processing of the subcommandUser or Operator Response: Verify and reenter thesubcommand with the correct client ID.Source File:DHCPD EXECTCP0636EThe specified client is associated withmore than one address. You must deletethe lease using the addressExplanation: 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.System Action:terminates.Processing of the subcommandUser or Operator Response: Specify the subcommandusing the ADDRESS operand instead of the CLIENToperand so that the subcommand can distinguishwhich subnet to change.Source File:TCP0637EDHCPD EXECaddress is not activeExplanation: The specified address is not activelyleased to a client.System Action:terminates.Processing of the subcommandUser or Operator Response: Respecify thesubcommand with the correct address.Source File:TCP0638EDHCPD EXECThe address range specified on the stmtstatement is not a subset of theSUBNET address rangeExplanation: 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.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0639EDHCPD EXECThe address specified on the stmtstatement is not within the SUBNETaddress rangeExplanation: 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.8 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesSystem Action: Processing of the statementterminates.User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0640EDHCPD EXECThe option length is missing for userdefined option type optionExplanation: The length operand was not specified onthe statement which defines the indicated option.System Action:terminates.Processing of the statementUser 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.Source File:TCP0640EDHCPD EXECThe option length is missing forinternally defined option type optionExplanation: The length operand was not specified foran option that was being internally defined by theDHCPD server.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 noify them of the problem. You willneed to provide the complete message text.Source File:TCP0641EDHCPD EXECThe minimum value is missing for userdefined option type optionExplanation: 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.User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:DHCPD EXECTCP0641EThe minimum value is missing forinternally defined option type optionExplanation: The minimum value operand was notspecified for an option that was being internallydefined by the DHCPD server.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.Source File:TCP0642EDHCPD EXECThe maximum value is missing for userdefined option type optionExplanation: The maximum 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.User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0642EDHCPD EXECThe maximum value is missing forinternally defined option type optionExplanation: The maximum value operand was notspecified for an option that was being internallydefined by the DHCPD server.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.Source File:TCP0643EDHCPD EXECThe minimum value is not valid foruser defined option type optionExplanation: The minimum value operand wasincorrectly specified on the statement which defines theindicated option.System Action: Processing of the statementterminates. The Option is not defined. Any optionstatements for this option are treated according to therules for undefined options.Chapter 1. BOOTPD and DHCPD Messages 9

BOOTPD and DHCPD MessagesUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0643EDHCPD EXECThe minimum value is not valid forinternally defined option type optionExplanation: The minimum value operand wasincorrectly specified for an option that was beinginternally defined by the DHCPD server.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.Source File:TCP0644EDHCPD EXECThe maximum value is not valid foruser defined option type optionExplanation: The maximum value operand wasincorrectly specified on the statement which defines theindicated option.System Action: Processing of the statementterminates. The Option is not defined. Any optionstatements for this option are treated according to therules for undefined options.User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0644EDHCPD EXECThe maximum value is not valid forinternally defined option type optionExplanation: The maximum value operand wasincorrectly specified for an option that was beinginternally defined by the DHCPD server.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.Source File:DHCPD EXECTCP0645EThe minimum value is greater than themaximum value for user defined optiontype optionExplanation: The minimum value is greater than themaximum value specified on the statement whichdefines the indicated option.System Action: Processing of the statementterminates. The Option is not defined. Any optionstatements for this option are treated according to therules for undefined options.User or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0645EDHCPD EXECThe minimum value is greater than themaximum value for internally definedoption type optionExplanation: The minimum value is greater than themaximum value specified for an option that was beinginternally defined by the DHCPD server.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.Source File:TCP0650EDHCPD EXECLabel name is greater than 64 characters:operandExplanation: The specified label name is longer thanthe allowed maximum length.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0651EDHCPD EXECLabel name is specified more than once:operandExplanation: The indicated label was specified morethan once on the statement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.10 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesSource File:DHCPD EXECSource File:DHCPD EXECTCP0652ELabel list is too longExplanation: The list of labels is too long. It may beno more than 5000 characters long. Extra blanks areremoved before the maximum is checked.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0653EDHCPD EXECLabel name is specified in both theInOrder and Balance lists: labelExplanation: The indicated label name was specifiedon both the INORDER: and BALANCE: statements.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0654EDHCPD EXECSubnet statements for address specifydifferent labels: label1 label2Explanation: 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.Source File:TCP0655EDHCPD EXECUnable to determine the subnet maskfor subnet subnetExplanation: The SUBNET statement for the specifiedsubnet did not specify the subnet mask and the maskcould not be determined from the subnet address.System Action:terminates.Processing of the statementUser 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.TCP0660EExplanation:System Action:terminates.The specified time value is not valid:operandThe time value must be a whole number.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0661EDHCPD EXECThe specified unit of time is not valid:operandExplanation: The specified unit of time is notrecognized or valid for the statement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP0662EDHCPD EXECThe specified time is outside theallowed rangeExplanation: The specified time is outside the timerange allowed for the statement.System Action:terminates.Processing of the statementUser or Operator Response: Correct the statement inthe machine file and reenter the command orsubcommand that read the file.Source File:TCP5000WDHCPD EXECDHCPDecline received for address, sentby client ID Address is not available foruseExplanation: 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:untilThe address is marked unavailableUser 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.Source File:DHCPD EXECChapter 1. BOOTPD and DHCPD Messages 11

BOOTPD and DHCPD MessagesTCP5001WICMP ECHO REPLY received for addressAddress is not available for use ClientID id value will not be serviced at thistimeExplanation: 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.Source File:TCP6500IDHCPD EXECSocket(SendTo) to port at ipaddrreturned: returned valuesExplanation: 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6501ISocket(Initialize) returned: returnedvaluesExplanation: An error occurred on a SOCKETINITIALIZE 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6502ISocket(Socket) returned: returned valuesExplanation: An error occurred on a SOCKETSOCKET 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6503ISocket(SetSockOpt) on socket socketreturned: returned valuesExplanation: An error occurred on a SOCKETSETSOCKOPT 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6504IExplanation:function.Socket(Ioctl) on socket socket returned:returned valuesAn error occurred on a SOCKET IOCTLSystem 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6505IExplanation:function.Socket(Bind) on socket, port port, addressaddress returned: returned valuesAn error occurred on a SOCKET BINDSystem 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHC12 z/VM: TCP/IP Messages and Codes

BOOTPD and DHCPD MessagesTCP6506ISocket(IoCtl,SiocGifConf) returned:returned valuesExplanation: An error occurred on a SOCKET IOCTLSIOCGIFCONF 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6507ISocket(GetHostId) returned: returnedvaluesExplanation: An error occurred on a SOCKETGETHOSTID 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6508IExplanation:function.Socket(Close) on socket socket returned:returned valuesAn error occurred on a SOCKET CLOSESystem 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6509ISocket(IoCtl,SiocGifNetMask) forinterface name returned: returned valuesExplanation: An error occurred on a SOCKET IOCTLSIOCGIFNETMASK 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6510IExplanation:function.Socket(Select) returned: returned valuesAn error occurred on a SOCKET SELECTSystem 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6511ISocket(RecvFrom) returned: returnedvaluesExplanation: An error occurred on a SOCKETRECVFROM 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.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCTCP6512ITCP6512I Socket(IoCtl,SiocGifBrdAddr)for interface name returned: returned valuesExplanation: 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.User or Operator Response: See the z/VM: CMSCallable Services Reference for information on theSOCKET returned values. Correct the problem.Source File: BOOTPD EXEC for TCPBOO or DHCPDEXEC for TCPDHCChapter 1. BOOTPD and DHCPD Messages 13

BOOTPD and DHCPD Messages14 z/VM: TCP/IP Messages and Codes

Chapter 2. Domain Name Server and Resolver MessagesThis 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 originSeverity: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.System Action:None.User or Operator Response:None.ACQUIRE PUBLIC DBSPACE NAMES tableName(PAGES=count)Severity:Informational.Explanation: NSACQ issues this message echoing theSQL command used to acquire space for the nameserver.System Action:None.User or Operator Response:Couldn’t open output fileSeverity:Error.None.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 fileSeverity:Error.Explanation: NSDBLOAD encountered an erroropening a resource record file previously generated.System Action:NSDBLOAD terminates.User or Operator Response: Verify that the file can befound in the current search order.Couldn’t read output resource record fileSeverity: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.System Action:User or Operator Response:access to the file.NSDBLOAD terminates.Create index tableName on tableNameSeverity:Informational.Verify NSDBLOAD’sExplanation: NSDBLOAD is creating an index fortableName using the same name prior to adding thenew resource records to the table.System Action:Processing continues.User or Operator Response:Creating table tableNameSeverity:Informational.None.Explanation: NSTABLE issues SQL commands tocreate the indicated table.System Action:Create the SQL table.User or Operator Response:None.© Copyright IBM Corp. 1987, 2002 15

DNS and Resolver MessagesCurrently used TABLES: TableNameListUser or Operator Response:None.Severity:Explanation:tables.System Action:Informational.NSDBLOAD is using the indicatedNone.User or Operator Response:Data base update completed.Severity:Explanation:update.System Action:Informational.None.NSDBLOAD has completed the databaseNone.User or Operator Response:Data outside of inner parensSeverity:Error.None.Explanation: A CMSRESOL command line containeddata outside the inner parenthesis. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.System Action:User or Operator Response:syntax.The CMSRESOL command terminates.Correct the commandDATAGRAM|CONN|IUCV & timeout args missingSeverity: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.System Action:User or Operator Response:line arguments.The CMSRESOL command terminates.Delete all data from tableName tableSeverity:Informational.Use the correct commandExplanation: NSDBLOAD is about to delete all datafrom the indicated table.System Action:None.User or Operator Response:None.Deleted all data in SQL table tableNameSeverity:Informational.Explanation: NSDBLOAD has completed deleting alldata in the indicated SQL table.System Action:None.Do you want to create resource records froma master file(y/n)?Severity:Informational.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:terminate.If the response is N, the program willUser or Operator Response: Enter Y or N.Do you want to delete all resource records fromdb(y/n)?Severity:Informational.Explanation: The NSDBLOAD command is promptingyou to determine if all resource records should bedeleted from the database.System Action:None.User or Operator Response: Enter Y or N.Do you want to insert the RR in the SQL tablenow(y/n)?Severity:Informational.Explanation: NSDBLOAD is prompting you todetermine if the resource records defined in the inputparameters should be inserted into the SQL tables now.System Action:None.User or Operator Response: Enter Y or N.Do you want to translate all data to lower case?(y/n)Severity:Informational.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.System Action:None.User or Operator Response: Enter Y or N.Do you want to translate all data to upper case?(y/n)Severity:Informational.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.16 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesSystem Action: None.User or Operator Response: Enter Y or N.Drop index tableNameSeverity: Informational.Explanation: NSDBLOAD is deleting the current datafor this table.System Action: None.User or Operator Response: None.Error occurred deleting table infoSeverity: Error.Explanation: NSDBLOAD encountered an errordeleting SQL table information.System Action: NSDBLOAD terminates.User or Operator Response: None.Severity:Informational.Explanation: The NSACQ command line syntax isdisplayed in response to the NSACQ ? command.System Action:NSACQ terminates.User or Operator Response:None.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 ASeverity:Informational.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.User or Operator Response:None.Error(s) occurred reading master datafileSeverity:Error.Explanation: NSDBLOAD encountered an error whileprocessing the master data file.System Action:User or Operator Response:data in the master data file.NSDBLOAD terminates.EXEC SQLINIT DBNAME(dbname)Severity:Informational.Verify the syntax of theExplanation: NSACQ issues this message echoing theSQL command used to initialize its access to SQL.System Action:None.User or Operator Response:Finished adding data to table ...Severity:Informational.None.Explanation: NSDBLOAD has finished adding data toits SQL table.System Action:None.User or Operator Response:None.format: NSACQ dbname dbspace npagesNSACQ acquires a dbspace in dbname withN number of pages.Defaults:dbname TCPDBAdbspace TCPSPACEnpages 5120Include file not definedSeverity: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:statement.Incomplete section entrySeverity:Error.Correct the $INCLUDEExplanation: 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.System Action:User or Operator Response:line syntax.Incomplete entry listSeverity:Error.The CMSRESOL command terminates.Use the correct commandExplanation: A CMSRESOL command line containedan incorrect number of entries. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.System Action:User or Operator Response:the command line.The CMSRESOL command terminates.Use the correct syntax onChapter 2. Domain Name Server and Resolver Messages 17

DNS and Resolver MessagesIncomplete question entrySeverity:Error.Explanation: A CMSRESOL command line containedan incomplete question entry. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.System Action:User or Operator Response:syntax.Invalid arg argSeverity:Error.The CMSRESOL command terminates.Use the correct commandExplanation: A CMSRESOL command line containedan invalid connection method argument. Validarguments are:v DATAGRAMv CONNv IUCVSee TCP/IP User’s Guide for the syntax of theCMSRESOL command.System Action:User or Operator Response:syntax.Invalid class dataSeverity:Error.The CMSRESOL command terminates.Use the correct commandExplanation: 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.System Action:The CMSRESOL command terminates.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.System Action:The CMSRESOL command terminates.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 DBASESee TCP/IP User’s Guide for the syntax of theCMSRESOL command.System Action:The CMSRESOL command terminates.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 CSSee TCP/IP User’s Guide for the syntax of theCMSRESOL command.System Action:The CMSRESOL command terminates.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:ALOC97DBUPDDBQRYNSMDMFCNAMESOAMBMGMRMXTXTNULLWKSPTRHINFOMINFOAXFRMILBMILA*See TCP/IP User’s Guide for the syntax of theCMSRESOL command.System Action:User or Operator Response:The CMSRESOL command terminates.Use a correct value for18 z/VM: TCP/IP Messages and Codes

DNS and Resolver Messagesthe 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.System Action:User or Operator Response:syntax.Invalid wild card definitionSeverity:Warning.The CMSRESOL command terminates.Use the correct commandExplanation: 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 definedSeverity: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:with the correct syntax.IUCV Connect rc = returnCodeSeverity:Error.Reissue the commandExplanation: 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.System Action:User or Operator Response:your system programmer.The CMSRESOL command terminates.Report the problem toSystem 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 = returnCodeSeverity: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.System Action:User or Operator Response:your system programmer.The CMSRESOL command terminates.Report the problem toSystem 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 updateSeverity: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.System Action:The CMSRESOL command terminates.User or Operator Response: Correct the CMSRESOLcommand to communicate by means of IUCV.IUCV Sever failed rc= returnCodeSeverity:Error.Explanation: CMSRESOL encountered an errorsevering an IUCV connection.System Action:User or Operator Response:the system programmer.The CMSRESOL command terminates.Report the problem toSystem 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.Chapter 2. Domain Name Server and Resolver Messages 19

DNS and Resolver MessagesLine lineNumber SOA mailbox error: badValueSeverity: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 missingSeverity:Error.Explanation: A CMSRESOL command ended before aname server address was specified. See TCP/IP User’sGuide for the syntax of the CMSRESOL command.System Action:The CMSRESOL command terminates.User or Operator Response: Invoke CMSRESOL withthe required ADDRESS parameter.New origin originSeverity:Informational.Explanation: NSDBLOAD encountered an $ORIGINstatement in its input file. This origin is used forsubsequent statements.System Action:None.User or Operator Response:Origin definition errorSeverity:Error.None.Explanation: NSDBLOAD encountered an $ORIGINstatement in the input file without an accompanyingdefinition.System Action:NSDBLOAD terminates.User or Operator Response: Correct the $ORIGINstatement in the input data file.RoutineName: Active open successful on connectionconnNumSeverity:Informational.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.User or Operator Response:None.RoutineName: Address conversion failed for 'IPaddress'Severity:Informational.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.User or Operator Response:None.RoutineName: An invalid address (IPaddress) wasspecified in the FORWARDERS statementSeverity: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 errorSeverity:Error.Explanation: This message indicates we received anIUCV interrupt for a function we do not support.System Action:is skipped.User or Operator Response:All processing for the IUCV interruptNoneOrigin has not been definedSeverity:Error.Explanation: A relative domain name defined in theinput file requires a domain origin suffix, but no$ORIGIN statement has been provided.System Action:NSDBLOAD terminates.User or Operator Response: Correct the input file toinclude an "$ORIGIN domainName" statement.RoutineName: Buffer pointer is 'bufferAddress'xSeverity:Informational.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.System Action:Execution continues.20 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesUser or Operator Response: This message can beignored if not accompanied by other messagesindicating an error situation.RoutineName: Cache is FULL - Cannot make anyentriesSeverity:Informational.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 statementsSeverity: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:configuration file.Correct the conflict in theRoutineName: Compressed name continues past end ofpacketSeverity:Informational.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 sothe 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}Severity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: Connection: connNum ForeignAddress: IPaddressSeverity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: connType connection never openedSeverity: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.User or Operator Response:None.RoutineName: Connection connNum closed normallySeverity:Informational.Explanation: The specified connection closed whenexpected. The message is only issued during diagnostictracing.System Action:None.Chapter 2. Domain Name Server and Resolver Messages 21

DNS and Resolver MessagesUser or Operator Response:None.RoutineName: Data length size > UDPBUFSIZESeverity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: dataType data: length is 0Severity: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: Data never delivered on connNumconnectionSeverity: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.User or Operator Response:None.RoutineName: dataType data: no comma or blankSeverity: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:in the SQL tables.Correct the informationRoutineName: DATAdelivered error, bytes = byteCountSeverity: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.User or Operator Response:None.RoutineName: Datagram reply truncatedSeverity: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:User or Operator Response:different name server.The operation is terminated.Route the question to aRoutineName: Data never delivered on connNumconnectionSeverity: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.User or Operator Response:None.RoutineName: Disk re-access before SMSG processingis not availableSeverity:Informational.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 SMSG22 z/VM: TCP/IP Messages and Codes

DNS and Resolver Messagesauthorization 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) bytesmemoryAddress hWord hWord hWord hWord *cData*Severity:Informational.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.System Action:Execution continues.User or Operator Response: The information may beuseful in determining the nature of any problemreported or being diagnosed.RoutineName: Duplicate SQL table name tableNameSeverity: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 databaseSeverity: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.User or Operator Response:None.RoutineName: Error returnCode beginning TCP/IPserviceSeverity: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 calledRoutineSeverity: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.User or Operator Response:None.RoutineName: ErrorinTCPIPservice: errorInfoSeverity: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.User or Operator Response:None.RoutineName: Error opening connection to remotename serverSeverity:Warning.Explanation: An error occurred while attempting toopen a TCP connection to a remote name server. Theoperation that was going to be performed isChapter 2. Domain Name Server and Resolver Messages 23

DNS and Resolver Messagesterminated. 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:User or Operator Response:The operation will be retried.None.RoutineName: FORWARDERS address IPaddressignored, only limit are allowedSeverity:WarningExplanation: 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.User or Operator Response:None.RoutineName:Foreign name server responds withRCODE = rcodeSeverity:WarningExplanation: 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 useSeverity:Informational.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.User or Operator Response:None.RoutineName: Insufficient data availableSeverity: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.User or Operator Response:None.RoutineName: Invalid flags 'xxxx'xSeverity: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 > maxLengthSeverity: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.24 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesRoutineName: Limiting cacheName cache size to newSizeSeverity:Informational.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 EXTSeverity:Informational.Explanation: The name server was shut down by anexternal interrupt, issued with the CP EXT command atthe name server console.System Action:None.User or Operator Response:None.RoutineName: Name server shutting down due toTCP/IPSeverity: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.User or Operator Response:None.RoutineName: name='name', type=type, class=classSeverity:Informational.Explanation: The contents of some of the fields of aresource record are displayed.System Action:None.User or Operator Response:None.RoutineName: New serial value old serial valueSeverity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: Newdomain SOA: serial serial refreshvalueSeverity:Informational.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.System Action:None.User or Operator Response:RoutineName: No data availableSeverity:Warning.None.Explanation: The name server received a datagramwithout data.System Action:User or Operator Response:The datagram is ignored.None.RoutineName: No room: retend memoryAddress retpmemoryAddressSeverity:Informational.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.User or Operator Response:None.RoutineName: No room for InformationTypeSeverity: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 orChapter 2. Domain Name Server and Resolver Messages 25

DNS and Resolver Messagesattempt to obtain the data via TCP.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.User or Operator Response:None.RoutineName: No room for headerSeverity: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.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 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.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:Datagram construction is halted. Thetruncated 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 classSeverity: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.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 host uses the partial packet. Thedata it contains is usually sufficient, and processingcontinues..User or Operator Response:None.RoutineName: No SOA or NS records foundSeverity: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.System Action:None.User or Operator Response: Verify that the zone datacontains the correct SOA and NS resource records.RoutineName: Notice arrives -->Severity:Informational.Explanation: We have just started processing a newpiece of work delivered via the PASCAL API. Themessage is only issued during diagnostic tracing.System Action:None.User or Operator Response:None.26 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesRoutineName: NoticeType notify arrived on connectionconnNumSeverity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: Passive open for port portNumber failed,rc = ReturnCodeSeverity: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 NULLSeverity:Informational.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.System Action:Execution continues.User or Operator Response:None.RoutineName: Purging the entire cacheName cacheSeverity:Informational.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.User or Operator Response:None.RoutineName: qname='name', qtype=type, qclass=classSeverity:Informational.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.System Action:Execution continues.User or Operator Response:None.RoutineName: Raising cacheName cache size limit tonewSizeSeverity:Informational.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.User or Operator Response:None.RoutineName: Request for storage of size bytesOfStorageSeverity:Informational.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.System Action:Execution continues.User or Operator Response:None.RoutineName: Recursion not configured or requestedSeverity:Informational.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.User or Operator Response:None.RoutineName: Received bad packet from IPaddressSeverity:Informational.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 packetsChapter 2. Domain Name Server and Resolver Messages 27

DNS and Resolver Messagesare 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 valueSeverity:Informational.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:and restarted.User or Operator Response:The zone-transfer refresh timer is resetNone.RoutineName: Response from unexpected addressfromAddress, expected expectedAddressSeverity: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.System Action:Execution continues.User or Operator Response:None.RoutineName: Results from TcpStatusSeverity:Informational.Explanation: This is the header line preceding adisplay of the status of a TCP connection. The messageis only issued during diagnostic tracing.System Action:None.User or Operator Response:None.RoutineName: Sending domainName zoneSeverity:Informational.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.System Action:None.User or Operator Response:None.RoutineName: TABLES specified in PRIMARY orSECONDARY statements are conflictingSeverity: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:configuration file.Correct the error in theRoutineName: TCP table not defined, no zones definedSeverity: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 initiatedSeverity:Informational.Explanation: The name server’s TCP/IP initializationwas successful.System Action:None.User or Operator Response:None.RoutineName: tcpclose failed for active conn connNumSeverity:Warning.Explanation: After returning a query answer, thename server fails to close the TCP connection. Theremote host may have already closed the connection.System Action:None.User or Operator Response:None.RoutineName: The following traces are in effect:traceListSeverity:Informational.Explanation: This message shows the list of traces thatare currently active.System Action:None.User or Operator Response:None.28 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesRoutineName: The FORWARDERS statement requiresat least 1 address traceListSeverity: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 connNumSeverity: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.User or Operator Response:None.RoutineName: Timer expired for inactive connectionSeverity:Warning.Explanation: A TIMER expired notification wasreceived for a connection block that is not in use.System Action:notification.User or Operator Response:The name server ignores theNone.RoutineName: ttl=value rdata='value'Severity:Informational.Explanation: The contents of some of the fields of aresource record are displayed.System Action:None.User or Operator Response:None.RoutineName: Unable to find VM password in rdataSeverity: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:User or Operator Response:The SQL update is ignored.None.RoutineName: Unable to extract TCP view informationfromSQL,rc=returnCodeSeverity:Informational.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.User or Operator Response:None.RoutineName: Undefined remote name server for zonedomainNameSeverity: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 stateValueSeverity:Warning.Explanation: The old connection state value was notan expected value.System Action:value.User or Operator Response:The connection state is set to a correctNone.RoutineName: Undefined remote name server for zonedomainNameSeverity: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 questionSeverity: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.Chapter 2. Domain Name Server and Resolver Messages 29

DNS and Resolver MessagesSystem Action: The zone transfer aborts. Name serverexecution continues.User or Operator Response:None.RoutineName: Unexpected notification notificationIDSeverity:Informational.Explanation: An unexpected notification arrived whilewaiting for activity on a connection. The notification IDis displayed.System Action:None.User or Operator Response: This message can beignored if not accompanied by other messagesindicating an error situation.RoutineName: Unexpected query type queryTypeSeverity: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.User or Operator Response:None.RoutineName: Unknown type during SQLfunctionSeverity: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.User or Operator Response:None.RoutineName: Using cache file 'FileId'Severity:Informational.Explanation: The name server is using FileId as theinput file for defining the remote name servers that willbe used in a CACHINGONLY configuration.System Action:None.User or Operator Response:None.RoutineName: Using input file FileIdSeverity:Informational.Explanation: The name server issues this message toindicate what configuration file it is using.System Action:None.User or Operator Response:None.RoutineName: VM id of Name Server Required forIUCVSeverity: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:User or Operator Response:syntax.CMSRESOL halts and exits.Correct the commandRoutineName: VM password is longer than max of 8charsSeverity: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:User or Operator Response:Select remarksSeverity:The SQL update is ignored.Informational.None.Explanation: NSDBLOAD is issuing an SQL SELECTREMARKS command while attempting to determinewhether to update the ″0″ table or the ″1″ table.System Action:Processing continues.User or Operator Response:Table tableName already existsSeverity:Informational.None.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.User or Operator Response:Timeout arg missingSeverity:Error.None.Explanation: A CMSRESOL command line omitted atimeout-interval specification. See TCP/IP User’s Guidefor the syntax of the CMSRESOL command.30 z/VM: TCP/IP Messages and Codes

DNS and Resolver MessagesSystem Action:The CMSRESOL command terminates.User or Operator Response: Verify the correct use ofthe TIMEOUT value in the parameter list.Too many nested parenthesesSeverity: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.System Action:User or Operator Response:of the command.Too many parms in section entrySeverity:Error.The CMSRESOL command terminates.Verify the correct syntaxExplanation: 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.System Action:User or Operator Response:of the command.Too many right parensSeverity:Error.The CMSRESOL command terminates.Verify the correct syntaxExplanation: A CMSRESOL command line containedan incorrect number of right parentheses. See TCP/IPUser’s Guide for the syntax of the CMSRESOLcommand.System Action:User or Operator Response:of the command.The CMSRESOL command terminates.Verify the correct syntaxnature of the problem. Correct the problem and retrythe command.Update statistics on the tableName tableSeverity:Informational.Explanation: NSDBLOAD updates the statistics for thetable just processed after all the records have beenadded.System Action:None.User or Operator Response:Using input file FileNameSeverity:Informational.None.Explanation: NSTABLE and NSDBLOAD issue thismessage to indicate what configuration file they areusing.System Action:None.User or Operator Response:Using sql table tableNameSeverity:Informational.None.Explanation: NSDBLOAD is indicating which SQLtable will be processed.System Action:User or Operator Response:Zone transfer request failedSeverity:Warning.NSDBLOAD continues.None.Explanation: The attempt to connect to a foreign nameto accomplish a zone transfer has failed.System Action:a later time.User or Operator Response:We will try to obtain the zone data atNone.UNEXPECTED SQL ERROR RETURNEDSQLCODE: returnCodeCHANGES WILL BE BACKED OUTFAILING SQL STATEMENT IS:SQLstatementSeverity: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 theChapter 2. Domain Name Server and Resolver Messages 31

DNS and Resolver Messages32 z/VM: TCP/IP Messages and Codes

Chapter 3. FTP Messages|||||||||||||||||||||||||||||||||||||||||This chapter contains File Transfer Protocol (FTP) messages.FTP Server Numbered MessagesDTCFTS0002I Using translate table filenameTCPXLBIN.Severity:Informational.This section contains the numbered messages.Explanation: The FTP server has successfully loadedthe required translation table from the specifiedTCPXLBIN file.System Action:User or Operator Response:Source File:Procedure Name:DTCFTS0003ISeverity:Program execution continues.FTSRVPA PASCALInitializeNone.Using built-in translate tables.Informational.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.System Action:Program execution continues.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.Source File:Procedure Name:FTSRVPA PASCALInitializeDTCFTS0004E Server-FTP: program requires ECMODE ON.Severity:Explanation:Error.System Action:EC MODE is off.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.Source File:Procedure Name:FTSRVPA PASCALInitialize||||||||||||||||||||||||||||||||||DTCFTS0005E Server-FTP: unable to determinevirtual machine IDSeverity:Error.Explanation: FTP cannot determine the servermachine’s virtual ID.System Action:None.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.Source File:Procedure Name:DTCFTS0009ESeverity:Error.FTSRVPA PASCALInitializePort number port_number is not validExplanation: 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.Source File:Procedure Name:FTSRVPA PASCALProcessConfigFileDTCFTS0010I External Security Manager will beusedSeverity:Informational.Explanation: The FTP server will use an ExternalSecurity Manager for authentication purposes.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitialize© Copyright IBM Corp. 1987, 2002 33

|||FTP MessagesDTCFTS0013E Unrecognized configuration filestatement: statement|||DTCFTS0020E Server-FTP cannot do its initialpassive open||||||||||||||||||||||||||||||||||||||||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.System Action:Server initialization stops.User or Operator Response: Delete or correct thestatement that is in error, then restart the FTP server.Source File:Procedure Name:DTCFTS0014ISeverity:FTSRVPA PASCALDoNewCommandUsing port port.InformationalExplanation: The FTP server will listen for FTP clientson the specified port.System Action:User or Operator Response:Source File:Procedure Name:DTCFTS0015ISeverity:Program execution continues.None.FTSVMSUB PASCALSystemInitializeInactivity time is time.Informational.Explanation: The FTP server will use the specifiedamount of time for determining when an inactiveconnection should be closed.System Action:User or Operator Response:Source File:Procedure Name:DTCFTS0019ESeverity:Explanation:initialization.Error.System Action:Program execution continues.None.FTSVMSUB PASCALSystemInitializeUser or Operator Response:resubmit the job.Source File:Procedure Name:Cannot start ServerFtp: ReturnCodeYou received a nonzero return code atThe server program halts.FTSRVPA PASCALMainLoopIdentify the problem and|||||||||||||||||||||||||||||||||||||||||||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 completedDateTimeSeverity:Informational.Explanation: FTP server initialization completed at thespecified date and time.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.FTSRVPA PASCALMainLoopNone.DTCFTS0033E FSENDresponse note shows error:reasonSeverity:Error.Explanation: The FTP server received an error when ittried to send data over a connection. The reasonindicates the problem.System Action:Program execution continues.User or Operator Response: Determine why the datacould not be sent over the connection. If needed,contact your IBM Support Center for assistance.Source File:Procedure Name:DTCFTS0034ESeverity:Error.FTSRVPA PASCALMainLoopFRECEIVEerror note shows: reasonExplanation: The FTP server received an error when ittried to receive data over a connection. The reasonindicates the problem.System Action:Program execution continues.User or Operator Response: Determine why the datacould not be received over the connection. If needed,contact your IBM Support Center for assistance.|||Source File:Procedure Name:FTSRVPA PASCALMainLoop34 z/VM: TCP/IP Messages and Codes

||||||||||||||||||||||||||||||||||||||||||||||DTCFTS0035ISeverity:Error.Connection conn: received note ’type’Explanation: The FTP server received the givennotification type on the specified connection. Thisnotification type is not supported.System Action:Program execution continues.User or Operator Response: Determine why the FTPserver received the specified notification. If needed,contact your IBM Support Center for assistance.Source File:Procedure Name:FTSRVPA PASCALMainLoopDTCFTS260I Using Kanji translate table FileNameFileTypeSeverity:Informational.Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPKJBIN binary translate table file.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitializeDTCFTS0261I Using Hangeul translate tableFileName FileTypeSeverity:Informational.Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPHGBIN binary translate table file.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitializeDTCFTS262I Using TChinese translate table FileNameFileTypeSeverity:Informational.Explanation: The FTP server has successfully loadedthe required DBCS translation table/s from theTCPCHBIN binary translate table file.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitialize||||||||||||||||||||||||||||||||||||||||||||||||||||DTCFTS0263I *** Warning: Could not load the Kanjitranslation tableSeverity: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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS0265I *** Warning: Could not load theHangeul translation tableSeverity: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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS0267I *** Warning: Could not load theTchinese translation tableSeverity:Error.FTP MessagesExplanation: 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. TheChapter 3. FTP Messages 35

||||||||||||||||||||||||||||||||||||||||||||||FTP MessagesTraditional 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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS0300I Unable to determine TCP/IP buffersize; default = 8K.Severity:Informational.Explanation: An error occurred when the FTP serverqueried the stack for the TCP/IP buffer size. A defaultof 8K will be used.System Action:User or Operator Response:Source File:Procedure Name:DTCFTS0307ESeverity:Error.Program execution continues.FTSRVPA PASCALMainLoopNone.Configuration file name is not validExplanation: The configuration file name specifiedwith the SRVRFTP command contains more than eightcharacters.System Action:Server initialization stops.User or Operator Response: Correct the appropriate:Parms. tag entry in the DTCPARMS file, then restartthe FTP server.System Programmer Response:Source File:Procedure Name:DTCFTS0308ESeverity:Error.FTSRVPA PASCALInitConfigsNone.Configuration file type is not validExplanation: The configuration file type specified withthe SRVRFTP command contains more than eightcharacters.System Action:Server initialization stops.User or Operator Response: Correct the appropriate:Parms. tag entry in the DTCPARMS file, then restartthe FTP server.System Programmer Response:Source File:Procedure Name:FTSRVPA PASCALInitConfigsNone.|||||||||||||||||||||||||||||||||||||||||||||||DTCFTS0309ESeverity:Error.Configuration file mode is not validExplanation: The configuration file mode specifiedwith the SRVRFTP command contains more than twocharacters.System Action:Server initialization stops.User or Operator Response: Correct the appropriate:Parms. tag entry in the DTCPARMS file, then restartthe FTP server.System Programmer Response:Source File:Procedure Name:FTSRVPA PASCALInitConfigsNone.DTCFTS0310I Unable to find input file: filenamefiletype filemodeSeverity:Error.Explanation: The configuration file listed in themessage does not exist on any minidisk that has beenaccessed by the FTP server.System Action:Server initialization stops.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.Source File:Procedure Name:FTSRVPA PASCALInitConfigsDTCFTS0311E Invalid numeric operand found:operandSeverity:Error.Explanation: While parsing the FTP serverconfiguration file, the FTP server found the specifiedoperand when it expected to find a number.System Action:Server initialization stops.User or Operator Response: Correct the appropriateconfiguration file statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALErrorDTCFTS0312E Port number not specified for PORTstatementSeverity:Error.Explanation: The PORT statement requires a portnumber to be specified.System Action:Server initialization stops.36 z/VM: TCP/IP Messages and Codes

FTP Messages||User or Operator Response: Correct the configurationfile statement and restart the FTP server.||User or Operator Response: Specify only supportedoptions on the SRVRFTP command.|Source File:FTSRVPA PASCAL|Source File:FTSRVPA PASCAL|Procedure Name:Error|Procedure Name:ParseOptions|||||||||||||||||||DTCFTS0313E Setting not specified for INACTIVEstatementSeverity:Error.Explanation: The INACTIVE statement requires atiming value (in seconds) to be specified.System Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALErrorDTCFTS0314E Translate table not specified forLOADDBCSTABLE statementSeverity:Error.Explanation: The LOADDBCSTABLE statementrequires a valid table name to be specified. For detailedinformation about the LOADDBCSTABLE statement seeTCP/IP Planning and Customization.|||||||||||||||||||DTCFTS0349ESeverity:Error.Translate table table-name is not validExplanation: The indicated translation table is notvalid for the LOADDBCSTABLE statement. For detailedinformation about the LOADDBCSTABLE statement seeTCP/IP Planning and Customization.System Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALProcessConfigFileDTCFTS0358E RDR statement filemode fm is notvalid or is not writableSeverity:Error.Explanation: The indicated file mode is not a valid filemode, or the file mode is valid but is not accessed withread/write status.|System Action:Server initialization stops.|System Action:Server initialization stops.||||||||||||||||||||||User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:DTCFTS0315ESeverity:Error.FTSRVPA PASCALErrorINACTIVE time seconds is not validExplanation: The timing value specified for theINACTIVE statement is not correct. The INACTIVEtime setting must be an integer between 1 and1,048,576.System Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:DTCFTS0317ESeverity:Error.FTSRVPA PASCALErrorUnrecognized option: optionExplanation: An unsupported option was specified onthe SRVRFTP command.System Action:Server initialization stops.|||||||||||||||||||||||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:Procedure Name:FTSRVPA PASCAL, FTSVMSUB PASCALError, SystemInitializeDTCFTS0359I Filemode ’RDRfm’ will be used forreader file supportSeverity:Informational.Explanation: The specified file mode will be used totemporarily store files before they are sent to a virtualreader.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitializeDTCFTS0360E Filemode not specified for RDRstatementSeverity:Error.Explanation: The RDR statement requires a valid filemode to be specified.Chapter 3. FTP Messages 37

|||||||||||||||||||||||||||||||||||||||||||||FTP MessagesSystem Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALErrorDTCFTS0363I DMSESM rc=rc; All minidisk linkswill be performed using native CPsecurity servicesSeverity: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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS0365E 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.System Action:None.User or Operator Response: Contact the systemadministrator for the External Security Manager (ESM)that is in use, for assistance in resolving this problem.Source File:Procedure Name:FTSVMSUB PASCALDoPassDTCFTS0366E Wrong level of CMS: routine notfoundSeverity:Error.Explanation: A CSL routine returned with a -7 returncode, meaning the routine was not found.System Action:User or Operator Response:appropriate level of CMS.Source File:Procedure Name:CheckPasswordThe server program halts at this point.FTSRVPA, FTSVMSUBRe-IPL with theInitialize, SystemInitialize,||||||||||||||||||||||||||||||||||||||||||||||DTCFTS0367E Wrong level of CP: Diagnose 88 notavailableSeverity:Error.Explanation: Diagnose 88 support is not available inthe level of CP that you are running.System Action:User or Operator Response:appropriate level of z/VM.Source File:Procedure Name:The server program halts at this point.FTSVMSUBSystemInitializeUpgrade to theDTCFTS0368I Warning: FTP server is missing classD privileges for virtual reader supportSeverity: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.System Action:Program execution continues.User or Operator Response: If users need to be ableto list or delete virtual reader files, the FTP server mustbe given class D privileges.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS0369E Format type not specified forLISTFORMAT statementSeverity:Error.Explanation: The LISTFORMAT statement requires atype of list format to be specified; valid list formattypes are VM and UNIX.System Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALErrorDTCFTS0370E LISTFORMAT type list_format is notvalidSeverity:Error.Explanation: The indicated type of list format is notvalid for the LISTFORMAT statement. Valid list formattypes are VM and UNIX.System Action:Server initialization stops.|||User or Operator Response: Correct the configurationfile statement and restart the FTP server.38 z/VM: TCP/IP Messages and Codes

FTP Messages|Source File:FTSRVPA PASCAL|System Action:Server initialization stops.|||Procedure Name:DTCFTS0371IErrorDefault list format is format|||User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:FTSRVPA PASCAL|Severity:Informational.|Procedure Name:Error|||||||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.System Action:User or Operator Response:Program execution continues.None.|||||||DTCFTS0376E TIMESTAMP setting timestamp-settingis not validSeverity:Error.Explanation: The indicated type of TIMESTAMPsetting is not valid for the TIMESTAMP statement.Valid TIMESTAMP settings are ON and OFF.|Source File:FTSVMSUB PASCAL|System Action:Server initialization stops.|||||||||||||Procedure Name:SystemInitializeDTCFTS0372E AUTOTRANS setting setting is notvalidSeverity:Error.Explanation: The indicated automatic translationsetting is not valid for the AUTOTRANS statement.Valid automatic translation settings are ON and OFF.System Action:Server initialization stops.User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:FTSRVPA PASCALError|||||||||||||User or Operator Response: Correct the configurationfile statement and restart the FTP server.Source File:Procedure Name:DTCFTS2500ISeverity:FTSRVPA PASCALErrorNewConnectionEvent: Bad state stateInformationalExplanation: NewConnectionEvent was called whenthe connection was in the specified state instead ofCONNECTIONopening state.System Action:Program execution continues.User or Operator Response: Contact your IBMSupport Center for assistance.|||||||||||||||||||||DTCFTS0373I Default automatic translation isturned settingSeverity:Informational.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.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.FTSVMSUB PASCALSystemInitializeDTCFTS0374E Setting not specified forAUTOTRANS statementSeverity:Error.Explanation: The AUTOTRANS statement requires anautomatic translation setting to be specified; validsettings are ON and OFF.||||||||||||||||||||Source File:Procedure Name:FTSEVEN PASCALNewConnectionEventDTCFTS2515I SRVRFTP: timer expired onnon-control connectionSeverity:Error.Explanation: A timer expired on a data connection.There should not be a timer associated with a dataconnection.System Action:Program execution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:DTCFTS2519ESeverity:Error.FTSEVEN PASCALTimerExpiredEventFTP Server shutdown initiated.Explanation: The ShutDownAndDie procedure issuesthis informational message.System Action:When an external interrupt isChapter 3. FTP Messages 39

||||||||||||||||||||||||||||||||||||||||||||||||||FTP Messagesreceived, 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:resubmit the job.Source File:Procedure Name:FTSEVEN PASCALShutDownAndDieCorrect the problem andDTCFTS2520E 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.User or Operator Response:resubmit the job.Source File:Procedure Name:FTSEVEN PASCALShutDownAndDieCorrect the problem andDTCFTS2521E 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.Source File:Procedure Name:FTSEVEN PASCALShutDownAndDie||||||||||||||||||||||||||||||||||||||||||||||||||DTCFTS2522E Enter a second STOP command toshutdown immediatelySeverity: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.Source File:Procedure Name:FTSEVEN PASCALShutDownAndDieDTCFTS2524E 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.User or Operator Response:resubmit the job.Source File:Procedure Name:FTSEVEN PASCALShutDownAndDieCorrect the problem andDTCFTS2582E List format format for User user inCHKIPADR is not validSeverity:Error.Explanation: The indicated type of list format is notvalid for the CHKIPADR exit. Valid list format typesare VM and UNIX.System Action:User or Operator Response:exit.Source File:Program execution continues.FTSVMSUB PASCALCorrect the CHKIPADR||Procedure Name:VMIpAdrChk40 z/VM: TCP/IP Messages and Codes

|||||DTCFTS2583E Format type not specified inLISTFORMAT command for User userin CHKIPADRSeverity:Error.|||||FTP MessagesUser 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.||||||Explanation: The LISTFORMAT statement requires atype of list format to be specified; valid list formattypes are VM and UNIX.System Action:User or Operator Response:exit.Program execution continues.Correct the CHKIPADR||||||Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2601I {LINES | TRANSLATE} value notspecified for VMFILETYPE extensionstatement|Source File:FTSVMSUB PASCAL|Severity:Error.|||||||||||||||||||||||||||||||||||||Procedure Name:VMIpAdrChkDTCFTS2592E AUTOTRANS setting setting for Useruser in CHKIPADR is not validSeverity:Error.Explanation: The indicated automatic translationsetting is not valid for the CHKIPADR exit. Validautomatic translation settings are ON and OFF.System Action:User or Operator Response:exit.Source File:Procedure Name:Program execution continues.FTSVMSUB PASCALVMIpAdrChkCorrect the CHKIPADRDTCFTS2593E Setting not specified forAUTOTRANS command for User user inCHKIPADRSeverity:Error.Explanation: The AUTOTRANS statement requires atype of automatic translation setting to be specified;valid automatic translation settings are ON and OFF.System Action:User or Operator Response:exit.Source File:Procedure Name:Program execution continues.FTSVMSUB PASCALVMIpAdrChkCorrect the CHKIPADRDTCFTS2600I {LINES | TRANSLATE} value notspecified for VMFILETYPEDEFAULTstatementSeverity: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|||||||||||||||||||||||||||||||||||||||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:NoneUser 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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2602I {LINES | TRANSLATE} value valuefor VMFILETYPEDEFAULT statement isnot validSeverity: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.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2603I {LINES | TRANSLATE} value valuefor VMFILETYPE extension statement isnot validSeverity:Error.Explanation: An error exists in the TCPIP DATA file.The indicated value is not supported for use with theChapter 3. FTP Messages 41

||||||||||||||||||||||||||||||||||||||||||||||||FTP MessagesLINES or TRANSLATE parameter. This parameter hasbeen specified as part of the VMFILETYPE statementthat defines translation characteristics for the indicatedfile extension.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 thisstatement, see TCP/IP Planning and Customization.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2604I Parameter parameter specified forVMFILETYPEDEFAULT statement is notrecognizedSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2605I Parameter parameter specified forVMFILETYPE extension statement is notrecognizedSeverity: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.System Action:None.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.Source File:FTSVMSUB PASCAL||||||||||||||||||||||||||||||||||||||||||||||||DTCFTS2606E Unable to processVMFILETYPEDEFAULT statement;DMSTCD rc rc rsc rscSeverity:Error.Explanation: An error occurred while using theDMSTCD CSL routine to process the TCPIP DATA file.System Action:Program execution continues.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.Source File:Procedure Name:FTSVMSUB PASCALProcessFileExtInfoDTCFTS2607E Unable to process VMFILETYPEstatement; DMSTCD rc rc rsc rscSeverity:Error.Explanation: An error occurred while using theDMSTCD CSL routine to process the TCPIP DATA file.System Action:Program execution continues.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.Source File:Procedure Name:FTSVMSUB PASCALProcessFileExtInfoDTCFTS2608I Parameter not specified forVMFILETYPEDEFAULT statementSeverity:Error.Explanation: An error exists in the TCPIP DATA file.The VMFILETYPEDEFAULT statement was specified,but a LINES or TRANSLATE parameter has not beenincluded.System Action:None.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.|Procedure Name:ProcessParms|Source File:FTSVMSUB PASCAL||Procedure Name:ProcessFileExtInfo42 z/VM: TCP/IP Messages and Codes

||||||||||||||||||||||||||||||||||||||||||||||DTCFTS2609I Extension not specified forVMFILETYPE statementSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessFileExtInfoDTCFTS2610I {LINES | TRANSLATE} parameterspecified for VMFILETYPEDEFAULTstatement cannot be repeatedSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2611I {LINES | TRANSLATE} parameterspecified for VMFILETYPE extensionstatement cannot be repeatedSeverity: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.System Action:None.|||||||||||||||||||||||||||||||||||||||||||||||Procedure Name:ProcessParmsDTCFTS2612I {LINES | TRANSLATE} parametersyntax is not correct forVMFILETYPEDEFAULT statement;delimiter '=' is missingSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2613I {LINES | TRANSLATE} parametersyntax is not correct for VMFILETYPEextension statement; delimiter '=' ismissingSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsFTP Messages||||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.|||Source File:FTSVMSUB PASCALChapter 3. FTP Messages 43

|||||||||||FTP MessagesDTCFTS2614I VMFILETYPEDEFAULT statementsyntax is not correct; delimiter 'delimiter'is not validSeverity: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.|||||||||||DTCFTS2623I Wildcard in middle of file extensionFileExt ignoredSeverity:Informational.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.|System Action:None.|System Action:None.|||||||||||||||||||||||||||||||||||||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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2615I VMFILETYPE statement syntax is notcorrect; delimiter ' delimiter' is not validSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALProcessParmsDTCFTS2622I VMFILETYPE extension FileExttruncated to eight charactersSeverity:Informational.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.System Action:None.User or Operator Response:Source File:Procedure Name:None.FTSVMSUB PASCALProcessFileExtInfo|||||||||||||||||||||||||||||||||||||User or Operator Response: Specify separateVMFILETYPE statements for each file extensioncovered by the wildcard.Source File:Procedure Name:DTCFTS4014ESeverity:Explanation:Error.FTSVMSUB PASCALProcessFileExtInfoTime Date: ReturnCodeFTP cannot communicate.System Action: The time, date, and return code reasonare displayed, and the program discontinuesprocessing.User or Operator Response:Source File:Procedure Name:DTCFTS4016ESeverity:Error.FTSUTIL PASCALCheckResultWait and try again.Server-FTP Time Date: ReturnCodeExplanation: This message implies an error in theserver FTP code.System Action:None.User or Operator Response: Ask the systemprogrammer for instructions.System Programmer Response:Support Center.Source File:Procedure Name:FTSUTIL PASCALCheckResultContact the IBMDTCFTS4025I TcpOpen in OpenConnection returnsmessage textExplanation: 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 has44 z/VM: TCP/IP Messages and Codes

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:reasonSeverity:Error.Explanation: The FTP server received an error whentrying to send data over a connection. The reasonindicates the error.System Action:Program execution continues.User or Operator Response: Determine why the stackcannot send data over the connection.Source File:Procedure Name:FTSUTIL PASCALTryToSendDTCFTS7001E Server-FTP: Attempt to open log filereturns ReturnCodeSeverity: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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS7002E 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.System Action:None.User or Operator Response: You can free at least oneaccessing mode to allow this FTP request to beresubmitted.|||||||||||||||||||||||||||||||||||||||||||||||Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS7003I Diagnose 88 authorization and Class Bprivilege confirmedSeverity:Informational.Explanation: The FTP server has Diagnose X’88’ andClass B privileges in order to authenticate FTP serverusers.System Action:User or Operator Response:Source File:Procedure Name:DTCFTS7012ESeverity:Error.Program execution continues.None.FTSVMSUB PASCALSystemInitializeTidyFile: FINIS returns ReturnCodeExplanation: 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:try again.Source File:Procedure Name:DTCFTS7014ESeverity:Error.FTSVMSUB PASCALTidyFileCorrect the problem andCannot determine z/VM levelExplanation: The FTP server tried to determine thelevel of z/VM using the QUERY CPLEVEL command,but the command failed.System Action:Server initialization stops.User or Operator Response: Try to determine why theQUERY CPLEVEL command might have failed. Ifnecessary, contact your IBM Support Center forassistance.Source File:Procedure Name:DTCFTS7015ESeverity:Error.FTSVMSUB PASCALGetReleaseLevelUnsupported z/VM levelExplanation: The FTP server is not supported on thelevel of z/VM that is installed.System Action:System initialization stops.Chapter 3. FTP Messages 45

FTP Messages|||||||||||||||||||||||||||||||||||||||||||||||||User or Operator Response: Install a supported levelof z/VM and restart the FTP server.Source File:Procedure Name:FTSVMSUB PASCALGetReleaseLevelDTCFTS7017I Warning: Cannot setIGNOREincomingPUSH option: reasonSeverity:Informational.Explanation: An error occurred when the FTP servertried to set the IGNOREincomingPUSH option on aconnection. The reason indicates what error occurred.System Action:Program execution continues.User or Operator Response: Determine if other errorsoccurred because the IGNOREincomingPUSH optioncould not be set.Source File:Procedure Name:FTSVMSUB PASCALDoFileDTCFTS7021I IAC Encountered on conn #nn: xxxxSeverity:Informational.Explanation: An IAC control sequence wasencountered on the control connection numbered nn.The actual command encountered is xxxx, wherethefirst byte is the interrupt character (should always bex’FF’) and the second byte is the actual command. Seethe TELNET RFC for details commands.System Action:None.User or Operator Response: None. This is aninformational message encountered in FTP servertraces.Source File:Procedure Name:FTSCMD PASCALDoCommand()DTCFTS7022I Command Received on conn #nn:commandSeverity:Informational.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.System Action:None.User or Operator Response: None;thisisaninformational message encountered in FTP servertraces.System Programmer Response:Source File:FTSCMD PASCALNone.||||||||||||||||||||||||||||||||||||||||||||||||Procedure Name:DoCommand()DTCFTS7023E FTP server is missing class Bprivileges or diagnose 88 authorizationSeverity: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 pointUser or Operator Response: Ensure that the FTPserver virtual machine’s user directory entry includesClass B privileges and an OPTION DIAG88 statement.Source File:Procedure Name:FTSVMSUBSystemInitializeDTCFTS8004I Link Error: DMSLINK owner addr byuser username returns rcSeverity:Error.Explanation: CSL routine DMSLINK had a pagingerror attempting to LINK a minidisk.System Action:None.User or Operator Response: Contact your RACFadministrator to determine the cause of the problem.Source File:Procedure Name:FTSVMSUB PASCALMinidiskLinkDTCFTS8009E DMSLINK Error: VMRDR,Entity=target_user Userid=agent_user,rc=rcSeverity:Error.Explanation: An error occurred when the FTP servertried to link the agent_user to the target_user virtualreader.System Action:Program execution continuesUser 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.Source File:Procedure Name:FTSVMSUB PASCALCheckRDRDTCFTS8101I RACROUTE AUTH call returnsSafRc=Safrc, RacfRc=RacfRc,RacfReas=RacfRscSeverity:Informational.Explanation: The FTP server used the RACROUTEmacro to determine a user’s SFS authorization, but themacro returned an unknown reason code.46 z/VM: TCP/IP Messages and Codes

FTP Messages|System Action:Program execution continues.|Source File:FTSVMSUB PASCAL||||||||||||||||||||||||||||||||||||||||||||||||||||User or Operator Response: Use the reason code fromthe RACROUTE macro to determine what erroroccurred. Contact your IBM Support Center forassistance.Source File:Procedure Name:FTSVMSUB PASCALDoQAuthDTCFTS8104I No CMS Byte File System supportavailableSeverity:Informational.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.Source File:Procedure Name:FTSVMSUB PASCALSystemInitializeDTCFTS8105E 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:SystemTerminateDTCFTS8199E SFSFLAG is on but WorkUnit is zero;System Error.Severity:Explanation:Error.System Action:An internal error occurred.None.User or Operator Response: Close the currentconnection and issue the Open command to re-establishthe connection.Source File:Procedure Name:FTSVMSUB PASCALDoCwdDTCFTS8400I You are not authorized to issuecommands to this serverSeverity: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.System Action:None.User or Operator Response:Source File:Procedure Name:DTCFTS8502ISeverity:Error.FTSEVENSMSGEventNone.Load of FTPExit failed, RC = rcExplanation: 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.System Action:None.User or Operator Response: Correct the problem andtry loading the exit again. Either restart the server oruse the SMSG FTPEXIT RELOAD command.Source File:Procedure Name:FTSVMSUB, FTSEVENSystemInitialize, DoReloadDTCFTS8505I FTPEXIT: Unexpected return, type =ExitType, rc=rcSeverity:Error.Explanation: The Ftp server exit (FTPEXITASSEMBLE) returned to the server with a return codeother than 0, 4, 8, or 12.System Action:None.Chapter 3. FTP Messages 47

|||||||||||||||||FTP MessagesUser or Operator Response: Review the FTPEXITASSEMBLE file and correct the problem; thenreassemble and reload the FTPEXIT routine.Source File:Procedure Name:FTSVMSUB, FTSCMDCallFTPexit, DoCommandDTCFTS8509I FTPExit has been reloaded at addressby userSeverity:Informational.Explanation: The FTPExit has been successfullyreloaded at the specified address because the specifieduser submitted the FTP server SMSG FTPEXITRELOAD command.System Action:User or Operator Response:Source File:Program execution continues.FTSEVEN PASCALNone.FTP Server Unnumbered Messages| Procedure Name: DoReload|| DTCFTS8512E Reload of FTPExit by user failed, RC|= rc| Severity: Error.| Explanation: An error occurred when the FTP server|||tried to reload the FTPExit in response to an FTP serverSMSG FTPEXIT RELOAD command submitted by thespecified user.| System Action: Program execution continues.| User or Operator Response: Use the return code from|||the LOAD instruction to determine why the erroroccurred. If necessary, contact your IBM Support Centerfor assistance.| Source File: FTSEVEN PASCAL| Procedure Name: DoReloadThis 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 validSeverity: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.Source File:Procedure Name:FTSEVEN PASCALDoAutoTransCannot drop connection conn_num - data connectionSeverity:Error.Explanation: The indicated connection numberrepresents a data connection and cannot be dropped.System Action:None.User or Operator Response:Source File:Procedure Name:FTSEVENDoDropNone.Cannot release filemode fm - reserved by the serverSeverity:Explanation:Error.The SMSG RELEASE command wasreceived but the file mode specified is reserved forserver use and cannot be released/detached using thiscommand.System Action:None.User or Operator Response:Source File:Procedure Name:FTSEVENDoReleaseNone.Connection conn_num has already been dropped.Cannot drop connection conn_num - no user oractive user.Severity:Error.Explanation: No active connection exists with theindicated connection number.System Action:None.User or Operator Response:Source File:Procedure Name:FTSEVENDoDropNone.Currently processing PUT to reader. Cannot changereader filemodeSeverity:Error.Explanation: The FTP server RDR file mode cannot bechanged while the FTP server is processing a PUT to areader directory.System Action:None.48 z/VM: TCP/IP Messages and Codes

FTP MessagesUser 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.Source File:Procedure Name:FTSEVEN PASCALDoRDRCurrently 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.System Action:None.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.Source File:Procedure Name:FTSEVEN PASCALDoRDRFilemode fm on RDRmode statement is not valid ornot writableSeverity:Error.Explanation: The indicated file mode is not a valid filemode, or the file mode is valid but is not accessed withread/write status.System Action:None.User or Operator Response: Issue an SMSGRDRmode command that specifies a valid file modethat is accessed by the FTP server in read/write status.Source File:Procedure Name:FTSEVEN PASCALDoRDRFTP connection number conn_num is invalid.No connection number specifiedSeverity: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:NoneUser or Operator Response: Reissue your commandwith an appropriate connection number specified.Source File:Procedure Name:FTSEVENDoDropInvalid 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.System Action:None.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.Source File:Procedure Name:FTSEVENDoReleaseList format list_format is not validSeverity: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:changed.The default server list format is notUser or Operator Response: Issue a valid FTP serverSMSG LISTFORMAT command specifying a valid listformat type.Source File:Procedure Name:No filemode specifiedSeverity:Error.FTSEVEN PASCALDoListFormatExplanation: The SMSG RELEASE command wasreceived but no file mode was specified.System Action:None.User or Operator Response: Issue the SMSGRELEASE command with an appropriate file modespecified.Source File:Procedure Name:FTSEVENNo list format specifiedSeverity:Error.DoReleaseExplanation: 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:changed.The default server list format is notChapter 3. FTP Messages 49

FTP MessagesUser or Operator Response: Issue a valid FTP serverSMSG LISTFORMAT command specifying a valid listformat type.Source File:Procedure Name:FTSEVEN PASCALDoListFormatNo such user user can be foundNo active user can be foundSeverity:Error.Explanation: The user specified is not currently anactive FTP user or there are no active FTP users at thistime.System Action:None.User or Operator Response:Source File:Procedure Name:FTSEVENDoQueryUserNone.REFresh must be followed by VMFiletype keywordSeverity:Error.Explanation: The FTP server SMSG REFresh commandmust have the VMFiletype keyword given.System Action:None.User or Operator Response:VMFiletype command.Source File:Procedure Name:FTSEVEN PASCALDoRefreshTIMESTAMP setting setting is not validSeverity:Explanation:Error.Issue the SMSG REFreshThe indicated type of time stamp settingis not valid for the FTP server SMSG TIMESTAMPcommand. Valid time stamp settings are ON and OFF.System Action:None.User or Operator Response: Issue a valid FTP serverSMSG TIMESTAMP command specifying a valid timestamp setting.Source File:Procedure Name:FTSEVEN PASCALSMSGEventTIMESTAMP setting was not specifiedSeverity:Error.Explanation: The FTP server SMSG TIMESTAMPcommand requires a valid time stamp setting to bespecified. Valid time stamp settings are ON and OFF.System Action:None.User or Operator Response: Issue a valid FTP serverSMSG TIMESTAMP command specifying a valid timestamp setting.Source File:Procedure Name:FTSEVEN PASCALSMSGEventToo many parameters on RDRmode commandSeverity:Error.Explanation: An FTP server SMSG RDRmodecommand was issued specifying too many parameters.System Action:None.User or Operator Response:RDRmode command.Source File:Procedure Name:FTSEVEN PASCALSMSGEventIssue a valid SMSG|||||||||||||FTP Client Numbered MessagesThis section contains the numbered FTP client messages.|DTCFTC0005E Unable to use TCP: reason| DTCFTC0006E Error in init: Handle returns|ReturnCodeSeverity: Error.| Severity: Error.Explanation: An error occurred when the FTP clienttried to begin using TCP/IP services. The reason | Explanation: Program initialization was unsuccessful.indicates what error occurred.| System Action: FTMAIN is exited.System Action: Command execution stops.| User or Operator Response: Check the return codes,User or Operator Response: Ensure that the TCP/IP | correct your input, and resubmit the job.server is running and retry the FTP command.| Source File: FTMAIN PASCALSource File: FTMAIN PASCAL| Procedure Name: InitializeProcedure Name: Initialize50 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||||DTCFTC0015ESeverity:Error.Missing parm after TRANSLATEExplanation: 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:Procedure Name:DTCFTC0018ESeverity:Error.FTPROCS PASCALGetOptionsFTP: Unknown option ’option’Explanation: The FTP command contained thespecified unsupported option.System Action:Command execution continues.User or Operator Response: If needed, quit out of theFTP command and issue an FTP command with asupported option.Source File:Procedure Name:DTCFTC0031ESeverity:Error.FTPROCS PASCALGetOptionsInvalid argument stringExplanation: 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:Source File:Procedure Name:FTUTIL PASCALFtpTokenEnter a valid command.DTCFTC0032E Cannot find closing quote incommand stringSeverity:Error.Explanation: A subcommand was entered with aquoted string but the ending quote could not be found.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Enter a validsubcommand containing a quoted string ensuring thatthe closing quote is present.Source File:FTUTIL PASCAL||||||||||||||||||||||||||||||||||||||||||||||||Procedure Name:DTCFTC0033ESeverity:Error.FtpTokenImageMode: software errorExplanation: An internal error has occurred. The callto the ImageMode procedure is not valid.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:FTPROCS PASCALImageModeDTCFTC0034E ImageMode: can not allocate bufferspaceSeverity:Error.Explanation: The current subcommand cannot beprocessed because the FTP client cannot obtain neededbuffer space.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.Source File:Procedure Name:DTCFTC0035ESeverity:Error.FTPROCS PASCALImageModeImageMode: svc2 error rcExplanation: An error occurred trying to write to afile using the ampxsvc2 procedure.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:FTPROCS PASCALImageModeDTCFTC0038E Software error: unsupported mode:modeSeverity:Error.Explanation: An internal error occurred. TheAsciiToRecord procedure was called with anunsupported transfer type.FTP MessagesChapter 3. FTP Messages 51

FTP Messages|||||||||||||||||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:DTCFTC0039ESeverity:Error.FTPROCS PASCALAsciiToRecordSoftware error: not connectionExplanation: 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.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.|||||||||||||||||||Procedure Name:AsciiToRecordDTCFTC0042E 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.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Ensure the file beingretrieved has the appropriate end of record charactersand reissue the GET subcommand.Source File:Procedure Name:FTPROCS PASCALAsciiToRecordDTCFTC0050E Software error: unsupported mode:mode|Source File:FTPROCS PASCAL|Severity:Error.||||||||||Procedure Name:DTCFTC0040ESeverity:Error.AsciiToRecord, RecordToAsciiCannot allocate buffer spaceExplanation: An error occurred when the FTP clienttried to allocate buffer space to perform the GETsubcommand in stream mode.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.||||||||||Explanation: An internal error occurred. TheRecordToAscii procedure was called with anunsupported transfer type.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:FTPROCS PASCALRecordToAscii||||||||User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.Source File:Procedure Name:DTCFTC0041EFTPROCS PASCALAsciiToRecordCMS write error rc||||||||DTCFTC0051ESeverity:Error.CMS error code rc in LISTFILEExplanation: An error occurred trying to determinethe file mode of a local file.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.|||||||||||Severity:Error.Explanation: An error occurred attempting to use theFSWRITE macro to write to a file.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.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.Source File:FTPROCS PASCAL|||||||||User or Operator Response: Use the return code fromthe CMS LISTFILE command to determine what erroroccurred.Source File:Procedure Name:DTCFTC0052ESeverity:Explanation:Error.FTPROCS PASCALRecordToAsciiCMS error code rc in QUERY DISKAn error occurred trying to determine52 z/VM: TCP/IP Messages and Codes

FTP Messages||disk information using the CMS QUERY DISKcommand.||command execution stops; otherwise commandexecution continues.|||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.|||||User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.Source File:FTPROCS PASCAL|Source File:FTPROCS PASCAL|Procedure Name:RecordToAscii|||||||||Procedure Name:RecordToAsciiDTCFTC0053E Software error: no mode is availableto reaccess the diskSeverity: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.|||||||||DTCFTC0056ESeverity:Error.CMS error code rcExplanation: An error occurred when the FTP clienttried to read data from disk in order to perform a PUTor APPEND.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.|||||||||||||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Release a file mode andreissue the PUT or APPEND subcommand.Source File:Procedure Name:DTCFTC0054ESeverity:Error.FTPROCS PASCALRecordToAsciiCMS error code rc in ACCESSExplanation: 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.|||||||||||||||User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:DTCFTC0061ESeverity:Error.FTPROCS PASCALRecordToAscii, RecordToBlockCMS error code rc in RELEASEExplanation: 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.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.||||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 RELEASE command to determine what erroroccurred. Refer to the z/VM: CMS Command andUtility Reference for further assistance.||||||||||||User or Operator Response: Use the return code fromthe CMS ACCESS command to determine what erroroccurred.Source File:Procedure Name:DTCFTC0055ESeverity:Error.FTPROCS PASCALRecordToAsciiCannot allocate buffer spaceExplanation: 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,|||||||||||||Source File:Procedure Name:DTCFTC0067ESeverity:Error.FTPROCS PASCALRecordToAsciiSoftware error: not connectionExplanation: 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.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response:Contact your IBMChapter 3. FTP Messages 53

||||||||||||||||FTP MessagesSupport Center for assistance.Source File:Procedure Name:DTCFTC0068ESeverity:Error.FTPROCS PASCALRecordToBlockCannot allocate buffer spaceExplanation: An error occurred when the FTP clienttried to allocate buffer space to perform the PUT orAPPEND subcommand in block mode.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.||||||||||||||||DTCFTC0100ESeverity:Error.CMS return code: rcExplanation: The CMS command entered failed withthe specified return code.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Use the return code fromthe CMS command entered to determine what erroroccurred.Source File:Procedure Name:DTCFTC0102ESeverity:Error.FTCVMSUB PASCALDoCMSUnknown host: ForeignName|||||||||||Source File:Procedure Name:DTCFTC0074ESeverity:Error.FTPROCS PASCALRecordToBlockCannot allocate buffer spaceExplanation: An error occurred when the FTP clienttried to allocate buffer space to perform the GETsubcommand in block mode.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.|||||||||||Explanation: The foreign host specified on the OPENsubcommand could not be resolved.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Specify a known host orIP address on the OPEN subcommand.Source File:Procedure Name:DTCFTC0103EFTPROCS PASCALDoConnectNonnumeric port designation: port|||||User or Operator Response: Ensure there is enoughvirtual memory available for the FTP client tosuccessfully complete the subcommand and reissue thesubcommand.Source File:FTPROCS PASCAL|||||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.||||||||||Procedure Name:DTCFTC0081ESeverity:Error.BlockToRecordNotification error: messageExplanation: An error occurred while waiting for adata connection to open.System Action:Command execution continuesUser or Operator Response: Use the message todetermine what error occurred. If needed, contact yourIBM Support Center for assistance.||||||||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Reissue the FTPcommand specifying a valid numeric port.Source File:Procedure Name:DTCFTC0104ESeverity:Error.FTPROCS PASCALDoConnectPort number too large: port||Source File:Procedure Name:FTPROCS PASCALUntilOpen|||Explanation: The port number specified on the FTPcommand is too large. The port number must be anumber in the range of 1 through 65535.||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.54 z/VM: TCP/IP Messages and Codes

FTP Messages||User or Operator Response: Reissue the FTPcommand specifying a valid numeric port.||User or Operator Response: Contact your IBMSupport Center for assistance.|Source File:FTPROCS PASCAL|Source File:FTSYPRO PASCAL|Procedure Name:DoConnect|Procedure Name:GetFromTcp|||||||||||||||||||DTCFTC0192ESeverity:Error.Openfscb: bad modeExplanation: An internal error occurred. TheOpenFscb procedure was called with an invalid mode.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:FTCVMSUB PASCALOpenFscbDTCFTC0198E In SysClose: GetNextNote returns:messageSeverity:Error.Explanation: An error occurred while waiting for aconnection to close.System Action:Command execution continues|||||||||||||||||||DTCFTC0254E Could not initiate emulation of ECmodeSeverity:Error.Explanation: This message is output from theSysPrintError procedure just before FTP shutdown.System Action:None.User or Operator Response:try again.Source File:Procedure Name:DTCFTC0260ESeverity:Error.FTSYPRO PASCALSysPrintErrorCorrect your input andCannot perform MPUT, Disk A is fullExplanation: 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: Use the message todetermine what error occurred. If needed, contact yourIBM Support Center for assistance.|||User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits.|Source File:FTSYPRO PASCAL|Source File:FTCVMSUB PASCAL|Procedure Name:SysClose|Procedure Name:DoMPUT||||||||||||||||||DTCFTC0203ESeverity:Error.Error - should not call closefileExplanation: An internal error occurred. The SysCloseprocedure was called with an invalid mode.System Action:Command execution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:DTCFTC0211ESeverity:Error.FTSYPRO PASCALSysCloseGetFromTcp: not a connectionExplanation: The FTP client tried to get data from aconnection that is not valid or is not in a valid state.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.|||||||||||||||||||DTCFTC0261E Cannot perform MPUT, filemode A isnot accessed or not writableSeverity: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.System Action: The MPUT is not processed and theFTP client continues execution.User or Operator Response: Access a Read/Write diskas filemode A then reissue the command.Source File:Procedure Name:FTCVMSUB PASCALDoMPUTDTCFTC0262E Cannot perform MPUT, LISTFILEcommand failed with a return code rcSeverity:Explanation:Error.In order to process the MPUTChapter 3. FTP Messages 55

||||FTP Messagessubcommand, 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.||||DTCFTC0331E In SendToTcp: GetNextNote returns:messageSeverity:Error.||System Action: The MPUT is not processed and theFTP client continues execution.||Explanation: An error occurred waiting for anotification after sending data to the FTP server.|||User or Operator Response: Check the return codefrom the LISTFILE commnd to determine the reason forthe error.|||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.||||||||Source File:Procedure Name:FTCVMSUB PASCALDoMPUTDTCFTC0278E In SysRead: GetNextNote returns:messageSeverity:Error.Explanation: An error occurred while trying to readdata on a connection.||||||||User or Operator Response: Use the message todetermine what error occurred.Source File:Procedure Name:FTSYPRO PASCALSendToTcpDTCFTC0334E In SendToTcp: Server not responding,closing connection.Severity:Error.|||||||||||||||||||||||||||||||||System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Use the message todetermine what error occured. If needed, contact yourIBM Support Center for assistance.Source File:Procedure Name:FTSYPRO PASCALGetFromTcp, SysReadDTCFTC0281E 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.Source File:Procedure Name:FTPROCS PASCALRecordToAscii()|||||||||||||||||||||||||||||||||||Explanation: The connection timed out while trying tosend data to the FTP server.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Determine why theconnection timed out without completing the datatransfer successfully.Source File:Procedure Name:FTSYPRO PASCALSendToTcpDTCFTC0357E 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 source56 z/VM: TCP/IP Messages and Codes

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.Source File:Procedure Name:FTPROCS PASCALAsciiToRecordDTCFTC0358E 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.System Action:None.User or Operator Response:Source File:None.FTSVMSUB PASCAL, FTPROCS PASCALDTCFTC0360E 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.System Action:None.User or Operator Response: Change to another localdirectory or contact the directory owner to gain properauthorization to the file.Source File:Procedure Name:FTSYPRO PASCALSysPrintErrorDTCFTC0368E 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.||||||||||||||||||||||||||||||||||||||||||||||System Action:None.User or Operator Response: Specify a device type ofDisk or Terminal and try again.Source File:Procedure Name:FTCVMSUB PASCALInputOutputDTCFTC0376E Wrong level of CMS: routine notfoundSeverity:Error.Explanation: A CSL routine returned with a -7 returncode, meaning the routine was not found.System Action:User or Operator Response:appropriate level of CMS.Source File:Procedure Name:Command execution stops.FTMAIN PASCALInitializeRe-IPL with theDTCFTC0391E File transfer aborted. Shortage of diskspaceSeverity: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.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Ensure there is enoughspace on the local disk and reissue the GETsubcommand.Source File:Procedure Name:ImageModeFTPROCS PASCALAsciiToRecord, BlockToRecord,DTCFTC0392E File transfer aborted. Input string istoo longSeverity:Error.Explanation: The data transfer associated with a GETcommand has been aborted because the input buffer istoo large.System Action: If the command exit option is in use,command execution stops; otherwise commandexecution continues.User or Operator Response: Contact your IBMSupport Center for assistance.Source File:Procedure Name:FTPROCS PASCALAsciiToRecordChapter 3. FTP Messages 57

|||||||||||||||||||||||||||||||||||||||||||||||||||FTP MessagesFTP Client Unnumbered MessagesCannot load HANGEUL translate table fileSeverity:Informational.This section contains the unnumbered FTP client messages. Messages in thissection do not contain headers as headers would not be seen when they are issued.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.Source File:Procedure Name:FTMAIN PASCALInitializeCannot load KANJI translate table fileSeverity:Informational.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.Source File:Procedure Name:FTMAIN PASCALInitializeCannot load TCHINESE translate table fileSeverity:Informational.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.Source File:Procedure Name:FTMAIN PASCALInitializeCannot 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.System Action:None.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.Source File:Procedure Name:FTCVMSUB PASCALOpenInputOutputData connections will be initiated by the clientSeverity:Explanation:accepted.Informational.The PASSIVE subcommand has beenSystem Action: Data transfers will be performed inpassive mode. Processing continues normally.User or Operator Response:Source File:Procedure Name:FTPROCS PASCALDoPassiveNone.DIR/LS unimplemented in either Block Mode orImage TypeSeverity:Explanation:Informational.While preparing to issue a DIR or LS58 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||||||||||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.Source File:Procedure Name:FTPROCS PASCALGetDIRFILEDEF '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.System Action:None.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.Source File:Procedure Name:FTCVMSUB PASCALOpenInputOutput|||||||||||||||||||||||||||||||||||||||||||||||FSENDresponse note shows error: reasonSeverity:Informational.Explanation: An error occurred when trying to senddata to the remote FTP server.System Action:Command execution continues.User or Operator Response: Use the reason todetermine what error occurred. If necessary, contactyour IBM Suport Center for assistance.Source File:Procedure Name:FTSYPRO PASCALSendToTcpFTP DATA token CCONNTIME out of range -Default value used.Severity:Informational.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:Procedure Name:FTBVMSUB PASCALReadVMFtpDataFTP DATA token DATACTTIME out of range -Default value used.Severity:Informational.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.Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataFTP DATA token DCONNTIME out of range -Default value used.Severity:Informational.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:FTP MessagesIf necessary, terminateChapter 3. FTP Messages 59

||||||||||||||||||||||||||FTP Messagesthe FTP session and correct the DCONNTIME keywordvalue in the FTP DATA file.Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataFTP DATA token INACTTIME out of range - Defaultvalue used.Severity:Informational.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.Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataFTP DATA token MYOPENTIME out of range -Default value usedSeverity:Informational.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.||||||||||||||||||||||||||In UntilOpen: Passive Open for Fd conn TimeoutSeverity:Informational.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.Source File:Procedure Name:FTPROCS PASCALUntilOpenInvalid local file name FileName; Use name.type .modeor name.typeSeverity:Warning.Explanation: User warning instructing you aboutimproper usage of the Use instruction.System Action:None.User or Operator Response:instructions.Source File:Procedure Name:Follow the UseFTPROCS PASCAL, FTSYPRO PASCALDomPutLocal file not found or cannot be accessed||||||||User or Operator Response: If necessary, terminatethe FTP session and correct the MYOPENTIMEkeyword value in the FTP DATA file.Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataIn ReadVMFtpData: FTP DATA file not available -Default values used||||||||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.System Action:None.|||||||||||||||Severity:Informational.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.Source File:Procedure Name:FTMAIN PASCALMainLoop||||||||||||||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:Procedure Name:FRSYPRO PASCALSysPrintErrorLogon 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 the60 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||host specified as part of your command.System Action:Command execution stops.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:Procedure Name:FTMAINMainLoopTimeOut value out of range. Must be between 15 and720. Default Used.Severity:Informational.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:Procedure Name:FTPARSE PASCALGetOptionsTimeOut xx is not a numerical number. Default Used.Severity:Informational.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.Source File:Procedure Name:FTPARSE PASCALGetOptionsUnable to determine TCP/IP buffer size; default = 8K.Severity:Informational.Explanation: An error occurred when the FTP clientqueried the stack for the TCP/IP buffer size. A defaultof 8K will be used.System Action:User or Operator Response:Source File:Procedure Name:Command execution continues.FTMAIN PASCALInitializeNone.||||||||||||||||||||||||||||||||||||||||||||||||||Unknown Translate table table specified in FTP DATAfile - token ignoredSeverity:Informational.Explanation: An unsupported translate table namewas specified on the LOADDBCSTABLE statement inthe FTP DATA file. The statement is ignored.System Action:Command execution continues.User or Operator Response: If needed, quit out of theFTP command, ensure that the LOADDBCSTABLEstatement is correct, and reissue the FTP command.Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataUnknown Token token in FTP DATA file - TokenIgnored.Severity:Informational.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).Source File:Procedure Name:FTBVMSUB PASCALReadVMFtpDataUsage: HANGEUL Usage: HANGEUL change file transfer type to HangeulSeverity:Informational.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.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypesFTP MessagesChapter 3. FTP Messages 61

|||||||||||||||||||||||||||||||||||||||||||||||||||FTP MessagesUsage: JIS83KJ Usage: JIS83KJ change file transfer type to JIS 1983 KanjiSeverity:Informational.Explanation: Either help for the FTP client JIS83KJsubcommand was requested, or an invalid FTP clientJIS83KJ 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 JIS83KJ subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypesUsage: JIS78KJ Usage: JIS78KJ >change file transfer type to JIS 1978 KanjiSeverity:Informational.Explanation: Either help for the FTP client JIS78KJsubcommand was requested, or an invalid FTP clientJIS78KJ 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 JIS78KJ subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypesUsage: KSC5601 Usage: KSC5601 >(NOTYPE>change file transfer type to KSC5601Severity:Informational.Explanation: Either help for the FTP client KSC5601subcommand was requested, or an invalid FTP clientKSC5601 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 KSC5601 subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypes||||||||||||||||||||||||||||||||||||||||||||||||Usage: TCHINESE Usage: TCHINESE change file transfer type to Traditional ChineseSeverity:Informational.Explanation: Either help for the FTP client TCHINESEsubcommand was requested, or an invalid FTP clientTCHINESE 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 TCHINESE subcommand. See theTCP/IP User’s Guide book for more information aboutusing FTP client subcommands.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypesUsage: TYPE {A |E|I|F|B}Severity:Informational.Explanation: Either help for the FTP client TYPEsubcommand was requested, or an invalid FTP clientTYPE 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 TYPE subcommand. See the TCP/IPUser’s Guide book for more information about usingFTP client subcommands.Source File:Procedure Name:FTPROCS PASCALDoHelp or DoTypesWarning: Cannot set IGNOREincomingPUSH option:reasonSeverity:Informational.Explanation: An error occurred when the FTP clienttried to set the IGNOREincomingPUSH option on aconnection. The reason indicates what error occurred.System Action:Command execution continues.User or Operator Response: Determine if other errorsoccurred because the IGNOREincomingPUSH optioncould not be set.Source File:Procedure Name:FTPROCS PASCALDoTrFile, GetDirWidth ’width’ is not numeric; Default value is in effectSeverity:Explanation:Informational.The value specified for the WIDTH62 z/VM: TCP/IP Messages and Codes

|||||||||||||||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.Source File:Procedure Name:FTPARSE PASCALGetOptionsWidth ’width’ is not within the range 1 to 32767;Default value is in effectSeverity:Explanation:Informational.The value specified for the WIDTHFTP Reply Code 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.Source File:Procedure Name:FTPARSE PASCALGetOptionsFTP 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 HangeulSeverity:Informational.Explanation: The FTP server has received a validTYPEB5commandfromtheFTPclient. The currenttransfer type has successfully been changed to HangeulDBCS.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.200 Representation type is KANJI JIS 1978 shift-inASCIISeverity:Informational.Explanation: The FTP server has received a validTYPEB4orTYPE 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.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.200 Representation type is KANJI JIS 1978 shift-inJISROMANSeverity:Informational.Explanation: The FTP server has received a validTYPEB4RcommandfromtheFTPclient. The currenttransfer type has successfully been changed to JIS 1978Kanji DBCS, using the JISROMAN shift-in escapesequence.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.200 Representation type is KANJI JIS 1983 shift-inASCIISeverity:Informational.Explanation: The FTP server has received a validTYPEB3orTYPE 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.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.Chapter 3. FTP Messages 63

FTP Messages200 Representation type is KANJI JIS 1983 shift-inJISROMANSeverity:Informational.Explanation: The FTP server has received a validTYPEB3RcommandfromtheFTPclient. The currenttransfer type has successfully been changed to JIS 1983Kanji DBCS, using the JISROMAN shift-in escapesequence.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.200 Representation type is KSC-5601Severity:Informational.Explanation: The FTP server has received a validTYPEB6commandfromtheFTPclient. The currenttransfer type has successfully been changed to KoreanStandard Code KSC-5601 DBCS.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.200 Representation type is TChineseSeverity:Informational.Explanation: The FTP server has received a validTYPEB7commandfromtheFTPclient. The currenttransfer type has successfully been changed toTraditional Chinese (5550) DBCS.System Action: Program execution continues. Thecurrent FTP transfer type is changed.User or Operator Response:Source File:Procedure Name:FTSCMD PASCALDoTypeNone.220 User UserName has Acc_Type authoritySeverity:Explanation:of the user.System Action:Informational.The message displays the authority levelNone.User or Operator Response: This is an informationalmessage from the SITE QAUTH command.Source File:FTSVMSUB PASCALProcedure Name:DoSite230 Directory userid.RDR does not existSeverity:Error.Explanation: The user ID entered is not a valid userID on that system.System Action:None.User or Operator Response: Correct the user IDportion of the working directory established for youruser ID in CHKIPADR EXEC.Source File:Procedure Name:FTSVMSUBDoPass230 System error 24 occured trying to access directorySeverity:Error.Explanation: Routine DMSLINK returned with areturn code 24. A paging error has occurred.System Action:console.User or Operator Response:RACF administrator.Source File:Procedure Name:A message is written to the FTP serverFTSVMSUB PASCALDoPassContact your system or230 System error occurred setting up a readerdirectorySeverity:Error.Explanation: An error occurred defining a virtualpunch or issuing a spool command to the target user’sreader.System Action:None.User or Operator Response: Reissue the commandand if the error reoccurs, contact your TCP/IPadministrator to debug the problem.Source File:Procedure Name:FTSVMSUB PASCALDoPass230 You are not authorized for userid.RDRSeverity:Error.Explanation: You do not have the authority to accessthe user’s reader.System Action:None.User or Operator Response:Source File:Procedure Name:FTSVMSUBDoPassNone.64 z/VM: TCP/IP Messages and Codes

FTP Messages421 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.Source File:Procedure Name:FTPROCS PASCALDoNoop425 Can’t open data connection: ReturnCodeSeverity:Explanation:Error.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.Source File:Procedure Name:FTSVMSUB PASCALDoList450 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.System Action:None.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:Procedure Name:FTSCMD PASCAL, FTSVMSUB PASCALDoRnto, DoDelete; DoFile450 Directory is temporarily unavailable, SFSdirectory lock detected.Severity:Error.Explanation: The FTP Server is unable to issue CMSACCESS for the directory.System Action:None.User or Operator Response: Try to enter thecommand a few more times. if the lock persists, try toresolve the lock conflict. Enter the QUERY LOCKcommand to find out which user is holding the lock.Source File:Procedure Name:FTSVMSUB PASCALFindMode, DoList450 Disk access fails; you no longer have any workingdirectorySeverity: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.System Action:None.User or Operator Response: The working directoryminidisk is not in write mode access. Correct thesituation and try again.Source File:Procedure Name:FTSVMSUB PASCALDoAcct450 Insufficient resources to process requested actionSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALFindMode450 Minidisk temporarily unavailableSeverity:Error.Explanation: The system cannot access the VMminidisk containing the working directory. Thistemporary problem is probably caused by VMperformance.System Action:None.User or Operator Response:again.Source File:Procedure Name:FTSVMSUB PASCALFindModeWait for a while and tryChapter 3. FTP Messages 65

FTP Messages450 Minidisk unexpectedly inaccessibleSeverity:Error.Explanation: This VM system problem is probablycaused by multiple, concurrent, minidisk accessrequests. The working directory minidisk cannot bere-accessed.System Action:None.User or Operator Response:again.Source File:Procedure Name:FTSVMSUB PASCALFindModeWait for a while and try450 No current working directory definedSeverity:Error.Explanation: You must define a working directory forFTP processing.System Action:None.User or Operator Response:directory before proceeding.Source File:Procedure Name:FTSVMSUB PASCALFindModeDefine a working450 Rename 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.System Action:None.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:Procedure Name:FTSCMD PASCAL, FTSVMSUB PASCALDoRnto, DoDelete; DoFile450 Store 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.System Action:None.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:Procedure Name:FTSCMD PASCAL, FTSVMSUB PASCALDoRnto, DoDelete; DoFile450 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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALDoFile450 Store failed, unable to access the directory.Severity:Explanation:directory.Error.System Action:The FTP Server cannot access the SFSNone.User or Operator Response: Make sure you areauthorized for the file pool and determine the status ofthe file pool.Source File:Procedure Name:FTSVMSUB PASCALDoFile450 System error occurred trying to determine BFSauthorizationSeverity: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 PASCAL66 z/VM: TCP/IP Messages and Codes

FTP MessagesProcedure Name: DoSite, DoFile, CDtoBFS, SendData,DataArrivedEvent450 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.System Action:None.User or Operator Response:again.Source File:Procedure Name:FTSVMSUB PASCALDoFile451 Data transfer aborted: file is locked.Severity:Error.Wait for a while and tryExplanation: Return code 70 trying to write to the file;file is locked.System Action:None.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.Source File:FTSEVEN PASCALProcedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent451 Data transfer aborted: not authorized to write tofileSeverity: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.System Action:None.User or Operator Response: Change to anotherdirectory or contact the directory owner to gain properauthorization to the file or directory.Source File:FTSEVEN PASCALProcedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent,NewConnectionEvent451 Error closing BFS data set. System error.Severity:Explanation:Error.BFS System Error.System Action:None.User or Operator Response: Retry the command. Ifthe problem persists, contact your system supportpersonnel.Source File:Procedure Name:FTSUTIL PASCALDataReply451 Error closing data set. File not open or invalid ornot authorizedSeverity:Error.Explanation: Error occurred on the CMS FINIScommand. File was not found.System Action:None.User or Operator Response: Retry the command. Ifthe problem persists, contact your system supportpersonnel.Source File:Procedure Name:FTSUTIL PASCALDataReply451 Error closing SFS data set. Rollback performedSeverity:Explanation:SFS files.Error.SFS Error occurred closing one or moreSystem 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.Source File:Procedure Name:FTSUTIL PASCALDataReply451 Error closing SFS data set. System error.Severity:Explanation:Error.System Action:SFS System Error.None.User or Operator Response: Retry the command. Ifthe problem persists, contact your system supportpersonnel.Source File:Procedure Name:FTSUTIL PASCALDataReply451 Error closing SFS data set. System limit exceeded.Severity:Error.Explanation: System limits were exceeded whenattempting to commit the changes.Chapter 3. FTP Messages 67

FTP MessagesSystem Action:User or Operator Response:support personnel.Source File:Procedure Name:The SFS work unit was rolled back.FTSUTIL PASCALDataReplyContact you system451 Error writing or closing reader file.Severity:Error.Explanation: An error occurred trying to write to orclose a spool file.System Action:None.User or Operator Response: Reissue the commandand if the error reoccurs, contact your TCP/IPadministrator to debug the problem.Source File:Procedure Name:FTSUTIL PASCALDataReply451 Transfer aborted: file not found, disk notaccessed, or insufficient authority.Severity:Error.Explanation: Bad return code encountered whilereading the file.System Action:None.User or Operator Response: Check to make sure filewas specified correctly and issue SITE QAUTH to makesure you have the proper authority.Source File:Procedure Name:FTSUTIL PASCALSenddata451 Unexpected software errorSeverity: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.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.Source File:Procedure Name:FTSVMSUB PASCALDoList451 Unexpected system errorSeverity:Error.Explanation: This message indicates that a nonzeroreturn code was generated during the processing of anFTP server request. None of the built-in error checkingfunctions could determine the cause of the problem.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.Source File:Procedure Name:FTSVMSUB PASCALDoList452 The disk used to temporarily store reader fileshas insufficient space availableSeverity:Error.Explanation: An error occurred trying to STOR a filetoaVMreader.System Action:console.A message is written to the FTP serverUser or Operator Response: Contact your systemadministrator to increase the size of the disk identifiedon the RDR startup parameter.Source File:Procedure Name:FTSVMSUBDoFile500 Unknown commandSeverity:Explanation:command.Error.System Action:You entered an unrecognizableNone.User or Operator Response: Examine your inputsyntax to identify and correct your error.Source File:Procedure Name:FTSVMSUB PASCALDoFile501 ACCT not allowed with SFS or BFS directoriesSeverity: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.System Action:None.User or Operator Response: In order to use the ACCTcommand, the current working directory must bechanged to a minidisk using the CWD command.Source File:Procedure Name:FTSVMSUB PASCALDoAcct68 z/VM: TCP/IP Messages and Codes

FTP Messages501 Directory userid.RDR does not exist;Directory remains old_directorySeverity:Error.Explanation: The user ID entered is not a valid userID on that system.System Action:None.User or Operator Response:reenter the command.Source File:Procedure Name:FTSVMSUBCDtoRDRCorrect the user ID and501 Error occurred attempting to purge spool filennnn, rc=rcSeverity:Error.Explanation: An error occurred on the CP PURGEuserid RDR spool ID command.System Action:None.User or Operator Response: Check the return codeand determine the reason for the error.Source File:Procedure Name:FTSCMDDoDelete501 Invalid BYUSER name in USER command501 BYUSER name is missing from USERcommandSeverity:Error.Explanation: BYUSER name was specified an asterisk(*) or was missing from the USER command.System Action:None.User or Operator Response:reenter the command.Source File:Procedure Name:FTSCMDDoUserCorrect the syntax and501 Invalid character in file name BadFileNameSeverity:Error.Explanation: You have made a syntax error in thelisted file name identifier.System Action:None.User or Operator Response:resubmit the job.Source File:Procedure Name:FTSVMSUB PASCALDoListCorrect your syntax and501 Invalid directory suppliedSeverity: Error.Explanation: The account command failed becauseyou requested a working directory that is not valid.System Action: None.User or Operator Response: Check your input logicand syntax, then resubmit the command.Source File: FTSVMSUB PASCALProcedure Name: DoCwd501 Invalid file identifier; use ‘name.type’Severity: Error.Explanation: You entered an incorrect file type andthe file type is not set to the default.System Action: None.User or Operator Response: Reenter the commandand follow the usage instructions.Source File: FTSVMSUB PASCALProcedure Name: DoList501 Invalid file identifier. Use "name.type"Severity: Error.Explanation: You entered an incorrect file type andthe file type is not set to the default.System Action: None.User or Operator Response: Reenter the commandand follow the usage instructions.Source File: FTSVMSUB PASCALProcedure Name: DoFile501 Invalid spoolid in Delete commandSeverity: Error.Explanation: The spool file ID entered is not valid.System Action: None.User or Operator Response: Correct the syntax andreenter the command.Source File: FTSCMDProcedure Name: DoDelete501 No minidisk password supplied with ‘ACCT’Severity: Error.Explanation: You must enter a password with theaccount command.System Action: None.Chapter 3. FTP Messages 69

FTP MessagesUser or Operator Response: Reenter the accountcommand and supply a valid minidisk password.Source File:Procedure Name:FTSVMSUB PASCALDoAcct501 Password missing in PASS commandSeverity:Explanation:Error.System Action:You did not enter your password.None.User or Operator Response:for the user ID requested.Source File:Procedure Name:FTSVMSUB PASCALDoPassEnter a valid password502 Command failed. You are not authorized to viewor delete filesSeverity:Error.Explanation: The subcommand entered was for a VMreader directory, to which you are not authorized.System Action:None.User or Operator Response: Login as the user whoseVM reader you wish to manipulate.Source File:Procedure Name:FTSVMSUBDoList, DoDelete502 Command not supported for VM reader filesSeverity:Error.Explanation: The subcommand entered is notimplemented for VM reader files.System Action:None.User or Operator Response: Use Telnet instead of FTPto manipulate VM reader files.Source File:Procedure Name:FTSCMD, FTSVMSUBDoRnFr, DoCwd, DoFile502 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.System Action:None.User or Operator Response: Use Telnet instead of FTPto manipulate VM reader files or contact the systemadministrator to enable FTP reader support.Source File:FTSVMSUBProcedure Name:502 textSeverity:Error.DoFileExplanation: The FTP user exit has rejected thesubcommand. text provides more information about theerror.System Action:None.User or Operator Response:Source File:Procedure Name:None.FTSCMD, FTSVMSUBDoCommand, CallFTPexit503 Your InterNet Address is not allowed forthis server503 Your UserId is not authorized for this serverSeverity:Fatal.Explanation: The FTP server CHKIPADR exit hasrejected your InterNet Address and user ID.System Action:None.User or Operator Response:support personnel.Source File:Procedure Name:FTSCMD PASCALVMIpAdrChkContact your system504 Block mode implemented with type EBCDIC onlySeverity:Error.Explanation: A file transfer in block mode has beenattempted with a file transfer type of something otherthan EBCDIC.System Action:None.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).Source File:Procedure Name:FTSVMSUB PASCALDoFile504 Type not Supported: Translation Table is notLoaded.Severity:Informational.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.System Action: Program execution continues. Thecurrent FTP transfer type is unchanged.User or Operator Response:Configure a valid DBCS70 z/VM: TCP/IP Messages and Codes

FTP Messagesbinary 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.Source File:Procedure Name:FTSCMD PASCALDoType504 Unknown Shift-in option optionSeverity:Informational.Explanation: The FTP server received a TYPE B3orTYPEB4commandfromtheFTPclient 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.System Action: Program execution continues. Thecurrent FTP transfer type is unchanged.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.Source File:Procedure Name:FTSCMD PASCALDoType521 Directory already exists, taking no action.Severity:Error.Explanation: You specified a MKDIR command for adirectory that already exists.System Action:None.User or Operator Response: Reissue the MKDIRcommand for a new directory or rename the existingdirectory.Source File:Procedure Name:FTSVMSUB PASCALDoMkDir530 A system error occurred during passwordvalidation; Login rejectedSeverity: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:server console.User or Operator Response:RACF administrator.Source File:A message is displayed on the FTPFTSVMSUB PASCALContact your system orProcedure Name:DoPass530 Login attempt by UserName rejected530 Login attempt of UserName byByUserName rejectedSeverity:Explanation:password.Error.System Action:You entered an incorrect login or logonNone.User or Operator Response:logon password.Source File:Procedure Name:FTSVMSUB PASCALDoPassEnter the correct login or530 Login attempt by UserName rejected; passwordexpired530 Login attempt of UserName by ByUserNamerejected;password expiredSeverity:Explanation:Error.System Action:Your login password has expired.None.User or Operator Response: You must logon to theVM user ID to change the pasword, it cannot bechanged through FTP.Source File:Procedure Name:FTSVMSUB PASCALDoPass532 Before action files on Owner Address, you mustsupply the write password using the ACCT commandSeverity: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.Source File:Procedure Name:FTSVMSUB PASCALUpGradeLinkChapter 3. FTP Messages 71

FTP Messages532 Invalid password; Owner Address remainsReadOnlySeverity:Error.Explanation: The listed working directory minidisk isaccessed in a read-only mode because you did notenter a correct minidisk password.System Action:None.User or Operator Response:minidisk password.Source File:Procedure Name:FTSVMSUB PASCALDoAcct532 Invalid password; WorkingDirectorySeverity:Error.Enter a valid accountExplanation: You entered an incorrect password forthe referenced minidisk working directory.System Action:None.User or Operator Response:Source File:Procedure Name:FTSVMSUB PASCALDoAcctEnter a valid password.532 System error 24 occurred trying to access directorySeverity: 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.Source File: FTSVMSUB PascalProcedure Name: DoAcct550 ACCT fails: WorkingDirectorySeverity: Error.Explanation: The account command failed becauseyou do not have the proper RACF authority.System Action: None.User or Operator Response: Check with your RACFadministrator for the proper authority.Source File: FTSVMSUB PASCALProcedure Name: DoAcct532 Permission denied to LINK to NewOwnerNewAddressSeverity:Error.Explanation: The account command failed becauseyou did not have RACF authority to write-link thelisted working directory minidisk.System Action:None.User or Operator Response: Check with your RACFadministrator for the proper authority.Source File:Procedure Name:FTSVMSUB PASCALDoAcct532 Permission denied for write LINK to NewOwnerNewAddressSeverity:Error.Explanation: The account command failed becauseyou did not have RACF authority to write-link thelisted working directory minidisk.System Action:None.User or Operator Response: Check with your RACFadministrator for the proper authority.Source File:Procedure Name:FTSVMSUB PASCALDoAcct550 Attempt to rename ’RnfrBFSFile’ to ’RntoBFSFile’has failedSeverity: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.System Action:None.User or Operator Response: Use the SITE PERMITcommand to check your current authorization, and tryto determine why the OPENVM RENAME failed.Source File:Procedure Name:FTSCMD PASCALDoRnto550 AUTOTRANS setting setting is not validSeverity:Error.Explanation: The indicated automatic translationsetting is not valid for the AUTOTRANS operand. Validsettings are ON and OFF.System Action:None.User or Operator Response: Specify a valid setting(ON or OFF) when the SITE AUTOTRANSsubcommand is issued.Source File:Procedure Name:FTSVMSUB PASCALDoAutoTrans72 z/VM: TCP/IP Messages and Codes

FTP Messages550 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.System Action:None.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.Source File:Procedure Name:550 BFS directory errorSeverity:Error.FTSVMSUB PASCALCDtoBFSExplanation: 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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALDoList550 BFS file (’BFSfile’) not foundSeverity:Explanation:Error.System Action:The specified BFS file does not exist.None.User or Operator Response: The command that wasentered requires a BFS file identifier for an existing file.Source File:Procedure Name:FTSVMSUB PASCALParseBFSIdentifier550 Cannot get SFS WorkUnit; directory remainsworking directorySeverity:Error.Explanation: The FTP Server attempted to get an SFSworkunit and failed. Either no workunit IDs areavailable or there is no storage available for associatinga user ID with a workunit.System Action:None.User or Operator Response: Contact your systemsupport personnel. They may have to re-IPL the FTPserver virtual machine to make some workunits IDsavailable.Source File:Procedure Name:FTSVMSUB PASCALDoCwd, DoPass550 Command fails; LINK command returnedReturnCode; WorkingDirectorySeverity:Error.Explanation: You cannot do a write-link to the listedminidisk for the specified reason.System Action:None.User or Operator Response: Correct your link logic,your syntax, or try another minidisk.Source File:Procedure Name:FTSVMSUB PASCALDoCwd550 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 directoryis locked.Severity:Explanation:Error.System Action:A lock exists on the file or the directory.None.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:Procedure Name:FTSVMSUB PASCAL, FTSCMD PASCALFileOk; DoDelete, DoRnto550 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.System Action:None.Chapter 3. FTP Messages 73

FTP MessagesUser or Operator Response: See the z/VM: CMSCommand and Utility Reference for more information onthe DIRATTR command.Source File:Procedure Name:FTSVMSUB PASCALDoSite550 Error opening file: File has invalid recordformat550 Error opening file: Insufficient virtual storageavailable550 Error opening file: APPC/VM error550 Error opening file: File sharing conflict550 Error opening file: A required system resourceis unavailable550 Error opening file: File cannot be opened forREPLACE. (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.System Action:None.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:PASCALProcedure Name:FTSVMSUB PASCAL, FTBVMSUBSOpenFscb, OpenFscb550 Error rsc reading filename TCPXLBIN from disk ordirectorySeverity:Error.Explanation: The server was unable to read thetranslate table. The reason code contains the returncode from the failing FSOPEN or FSREAD macro.System Action:None.User or Operator Response: Try to determine why thespecified translate table could not be read and correctthe problem.Source File:Procedure Name:FTSRVPA, FTSVMSUB550 FileName does not exist.Severity:Error.Initialize, DoSite2Explanation: FTP cannot find the file you marked fordeletion on any of the accessed minidisks.System Action:None.User or Operator Response:and try again.Correct your input syntaxSource File:Procedure Name:FTSCMD PASCALDoDelete550 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.System Action:None.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:Procedure Name:FTSCMDDoDelete, DoRnto550 Format type not specified for SITE LISTFORMAToperandSeverity:Error.Explanation: The LISTFORMAT operand of the SITEsubcommand was used, but a list format type was notprovided.System Action:None.User or Operator Response: Specify a valid list formattype (VM or UNIX) when the SITE LISTFORMATsubcommand is issued.Source File:Procedure Name:FTSVMSUB PASCALDoListFormat550 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.System Action:None.User or Operator Response:support personnel.Source File:Procedure Name:FTSVMSUB PASCALDoCwd, DoPassContact your system550 Invalid directory identifier in Site cmd. Use fullyqualified name or "."Severity:Error.Explanation: Command syntax was not valid for SiteGrant, Revoke, QDirattr or Dirattr.System Action:None.User or Operator Response:SITE commands Grant,74 z/VM: TCP/IP Messages and Codes

FTP MessagesRevoke, QDirattr, Dirattr only accept the fully qualifieddirectory name or ’.’ for the current working directory.Correct the syntax and reissue command.Source File:Procedure Name:FTSVMSUB PASCALDoSite550 Invalid file identifier in SITE QAUTH cmd. UseSITE QAUTH fn ft.Severity:Error.Explanation: The command syntax was incorrect forthe Query Authority command.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALDoSite550 Invalid filename specified in Site command Use’SITE XLATE filename’Severity:Error.Explanation: The SITE XLATE or SITE TRANSLATEcommand syntax was incorrect.System Action:None.User or Operator Response:reenter the command.Source File:Procedure Name:FTSVMSUBDoSite2Correct the syntax and550 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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALDoSite550 LISTFORMAT type list_format is not validSeverity:Error.Explanation: The indicated type of list format is notvalid for the LISTFORMAT operand. Valid list formattypes are VM and UNIX.System Action:None.User or Operator Response: Specify a valid list formattype (VM or UNIX) when the SITE LISTFORMATsubcommand is issued.Source File:Procedure Name:FTSEVEN PASCALDoListFormat550 m1 is not allowed: Owner Address is ReadOnlySeverity:Error.Explanation: You cannot do a write-link to the listedminidisk because it is accessed in a read-only mode.System Action:None.User or Operator Response:try another minidisk.Source File:Procedure Name:FTSVMSUB PASCALUpgradeLink550 MKDIR for BFS failed.Severity:Error.Correct your link logic orExplanation: An unusual error was encountered bythe FTP server virtual machine while attempting toissue an OPENVM CREATE DIR command in order tohonor a MKDIR request.System Action:None.User or Operator Response: Try to understand whythe OPENVM CREATE DIR command failed, andcorrect the problem.Source File:Procedure Name:FTSVMSUB PASCALDoMkDir550 NewOwner New Address is not a validminidisk/directory.Severity:Explanation:found.Error.System Action:The minidisk/directory specified was notNone.User or Operator Response:and try again.Source File:Procedure Name:FTSVMSUB PASCALDoCwdCheck your input syntaxChapter 3. FTP Messages 75

FTP Messages550 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.System Action:None.User or Operator Response: Ensure that all files in thetarget directory are closed before the RMDIR commandis issued.Source File:Procedure Name:FTSVMSUB PASCALDoRmDir550 Parent directory control directory is accessedread-only550 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.System Action:None.User or Operator Response: Another user currentlyhas the directory control directory accessed read-only.Retry the command later.Source File:Procedure Name:FTSVMSUB PASCALDoMkDir, DoRmDir550 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.System Action:None.User or Operator Response: Ensure you havespecified the directory correctly. If you are not anadministrator, make sure you are the owner of theparent directory.Source File:Procedure Name:FTSVMSUB PASCALDoMkDir550 Permission denied for write LINK to NewOwnerNewAddressSeverity:Error.Explanation: A write-link is not allowed to the listedminidisk for an unspecified reason.System Action:None.User or Operator Response:try another minidisk.Source File:Procedure Name:FTSVMSUB PASCALUpgradeLinkCorrect your link logic or550 Permission denied to LINK to NewOwnerNewAddress;Severity:Explanation:Error.System Action:A LINK permission rejection occurred.None.User or Operator Response: Identify the problem withthe LINK command and try again.Source File:Procedure Name:FTSVMSUB PASCALDoCwd550 Setting not specified for SITE AUTOTRANSoperandSeverity:Error.Explanation: The AUTOTRANS operand of the SITEsubcommand was used, but an automatic translationsetting was not provided.System Action:None.User or Operator Response: Specify a valid automatictranslation setting (ON or OFF) when the SITEAUTOTRANS subcommand is issued.Source File:Procedure Name:FTSVMSUB PASCALDoAutoTrans550 SFS directory name format may be wrong;directory remains working directory.Severity:Explanation:valid.Error.System Action:The specified directory name is notNone.User or Operator Response:and reenter the command.Source File:Procedure Name:FSTVMSUB PASCALDoCwd, DoPassCheck your input syntax550 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:Explanation:Error.Currently, you are not allowed to CD to76 z/VM: TCP/IP Messages and Codes

a subdirectory of a locked directory.System Action:None.User or Operator Response: Try to reissue thecommand a few times. If the lock persists, try toresolve the lock conflict.Source File:Procedure Name:FTSVMSUBDoCwd550 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.System Action:None.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.Source File:Procedure Name:FTSVMSUBDoCwd550 SFS system error; cslname rc x reason y550 SFS System Error; cslname rc x reason y ;directory remains workingdirectorySeverity: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.System Action:None.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 PASCALProcedure Name: FileOk, DoCwd, DoMkDir,DoRmDir; DoDelete, DoRnto, DoPass550 Specified directory contains one or moresubdirectories.Severity:Error.Explanation: You cannot erase a directory thatcontains a subdirectory.System Action:None.User or Operator Response:Remove all subdirectories|||||||||from the directory you want to erase, then reissue theoriginal RMDIR command.Source File:Procedure Name:FTSVMSUB PASCALDoRmDir550 Spool file nnnn does not existSeverity:Error.Explanation: The specified spool file was not found,therefore it could not be deleted.System Action:None.User or Operator Response: Ensure the spool file IDis correct and re-enter the DELETE command.Source File:Procedure Name:FTSCMD PASCALDoDelete550 System error 24 occurred trying to access directorySeverity:Error.Explanation: Routine DMSLINK returned with areturn code 24. A paging error has occurred. A pagingerror has occurred.System Action:console.User or Operator Response:RACF aministrator.Source File:Procedure Name:A message is written to the FTP serverFTSVMSUB PASCALContact your system orDoCwd, UpGradeLink550 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.System Action:None.User or Operator Response: Reissue the commandand if the error reoccurs, contact your TCP/IPadministrator to debug the problem.Source File:Procedure Name:FTSVMSUB PASCALCDtoRDR550 The Directory is not empty.Severity:Error.Explanation: An attempt has been made to erase aBFS directory that is not empty.System Action:None.User or Operator Response:FTP MessagesRemove all files andChapter 3. FTP Messages 77

FTP Messagessubdirectories from the directory you wish to erase andreissue the command.Source File:Procedure Name:FTSVMSUB PASCALDoRmDir550 The foreign file was not erased.550 Error storing file: The empty file was notstored on the foreign host.550 The foreign file has been erased.550 Error storing file: The empty file was notstored 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.System Action:None.User or Operator Response:Source File:Procedure Name:None.FTSVMSUB PASCAL, FTPROCS PASCALHandleNullFile550 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.System Action:None.User or Operator Response: Contact your systemsupport personnel to determine the status of the filepool.Source File:Procedure Name:FTSVMSUB PASCALDoRmdir550 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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALDoRmDir550 The working directory is emptySeverity:Explanation:directory.Error.System Action:There are no files in the workingNone.User or Operator Response: If this situation istolerable, continue. Otherwise, correct the problembefore resubmitting the job.Source File:Procedure Name:FTSVMSUB PASCALFindMode550 Translate file filename TCPXLBIN is in an invalidformatSeverity:Error.Explanation: The translate table was found, but couldnot be loaded because it is not a valid TCP/IP translatefile.System Action:None.User or Operator Response: Try to determine why thespecified translate table could not be read and correctthe problem.Source File:Procedure Name:FTSRVPA, FTSVMSUBInitialize, DoSite2550 Translate file ’filename TCPXLBIN’ not foundSeverity:Error.Explanation: The server was unable to locate thetranslate table specified.System Action:None.User or Operator Response: Ensure you havespecified the file name correctly and reenter thecommand.Source File:Procedure Name:FTPRVPA, FTSVMSUBInitialize, DoSite278 z/VM: TCP/IP Messages and Codes

FTP Messages550 Unable to append to the Null directory.Procedure Name:HandleFileOpenSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALHandleFileOpen550 Unable to append to filename550 Unable to append to filename, file or directoryis locked.550 Unable to append to filename, you are notauthorized.550 Unable to append to filename, SFS create fileerror.550 Unable to append to filename, virtual storagecapacity 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 SFSfile or directoryv Access to the file has been denied due to lack ofproper authorizationv An attempt to create a new file in the target SFSdirectory has failedv An insufficient virtual storage condition has beendetected.System Action:None.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.Source File:FTSVMSUB PASCAL550 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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALHandleFileOpen550 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.System Action:None.User or Operator Response: Use the SITE PERMITcommand to check your current authorization, and tryto determine why the OPENVM ERASE failed.Source File:Procedure Name:FTSCMD PASCALDoDelete550 Unable to send filename, file or directory is lockedSeverity: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.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALHandleFileOpenChapter 3. FTP Messages 79

FTP Messages550 Unable to store filename550 Unable to store filename, file or directoryis locked.550 Unable to store filename, you are notauthorized.550 Unable to store filename, SFS create file error.550 Unable to store filename, virtual storagecapacity 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 SFSfile or directoryv Access to the file has been denied due to lack ofproper authorizationv An attempt to create a new file in the target SFSdirectory has failedv An insufficient virtual storage condition has beendetected.System Action:None.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.Source File:Procedure Name:FTSVMSUB PASCALHandleFileOpen550 Unable to store unique filename550 Unable to store unique filename, file ordirectory is locked.550 Unable to store unique filename, you are notauthorized.550 Unable to store unique filename, SFS createfile error.550 Unable to store unique filename, virtualstorage 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 SFSfile or directoryv Access to the file has been denied due to lack ofproper authorizationv An attempt to create a new file in the target SFSdirectory has failedv An attempt to create the named file (or auniquely-named copy of this file) has failedv 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.Source File:Procedure Name:FTSVMSUB PASCALHandleFileOpen550 Wildcards not supported in QAUTH for protectedSFSSeverity:Error.Explanation: Wildcards are not supported for theQuery Authority.System Action:None.User or Operator Response:with file name and file type.Source File:Procedure Name:FTSVMSUB PASCALDoSiteReissue the command550 Write access unavailable for Owner Address due toother linksSeverity:Error.Explanation: Another VM user has accessed yourworking directory minidisk in write mode. VM does80 z/VM: TCP/IP Messages and Codes

FTP Messagesnot allow multiple write access to prevent two usersfrom modifying the same file at the same time.System Action:None.User or Operator Response: Wait until the other userde-accesses the minidisk, or assign another nonaccessedminidisk as working storage.Source File:Procedure Name:FTSVMSUB PASCALUpgradeLink550 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).System Action:None.User or Operator Response: If you meant to create adirectory within the directory structure, use the MKDIRcommand with one more level.(FILEPOOL:USERID.SUBDIRECTORY).Source File:Procedure Name:FTSVMSUB PASCALDoMkDir550 You are not authorized for userid.RDR;Directory remains old_directorySeverity:Error.Explanation: You do not have the authority to accessthe user’s reader.System Action:None.User or Operator Response:Source File:Procedure Name:FTSVMSUBCDtoRDRNone.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 arenot in SFS.550 You are not using an SFS directory. CDUP isnot allowed.550 You can not Remove Directory because you arenot in SFS.Severity:Error.Explanation: SFS/BFS commands are not allowedunless your current working directory is an SFS/BFSdirectory.System Action:None.User or Operator Response:Issue CD command tochange your current working directory to an SFS/BFSdirectory.Source File:Procedure Name:DoRmDirFTSVMSUB PASCALDoCwd, DoSite, DoMkDir, DoCdup,550 You can not erase a top-level directory.Severity:Error.Explanation: You attempted to erase a top directory.This directory cannot be erased.System Action:None.User or Operator Response: To erase all objectscontained in the directory, issue an appropriate series oferase commands for those objects.Source File:Procedure Name:FTSVMSUB PASCALDoRmdir550 You can not remove the current working directory.Severity:Error.Explanation: You issued an RMDIR command for thecurrent working directory.System Action:None.User or Operator Response: Use the CD command tochange to another SFS directory and reissue thecommand.Source File:Procedure Name:FTSVMSUB PASCALDoRmDir550 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.System Action:None.User or Operator Response: Select a newdirectory/mini-disk or contact the directory owner forauthorization.Source File:Procedure Name:FTSVMSUB PASCALDoList, DoCwdChapter 3. FTP Messages 81

FTP Messages552 Data transfer aborted, BFS file space is fullProcedure Name:ParseBFSIdentifierSeverity:Error.Explanation: There is not enough room in the filespace to complete the request.System Action:None.User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits in the file pool.Source File:Procedure Name:FTSEVEN PASCALWriteBFSData552 Data transfer aborted due to disk overflow.552 Data transfer aborted, SFS file space is full.552 Data transfer aborted. Disk overflow occurredon 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.System Action:None.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.Source File:FTSEVEN PASCALProcedure Name: StoreBlock, StoreFile,WriteImageData, TheyClosedEvent552 Storage group space limit exceeded.Severity:Error.Explanation: There is no room in the filespace tocomplete the request.System Action:None.User or Operator Response: Delete some files or askyour system administrator to increase your storagespace limits in the file pool.Source File:Procedure Name:FTSVMSUB PASCALDoMkDir, DoRmDir553 Invalid character (″/″) in BFS file identifier:’BFSfile’Severity:Error.Explanation: The ″/″ command is not allowed in aBFS file identifier.System Action:None.User or Operator Response: Correct the invalid BFSfile specification and reissue the command.Source File:Procedure Name:FTSVMSUB PASCALParseBFSIdentifier553 Invalid CMS file identifier FileName553 Invalid character in filename FileName550 File FileName is not on an accessed mini-disk550 File error ReturnCode in accessing FileNameSeverity:Error.Explanation: FTP sends one of these four messages,depending on the problem.System Action:None.User or Operator Response: Correct thecorresponding problem and resubmit the job.Source File:Procedure Name:FTSVMSUB PASCALFileOk553 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).System Action:None.User or Operator Response: Correct the BFS filespecification and reissue the command.Source File:Procedure Name:FTSVMSUB PASCALParseBFSIdentifier553 Invalid BFS file identifier: ’BFSfile’Severity: Error.Explanation: The specified BFS file identifier is notvalid.System Action: None.User or Operator Response: Correct the BFS filespecification and reissue the command.Source File: FTSVMSUB PASCAL82 z/VM: TCP/IP Messages and Codes

Chapter 4. GDDMXD/VM Messages and CodesGDDMXD/VM MessagesThis chapter contains the GDDMXD/VM messages and ABEND codes you canencounter when you use GDDMXD/VM.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.ABEND CodesCode: 102Explanation: Either GDXLIOX0 MODULE orGDXADML1 MODULE could not be found.User or Operator Response: Access the diskcontaining these modules and try again.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.User or Operator Response: Try again. If the errorreoccurs, report the problem to your IBM SupportCenter.Code: 103Explanation: 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: 104Explanation: The X Window System has detected anerror and is unable to continue. This ABEND isgenerally preceded by an X Window System message.© Copyright IBM Corp. 1987, 2002 83

GDDMXD/VM Messages and Codes84 z/VM: TCP/IP Messages and Codes

Chapter 5. IMAP MessagesThis section contains the IMAP messages.DTCIMP1000E ip_address Buffer overrun receivingcommandExplanation: 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:terminated.IMAP continues but the connection isSystem 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_codeExplanation: 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_codeExplanation: An error occurred while trying to closethe specified file using the DMSCLOSE CSL routine.System Action:IMAP continues.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_codeExplanation: An error occurred while trying to readthe specified file using the DMSREAD CSL routine.System Action:IMAP continues.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_codeExplanation: An error occurred while trying to writeto the specified file using the DMSWRITE CSL routine.System Action:IMAP continues.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_codeExplanation: The DMSCHECK CSL routine returnedthe specified return code and reason code while tryingto determine if an asynchronous SFS request hadcompleted.System Action:IMAP continues.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_codeExplanation: An error occurred while trying tocommit changes to the SFS file pool containing theIMAP mailstore using the DMSCOMM CSL routine.System Action:IMAP continues.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_codeExplanation: An error occurred while trying to createthe specified directory using the DMSCRDIR CSLroutine.System Action:IMAP continues.System Programmer Response: Use the given reasoncode from the DMSCRDIR CSL routine to determinewhy the error occurred.© Copyright IBM Corp. 1987, 2002 85

IMAP MessagesDTCIMP1008E ip_address Error opening directorydirname: DMSOPDIR rs=reason_codeExplanation: An error occurred while trying to openthe specified directory using the DMSOPDIR CSLroutine.System Action:IMAP continues.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_codeExplanation: An error occurred while trying to closethe specified directory using the DMSCLDIR CSLroutine.System Action:IMAP continues.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_codeExplanation: The DMSEXIFI CSL routine returned thespecified reason code for the given file.System Action:IMAP continues.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_codeExplanation: An error occurred while trying to obtainthe given directory’s information using the DMSGETDICSL routine.System Action:IMAP continuesSystem 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_codeExplanation: An error occurred while trying to erasethe specified object using the DMSERASE CSL routine.System Action:IMAP continuesSystem 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_codeExplanation: An error occurred while trying to returnan SFS work unit id using the DMSRETWU CSLroutine.System Action:IMAP continuesSystem 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 registeredExplanation: An operation requiring a valid user IDwas attempted, but the specified user is not enrolled inthe IMAP mailstore.System Action:IMAP continues.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 validExplanation: 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= rcExplanation: 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_codeExplanation: An error occurred when the IMAP servertried to respond to an administrative interface86 z/VM: TCP/IP Messages and Codes

IMAP Messagescommand using the QueueReply() CMS multitaskingfunction.System Action:IMAP continues.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_codeExplanation: 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_codeExplanation: 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 Action:IMAP continues.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_codeExplanation: 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 Action:IMAP continues.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 storageExplanation: The IMAP server was unable to allocatevirtual storage.System Action:IMAP continuesSystem 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 beenexhaustedExplanation: The specified user has used all of theirallocated space in the IMAP SFS mailstore.System Action:IMAP continues.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_codeExplanation: An error occurred while attempting tocopy a file. The error occurred using the given CSLroutine.System Action:IMAP continuesSystem 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_codeExplanation: An error occurred while trying torename the specified file or directory in the IMAP SFSmailstore using the DMSRENAM CSL routine.System Action:IMAP continues.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 ignoredExplanation: 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.System Programmer Response:None.Chapter 5. IMAP Messages 87

IMAP MessagesDTCIMP1026I Administrative request from useruserid: requestExplanation: The IMAP server received the givenadministrative interface command (request) fromthespecified user.System Action:IMAP continuesSystem Programmer Response:DTCIMP1027INone.ip_address ConnectedExplanation: An IMAP client from the specified IPaddress has connected to the IMAP server.System Action:IMAP continues.System Programmer Response:DTCIMP1028INone.ip_address Authenticated as user useridExplanation: An IMAP client from the specified IPaddress has authenticated their connection to the IMAPserver using the specified user ID.System Action:IMAP continues.System Programmer Response:DTCIMP1029INone.ip_address Connection terminatedExplanation: 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 Action:IMAP continues.System Programmer Response: See previousmessages to determine what error occurred.DTCIMP1030Iip_address DisconnectedExplanation: The connection to the IMAP server fromthe specified IP address has ended.System Action:IMAP continuesSystem Programmer Response:None.DTCIMP1031E Error transferring file spoolid to useruserid:rc=rcExplanation: 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.DTCIMP1032IFile spoolid transferred to user useridExplanation: The specified spool file has beentransferred to the specified user ID.System Action:IMAP continues.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= rcExplanation: 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:Support Center for assistance.Contact your IBMDTCIMP1034E Unable to open configuration filefilename: DMSOPEN rs=reason_codeExplanation: An error occurred while trying to openthe specified configuration file using the DMSOPENCSL routine.System Action:Server initialization stops.System Programmer Response: Use the given reasoncode from the DMSOPEN CSL routine to determinewhy the error occurred.DTCIMP1035E Missing token on statement statementin configuration fileExplanation: The given statement requires moretokens than were specified in the IMAP configurationfile.System Action:Server initialization stops.System Programmer Response: Correct theconfiguration file statement and restart the IMAPserver.DTCIMP1036E Unable to validate filepoolidfilepoolid: DMSGETWU rc=return codeExplanation: 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.System Action:Server initialization stops.88 z/VM: TCP/IP Messages and Codes

IMAP MessagesSystem 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 administratorExplanation: 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 Action:Server initialization stops.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_codeExplanation: 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.DTCIMP1043E No BADFILEID specified in theconfiguration fileExplanation: The BADFILEID statement is requiredand must be specified in the IMAP server configurationfile.System Action:Server initialization stops.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 QueueSendReplyExplanation: The IMAP server received a messageover the administrative interface queue that was notsent using the QueueSendReply CMS multitaskingfunction. The message is ignored.System Action:IMAP continues.System Programmer Response:None.DTCIMP1045E Invalid token token on statementstatement in configuration fileExplanation: The specified token is not valid for thegiven configuration file statement.System Action:Server initialization stops.System Programmer Response: Correct theconfiguration file statement and restart the IMAPserver.DTCIMP1041E Unknown configuration filestatement statementExplanation: 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 Action:Server initialization stops.System Programmer Response: Delete or correct thestatement that is in error, then restart the IMAP server.DTCIMP1042E No FILEPOOLID specified in theconfiguration fileExplanation: The FILEPOOLID statement is requiredand must be specified in the IMAP server configurationfile.System Action:Server initialization stops.System Programmer Response: Specify theFILEPOOLID statement in the IMAP serverconfiguration file and restart the IMAP server.DTCIMP1046E Excessive token token on statementstatement in configuration fileExplanation: Too many tokens were specified for thegiven configuration file statement, starting with thetoken specified in the message.System Action:Server initialization stops.System Programmer Response: Correct theconfiguration file statement and restart the IMAPserver.DTCIMP1047EInvalid command input: commandExplanation: The specified console command is not avalid input command.System Action:IMAP continues.System Programmer Response:command.Enter a valid consoleChapter 5. IMAP Messages 89

IMAP MessagesDTCIMP1048IShutting down at your request.Explanation: The IMAP server is shutting downbecause a SHUTDOWN administrative command wasenteredSystem Action:IMAP shuts down.System Programmer Response:None.DTCIMP1049I Additional reader thread created atyour requestExplanation: An additional thread is created forprocessing reader files because a STARTRDRadministrative command was entered.System Action:IMAP continues.System Programmer Response:None.DTCIMP1050E Unknown command entered:commandExplanation: An unsupported console command wasentered on the IMAP server.System Action:IMAP continuesSystem Programmer Response:valid console command.DTCIMP1051EIf necessary, enter aFlag or TIC not as expectedExplanation: An unrecognized Channel CommandWord (CCW) flag or Transfer in Channel (TIC)command was encountered while processing a spoolfile.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:Support Center for assistance.DTCIMP1052EContact your IBMCard image would overrun bufferExplanation: 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.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:Support Center for assistance.Contact your IBMDTCIMP1053EPremature end of cardsExplanation: An error occurred while processing aspool file. The spool file data did not contain all of itscard images.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:Support Center for assistance.Contact your IBMDTCIMP1054E Invalid netdata segment sizeencounteredExplanation: An error occurred while processing aspool file. The spool file contained a NETDATA recordwhich had a segment size less than one.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:Support Center for assistance.Contact your IBMDTCIMP1055E Invalid netdata segment flagsencounteredExplanation: An error occurred while processing aspool file. The spool file contained a NETDATA recordwhich had an unrecognized segment flag.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:Support Center for assistance.DTCIMP1056EContact your IBMInvalid control record encounteredExplanation: An error occurred while processing aspool file. The spool file contained a NETDATA controlrecord that did not begin with an INMR0 string.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:Support Center for assistance.Contact your IBMDTCIMP1057E Recipient user ID in spool file is toolargeExplanation: 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 the90 z/VM: TCP/IP Messages and Codes

IMAP Messagesuser ID specified in the BADFILEID statement in theIMAP configuration file. A later message indicateswhich spool file had the error.System Programmer Response:Support Center for assistance.Contact your IBMDTCIMP1058E Error connecting to *SPL:re=return_codeExplanation: 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 valueExplanation: 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.DTCIMP1060IReader thread terminatingExplanation: 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 serverExplanation: 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 unsupporteddeviceExplanation: 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 Action: The spool file is transferred to theuser ID specified in the BADFILEID configuration filestatement.System Programmer Response:with the unsupported file.Determine what to doDTCIMP1064E Unable to determine recipient forspool file spoolid, may not be inNETDATA formatExplanation: The IMAP server is unable to determineif the given spool file is in NETDATA format. Allincoming mail must be in NETDATA format.System Action: The spool file is transferred to theuser ID specified in the BADFILEID configuration filestatement.System Programmer Response:with the unsupported file.Determine what to doDTCIMP1065I File spoolid added to INBOX of useruserid as UID uidExplanation: The given spool file has beensuccessfully received by the IMAP server and has beenadded to the INBOX of the given user ID.System Action:IMAP continues.Chapter 5. IMAP Messages 91

IMAP MessagesSystem Programmer Response:None.DTCIMP1066E Error adding file spoolid to folderINBOX for user userid: rs=reason_codeExplanation: 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 Action:IMAP continues.System Programmer Response: See the reason_codedocumentation and previous error messages todetermine why the error occurred.DTCIMP1067I Verify userid has IUCV *SPLdirectory statementExplanation: 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_codeExplanation: 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.System Programmer Response:Support Center for assistance.DTCIMP1069IContact your IBMReader support terminatingExplanation: 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 validExplanation: The configuration file name specifiedwith the IMAPMAIN command contains more thaneight characters.System Action:Server initialization stops.System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.DTCIMP1071E Configuration file type filetype is notvalidExplanation: The configuration file type specified withthe IMAPMAIN command contains more than eightcharacters.System Action:Server initialization stops.System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.DTCIMP1072E Configuration file mode filemode isnot validExplanation: The configuration file mode specifiedwith the IMAPMAIN command contains more thantwo characters.System Action:Server initialization stops.System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.DTCIMP1073EExcessive parms, starting with parmExplanation: Too many parameters were specified onthe IMAPMAIN command, starting with the specifiedparameter. For more information on the IMAPMAINcommand, see TCP/IP Planning and Customization.System Action:Server initialization stops.System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.DTCIMP1074E Error determining filemode ofconfiguration file: DMSERPrc=return_codeExplanation: An error occurred while trying todetermine the file mode of the IMAP serverconfiguration file using the DMSERP CSL routine.System Action:Server initialization stops.System Programmer Response: Use the return codefrom the DMSERP CSL routine to determine why theerror occurred.92 z/VM: TCP/IP Messages and Codes

IMAP MessagesDTCIMP1075E Wrong level of CMS: routine notfoundExplanation: The given CSL routine was not foundand returned a -7 return code.System Action:Server initialization stops.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_rsExplanation: An error occurred while trying to createan External Security Manager (ESM) token using theDMSESM CSL routine.System Action:Server initialization stops.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 authorizationExplanation: The IMAP server must be authorized touse DIAGNOSE X’88’ in order to validate IMAP clientpasswords.System Action:Server initialization stops.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 notavailableExplanation: Diagnose 88 support is not available inthe level of CP that the IMAP server is running.System Action:Server initialization stops.System Programmer Response:appropriate level of z/VM.Upgrade to theDTCIMP1080E ip_address Specified password expiredfor user useridExplanation:System Action:The given user’s password has expired.IMAP continues.System Programmer Response:their logon password.DTCIMP1081EThe user must changeUnrecognized option: optionExplanation: 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.System Action:Server initialization stops.System Programmer Response: Correct theappropriate :Parms. tag entry in the DTCPARMS file,then restart the IMAP server.DTCIMP1082EConfiguration file filename not foundExplanation: The configuration file listed in themessage does not exist on any minidisk that has beenaccessed by the IMAP server.System Action:Server initialization stops.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_codeExplanation: An error occurred while attempting toobtain file space limits information for a user using theDMSQLIMU CSL routine.System Action:IMAP continues.System Programmer Response: Use the return codefrom the given CSL routine to determine why the erroroccurred.DTCIMP1079E Error deleting ESM token: DMSESMDelete_Token rc=return_code, ESMrc=ESM_rc, ESM rs=ESM_rsExplanation: 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.DTCIMP2000E ip_address Bad parameters received oncommand commandExplanation: The specified command received fromthe specified IP address contained invalid parameters.System Action: IMAP continues.System Programmer Response: None.Chapter 5. IMAP Messages 93

IMAP MessagesDTCIMP2001Eip_address Bad part specifier specifierExplanation: The FETCH command from the given IPaddress contained an invalid part specifier.System Action:IMAP continues.System Programmer Response:None.DTCIMP2002W ip_address Non-permanent flag, flag,is being ignoredExplanation: The IMAP client at the specified IPaddress attempted to set a non-permanent flag. Thespecified flag is ignored.System Action:IMAP continues.System Programmer Response:None.DTCIMP3000E ip_address Bad command commandreceived; connection state stateExplanation: 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.System Action:IMAP continues.System Programmer Response:None.DTCIMP3001E ip_address Bad parameters received oncommand commandExplanation: The IMAP client at the specified IPaddress supplied invalid parameters on the givencommand.System Action:IMAP continues.System Programmer Response:None.DTCIMP3002E ip_address command command failed,see previous messages for detailsExplanation: The given command from the IMAPclient at the specified IP address failed.System Action:IMAP continues.System Programmer Response: See previousmessages to determine what error occurred.DTCIMP3003E ip_address command command failed:rc=return_code, rs=reason_codeExplanation: The given command from the IMAPclient at the specified IP address failed.System Action:IMAP continues.System Programmer Response: Previous messagesmay help determine what error occurred.DTCIMP3004E ip_address Access to mailbox denied,must be selected write to STORE orEXPUNGEExplanation: The IMAP client at the given IP addressattempted to send a STORE or EXPUNGE commandwhile the specified mailbox was not selected in writemode.System Action:IMAP continues.System Programmer Response:None.DTCIMP3005E ip_address Write access to mailboxmailbox deniedExplanation: 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.System Action:IMAP continues.System Programmer Response:DTCIMP3006ENone.ip_address Bad mailbox name mbxnameExplanation: The IMAP client at the given IP addresssupplied an invalid mailbox name in a command.System Action:IMAP continues.System Programmer Response:None.DTCIMP3007E ip_address Mailbox mailbox does notexistExplanation: The IMAP client at the given IP addresssupplied a command with a mailbox name that doesnot exist.System Action:IMAP continues.System Programmer Response:None.DTCIMP3008E ip_address Mailbox mailbox alreadyexistsExplanation: 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.System Action:IMAP continues.System Programmer Response:None.DTCIMP3009E ip_address Error selecting mailboxmailboxExplanation: The IMAP client at the given IP addressattempted to select the specified mailbox, but themailbox is marked as \NoSelect.System Action:IMAP continues.94 z/VM: TCP/IP Messages and Codes

IMAP MessagesSystem Programmer Response:None.DTCIMP3010E ip_address Error creating mailboxmailboxExplanation: The IMAP client at the given IP addressattempted to create the specified mailbox, but themailbox could not be created.System Action:IMAP continues.System Programmer Response: See previousmessages to determine why the mailbox could not becreated.DTCIMP3011E ip_address Error deleting mailboxmailboxExplanation: 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.System Action:IMAP continues.System Programmer Response:None.DTCIMP3015E ip_address Error committing work foruser userid on command command:rs=reason_codeExplanation: 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 Action:IMAP continues.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 useridExplanation: The IMAP server was unable to obtain awork unit for the specified user at the given IP address.System Action: The connection remainsunauthenticated.System Programmer Response:None.DTCIMP3012E ip_address Error relocating directorydirnameExplanation: The IMAP client at the given IP addressattempted to rename the specified directory to INBOX.System Action:IMAP continues.System Programmer Response:None.DTCIMP3013E ip_address Error renaming mailboxmailbox: see previous messageExplanation: 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.System Action:IMAP continues.System Programmer Response:None.DTCIMP3014E ip_address Error copying file filename:rc=return_code, rs=reason_codeExplanation: The IMAP client at the given IP addressattempted to copy the specified file, but the file couldnot be copied.System Action:IMAP continues.System Programmer Response: See previousmessages to determine why the file could not becopied.DTCIMP3017E ip_address Error appending new noteto folder mbxname for user userid:rs=reason_codeExplanation: 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 Action:IMAP continues.System Programmer Response: See the reason_codedocumentation and previous error messages todetermine why the error occurred.DTCIMP3018E ip_address EXPUNGE mailbox failed:multiple concurrent selectorsExplanation: 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 Action:IMAP continues.System Programmer Response: The client shouldretry the EXPUNGE when it is the only selector of themailbox.DTCIMP4000EMalloc error, requested size was bytes.Explanation: An error occurred when the IMAP serverattempted to allocate bytes amount of storage.System Action:IMAP continues.Chapter 5. IMAP Messages 95

IMAP MessagesSystem 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 commandExplanation: 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.System Programmer Response:None.DTCIMP4002E ip_address Error starting timer:TimerStartInt rc=return_code,rs=reason_codeExplanation: 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_codeExplanation: 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.DTCIMP5002E Error waiting on event: EventWaitrc=return_code, rs=reason_codeExplanation: An error occurred while waiting for anasynchronous request to complete using the EventWaitCMS multitasking function.System Action:IMAP terminates.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_codeExplanation: An error occurred while attempting tocreate a message queue using the QueueCreate CMSmultitasking function.System Action:Server initialization stops.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_codeExplanation: An error occurred while trying toidentify a service queue using the QueueIdentifyServiceCMS multitasking function.System Action:Server initialization stops.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.DTCIMP5001E Error creating event monitor:EventMonitorCreate rc=return_code,rs=reason_codeExplanation: An error occurred when the IMAP serverattempted to create an event monitor for notification ofconsole commands using the EventMonitorCreate CMSmultitasking function.System Action:Server initialization stops.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.DTCIMP5005E An error occurred during serverinitializationExplanation: An error occurred while the IMAP serverwas initializing.System Action:Server initialization stops.System Programmer Response: See previousmessages to determine what error occurred.DTCIMP5006E Error creating semaphore: SemCreaterc=return_code, rs=reason_codeExplanation: An error occurred while attempting tocreate a semaphore using the SemCreate CMSmultitasking function.System Action:IMAP terminates.96 z/VM: TCP/IP Messages and Codes

IMAP MessagesSystem 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_codeExplanation: An error occurred while attempting tocreate a mutex using the MutexCreate CMSmultitasking function.System Action:Server initialization stops.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_codeExplanation:call.System Action:An error occurred on the given socketIf necessary, IMAP terminates.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_codeExplanation: An error occurred while attempting toset the internal date of a note. The given date wasreturned from the DateTimeSubtract CMS multitaskingfunction.System Action:IMAP terminates.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_codeExplanation: An error occurred on the given socketcall during IMAP initialization.System Action:Server initialization stops.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 commandExplanation: The buffer used to reply to the specifiedcommand on the connection to the given IP addresshas been overrun.System Action:IMAP terminatesSystem Programmer Response:Support Center for assistance.Contact your IBMDTCIMP5012E ip_address Unexpected error whiledetermining if user userid is enrolled:procedure_name rc=return_codeExplanation: An error occurred while determining ifthe given user is enrolled in the IMAP mailstore. Theerror occurred while calling the given procedure.System Action:IMAP terminates.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_codeExplanation: The IMAP server’s ErrorHandleprocedure was called with an unknown error number.System Action:IMAP terminates.System Programmer Response:Support Center for assistance.Contact your IBMDTCIMP5014E ip_address Error on socket call: socketrc=return_codeExplanation: An error occurred on the given socketcall for the specified IP address.System Action:If necessary, IMAP terminates.System Programmer Response: Examine the returncode from the socket call to determine what erroroccurred.DTCIMP5015EBinary tree balance factor not correctExplanation: The internal binary tree of selectedmailboxes contains a node with a balance factor that isnot correct.System Action:IMAP terminates.System Programmer Response: Restart the IMAPserver and contact your IBM Support Center forassistance.Chapter 5. IMAP Messages 97

IMAP MessagesDTCIMP5016EMailbox mbx not in binary treeExplanation: The specified mailbox could not befound in the internal binary tree of selected mailboxes.System Action:IMAP terminates.System Programmer Response: Restart the IMAPserver and contact your IBM Support Center forassistance.DTCIMP5017E An invalid thread switch occurredExplanation: An invalid thread switch occurred whileattempting to receive data on a connection.System Action: IMAP terminates.System Programmer Response: Contact your IBMSupport Center for assistance.DTCIMP5018E Invalid connection address providedExplanation: A socket read completed and theconnection address given was not valid.System Action: IMAP terminates.System Programmer Response: Contact your IBMSupport Center for assistance.98 z/VM: TCP/IP Messages and Codes

Chapter 6. MPROUTE MessagesThis section contains the MPROUTE messages.DTCMPR7800IExplanation:System Action:MPROUTE startingThe MPROUTE application is starting.None.User or Operator Response:System Programmer Response:None.None.DTCMPR7801I Deleting stack route to destination,mask mask via gateway, link link, metricmetric, type typeExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7802I MPROUTE invalid option specified:optionExplanation: An unsupported command line optionwas used. option is the invalid option.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Verify command lineoptions used when MPROUTE was started and retry.DTCMPR7803I MPROUTE, functionerrno=errno:description, errno2=errno2Explanation: The indicated function failed with theindicated error. errno is the system error code.System Action:User or Operator Response:MPROUTE terminates.System Programmer Response:error reported.DTCMPR7804IExplanation:normally.System Action:None.MPROUTE exitingCorrect the systemThe MPROUTE application is exitingMPROUTE terminates.User or Operator Response:System Programmer Response:desired.None.Restart MPROUTE ifDTCMPR7805I MPROUTE exiting abnormally -RC(returncode)Explanation: Application is exiting abnormally withthe specified return code:Reason CodeCause1 Exited due to unrecoverable error3 Exited due to receipt of terminating signal4 Exited due to invalid start up parameterpassed to MPROUTE5 Exited due to failure to add route to TCP/IPstack’s route table6 Exited due to failure to obtain storage viamalloc7 Exited due to the TCP/IP stack going down8 Exited while initializing the PSA environment9 Exited while initializing the log/trace facility11 Exited while initializing the OSPF, RIP andINFORMATIONAL sockets12 Exited while configuring the MPROUTEapplication13 Exited while obtaining the TCP/IP stack’sroute table14 Exited while initializing the RIP protocol15 Exited while initializing the OSPF protocol16 Exited while dynamically adding an OSPFinterface17 Exited due to failure to delete route fromTCP/IP stack’s route18 Exited due to failure to change route inTCP/IP stack’s route tableSystem Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Take necessarycorrective action based upon specified return code andany preceding messages indicating the cause of theabnormal exit. Restart MPROUTE if desired.© Copyright IBM Corp. 1987, 2002 99

MPROUTE MessagesDTCMPR7806I Changing stack route to destination,mask mask via gateway, link link, metricmetric, type typeExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7807I Abnormal termination - out ofstorageExplanation: MPROUTE requested storage for acontrol block or buffer and that request has failed.System Action:User or Operator Response:MPROUTE terminates.System Programmer Response:shortage.None.Resolve the storageDTCMPR7810I Route not deleted from stack routingtable - reasonExplanation: A dynamic route was not deleted fromthe stack’s routing table for the specified reason.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7812I Could not obtain stack interfaceflags, ioctl errno=errno:description,errno2=errno2Explanation: An attempt to obtain the flags for aTCP/IP interface failed with the specified error.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7813I Could not obtain stack interfacebroadcast address, ioctlerrno=errno:description, errno2=errno2Explanation: An attempt to obtain the broadcastaddress for a TCP/IP interface failed with the specifiederror.System Action:None.User or Operator Response:System Programmer Response:None.100 z/VM: TCP/IP Messages and CodesPossible internal error.||||||||Contact the IBM Support Center.DTCMPR7814I Unable to create socket type type,errno=errno:description, errno2=errno2Explanation: An attempt to create a socket of thespecified type failed with the specified error.System Action:User or Operator Response:MPROUTE terminates.None.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=errno2Explanation: An attempt to bind to the specified portfailed with the specified error.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7816I Unable to set option option for typesocket socket, errno=errno:description,errno2=errno2Explanation: An attempt to set the specified option onthe specified socket failed with the specified error.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7817IUsing type OSPF protocol protocolExplanation: The specified protocol number is beingused for OSPF communication.System Action:None.User or Operator Response:System Programmer Response:None.None.

MPROUTE MessagesDTCMPR7818I Unable to listen on socket socket,errno=errno:description, errno2=errno2Explanation: An attempt to listen on the specifiedsocket failed with the specified error.System Action:None.User or Operator Response:None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7819I Invalid value for keyword coded ontype statementExplanation: 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.User or Operator Response:None.System Programmer Response: Correct the valuecoded for the specified keyword in the MPROUTEconfiguration file.DTCMPR7820I Required parameter for keyword notcoded on type statementExplanation: A required keyword for which no defaultcan be taken was not coded on the specifiedconfiguration statement in the MPROUTE configurationfile.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Add the requiredkeyword to the appropriate configuration statement inthe MPROUTE configuration file.DTCMPR7821IIgnoring duplicate type statementExplanation: Found a duplicate of the specifiedconfiguration statement in the MPROUTE configurationfile.System Action:User or Operator Response:The duplicate statement is ignored.None.System Programmer Response: Remove the duplicatestatement from the MPROUTE configuration file.DTCMPR7822ICould not find configuration fileExplanation: The MPROUTE configuration file couldnot be found.System Action:User or Operator Response:MPROUTE terminates.System Programmer Response:None.Check the searchhierarchy 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.User or Operator Response:None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7826I Unable to accept connections onsocket socket, errno=errno:description,errno2=errno2Explanation: An attempt to accept a connection on thespecified socket failed with the specified error.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7827I Adding stack route to destination,mask mask via gateway, link link, metricmetric, type typeExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7828I Error adding/deleting/changing stackroute, return code retcode, iocterrno=errno:description, errno2=errno2Explanation: An attempt to add, delete, or change aroute in the stack’s route table has failed for thespecified reason.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.Chapter 6. MPROUTE Messages 101

MPROUTE MessagesDTCMPR7829I Route not changed in stack routingtable - reasonExplanation: A dynamic route was not changed in thestack’s routing table for the specified reason.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7830I error at line line of MPROUTEconfiguration file processing tokenExplanation: The specified error occurred on thespecified line in the MPROUTE configuration file. Theerror was encountered on or just previous to thespecified token.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Correct the error inthe MPROUTE configuration file.DTCMPR7837I Could not obtain stack interfaceindex, ioctl errno=errno:description,errno2=errno2Explanation: The attempt to obtain the list ofinterfaces defined to the TCP/IP stack failed with thespecified error.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7838IUsing configuration file: filenameExplanation: The specified configuration file is beingused to configure MPROUTE.System Action:None.User or Operator Response:System Programmer Response:DTCMPR7839INone.None.type receive thread terminatesExplanation: The specified MPROUTE thread isterminating. Communications over this thread areterminated.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Actions determinedby preceding messages indicating the cause of thethread termination.DTCMPR7840I sendto() error, errno=errno:description,errno2=errno2Explanation: 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.User or Operator Response:None.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 closedunexpectedlyExplanation: A TCPIP socket used for communicationsby MPROUTE has closed or has timed out.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Investigate possibleproblems with TCPIP. Restart MPROUTE.DTCMPR7842I type function error,errno=errno:description, errno2=errno2Explanation: The indicated function failed with theindicated error. errno is the system error code.System Action:User or Operator Response:MPROUTE terminates.System Programmer Response:error reported.None.Correct the systemDTCMPR7857I error (text) on MPROUTE SMSGcommandExplanation: The specified error has occurred whileprocessing an MPROUTE SMSG command.System Action:ignored.User or Operator Response:The MPROUTE SMSG command isNone.System Programmer Response: Verify the syntax ofthe SMSGY command and reissue.DTCMPR7858I Unable to send debug and/or traceoutput to debug destinationExplanation: MPROUTE was unable to access thedebug destination for storage of debug and/or traceoutput.System Action: MPROUTE continues, unable to writedebug and trace information.102 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesUser or Operator Response:System Programmer Response:None.None.DTCMPR7861I Sink network discarding packet todestinationExplanation: An OSPF or RIP packet, intended for thespecified destination, is being discarded due to the lackof an active interface to the destination.System Action:None.User or Operator Response:System Programmer Response:DTCMPR7862INone.None.Received type interface nameExplanation: 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.User or Operator Response:System Programmer Response:DTCMPR7863INone.None.Received type route to destinationExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR7864I Deleting all stack routes todestination, maskmaskExplanation: 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).System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7865I Class mask class_mask being used forinterface interfaceExplanation: The specified interface was notconfigured in the MPROUTE configuration file throughan OSPF_Interface, RIP_Interface, or Interfaceconfiguration 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.User or Operator Response:None.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 commandacceptedExplanation:MPROUTE.System Action:User or Operator Response:A SMSG command has been received bySystem Programmer Response:The SMSG command is processed.None.None.DTCMPR7867I Invalid type value specified in SMSGcommandExplanation: An invalid value of the specified typewas entered in an SMSG command received byMPROUTE.System Action:User or Operator Response:The SMSG command is ignored.None.System Programmer Response: Verify the syntax ofthe SMSG command and reissue.DTCMPR7868I Dead Router Interval must be greaterthan Hello Interval on type statement,taking defaultsExplanation: 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.User or Operator Response:None.System Programmer Response: Modify theMPROUTE configuration file to either increase theDead Router Interval or decrease the Hello Interval.Chapter 6. MPROUTE Messages 103

MPROUTE MessagesDTCMPR7869I MPROUTE configuration file mustcontain OSPF or RIP interfacestatementsExplanation: MPROUTE has found no OSPF_Interfaceor RIP_Interface configuration statements in theMPROUTE configuration file.System Action:User or Operator Response:MPROUTE terminates.None.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 forkwrdExplanation: 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 Action:User or Operator Response:MPROUTE terminates.None.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.User or Operator Response:None.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 activeExplanation: 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 Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Stop the activerouting application and restart MPROUTE.DTCMPR7873I Required parameter parm missing onMPROUTE SMSG commandExplanation: The specified required parameter wasnot provided on a SMSG command received byMPROUTE.System Action:User or Operator Response:The MODIFY command is ignored.None.System Programmer Response: Verify the syntax ofthe SMSG command and re-issue.DTCMPR7875INo default route definedExplanation: 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.User or Operator Response:None.System Programmer Response: Activate the next hopinterface and the default route will become active.DTCMPR7876I -- protocol Packet Sent ------ Type: typeversionExplanation: A packet, of the specified type andversion, has been sent by the specified protocol.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7877I -- protocol Packet Received -- Type:type versionExplanation: A packet, of the specified type andversion, has been received by the specified protocol.System Action:None.User or Operator Response:System Programmer Response:DTCMPR7878IExplanation:output.System Action:formatstringNone.None.Used for displaying formatted packetNone.104 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesUser or Operator Response:System Programmer Response:None.None.DTCMPR7879I reason multicast group group oninterface interfaceExplanation: MPROUTE is joining or leaving thespecified multicast group on the specified interface.These groups are used for RIPv2 and OSPF protocols.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7881I field required for point to point linknameExplanation: 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 Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Modify theMPROUTE configuration file, adding the requiredkeyword.DTCMPR7882I Processing static route from stack,destination dest, maskmask, gateway gwExplanation: 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.User or Operator Response:None.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 Action:User or Operator Response:MPROUTE terminates.System Programmer Response:None.Check the searchorder 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 flgsExplanation: The specified interface is defined to theTCP/IP stack. MPROUTE has learned of this interfaceduring initialization.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7884I RouterID id not a configured systeminterface, taking defaultExplanation: 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.User or Operator Response:None.System Programmer Response: Modify theMPROUTE configuration file, providing a configuredinterface as the Router ID.DTCMPR7885I Route not added to stack routingtable - reasonExplanation: A dynamic route was not added to thestack’s routing table for the specified reason.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7886I MPROUTE SMSG commandacceptedExplanation: An SMSG command has been receivedby MPROUTE.System Action:User or Operator Response:System Programmer Response:The SMSG command processed.None.None.Chapter 6. MPROUTE Messages 105

MPROUTE MessagesDTCMPR7888I one statement ignored, conflicts withprevious two statementExplanation: MPROUTE has found a configurationstatement in the OMPROUTE configuration file thatconflicts with a previous configuration statement.System Action: MPROUTE continues, ignoring thespecified configuration statement.User or Operator Response:None.System Programmer Response: Modify theMPROUTE configuration file to resolve the conflict.DTCMPR7890I kwd ignored when stmt statement is awildcardExplanation: 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.User or Operator Response:None.System Programmer Response: Modify theMPROUTE configuration file, removing the extrakeyword.DTCMPR7891I Multiple stmt statements for subnetsub have kwd coded as primaryExplanation: 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.User or Operator Response:None.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 ignoredExplanation: 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.User or Operator Response:System Programmer Response:None.Modify theMPROUTE 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 nameExplanation: 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 Action:User or Operator Response:MPROUTE terminates.None.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 - commandExplanation: An SMSG command request wasreceived from the indicated user ID.System Action:User or Operator Response:System Programmer Response:The SMSG command is processed.None.None.DTCMPR7896I Could not obtain stack routing table,ioctl errno=errno:description,errno2=errno2Explanation: The attempt to obtain the contents of theTCP/IP stack’s route table failed with the specifiederror.System Action:User or Operator Response:MPROUTE terminates.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7898IMPROUTE Initialization CompleteExplanation: The MPROUTE application hascompleted its initialization.System Action:None.User or Operator Response:System Programmer Response:None.None.106 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesDTCMPR7900I Bad length packet, from source, typetypeExplanation: 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:User or Operator Response:The packet is discarded.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7901I Bad packet checksum, from source,type typeExplanation: An OSPF packet of the specified type hasbeen received. The packet has an invalid OSPFchecksum.System Action:User or Operator Response:The packet is discarded.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7902I Bad OSPF version, from source, typetypeExplanation: An OSPF packet of the specified type hasbeen received. The version field in the OSPF header isnot equal to 2.System Action:User or Operator Response:The packet is discarded.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7903I No matching SPF-interface for packetfrom source, type typeExplanation: 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.System Action:User or Operator Response:The packet is discarded.System Programmer Response:None.None.DTCMPR7904I Packet authentication failure, fromsource, type typeExplanation: An OSPF packet of the specified type hasbeen received. The packet fails to authenticate.System Action:User or Operator Response:The packet is discarded.None.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 typeExplanation: 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.System Action:User or Operator Response:The packet is discarded.System Programmer Response:None.None.DTCMPR7906I Bad packet type received from source,type typeExplanation: An OSPF packet of the specified type hasbeen received. The OSPF packet type field is invalid.System Action:User or Operator Response:The packet is discarded.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7908IReceived packet type type from sourceExplanation: An OSPF packet of the specified typewas received from the specified source.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7909I Sending unicast type type dstdestinationExplanation: A unicast OSPF packet of the specifiedtype has been sent to the specified IP destination.System Action:None.User or Operator Response:None.Chapter 6. MPROUTE Messages 107

MPROUTE MessagesSystem Programmer Response:None.System Programmer Response:None.DTCMPR7910I Sending multicast, type type,destination destination net net_indexinterface nameExplanation: A multicast OSPF packet of the specifiedtype sent out the specified interface to the specifieddestination.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7911I Retransmitting packet, type type,source -> destinationExplanation: A unicast OSPF packet of the specifiedtype is being retransmitted, using the specified sourceand destination.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7912I No FSM match, interface interface,state state, event eventExplanation: 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.User or Operator Response:None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7913I State change, interface interface, newstate state, event eventExplanation: The specified event occurred on thespecified interface, causing its state to transition to thespecified new state.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7914I No match for hello received onvirtual link, from sourceExplanation: A hello packet was received that couldonly match a virtual link, yet that link is notconfigured.System Action:User or Operator Response:The packet is discarded.None.DTCMPR7915I Network mask mismatch in hellofrom sourceExplanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the network mask of their commonnetwork.System Action:User or Operator Response:The packet is discarded.None.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 sourceExplanation: A hello packet was received from thespecified neighbor. The neighbor disagrees with thisrouter concerning the hello interval to be used on thecommon network.System Action:User or Operator Response:The packet is discarded.None.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 sourceExplanation: 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 Action:User or Operator Response:The packet is discarded.None.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 eventExplanation: 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.User or Operator Response:System Programmer Response:None.Possible internal error.108 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesContact the IBM Support Center.DTCMPR7919I State change, neighbor neighbor, newstate state, event eventExplanation: The specified event has been generated,causing the specified neighbor to transition to thespecified new state.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7920I Outstanding Database Descriptionpacket not avail for neighbor neighborExplanation: An attempt was made to retransmit aDatabase Description packet to the specified neighbor,but the packet could not be found.System Action:User or Operator Response:Retransmission is aborted.None.System Programmer Response: Possible internal error.Contact the IBM Support Center.DTCMPR7922I Bad length Link state advertisementreceived from neighborExplanation: 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:discarded.User or Operator Response:The partial advertisement isNone.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7923I from neighbor, LS advertisementchecksum fails: LS type type iddestination org sourceExplanation: 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:User or Operator Response:The advertisement is ignored.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7924I from neighbor, bad LS type,advertisement: typ type id destination orgsourceExplanation: 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.System Action:User or Operator Response:The advertisement is ignored.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7925I from neighbor, AS external link adv.on Virtual Link: typ type id destinationorg sourceExplanation: 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.System Action:User or Operator Response:The advertisement is ignored.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7926I from neighbor, old LS advertisement:typ type id destination org sourceExplanation: A link state advertisement has beenreceived from the specified neighbor. Theadvertisement is older than the current database copy.System Action:User or Operator Response:System Programmer Response:The advertisement is ignored.None.None.DTCMPR7927I from neighbor, self update: typ type iddestination org sourceExplanation: 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.System Action:None.User or Operator Response:None.Chapter 6. MPROUTE Messages 109

MPROUTE MessagesSystem Programmer Response:None.DTCMPR7928I from neighbor, new LS advertisement:typ type id destination org sourceExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR7929I from neighbor, Old acknowledgmentfor advertisement: typ type id destinationorg sourceExplanation: An unexpected link stateacknowledgment has been received from the specifiedneighbor. The acknowledgment, however, is for aprevious instantiation of the link state advertisement.System Action:User or Operator Response:System Programmer Response:The acknowledgment is ignored.None.None.DTCMPR7930I Bad acknowledgment from neighborfor advertisement: typ type id destinationorg sourceExplanation: An unexpected link stateacknowledgment has been received from the specifiedneighbor. The acknowledgment, however, is for thecurrent instantiation of the link state advertisement.System Action:User or Operator Response:System Programmer Response:The acknowledgment is ignored.None.None.DTCMPR7931I LS update retransmission to neighborneighborExplanation: A Link State Update packet containingretransmitted link state advertisements has been unicastto the specified neighbor. This probably indicatespacket loss during the flooding procedure.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7932I LS acknowledgment sent directly toneighbor neighborExplanation: A Link State Acknowledgment packethas been sent directly to the specified neighbor. This isin response to duplicate link state advertisementsreceived from the neighbor. This probably indicatespacket loss during the flooding procedure.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7933I Flushing advertisement: typ type iddestination org sourceExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7934I Originating LS advertisement: typtype id destination org sourceExplanation: The specified link state advertisement isbeing (re)originated by the router. This can be due totopological change, or the necessity to refresh.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7935I New MPROUTE route to destinationdesttype destination, type routetype cost costExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR7936I NBMA hello sent to IP destinationneighborExplanation: An OSPF hello has been sent to thespecified IP destination. This has been done over anon-broadcast, multi-access interface.System Action:None.User or Operator Response:System Programmer Response:None.None.110 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesDTCMPR7937I The OSPF routing protocol isdispositionExplanation: Displayed on router startup. Indicatesoperational status of the OSPF protocol.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7938I OSPF Interface interface (name) isnotan IP interface, interface not installedExplanation: Displayed on router start up when anOSPF interface address is configured, yet this addresshas not been configured to the TCP/IP stack.System Action:User or Operator Response:The OSPF interface is not installed.None.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 neighborExplanation: Unexpected link state acknowledgmenthas been received from the specified neighbor. Thisprobably indicates packet loss during the floodingprocedure.System Action:ignored.User or Operator Response:System Programmer Response:The link state acknowledgment isNone.None.DTCMPR7940I from neighbor, bad age field,advertisement: typ type id destination orgsourceExplanation: The specified link state advertisementhas been received from the specified neighbor. Theadvertisement’s LS age field is invalid.System Action:User or Operator Response:System Programmer Response:The advertisement is ignored.None.None.DTCMPR7941I Transit area area not configured,virtual link ignoredExplanation: A virtual link has been configured tohave a certain transit area, yet that area has not beenconfigured.System Action:User or Operator Response:The virtual link is ignored.None.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 discardedExplanation: 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.User or Operator Response:None.System Programmer Response: Modify theMPROUTE configuration statement to configure thebackbone area.DTCMPR7943I Destination desttype destination nowunreachableExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR7945I from neighbor, received unexpectedMaxAge: typ type id destination org sourceExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR7946I error in advertisement: typ type iddestination org sourceExplanation: The specified link state advertisementhas been received from the specified neighbor. Theadvertisement contains an error.System Action:User or Operator Response:The advertisement is discarded.None.System Programmer Response: Contact themanufacturer of the OSPF application on the sourceChapter 6. MPROUTE Messages 111

MPROUTE Messagesrouter to report the problem.DTCMPR7947I Stub area mismatch in hello fromsourceExplanation: 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:User or Operator Response:The Hello packet is ignored.None.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 orgsourceExplanation: 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:discarded.User or Operator Response:The link state advertisement isNone.System Programmer Response: Contact themanufacturer of the OSPF application on the sourcerouter to report the problem.DTCMPR7949I Dijkstra calculation performed, onnumber area(s)Explanation: As a result of a topology change, therouting table has been recalculated, starting with theDijkstra calculation.System Action:None.User or Operator Response:System Programmer Response:None.None.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:User or Operator Response:System Programmer Response:The advertisement is flushed.None.None.DTCMPR7951IReparsing Network LSA: LS_IDExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7956I OSPF area area not configured,interface interface not installedExplanation: 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.User or Operator Response:None.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 areaExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7962I Demand circuit support not active forarea areaExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.112 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesDTCMPR7963I Unchanged advertisement: typ type iddestination org source suppressed fordemand interfacesExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7964I Hello’s on interface interface toneighbor neighbor are being suppressed.Explanation: Displayed when hello suppressionbecomes active for the specified interface and neighbor.System Action:None.User or Operator Response:System Programmer Response:None.None.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.System Action:None.User or Operator Response:System Programmer Response:None.None.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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR7967I advertisement discarded, overflowsbuffer: LS type type id destination orgsourceExplanation: 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 Action:None.User or Operator Response:None.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 sourceExplanation: The version field in the RIP header didnot match the current version. This is probably causedby an error in the source host.System Action:User or Operator Response:The received RIP packet is ignored.None.System Programmer Response: Contact themanufacturer of the source host and report theproblem.DTCMPR8001Irequest received from host sourceExplanation: A RIP routing table request was receivedfrom another host.System Action: A routing table update will be sent tothe requesting host.User or Operator Response:System Programmer Response:None.None.DTCMPR8002I trace on to file received from hostsourceExplanation: A request from a host to turn RIP tracingon to a given log file was received.System Action:User or Operator Response:This request is ignored.System Programmer Response:DTCMPR8003INone.None.trace off received from host sourceExplanation: A request from a host to turn RIP tracingoff was received.System Action:User or Operator Response:This request is ignored.System Programmer Response:None.None.Chapter 6. MPROUTE Messages 113

MPROUTE MessagesDTCMPR8004Iresponse received from host sourceExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8005I bad command code command receivedfrom host sourceExplanation: 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 Action:User or Operator Response:The received RIP packet is ignored.None.System Programmer Response: Contact themanufacturer of the source host and report theproblem.DTCMPR8006I response received from off networkhost sourceExplanation: 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 Action:User or Operator Response:The packet is discarded.None.System Programmer Response: Examine audit trailsand other information to determine the original sourcehost.DTCMPR8008I dynamic route to destination fromsource disallowedExplanation: 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:User or Operator Response:System Programmer Response:Received dynamic route is ignored.None.None.DTCMPR8009I network destination now unreachablevia router router, deletedExplanation: An incoming RIP update from the routerthat was previously listed as the next hop to thedestination network has announced that the destinationis 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.User or Operator Response:System Programmer Response:None.None.DTCMPR8010I update route to net destination atmetric metric hops via router routerExplanation: 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.User or Operator Response:System Programmer Response:DTCMPR8011INone.None.send request to address sourceExplanation: MPROUTE is sending a RIP request fromeach of the addresses associated with an interfacewhich has just come up.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8012I sending broadcast response toaddress destination in count packets withnumber routesExplanation: The router is sending a normal RIPbroadcast update (triggered either by a timer or achange in the routing table) to the specified address.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8013I sending response to addressdestination in count packets with numberroutesExplanation: The router is sending a RIP update(triggered by a request from another host) to thespecified address.System Action:None.User or Operator Response:None.114 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesSystem Programmer Response:DTCMPR8015INone.sending packet to destinationExplanation: A RIP packet (either a routing tableupdate, or when an interface first comes up, a request)was sent to the specified destination.System Action:None.User or Operator Response:System Programmer Response:DTCMPR8017INone.None.network route to destination timed outExplanation: 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.User or Operator Response:System Programmer Response:DTCMPR8018INone.None.network route to destination deletedExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR8019I Mismatch version version receivedfrom host sourceExplanation: The version field in the received RIPheader did not match the configured version on thereceiving interface.System Action:User or Operator Response:The received RIP packet is ignored.None.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 sourceExplanation: A RIP packet from the specified host hasbeen rejected due to an authentication error caused byeither invalid authentication info or authentication notbeing enabled. This is probably caused by amisconfiguration.System Action:None.User or Operator Response:None.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 routesExplanation: The router is sending a normal RIP2update (triggered either by a timer or a change in therouting table) to the specified address.System Action:None.User or Operator Response:System Programmer Response:DTCMPR8023INone.None.The RIP routing protocol is dispositionExplanation: Displayed on router start up. Indicatesoperational status of the RIP protocol.System Action:None.User or Operator Response:System Programmer Response:None.None.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.System Action:User or Operator Response:The packet is discarded.System Programmer Response:DTCMPR8025INone.None.RIP send to destination failsExplanation: 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 Action:None.User or Operator Response:None.System Programmer Response: Other MPROUTEmessages will give the errno explanation for thisfailure.Chapter 6. MPROUTE Messages 115

MPROUTE MessagesDTCMPR8054I Add failed for net network; badnetwork numberExplanation: 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 Action:None.User or Operator Response:None.System Programmer Response: If the net is valid,there is a possible internal error, contact the IBMSupport Center.DTCMPR8055IRe-adding static route to net networkExplanation: This message is generated when a staticroute to a network is brought back into use.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8057I Added network network to interfaceinterface on net net_index interface nameExplanation: 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.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8058I Ignoring bad static route to network,mask maskExplanation: This message is generated when a badstatic route is encountered.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8059I Added network network with routevia gateway on net net_index interfacenameExplanation: 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.System Action:None.User or Operator Response:None.System Programmer Response:None.DTCMPR8061I Deleted net network route via gatewaynet net_index interface nameExplanation: This message is generated when aninterface goes down and the corresponding route isdeleted from the route table.System Action:None.User or Operator Response:System Programmer Response:DTCMPR8062INone.None.Subnet network definedExplanation: This message is generated when a newsubnetted network is defined.System Action:None.User or Operator Response:System Programmer Response:DTCMPR8063INone.None.Deleting subnetted network networkExplanation: This message is generated when asubnetted network is deleted. This happens when thereare no longer any interfaces to that network.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8064I RIP disabled on interface variablelength subnet masksExplanation: The router is configured with variablelength subnet masks on the same network, which RIPcan’t handle. Thus RIP is disabled on the interface.System Action:None.User or Operator Response:System Programmer Response:DTCMPR8066INone.None.IP protocol does not run over typeExplanation: An IP address was configured for a typeof network which currently doesn’t support IP.System Action:None.User or Operator Response:System Programmer Response:None.None.116 z/VM: TCP/IP Messages and Codes

MPROUTE MessagesDTCMPR8067I Network net_index interface name isinactiveExplanation: This message is generated when aninactive network interface is encountered duringinitialization, no direct routes will be created on thisnetwork.System Action:None.User or Operator Response:System Programmer Response:None.None.DTCMPR8088I The (ETC GATEWAYS) file wasfound, MPROUTE server will ignore itExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCMPR8079I SMSG command from user_id notauthorizedExplanation: 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 stackExplanation: 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.User or Operator Response: Notify the systemprogrammer about the problem.System Programmer Response: Verify which dynamicrouter you wish to run and only have this one runningwith the stack.Chapter 6. MPROUTE Messages 117

MPROUTE Messages118 z/VM: TCP/IP Messages and Codes

Chapter 7. NETSTAT MessagesThis 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||DTCNET104E Invalid option(s) specified withINTERVAL: optionsSeverity:Error.|Severity:Error.Explanation:a value.You specified a DROP parameter without||Explanation: You specified an extraneous option onthe NETSTAT command.System Action:The NETSTAT program exits.|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.|||||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 EXECSource File:Procedure Name:CMNETST PASCALParseCommandLine|DTCNET105ESeverity:Error.NetStat Error: explanation|||||||||||||DTCNET101E NETSTAT: TCP parameter requires avirtual machineSeverity:Error.Explanation: You specified a TCP parameter withoutspecifying a TCP/IP server.System Action:The NETSTAT program exits.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.Source File:Procedure Name:CMNETST PASCALParseCommandLineExplanation: TCP/IP could not obtain requestednetwork statistics. An error was encountered asdescribed by the explanation.System Action:The NETSTAT program exits.User or Operator Response: One of the followingNETSTAT options could not obtain the requiredinformation:v Allconnv Connv Devlinksv Gatev Homev Poolv Socketv Telnet.|DTCNET103ESeverity:Explanation:Error.System Action:Invalid parameter: BadParameterYou specified an invalid parameter.The NETSTAT program exits.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.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.Source File:Procedure Name:CMNETST PASCALBadReturnCodeSource File:CMNETST PASCALProcedure Name:ParseCommandLine© Copyright IBM Corp. 1987, 2002 119

NETSTAT Messages|DTCNET154ESeverity:Error.explanationExplanation: An error occurred processing theNETSTAT CP parameter as described by the explanation.System Action:The NETSTAT program exits.User or Operator Response: Examine the error asdescribed by the explanation. Resolve the problem andresubmit the NETSTAT command.|||||||||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.Source File:CMNETST PASCAL|Source File:CMNETST PASCALProcedure Name:DoCpCmd||Procedure Name: DoDrop, DoResetPoolInform,DoCpCmd, DoDeleteArp, DoResetDos|DTCNET160ESeverity:Explanation:dropped.Error.System Action:No such connectionA connection could not be successfullyThe NETSTAT program exits.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.Source File:Procedure Name:CMNETST PASCALDoDrop|DTCNET326E Netstat: Missing or invalid parameterafter ARPSeverity:Recoverable error.Explanation: The parameter following ARP is eithernot valid or missing.System Action:The NETSTAT program exits.User or Operator Response: Specify the TCPIPaddress to be queried by ARP, and re-enter theNETSTAT command.System Programmer Response:Source File:Procedure Name:CMNETST PASCALNone.ParseCommandLine||||||||||||DTCNET266ESeverity:Error.Cannot use TCP/IP: explanationExplanation: TCP/IP could not begin processing. Anerror has been encountered as described by theexplanation.System Action:The NETSTAT program exits.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.|||||||||||DTCNET331E INTERVAL option must be invokedvia the NETSTAT EXECSeverity:Explanation:directly.Error.System Action:The NETSTAT MODULE was invokedThe NETSTAT program exits.User or Operator Response: Change the invocationsuch that the NETSTAT EXEC gets executed. (ie.″address command ’NETSTAT INTERVAL’″ is notallowed)Source File:CMNETST PASCAL|Source File:CMNETST PASCAL|Procedure Name:ParseCommandLine|||Procedure Name:MainDTCNET325E TCPIP reports error: You are notauthorized to issue this command|DTCNET338E Addr MAC address is not in the ARPtableSeverity:Recoverable error.|||||Severity:Error.Explanation: You are not authorized to issueNETSTAT commands CP, DelArp, Drop, ResetDos orResetPool.System Action:The request is ignored. ProcessingExplanation: The address specified is not currently inthe ARP table.System Action:User or Operator Response:System Programmer Response:The NETSTAT program exits.None.None.120 z/VM: TCP/IP Messages and Codes

NETSTAT MessagesSource File:CMNETST PASCAL|System Action:The NETSTAT program exits.|||||Procedure Name:DoQueryArpDTCNET339E Userid specified for TCP must be 8characters or lessSeverity:Explanation:is too long.Error.You specified a TCP/IP server name that|||||||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.Source File:Procedure Name:CMNETST PASCALParseCommandLine||||||||||||||||||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.Source File:Procedure Name:CMNETST PASCALParseCommandLineDTCNET341E NETSTAT: Missing or invalid IPaddress after DELARPSeverity:Error.Explanation: The parameter following DELARP iseither not valid or missing.System Action:The NETSTAT program exits.User or Operator Response: Specify a valid IP addressto be deleted from the ARP cache and re-enter theNETSTAT command.Source File:Procedure Name:CMNETST PASCALParseCommandLine||||||||||||||DTCNET348E NETSTAT: Missing or invalid IPaddress after UNBLOCKSeverity:Error.Explanation: The parameter following UNBLOCK iseither not valid or missing.System Action:The NETSTAT program exits.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.Source File:Procedure Name:DTCNET349ESeverity:Error.CMNETST PASCALParseCommandLineTCPIP reports error explanationExplanation: While processing the NETSTATRESETPOOL option, an error has been encountered asdescribed by the explanation.|||DTCNET343E NETSTAT: Missing or invalidparameter after IDENTIFYSeverity:Error.System Action:The NETSTAT program exits.User or Operator Response: Inform the systemprogrammer that you encountered an error processingthe NETSTAT RESETPOOL option.||Explanation: The parameter following IDENTIFY iseither not valid or missing.System Programmer Response: Check the PROFILETCPIP file for the definition of the POOLSIZE.||||||System Action:The NETSTAT program exits.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.For information about modifications to the TCP/IPProfile POOLSIZE, see the TCP/IP Planning andCustomization.Source File:Procedure Name:CMNETST PASCALDoResetPoolInform||Source File:Procedure Name:CMNETST PASCALParseCommandLine|DTCNET371E Netstat: Connection number ConnNumis not valid|||DTCNET347E NETSTAT: Missing or invalid IPaddress after BLOCKSeverity:Error.Severity:Error.Explanation: The indicated connection number is nota valid setting for the NETSTAT DROP statement. Theconnection number must be numeric.||Explanation: The parameter following BLOCK iseither not valid or missing.System Action:User or Operator Response:The NETSTAT program exits.Specify a valid numericChapter 7. NETSTAT Messages 121

NETSTAT MessagesTCP/IP connection number to drop following theDROP parameter, and resubmit the NETSTATcommand.System Programmer Response:Source File:Procedure Name:CMNETST PASCALNone.ParseCommandLine|||||System Action:The NETSTAT program exits.User or Operator Response: Correct the error andre-enter the NETSTAT command.Source File:Procedure Name:CMNETST PASCALDoObey||||||||||||||||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.System Action:Processing continues.User or Operator Response: Issue the NETSTAT DOScommand to obtain information about the type andfrequency of attacks.System Programmer Response:Source File:DTCNET500ESeverity:Error.CMNETST PASCALNone.MonQuery fails: explanationExplanation: TCP/IP could not obtain the RequestedControl Block information. An error has beenencountered as described by the explanation.System Action:The NETSTAT program exits.User or Operator Response: One of the followingNETSTAT options could not obtain the requiredControl Block information:v Allconnv Conn.||||||||||||||DTCNET504E NETSTAT: Missing statement afterOBEYSeverity:Error.Explanation: You used the OBEY function withoutspecifying a configuration statement to be processed.System Action:The NETSTAT program exits.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.Source File:Procedure Name:CMNETST PASCALDoObeyDTCNET509E Selecting connections can only bedone with ALL, ALLConn, CLients,COnn, Gate, IDENTify, Interval, TELnetSeverity:Recoverable error.Explanation: You attempted to select a connectionwithout the use of one of the specified parameters.System Action:The NETSTAT program exits.User or Operator Response: Specify a valid NETSTATcommand before selecting connections and re-enter theNETSTAT command.System Programmer Response:Source File:Procedure Name:CMNETST PASCALLimitSearchToNone.Inform the system programmer the NETSTAT option inwhich you encountered the error.|DTCNET510EParenthesis but no search criteriaSystem 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.Source File:Procedure Name:CMNETST PASCALPipeDataSeverity:Recoverable error.Explanation: You specified a NETSTAT commandwithout the appropriate search criteria.System Action:The NETSTAT program exits.User or Operator Response: Specify the search criteriaand re-enter the NETSTAT command.System Programmer Response:None.||DTCNET501ESeverity:Error.explanationSource File:Procedure Name:CMNETST PASCALParseCommandLine||Explanation: The OBEY function encountered an errordescribed by the explanation.122 z/VM: TCP/IP Messages and Codes

NETSTAT Messages|DTCNET511E Close parenthesis precedes searchcriteriaSource File:Procedure Name:CMNETST PASCALParseCommandLineSeverity:Recoverable error.Explanation: You entered the NETSTAT commandwith incorrect syntax.|DTCNET515ESeverity:Invalid netstat option: optionRecoverable error.System Action:The NETSTAT program exits.User or Operator Response: Correct the syntax errorby removing the close parenthesis before the searchcriteria, and re-enter the NETSTAT command.System Programmer Response:None.Explanation: You specified a NETSTAT commandwith an invalid option.System Action:The NETSTAT program exits.User or Operator Response: Re-enter the NETSTATcommand with a valid option.Source File:CMNETST PASCALSystem Programmer Response:None.Procedure Name:LimitSearchToSource File:CMNETST PASCAL|DTCNET512E Too many selection values: Maximumis numberSeverity:Explanation:System Action:Recoverable error.You specified too many selection values.The NETSTAT program exits.|Procedure Name:DTCNET516ESeverity:Error.ParseCommandLineInterval value of val is invalidExplanation: You specified an interval value that isnot valid and could not be interpreted.User or Operator Response: Remove extraneousselections and re-enter the NETSTAT command.System Programmer Response:Source File:Procedure Name:CMNETST PASCALLimitSearchToNone.System Action:The NETSTAT program exits.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.System Programmer Response:None.|DTCNET513E Search criteria parameter string is toolongSeverity:Recoverable error.Explanation: You specified a search parameter stringthat was longer than 16 characters.System Action:The NETSTAT program exits.User or Operator Response: Correct the search criteriaparameters and re-enter the NETSTAT command.System Programmer Response:Source File:Procedure Name:CMNETST PASCALLimitSearchToNone.|Source File:CMNETST PASCALDTCNET517E Interval value of val is invalid.Maximum allowed is 3600Severity:Explanation:too large.Error.System Action:You specified an interval value that isThe NETSTAT program exits.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.|DTCNET514E Select Option Specified but no searchcriteriaSystem Programmer Response:Source File:CMNETST PASCALNone.Severity:Recoverable error.Explanation: You specified a NETSTAT commandwithout the appropriate search criteria.System Action:The NETSTAT program exits.User or Operator Response: Specify the search criteriaand re-enter the NETSTAT command.System Programmer Response:None.Chapter 7. NETSTAT Messages 123

NETSTAT Messages124 z/VM: TCP/IP Messages and Codes

Chapter 8. NFS MessagesNumbered MessagesThis chapter contains Network File System (NFS) messages.This 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:Procedure Name:NFSMAINC CmainDTCNFS1301E 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.Source File:Procedure Name:DTCNFS1302INFSMAINC CmainTrace mask value set to maskExplanation: The mask for the VMNFS server internaltrace facility has been set.System Action:None.User or Operator Response:Source File:Procedure Name:NFSMAINC CmainNone.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:256.The default number of block buffers isUser or Operator Response: If desired, restart theVMNFS server with a correct block buffers value.Source File:Procedure Name:NFSMAINC CmainDTCNFS1304E 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.System Action:256.The default number of block buffers isUser or Operator Response: If desired, restart theVMNFS server with a correct disk block buffers value.Source File:Procedure Name:NFSMAINC CmainDTCNFS1305E Number of buffers value buffers is toosmall; using default of default_buffers.Explanation: The number of disk block buffersspecified is too small.System Action:256.The default number of block buffers isUser or Operator Response: If desired, restart theVMNFS server with a correct block buffers value.Source File:Procedure Name:NFSMAINC CmainDTCNFS1306I Number of disk block buffers set tonnnnExplanation: This informational message was issuedbecause the B argument was specified when VMNFSwas invoked.System Action:None.User or Operator Response:Source File:NFSMAINC CNone.© Copyright IBM Corp. 1987, 2002 125

NFS MessagesProcedure Name:mainProcedure Name:mainDTCNFS1307E Invalid VMNFS command argumentignored: number nn, value hex-valueExplanation: An invalid argument was specified whenVMNFS was invoked.System Action:User or Operator Response:reissue the command.Source File:Procedure Name:The incorrect value is ignored.NFSMAINC CmainCorrect the argument andDTCNFS1308I 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).System Action:None.User or Operator Response: If you wish to change theaccess control used, restart VMNFS with theappropriate argument.Source File:Procedure Name:DTCNFS1309INFSMAINC CmainAnonymous access will be allowedExplanation: :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.System Action:None.User or Operator Response: If anonymous access isnot desired, change the DTCPARMS entry to:Anonymous.No and restart the server.Source File:Procedure Name:NFSMAINC CmainDTCNFS1310I External mount monitor VMNFSMONEXEC will be usedExplanation: This message indicates an externalmonitor is present to screen mount requests and givesthe file mode where the exec was found.System Action:None.User or Operator Response:Source File:NFSMAINC CNone.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.Source File:Procedure Name:DTCNFS1313INFSMAINC CmainOpened debug file vmnfs.logExplanation: The ’D’ (debug) argument was specifiedwhen VMNFS was started.System Action:vmnfs.log.User or Operator Response:Source File:Procedure Name:Trace information will be written toNFSMAINC CmainNone.DTCNFS1314I Registration with Portmap failed;waiting 30 seconds before trying again.Explanation: The registration by VMNFS with the portmapper has failed.System Action:times.VMNFS attempts registration threeUser or Operator Response: If necessary, determine ifthe port mapper is available.Source File:Procedure Name:DTCNFS1315IExplanation:completed.System Action:NFSMAINC CmainUser or Operator Response:Source File:Procedure Name:Registration completed.Registration with the port mapper hasVMNFS processing continues.NFSMAINC CmainNone.DTCNFS1316S nfsmain: return code returncode fromcextpostExplanation: An attempt to create an interrupthandler failed. The return code is listed to help withproblem resolution.126 z/VM: TCP/IP Messages and Codes

NFS MessagesSystem Action:VMNFS server processing terminates.User or Operator Response: See the HNDEXTmacroinstruction in the z/VM: CMS Macros andFunctions Reference.Source File:Procedure Name:NFSMAINC CmainDTCNFS1318E Unexpected exit code exitcode from:functionExplanation: 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. Ifitcannotbe corrected, report it to the IBM Support Center.Source File:Procedure Name:DTCNFS1321INFSMAINC CmainSFS operations will be supported.Explanation: This message indicates that NFS clientrequests for SFS objects will be honored.System Action:None.User or Operator Response:Source File:Procedure Name:NFSMAINC CmainNone.DTCNFS1322E Exit code = exitcode from call toVMNFSANCExplanation: 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.Source File:Procedure Name:NFSMAINC CmainDTCNFS1324I External interrupt requestedtermination.Explanation: The VMNFS server received a request toterminate the server.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing terminates.NFSMAINC CmainNone.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:User or Operator Response:Source File:Procedure Name:The ECB post is ignored.NFSMAINC CmainNone.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:Procedure Name:NFSMAIN CmainDTCNFS1331S Error code ReturnCode from c_ciucvsever path pathidExplanation: 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 callingChapter 8. NFS Messages 127

NFS MessagesSIGERROR, 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:Procedure Name:FH@HIST Cfh_checkDTCNFS1332S fh_check: error code ReturnCode (xrc)from c_ciucv connect request to vaddrvaddr disk userid.addressExplanation: 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.Source File:Procedure Name:DTCNFS1333SFH@HIST Cfh_checkVaddr vaddr userid.addressExplanation: Identifies the disk for which an IUCVconnection request to *BLOCKIO failed. This isfollowed by a call to SIGERROR.System Action:None.User or Operator Response:Source File:Procedure Name:FH@HIST Cfh_checkNone.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:abandoned.The NFS client’s request isUser 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.Source File:Procedure Name:FH@HIST Cdb_lookupDTCNFS1335E 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.Source File:Procedure Name:FH@HIST Cck_mdateDTCNFS1336I time ck_mdate is detachinguserid.address.Explanation: This message is issued after messageDTC1335E. VMNFS is detaching the minidisk.System Action:User or Operator Response:Source File:Procedure Name:VMNFS Server processing continues.FH@HIST Cck_mdateNone.DTCNFS1337E ck_mdate: RC=ReturnCode fromdetach.Explanation: VMNFS received a nonzero return codewhile detaching a minidisk. The ReturnCode is listed tohelp with problem isolation.System Action:VMNFS Server processing continues.User or Operator Response: If the error recurs, reportit to the IBM Support Center.Source File:Procedure Name:FH@HIST Cck_mdateDTCNFS1338E 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.Source File:Procedure Name:FH@HIST Cck_mdate128 z/VM: TCP/IP Messages and Codes

NFS MessagesDTCNFS1339E 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.User or Operator Response: None.Source File: RDLABEL CProcedure Name: open_pathDTCNFS1350I Refresh command came from: userid atnodeidExplanation: This message accompanies a previousmessage with an invalid syntax. It indicates where theoriginal request was issued from.System Action:User or Operator Response:Source File:Procedure Name:VMNFS Server processing continues.REQSMSG CsmrefreshNone.DTCNFS1340E open_path error code code (0xcode)device addressExplanation:Valid values are as follows:< 0: c_iucv value * -1 (error in CMSIUCV .connect macro).> 0 error from *BLOCKIO:100 = (100 + error in *BLOCKIO read request).1000 = Bad label format.System Action: Error status (such as ENOMEM) isreturned to the NFS client.User or Operator Response:Source File:Procedure Name:DTCNFS1342ERDLABEL CrdlabelNone.Invalid argument arg ignored.Explanation: The VMNFS server received an SMSGrequest with an invalid argument.System Action:User or Operator Response:and reissue.Source File:Procedure Name:VMNFS server processing continues.REQSMSG CsmqueryCorrect the commandDTCNFS1343I Valid query arguments are: LINK,MOUNT, RESOURCE, and CONFIGExplanation: An invalid SMSG QUERY request wassent to the VMNFS server. The valid arguments arelisted in the message.System Action:User or Operator Response:command and reissue.Source File:Procedure Name:VMNFS Server processing continues.REQSMSG CsmqueryCorrect the QUERYDTCNFS1351W 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:User or Operator Response:Source File:Procedure Name:The program returns to the caller.REQSMSG CNone.smrefresh, smdetachDTCNFS1352E time Refresh request for [userid.address| VMNFS.CONFIG] rejected becauseunique access cannot be obtainedExplanation: VMNFS attempted to gain control of theminidisk to be refreshed, or of the VMNFS server as awhole, but could not.System Action:User or Operator Response:command.Source File:Procedure Name:VMNFS Server processing continues.REQSMSG CsmrefreshReissue the refreshDTCNFS1353I [Disk | File] [userid.address|VMNFS.CONFIG] refreshed.Explanation: The request to refresh the minidisk orVMNFS CONFIG file was successful.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing continues.REQSMSG CsmrefreshNone.Chapter 8. NFS Messages 129

NFS MessagesDTCNFS1354E time [Disk | File] [userid.address |VMNFS.CONFIG] refresh failed; errorcode = ReturnCodeExplanation: 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 = (100 + error in *BLOCKIO read request).1000 = Bad label format.System Action:The program returns to the caller.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.Source File:Procedure Name:DTCNFS1356IREQSMSG Csmrefreshtime SMSG from userid, stringExplanation: When certain tracing is activated, thismessage displays the response, string, sent to user IDuserid as a result of processing an SMSG request.System Action:None.User or Operator Response:Source File:Procedure Name:REQSMSG CsmrefreshNone.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.Source File:Procedure Name:REQSMSG CsmdetachDTCNFS1359I time SMSG from origin: detachuserid.addressExplanation: A request was received to detach thelisted minidisk.System Action:request.User or Operator Response:Source File:Procedure Name:VMNFS will process the detachREQSMSG CsmdetachNone.DTCNFS1360I RC=Return_Code from detachinguserid.addressExplanation: 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:User or Operator Response:Source File:Procedure Name:The detach request is aborted.REQSMSG CsmdetachNone.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:User or Operator Response:Source File:Procedure Name:DTCNFS1362EThe detach request is aborted.REQSMSG CsmdetachNone.Trace write failed; error ReturnCodeExplanation: 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.System Action:None.User or Operator Response:Source File:Procedure Name:None.REQSMSG C, SIGERROR Csmtwrite130 z/VM: TCP/IP Messages and Codes

NFS MessagesDTCNFS1363E 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.System Action:None.User or Operator Response:Source File:Procedure Name:DTCNFS1364IREQSMSG CsmtwriteNone.Trace write successful to file fileidExplanation: An SMSG request to write the trace filewas successful.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing continues.None.REQSMSG C, SIGERROR CsmtwriteDTCNFS1365I Trace data written to file fileid byuserid at nodeid (time).Explanation: An SMSG request to write the trace datato a file was successful.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing continues.REQSMSG CsmtwriteNone.DTCNFS1366E Invalid mask value; trace maskremains mask-valueExplanation: 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:specifying a valid value.Source File:Procedure Name:REQSMSG CsmmaskReissue the request,DTCNFS1367I Trace mask set to new_mask_value;previous value was old_mask_valueExplanation: An SMSG request was made to changethe trace mask value.System Action: VMNFS server processing continuesusing the new mask value.User or Operator Response:Source File:Procedure Name:REQSMSG CsmmaskNone.DTCNFS1368I Trace mask set to new_mask_value byorigin; previous value was old_mask_valueExplanation: An SMSG request to set the trace maskvalue was processed.System Action: VMNFS server processing continuesusing the new mask value.User or Operator Response:Source File:Procedure Name:REQSMSG CsmmaskNone.DTCNFS1369E reqsmsg: discarding too long SMSGfrom originExplanation: An SMSG request was received with aninvalid syntax.System Action:User or Operator Response:reissue.Source File:Procedure Name:DTCNFS1371EVMNFS server processing continues.REQSMSG CreqsmsgCorrect the request andUnknown verb in command: commandExplanation: An SMSG request was received for anunknown command.System Action:User or Operator Response:reissue.Source File:Procedure Name:VMNFS server processing continues.REQSMSG CreqsmsgCorrect the message andDTCNFS1374E *blockio: *BLOCKIO error ReturnCodefrom c_iucv send.Explanation: An unexpected error was received whileprocessing a *BLOCKIO function. The return code islisted.System Action:client.An error status is returned to the NFSUser or Operator Response: Determine the initialfailing case and report it to the IBM Support Center.Source File:Procedure Name:BLOCKIO Cblockio_driverChapter 8. NFS Messages 131

NFS MessagesDTCNFS1375E blockio: abnormal responseReturnCode (not ’message complete’)Explanation: An unexpected return code was receivedwhile processing a *BLOCKIO function. The returncode is listed.System Action:client.An error status is sent to the NFSUser or Operator Response: Determine the initialfailing case and report it to the IBM Support Center.Source File:Procedure Name:BLOCKIO Cblockio_driverDTCNFS1376I 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:level of CP is being used.Source File:Procedure Name:BLOCKIO Cblockio_driverDetermine if the wrongDTCNFS1377E blockio: *BLOCKIO general errorReturnCodeExplanation: An unexpected return code was receivedfrom a *BLOCKIO request.System Action:client.An error status is sent to the NFSUser or Operator Response: Determine the initialfailing case, and report it to the IBM Support Center.Source File:Procedure Name:BLOCKIO Cblockio_driverDTCNFS1381E blockio: block {read|write} errorReturn_Code block number =block_number block address =buffer_address : disk vaddr = vdev disk =userid.addressExplanation: An unexpected return code was receivedwhile processing a *BLOCKIO function. The listedinformation will help indicate where the error occurred.System Action:client.An error status is returned to the NFSUser or Operator Response: Determine the initialfailing case, and report it to the IBM Support Center.Source File:Procedure Name:BLOCKIO Cwr_bloks, bmbreadDTCNFS1383I reqmount: unknown authorizationflavor flavor from foreign address addressExplanation: An unknown style of authentication wasreceived. VMNFS accepts only AUTH_UNIX,AUTH_DES, or AUTH_SHORT.System Action:NFS client.An error response is returned to theUser or Operator Response: Determine why anunsupported authentication style was used by theclient.Source File:Procedure Name:DTCNFS1384IREQSTART Ccheck_authtime Umount userid.address usage data:Explanation: VMNFS received a request to unmountthe specified device.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing continues.REQSTART CreqmountNone.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.System Action:User or Operator Response:used by the VMNFS server.Source File:VMNFS server processing terminates.INIT CProcedure Name:initCorrect the level of CMSDTCNFS1385E 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.System Action:User or Operator Response:Source File:Procedure Name:VMNFS server processing continues.REQSTART CreqmountReissue the umount.132 z/VM: TCP/IP Messages and Codes

NFS MessagesDTCNFS1386IExplanation:successful.System Action:User or Operator Response:Source File:Procedure Name:Umount: userid.address detachedA request to unmount a minidisk wasVMNFS server processing continues.REQSTART CreqmountNone.DTCNFS1387I time Umount-all userid.address usagedata:Explanation: VMNFS received a request to umount alldisks and directories.System Action:User or Operator Response:Source File:Procedure Name:DTCNFS1388IExplanation:successful.System Action:VMNFS server processing continues.REQSTART CreqmountUser or Operator Response:Source File:Procedure Name:None.Umount-all: userid.address detachedA request to unmount a directory wasVMNFS server processing continues.REQSTART CreqmountNone.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 ofNFS protocol]System Action:client.The error status is sent to the NFSUser 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.Source File:Procedure Name:REQSTART Ccheck_authDTCNFS1390INFS client address = addressExplanation: 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 ofNFS protocol]System Action:client.The error status is sent to the NFSUser 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.Source File:Procedure Name:REQSTART Ccheck_authDTCNFS1391E 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.Source File:Procedure Name:DTCNFS1392IREQSTART CreqstartUnknown 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 NFSChapter 8. NFS Messages 133

NFS MessagesRFC. Perhaps the client can be configured to avoidmaking these calls.Source File:Procedure Name:REQSTART CreqstartDTCNFS1394I 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.System Action:VMNFS server processing continues.User or Operator Response: Correct the password orgive LOGON BY privileges to byuserid.Source File:Procedure Name:NFSLINK CcheckpwDTCNFS1400E Return code Return_Code from:commandExplanation: An unexpected return code was receivedwhile processing the listed AUTOLINK command. Thereturn code displayed should help in problemdetermination.System Action:client.An error status is sent to the NFSUser or Operator Response: Determine the cause ofthe error. If necessary, call the IBM Support Center.Source File:Procedure Name:NFSLINK CnfslinkDTCNFS1403E 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.User or Operator Response:Source File:Procedure Name:LINKDEV CnfslinkNone.DTCNFS1404E Unexpected return code ReturnCodefrom: commandExplanation: The listed CP command failed with thelisted return code.System Action:Another message is sent to theSIGERROR 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.User or Operator Response:Source File:Procedure Name:None.NFSLINK C, INIT Cnfslink, initDTCNFS1406E 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:warningsExplanation: An unexpected return code and reasoncode was received while processing a request.System Action:client.An error status is returned to the NFSUser 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_functionDTCNFS1410E 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.Source File:Procedure Name:NFSLINK Ccall_VMNFSMONDTCNFS1411E call_VMNFSMON: error parsingGLOBALV data from external mountmonitor.Explanation: An unexpected error occurred parsingthe GLOBALV data after calling the VMNFSMON exitroutine.134 z/VM: TCP/IP Messages and Codes

NFS MessagesSystem Action: An error status is returned to the NFSclient.User or Operator Response: Correct the GLOBALVproblem or if necessary, contact the IBM SupportCenter.Source File:Procedure Name:DTCNFS1416ENFSLINK Ccall_VMNFSMONSIGERROR called: errorstringExplanation: 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:Procedure Name:SIGERROR CSIGERRORDTCNFS1420E 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.System Action:VMNFS server processing continues.User or Operator Response: If the error recurs, reportit to the IBM Support Center.Source File:Procedure Name:TASKEND C, BLOCKIO CTASKEND, wr_bloksDTCNFS1421ERC = Return_Code from commandExplanation: The VMNFS server did not find a 191minidisk defined or an error occurred while trying todetermine if the 191 minidisk was defined.System Action:VMNFS server processing terminates.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 CProcedure Name:initDTCNFS1422E Init error: cannot understandresponse to ″CP Query Virtual 191″Explanation: The expected response was not receivedfrom the command.System Action:VMNFS server processing terminates.User or Operator Response: Try to determine thefailing case and report the problem to the IBM SupportCenter.Source File:INIT CProcedure Name:initDTCNFS1423E 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.System Action:VMNFS server processing terminates.User or Operator Response: Make the 191 diskavailable in read-write mode to the VMNFS server.Source File:INIT CProcedure Name:initDTCNFS1424I 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.System Action:VMNFS processing continues.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 CChapter 8. NFS Messages 135

NFS MessagesProcedure Name:initDTCNFS1425I 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.System Action:VMNFS processing continues.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 CProcedure Name:initDTCNFS1426I 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.System Action:VMNFS processing continues.User or Operator Response: You may want toredefine any minidisks that conflict with this range.Source File:INIT CProcedure Name:initDTCNFS1427E 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 CProcedure Name:initDTCNFS1428E 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 CProcedure Name:initDTCNFS1429E tracev: invalid argument type type incall from address addressExplanation: 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.System Action:None.User or Operator Response:the IBM Support Center.Source File:Procedure Name:DTCNFS1430ITRACEV CtracevFormat is: tvprint fileid.Report the problem toExplanation: This message is displayed when theTVPRINT module is not invoked with the correctnumber of parameters.System Action:User or Operator Response:and reissue the command.Source File:Procedure Name:DTCNFS1431ITVPRINT processing terminates.TVPRINT CmainCorrect the parametersExample: tvprint tracev.fileExplanation: This message is displayed when theTVPRINT module is not invoked with the correctnumber of parameters.System Action:User or Operator Response:and reissue the command.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainCorrect the parameters136 z/VM: TCP/IP Messages and Codes

NFS MessagesDTCNFS1432I If HEX is specified, hexadecimaldisplay of all trace data follows theformatted display.Explanation: This message is displayed when theTVPRINT module is not invoked with the correctnumber of parameters.System Action:User or Operator Response:and reissue the command.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainCorrect the parametersDTCNFS1433E Invalid tracev buffer size buff_size(0xhex_buff_size)Explanation: An incorrect size of the internal tracebuffer was determined.System Action:TVPRINT processing terminates.User or Operator Response: Ensure the correct fileidwas specified on the TVPRINT command.Source File:Procedure Name:TVPRINT CmainDTCNFS1434I 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:User or Operator Response:Source File:Procedure Name:TVPRINT processing continues.TVPRINT CmainNone.DTCNFS1435E Cannot allocate tracev buffer ofbuff_size (0xhex_buff_size) bytes.Explanation: A request to obtain virtual storage in thelisted size was unsuccessful.System Action:TVPRINT processing terminates.User or Operator Response: Define a larger virtualmachine for use in formatting the trace file.Source File:Procedure Name:DTCNFS1436ETVPRINT Cmainfseek error on input file.Explanation: An unexpected return code was receivedwhile processing the trace file.System Action:TVPRINT processing terminates.User or Operator Response:input file was used.Source File:Procedure Name:TVPRINT CmainDetermine if the correctDTCNFS1437E Error reading tracev buffer frominput fileExplanation: An unexpected return code was receivedwhile processing the tracev buffer.System Action:User or Operator Response:input file was used.Source File:Procedure Name:DTCNFS1438ETVPRINT processing terminates.TVPRINT CmainDetermine if the correctFailure reading tracev bufferExplanation: An unexpected return code was receivedwhile reading the input file.System Action:User or Operator Response:input file was used.Source File:Procedure Name:DTCNFS1439ETVPRINT processing terminates.TVPRINT CmainDetermine if the correctCannot allocate storage map.Explanation: A request to obtain storage by theTVPRINT module failed.System Action:TVPRINT processing terminates.User or Operator Response: Define a larger virtualmachine to process the trace file or determine if thecorrect input file was used.Source File:Procedure Name:DTCNFS1440ETVPRINT CmainFailure reading storage mapExplanation: An unexpected error was receivedreading the storage map while processing the TVPRINTcommand.System Action:User or Operator Response:input file was used.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainDetermine if the correctChapter 8. NFS Messages 137

NFS MessagesDTCNFS1441EFormat error in simple storage map.Explanation: The storage map being processed wasnot in the correct format.System Action:User or Operator Response:input file was used.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainDetermine if the correctDTCNFS1442I 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.System Action:None.User or Operator Response:Source File:Procedure Name:TVPRINT CmainNone.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.System Action:User or Operator Response:Source File:Procedure Name:DTCNFS1444ETVPRINT processing terminates.TVPRINT CmainNone.Cannot open tracev callid file fileidExplanation: An unexpected error was received tryingto open the specified file.System Action:User or Operator Response:available.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainDetermine if the file isDTCNFS1445E Format error reading tracev callid filefileid at line line_num : datumExplanation: While processing the callid file, anunexpected error occurred.System Action:User or Operator Response:callid file was used.Source File:TVPRINT processing terminates.TVPRINT CDetermine if the correctProcedure Name:mainDTCNFS1446I Time stamp of first tracev element is:timeExplanation: This message indicates the timeassociated with the trace element.System Action:User or Operator Response:Source File:Procedure Name:TVPRINT processing continues.TVPRINT CmainNone.DTCNFS1447E Invalid format for tracev element atrelative address address, previouselement at relative address prev_addressExplanation:System Action:User or Operator Response:trace file was used.Source File:Procedure Name:An invalid trace record was found.TVPRINT processing terminates.TVPRINT CmainDetermine if the correctDTCNFS1448E Invalid callid value value(0xhex_value).Explanation: An unexpected value was found whileprocessing the trace file.System Action:User or Operator Response:trace file was used.Source File:Procedure Name:TVPRINT processing terminates.TVPRINT CmainDetermine if the correctDTCNFS1450E Unrecognized tracev callid value value(0xhex_value)Explanation: An unexpected value was found whileprocessing the trace file.System Action:User or Operator Response:Source File:Procedure Name:DTCNFS1464IProcessing of the element is ignored.TVPRINT CmainNone.Directory is not locked.Explanation: This message indicates the minidiskdirectory was not locked.System Action:User or Operator Response:TVPRINT processing continues.None.138 z/VM: TCP/IP Messages and Codes

NFS MessagesSource File:Procedure Name:TVPRINT CmainDTCNFS1472I 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:Procedure Name:NFSRENAM CnsfrenameDTCNFS1473E File erase failure: disk userid.addressfile filename filetypeExplanation: 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 aminidisk from more than one CMS virtual machinev Disk write errors because I/O operations were notcorrectly completed (because of power or hardwarefailures).System Action:NFS client.I/O error status is returned to theUser 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.Source File:Procedure Name:NFSRENAM CnfseraseDTCNFS1477S FINDBLOK: wait for Buffer Blockfailed block=block_numberdevice=userid.address vaddr=vaddrExplanation: 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:abandoned.User or Operator Response:processing it is aborted.Source File:Procedure Name:The NFS client’s request isFINDBLOK CfindblokNone. The taskDTCNFS1482E returning cc=cc rc=ReturnCode fromdiag 0x4CExplanation: 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:of FALSE.The program continues with a returnUser 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:Procedure Name:NFSUTIL CsenddataDTCNFS1486E Record length exceeds CMS Vmaximum: file offset xoffsetExplanation: 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:client.User or Operator Response:Source File:Procedure Name:NFSERR_IO is returned to the NFSNFSWRIT1 Cwrite_VNone.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.User or Operator Response:Source File:Procedure Name:PRINTLOG CmainNone.Chapter 8. NFS Messages 139

NFS MessagesDTCNFS1493ECannot open output file fileidExplanation: 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.Source File:Procedure Name:PRINTLOG CmainDTCNFS1495E Error code Error_code from creadbin atrecord number nnnnnExplanation: In processing the trace log file, thePRINTLOG encountered an error. The listed error codeshould help in problem determination.System Action:PRINTLOG processing terminates.User or Operator Response: Try to determine theproblem and reissue the PRINTLOG command.Source File:Procedure Name:PRINTLOG CmainDTCNFS1500I Task block address is zero: there is nocurrent operation.Explanation: The VMNFS server is stopped by a #CPEXT command entered from its console.System Action:None.User or Operator Response:Source File:Procedure Name:DTCNFS1501ISUM_OP Csum_opNone.Task block address: TaskBlockAddressExplanation: This message lists the task block addressfor the current operational summary report.System Action:None.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:Procedure Name:SUM_OP Csum_opDTCNFS1497EIncorrect argument.Explanation: A problem was found while formattingthe VMNFS trace file.System Action:PRINTLOG processing terminates.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.Source File:Procedure Name:DTCNFS1499IPRINTLOG CmainCurrent operation summary at timeExplanation: 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:Procedure Name:SUM_OP Csum_opDTCNFS1502I 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.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:Procedure Name:SUM_OP Csum_opDTCNFS1503I Queued write request at offset xoffset,length xlengthExplanation: This message lists the queued writerequest data for the current task in an operationalsummary report.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 error140 z/VM: TCP/IP Messages and Codes

NFS Messagescondition in NFS. Use the report to help with problemresolution where possible.Source File:Procedure Name:SUM_OP Csum_opDTCNFS1504I RPC program program version versionprocedure procedureExplanation: This informational message lists RPCprogram data for the current operational summaryreport.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:Procedure Name:SUM_OP Csum_opDTCNFS1505I 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.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:Procedure Name:SUM_OP Csum_opDTCNFS1508I 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.dddExplanation: 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.User or Operator Response:Source File:Procedure Name:NFSBADPW CnfsbadpwNone.DTCNFS1511E module name: socket function() call online line number failed, reason is: reasonExplanation: Acalltomodule name: socket function hasfailed. The reason for the failure will be included in themessage.System Action:None.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:Procedure Name:NFSMAINC C, NFSUTIL C, SIGERROR CmainDTCNFS1512W 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:requests only.Processing continues for minidiskUser or Operator Response: Determine why theTCPCSLIB CSLLIB could not be found.Source File:Procedure Name:NFSMAINC CmainChapter 8. NFS Messages 141

NFS MessagesDTCNFS1513I time NFSPROC_NULL call receivedfrom address, XID0xIDExplanation: An NFSPROC_NULL request wasreceived by the VMNFS server.System Action:User or Operator Response:Source File:Procedure Name:A null reply is sent to the NFS client.REQSTART CreqnfsNone.DTCNFS1514E Format is: replytag verb ...Explanation: An SMSG request with an invalid syntaxwas received by the VMNFS server.System Action:User or Operator Response:and reissue.Source File:Procedure Name:DTCNFS1515IVMNFS processing continues.REQSMSG CreqsmsgCorrect the SMSG requestTRACENUL flag is now trace_valueExplanation: An SMSG request to set the TRACENULflag was processed.System Action:User or Operator Response:Source File:Procedure Name:VMNFS processing continues.REQSMSG CreqsmsgNone.DTCNFS1516I time Syntax error in Refresh commandfrom origin: SMSG stringExplanation: VMNFS received an SMSG Refreshcommand with invalid syntax.System Action:User or Operator Response:reissue the command.Source File:Procedure Name:VMNFS processing continues.REQSMSG CsmrefreshCorrect the syntax andDTCNFS1519W File filename not found; initializationcontinuingExplanation: 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,vall file names will default to lines=CMS andtrans=no, which is equivalent to the record=binarydefault.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.User or Operator Response:Source File:INIT CProcedure Name:init_configNone.DTCNFS1520E The file pool server is not at theproper release levelExplanation: 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:NFS client.Error status NFSERR_IO is sent to theUser or Operator Response: Contact system supportto upgrade the file pool server to at least VM/ESAVersion 2 Release 3.0.Source File:Procedure Name:BFSPROCS CMount_BFSDTCNFS1521I item on line lineno of file VMNFSCONFIG is errorExplanation: 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 CProcedure Name:init_configDTCNFS1523I File filename TCPXLBIN used fordefault translation tableExplanation: The translation table in the identified filewill be used for ASCII/EBCDIC translation when noXLATE value is specified on client mount requests.System Action:User or Operator Response:Source File:VMNFS server initialization continues.NFSXLAT CNone.142 z/VM: TCP/IP Messages and Codes

NFS MessagesProcedure Name:init_xlatProcedure Name:init_xlatDTCNFS1524W Error reading file filename filetype fm;initialization continuesExplanation: 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.User or Operator Response:Source File:Procedure Name:NFSXLAT Cinit_xlatNone.DTCNFS1525E No space remaining in VMNFSTRANSLAT file. Unable to addtablenameExplanation: 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:NFS client.Error status NFSERR_IO is sent to theUser 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.Source File:Procedure Name:NFSXLAT Cname_xlat_locateDTCNFS1526W VMNFS HISTORY and VMNFSTRANSLAT do not matchExplanation: 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.User or Operator Response:Source File:INIT CNone.DTCNFS1527E Error reading file filename, serverterminated.Explanation: The VM NFS server requires file filenamefor its operation. An attempt to read this file failedSystem Action:User or Operator Response:named file cannot be read.Source File:VMNFS Server processing terminates.INIT CProcedure Name:init_configDetermine why theDTCNFS1528I Accept of socket m greater thanFD_SETSIZE nExplanation: 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.User or Operator Response:Source File:Procedure Name:NFSUTIL CNone.Handle_New_TCP_ClientDTCNFS1536W Error calling set groups function.BPX1VM5 return code rc and reasoncode rsExplanation: 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 CProcedure Name:DTCNFS1543EinitCannot allocate virtual storageExplanation: The VMNFS server was not able toprocess a request, because an error was returned on anattempt to allocate virtual storage.System Action:VMNFS server processing continues.Chapter 8. NFS Messages 143

NFS MessagesUser or Operator Response:Source File:Procedure Name:REQSMSG Cadd_cmiNone.DTCNFS1544E Authorization denied byVMNFSSMG.EXECExplanation: The system administrator activated anexit for the VMNFS server, called VMNFSSMG EXEC,which denied your SMSG request.System Action:The program returns to the caller.User or Operator Response: Contact your systemadministrator to see why the request was denied.Source File:Procedure Name:NFSSMSG CSMAUTHDTCNFS1546E Unable to accept new TCPconnections from NFS clientsExplanation: 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.Source File:Procedure Name:NFSUTIL CHandle_New_TCP_ClientDTCNFS1547E Size of buffer defined for UDP is toosmallExplanation: 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.System Action:User or Operator Response:VMNFS server processing terminates.The VM NFSadministrator must change the lrg_env_size parameterto have a value of 8192 or larger.Source File:Procedure Name:NFSMAIN CmainDTCNFS1553I MAXTCPUSERS value adjusted fromn1 to n2Explanation: 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.Source File:Procedure Name:NFSUTIL CInit_SocketDTCNFS1554E Unable to allocate storage for fd setExplanation: Initialization of the VM NFS server wasunable to obtain storage for the specified read or writefd set.System Action:VM NFS server processing terminatesUser 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.Source File:Procedure Name:NFSMAINC CmainDTCNFS1555E 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.144 z/VM: TCP/IP Messages and Codes

NFS MessagesSource File:Procedure Name:DTCNFS1556ENFSMAINC CmainLog data: Log_dataExplanation: An earlier message indicated there was aproblem with a call to a CMS function, and that CMSfunction returned detailed log_data describing the error.System Action:None.User or Operator Response:Source File:Procedure Name:NFSLINK CcheckpwNone.DTCNFS1557E No EXPORT list defined whenEXPORTONLY YES was specifiedExplanation: 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 CProcedure Name:init_configDTCNFS1559E VM NFS server is missing class Bprivileges or diagnose 88 authorizationExplanation: 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 CProcedure Name:initDTCNFS1560E Incorrect level of CP; requiredfunction not availableExplanation: Diagnose 88 support is not available inthe level of CP that you are running.System Action:User or Operator Response:appropriate level of /vm;.Source File:The VM NFS server terminates.INIT CProcedure Name:initUpgrade to theDTCNFS1561E Unable to set desiredMAXTCPUSERS value.Explanation: An error occurred trying to set theMAXTCPUSERS value.System Action:VMNFS server processing terminates.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.Source File:Procedure Name:NFSUTIL CInit_SocketDTCNFS1562E Unrecoverable NFS Client error,reason code 0xnnnn parm 0xnnnnExplanation: 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:Procedure Name:DTCCAVM.ASSEMBLEVMABENDSIGERROR 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.Chapter 8. NFS Messages 145

NFS MessagesSome 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 PORTMAPPERSeverity:Error.Explanation: Failed to register NFS and MOUNTprograms with port mapper. The only common reasonfor this is that the PORTMAP virtual machine is notrunning.System Action:None.User or Operator Response: Evaluate possible reasonsfor this failure. Use the RPCINFO command to test forcomplete failure of PORTMAP.Source File:Procedure Name:NFSMAIN CmainCan’t open debug fileSeverity:Error.Explanation: The DEBUG, and/or the GENLOGruntime options are selected. The VMNFS LOG fileopen failed.System Action:None.User or Operator Response: Correct any minidiskaccess problems (for example, read-only disk) beforecontinuing.Source File:Procedure Name:NFSMAIN Cmainclcvm.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.System Action:None.User or Operator Response: Examine the header inquestion, determine a reason for the failure, and correctthe problem before continuing.Source File:Procedure Name:NFSCVM Cclcvm_createdelbb_r: buffer not in use by current task.Severity:Explanation:Error.This message is issued by proceduredelbb_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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:GETBB Cdelbb_rDELFB: 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.System Action:None.User or Operator Response: Suspect system problems.Try to determine the initial failing case, and report it tothe IBM Support Center.Source File:Procedure Name:RDLABEL CDELFBDELFB: File Block use count is positive, but no taskis using it.Severity:Explanation:Error.System Action:Internal error in the VMNFS program.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:RDLABEL CDELFBDELFB: use count negative.Severity:Error.Explanation: The expected File Block use count waszero and a negative value was found.146 z/VM: TCP/IP Messages and Codes

NFS MessagesSystem Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:RDLABEL CDELFBDirectory 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSCREAT Cunlock_directoryFatal 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.System Action:None.User or Operator Response: Try reformatting the CMSminidisk. If problems recur, contact the IBM SupportCenter.Source File:Procedure Name:FNTRANS Cmake_tfFatal 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.System Action:None.User or Operator Response: Try reformatting the CMSminidisk. If problems recur, contact the IBM SupportCenter.Source File:Procedure Name:NFSCREAT Ccreate_filefh_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.System Action:None.User or Operator Response:Source File:Procedure Name:FH@HIST Cfh_checkfh_check: IUCV sever failure.Severity:Error.None.Explanation: Unexpected return code; probable errorin VMNFS program logic.System Action:None.User or Operator Response:Source File:Procedure Name:FH@HIST Cfh_checkGETBB: no available blocksSeverity:Error.None.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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:GETBB CGETBBGETBLOCK: error from FINDBLOKSeverity:Error.Explanation: A disk block has been read, but the blockbuffer holding it cannot be located. Error in VMNFSprogram logic.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FINDBLOK CGETBLOCKChapter 8. NFS Messages 147

NFS MessagesGETBLOCK: error from RWBLOCKSSeverity: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.User or Operator Response:Source File:Procedure Name:FINDBLOK CGETBLOCKNone.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.System Action:None.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:Procedure Name:FINDFILE Cgetrem: invalid offsetSeverity:Explanation:Error.System Action:GETFBLOKVMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:GETREM CgetremHistory 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.System Action:None.User or Operator Response:used by VMNFS.Source File:Procedure Name:FHãHIST CfindfhrCheck for a full 191 diskinit: error making device block for history fileSeverity:Error.Explanation: The VMNFS server’s 191 device is not anormal CMS minidisk.System Action:None.User or Operator Response:Source File:INIT CProcedure Name:initinit: IDENTIFY errorSeverity:Error.None.Explanation: A CMS IDENTIFY command failed(nonzero return code).System Action:None.User or Operator Response:Source File:INIT CProcedure Name:initinit: IUCV initialization error.Severity:Error.None.Explanation: The procedure c_hiucv sends anincorrect return code, which indicates that IUCVinitialization failed.System Action:None.User or Operator Response:Source File:INIT CProcedure Name:initinit: translation table errorSeverity:Error.None.Explanation: An attempt to load the special translatetable file VMNFS TCPXLBIN, or the standard translatetable file STANDARD TCPXLBIN, found that the148 z/VM: TCP/IP Messages and Codes

NFS Messagessecond or third records in the file did not contain 256bytes.System Action:None.User or Operator Response:file before you try again.Source File:INIT CProcedure Name:initInvalid diskaddr arg to findfhr.Severity:Explanation:Error.System Action:Correct the translationVMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FHãHIST CfindfhrLINKDEV: failure in NFSTISETSeverity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:make_tf: lost fileSeverity:Error.LINKDEV CMAKE_DBExplanation: An error occurred while trying to createa Name Translation file on a minidisk. This is probablybecause of a VMNFS program logic error.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FNTRANS Cmake_tfmake_tf: translation file already existsSeverity:Explanation:Error.VMNFS program logic error.System Action: Try to determine the initial failingcase, and report it to the IBM Support Center.User or Operator Response:Source File:Procedure Name:FNTRANS Cmake_tfNone.nfscreate: just-created file cannot be foundSeverity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSCREAT Cmkdopresnfslink: detach command failedSeverity:Error.Explanation: A CP DETATCH command failed. Thefailing command and its return code is displayed justbefore this error signal.System Action:None.User or Operator Response:Source File:Procedure Name:NFSLINKnfslinknfsrename: missing FSTSeverity:Error.None.Explanation: Cannot locate the FST for a directory.VMNFS program logic error.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSRENAM CnfsrenameNo storage for TCP client list elementSeverity:ErrorExplanation: Error getting storage when acceptingnew TCP client connection.System Action: VMNFS is restarted automaticallywhich should clear the storage problem.User or Operator Response:Source File:Procedure Name:NFSUTIL CNone.Handle_New_TCP_ClientChapter 8. NFS Messages 149

NFS MessagesNo Task Block for TCP is availableNo Task Block for UDP is availableNo Task Block is availableSeverity:Error.Explanation: No task blocks are available. Anotherclient request was received when all tasks were busyprocessing previous requests. The number of tasks iscurrently 64.System Action:None.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.Source File:Procedure Name:NFSMAIN CmainQUEUEB: no Device Block.Severity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:GETBB CQUEUEBRDLABEL: 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.System Action:None.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.Source File:Procedure Name:RDLABEL CRDLABELrdlabel: IUCV sequence error.Severity:Error.Explanation: Unexpected status from an IUCVoperation to *BLOCKIO.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:RDLABEL Copen_pathrefresh: 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.System Action:None.User or Operator Response: If this condition recurs,try to determine the initial failing case, and report it tothe IBM Support Center.Source File:Procedure Name:REQSMSG CrefreshRELBBs: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:GETBBProcedure Name:RELBBsrename: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.150 z/VM: TCP/IP Messages and Codes

NFS MessagesSource File: NFSRENAM CProcedure Name: nfsrenameSource File: NFSXLAT CProcedure Name: name_xlat_locatereqmount: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:REQSTART Creply_procreqstart: 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.Source File:Procedure Name:REQSTART Creply_procrtnname: Error reading VMNFS TRANSLAT.Severity:Error.Explanation: The VMNFS server was unable to readthe VMNFS TRANSLAT file.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.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:terminated.VMNFS server initialization isUser 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.Source File:Procedure Name:NFSXLAT Cinit_xlatrtnname: VMNFS HISTORY/TRANSLAT file error.Severity:Error.Explanation: An attempt to verify and initialize theVMNFS HISTORY and VMNFS TRANSLAT file hasfailed.System Action:None.User or Operator Response: Examine the serverconsole for additional error messages.Source File:INIT CProcedure Name:RWBLOCKS: not read nor write.Severity:Explanation:Error.System Action:recreate_history_files, init_history.VMNFS program logic error.None.User or Operator Response:Try to determine theChapter 8. NFS Messages 151

NFS Messagesinitial failing case, and report it to the IBM SupportCenter.Source File:IO1 CProcedure Name:RWBLOCKSRWBLOCKS: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:IO1 CProcedure Name:Selectex failedSeverity:Error.RWBLOCKSExplanation: This msg follows msg DTCNFS1511E.See the information in that msg for the reason for thefailure.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSMAINC Cmainsmdetach: lost Device Block.Severity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:REQSMSG Csmdetachtaskend: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:TASKEND CTASKENDTASKEND: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:TASKEND CTASKENDtf_client: name too long.Severity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FNTRANS Ctr_clientThreadYield counter corrupted- {A | B}Severity:Error.Explanation: An internal error has occurred in the VMNFS program.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSMAINC.CMAINtr_add: name too long.Severity:Explanation:Error.System Action:VMNFS program logic error.None.152 z/VM: TCP/IP Messages and Codes

NFS MessagesUser or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FNTRANS Ctr_addtr_CMS: name too long.Severity:Explanation:Error.System Action:VMNFS program logic error.None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:FNTRANS Ctr_CMSwrite_V: offset computation yields invalid block.Severity:Error.Explanation: Either an error in VMNFS serverprogram logic, or a CMS minidisk file system can becorrupted.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:NFSWRIT1 Cwrite_Vtr_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.System Action:None.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.Source File:Procedure Name:FNTRANS Ctr_get_recordtracev: 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.System Action:None.User or Operator Response: Try to determine theinitial failing case, and report it to the IBM SupportCenter.Source File:Procedure Name:TRACEV CtracevChapter 8. NFS Messages 153

NFS Messages154 z/VM: TCP/IP Messages and Codes

Chapter 9. PING MessagesThis 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: ReturnCodeSeverity:Explanation:Warning.System Action:TCP/IP could not begin processing.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:Procedure Name:CMPING PASCALMainHandle failed: ReturnCodeSeverity:Explanation:Warning.System Action:TCP/IP cannot handle notes.The PING program halts and exits.User or Operator Response: Tell 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:Procedure Name:CMPING PASCALMainLength must be between 8 & 8500Severity:Explanation:specified.Warning.System Action:An invalid LENGTH parameter wasThe PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLineMissing number after COUNT optionSeverity:Warning.Explanation: You specified a COUNT parameterwithout a value.System Action:The PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLineHost name or address not found.Severity:Explanation:IP address.Warning.System Action:You specified an unknown host name orThe PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLineMissing number after LENGTH optionSeverity:Warning.Explanation: You specified a LENGTH parameterwithout a value.System Action:The PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLine© Copyright IBM Corp. 1987, 2002 155

PING MessagesMissing number after TIMEOUT optionSeverity:Warning.Explanation: You specified a TIMEOUT parameterwithout a value.System Action:The PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLineMonQuery buffer sizes failed: ReturnCodeSeverity:Error.Explanation: The size of the PING request was greaterthan the maximum size allowed by TCP/IP.System Action:The PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALMainMonQuery buffer sizes returns bad lengthMonQueryLenSeverity:Error.Explanation: The PING request was too large forTCP/IP to accept.System Action:User or Operator Response:The PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALMainNon-numerical argument BadArgumentSeverity:Warning.Explanation: You specified a non-numerical argumentwhen a numerical argument was expected.System Action:The PING program halts and exits.User or Operator Response: Correct the syntax of theinvalid parameter, and resubmit the PING command.For information about the syntax of the PINGcommand, see the TCP/IP User’s Guide.Source File:Procedure Name:CMPING PASCALSafeConvertPING: Extraneous parameter BadParameterSeverity:Explanation:Warning.System Action:You specified an extraneous parameter.The PING program halts and exits.User or Operator Response: Remove the extraneousparameter and resubmit the PING command.For information about the syntax of the PINGcommand, see the TCP/IP User’s Guide.Source File:Procedure Name:CMPING PASCALParseCommandLinePing request failed: ReturnCodeSeverity:Warning.Explanation: The PING request could not complete.The listed return code explains why the PING requestfailed. For example, the TIMEOUT parameter expired.156 z/VM: TCP/IP Messages and Codes

PING MessagesSystem Action:The PING program halts and exits.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.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:Procedure Name:CMPING PASCALMainPING: Unknown host HostNameSeverity:Warning.Explanation: The host name specified was not in thehost address cross-reference table.System Action:The PING program halts and exits.User or Operator Response:1. Correct the syntax of the host name and resubmitthe PING command.For information about the syntax of the PINGcommand, see the TCP/IP User’s Guide.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:address cross-reference table.Verify the hostFor information about the host address cross-referencetable in TCP/IP, see the TCP/IP Planning andCustomization.Source File:Procedure Name:CMPING PASCALMainTimeout must be between MINpingTIMEOUT &MAXpingTIMEOUTSeverity:Explanation:parameter.Warning.System Action:You specified an invalid TIMEOUTThe PING program halts and exits.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.Source File:Procedure Name:CMPING PASCALParseCommandLinePING: Unknown option BadOptionSeverity:Explanation:Warning.System Action:You specified an unknown option.The PING program halts and exits.User or Operator Response: Remove the unknownoption, and resubmit the PING command.For information about the syntax of the PINGcommand, see the TCP/IP User’s Guide.Source File:Procedure Name:CMPING PASCALParseCommandLineChapter 9. PING Messages 157

PING Messages158 z/VM: TCP/IP Messages and Codes

Chapter 10. PORTMAP MessagesThis 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_createSeverity: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:Procedure Name:portmap cmain() svctcp_create()couldn’t do udp_create ReturnCodeSeverity:Fatal.Explanation: Portmap encountered an errorestablishing a UDP 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:Procedure Name:portmap cmain() svcudp_create()portmap cannot bind ReturnCodeSeverity:Fatal.Explanation: Portmap encountered an error binding aname to a socket. The program exits.System Action: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.Source File:Procedure Name:portmap cmain() bind()portmap cannot bind ReturnCodeSeverity:Fatal.Explanation: Portmap encountered an error binding asocket to a name. The program exits.System Action: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.Source File:Procedure Name:portmap cmain() bind()portmap cannot create socket ReturnCodeSeverity:Fatal.Explanation: Portmap encountered an error creating asocket. The program exits.System Action:The program exits.User or Operator Response: Check memoryavailability. Check that tcpip is running.Source File:Procedure Name:portmap: startedSeverity:Explanation:System Action:portmap cInformational.main() socket()User or Operator Response:Portmap execution has begun.The program continues.None.© Copyright IBM Corp. 1987, 2002 159

PORTMAP MessagesSource File: portmap cProcedure Name: main() reg_portmapper()run_svc returned unexpectedlySeverity: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.Source File:Procedure Name:portmap cmain() svc_run()stderr, svc_sendreplySeverity:Fatal.Explanation: An error occurred while sending thereply back to the client. Portmap aborts. The messageprints out only during debugging (-d/-D optionparameter).System Action:None.User or Operator Response:Source File:Procedure Name:portmap cNone.reg_srv() svc_sendreply()160 z/VM: TCP/IP Messages and Codes

Chapter 11. Remote Printing MessagesLPD MessagesThis chapter contains remote printing messages.This 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.System Action: None.Source File: LPD PASCALProcedure Name: DoNewConnStateAttempted SMSG from userid ignored.Severity: Warning.Explanation: You are not authorized to send amessage to LPD. The command you sent is ignored.System Action: None.User or Operator Response: Request authorizationfrom the system programmer.Source File: LPD PASCALProcedure Name: ProcessSMSGBeginTcpip: ReturnCodeSeverity: Error.Explanation: An error occurred connecting to TCP/IPservices.System Action: None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Check to see thatTCPIP services are running.Source File: LPD PASCALProcedure Name: PrepareTCPCall to DTCXLATE failed with reason code: reasoncodeSeverity: 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.System Action:LPD server processing terminates.User or Operator Response: Inform the systemadministrator of this problem.System Programmer Response:support center of this problem.Source File:Procedure Name:LPD PASCALInform the IBMProcessOptions, PreparePrintersCallable 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.System Action:User or Operator Response:appropriate level of CMS.Source File:Procedure Name:LPD server processing terminates.LPD PASCALRe-IPL with theProcessOptions, DoXlateTableCannot find the file filename filetype filemode.Severity:Warning.Explanation: You specified a file that does not exist onthe disks to which you have access.System Action:None.User or Operator Response: Reissue the commandwith the correct file specification.Source File:Procedure Name:LPD PASCALProcessOperandsCannot open filename filetype.Severity:Error.Explanation: The indicated configuration file couldnot be opened.© Copyright IBM Corp. 1987, 2002 161

LPD MessagesSystem Action:The program halts.User or Operator Response: Check the accessrestrictions on the specified file.Source File:Procedure Name:Cannot reach hostSeverity:LPD PASCALWarning.PreparePrintersExplanation: The host you specified could not bereached. This host is specified as the remote host on theREMOTE statement in the configuration file.System Action:None.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.Source File:Procedure Name:LPD PASCALGetHostResolCannot use mode mode as spool for printerSeverity:Warning.Explanation: The indicated disk mode could not beused as a spool disk for the specified printer.System Action:None.User or Operator Response:Use the default disk.System Programmer Response: Check to see thatLPSERVE is accessing its A disk in read-write mode.Source File:Procedure Name:LPD PASCALCompletePrintersCMSPPRT: DoSioWat failed. CSW = Keys CCWAdrUnitStat ChanStat BytesSeverity:Explanation:Error.System Action:A DoSioWat call failed in CMSPPRT.None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:machine.Source File:Procedure Name:CMSPPRT PASCALPrintLRestart the LPSERVECommand not understood.Severity:Error.Explanation: An invalid command was received bymeans of SMSG.System Action:None.User or Operator Response:try again.Source File:Procedure Name:LPD PASCALProcessSMSGCheck the command andConnection connection terminated because ReturnCodeSeverity:Error.Explanation: LPD terminated this connection for theindicated reason.System Action:None.User or Operator Response: Check the indicatedreason and take the appropriate action.Source File:Procedure Name:LPD PASCALDoEndConnectionContent of file tablename TCPXLBIN {specified forservice servicename} is not validSeverity: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.System Action:LPD server processing terminates.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.Source File:Procedure Name:LPD PASCALProcessOptions, PreparePrintersCould not define address as a punchSeverity:Error.Explanation: A CP DEFINE command failed for theindicated device.System Action:None.162 z/VM: TCP/IP Messages and Codes

LPD MessagesUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address.Source File:Procedure Name:LPD PASCALDefineCPDeviceVerify the punchCould 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 Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Verify the SERVICESstatement in LPD CONFIG file on the LPSERVE’s Adisk.Source File:Procedure Name:LPD PASCALGetJobDeviceCould not define printer at vaddr. Return code wasReturnCodeSeverity:Error.Explanation: A CP DEFINE failed for the indicatedprinter address.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address.Source File:Procedure Name:LPD PASCALDefineCPDeviceVerify the printerCould not DETACH PUNCH address. Return code wasReturnCodeSeverity:Error.Explanation: A CP DETACH command failed for theindicated punch device.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:status.Source File:LPD PASCALCheck the punchProcedure Name:SendFailingMailCould not do IDENTIFY. RC = ReturnCodeSeverity:Error.Explanation: An attempt to determine the local node’sname failed. This is a necessary step to prepare theprinters.System Action:The program exits.User or Operator Response:Source File:Procedure Name:LPD PASCALPreparePrintersVerify the printer name.Could not erase name type mode. RC=ReturnCodeSeverity:Warning.Explanation: The program could not erase theindicated file.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Check the accessinformation of LPSERVE’s A disk.Source File:Procedure Name:LPD PASCALEraseFileCould not open control file site CFjob printer. Jobabandoned.Severity:Explanation:opened.Error.System Action:The indicated control file could not beThe job aborts.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Check to see if theLPR client is sending a corrupted control file to theserver.Source File:Procedure Name:LPD PASCALProcessControlFileCould not open data file site ftype. Job abandoned.Severity:Explanation:Error.System Action:The indicated file could not be opened.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 conditionChapter 11. Remote Printing Messages 163

LPD Messagescontinues, tell the system programmer about theproblem.Source File:Procedure Name:LPD PASCALDoSendStepCould not open "name QUEUE"Severity:Error.Explanation: The indicated printer queue file couldnot be opened.System Action:None.User or Operator Response:printed.Source File:Procedure Name:LPD PASCALSavePrinterQueueCould not open "name SITE"Severity:Explanation:opened.Warning.System Action:Wait until the file isThe indicated SITE file could not beNone.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that the IPaddress is in the indicated file so that LPD can openthe file.Source File:Procedure Name:LPD PASCALLoadSiteCould not open site JFJob.Severity:Error.Explanation: The program could not open theindicated file.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that the IPaddress is in the indicated file so that LPD can openthe file.Source File:Procedure Name:LPD PASCALLoadSiteCould not retrieve SMSGSeverity:Warning.Explanation: An attempt to read the next SMSGfailed. The queue may be empty.System Action:None.User or Operator Response:Source File:Procedure Name:LPD PASCALProcessSMSGNone.Could not spool device address. Return code wasReturnCodeSeverity:Error.Explanation: A CP spool command failed with theindicated return code.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address for the local pointer.Source File:Procedure Name:LPD PASCALGetJobDeviceCheck the deviceCould not spool PUNCH address to smtp. Return codewas ReturnCodeSeverity:Error.Explanation: This message is sent to you throughSMTP mail if you specified mail as a FAILEDJOBparameter in the LPD CONFIG file.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address.Source File:Procedure Name:LPD PASCALSendFailingMailCheck the punchCould not TAG device address string. Return code wasReturnCode. Response was ResponseString.Severity:Explanation:Error.System Action:A CP TAG command failed.None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:tag value is correct.Source File:Procedure Name:LPD PASCALGetJobDeviceCheck to see that the164 z/VM: TCP/IP Messages and Codes

LPD MessagesCP command failed. RC = ReturnCode ResponseresponseSeverity:Error.Explanation: A CP command, issued as a result of acommand received by way of an SMSG, failed.System Action:None.User or Operator Response:command sent to LPSERVE.Source File:Procedure Name:LPD PASCALProcessSMSGCheck the SMSGDisk 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 Action:The program halts.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Check to ensure thatLPD has write access to its A disk.Source File:Procedure Name:LPD PASCALPreparePrintersError 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.System Action:LPD server processing terminates.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.Source File:Procedure Name:LPD PASCALProcessOptions, PreparePrintersFailed to allocate block for jobnumber from siteSeverity:Error.Explanation: A step block, required for remoteprinting, could not be allocated for this job because ofinsufficient memory.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Re-IPL the LPSERVEvirtual machine. Increase virtual memory for LPSERVE,if necessary.Source File:Procedure Name:LPD PASCALFailed to open site filetype.Severity:Explanation:Error.System Action:DoNewSubcommandThe indicated file could not be opened.None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:clear the last error.Source File:Procedure Name:LPD PASCALDoNewSubcommandRe-IPL LPSERVE toFailed to write to printer address. RC=ReturnCodeSeverity:Explanation:Error.System Action:An error occurred writing to this printer.None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address and status.Source File:Procedure Name:LPDFLPF PASCALWritePrinterCheck the printerFailed to write to punch address. RC=ReturnCodeSeverity:Error.Explanation: An error occurred writing to theindicated punch.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:punch service.Source File:Procedure Name:LPD PASCALPunchLineCheck the status ofChapter 11. Remote Printing Messages 165

LPD MessagesIDENTIFY output format different than expectedSeverity:Warning.Explanation: The output of a CMS IDENTIFYcommand was in an unexpected format.System Action:The program halts.User or Operator Response: From the CMS commandline, type "ID" to obtain sample output. Have thisinformation available when contacting the IBM SupportCenter.Source File:Procedure Name:LPD PASCALPreparePrintersIgnoring 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:try again.Source File:Procedure Name:LPD PASCALLoadPrinterQueueCheck the LPR client andIgnoring TCP/IP notice tag on connection connectionSeverity:Warning.Explanation: The indicated notification is ignoredbecause of a probable error in the connection.System Action:None.User or Operator Response:information and try again.Source File:Procedure Name:LPD PASCALInitEmulation failedSeverity:Error.ProcessTCPCheck the tagExplanation: An error occurred initializing EC modeemulation, which is necessary to run TCP/IP in avirtual machine with ECMODE OFF.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:of EC mode emulation.Source File:Procedure Name:LPD PASCALPrepareTCPInvestigate the statusJob is in unrecognized state (state).Severity:Explanation:Warning.System Action:A job is in an unrecognized state.None.User or Operator Response: Check the network statusand tell the system programmer about the problem.System Programmer Response:machine.Source File:Procedure Name:LPD PASCALProcessWorkJob job abandoned. Job file too short.Severity:Error.Re-IPL the LPSERVEExplanation: The indicated job was abandonedbecause the job file did not contain enoughinformation. The printer name, site name, or lengthfields could not be read.System Action:None.User or Operator Response:and try again.Source File:Procedure Name:LPD PASCALLoadJobJob job abandoned. Not enough storage.Severity:Error.Check the network statusExplanation: The program could not allocate storageto process another job.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: If the file is large andif the LPSERVE is used as a spool, increase the diskcapacity for LPSERVE.Source File:Procedure Name:LPD PASCALLoadJobOut of storage for connectionsSeverity:Error.Explanation: A connection record could not be builtbecause sufficient memory was not available.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:If this condition166 z/VM: TCP/IP Messages and Codes

LPD Messagesfrequently occurs, allocate more virtual memory for thisvirtual machine.Source File:Procedure Name:LPD PASCALAllocConnectionProgram error: Invalid option (option)Severity:Explanation:Error.System Action:You specified an invalid option.None.User or Operator Response:with the correct option.Source File:Procedure Name:LPD PASCALReissue the commandPreparePrinters, ProcessOptionsSite file "name SITE" record 1 unreadable.Severity:Warning.Explanation: The first record in the indicated SITE fileis unreadableSystem Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address is in the indicated file.Source File:Procedure Name:LPD PASCALLoadSiteEnsure that the IPSite file "SName SITE" record 2 unreadable.Severity:Warning.Explanation: The second record in the indicated SITEfile is unreadable.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that the IPaddress is in the indicated file. None.Source File:Procedure Name:LPD PASCALLoadSitespooltype kind is unknown (type).Severity:Error.Explanation: A printer specification contained anunknown spool type. RSCS did not recognize theprinter.System Action:None.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Source File:Procedure Name:LPD PASCALGetJobDeviceCheck the printer ID.The keyword word is ambiguous. Use a longerabbreviation.Severity:Warning.Explanation: The indicated configuration file keywordabbreviation is ambiguous.System Action:None.User or Operator Response: Replace thisconfiguration file entry with a longer abbreviation andreissue the command.Source File:Procedure Name:LPD PASCALProcessOptionsThe keyword word is not a keyword.Severity:Explanation:is not valid.Warning.System Action:The indicated configuration file keywordNone.User or Operator Response: Correct the configurationfile and reissue the command.Source File:Procedure Name:LPD PASCALConfigServiceThe keyword word is too short. Use a longerabbreviation.Severity:Warning.Explanation: The indicated configuration file keywordabbreviation is ambiguous.System Action:None.User or Operator Response: Replace the indicatedconfiguration file keyword with a longer abbreviationof the keyword and reissue the command.Source File:Procedure Name:LPD PASCALConfigServiceThe keyword word was not recognized.Severity:Explanation:is not valid.Error.System Action:The indicated configuration file keywordNone.User or Operator Response: Correct the configurationfile entry and reissue the command.Chapter 11. Remote Printing Messages 167

LPD MessagesSource File:Procedure Name:LPD PASCALConfigServiceThe option option is ambiguous. Use a longerabbreviation.Severity:Warning.Explanation: The abbreviation specified for thiscommand-line option is ambiguous.System Action:None.User or Operator Response: Reissue the commandwith a longer abbreviation for the intended option.Source File:Procedure Name:LPD PASCALConfigServiceThe 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.System Action:None.User or Operator Response: Reissue the commandwith valid option specifications.Source File:Procedure Name:LPD PASCALProcessOptionsThe 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.System Action:None.User or Operator Response: Remove the duplicatestatement and any associated statements, such asLOCAL, RSCS, or REMOTE, and reissue the command.Source File:Procedure Name:LPD PASCALPreparePrintersTranslation file tablename TCPXLBIN {for serviceservicename} not foundSeverity: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.System Action:LPD server processing terminates.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.Source File:Procedure Name:LPD PASCALUse a class of A to Z, 0 to 9.Severity:Explanation:Error.System Action:ProcessOptions, PreparePrintersThe class was not valid.The program halts.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.System Action: None.User or Operator Response: Check the host name andprinter name before you reissue the command.Source File: LPQ PASCALProcedure Name: ProcessOptionsCannot get a printer name.Severity:Error.Explanation: The program could not find the printername on the command line or in the GLOBALV file.System Action:None.User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer name.Source File:Procedure Name:LPQ PASCALProcessOptions168 z/VM: TCP/IP Messages and Codes

LPQ MessagesCannot get the printer host.Severity:Error.Explanation: The default host name could not be readfrom the GLOBALV file.System Action:None.User or Operator Response: Specify the host name onthe command line, or use LPRSET to set up the defaulthost name.Source File:Procedure Name:LPQ PASCALProcessOptionsThe printer name is not known.Severity:Error.Explanation: The program could not determine theprinter name.System Action:None.User or Operator Response: Check the printer nameat the server machine and reissue the command with avalid printer name.Source File:Procedure Name:LPQ PASCALProcessOptionsProgram error: Invalid option (option)Severity: Error.Explanation: You specified an invalid option on thecommand line.System Action: None.User or Operator Response: Reissue the commandwith valid options.Source File: LPQ PASCALProcedure Name: ProcessOptionsThe host name is not known.Severity:Explanation:host name.Error.System Action:The program could not determine theNone.User or Operator Response: Use the valid host namewith the command. A valid host name is one that canbe resolved by the program.Source File:Procedure Name:LPQ PASCALProcessOptionsThe 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.System Action:None.User or Operator Response:with valid options.Source File:Procedure Name:LPQ PASCALProcessOptionsReissue the commandChapter 11. Remote Printing Messages 169

LPR and LPRSET MessagesLPR and LPRSET MessagesThis section contains messages issued by LPR and LPRSET.0000 TCP/IP installation error: DTCUMETEXT not foundSeverity:ErrorExplanation: 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.System Action:Command execution stops.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 EXEC2001 File mode 'fm' is not valid; acceptedvalues are: A-Z. The default file mode(fm-default) will be usedSeverity: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.User or Operator Response:Source File:LPR EXECNone.2002 File mode number 'nn' is not valid;accepted values are: 0-6. The default filemode (fm-default) will be usedSeverity: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.User or Operator Response:Source File:LPR EXECNone.2003 Ignoring additional file identifierinformation: aaaaaaaaSeverity: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.System Action:User or Operator Response:Source File:Command execution continues.LPR EXECNone.2004 File 'fn ft fm' was not foundSeverity:Error.Explanation: The listed file was not found at theindicated file mode.System Action:Command execution stops.User or Operator Response: Verify all file identifierinformation has been correctly specified. Also, ensurethe disk or directory on which the file resides isaccessed.Source File:LPR EXEC2005 No file has been identified for printingSeverity:Error.Explanation: The LPR command was invoked withprint-specific options, but information that identifies afile to be printed has been omitted.System Action:Command execution stops.User or Operator Response: Provide the file name, filetype and (optionally) the file mode of the file to beprinted when this command is issued.Source File:LPR EXEC2006 A file type must be provided for file:filenameSeverity:Error.Explanation: The LPR command was invoked withoutsufficient information to identify the file to be printed;only the indicated file name was provided.System Action:Command execution stops.User or Operator Response: Provide the file name, filetype and (optionally) the file mode of the file to beprinted when this command is issued.Source File:LPR EXEC170 z/VM: TCP/IP Messages and Codes

LPR and LPRSET Messages2007 File identifier 'fileid' is not validSeverity:Error.Explanation: The provided file information does notcomprise a valid CMS file identifier.System Action:Command execution stops.User or Operator Response: Verify all file identifierinformation has been correctly specified.Source File:LPR EXEC2008 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.System Action:User or Operator Response:Source File:Command execution stops.LPR EXECNone.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.System Action:Command execution stops.User or Operator Response: Review the descriptionsof both options (option1 and option2) identified by thismessage, then retry the command with the correctoption combination.Source File:LPR, LPRSET EXEC2010 The option option value (value) isnot{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.System Action:Command execution stops.User or Operator Response: Review the description ofthe listed option to determine why the current valuewas not accepted, then retry the command with anappropriate value specified.Source File:LPR, LPRSET EXEC2011 The option1 and option2 options aremutually exclusive.Severity:Error.Explanation: The two options listed (option1 andoption2) cannot be used together.System Action:Command execution stops.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.Source File:LPR, LPRSET EXEC2012 Option option is not recognized or is notvalid.Severity:Error.Explanation: The option listed is not supported bythis command.System Action:Command execution stops.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.Source File:LPR, LPRSET EXEC2013 An RSCS link or node parameter hasbeen incorrectly specified. Specify linkand node parameters using one of thefollowing formats: linkid,nodeidlinkid@nodeid linkid AT nodeidSeverity:Error.Explanation: The link and node values supplied withthe RSCS option are not valid, or have not beencorrectly specified.System Action:Command execution stops.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.Source File:LPR, LPRSET EXEC2014 Error reading file: file Return code: rcSeverity:Error.Explanation: An error occurred while attempting toread the specified file.Chapter 11. Remote Printing Messages 171

LPR and LPRSET MessagesSystem Action:Command execution stops.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 '

LPR and LPRSET Messagesbut 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.System Action:Source File:Command execution stops.LPR, LPRSET EXEC2022 No printer has been identified toprocess file: fileSeverity:Error.Explanation: The listed file cannot be processedbecause a printer has not been specified on which thefile is to be printed.System Action:Command execution stops.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.Source File:LPR, LPRSET EXEC2023 No host has been identified to processfile: fileSeverity:Error.Explanation: The listed file cannot be processedbecause a printer host has not been specified to whichthe file should be directed.System Action:Command execution stops.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.Source File:LPR, LPRSET EXEC2024 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.System Action:Command execution stops.User or Operator Response: Specify an appropriatevalue in addition to this option when the command isissued.Source File:LPR, LPRSET EXEC2025 Nickname name in file file does notdefine usable dataSeverity: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.System Action:Command execution stops.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.Source File:LPR EXEC2026 Tag tagname for nickname name in filefile defines a value that is not validSeverity: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 wholenumber.System Action:Command execution stops.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.Source File:LPR EXEC2027 Tag tagname for nickname name in filefile does not define any dataSeverity:Error.Explanation: An attempt was made to retrieveinformation defined by the listed nickname from theindicated file. However, only the tag itself is present.System Action:Command execution stops.User or Operator Response: Verify the correctnickname/tag was specified, or define an appropriatevalue using this tag, then retry the command.Source File:LPR EXECChapter 11. Remote Printing Messages 173

LPR and LPRSET Messages2028 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.System Action:Command execution stops.User or Operator Response: Verify the correctnickname/tag was specified, or define an appropriatevalue using this tag, then retry the command.Source File:LPR EXEC2029 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.System Action:Command execution stops.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.Source File:LPR EXEC2031 command Level level, Internal version IDversionSeverity:Informational.Explanation: The indicated information is providedwhen the QUERY option has been processed.System Action:User or Operator Response:Source File:Command execution continues.None.LPR, LPRSET EXEC2038 The following command failed: commandReturn code: rcSeverity:Error.Explanation: The indicated CP or CMS commandfailed with the listed return code.System Action:User or Operator Response:Command execution stops.Review the appropriateCP or CMS documentation to determine why thiscommand failed, and correct any problems.Source File:LPR, LPRSET EXEC2039 Internal error in routine: routinenameError information: errortextSeverity:Error.Explanation: A logic error was detected duringcommand processing.System Action:Command execution stops.User or Operator Response: Inform the systemadministrator of this problem.System Programmer Response:support center of this problem.Source File:LPR, LPRSET EXECInform the IBM2040 Use this form: command printer hostSeverity: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.System Action:Command execution stops.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 EXEC2041 Parameters cannot be specified with theoption optionSeverity:Error.Explanation: When the indicated option is used,printer and host values cannot be specified.System Action:Command execution stops.User or Operator Response: Do not include printerand host information when the listed option is used.Source File:LPRSET EXEC2042 Supported options are: optionlistSeverity:Informational.Explanation: The LPRSET command was invokedwith a question mark (?) insead of conventional printerand host information. In response, minimal usage174 z/VM: TCP/IP Messages and Codes

LPR and LPRSET Messagesinformation is displayed that includes the options listedby this message.System Action:User or Operator Response:Source File:Command execution stops.LPRSET EXECNone.2043 Suitable arguments or options were notspecified with the option optionSeverity:Error.Explanation: The indicated option has been specified,but no options or values were provided upon whichthis option will have an effect.System Action:Command execution stops.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.Source File:LPRSET EXEC2044 Only the following options can bespecified with the option option:optionlistSeverity: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.System Action:Command execution stops.User or Operator Response: If necessary, review theoption descriptions for this command to determine anappropriate combination of options.Source File:LPRSET EXEC2045 Ignoring additional destinationinformation: aaaaaaaaSeverity: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.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2050 Printer and host values have not beendefinedSeverity:Informational.Explanation: At present, no printer or host defaultsare being maintained using CMS global variables.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2051 Your LPR printer is currently set to:printer at: hostSeverity:Informational.Explanation: The indicated printer and host values arethose being maintained using CMS global variables; thecurrent values are listed.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2052 Server is defined as: serverid {(Default)}Severity:Informational.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.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2053 Printer is connected on link: linkid{(Default)}Severity:Informational.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.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2054 Printer is connected on node: nodeid{(Default)}Severity:Informational.Explanation: The indicated RSCS node will be used toprocess asynchronous print requests. If a user-specificvalue has not been established through use of a priorChapter 11. Remote Printing Messages 175

LPR and LPRSET MessagesLPRSET command, the system default is indicated.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2055 LPR mode: {ASYNCHRONOUS |SYNCHRONOUS} {(Default)}Severity:Informational.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.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXEC2056 Nickname: nameSeverity:Informational.None.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.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.Source File:LPRSET EXECBoth the printer and the host name are not known.Severity:Error.Explanation: The program could determine neither theprinter name nor the host name.System Action:None.User or Operator Response: Check the host name andthe printer name and reissue the command.Source File:Procedure Name:LPRP PASCALProcessOptionsCall to DTCXLATE failed with reason code: reasoncodeSeverity: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.System Action:Command execution stops.User or Operator Response: Inform the systemadministrator of this problem.System Programmer Response:support center of this problem.Source File:Procedure Name:LPRP PASCALGetTranslateTablesInform the IBM2057 Nickname Tag: tagnameSeverity:Informational.Explanation: The indicated nickname tag will be usedto obtain printer and host addressing information froma CMS NAMES file when print requests are processed.System Action:User or Operator Response:Source File:Command execution continues.LPRSET EXECNone.2058 The provided {printer | host} name isnot validSeverity:Error.Explanation: The printer or host name you providedis not valid. The value may be too long or too short, ormay contain inappropriate characters.System Action:Command execution stops.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.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.System Action:User or Operator Response:appropriate level of CMS.Source File:Procedure Name:Command execution stops.LPRP PASCALGetTranslateTablesRe-IPL with theCannot find the file filename filetype filemode.Severity:Warning.Explanation: The file specified on the command linedoes not exist.System Action:None.User or Operator Response:name with the command.Source File:LPRP PASCALSpecify the correct file176 z/VM: TCP/IP Messages and Codes

LPR and LPRSET MessagesProcedure Name:ProcessOptionsCannot get a printer name.Severity:Error.Explanation: The program could not find the printername in the GLOBALV file.System Action:None.User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer.Source File:Procedure Name:LPRP PASCALProcessOptionsCannot get the printer host.Severity:Error.Explanation: The host name could not be read fromthe GLOBALV file.System Action:None.User or Operator Response: Specify the host name onthe command line, or use LPRSET to set up the defaulthost name.Source File:Procedure Name:LPRP PASCALProcessOptionsContent of file tablename TCPXLBIN is not validSeverity: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.System Action:Command execution stops.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.Source File:Procedure Name:LPRP PASCALGetTranslateTablesError 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.System Action:Command execution stops.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.Source File:Procedure Name:LPRP PASCALGetTranslateTablesHost host did not accept printer name printer.Severity:Warning.Explanation: The indicated host did not recognize theindicated printer.System Action:None.User or Operator Response: Check for the correctprinter name at the foreign host and specify it with thecommand.Source File:Procedure Name:LPRP PASCALMainTranslation file tablename TCPXLBIN not foundSeverity:Error.Explanation: The named translation table was notlocated on any currently accessed minidisk.System Action:Command execution stops.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.Source File:Procedure Name:LPRP PASCALGetTranslateTablesTranslation file tablename TCPXLBIN not foundSeverity:Error.Explanation: The named translation table was notlocated on any currently accessed minidisk.System Action:None.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.Source File:Procedure Name:LPR EXECOptionCheckUse either the NOPOSTSCRIPT or POSTSCRIPToption but not both.Severity:Explanation:Warning.You selected both the NOPOSTSCRIPTChapter 11. Remote Printing Messages 177

LPR and LPRSET Messagesand POSTSCRIPT options. You can select only one ofthese options.System Action:None.User or Operator Response: Correct the commandline and reissue the command.Source File:Procedure Name:LPRP PASCALProcessOptionsLANDSCAPE options. You can select only one of theseoptions.System Action:None.User or Operator Response: Correct the commandline and reissue the command.Source File:Procedure Name:LPRP PASCALProcessOptionsUse either the POSTSCRIPT or LANDSCAPE optionbut not both.Severity:Explanation:Warning.LPRM MessagesYou selected both the POSTSCRIPT andThis section contains LPRM messages.Both the printer and the host name are not known.Procedure Name:ProcessOptionsSeverity:Error.Explanation: The program could not determine theprinter name or host name.System Action:None.User or Operator Response: Check the host name andprinter name before you reissue the command.Source File:Procedure Name:LPRM PASCALProcessOptionsCannot get a printer name.Severity:Error.Explanation: The program could not find the printername on the command line or in the GLOBALV file.System Action:None.User or Operator Response: Specify the printer nameon the command line, or use LPRSET to set up thedefault printer name.Source File:Procedure Name:LPRM PASCALProcessOptionsCannot get the printer host.Severity:Error.Explanation: The default host name could not be readfrom the GLOBALV file.System Action:None.User or Operator Response: Specify the host name onthe command line, or use LPRSET to set up the defaulthost name.Source File:LPRM PASCALProgram error: Invalid option (option)Severity:Error.Explanation: You specified an invalid option on thecommand line.System Action:None.User or Operator Response:with valid options.Source File:Procedure Name:LPRM PASCALProcessOptionsThe host name is not known.Severity:Explanation:host name.Error.System Action:Reissue the commandThe program could not determine theNone.User or Operator Response: Use the valid host namewith a command. A valid host name is one that can beresolved by the program.Source File:Procedure Name:LPRM PASCALProcessOptionsThe option option is ambiguous. Use a longerabbreviation.Severity:Warning.Explanation: The abbreviation you specified for thiscommand-line option is ambiguous.System Action:None.User or Operator Response:Reissue the command178 z/VM: TCP/IP Messages and Codes

LPRM Messageswith a longer abbreviation for the intended option.Source File: LPRM PASCALProcedure Name: ProcessOptionsThe 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.System Action:None.User or Operator Response:with valid options.Source File:Procedure Name:LPRM PASCALProcessOptionsReissue the commandThe printer name is not known.Severity:Error.Explanation: The program could not determine theprinter name.System Action:None.User or Operator Response: Check the printer nameat the server machine and reissue the command with avalid printer name.Source File:Procedure Name:LPRM PASCALProcessOptionsChapter 11. Remote Printing Messages 179

LPRM Messages180 z/VM: TCP/IP Messages and Codes

Chapter 12. Remote Procedure Call MessagesRPC MessagesThis chapter contains RPCLIB, RPCINFO, RPCGEN, and VMRPC messages.This 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.vCheck that sufficient memory is available for tasks. The required heap sizevaries, 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 anumber 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). Stringsrequire 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 ReturnCodeSeverity:Fatal.Explanation: RPC encountered an error organizing anauthorization structure.System Action:The program exits.User or Operator Response:None.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 cProcedure Name: marshal_new_auth(),xdr_opaque_auth(), xdr_enum()authunix_create: out of memorySeverity:Explanation:memory.Fatal.RPC could not allocate sufficientSystem Action:The program exits.User or Operator Response: Remove unusedprograms from memory. Compress memory. Restart theprogram.System Programmer Response: Check the freememory requirements for this program.Source File:Procedure Name:auth_uni cauthunix_create()bad auth_len gid length str length auth lengthSeverity:Error.Explanation: An RPC server received authorizationcredentials of an invalid length.System Action:continues.Authorization is denied. The programUser or Operator Response: Check authorizationcredentials, correct and restart program.Source File:Procedure Name:svc_auun c_svcauth_unix()© Copyright IBM Corp. 1987, 2002 181

RPC MessagesBroadcast select problem ReturnCodeSeverity: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:Procedure Name:pmap_rmt crecv_again(), select()broadcast: ioctl (get interface broadcast address)Severity:Error.Explanation: A Portmapper RPC client encountered anerror obtaining the interface broadcast address.System Action:User or Operator Response:The program continues.None.System Programmer Response: For information aboutioctl, see the TCP/IP Programmer’s Reference.Source File:Procedure Name:pmap_rmt cgetbroadcastnets(), ioctl()broadcast: ioctl (get interface configuration)ReturnCodeSeverity:Error.Explanation: A Portmapper RPC client encountered anerror obtaining interface configuration information.System Action:User or Operator Response:The procedure returns.None.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:Procedure Name:pmap_rmt cgetbroadcastnets(), ioctl()broadcast: ioctl (get interface destination address)ReturnCodeSeverity:Error.Explanation: A Portmapper RPC client encountered anerror obtaining the interface destination address.System Action:User or Operator Response:The program continues.None.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.Source File:Procedure Name:pmap_rmt cgetbroadcastnets(), ioctl()broadcast: ioctl (get interface flags): ReturnCodeSeverity:Error.Explanation: A Portmapper RPC client encountered anerror obtaining interface flag settings.System Action:User or Operator Response:The program continues.None.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:Procedure Name:pmap_rmt cgetbroadcastnets(), ioctl()can’t reassign procedure number procSeverity: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:number. The program returns.Source File:Procedure Name:svc_simp cregisterrpc()Correct the procedureCannot create socket for broadcast rpc ReturnCodeSeverity:Fatal.Explanation: A Portmapper RPC client encountered anerror creating a socket for broadcast RPC.System Action:The program exits.User or Operator Response:None.System Programmer Response: Possible causes forthis message include all sockets taken and not enoughmemory. See the TCP/IP Programmer’s Reference for182 z/VM: TCP/IP Messages and Codes

RPC Messagestcperror codes. Use the tcperror code to determine thefault and correct the usage.Source File:Procedure Name:pmap_rmt cclnt_broadcast(), socket()Cannot receive reply to broadcastSeverity:Fatal.Explanation: A Portmapper RPC client encountered anerror attempting to receive a reply to a broadcast.System Action:The program returns.User or Operator Response:None.System Programmer Response: Check pointers thatcould give program check. Check errno for a returncode.Source File:pmap_rmt c, cmiucsoc cProcedure Name: recvfrom(), common_recv()recvfrom(), common_recv()Cannot send broadcast packet ReturnCodeSeverity:Fatal.Explanation: A Portmapper RPC client encountered anerror sending a broadcast packet.System Action:The program exits.User or Operator Response:None.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:Procedure Name:common_send()pmap_rmt c, cmiucsoc cclnt_broadcast(), sendto(),clnt_raw.c - Fatal header serialization error. ReturnCodeSeverity:Explanation:header.Fatal.System Action:RPC encountered an error serializing aThe program returns.User or Operator Response:None.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:Procedure Name:clnt_raw c, xdr c, rpc_prot cclntraw_create(), xdr_callhdr(),xdr_u_long(), xdr_enum(), xdr_short(), xdr_putlong(),xdr_getlong()clnttcp_create: out of memorySeverity:Explanation:memory.Fatal.System Action:RPC could not allocate sufficientThe program returns.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:Procedure Name:clnt_tcp cclntudp_create: out of memorySeverity:Explanation:memory.Fatal.System Action:clnttcp_create(), mem_alloc()RPC could not allocate sufficientThe program returns.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:Procedure Name:clnt_udp ccouldn’t create an rpc serverSeverity:Explanation:failed.Fatal.System Action:clntudp_bufcreate(), mem_alloc()A request to have RPC create a serverThe program returns.User or Operator Response:None.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 cProcedure Name: registerrpc(), svcudp_create(),svcudp_bufcreate(), sock(), bind(), mem_alloc(),xdrmem_createChapter 12. Remote Procedure Call Messages 183

RPC Messagescouldn’t register prog number vers numberSeverity:Fatal.Explanation: A request to have RPC register thisprogram and version failed. Portmapper may not berunning. Storage may not be available.System Action:The program returns.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 cProcedure Name: registerrpc(), svc_register(),pmap_set(), clntudp_bufcreate(), clnt_call()get_myaddress: ioctl (get interface configuration)ReturnCodeSeverity:Fatal.Explanation: An RPC client encountered an errorobtaining interface configuration information(SIOCGIFCONF option).System Action:User or Operator Response:The client exits and the program exits.None.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:Procedure Name:pmap_cln c, cmiucsoc cget_myaddress(), ioctl()get_myaddress: ioctl ReturnCodeSeverity:Fatal.Explanation: An RPC client encountered an errorsetting the interface configuration flags.System Action:User or Operator Response:The client exits. The program exits.None.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 cProcedure Name: get_myaddress(), ioctl()get_myaddress(), ioctl()never registered prog numberSeverity:Informational.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.Source File:Procedure Name:svc_simp cregisterrpc: out of memorySeverity:Fatal.universal() universal()Explanation: An attempt to register an RPC serverfailed because of a lack of memory.System Action:None.User or Operator Response: Remove all possible tasksto clear storage for this task and restart.System Programmer Response:enough storage for the task.Source File:Procedure Name:svc_simp cregisterrpc(), malloc()svc.c: - Select failed ReturnCodeSeverity:Fatal.Verify that there isExplanation: An RPC server encountered an errorwaiting for an incoming message.System Action:The program returns.User or Operator Response:None.System Programmer Response: See the TCP/IPProgrammer’s Reference for tcperror codes. Use thetcperror code to determine the fault and correct theusage.Source File:Procedure Name:svcc,cmiucsoccsvc_run(), select(), common_select()svc_tcp: makefd_xprt: out of memorySeverity:Explanation:Fatal.System Action:An RPC server ran out of memory.The program exits.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.184 z/VM: TCP/IP Messages and Codes

RPC MessagesSource File:Procedure Name:svc_tcp cmakefd_xprt(), mem_alloc()svctcp_.c - cannot getsockname or listen ReturnCodeSeverity: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 Action:The program returns.User or Operator Response:None.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:Procedure Name:listen()svc_tcp c, cmiucsoc csvctcp_create(), getsockname(),svctcp_.c - udp socket creation problem ReturnCodeSeverity:Fatal.Explanation: An RPC server encountered an errorcreating a TCP socket.System Action:The program returns.User or Operator Response:tasks and restart the task.Remove all unneededSystem 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:Procedure Name:svc_tcp c, cmiucsoc csvctcp_create: out of memorySeverity:Explanation:Fatal.System Action:svctcp_create(), socket()An RPC server ran out of memory.None.User or Operator Response: Remove all unneededtasks to free storage and restart task.System Programmer Response:storage is available to run task.Source File:Procedure Name:svc_tcp cCheck that enoughsvctcp_create(), mem_alloc()svcudp_create - cannot getsocknameSeverity:Fatal.Explanation: An RPC server encountered an errorgetting the name of a socket.System Action:The program returns.User or Operator Response:System Programmer Response:pointer.Source File:Procedure Name:None.svc_udp c, cmiucsoc csvcudp_create: out of memorySeverity:Explanation:Fatal.System Action:Check for a badsvcudp_bufcreate(), getsockname()An RPC server ran out of memory.None.User or Operator Response: Remove all unneededtasks to free storage and restart task.System Programmer Response:available for the task.Source File:Procedure Name:svc_udp cCheck that storage issvcudp_bufcreate(), mem_alloc()svcudp_create: socket creation problemSeverity:Fatal.Explanation: An RPC server encountered an errorcreating a socket.System Action:The program returns.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:Procedure Name:svc_udp c, cmiucsoc ctrouble replying to prog numberSeverity:Fatal.svcudp_bufcreate(), socket()Explanation: An error was encountered replying to aremote procedure. The program exits.System Action:The program exits.User or Operator Response:None.System Programmer Response: Check for a badpointer. Check whether the task has adequate storage.Source File:svc_simp c, svc cChapter 12. Remote Procedure Call Messages 185

RPC MessagesProcedure Name: universal(), svc_sendreply()xdr_array: out of memorySeverity: Fatal.Explanation: An XDR function could not allocatesufficient memory.System Action: The program returns.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 cProcedure Name: xdr_array(), mem_alloc()xdr_bytes: out of memorySeverity: Fatal.Explanation: An XDR function could not allocatesufficient memory.System Action: The program returns.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 cProcedure Name: xdr_bytes(), mem_alloc()xdr_reference: out of memorySeverity: Fatal.Explanation: An XDR function could not allocatesufficient memory.System Action: The program returns.User or Operator Response: Remove unneeded tasksto free storage and restart task.System Programmer Response: Determine that thereis sufficient storage for the task.Source File: xdr_refe cProcedure Name: xdr_reference(), mem_alloc()xdr_string: out of memorySeverity:Fatal.Explanation: An XDR function could not allocatesufficient memory.System Action:The program returns.User or Operator Response: Remove unneeded tasksto free storage and restart task.System Programmer Response:is sufficient storage for the task.Source File:Procedure Name:xdr_str cxdrrec_create: out of memorySeverity:Fatal.Determine that therexdr_string(), mem_alloc()Explanation: An XDR function could not allocatesufficient memory.System Action:The program returns.User or Operator Response: Remove unneeded tasksto free storage and restart task.System Programmer Response:is sufficient storage for the task.Source File:Procedure Name:xxxSeverity:xdr_rec cInformational.Determine that therexdrrec_create(), mem_alloc()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:program exits.The svc_sendreply() call failed. TheUser or Operator Response: Remove unneeded tasksto free storage and restart task.System Programmer Response: Check for a badpointer. Check that storage is sufficient.Source File:Procedure Name:svc_simp c, svc cuniversal(), 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.186 z/VM: TCP/IP Messages and Codes

RPC Messagesaddress { (unknown) | name }Severity:Informational.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.User or Operator Response:Source File:Procedure Name:RPCINFO Creply_proc()No remote programs registered.Severity:Informational.None.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.Source File:Procedure Name:RPCINFO Cpmapdump()program number version version ready and waitingSeverity:Explanation:System Action:Informational.User or Operator Response:Source File:Procedure Name:The indicated program is ready.RPCINFO continues execution.RPCINFO Cprogram vers proto portSeverity:Informational.pmapdump()None.Explanation: A list of programs registered on thechosen Portmapper, with version protocol and portinformation, follows this message.System Action:User or Operator Response:Source File:Procedure Name:The program continues.RPCINFO Cpmapdump()None.rpcinfo: broadcast failed: ReturnCodeSeverity:Explanation:broadcast.Fatal.System Action:RPCINFO encountered an error issuing aRPCINFO exits.User or Operator Response: Use err in the message todetermine the probable cause. There are multiple,possible return codes.Source File:Procedure Name:RPCINFO Cbrdcst(), clnt_broadcast()rpcinfo: can’t contact portmapper: rpcinfo ReturnCodeSeverity:Fatal.Explanation: RPCINFO encountered an errorestablishing a TCP connection to Portmapper.System Action:RPCINFO exits.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.Source File:Procedure Name:clnt_broadcast()RPCINFO Crpcinfo: host is unknown hostSeverity:Fatal.pmapdump(), clnt_call() brdcst(),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.System Action:RPCINFO exits.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.Source File:RPCINFO CProcedure Name: get_net_address() udpping(),socket() udpping(), tcpping()rpcinfo: service is unknown serviceSeverity:Informational.Explanation: The program number specified on thecommand line does not correspond to a known service.Chapter 12. Remote Procedure Call Messages 187

RPC MessagesSystem Action:RPCINFO exits.User or Operator Response: Correct the programnumber. Verify that the server is running and that itregisters the correct number. Rerun.Source File:Procedure Name:rcpinfo: socketSeverity:Fatal.RPCINFO Cgetprognum(), getrpcbyname()Explanation: RPCINFO encountered an error openinga UDP socket for PING.System Action:RPCINFO exits.User or Operator Response: Retry. for socket()parameters. Check for a memory constraint. Checkwhether TCPIP is running locally or remotely.Source File:RPCINFO CProcedure Name:udpping(), socket()Usage: rpcinfo [ -n portnum ] -u host prognum [versnum ] rpcinfo [ -n portnum ] -t host prognum [versnum ] rpcinfo -p [ host ] rpcinfo -b prognumversnumSeverity:Informational.Explanation: The command line syntax is displayed toindicate that the user invoked RPCINFO with invalidarguments.System Action:RPCINFO exits.User or Operator Response: Reenter RPCINFO withthe correct control parameter syntax.Source File:Procedure Name:RPCINFO Cusage()RPCGEN MessagesThis section contains RPCGEN messages.command: file ReturnCodeSeverity: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:Procedure Name:RPCMAIN Copen_input()command: output would overwrite fileSeverity:Fatal.Explanation: The specified output file wouldoverwrite the input file. You must choose an output filename different from the input file name.System Action:RPCGEN exits.User or Operator Response:name and restart.Source File:Procedure Name:RPCMAIN Copen_output()Change the output filecommand: unable to open file ReturnCodeSeverity:Explanation:file.Fatal.System Action:RPCGEN was unable to open the outputRPCGEN exits.User or Operator Response: Determine from the errorcode why the file is unavailable. Possible reasonsinclude: missing, out of memory, and wrong pointer.Source File:Procedure Name:RPCMAIN Copen_output()line file, line number: array declaration expectedSeverity:Fatal.Explanation: TCP/IP expected an array declaration atthis line of the source file.System Action:RPCGEN exits.User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.System Programmer Response:Source File:Procedure Name:RPCPARSE Cget_declaration()Correct the program.line file, line number: constant or identifier expectedSeverity: Fatal.Explanation: TCP/IP expected a constant or identifierat this point in the source file.188 z/VM: TCP/IP Messages and Codes

RPC MessagesSystem Action: RPCGEN exitsUser or Operator Response: Correct the program andrestart, or tell the system programmer about the error.Source File: RPCSCAN CProcedure Name: scan_num()line file, line number: definition keyword expectedSeverity: Fatal.Explanation: RPCGEN expected a definition keywordat this point in the source file.System Action: RPCGEN exits.User or Operator Response: Correct the source fileand restart.Source File: RPCPARSE CProcedure Name: get_definition()User or Operator Response: Correct the source andrestart.Source File: RPCPARSE CProcedure Name: def_program()line file, line number: illegal character in fileSeverity: Fatal.Explanation: TCP/IP encountered an illegal characterin the source file.System Action: RPCGEN exits.User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.System Programmer Response: Correct the program.Source File: RPCSCAN CProcedure Name: get_token()line file, line number: expected type specifierSeverity: Fatal.Explanation: TCP/IP expected a type specifier at thispoint in the source file.System Action: RPCGEN exits.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 CProcedure Name: get_type()line file, line number: expected type specifierSeverity: Fatal.Explanation: TCP/IP expected a type specifier at thispoint in the source file.System Action: RPCGEN exits.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 CProcedure Name: get_type()line file, line number: illegal argument typeSeverity: Fatal.Explanation: TCP/IP encountered an illegal argumenttype, opaque, on this line of the source file.System Action: RPCGEN exitsline file, line number: illegal result typeSeverity:Fatal.Explanation: TCP/IP encountered an illegal resulttype, opaque, on this line of the source file.System Action:RPCGEN exits.User or Operator Response:and restart.Source File:Procedure Name:RPCPARSE Cdef_program()Correct the source fileline file, line number: no array-of-pointer declarations --use typedefSeverity: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.System Action:RPCGEN exits.User or Operator Response: Do a typedef of thearray-of-pointers, or tell the system programmer aboutthe error.System Programmer Response:array-of-pointers and restart.Source File:Procedure Name:RPCPARSE Cget_declaration()Do a typedef of theChapter 12. Remote Procedure Call Messages 189

RPC Messagesline file, line number: preprocessor errorSeverity: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.System Action:RPCGEN exits.User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.System Programmer Response:Source File:Procedure Name:RPCSCAN Cdocppline()Correct the program.line file, line number: unterminated string constantSeverity: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 Action:RPCGEN exits.User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.System Programmer Response: Examine the programdata for an unterminated string or a bad pointer.Correct the program.Source File:Procedure Name:RPCSCAN Cfindstrconst()line file, line number: variable-length array declarationexpectedSeverity:Fatal.Explanation: TCP/IP expected a variable-length arraydeclaration at this point in the source file.System Action:RPCGEN exits.User or Operator Response: Correct the inputprogram and restart, or tell the system programmerabout the error.System Programmer Response:program.Source File:Procedure Name:RPCPARSE Cget_declaration()Correct the inputvoid type at this line in the source file.System Action:RPCGEN exits.User or Operator Response: Correct the program andrestart, or tell the system programmer about the error.System Programmer Response:Source File:Procedure Name:too many files!Severity:Fatal.RPCPARSE Cget_type()Correct the program.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 tozero.IfCdoes not clear nfiles to 0, the message occursunpredictably.System Action:exits.User or Operator Response:If the message appears, RPCGENNoneSystem Programmer Response: If the compiler doesnot provide a reset to nfiles, add a software reset tonfiles.Source File:Procedure Name:RPCUTIL Crecord_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]]Severity:Informational.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.System Action:RPCGEN exits.User or Operator Response:restart.Source File:Procedure Name:RPCMAIN Cmain()Correct the syntax andline file, line number: voids allowed only inside unionand program definitionsSeverity:Explanation:Fatal.TCP/IP encountered an inappropriate190 z/VM: TCP/IP Messages and Codes

Chapter 13. REXEC and REXECD MessagesREXEC MessagesThis chapter contains REXEC and REXECD messages.Command timed outSeverity: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:Procedure Name:Error:Severity:Error.REXEC PASCALRECV_NOTICESExplanation: The DataDelivered procedureencountered an error condition. This message can befollowed by a specific message output line for eachbuffer character error encountered thereafter.System Action:None.User or Operator Response:Source File:Procedure Name:Error: bad characterSeverity:Error.REXEC PASCALNone.RECV_NOTICESExplanation: The DataDelivered procedureencountered a specific error. The message lists anerroneous buffer character for each error at the end ofthe message.System Action:None.User or Operator Response:Source File:Procedure Name:REXEC PASCALHost foreignhost Unknown.Severity:Error.None.RECV_NOTICESExplanation: The requested foreign host is unknownto this host. This message means that the requestedforeign host is not listed in the search table defined tothis REXEC session.System Action:REXEC halts.User or Operator Response: Determine the reason forthis failure, correct it, and rerun the program.Source File:Procedure Name:REXEC PASCALUTSTARTTELNETINITLogon 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.System Action:Command execution stops.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.Source File:Procedure Name:REXEC PASCALGETPARM-p option requires one parameter: Severity:Error.Explanation: An option parameter was missing fromor invalid in the -p option.System Action:REXEC halts.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.Source File:Procedure Name:REXEC PASCALGETPARMrexec: no command given.Severity:Explanation:Error.The command input was null.© Copyright IBM Corp. 1987, 2002 191

REXEC MessagesSystem Action:REXEC halts.User or Operator Response: Input a valid REXECcommand when you rerun the program.Source File:Procedure Name:REXEC PASCALGETPARMrexec: No foreign hostname given.Severity:Explanation:Error.System Action:The foreign host name input was null.REXEC halts.User or Operator Response: Input a valid foreign hostname when you rerun the program.Source File:Procedure Name:REXEC PASCALGETPARM-s option requires one parameter: Severity:Error.Explanation: An option parameter was missing fromor invalid in the -s option.System Action:REXEC halts.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.Source File:Procedure Name:REXEC PASCALGETPARM-t option requires one parameter: Severity:Error.Explanation: An option parameter was missing fromor invalid in the -t option.System Action:REXEC halts.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.Source File:Procedure Name:REXEC PASCALtcpwaitsend: ReturnCodeSeverity:Error.GETPARMExplanation: A nonzero return code was returnedfrom a tcpwaitsend call.System Action:REXEC halts.User or Operator Response: Determine if a networkproblem exists before you rerun the program.Source File:Procedure Name:REXEC PASCALREXEC_UTILtimeout is not a valid number of secondsSeverity: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.System Action:REXEC halts.User or Operator Response: Input a valid time-outwith the -t option when you rerun the program.Source File:Procedure Name:REXEC PASCALGETPARMUnable to open passive port for host foreignhostSeverity:Explanation:exists.Error.System Action:A possible network or hardware problemREXEC halts.User or Operator Response: Determine the reason forthis failure, correct it, and rerun the program.Source File:Procedure Name:REXEC PASCALUTSTARTTELNETINITUnable to open port TCP_REXEC to host foreignhostSeverity:Explanation:exists.Error.System Action:A possible network or hardware problemREXEC halts.User or Operator Response: Determine the reason forthis failure, correct it, and rerun the program.Source File:Procedure Name:REXEC PASCALUnknown option optionSeverity:Error.UTSTARTTELNETINITExplanation: You input an invalid option, which islisted at the end of the message.System Action:REXEC halts.User or Operator Response: Input a valid optionwhen you rerun the program.Source File:Procedure Name:REXEC PASCALGETPARM192 z/VM: TCP/IP Messages and Codes

REXECD MessagesREXECD Messagesafter 30 secs, rc ReturnCodeSeverity: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.System Action:None.User or Operator Response: Determine the cause ofthis problem and correct it before continuing.Source File:Procedure Name:RXMAIN CMAINCannot execute the following command; commandrc=returncode >> Severity:Error.Explanation: The listed command could not beexecuted for the reason listed in the return code.System Action:None.User or Operator Response: Determine the reason thismessage was issued and correct the problem beforecontinuing.Source File:Procedure Name:RXMAIN Ccommand cannot be executedSeverity:Explanation:executed.Error.System Action:FILL_CONN_STRUCTThe listed command could not beNone.User or Operator Response: Determine the reasonthat this message was issued and correct the problembefore continuing.Source File:Procedure Name:RXMAIN CMAINDiag 0x084 returns: cc=cc rc=returncodeUser ID: userid Password: passwwordSeverity:Error.Explanation: You entered an erroneous user ID orpassword combination that caused diagnose 0x084 tofail with the listed nonzero condition and return codes.System Action:None.User or Operator Response:and password.Source File:Procedure Name:RXMAIN CCHECK_PWDDiag 0x08 returns: rc=returncodeFor command: command_stringSeverity:Error.Enter a correct user IDExplanation: The diagnose 0x08 failed with the listednonzero return code from an attempt to issue a CPcommand.System Action:None.User or Operator Response: Review the diagnosereturn code to determine why the diagnose 0x08command failed.Source File:Procedure Name:RXMAIN CCPError in TCP receive - - ReturnCodeSeverity: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:Procedure Name:RXUTILS CSTDREADError in TCP send retcode ReturnCodeSeverity: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.System Action:REXECD halts.User or Operator Response: Check and correct anynetwork problems before you resubmit this taskrequest.Source File:Procedure Name:RXUTILS CSTDWRITEError in TCP Wait receive - - ReturnCodeSeverity:Explanation:Error.A call to the tcpwaitreceive procedureChapter 13. REXEC and REXECD Messages 193

REXECD Messagesresulted 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:Procedure Name:RXUTILS CWATREADError: Unknown NETSTAT command, typeSeverity:Error.Explanation: The command was not a knownNETSTAT command. The following are valid NETSTATcommands:v CPv CONNv UPv ALLCONNv DROPv CLIENTSv GATEv DEVLINKSv HOMEv SOCKETv TELNETv POOLSIZEv ALLv INTERVALSystem Action:None.User or Operator Response:command.Source File:Procedure Name:RXMAIN CNETSTAT_CMDError: Unknown option: optionSeverity:Error.Submit a valid NETSTATExplanation: 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:and try again.Source File:Procedure Name:RXMAIN CGET_OPTSFailure on call to: getidentitySeverity:Error.Correct the input syntaxExplanation: This message is the first line of an errormessage that indicates that a call to the cgetidentityprocedure resulted in a nonzero return code.System Action:None.User or Operator Response:Source File:RXMAIN CNone.Procedure Name:Incorrect passwordSeverity:Explanation:Error.System Action:MAINYou entered an incorrect password.None.User or Operator Response: Enter the correctpassword for the requested user ID.Source File:Procedure Name:RXMAIN CIncorrect userid/passwordSeverity:Error.CHECK_PWDExplanation: You entered an incorrect user ID orpassword combination. Your logon request was denied.System Action:None.User or Operator Response:and password combination.Source File:Procedure Name:Invalid passwordSeverity:Explanation:Error.System Action:RXMAIN CCHECK_PWDEnter a correct user IDYou entered an invalid password.None.User or Operator Response:for the requested user ID.Source File:Procedure Name:RXMAIN CCHECK_PWDEnter the valid passwordMSG machine name Remote Execution DaemonshutdownSeverity:Warning.Explanation: The CP MSG facility on the host sendsthis message to warn agent machines that REXECD isshutting down.System Action:None.User or Operator Response: You cannot use REXECDuntil the program is restarted.Source File:Procedure Name:RXMAIN CMAIN194 z/VM: TCP/IP Messages and Codes

REXECD MessagesNo agent machines are available at this time.Severity:Error.Explanation: No agent machines are available forprocessing REXECD requests.System Action:None.User or Operator Response: Determine the reason thismessage was issued and correct the problem beforecontinuing.Source File:Procedure Name:RXMAIN CXVM_N_SENDREXEC port number is not valid. Using defaultREXEC port: 512Severity:Explanation:zero.Warning.You entered a port number less thanSystem Action: The program uses the default REXECport and continues processing.User or Operator Response:Source File:Procedure Name:RXMAIN CGET_OPTSNone.Shutting down due to notification from TCP/IPSeverity: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.User or Operator Response:Source File:Procedure Name:RXMAIN CMAINTcpwrite failed on conn connSeverity:Error.None.Explanation: A nonzero return code was returnedfrom a call to tcpwrite on the listed connection.System Action:None.User or Operator Response: Investigate possiblenetwork problems before you resubmit the task.Source File:Procedure Name:RXMAIN CMAINGENDELIV MODULE not accessibleSeverity:Warning.Explanation: A required part of the executables forREXECD does not reside on any of the VM minidisksaccessed by the program driver.System Action:None.User or Operator Response: Ensure that theGENDELIV component is on an accessed minidiskbefore you resubmit this task request.Source File:Procedure Name:RXMAIN CMAINWAITDEV MODULE not accessibleSeverity:Warning.Explanation: A required part of the executables forREXECD does not reside on any of the VM minidisksaccessed by the program driver.System Action:None.User or Operator Response: Ensure that theWAITDEV MODULE is on an accessed minidisk beforeyou resubmit this task request.Source File:Procedure Name:RXMAIN CMAINReceived a catastrophic error from the client:OPENrejected Recycling REXECDSeverity: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.User or Operator Response:Source File:Procedure Name:RXMAIN CMAINNone.RSH port number is not valid. Using default RSHport: 514Severity:Explanation:zero.Warning.You entered a port number less thanSystem Action: The program uses the default RSHport and continues processing.User or Operator Response:Source File:Procedure Name:RXMAIN CGET_OPTSNone.Chapter 13. REXEC and REXECD Messages 195

REXECD MessagesThe -e option requires one parameter: Severity:Explanation:this option.Error.A port number was not provided withSystem Action: REXECD halts with a return code of 1.User or Operator Response: Reissue the commandproviding an appropriate port number.Source File:Procedure Name:RXMAIN CGET_OPTSThe -h option requires one parameter: Severity:Explanation:this option.Error.A port number was not provided withSystem Action: REXECD halts with a return code of 1.User or Operator Response: Reissue the commandproviding an appropriate port number.Source File:Procedure Name:RXMAIN CGET_OPTSThe -s option requires one parameter: Severity:Explanation:Error.You made a syntax error in your input.System Action: REXECD halts with a return code of 1.User or Operator Response: Correct the input syntaxfor the agent service machine and try again.Source File:Procedure Name:RXMAIN CGET_OPTSThe -t option requires one parameter: Severity:Explanation:Error.You made a syntax error in your input.System Action: REXECD halts with a return code of 1.User or Operator Response: Correct the input syntaxfor the connection time-out value and try again.Source File:Procedure Name:RXMAIN CGET_OPTSTcp active open failed -- rc ReturnCodeSeverity: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 haltsafter 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.System Action:None.User or Operator Response: Check for and correctany network problems before resubmitting this taskrequest.Source File:Procedure Name:RXMAIN CACT_OPENTCPCLOSE failed, rc ReturnCodeSeverity:Warning.Explanation: The listed nonzero return code wasreturned from a call to tcpclose for an activeconnection.System Action:None.User or Operator Response: Investigate possiblenetwork problems before you resubmit the task.Source File:Procedure Name:RXMAIN CCLOSETcp open failed -- rc ReturnCodeSeverity: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.System Action:REXECD halts.User or Operator Response: Check and correct anynetwork problems before you resubmit this taskrequest.Source File:Procedure Name:RXMAIN CPASS_OPENTimeout value is not valid; Using default value: 240secondsSeverity:Warning.Explanation: You have entered a time-out value lessthan zero. In this case, the program uses the defaulttime-out value and continues processing.System Action:None.User or Operator Response:Source File:Procedure Name:RXMAIN CGET_OPTSNone.196 z/VM: TCP/IP Messages and Codes

REXECD MessagesTimer Expired: Connection ClosedSeverity:Error.Explanation: A timer has expired and the connectionhas been closed.System Action:None.User or Operator Response: Determine the reason thismessage was issued and correct the problem beforecontinuing.Source File:Procedure Name:RXMAIN CMAINUnable to Autolog machine nameSeverity:Explanation:machine.Warning.System Action:REXECD could not autolog the agentNone.User or Operator Response:machine before continuing.Source File:Procedure Name:RXMAIN CMAINLog or force off the agentUnable to open active connectionSeverity:Explanation:Warning.System Action:There was a ctcpwatopen failure.None.User or Operator Response: Check for and correctany network problems before he resubmits this taskrequest.Source File:Procedure Name:RXMAIN CACT_OPENUnknown notification, 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.System Action:None.User or Operator Response:Source File:Procedure Name:RXUTILS CPRTNOTICENone.Unable to autolog user UserIDSeverity: Warning.Explanation: The listed user ID could not beautologged with the RXSNDIU EXEC for any system.System Action: None.User or Operator Response: None.Source File: RXMAIN CProcedure Name: XVM_N_SENDUnable to communicate with user UserIDSeverity:Warning.Explanation: The system was unable to communicatewith the listed user ID.System Action:None.User or Operator Response: The remote user shoulddetermine the reason that this message was issued andcorrect the problem before continuing.Source File:Procedure Name:RXMAIN CXVM_N_SENDChapter 13. REXEC and REXECD Messages 197

REXECD Messages198 z/VM: TCP/IP Messages and Codes

Chapter 14. ROUTED MessagesThis section contains the messages for the RouteD server.DTCRTD4820I VM TCP/IP RouteD server functionlevelExplanation: This message indicates the function levelof the RouteD server.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4823I Tracing debug packets actiontimestampExplanation: Debug packets tracing is enabled ordisabled. The packets are displayed in data format.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4825Sname/udpNone.None.Explanation: A UDP port number for the routerservice name was not resolved in the PROFILE TCPIPfile.System Action:User or Operator Response:RouteD ends abnormally.None.System Programmer Response: Verify that a UDPport has been reserved for RouteD using the PORTstatement in PROFILE TCPIP.DTCRTD4826S Terminating since clients require asocketExplanation: 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 Action:User or Operator Response:RouteD ends abnormally.None.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.DTCRTD4827SUsage: RouteD (Input parameters)Explanation: RouteD was passed parameters that arenot supported or were not formatted correctly.System Action:User or Operator Response:RouteD ends abnormally.None.System Programmer Response: Correct theparameters and separate them with spaces. Refer toTCP/IP Planning and Customization for moreinformation.DTCRTD4828IInput parameter(s): parameterExplanation: This message displays the inputparameters supplied to the RouteD server by the user.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4829INone.None.Waiting for incoming packetsExplanation: 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.User or Operator Response:None.System Programmer Response: If6ormoreofthesemessages 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.DTCRTD4830EThe main select was interruptedExplanation: An error was detected while RouteD waswaiting for an event to occur. A subsequent messagewill be issued with more error information.System Action:RouteD continues.User or Operator Response:System Programmer Response:running.None.Verify that TCPIP is© Copyright IBM Corp. 1987, 2002 199

ROUTED MessagesDTCRTD4831ISend delayed dynamic updateExplanation: A routing update that was delayed toprevent packet storms has been transmitted. Thisoccurs 2–5 seconds after a dynamic update has beenissued.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4832ENone.None.While receiving a packetExplanation: 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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4833SA socket could not be createdExplanation: RouteD could not open a new socket. Asubsequent message will be issued with more errorinformation.System Action:User or Operator Response:RouteD ends abnormally.None.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 socketExplanation: RouteD cannot enable the socket forbroadcasting. RouteD must be able to broadcast overinterfaces that support broadcasting to communicatewith other routers.System Action:User or Operator Response:RouteD ends abnormally.System Programmer Response:Software Support Center.DTCRTD4835SNone.The socket bind failedContact your IBMExplanation: RouteD was unable to associate aninternet address and port number with the newlycreated socket. This might be because anotherapplication is using the port.System Action:User or Operator Response:RouteD ends abnormally.None.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.DTCRTD4836Efunction: socket create failedExplanation: 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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4837Eioctl (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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4838Einterface: ioctl (get interface flags)Explanation: RouteD encountered an error whileobtaining the interface flags for interface. Amorespecific message follows, which indicates the errorreturned from the ioctl. The interface is skipped.System Action:RouteD continues.User or Operator Response:None.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.System Action:RouteD continues.User or Operator Response:None.200 z/VM: TCP/IP Messages and Codes

ROUTED MessagesSystem Programmer Response: Refer to the next errormessage issued and correct the error.System Programmer Response: Increase the VirtualMachine storage and restart RouteD.DTCRTD4840Einterface: 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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4845WentryExplanation: A warning is about to be issued for theindicated entry in the ETC GATEWAYS file. Asubsequent message will be issued with more errorinformation.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4841Einterface: 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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4846EentryExplanation: An error is about to be issued for theindicated entry in the ETC GATEWAYS file. Asubsequent message will be issued with more errorinformation.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4842W Ignoring incorrect metric oninterface interfaceExplanation: An incorrect metric value was specifiedfor this interface in the BSDROUTINGPARMSstatement. The default metric of 0 (zero) is used.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Specify a correctmetric value in the range from 0 to 15.DTCRTD4843Einterface: 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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Refer to the next errormessage issued and correct the error.DTCRTD4844SFunction function out of memoryExplanation: RouteD is unable to allocate the freestorage needed to process an interface.System Action:RouteD continues.User or Operator Response:None.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”.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4848E Gateway type ‘type’ incorrect foractive gatewayExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCChapter 14. ROUTED Messages 201

ROUTED MessagesDTCRTD4849IRouteD Server startedExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4850INone.None.Processing interface interfaceExplanation: The indicated interface was found inTCPIP’s interface table and is being added to RouteD’sinterface table.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4851E First two elements must be ‘active’for active gatewayExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4852ENone.Correct the ETCIncorrect 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4853E packet from unsupported addressfamily family, cmdcommandExplanation: 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 Action:RouteD continues.User or Operator Response:None.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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Correct the router thatis sending the version 0 packets.DTCRTD4855W trace command from unknownrouter routerExplanation: 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 Action:RouteD continues.User or Operator Response:None.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 interfaceExplanation: 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 Action:RouteD continues.User or Operator Response:None.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:202 z/VM: TCP/IP Messages and Codes

ROUTED MessagesReasonInterface in strange stateIflookup failedthis Link is PASSIVE!The packet is discarded.System Action:ExplanationRouteD continues.User or Operator Response:The network does notsupport broadcast orpoint-to-pointtransmissions.Not directly connected.Cannot update.None.System Programmer Response: Locate and correct therouter that originated the packet.DTCRTD4858W route from router in unsupportedaddress family familyExplanation: An incoming route from another routeris in an address family that is not supported byRouteD. Only internet addresses are supported. Theroute is ignored.System Action:RouteD continues.User or Operator Response:System Programmer Response:router that originated the route.None.Locate and correct theDTCRTD4859E Illegal address host in route fromrouterExplanation: 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 Action:RouteD continues.User or Operator Response:System Programmer Response:router that originated this route.None.Locate and correct theDTCRTD4860W Bad metric metric in route todestination from routerExplanation: A route was received from routercontaining a metric that was not in the range 1–16. Theroute is ignored.System Action:RouteD continues.User or Operator Response:System Programmer Response:router that originated this route.None.Locate and correct theDTCRTD4861ISend dynamic updateExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4862INone.None.Delay dynamic updateExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4863I Inhibit dynamic update for numbersecondsExplanation: A dynamic update has been sent. Furtherdynamic updates will not be sent during the next 2–5seconds.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4864E inet_output: sendto destinationdestinationExplanation: An error occurred while attempting totransmit a packet. The packet is not sent. A subsequentmessage will be issued with more error information.System Action:RouteD continues.User or Operator Response:System Programmer Response:message and correct the error.None.Refer to the next errorDTCRTD4865E Trace buffers not initialized forinterface interfaceExplanation: One or both of the trace buffers for thespecified interface could not be initialized. Tracing islimited.System Action:RouteD continues.Chapter 14. ROUTED Messages 203

ROUTED MessagesUser or Operator Response:None.System Programmer Response: Increase the VirtualMachine size for RouteD and restart.DTCRTD4866IExplanation:System Action:Tracing action timestampTracing is enabled or disabled.RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4867INone.None.Displaying internal type tableExplanation: RouteD’s internal IP routing or interfacetable is displayed for diagnosis.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4868INone.None.Tracing actions action timestampExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4869INone.None.Tracing packets action timestampExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4870INone.None.Tracing history action timestampExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4871I Tracing packet contents actiontimestampExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4882Itimestamp:None.None.Explanation: A full time stamp is issued showing dateand time so that traces can be interpreted correctly.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4883I action destination destination, routerrouter, metric metric flags flags state statetimer timerExplanation: A route to destination is added, changed,or deleted depending on the value of action. Thefollowing values for action are allowed:ValueADD:CHANGE FROM:CHANGE TO:DELETE:System Action:DescriptionA route to destination is addedthrough router at a metric of metric.The route to destination is changed,the old values are displayed.The route to destination is changed,the new values are displayed.The route to destination is deleted.RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4884ENone.None.rtadd: incorrect address familyExplanation: 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:added.RouteD continues, the route is not204 z/VM: TCP/IP Messages and Codes

ROUTED MessagesUser or Operator Response:None.System Programmer Response: Identify the routerwhich generated this route and correct the problem.DTCRTD4885W * Variable subnetting not supportedin TCPIPExplanation: RouteD has been configured to usevariable subnetting (RIP version 2), but the currentTCPIP stack is not configured to support variablesubnetting.System Action:RouteD continuesUser 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:DTCRTD4888InoneInterface interface is passiveExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4889I CHANGE metric destinationdestination, router router, from old metricto new metricExplanation: 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).System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4890I toall: requested to skip interfaceinterfaceExplanation: 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 broadcastto other interfaces to inform adjacent routers of therouting change.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4891I *** Packet history for interfaceinterface ***Explanation: Tracing is set at the history level and thehistory trace data for the inactive interface is displayed.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4892I *** End packet history ***Explanation: Tracing is set at the packet history leveland this message ends the history trace data for theinactivated interface.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4897INone.None.direction: no packetsExplanation: Either the input or output trace buffer,depending on the value of direction, isempty.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4898Idirection traceNone.None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4899I RIPcmd direction router -> port verversion timestampExplanation: 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:Chapter 14. ROUTED Messages 205

ROUTED MessagesRIPcmdREQUESTRESPONSETRACEONTRACEOFFDescriptionIndicates that the routing tableinformation is requested. Individualroutes or a complete routing tablemay be requested.Indicates that the routing tableinformation is broadcast.Request to start tracing to a specifiedfile.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4900S Bad cmd hex direction router–> portsize=size cp=cp packet=packettime=timestampExplanation: A malformed packet was encounteredduring tracing. The source of the packet is either routerif direction is “from”, or RouteD if direction is “to”.System Action:RouteD continues.User or Operator Response:None.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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Verify that theincoming packet was built correctly and can beprocessed by other routers.DTCRTD4902Idestination destination metric metricExplanation: 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.System Action:RouteD continues.User or Operator Response:None.System Programmer Response:DTCRTD4903INone.(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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4904W Unknown address family (family)metric metricExplanation: A route was found in the trace with anunknown address family.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: If the route originatedfrom another router, locate that router and correct it.DTCRTD4905ITraceOn file = fileExplanation: A TRACEON packet was received, tracedata is requested to go to file.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4909E Error adding route to destinationthrough router router, metric metricExplanation: An error occurred while attempting toadd a route to destination. A subsequent message willbe issued with more error information.System Action:added.User or Operator Response:System Programmer Response:DTCRTD4910ERouteD continues, the route is notNone.See DTCRTD4910E.function: SIOCADDRT ioctl failedExplanation: RouteD was unsuccessful in adding anew route. The error occurred in the indicated functionand is one of the following:FunctionrtaddrtchangeDescriptionRouteD attempted to add a new routeto the TCP/IP IP routing table.RouteD attempted to change themetric of a route in the TCPIP206 z/VM: TCP/IP Messages and Codes

ROUTED Messagesmainserver’s IP routing table by deletingthe old route, then adding a new onewith the updated metric.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:ErrorEACESSEEXISTDescriptionRouteD 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).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.ENOBUFSENOENTEINVALEOPNOTSUPPTCP/IP did not have a free IP RouteControl Block to add the route to therouting table.TCP/IP did not have a link interfacedefined for the route to be added to.An incorrect parameter has beenpassed to TCP/IP.TCP/IP does not support therequested operation.System Action: The route is not added. RouteDcontinues. If this occurs during initialization, thenRouteD ends abnormally.User or Operator Response:System Programmer Response:the following responses:ErrorEACESSEEXISTResponseNone.These errors requireMake sure that the user ID of theRouteD virtual machine is correctlyspecified in the OBEY statement forTCP/IP configuration file (PROFILETCPIP).Clear the IP routing table beforerestarting the RouteD Server. AnOBEY file with the word GATEWAYremoves all routes.ENOBUFSIncrease 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.ENOENTEINVALEOPNOTSUPPDefine 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.Verify the validity of statements inthe ETC GATEWAYS file.Verify that the statement“ASSORTEDPARMSVARSUBNETTING” appears in thePROFILE TCPIP.DTCRTD4912E Error deleting route to destinationthrough router router, metric metricExplanation: An error occurred while attempting todelete a route to destination. A subsequent message willbe issued with more error information.System Action:RouteD continues.User or Operator Response:None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4918ENone.None.function: SIOCDELRT ioctl failedExplanation: RouteD was unsuccessful in deleting aroute. The error occurred in function, and is one of thefollowing:FunctionrtdeletertchangeDescriptionRouteD attempted to delete a routefrom TCP/IP’s routing table.RouteD needed to change a route, butChapter 14. ROUTED Messages 207

ROUTED MessagesrtdeleteallTCP/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.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:deleted.User or Operator Response:System Programmer Response:Software Support Center.DTCRTD4919IRouteD continues, the route is notNone.Contact your IBMUsing backup interface interfaceExplanation: A primary interface became inactive anda secondary interface is serving as the backup.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4920I Add type route ignored, route existson interface interfaceExplanation: A network, subnetwork, or destinationtype route already exists on an active interface. Asageneral 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:Software Support Center.None.Contact your IBMDTCRTD4922IOption(s): optionsExplanation: Additional RouteD options, specified inan ETC GATEWAYS file, are being processed. Refer toTCP/IP Planning and Customization for moreinformation.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4923ENone.None.Invalid option: optionExplanation: The entry in the ETC GATEWAYS filehas an incorrect option. Although other options may beprocessed normally, the incorrect one is ignored.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4924INone.Correct the ETCRe-installing interface interfaceExplanation: The previously deleted interface is beingreinstalled because traffic has been detected over it.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4925INone.None.Start of ETC GATEWAYS processingExplanation: The ETC GATEWAYS file is about to beprocessed. Processing messages may follow for theentries in the file.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4926INone.None.End of ETC GATEWAYS processingExplanation: Processing has completed for the ETCGATEWAYS file.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4927W Specified metric not allowed,changing to metricExplanation: 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 was208 z/VM: TCP/IP Messages and Codes

ROUTED Messagesspecified and is changed to 15 for any other value notin the valid range.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4928S Out of memory while processingETC GATEWAYSExplanation: RouteD did not have enough storageavailable to process the ETC GATEWAYS file.System Action:User or Operator Response:RouteD ends abnormally.None.System Programmer Response: Increase the VirtualMachine storage size for RouteD and restart it.DTCRTD4929IPort port assigned to nameExplanation: RouteD listens for traffic from otherrouters on the specified port number port assigned torouter service name.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.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 Action:RouteD continues.User or Operator Response:None.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 supportedExplanation: 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 Action:RouteD continues.User or Operator Response:None.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 Action:RouteD continues.User or Operator Response:None.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 Action:RouteD continues.User or Operator Response:None.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.DTCRTD4934IExplanation:opened.System Action:Opening ETC GATEWAYS (filename)The ETC GATEWAYS file is beingRouteD continues.User or Operator Response:System Programmer Response:DTCRTD4935SNone.None.Incorrect parameter: parameterExplanation: An incorrect parameter was passed toRouteD. The parameter could either be passed from thecommand line parameters or from the list in theDTCPARMS file.System Action:RouteD continues.User or Operator Response:None.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 metricExplanation: The indicated route, defined in the ETCGATEWAYS file, is being added to RouteD’s routingChapter 14. ROUTED Messages 209

ROUTED Messagestable. The route to the gateway will not be replaced bya competing RIP route.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4937W Subnetwork mask unknown fordestination, using network route routeExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4938I Adding active gateway ip_addr, metricmetricExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4939S Trace levels exceeded maximum of 4Explanation: 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.System Action:RouteD ends abnormally.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.System Programmer Response:None.DTCRTD4940I Point-to-point interface, usingaddrtypeExplanation: 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 apoint-to-point link is used. This address is used forsending routing information over an interface to thedestination router or host.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4941I Interface interface skipped, interface ismulticast-incapableExplanation: 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 Action:RouteD continues.User or Operator Response:None.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.DTCRTD4942INot an internal interfaceExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4943INone.None.Adding type route for interfaceExplanation: The route using the network,subnetwork, or host type is being added to theinterface in RouteD’s routing table.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Non-IP addresses arenot supported in this version of RouteD. Either ignore210 z/VM: TCP/IP Messages and Codes

ROUTED Messagesthe 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.DTCRTD4945Iifwithnet: compare with valueExplanation: The route’s network address is beingcompared to one of RouteD’s interface entries for anetwork number match.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4946S ifwithnet: interface has bad addressfamilyExplanation: 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.User or Operator Response:None.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.DTCRTD4947Inetmatch ipaddr1 and ipaddr2Explanation: The network number for the first addressmatches the network address of the interface entry withthe second address.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4948INone.None.This interface is not point-to-pointExplanation: The interface RouteD is currentlyhandling is not a point-to-point interface. RouteD willcreate a route to the network for the interface.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4949IInterface interface not upExplanation: RouteD determined that the indicatedinterface is not active. No routes will be added untilthe interface is activated or reactivated.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4950WNone.None.Interface interface ignoredExplanation: The indicated interface address family isnot valid. The interface is ignored to prevent networkor subnetwork routes from being added.System Action:RouteD continues.User or Operator Response:None.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 destinationExplanation: 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:ValueAction3 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.User or Operator Response:System Programmer Response:the following responses:ValueResponseNone.These actions require3 If the route was broadcast for a while and thenChapter 14. ROUTED Messages 211

ROUTED Messagessuddenly 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.DTCRTD4955IIgnoring route destination, filtered outExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4956INone.None.Deleting interface interface_nameExplanation: RouteD is deleting the interface from itsinterface tables. The interface is unusable and may havebeen deleted via a new HOME list.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4957I timer_value second timer expired(reason)Explanation: Depending upon the timer_value andreason, one of the following actions is taken:Value Reason Action30 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 ActionmnSystem Action:rescan kernelfor interfacespoll interfacesfor statusEvery 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.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.RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4958INone.None.supply destination -> port via interfaceExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.212 z/VM: TCP/IP Messages and Codes

ROUTED MessagesDTCRTD4959IInterface interface upExplanation: The specified interface, which was notpreviously active, is now active. The interface mighthave been inactive or re-installed.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4961ENone.Correct the ETCIncorrect 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4962ENone.Correct the ETCIncorrect 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4963INone.Correct the ETC(no ETC GATEWAYS definitions)Explanation: The ETC GATEWAYS file does notcontain any definitions for configuring the routingtables on your host.System Action:TCPIP continues.User or Operator Response: Include appropriatedefinitions in the ETC GATEWAYS file for configuringthe routing tables on your host before starting RouteD.System Programmer Response:DTCRTD4964WNone.Incorrect metric, changing to oneExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.DTCRTD4965INone.Virtual interfaceCorrect the ETCExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD4972ENone.None.Incorrect type value: valueExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD4973E 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCChapter 14. ROUTED Messages 213

|||||||||||||||||||ROUTED MessagesDTCRTD4974IIssuing Kill Route MessagesExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD4975E Cannot establish communicationservices with the TCP/IP stackExplanation: The BEGINtcpIPservice routine failedwhen RouteD attempted to establish a connection tothe TCP/IP stack.System Action:RouteD 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.DTCRTD4976Emaxdesc returned errno: nnExplanation: The RouteD server encountered an errorfrommaxdesc()function.System Action:RouteD ends abnormally.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 shouldmatchExplanation:values.System Action:getdtablesize ()returneddifferentRouteD ends abnormally.User or Operator Response: Notify the systemprogrammer about the problem.System Programmer Response:support center.Contact your IBMDTCRTD6000E SMSG Command from user_id:commandExplanation: An SMSG command request wasreceived from the indicated user ID.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD6001E SMSG Command from user_id: usernot authorizedExplanation: 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.System Action:RouteD continues.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_idExplanation: The SMSG SHUTDOWN command wasreceived. The RouteD server will be immediatelyshutdown.System Action:User or Operator Response:RouteD ends normally.None.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 suppressedExplanation: 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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Check the ETCGATEWAYS file. If this is not the desired result offiltering, change the ETC GATEWAYS file and restartRouteD.214 z/VM: TCP/IP Messages and Codes

ROUTED MessagesDTCRTD8481W Unknown next hop address ipaddressfor route destination from router routerExplanation: An unknown next hop address ipaddresswas received in a RIP packet for a route to destinationfrom router. The route is ignored.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD8482I Address is experimental or hasnonzero portExplanation: 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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Identify the machineor user that generated the packet in question andcorrect the problem.DTCRTD8483WIncorrect internet addressExplanation: An internet address in an incoming routeis not a member of any defined internet address class.The route is discarded.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Locate the router thatoriginated the packet and correct the problem.DTCRTD8484WA ’must-be-zero’ field is nonzeroExplanation: An internet address in an incoming routecontains a nonzero value in a field which must be zero.The incoming route is discarded.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Locate the router thatoriginated the packet and correct the problem.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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Reconfigure the routerto use a correct port number and locate the applicationthat is generating the updates and correct the problem.DTCRTD8486EIncorrect 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD8487W 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 Action:RouteD continues.User or Operator Response:None.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.DTCRTD8488IOpening ROUTED CONFIG (config)Explanation: The specified ROUTED CONFIG file isbeing opened for processing.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD8485IResponse from non-router ipaddressExplanation: 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, andDTCRTD8489S Unknown keyword (keyword) inROUTED CONFIGExplanation: An unknown keyword was used in astatement in the ROUTED CONFIG. The statement isignored.Chapter 14. ROUTED Messages 215

ROUTED MessagesSystem Action:RouteD continues.User or Operator Response:System Programmer Response:CONFIG file.None.Correct the ROUTEDDTCRTD8490W 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 Action:RouteD continues.User or Operator Response:None.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 charactersExplanation: 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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Correct the ROUTEDCONFIG or ETC GATEWAYS file.DTCRTD8492S Ignore SOURCEVIPA option cannotbe enabled on the socketExplanation: 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.System Action:User or Operator Response:RouteD ends abnormally.System Programmer Response:Software Support Center.None.Contact your IBMDTCRTD8493I Interface interface skipped, supply issuppressedExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD8494I rip_control rip_version packets fromaddress_destination on interface interfacenot allowedExplanation: 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 Action:RouteD continues.User or Operator Response:None.System Programmer Response: Correct the ROUTEDCONFIG or ETC GATEWAYS file.DTCRTD8495I RIP2 packet from router router notauthorizedExplanation: 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.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.DTCRTD8496E Gateway address ’address’ not arouting interface in the networkExplanation: The indicated route, defined in RouteD’sETC GATEWAYS file, referenced an unknown routinginterface based upon the gateway address. The routedefinition is ignored.System Action:RouteD continues.User or Operator Response:None.System Programmer Response: Correct the ETCGATEWAYS file. Verify that the gateway address is216 z/VM: TCP/IP Messages and Codes

ROUTED Messagescorrect and a valid routing interface is defined.DTCRTD8497Ioption valueExplanation: The ROUTED CONFIG has been readand the option and its associated value are displayed.System Action:RouteD continues.User or Operator Response:System Programmer Response:None.None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:DTCRTD8499ENone.None.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.System Action:RouteD continues.User or Operator Response:System Programmer Response:GATEWAYS file.None.Correct the ETCDTCRTD8501W VARSUBNETTING parameter notspecified, resetting RIP SUPPLYCONTROL: RIP1Explanation: 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 Action:RouteD continues.User or Operator Response:None.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 Action:RouteD ends abnormally.User or Operator Response: Notify the systemprogrammer about the problem.System Programmer Response: Verify which dynamicrouter you wish to run and have only this one runningwith the stack.DTCRTD8500E Config error: The RouteD servervirtual machine is not defined in theOBEY listExplanation: 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 Action:User or Operator Response:RouteD ends abnormally.None.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.Chapter 14. ROUTED Messages 217

ROUTED Messages218 z/VM: TCP/IP Messages and Codes

Chapter 15. Site Table Configuration MessagesTESTSITE MessagesThis section contains TESTSITE messages.No gateway named gatewaySeverity: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:Procedure Name:No host named hostSeverity:Error.CMTSITE PASCALDoItExplanation: There are no HOST 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:Procedure Name:No net named netSeverity:Error.CMTSITE PASCALDoItExplanation: There are no NET 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:Procedure Name:CMTSITE PASCALDoItMAKESITE MessagesThis section contains the MAKESITE messages.Address hash table overflow on hostSeverity: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:Procedure Name:CMMAKSI PASCALInsertLine LineNumber: bad address syntaxSeverity: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.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALGetAddress© Copyright IBM Corp. 1987, 2002 219

MAKESITE MessagesLine LineNumber: hash table overflowSeverity: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.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:Procedure Name:CMMAKSI PASCALLookUpLine LineNumber: no address specifiedSeverity:Error.Explanation: The listed line number in the input filedid not contain one valid address.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineLine LineNumber: no name fieldSeverity:Error.Explanation: The listed line number in the input filedid not contain a name field.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:DTCMAK52IDTCMAK53IDTCMAK54IDTCMAK58ESeverity:Error.CMMAKSI PASCALParseLineSize of SITE table exceeds thecapacity of MAKESITE.Maximum size of SITE table: Computed SITE table size: MAKESITE TerminatingAbnormallyExplanation: These messages are issued as a group.This indicates that the HOSTS LOCAL file containedtoo many sitenames.xxxyyySystem Action:code of 255.Maximum size allowed for SITE tableComputed size of SITE tableMAKESITE terminates with a returnSystem 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.Source File:CMMAKSI PASCALDTCMAK55I Size of ADDR table exceeds thecapacity of MAKESITE.DTCMAK56I Maximum size of ADDR table:DTCMAK57I Computed ADDR table size: DTCMAK58E MAKESITE Terminating AbnormallySeverity:Error.Explanation: These messages are issued as a group;they indicate that the HOSTS LOCAL file contained toomany internet addresses.xxxyyySystem Action:code of 255.Maximum size allowed for ADDR tableComputed size of ADDR tableMAKESITE terminates with a returnSystem 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.Source File:CMMAKSI PASCALLine LineNumber: no type specifiedSeverity:Error.Explanation: The listed line number in the input filehad a null type field.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineDTCMAK59E 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 you220 z/VM: TCP/IP Messages and Codes

MAKESITE Messagesspecified a valid file mode, but one that is accessedread-only.System Action:code 255.MAKESITE terminates with a returnUser or Operator Response: Specify a valid keywordor a read-write file mode as a parameter on theMAKESITE command.Source File:Procedure Name:CMMAKSI PASCALStartUpDTCMAK60E 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:code 255.MAKESITE terminates with a returnUser or Operator Response: Correct the problemdescribed by the return and reason code and retry thecommand.Source File:Procedure Name:CMMAKSI PASCALStartUpLine LineNumber: only Fields fieldsSeverity:Error.Explanation: The number of listed field terminatorswas less than the required minimum of three for thelisted line number in the input file.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineLine LineNumber: unknown type BadTypeSeverity:Error.Explanation: The listed line number in the input filewas not null and did not contain HOST, GATEWAY, orNET in the type field.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified on the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineUnable to read HOSTS LOCAL *.Severity:Error.Explanation: TCP/IP could not find the HOSTSLOCAL file on any of the accessed minidisks.System Action:message.The program halts after displaying theUser or Operator Response: Rerun MAKESITE afteryou ensure that access to the HOSTS LOCAL file isavailable.Source File:Procedure Name:CMMAKSI PASCALStartUpWarning: 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.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified in the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineWarning: 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.System Action: The program continues afterdisplaying this message.User or Operator Response: Correct the problemidentified in the listed line and continue.Source File:Procedure Name:CMMAKSI PASCALParseLineWarning: line LineNumber truncated to MAXlinecharactersSeverity:Warning.Explanation: A line has been truncated because it islonger than the MaxLine constant. Comments areignored when determining the length of a line.Chapter 15. Site Table Configuration Messages 221

MAKESITE MessagesSystem Action: The program continues afterdisplaying this message.User or Operator Response: If this truncationcondition is unacceptable, correct the problem beforecontinuing.Source File:Procedure Name:CMMAKSI PASCALGetLineWarning name lost: NameSeverity: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.System Action: The program continues afterdisplaying this message.User or Operator Response: Determine the cause ofthe problem; correct it, if necessary, and continue.Source File:Procedure Name:CMMAKSI PASCALProcessAdr**** Fatal error: MakeSite abortedSeverity: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:message.The program halts after displaying theUser or Operator Response: Correct the problemidentified in the listed line and continue. If the problempersists, contact the IBM Support Center.Source File:Procedure Name:CMMAKSI PASCALLookUpWarning name lost: NameSeverity: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.System Action: The program continues afterdisplaying this message.User or Operator Response: Determine the cause ofthe problem; correct it, if necessary, and continue.Source File:Procedure Name:CMMAKSI PASCALMergeNamesWarning: Name1 agrees with Name2 in the firstCMSwordLIMIT charactersSeverity: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.System Action: The program continues afterdisplaying this message.User or Operator Response: If this condition isunacceptable, correct the problem before continuing.Source File:Procedure Name:CMMAKSI PASCALLookUp222 z/VM: TCP/IP Messages and Codes

Chapter 16. SMTP MessagesThis chapter contains Simple Mail Transfer Protocol (SMTP) messages, SMTP replycode messages, and SMTPRSCS messages.||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1028ESeverity:Error.This section contains the numbered SMTP Server Messages.Invalid FileName SpecificationExplanation: 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:Procedure Name:DTCSMT1029ESeverity:Error.SMTP PASCALErrorInvalid FileType SpecificationExplanation: You entered a file type 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:Procedure Name:DTCSMT1030ESeverity:Error.SMTP PASCALErrorInvalid FileMode SpecificationExplanation: You entered a file mode containing morethan 2 characters.System Action:SMTP halts.System Programmer Response: Correct the file modeso that it is less than two characters, and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1031I Unable to find input file: FileNameFileType FileModeSeverity: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 Action:SMTP halts.System Programmer Response: Verify that SMTP hasaccess to the specified file before restarting SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1032E Unrecognized option inconfiguration file: BadOptionSeverity: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 Action:SMTP halts.System Programmer Response: Correct the erroneousentry in the configuration file and try again.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1033E Invalid LOG file destination:BadDestinationSeverity:Error.Explanation: You specified an invalid destination forthe LOG option in the configuration file. The onlydestinations are DISK and SPOOL.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError© Copyright IBM Corp. 1987, 2002 223

||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1034E Invalid Address in Restricted List:BadAddressSeverity:Error.Explanation: SMTP found an invalid address in theRESTRICT list. Addresses must be in the formuserid@nodeid, with the asterisk character (*)representing wildcards.System Action:SMTP halts.System Programmer Response: Correct the erroneousentry in the configuration file and try again.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1035E Invalid Local Delivery Format:BadFormatSeverity:Error.Explanation: You specified an invalid delivery formatfor the LOCALFORMAT option in the configurationfile. The only valid delivery formats are NETDATA andPUNCH.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1036E Invalid Rscs Delivery Format:BadFormatSeverity:Error.Explanation: You specified an invalid option for theRSCSFORMAT option in the configuration file. Theonly valid choices for this option are NETDATA orPUNCH.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTPPASCALErrorDTCSMT1037E Invalid Disposition in Restrictcommand: BadCommandSeverity:Error.Explanation: The disposition specified with theRESTRICT option is not valid. Use only the validoptions of PURGE, RETURN, and TRANSFERTO withthe RESTRICT option.System Action:SMTP halts.|||||||||||||||||||||||||||||||||||||||||||||||System Programmer Response: Correct the erroneousentry in the configuration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1038E Invalid Address for Mailer:BadAddressSeverity: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 Action:SMTP halts.System Programmer Response: Correct the erroneousentry in the configuration file and restart SMTP.Source File:Procedure Name:DTCSMT1039ESeverity:Error.SMTP PASCALErrorInvalid Max Mail Bytes: BadParameterExplanation: The number_of_bytes parameter for theMAXMAILBYTES option is incorrect. It must be apositive integer value between 1 and 2 147 483 647.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:DTCSMT1040ESeverity:Error.SMTP PASCALErrorInvalid PostMaster Address: addressExplanation: The address specified on thePOSTMASTER configuration file statement is not valid.Additional messages will be given to indicate why theaddress is not valid.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:DTCSMT1041ESeverity:Error.SMTP PASCALErrorInvalid BadSpoolFileId Userid: useridExplanation: 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.224 z/VM: TCP/IP Messages and Codes

|||||System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError||||||DTCSMT1071ISeverity:SMTP Server Numbered MessagesError.Unknown Command: commandExplanation: The server received an unidentifiablecommand, which is listed at the end of the message.The allowable or known commands are:||||||||||||||||||||||||||||||||||||||||||DTCSMT1043E Invalid Transfer To Userid:BadUserIDSeverity:Error.Explanation: You specified a user ID that does notexist for the RESTRICT TRANSFERTO statement in theconfiguration file.System Action:SMTP halts.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.Source File:Procedure Name:DTCSMT1044ESeverity:Error.SMTP PASCALErrorInvalid Mailer Option: BadOptionExplanation: 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1050I Compiled-in. Unable to load:TranslateTableName TCPXLBIN *Severity:Informational.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.Source File:SMTP PASCAL||||||||||||||||||||||||||||||||||||||||DATA NOOP SENDEHLO QUEU SOMLEXPN QUIT TICKHELP RCPT TURNHELO RSET VERBMAIL SAML VRFYSystem Programmer Response: The sender mustcorrect the syntax before resubmitting the command. Ifnecessary, the user can request online help by enteringHELP.System Action:Source File:Procedure Name:SMTP continues.SMTPCMDS PASCALNoSuchCommandDTCSMT1093E Invalid numeric operand found:operandSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:DTCSMT1094ESeverity:Error.SMTP PASCALErrorInvalid ServerPort specified: portExplanation: An invalid port number was specified onthe PORT configuration file statement. The port mustbe a number in the range of 1 through 65535.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError|Procedure Name:LoadTranslateTableChapter 16. SMTP Messages 225

||||||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1097ISeverity:Error.NonExistent: ReturnCodeExplanation: 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 Action:SMTP continues.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:Procedure Name:DTCSMT1098ISeverity:SMTPEVNT PASCALWarning.CloseCompletedEventStoreData: entering ″discard″ modeExplanation: 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 Action:SMTP continues.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.Source File:Procedure Name:DTCSMT1099ISeverity:SMTPEVNT PASCALWarning.StoreDataStoreData: leaving ″discard″ modeExplanation: 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 Action:SMTP continues.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.Source File:Procedure Name:SMTPEVNT PASCALStoreDataDTCSMT1115E Invalid Rewrite822Header Option:BadOptionSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1116E Option Conflict: SECURE andRESTRICT may not both be specifiedSeverity:Error.Explanation: You cannot use the options SECURE andRESTRICT together because they are incompatible.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:DTCSMT1117ESeverity:Error.SMTP PASCALErrorInvalid DBCS Option: optionExplanation: An invalid option has been specified inthe SMTP CONFIG file for the DBCS statement.System Action:SMTP halts.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.Source File:Procedure Name:DTCSMT1118ESeverity:Error.SMTP PASCALErrorInvalid Kanji shift-in Option: optionExplanation: An invalid shift-in option has beenspecified in the SMTP CONFIG file for the DBCSstatement. The valid shift-in options for the JIS78KJ and226 z/VM: TCP/IP Messages and Codes

SMTP Server Numbered Messages|||||||JIS83KJ conversion types are ASCII and JISROMAN.System Action:SMTP halts.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.|||||||RFC 821. VM SMTP accepts the reply and truncates itto 512 bytes.System Action:SMTP continues.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:SMTP PASCAL|Source File:SMTPRPLY PASCAL|Procedure Name:Error|Procedure Name:DoReply|||DTCSMT1119E Too Many ALTTCPHOSTNAMEstatements - limit is MaxAltOurNames|||DTCSMT1161E Invalid value InactivityTimeOutspecified for Inactive. Default used.|Severity:Error.|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.||||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 halts.System Programmer Response: Reduce the number ofALTTCPHOSTNAME statements in the configurationfile and restart SMTP, or increase the parameterMaxAltOurNames to the desired number.|||||System Action:of 180 seconds.SMTP continues and uses the defaultSystem Programmer Response: If the defaultinactivity timeout is not appropriate, correct theconfiguration file and restart SMTP.|Source File:SMTP PASCAL|Source File:SMTP PASCAL|Procedure Name:Error|Procedure Name:DoInactiveState|||DTCSMT1134I Protocol Error. I= I Bytes Received =BytesReceived|||DTCSMT1162E Invalid value FinishOpenTimeOutspecified for FinishOpen. Default used.|Severity:Error.|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,·, followed by additional data. Thestring, ·, 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 ·.System Action:SMTP continues.System Programmer Response: Describe the problemto the postmaster of the SMTP server that is sendingthe incorrectly formatted mail.Source File:Procedure Name:DTCSMT1135ISeverity:SMTPEVNT PASCALWarning.StoreDataTableErrorsReply Line too longExplanation: SMTP sends this message to the serverconsole to indicate that a remote SMTP server’sresponse exceeded the 512-byte limitation specified by|||||||||||||||||||||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:of 120 seconds.SMTP continues and uses the defaultSystem Programmer Response: If the default finishopen timeout is not appropriate, correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALProcessConfigFileDTCSMT1163E 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:of 3 days.SMTP continues and uses the defaultChapter 16. SMTP Messages 227

|||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesSystem Programmer Response: If the default retry ageis not appropriate, correct the configuration file andrestart SMTP.Source File:Procedure Name:SMTP PASCALDoRetryIntervalDTCSMT1164E 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:of 20 minutes.SMTP continues and uses the defaultSystem Programmer Response: If the default retryinterval is not appropriate, correct the configuration fileand restart SMTP.Source File:Procedure Name:SMTP PASCALDoRetryIntStateDTCSMT1165E 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:of 20 minutes.SMTP continues and uses the defaultSystem Programmer Response: If the default resolverretry interval is not appropriate, correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALDoResolRetryIntDTCSMT1166E 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:60.SMTP continues and uses a default ofSystem Programmer Response: Correct the SMTPCONFIG file or TCPIP DATA file.Source File:Procedure Name:SMTP PASCALProcessConfigFile|||||||||||||||||||||||||||||||||||||||||||||||||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:of 0 retries.SMTP continues and uses the defaultSystem Programmer Response: If the defaulttemporary error retry value is not appropriate, correctthe configuration file and restart SMTP.Source File:Procedure Name:SMTP PASCALProcessConfigFileDTCSMT1168E RcpResponseDelay value is ignoredif name servers are not used for nameresolutionSeverity: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 Action:SMTP continues.System Programmer Response: Remove theRCPTRESPONSEDELAY statement from the SMTPconfiguration file if you are not planning to use a hostdomain name server.Source File:Procedure Name:SMTP PASCALDoRcptResponseStateDTCSMT1170E 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError228 z/VM: TCP/IP Messages and Codes

||||||||||||||||||||||||||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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1172E 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError||||||||||||||||||||||||||System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1175E 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1176E Invalid value RcptResponseDelayspecified for RcptResponseDelay.Severity:SMTP Server Numbered MessagesError.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.|||||||||||||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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALError|||||||||||||System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1177E 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.|||||||||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.System Action:SMTP halts.|||||||System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorChapter 16. SMTP Messages 229

||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1178E 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1179E Invalid VERIFYCLIENT option:optionSeverity:Error.Explanation: An invalid option was specified on theVERIFYCLIENT configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe VERIFYCLIENT statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1180E Invalid VERIFYCLIENTDELAYoption: delaySeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1191E Invalid FORWARDMAIL option:optionSeverity:Error.Explanation: An invalid option was specified on theFORWARDMAIL configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe FORWARDMAIL statement.System Action:SMTP halts.|||||||||||||||||||||||||||||||||||||||||||||||System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:DTCSMT1192ESeverity:Error.SMTP PASCALErrorInvalid SMTPCMDS option: optionExplanation: An invalid option was specified on theSMTPCMDS configuration file statement. See TCP/IPPlanning and Customization for valid options for theSMTPCMDS statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:DTCSMT1193ESeverity:Error.SMTP PASCALErrorInvalid TRACE option: optionExplanation: An invalid option was specified on theTRACE configuration file statement. See TCP/IPPlanning and Customization for valid options for theTRACE statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1195E Invalid SOURCEROUTES option :optionSeverity:Error.Explanation: An invalid option was specified on theSOURCEROUTES configuration file statement. SeeTCP/IP Planning and Customization for valid options forthe SOURCEROUTES statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1196E Invalid filename for 8-bit MIMESupport: FileNameSeverity:Error.Explanation: On the 8BITMIME statement in theconfiguration file, you specified an invalid file name.230 z/VM: TCP/IP Messages and Codes

SMTP Server Numbered Messages||||||||||||||||||||The name may be longer than 8 characters or it maycontain invalid characters.System Action:SMTP halts.System Programmer Response: Correct the SMTPconfiguration file so that the file name specified on the8BITMIME statement is a valid file name, and restartSMTP.Source File:Procedure Name:SMTP PASCALDoMimeSupport, ErrorDTCSMT1197E 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 Action:SMTP halts.System Programmer Response: Verify that this fileexists. Correct the SMTP configuration file, specifyingthe correct file name, and restart SMTP.||||||||||||||||||||Procedure Name:InitializeDeliveryQueueDTCSMT1202E Terminating: GATEWAY specifiedbut SMTPRSCS HOSTINFO file cannotbe foundSeverity: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.Source File:Procedure Name:SMTP PASCALInitializeRSCSTableDTCSMT1204E Terminating: Unable to properlyestablish UDP connection forNameserver queriesSeverity:Error.||||||||||Source File:Procedure Name:SMTP PASCALDoMimeSupportDTCSMT1198E 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 Action:SMTP halts.||||||||||Explanation: The server was unable to completeinitialization because it could not establish a workingUDP connection for use during Nameserver queries.System Action:SMTP terminates.System Programmer Response:server.Source File:Procedure Name:DTCSMT1205ISMTP PASCALMainLoopRestart the SMTPTerminating: CP EXT received|||||||||||||||||System Programmer Response: Verify that this file isa translation table. Correct the SMTP configuration file,specifying a valid translation table, and restart SMTP.Source File:Procedure Name:DTCSMT1201ESeverity:Error.SMTP PASCALDoMimeSupportTerminating: Disk ’A’ is read onlyExplanation: 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 Action:SMTP halts.System Programmer Response: Access the SMTP Aminidisk in read/write mode, and restart SMTP.Source File:SMTP PASCAL||||||||||||||||Severity:InformationalExplanation: SMTP terminates because an externalinterrupt was received.System Action:SMTP terminates.System Programmer Response:Source File:Procedure Name:DTCSMT1206ESeverity:Explanation:Error.System Action:SMTP PASCALNone.HandleTCPIPEventNotificationProcedure Terminating: reasonSMTP terminates for the specified reason.SMTP halts.System Programmer Response: Use the specifiedreason to determine why the SMTP server shut down. Ifneeded, contact your IBM Support Center forassistance.Chapter 16. SMTP Messages 231

||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesSource File:Procedure Name:DTCSMT1207ESeverity:Error.SMTPUTIL PASCALCheckResultProcedure SMTP bug: reasonExplanation: A software error has occurred in theSMTP server. The reason should not occur in SMTPprocessing.System Action:SMTP continues.System Programmer Response: Use the specifiedreason to determine what error occurred. Contact yourIBM Support Center for assistance.Source File:Procedure Name:SMTPUTIL PASCALCheckResultDTCSMT1208E Local Error in MakeAddrBlok RC =ReturnCodeSeverity:Error.Explanation: SMTP did not have enough free diskspace on its A-disk to store an ADDRBLOK file.System Action:SMTP continues.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.Source File:Procedure Name:SMTPEVNT PASCALStoreDataDTCSMT1210E FileName ADDRFILE is in aninconsistent state...repairingSeverity: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 Action:SMTP continues.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:Procedure Name:SMTPQUEU PASCALEnQueueForDelivery||||||||||||||||||||||||||||||||||||||||||||||DTCSMT1211E Delivery of Note AddrFile.fscbfn toAddrString failed RC = ReturnCodeSeverity: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 Action:SMTP continues.System Programmer Response: Determine the reasonfor this failure, correct it, and try again.Source File:Procedure Name:SMTPQUEU PASCALDeliverSpoolFileDTCSMT1214E Invalid IPMailer Address Specified:IPaddressSeverity: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.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1215E IPMAILERADDRESS statementconflicts with MAILER UNKNOWNstatementSeverity:ErrorExplanation: The MAILER UNKNOWN statement inyour SMTP configuration file is incompatible with theIPMAILERADDRESS statement.System Action: The SMTP server is halted until theproblem is corrected.System Programmer Response: Remove theUNKNOWN parameter from the MAILER statement.For details, see the TCP/IP Planning and Customization.Source File:Procedure Name:SMTP PASCALError|||232 z/VM: TCP/IP Messages and Codes

||||DTCSMT1220E *SPL Error Reading Data. Spool File:Spoolid transferred to BadSpoolFileIDSeverity:Error.||||SMTP Server Numbered MessagesSystem 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.||||||||||||||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:Procedure Name:SMTPINTR PASCALTransferSpoolDTCSMT1221E An unexpected Sever was receivedfrom *SPL.Severity:Error.||||||||||||||Source File:Procedure Name:SMTP PASCALMainloopDTCSMT1224E HNDIUCV SET failed with RC =ReturnCode, IUCV functions cannot beperformedSeverity:Error.Explanation: SMTP encountered an error whileattempting to issue the HNDIUCV SET macro.System Action:SMTP terminates.System Programmer Response: Identify the problemwith the HNDIUCV SET by looking up the return code.Correct the problem with HNDIUCV SET and restartthe server.||||||||||||||||||||||||||||||Explanation: SMTP encountered an unexpected Severfrom the *SPL system serviceSystem 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.Source File:Procedure Name:SMTPINTR PASCALRetrySpoolDTCSMT1222E Error detected during CMSIUCVConnect to *SPL, RC = Return CodeSeverity: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:Procedure Name:SMTPBTCH PASCALServRdrDisableDTCSMT1223E Initial CMSIUCV Connect to *SPLfailed, RC = Return CodeSeverity:Error.Explanation: SMTP encountered an error during theinitial Connect to the *SPL system service.System Action:SMTP terminates.||||||||||||||||||||||||||||||||Source File:Procedure Name:SMTP PASCALMainloopDTCSMT1225E Unreadable spool file: Spoolidtransferred to BadSpoolFileIDSeverity:Error.Explanation: The format of the spool file read fromthe reader is invalid, the spool file is unreadableSystem Action: SMTP continues but the spool fileprocessing terminates abnormally.System Programmer Response:Source File:Procedure Name:SMTPBTCH PASCALNoneHandleSPLPathWorkDTCSMT1226E Disk Almost Full. Spool File: Spoolidplaced in HOLD statusSeverity: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 orChapter 16. SMTP Messages 233

|||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered Messagesany mail files that you want delivered. Spool filesplaced in user hold status must be manually changedback to nohold status before they will be processed.Source File:Procedure Name:SMTPBTCH PASCALHandleSPLPathWorkDTCSMT1227E Null Spool File: Spoolid RC=ReturnCode transferred to: PostMasterIdSeverity: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 Action: SMTP continues but the spool fileprocessing terminates abnormally.System Programmer Response: Determine the originof the null spool file and correct the problem.Source File:Procedure Name:SMTPBTCH PASCALHandleSPLPathWorkDTCSMT1228E *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 Action: SMTP continues but the spool fileprocessing terminates abnormally.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.Source File:Procedure Name:SMTPINTR PASCALTransferSpoolDTCSMT1233E Unexpected return from user exitfilename filetype, RC=rcSeverity:Error.Explanation: The SMTP server received an unknownreturn code from the specified user exit.System Action:SMTP continues.System Programmer Response: Determine why theuser exit gave SMTP the unknown return code.Source File:PASCALSMTPCMDS, SMTPQUEU, SMTPRESProcedure 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.System Programmer Response:Source File:Procedure Name:SMTPUTIL PASCALCheckDiskFullNone.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 Action:SMTP halts.System Programmer Response: Re-ipl with the correctlevel of CMS and restart the SMTP server.Source File:SMTP PASCALProcedure Name: DoMimeSupport,LoadTranslateTableDTCSMT1241E Callable service routine DTCXLATEfailed with RC = rc, Reason = rscSeverity:Error.Explanation: An error occurred when the SMTP servertried to use the DTCXLATE CSL routine to load atranslate table.System Action:SMTP halts.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.Source File:Procedure Name:SMTP PASCALDoMimeSupport234 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||||||DTCSMT1243E Too many IP addresses configuredfor IPMAILERADDRESS statement. IPaddress address will not be usedSeverity:Error.Explanation: Only 16 IP addresses can be used on theIPMAILERADRESS statement. The specified address isignored.System Action:SMTP continues.System Programmer Response:Source File:Procedure Name:SMTP PASCALNone.DoIPMailerListStateDTCSMT1244E 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 Action:Server initialization stops.System Programmer Response: Correct theconfiguration file statement and restart the SMTPserver.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1245E 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 Action:Server initialization stops.System Programmer Response: Correct theconfiguration file statement and restart the SMTPserver.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1248E MAILER statement specifies anIMAP virtual machine that is not on thelocal RSCS nodeSeverity: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 Action: The SMTP server is halted until theproblem is corrected.System Programmer Response: Correct the problemin the SMTP configuration file and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1249E Invalid Address in SMSGAuthorization List: addressSeverity:Error.Explanation: The specified address is not valid for theSMSGAUTHLIST configuration file statement. Theaddress is a local address, but it is longer than 8characters.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1250E Disk Full Action Percent must be inthe range: -100..0..100 but found: percentSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1251E Duplicate Disk Full Action PercentSpecified: percentSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:SMTP Server Numbered MessagesSMTP PASCALErrorChapter 16. SMTP Messages 235

|||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1253E Expecting ’BEGIN’ or’ENDACTIONS’ but found: tokenSeverity:Error.Explanation: The specified token was found where a’BEGIN’ or ’ENDACTIONS’ token should be whileparsing the ONDISKFULL configuration file statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:Procedure Name:SMTP PASCALErrorDTCSMT1254E OnDiskFull Action must be less thanchars characters longSeverity:Error.Explanation: An action listed on the ONDISKFULLconfiguration file statement is too long. The action mustbe less than chars characters long.System Action:SMTP halts.System Programmer Response: Correct theconfiguartion file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1255E OnDiskFull Action must be a CPcommand not: action|||||||||||||||||||||||||||Source File:SMTPProcedure Name:ErrorDTCSMT1257E LOOPINGMAIL statement no longervalid. Please use the BADSPOOLFILEIDstatementSeverity:Error.Explanation: LOOPINGMAIL is no longer a validSMTP configuration file statement. Instead, you shoulduse the BADSPOOLFILEID statement.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1258E Only one POSTMASTER statementmay be specified in SECURE modeSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file and restart SMTP.|Severity:Error.|Source File:SMTP||||||||||||||||Explanation: The action specified on theONDISKFULL configuration file statement did notbegin with ’CP’. ONDISKFULL actions must be a CPcommand.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1256E Invalid Disk Full Action PercentSpecified: percentSeverity: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.||||||||||||||||Procedure Name:ErrorDTCSMT1259E Invalid POSTMASTER address:addressSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:Error|||System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.||236 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||||||DTCSMT1260E In SECURE mode, POSTMASTERaddress must be a valid local useridSeverity: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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1261E Expecting ’PRINT’ or ’NOPRINT’after ’REWRITE822HEADER YES’statementSeverity:Error.Explanation: A REWRITE822HEADER YESconfiguration file statement was not followed by the’PRINT’ or ’NOPRINT’ option.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1262E 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.System Action:SMTP halts.System Programmer Response: Correct theconfiguration file statement and restart SMTP.Source File:SMTPProcedure Name:ErrorDTCSMT1300I Deleting Spool File fromundetermined originSeverity: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 Action:SMTP continues.System Programmer Response: Determine why SMTPis receiving RSCS files without an RSCS TagUserid orTagNodeid, and correct the problem.Source File:Procedure Name:SMTPBTCH PASCALMakeBatchSMTPErrorFileDTCSMT1301I Deleting Spool File from UserID atNodeIDSeverity: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 Action:SMTP continues.System Programmer Response: Determine the originof the mail. Normally this message can be ignored.Source File:Procedure Name:SMTPBTCH PASCALMakeBatchSMTPErrorFileDTCSMT1302I Rejecting Spool File Spoolid FromUserID at NodeIDSeverity: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.System Action:SMTP continues.System Programmer Response:Source File:Procedure Name:DTCSMT1302ISeverity:Error.SMTPINTR PASCALNone.HandleRestrictedFileRejecting command line too longExplanation: The argument string supplied after acommand keyword exceeds the maximum allowableargument string length of 512 characters.System Action:SMTP continues.System Programmer Response: If the problempersists, determine what host is sending the badcommand line, and correct the SMTP server.Source File:Procedure Name:SMTP Server Numbered MessagesSMTPCMDS PASCALDoCommandChapter 16. SMTP Messages 237

||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT1303I Restricting Spool File Spoolid FromUserID at NodeIDSeverity: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.System Action:SMTP continues.System Programmer Response:Source File:Procedure Name:SMTPINTR PASCALNone.HandleRestrictedFileDTCSMT1308I Unregistered BSMTP Spool File fromUserID@NodeIDSeverity: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 Action:SMTP continues.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.Source File:Procedure Name:SMTPCMDS PASCALDoMailDTCSMT1309I Unregistered BSMTP MAIL FROM:PrintPath||||||||||||||||||||||||||||||||DTCSMT1310ISeverity:Warning.Unregistered RCPT TO: mailboxExplanation: This message is output to the SMTPbatch log to indicate that the specified address is not aregistered secure gateway user.System Action:SMTP continues.System Programmer Response: Update the SMTPSECTABLE security table, as required.Source File:Procedure Name:SMTPRES PASCALProcessLocalDTCSMT1314E 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.System Action:SMTP halts.System Programmer Response:Support Center for assistance.Source File:SMTPProcedure Name:CheckHardenedMailContact your IBMDTCSMT1317I Looping mail xxxxnnnn NOTEFILEand ADDRFILE are renamed toxxxxnnnn LOOPMAIL and LOOPADDR|Severity:Warning.|Severity:Informational.||||||||||||||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 Action:SMTP continues.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.Source File:Procedure Name:SMTPCMDS PASCALDoMail||||||||||||||||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 Action:SMTP continues.System Programmer Response: Examine the xxxxnnnnLOOPMAIL file to determine the reason for the loopingmail.Source File:Procedure Name:SMTPEVNT PASCALStoreData238 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||||||||||||||||||||||||||DTCSMT1318I Looping mail xxxxnnnn NOTEFILEand ADDRFILE process (or renamefunction) failed with return code of rcSeverity:Informational.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 Action:SMTP continues.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.Source File:Procedure Name:SMTPEVNT PASCALStoreDataDTCSMT1511I Date Time #Connection_numberDBCSEtoA Conversion ErrorSeverity:Informational.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, formoreinformation about DBCS support in SMTP.Source File:Procedure Name:SMTPRPLY PASCALResumeFillingDataBufferDTCSMT1512E DBCS conversion specified, but noDBCS tables could be loadedSeverity: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.Source File:Procedure Name:SMTP PASCALOpenOutputStreamsDTCSMT1513I Date Time #Connection_numberDBCSAtoE Conversion ErrorSeverity:Informational.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, formoreinformation about DBCS support in SMTP.Source File:Procedure Name:SMTPEVNT PASCALDoDbcsConversionDTCSMT2001E 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 Action:SMTP continues.System Programmer Response: Correct the problemsin the security table file and restart SMTP.Source File:Procedure Name:SMTP Server Numbered MessagesSMTPSEC PASCALSecurityTableErrorsChapter 16. SMTP Messages 239

|||||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Numbered MessagesDTCSMT2003ISeverity:Error.Expecting NodeId but found none.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 Action:SMTP continues.System Programmer Response: Correct the SMTPSECTABLE security table and restart SMTP.Source File:Procedure Name:SMTPSEC PASCALSecurityTableErrorsDTCSMT2004I Primary_NickName mapping must be’Y’ or ’N’ but found: TokenStrPrimary_MBox mapping must be ’Y’ or’N’ but found: BadInputSeverity:Error.Explanation: SMTP found a character string otherthanYorNforthePrimary_NickName or Primary_MBoxfields in the SMTP SECTABLE security file. Only thecharacters, Y and N, are valid.System Action:SMTP continues.System Programmer Response: Correct the SMTPSECTABLE security file, and restart SMTP.Source File:Procedure Name:SMTPSEC PASCALSecurityTableErrorsDTCSMT2008I Unexpected characters found afternicknameSeverity:Error.Explanation: SMTP found unexpected characters afteran entry in the SMTP SECTABLE security table.System Action:SMTP continues.System Programmer Response: Remove the extracharacters from the SMTP SECTABLE security table, ormark the characters as a comment with the asterisk (*)character.Source File:Procedure Name:SMTPSEC PASCALSecurityTableErrorsDTCSMT2009I 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 Action:SMTP continues.System Programmer Response: Correct the specifiednickname entries in the SMTP SECTABLE file, andrestart SMTP.Source File:Procedure Name:SMTPSEC PASCALSecurityTableErrorsDTCSMT2013I Special characters not allowed innicknameSeverity: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 Action:SMTP continues.System Programmer Response: Correct the specifiednickname in the SMTP SECTABLE security table, sothat it does not contain any special characters.Source File:Procedure Name:SMTPSEC PASCALSecurityTableErrorsDTCSMT2015E 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.System Action:SMTP halts.System Programmer Response: Correct the SMTPSECTABLE security table and restart SMTP.Source File:Procedure Name:SMTPSEC PASCALCheckSecurityTableDTCSMT2016E 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.240 z/VM: TCP/IP Messages and Codes

||||||||||||||||||||||||||||||||||||||||||||||||||System Action:SMTP halts.System Programmer Response: Correct the SMTPSECTABLE security table and restart SMTP.Source File:Procedure Name:SMTPSEC PASCALCheckSecurityTableDTCSMT2017E 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 Action:SMTP halts.System Programmer Response: Correct the specifiederrors in the SMTP SECTABLE file and restart SMTP.SMTP Server Unnumbered MessagesDBCS Conversion: conversion_statusSeverity:Informational.This section contains unnumbered SMTP messages. The headers will not appearhere as they would not appear when issued.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.Source File:Procedure Name:SMTP PASCALOpenOutputStreams8-bit MIME Support: YES (FileName TCPXLBIN *) |NOSeverity:Informational.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.System Action:SMTP continues.SMTP Server Numbered Messages| Source File: SMTPSEC PASCAL| Procedure Name: CheckSecurityTable|| DTCSMT2018E Fatal Error: Unable to find SMTP||SECTABLE but SECURE option wasspecified.| Severity: Fatal.| Explanation: The SECURE option was specified in the|||SMTP CONFIG configuration file, but the SMTPprogram did not have access to the SMTP SECTABLEfile.| System Action: SMTP halts.| System Programmer Response: Ensure that a valid| SMTP SECTABLE file is accessed and restart SMTP.| Source File: SMTPSEC PASCAL| Procedure Name: ReadSecurityTable| System Programmer Response: None.| Source File: SMTP PASCAL| Procedure Name: OpenOutputStreams|| Error in SMTP NAMES file:| Severity: Error.| Explanation: This message indicates a problem with||the SMTP NAMES file. Additional error messagesshould follow to further explain the error.| System Action: SMTP continues.| System Programmer Response: Use the||accompanying error messages to determine theproblem.| Source File: SMTPARSE PASCAL| Procedure Name: ReplySyntaxError|| IP Mailer Address : IPaddress| Severity: Informational.| Explanation: This message specifies the current IP|||address for the IPMAILERADDRESS statement in theSMTP configuration file. If only the MAILER statementis used, the IP address is shown as ″Disabled.″| System Action: SMTP continues.| System Programmer Response: None.| Source File: SMTP PASCAL| Procedure Name: OpenOutputStreamsChapter 16. SMTP Messages 241

|||||||||||||||||||||||||||||||||||||||||||||||SMTP Server Unnumbered MessagesLooping Mail Transferred to LoopingMailIdSeverity: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 Action:SMTP continues.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.Source File:Procedure Name:SMTPBTCH PASCALMakeBatchSMTPErrorFileNickname: Nickname Address: AddressSeverity: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 Action:SMTP continues.System Programmer Response: Correct the erroneousentry in the SMTP NAMES file before you try again.Source File:Procedure Name:SMTPNAME PASCALValidateAddressRcpt to unknown host: hostSeverity: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 Action:SMTP continues.System Programmer Response: If the host nameexists, check the domain name server or site tables forconfiguration errors, and resend the mail message.Source File:Procedure Name:SecRecordSeverity:Error.SMTPRES PASCALProcessRQR|||||||||||||||||||||||||||||||||||||||||||||System Action:SMTP continues.System Programmer Response:Source File:Procedure Name:SMTPSEC PASCALNone.SecurityTableErrorsSyntax Error: args after strcmd command: CommandLineSeverity: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 Action:SMTP continues.System Programmer Response: The sender mustcorrect the syntax before resubmitting the command, orissue the HELP command.Source File:Procedure Name:Syntax Error. messageSeverity:Error.SMTPCMDS PASCALDoCommandExplanation: An error exists in the SMTP NAMES file.This message is usually accompanied by other errormessages, such as, Error in SMTP NAMES file:.System Action:SMTP continues.System Programmer Response: Correct the specifiederror in the SMTP NAMES file, and restart SMTP.Source File:Procedure Name:SMTPARSE PASCALReplySyntaxErrorTerminating: 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 Action:SMTP continues.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.Source File:Procedure Name:SMTP PASCALInitVars||Explanation: This message displays the erroneoussecurity table record.242 z/VM: TCP/IP Messages and Codes

|SMTP Reply Code MessagesSMTP 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 processingSeverity:Error.Explanation: This message is returned to the mailsender from the local host when the sender’s mailwasnot successfully delivered. This message occurs whenSMTP is unable to write a mail file to its A-diskbecause the A-disk is full.System Action:SMTP continues.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.Source File:Procedure Name:SMTPEVNT PASCALStoreData500 Command Line too longSeverity:Warning.Explanation: You entered a command line thatexceeds the maximum allowable argumentstring-length of 512 characters.System Action:SMTP continues.System Programmer Response: Correct the syntaxand resubmit the command. If necessary, you canrequest online help by entering HELP.Source File:Procedure Name:SMTPCMDS PASCALDoCommand500 Unknown command, commandSeverity: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 VRFYSystem Action:SMTP continues.System Programmer Response: The sender issues acorrect and supported SMTP command. If necessary,the user can request online help by entering HELP.Source File:Procedure Name:SMTPCMDS PASCALNoSuchCommand501 Syntax Error. and not permitted inQuoted TextSeverity: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 Action:SMTP continues.System Programmer Response: Correct the quotedstring, so that it does not contain carriage returns orline feeds.Source File:Procedure Name:SMTPARSE PASCALQText501 Syntax Error. messageSeverity:Error.Explanation: This message is the prefix for all syntaxerrors returned to the SMTP client machine.System Action:SMTP continues.System Programmer Response: Examine the incorrectcommand and additional errors to determine theproblem with the command.Source File:Procedure Name:SMTPARSE PASCALReplySyntaxError501 Syntax Error. expectedSeverity:Error.Explanation: This message is returned to the sender toindicate that the SMTP server expected a valid IPaddress.System Action:SMTP continues.System Programmer Response: Correct the syntax tospecify a valid IP address in dotted decimal notation.Source File:Procedure Name:SMTPARSE PASCALDotNumChapter 16. SMTP Messages 243

SMTP Reply Code Messages501 Syntax Error. must be in range 0..255Severity: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.System Action:SMTP continues.System Programmer Response: Correct the syntax tospecify a valid IP address in dotted decimal notation.Source File:Procedure Name:SMTPARSE PASCALDotNum501 Syntax Error. too longSeverity: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.System Action:SMTP continues.System Programmer Response: Correct the syntax tospecify a valid IP address in dotted decimal notation.Source File:Procedure Name:SMTPARSE PASCALDotNum501 Syntax Error. ’.’ expectedSeverity: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.System Action:SMTP continues.System Programmer Response: Correct the syntax tospecify a valid IP address in dotted decimal notation.Source File:Procedure Name:SMTPARSE PASCALDotNum501 Syntax Error. ’[’ expected in PathNameSeverity:Error.Explanation: This message is returned to the sender toindicate that the parsing procedure expected a leftbracket ([).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALElementCorrect the command501 Syntax Error. ’:’ Expected in Path NameSeverity:Error.Explanation: This message is returned to the sender toindicate that the parsing procedure expected a colon (:).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALADLpath501 Syntax Error. ’@’ expectedSeverity:Error.Correct the commandExplanation: This message is returned to the sender toindicate that the parsing procedure expected an at sign(@).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALMailBoxCorrect the command501 Syntax Error. ’@’ Expected in Source RouteSeverity: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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALAtDomain501 Syntax Error. ’″’ expectedSeverity:Error.Correct the commandExplanation: This message is returned to the sender toindicate that the parsing procedure expected a quotemark (″).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALLocalPartCorrect the command244 z/VM: TCP/IP Messages and Codes

SMTP Reply Code Messages501 Syntax Error. ’BODY’ parameter cannot berepeatedSeverity:Error.Explanation: This message is returned to the sender ifthere is more than one BODY parameter in the MAILFROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. ’BODY’ value is not validSeverity: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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. Domain name cannot end with ’-’Severity:Error.Explanation: You cannot terminate a domain namewith a hyphen (-).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALName501 Syntax Error. Domain name missingSeverity:Error.Correct the commandExplanation: 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 Action:SMTP continues.System Programmer Response: Specify a valid hostname after the HELO or EHLO command.Source File:Procedure Name:SMTPCMDS PASCALDoHeloOrEhlo501 Syntax Error. Domain name too longSeverity: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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoHeloOrEhlo501 Syntax Error. Incomplete AddressSeverity:Error.Correct the commandExplanation: 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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALPlainString501 Syntax Error. Incomplete AddressSeverity:Error.Correct the commandExplanation: The parsing procedure did not expect anull argument at this point.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALPlainStringCorrect the command501 Syntax Error. Invalid LocalPart of AddressSeverity:Error.Explanation: The parsing procedure did not expect anull argument at this point.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALPlainStringCorrect the commandChapter 16. SMTP Messages 245

SMTP Reply Code Messages501 Syntax Error. Invalid Path SpecificationSeverity: Error.Explanation: The parsing procedure did not expect anull argument at this point.System Action: SMTP continues.System Programmer Response: Correct the commandsyntax and try again.Source File: SMTPARSE PASCALProcedure Name: ParsePath501 Syntax Error. Missing host name, ’@’ expectedSeverity: Error.Explanation: The parsing procedure did not find an atsign (@) before the expected host name string.System Action: SMTP continues.System Programmer Response: Correct the commandsyntax and try again.Source File: SMTPARSE PASCALProcedure Name: MailBox501 Syntax Error. Missing Domain NameSeverity: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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALPlainStringCorrect the command501 Syntax Error. Missing number of bytes for ’SIZE’parameterSeverity:Error.Explanation: This message is returned to the sender ifthere is no byte value given for the SIZE parameter forthe MAIL FROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. Missing equal sign after ’BODY’keywordSeverity:Error.Explanation: This message is returned to the sender ifthe BODY keyword for the MAIL FROM command isnot followed by an equal sign.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. Missing equal sign after ’SIZE’keywordSeverity:Error.Explanation: This message is returned to the sender ifthe SIZE keyword for the MAIL FROM command isnot followed by an equal sign.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. Missing value for ’BODY’ parameterSeverity:Error.Explanation: This message is returned to the sender ifthere is no type value given for the BODY parameterfor the MAIL FROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParms501 Syntax Error. Missing User nameSeverity:Error.Correct the commandExplanation: The parsing procedure did not expect anull argument for a user name at this point.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALMailBoxCorrect the command246 z/VM: TCP/IP Messages and Codes

SMTP Reply Code Messages501 Syntax Error. Must use ’MAIL FROM:’Severity:Error.Explanation: You entered an invalid MAIL command.You must use the MAIL FROM: command.System Action:SMTP continues.System Programmer Response:command and try again.Source File:Procedure Name:SMTPCMDS PASCALDoMail501 Syntax Error. Must use ’RCPT TO:’Severity:Explanation:Error.System Action:Use the MAIL FROMYou entered an invalid RCPT command.SMTP continues.System Programmer Response:command and try again.Source File:Procedure Name:SMTPCMDS PASCALDoRcptUse the RCPT TO501 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 Action:SMTP continues.System Programmer Response: Specify either VERBON or VERB OFF and try again.Source File:Procedure Name:SMTPCMDS PASCALDoVerb501 Syntax Error. Need args after ’MAIL’ commandSeverity:Error.Explanation: You entered an invalid MAIL FROMcommand. You must specify a valid mail address afterthe MAIL FROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoMailCorrect the command501 Syntax Error. Need args after ’RCPT’ commandSeverity:Error.Explanation: You entered an invalid RCPT TOcommand. You must specify a valid mail address afterthe RCPT TO command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoRcptCorrect the command501 Syntax Error. Need args after Strcmd commandSeverity:Error.Explanation: You entered an invalid VRFY or EXPNcommand. You must follow the VRFY and EXPNcommands with a user ID or mailing list.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoVrfyExpnCorrect the command501 Syntax Error. Need args after ’TICK’ commandSeverity:Error.Explanation: You entered an invalid TICK command.You must specify a text string after the TICK command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoTickCorrect the command501 Syntax Error. Need args after ’VERB’ commandSeverity:Error.Explanation: You entered an invalid VERB command.You must specify either ON or OFF after the VERBcommand.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoVerbCorrect the commandChapter 16. SMTP Messages 247

SMTP Reply Code Messages501 Syntax Error. No Args after strcmd commandSeverity:Error.Explanation: You entered an invalid DATA, QUIT,RSET, NOOP, TURN, or QUEU command. Argumentsare invalid or unnecessary with these commands.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoCommandCorrect the command501 Syntax Error. Non-numeric ’SIZE’ value is notvalidSeverity:Error.Explanation: This message is returned to the sender ifa non-numeric byte value is given for the SIZEparameter for the MAIL FROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command501 Syntax Error. Only ListId or Userid allowed asargument to this commandSeverity:Error.Explanation: You entered an invalid VRFY or EXPNcommand. You must enter a user ID or mailing listafter the VRFY and EXPN commands.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoVrfyExpn501 Syntax Error. Path too longSeverity:Error.Correct the commandExplanation: The path you specified in a MAIL FROMor RCPT TO command exceeded the limit of 256characters.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoMailCorrect the command501 Syntax Error. Null Recipient InvalidSeverity: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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALDoRcpt501 Syntax Error. Number ExpectedSeverity:Error.Correct the commandExplanation: The parsing procedure expected anumber (0..9) at this point.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALNumberCorrect the command501 Syntax Error. Quoted text is a null stringSeverity:Error.Explanation: The parsing procedure found nothingbetween two quote marks ("").System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALQtextCorrect the command501 Syntax Error. ’SIZE’ parameter cannot be repeatedSeverity:Error.Explanation: This message is returned to the sender ifthere is more than one SIZE parameter in the MAILFROM command.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParmsCorrect the command248 z/VM: TCP/IP Messages and Codes

SMTP Reply Code Messages501 Syntax Error. Special chars only with Escape CharSeverity:Error.Explanation: The parsing procedure did not expect aspecial character other than an at sign (@), right anglebracket (>), or a decimal point (.).System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALPlainStringCorrect the command501 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.System Action:SMTP continues.System Programmer Response:syntax and try again.Source File:Procedure Name:SMTPARSE PASCALName501 Syntax Error. Start Path name with ’

SMTP Reply Code Messages503 No Recipients specifiedSeverity: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.System Programmer Response: Verify that your SMTPcommands are sent in the correct order.Source File:Procedure Name:SMTPCMDS PASCALDoData503 No Sender specifiedSeverity: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.System Programmer Response: Verify that your SMTPcommands are sent in the correct order.Source File:Procedure Name:SMTPCMDS PASCALDoData503 Sender already specifiedSeverity:Warning.Explanation: You already issued a valid MAILcommand. You tried to issue the identical commandunnecessarily.System Action:continues.The MAIL command is ignored; SMTPSystem Programmer Response: Verify that your SMTPcommands are sent in the correct order.Source File:Procedure Name:SMTPCMDS PASCALDoMail503 Sender must be specified before recipientsSeverity:Warning.Explanation: You issued an RCPT command beforeyou issued the MAIL command.System Action:continues.The RCPT command is ignored; SMTPSystem Programmer Response: Verify that your SMTPcommands are sent in the correct order.Source File:Procedure Name:SMTPCMDS PASCALDoRcpt504 HELP topic unknownSeverity:Explanation:topic.Warning.System Action:You requested HELP on an unknownSMTP continues.System Programmer Response:of the valid SMTP commands.Source File:Procedure Name:SMTPCMDS PASCALDoHelpIssue HELP for a list550 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 Action:SMTP continues.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.Source File:Procedure Name:SMTPRES PASCALProcessRQR550 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 Action:SMTP continues.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.Source File:Procedure Name:SMTPRES PASCALProcessRQR250 z/VM: TCP/IP Messages and Codes

SMTP Reply Code Messages550 Host hostname UnknownSeverity: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 Action:SMTP continues.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.Source File:Procedure Name:SMTPRES PASCALProcessRQR550 Mail forwarding not supportedSeverity: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.Source File:Procedure Name:SMTPRES PASCALProcessRQR550 Mailing list CommandLine Nonexistent550 MailBox CommandLine NonexistentSeverity:Warning.Explanation: The mailing list or mailbox yourequested does not exist on the local host.System Action:SMTP continues.System Programmer Response: Specify a validmailing address that exists on the local host.Source File:Procedure Name:SMTPCMDS PASCALDoVrfyExpn550 Source routing not permitted in gatewaySeverity: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.System Programmer Response: Do not performsource routing through this gateway. Determine analternative path to deliver your mail. SMTP continues.Source File:Procedure Name:SMTPRES PASCALProcessRQR550 Spool File Origin: does notmatch Sender’s Address: PrintPathSeverity:Warning.Explanation: Unregistered BSMTP mail was receivedfrom the listed sender at the listed origin and cannot beprocessed.System Action:SMTP continues.System Programmer Response: Follow theinstructions in the SECURITY MEMO file that theSMTP server machine returned to you just prior to thismessage.Source File:Procedure Name:SMTPCMDS PASCALDoMail550 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.Source File:Procedure Name:SMTPRES PASCALProcessRQR550 Unable to resolve recipient address for RetryAgedurationSeverity: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).Chapter 16. SMTP Messages 251

SMTP Reply Code MessagesSystem 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.Source File:Procedure Name:SMTPRES PASCALSendRQR550 User UserName UnknownSeverity: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 Action:SMTP continues.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.Source File:Procedure Name:SMTPRES PASCALProcessLocal550 User UserID@NodeID on Restricted ListSeverity: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.System Action:SMTP continues.System Programmer Response:Source File:Procedure Name:SMTPCMDS PASCALDoRestrictedNone.550 User RSCSUser@RSCSHost is not a registeredgateway userSeverity: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.Source File:SMTPRES PASCALProcedure Name:552 Mail file too largeSeverity:Error.ProcessRQRExplanation: 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 Action:SMTP continues.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.Source File:Procedure Name:SMTPEVNT PASCALStoreData552 Message size exceeds fixed maximum messagesizeSeverity: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 Action:SMTP continues.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.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParms555 Unknown MAIL FROM parameter, parameterSeverity: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:MAILFROM: [SIZE=number_of_bytes][BODY=7BIT/8BITMIME]System Action:SMTP continues.System Programmer Response: Issue a correct MAILFROM command that contains supported parameters.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParms252 z/VM: TCP/IP Messages and Codes

SMTP Reply Code Messages555 8-bit MIME support is not enabledSeverity: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 Action:SMTP continues.System Programmer Response: Enable the 8-bitMIME support using the 8BITMIME configurationstatement.Source File:Procedure Name:SMTPCMDS PASCALParseSrvcExtParms||||||||||||||||||||||||||||||||||||||||SMTPRSCS MessagesDTCSMR2009ESeverity:Error.This section contains SMTPRSCS messages.Invalid FileName SpecificationExplanation: 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 haltsSystem Programmer Response: Reissue theSMTPRSCS command specifying a valid filename,filetype, and filemode.Source File:Procedure Name:DTCSMR2010ESeverity:Error.SMTPRSCSVerifyVMFileInvalid FileType SpecificationExplanation: 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.System Programmer Response: Reissue theSMTPRSCS command specifying a valid filename,filetype, and filemode.Source File:Procedure Name:DTCSMR2011ESeverity:Error.SMTPRSCSVerifyVMFileInvalid FileMode SpecificationExplanation: The filemode specified on theSMTPRSCS command is greater than 2 characters. Afilemode of 2 characters or less must be specified onthe 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|| DTCSMR2012E Garbage detected at end of|SMTPRSCS command.| Severity: Error.| Explanation: More than 3 parameters were specified|||on the SMTPRSCS command. The SMTPRSCScommand takes 3 parameters: a filename, filetype, andfilemode.| System Action: SMTPRSCS halts.| System Programmer Response: Reissue the||SMTPRSCS command specifying a valid filename,filetype, and filemode.| Source File: SMTPRSCS| Procedure Name: VerifyVMFile||||||||||||||||||||||DTCSMR2013E Unable to find input file: FileNameFileType FileModeSeverity:Error.Explanation: The RSCS configuration file specified onthe SMTPRSCS command could not be found on anyaccessed disk.System Action:SMTPRSCS halts.System Programmer Response: Ensure that the inputfile is available on an SMTP accessed disk and reissuethe SMTPRSCS command.Source File:Procedure Name:DTCSMR2014WSeverity:SMTPRSCSWarning.VerifyVMFileWarning: Duplicate entry: NodeExplanation: 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.Chapter 16. SMTP Messages 253

SMTPRSCS Messages|Source File:SMTPRSCS PASCAL|number of nodes specified by the MaxNodes constant.|Procedure Name:Insert|System Action:SMTPRSCS continues.||||||||||DTCSMR2015E Invalid system type specified:BadSysTypeSeverity:Error.Explanation: You entered an optionalSpoolSystemType that was not valid. These three arethe only valid options: RSCS, JES2 and JES3.System Action:SMTPRSCS continues.System Programmer Response: Rerun the programwith the correct SpoolSystemType.||||||||||System Programmer Response: Increase theMaxNodes constant in SMTPRSCS PASCAL to thedesired value, recompile the source, re-link theexecutable module, and rerun SMTPRSCS.Source File:Procedure Name:SMTPRSCS PASCALEndofGameDTCSMR2026E Increase the constant ’MaxNodes’ inSMTPRSCS and try again.Severity:Error.|||||||||||||||||||||||||||||||||||Source File:Procedure Name:DTCSMR2016ESeverity:Error.SMTPRSCS PASCALParseOptionalPartUnrecognized options: BadOptionExplanation: This error message indicates thatSMTPRSCS found additional characters in the optionstring after it found one of the valid options.System Action:SMTPRSCS continues.System Programmer Response: Rerun the SMTPRSCSprogram using the correct specified format. See theTCP/IP Planning and Customization for moreinformation.Source File:Procedure Name:SMTPRSCS PASCALParseOptionalPartDTCSMR2022E Unrecognized parameters:BadParameterSeverity:Error.Explanation: SMTPRSCS found a character that wasnot an open parenthesis in the input parameter stringafter the file mode.System Action:SMTPRSCS continues.System Programmer Response: Rerun the SMTPRSCSprogram using the correct, specified format. See theTCP/IP Planning and Customization for moreinformation.Source File:Procedure Name:SMTPRSCS PASCALProcessCommandLineDTCSMR2024E Found more than MaxNodes RSCSnodes!Severity:Error.Explanation: SMTPRSCS found more than 10000 JES2or JES3 nodes. This exceeds the maximum allowable|||||||||||||||||||||||||||||||||||||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 Action:SMTPRSCS continues.System Programmer Response: Increase theMaxNodes constant in SMTPRSCS PASCAL to a greatervalue, recompile the source, re-link the executablemodule, and rerun SMTPRSCS.Source File:Procedure Name:SMTPRSCS PASCALEndofGameDTCSMR2027W RSCS Node Name: RSCStokentruncated to: VMNodeidLenSeverity: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 Action:SMTPRSCS continues.System Programmer Response: Correct the RSCSnode name, so that it is 8 characters or less.Source File:Procedure Name:SMTPRSCS PASCALParseRSCSDirectFileDTCSMR2032E 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 Action:SMTPRSCS halts.System Programmer Response: Reissue theSMTPRSCS command specifying an input file thatcontains valid RSCS network nodes.254 z/VM: TCP/IP Messages and Codes

SMTPRSCS Messages| Source File: SMTPRSCS | Procedure Name: BuildHashTable|Chapter 16. SMTP Messages 255

SMTPRSCS Messages256 z/VM: TCP/IP Messages and Codes

Chapter 17. SNALINK MessagesSNALNK001I date time : Usage SNALINK 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:Procedure Name:SNALNK002ISNALINK ASSEMBLEMaindate time {lu} : Invalid mx RU size codeExplanation: 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:Procedure Name:snalink assembleMainSNALNK003I date time {lu} : Can not obtain storagefor path index tableExplanation: SNALINK could not allocate memory forthe path index table.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: Ensure the SNALINKvirtual machine is defined correctly.Source File:Procedure Name:snalink assembleMainSNALNK004I date time {lu} :Errorerror in IUCVINISETExplanation: SNALINK encountered an error issuingan IUCVINI SET request to initialize IUCV.System Action: SNALINK abends.User or Operator Response: None.System Programmer Response: Check the SNALINKdefinition, and ensure that it has IUCV authority.Source File: snalink assembleProcedure Name: mainSNALNK005I date time {lu} :Errorerror IN VTAMOPENExplanation: SNALINK encountered an error issuing aVTAM OPEN request.System Action: SNALINK abends.User or Operator Response: Ensure VTAM isoperational.System Programmer Response: Contact your localVTAM administrator.Source File: snalink assembleProcedure Name: main.SNALNK008I date time {lu} : TPEND exit called withreason valueExplanation: SNALINK exits with the indicatedreason code.System Action: SNALINK exits.User or Operator Response: None.System Programmer Response: Correct the problemindicated by the reason code.Source File: snalink assembleProcedure Name: mainSNALNK010I date time {lu} : Can not free path indextable storageExplanation: SNALINK encountered an error freeingmemory.System Action: SNALINK terminates.User or Operator Response: None.System Programmer Response: Check the VM systemfor system problems.© Copyright IBM Corp. 1987, 2002 257

SNALINK MessagesSource File:Procedure Name:snalink assembleMainSNALNK011I date time {lu} : Unexpected iptype typereceivedExplanation: SNALINK received an IUCV interruptwith an unexpected or out-of-range type.System Action:SNALINK abends.User or Operator Response:NoneSystem Programmer Response: This error indicates aprobable TCP/IP code problem.Source File:Procedure Name:SNALNK012IExplanation:from TCPIP.snalink assembleprociucvdate time {lu} : IUCV path path severedSNALINK received a SEVER interruptSystem 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.Source File:Procedure Name:snalink assembleseverSNALNK013I date time {lu} : Can’t find CONNBLOKfor severed path pathExplanation: SNALINK received a SEVER interruptfrom TCPIP, but could not find the associatedconnection in its tables.System Action: The connection is severed, andSNALINK execution continues.User or Operator Response:None.System Programmer Response: This messageindicates a probable TCP/IP code problem. Contact theIBM Support Center.Source File:Procedure Name:snalink assembleseverSNALNK014I date time {lu} : PENDCONN receivedfrom wrong TCPIP id idExplanation: 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.User or Operator Response:None.System Programmer Response: Check Profile GCS(VM) for the correct TCPIP user ID.Source File:Procedure Name:snalink assemblependconnSNALNK015I 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.User or Operator Response:None.System Programmer Response: Increase themaximum connections allowed. If existing connectionsare later closed, resources are freed to allow SNALINKto service this connection.Source File:Procedure Name:snalink assemblependconnSNALNK016I date time {lu} : Severing pending connbecause existing session not killedExplanation: SNALINK received a ConnectionPending interrupt for this LU. However, a connectionalready exists for this LU.System Action: This pending connection is severed,and SNALINK continuesUser 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.Source File:Procedure Name:snalink assemblependconnSNALNK019I date time {lu} : COMPMSG showsnon-zero IUCV audit field valueExplanation: SNALINK received a Message CompleteIUCV interrupt, with a nonzero audit field, indicatingan error.System Action: The associated connection is closed,and SNALINK continues execution.User or Operator Response:System Programmer Response:problem.Source File:snalink assembleNone.Probable TCP/IP code258 z/VM: TCP/IP Messages and Codes

SNALINK MessagesProcedure Name:CompmsgSNALNK020I date time {lu} : Zero UWORD field onCOMPMSG or PENDMSG interruptExplanation: SNALINK received a Message Pendingor Message Complete IUCV interrupt with noassociated connection block (CONNBLOK).System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This messageindicates a possible TCPIP or VTAM problem Tell yourlocal VTAM administrator.Source File:Procedure Name:snalink assemblecompmsg/pendmsgSNALNK021I date time {lu} : Unexpected GENTYPEvalue foundExplanation: SNALINK encountered an invalidGENTYPE value whenSystem Action:VTAM exit.User or Operator Response:System Programmer Response:possible TCP/IP code problem.Source File:Procedure Name:SNALINK abends. processing asnalink assembleprocvtamNone.This error indicates aSNALNK022I date time {lu} : Unexpected control fieldvalue IN SCIP exitExplanation: 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:administrator.Source File:Procedure Name:snalink assemblevtamscipTell your VTAMSNALNK023I date time {lu} : Rejecting bind from plu- no IUCV foundExplanation: 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.Source File:Procedure Name:snalink assemblescipbindSNALNK024I date time {lu} : Rejecting bind - alreadyhave receive sessionExplanation: SNALINK received a BIND request foran LU on which it has already establishedcommunication.System Action:User or Operator Response:coordinator.The BIND is not accepted.System Programmer Response:possible VTAM problem.Source File:Procedure Name:snalink assemblescipbindTell your VTAMThis error indicates aSNALNK026I date time {lu} : Error in MODCB NIBfor receive session. R15 value R0 valueExplanation: SNALINK encountered an errormodifying a Network Information Block in preparationfor an OPNSEC call to accept a BIND for this LU.System Action:User or Operator Response:administrator.The BIND is not accepted.System Programmer Response:possible TCP/IP code problem.Source File:Procedure Name:snalink assemblescipfounSee your VTAMThis error indicates aSNALNK029I date time {lu} : Zero user word in SCIPexit for UNBINDExplanation: SNALINK encountered an user wordcontaining zero in an UNBIND request, indicating anull connection block address.System Action:User or Operator Response:The request is not processed.None.System Programmer Response: This error indicates apossible TCPIP/VTAM problem. Tell your local VTAMadministrator.Source File:Procedure Name:snalink assemblescipunbdChapter 17. SNALINK Messages 259

SNALINK MessagesSNALNK030I date time {lu} : CID in SCIP UNBINDparm list not foundExplanation: SNALINK received an UNBIND requestthat was not associated with either the send or receivesession on its LU.System Action:User or Operator Response:The request is not processed.None.System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See theVTAM console for more information.Source File:Procedure Name:snalink assemblescipunbdSNALNK031I date time {lu} : TESTCB shows sendsession not establishedExplanation: SNALINK received a VTAM OPNDSTEXIT interrupt specifying a session that has not beenestablished.System Action:User or Operator Response:SNALINK ends the connection.None.System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem.Source File:Procedure Name:snalink assemblevtamopndSNALNK032I date time {lu} : OPNDST exit can’t findCONNBLOK. RPL addr addressExplanation: SNALINK received a VTAM OPNDSTEXIT interrupt for which it has no associatedconnection block.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates aprobable TCP/IP or VTAM code problem.Source File:Procedure Name:snalink assemblevtamopndSNALNK034I date time {lu} : TESTCB shows receivessession not establishedExplanation: SNALINK received a VTAM OPNSECEXIT interrupt specifying a session that has not beenestablished.System Action:User or Operator Response:SNALINK ends the connection.None.System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See yourlocal VTAM administrator.Source File:Procedure Name:snalink assemblevtamopnsSNALNK035I date time {lu} : OPNSEC exit can’t findCONNBLOK. RPL addr addressExplanation: SNALINK received a VTAM OPNSECEXIT interrupt for which it has no correspondingconnection block. SNALINK abends.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates aprobable TCP/IP or VTAM code problem.Source File:Procedure Name:snalink assemblevtamopnsSNALNK037I date time {lu} : SEND exit finds zeroRPLUSFLDExplanation: SNALINK received a VTAM SEND EXITinterrupt with a null connection block pointer.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates aprobable TCPIP or VTAM problem.Source File:Procedure Name:snalink assemblevtamsendSNALNK038I date time {lu} : RECEIVE-ANY showsRESPOND value CONTROL ctl RH valueExplanation: SNALINK handled a RECEIVE-ANYinterrupt with the indicated fields.System Action:exists;User or Operator Response:SNALINK ends the connection, if oneNone.System Programmer Response: Tell your VTAMcoordinator. otherwise, the interrupt is ignored.Source File:Procedure Name:snalink assemblercvisanySNALNK039I date time {lu} : Chaining err: Flags flgBuffer buf Pointer ptrExplanation: SNALINK encountered an inconsistencyin its buffer chain.System Action:User or Operator Response:System Programmer Response:possible TCP/IP code problem.SNALINK ends the connection.None.This error indicates a260 z/VM: TCP/IP Messages and Codes

SNALINK MessagesSource File: snalink assembleProcedure Name: rcvchkerSource File: snalink assembleProcedure Name: vtamlostSNALNK040I date time {lu} : RECEIVE exit finds zeroRPLUSFLDExplanation: SNALINK encountered a VTAMRECEIVE EXIT interrupt with a null connection blockpointer.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates aprobable TCPIP or VTAM problem.Source File:Procedure Name:snalink assemblevtamrcvSNALNK042I date time {lu} : CLSDST exit can’t findCONNBLOK. RPL addr addressExplanation: SNALINK received a VTAM CLSDSTEXIT interrupt with an invalid connection blockpointer.System Action:SNALINK abends.User or Operator Response:Restart SNALINKSystem Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See theVTAM console for more information.Source File:Procedure Name:snalink assemblevtamclsdSNALNK043I date time {lu} : TERMSESS exit can’tfind CONNBLOK. RPL addr addressExplanation: SNALINK received a VTAM TERMSESSEXIST interrupt with an invalid connection blockpointer.System Action:SNALINK abends.User or Operator Response:administrator.Source File:Procedure Name:snalink assemblevtamtermSee your VTAMSNALNK044I date time {lu} : LOSTERM reason valuefor receive sessionExplanation: SNALINK received a VTAM LOSTERMEXIT interrupt, indicating this LU lost its receivesession for the indicated reason code.System Action:User or Operator Response:VTAM for problems.SNALINK ends the connection.Check your hardware orSNALNK045I date time {lu} : LOSTERM reason valuefor send sessionExplanation: SNALINK received a VTAM LOSTERMEXIT interrupt, indicating this LU lost its receivesession for the indicated reason code.System Action:User or Operator Response:VTAM for problems.Source File:Procedure Name:SNALINK ends the connection.snalink assemblevtamlostCheck your hardware orSNALNK046I date time {lu} : Zero CONNBLOK ptr inLOSTERM exit, reason valueExplanation: SNALINK received a VTAM LOSTERMEXIT interrupt with a null connection block pointer.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates apossible VTAM or TCPIP problem. See your localVTAM administrator.Source File:Procedure Name:snalink assemblevtamlostSNALNK047I date time {lu} : CID in LOSTERM parmlist not found, reason valueExplanation: SNALINK received a VTAM LOSTERMEXIT interrupt for which it has no parameter list.System Action:User or Operator Response:SNALINK ignores the interrupt.None.System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See theVTAM console for more information.Source File:Procedure Name:snalink assemblevtamlostSNALNK048I date time {lu} : NSEXIT CLEANUPrequest for receive sessionExplanation: SNALINK received a VTAM NSEXITinterrupt with a cleanup request for this LU’s receivesession.System Action:User or Operator Response:VTAM for problems.Source File:SNALINK ends the connection.snalink assembleCheck your hardware orChapter 17. SNALINK Messages 261

SNALINK MessagesProcedure Name:vtamnsSNALNK049I date time {lu} : NSEXIT CLEANUPrequest for send sessionExplanation: SNALINK received a VTAM NSEXITinterrupt with a cleanup request for this LU’s sendsession.System Action:User or Operator Response:VTAM for problems.System Programmer Response:Source File:Procedure Name:SNALINK ends the connection.snalink assemblevtamnsCheck your hardware orNone.SNALNK050I date time {lu} : Zero CONNBLOK ptr inNSEXIT exitExplanation: SNALINK received a VTAM NSEXITinterrupt with a null connection block pointer.System Action:SNALINK abends.User or Operator Response:None.System Programmer Response: This error indicates apossible TCPIP or VTAM problem Tell your localVTAM administrator.Source File:Procedure Name:snalink assemblevtamnsSNALNK051I date time {lu} : CID in NSEXIT parmlist not foundExplanation: SNALINK received a VTAM NSEXITinterrupt for which an associated parameter list couldnot be found.System Action:User or Operator Response:SNALINK ignores the interrupt.None.System Programmer Response: This error indicates apossible VTAM or TCP/IP code problem. See theVTAM console for more information.Source File:Procedure Name:snalink assemblevtamnsSNALNK053I date time {lu} : Error in MODCB NIBfor send session. R15 value R0 valueExplanation: SNALINK received a VTAM OPNDSTinterrupt, but encountered an error executing theOPNDST. An error indication is returned to the caller.System Action:User or Operator Response:administrator.The BIND is not accepted.See your VTAMSystem Programmer Response:possible TCP/IP code problemSource File:Procedure Name:snalink assembledovtopndThis error indicates aSNALNK054I date time {lu} : Cannot issue OPNDST -Previous OPNDST activeExplanation: 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:request.User or Operator Response:System Programmer Response:problem.Source File:Procedure Name:SNALINK does not process thissnalink assembledovtopndNone.Possible TCP/IP codeSNALNK056I date time {lu} :Errorerror acceptingIUCV path pathExplanation: SNALINK encountered an error in anIUCV ACCEPT request.System Action: SNALINK ends the current connectionand returns to its caller.User or Operator Response:System Programmer Response:possible TCP/IP code problem.Source File:Procedure Name:snalink assembledoiucacpNone.This error indicates aSNALNK057I date time {lu} :Errorerror sending onIUCV path pathExplanation: SNALINK encountered an error sendingdata on the indicated IUCV path.System Action:connection.User or Operator Response:SNALINK ends the currentSystem Programmer Response:possible system problem.Source File:Procedure Name:snalink assembledoiucsndNone.This error indicates aSNALNK058I date time {lu} :Errorerror receiving onIUCV path pathExplanation: SNALINK encountered an error sendingdata on the indicated IUCV path.262 z/VM: TCP/IP Messages and Codes

SNALINK MessagesSystem Action: SNALINK ends the currentconnection.User or Operator Response: Ensure that TCPIP isoperational.System Programmer Response: This error indicates apossible TCP/IP code problem.Source File: snalink assembleProcedure Name: doiucrcvSNALNK059I date time {lu} :Errorerror severingIUCV path pathExplanation: SNALINK encountered an error severingthe indicated IUCV path.System Action: None.User or Operator Response: None.Source File: snalink assembleProcedure Name: doseverSNALNK060I date time {lu} :Errorerror in VTAMCLOSEExplanation: SNALINK encountered an error closingan ACB.System Action: None.User or Operator Response: None.Source File: snalink assembleProcedure Name: closeacbSNALNK061I date time {lu} : Error in GENCB RPL.R15 value R0 valueExplanation: SNALINK received an error from aGENCB RPL call.System Action: SNALINK resumes execution.User or Operator Response: None.System Programmer Response: Check errorindication. More errors can result.Source File: snalink assembleProcedure Name: setupconSource File:Procedure Name:snalink assemblesetupconSNALNK063I date time {lu} :function err. R15 value R0value RTNCD value FDBK2 valueExplanation: 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.User or Operator Response:System Programmer Response:administrator.Source File:Procedure Name:snalink assembleprtrplerNone.Tell your VTAMSNALNK064I date time {lu} :function CHECK err. R15value R0 value RTNCD value FDBK2 valueExplanation: 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.User or Operator Response:System Programmer Response:administrator.Source File:Procedure Name:snalink assembleprtchkerNone.Tell your VTAMSNALNK065I date time {lu} :function sense: SSENSEI,SSENSMU, USENSEI: value date time {lu}: SSENSE0,SSENSM0,USENSEO: valueExplanation: This message lists the sense fields from aSNALINK RPL.System Action:None.User or Operator Response:Source File:Procedure Name:snalink assembleprtsenseNone.SNALNK062I date time {lu} : Error in GENCB NIB.R15 value R0 valueExplanation: SNALINK received an error from aGENCB NIB call.System Action: SNALINK resumes execution.User or Operator Response: None.System Programmer Response: Check the errorindication. More errors can result.Chapter 17. SNALINK Messages 263

SNALINK Messages264 z/VM: TCP/IP Messages and Codes

Chapter 18. SNMP MessagesSNMPD MessagesThis chapter contains SNMPD, SNMPLIB, and SQESERV messages.This section contains SNMPD messages.bad privilege mask: maskSeverity:Warning.Explanation: SNMP encountered an invalid privilegemask in a password file entry. The mask is ignored.System Action:The data in the privilege mask fieldUser or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_aut ccan’t create SNMP portSeverity:Fatal.read_pw_fileExplanation: SNMPD encountered an error creating itsTCP/IP port to accept SNMP requests.System Action:SNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.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 cProcedure Name:maincan’t open config file: fileSeverity:Warning.Explanation: The SNMPD trap destination file filecould not be opened.System Action:are sent.SNMPD remains active, but no trapsUser or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io cread_destinationscreate_DPI_port::bind tcperrorSeverity:Warning.Explanation: SNMPD encountered an error bindingthe DPI socket.System Action:Processing continues.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_dpi ccreate_DPI_portcreate_DPI_port::socket tcperrorSeverity:Explanation:DPI socket.Warning.System Action:SNMP encountered an error creating theProcessing continues.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_dpi ccreate_DPI_port© Copyright IBM Corp. 1987, 2002 265

SNMPD Messagescreate_DPI_port:getsockname tcperrorSeverity:Warning.Explanation: SNMPD encountered an error attemptingto obtain the name for the DPI socket.System Action:Processing continuesUser or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_dpi ccreate_DPI_portcreate_SNMP_port::bind tcperrorSeverity:Explanation:socket.Fatal.System Action:SNMP encountered an error binding aSNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io ccreate_SNMP_portcreate_SNMP_port::socket tcperrorSeverity:Explanation:socket.Fatal.System Action:SNMP encountered an error opening aSNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io ccreate_SNMP_portdecode: rc = ReturnCodeSeverity:Warning.Explanation: An error occurred decoding an SNMPrequest; the request is ignored.System Action:SNMP ignores the request.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:DPI tcperrorSeverity:snmp_par cWarning.parse_snmpExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io chandle_errorsError get_snmp_socket: bindSeverity:Fatal.Explanation: SNMPD encountered an error binding tothe MIB/TCP_routed socket.System Action:SNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information abouthow to correct bind problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.Source File:mib_t cProcedure Name:get_snmp_socket266 z/VM: TCP/IP Messages and Codes

SNMPD MessagesError get_snmp_socket: socketSeverity:Fatal.Explanation: SNMPD could not open theMIB/RCP_routed socket.System Action:SNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information abouthow to correct socket problems, see Chapter 12,“Remote Procedure Call Messages” on page 181.Source File:mib_t cProcedure Name:get_snmp_socketmake_TCP_sock::connect tcperror destination addressSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:snmp_io cmake_TCP_sockmake_TCP_sock::socket tcperrorSeverity:Warning.Explanation: SNMP encountered an error creating asocket to send traps by means of TCP.System Action:No trap is sent.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:snmp_io cmake_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.Source File:Procedure Name:snmp_par c{ps2pe failed: ps_error}Severity:Warning.parse_snmpExplanation: An error occurred allocating storage toconvert the presentation stream to a presentationelement.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.Source File:Procedure Name:snmp_par cparse_snmpread_pw_file: can’t open fileSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:snmp_aut cread_pw_fileChapter 18. SNMP Messages 267

SNMPD Messagesread_pw_file: out of memorySeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Define a larger virtualstorage size for the SNMPD virtual machine.Source File:Procedure Name:select tcperrorSeverity:Fatal.snmp_aut cread_pw_fileExplanation: SNMP encountered an error from aselect() call, waiting for incoming packets.System Action:SNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io chandle_requestssend_SNMP_response tcperrorSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_io csend_SNMP_responsesend_UDP tcperrorSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmp_init failedSeverity:Explanation:Fatal.System Action:snmp_io csend_UDP_trapSNMPD initialization failed.SNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:mib_t cProcedure Name:main{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 Action:The current SNMP request is ignored.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Contact the IBMSupport Center. Processing continues with the nextrequest.Source File:Procedure Name:snmp_par cparse_snmp268 z/VM: TCP/IP Messages and Codes

SNMPD Messagesunknown SNMP request typeSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:sent the request for errors.Source File:Procedure Name:snmp_par cunknown socket typeSeverity:Explanation:type socket.Fatal.System Action:parse_snmpCheck the client thatSNMP received a packet on an unknownSNMPD terminates.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.Source File:Procedure Name:snmp_io chandle_requestsusage: snmpd Severity:Fatal.Explanation: SNMPD was invoked with too manyparameters; the correct command syntax is displayed.Note: The angle brackets (< >) are literal in thismessage.System Action:SNMPD terminates.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:start parameters.Source File:mib_t cProcedure Name:mainCorrect the SNMPDSNMPLIB MessagesThis section contains the SNMPLIB messages.SNM010Ecommand Invalid netmask or desirednetwork specifiedExplanation: 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:Procedure Name:SNM011EExplanation:function.System Action:snmpsnmp assemblesnmpcommand Invalid function: functionUser or Operator Response:An SNMP command specified an invalidThe command is ignored.If the command wasissued 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.Source File:Procedure Name:SNM012Esnmpsnmp assemblesnmpcommand 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.Source File:snmpsnmp assembleChapter 18. SNMP Messages 269

SNMPLIB MessagesProcedure Name:SNM013Esnmpcommand Missing functionExplanation: An SNMP command omitted therequired function specification.System Action:The command is ignored.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.Source File:Procedure Name:SNM014EExplanation:name.System Action:snmpsnmp assemblesnmpcommand Missing variable nameAn SNMP command omitted a variableThe command is aborted.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.Source File:Procedure Name:SNM015Esnmpsnmp assemblesnmpcommand Missing set value for variableExplanation: SNMP encountered a SET function withno value specified.System Action:The command is aborted.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.Source File:Procedure Name:snmpsnmp assemblesnmpSNM016Ecommand Missing or invalid destinationhost identificationExplanation: An SNMP command omitted a requiredhost ID specification.System Action:The command is aborted.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.Source File:Procedure Name:SNM017Esnmpsnmp assemblesnmpcommand Missing community nameExplanation: An SNMP command omitted a requiredcommunity name specification.System Action:The command is ignored.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.Source File:Procedure Name:SNM018Esnmpsnmp assemblesnmpcommand Request rejected, task task notactiveExplanation: 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.System Programmer Response:Source File:Procedure Name:SNM019Esnmpsnmp assemblesnmpNone.command Request rejected, task task not(yet) connectedExplanation: An SNMP request was rejected becausethe task task had not yet established an IUCVConnection with the SNMP Query Engine.270 z/VM: TCP/IP Messages and Codes

SNMPLIB MessagesSystem Action: The connection is still pending. Thesystem continues operation.User or Operator Response: Wait for the connectionto complete and reissue the SNMP request.System Programmer Response:Source File:Procedure Name:SNM020Esnmpsnmp assemblesnmpNone.command Error error on DSIGETExplanation: 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.Source File:Procedure Name:SNM021Esnmpsnmp assemblesnmpcommand Error error on DSIMQSExplanation: 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.Source File:Procedure Name:SNM022Esnmpsnmp assemblesnmpcommand Missing or invalid trap filter idExplanation: An SNMP command failed to specify orspecified an invalid trap filter ID.System Action:The command is aborted.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.Source File:snmpsnmp assembleProcedure Name:SNM051EsnmpSNMP Request request from origindiscarded, MsgCompleteIPAUDIT=XvalueExplanation: 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:Procedure Name:SNM052Esnmptask assemblesnmpiucvSNMP Request request from originatordiscarded, IUCV SEND error (R15)=errorExplanation: 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.Source File:Procedure Name:SNM053Esnmptask assemblesnmpiucvSNMP Request request from originatordiscarded, IUCV Connection SeveredExplanation: The indicated SNMP request, req, fromoperator, originator, was discarded because the SNMPIUCV connection was severed.System Action:Because the connection was severed,Chapter 18. SNMP Messages 271

SNMPLIB Messagesno 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.System Programmer Response:Source File:Procedure Name:SNM101Wsnmptask assemblesnmpiucvNone.SNMP task task found Query Enginename not readyExplanation: 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 EngineUser 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.Source File:Procedure Name:SNM103Esnmptask assemblesnmpiucvSNMP task task got error error onfunction sub-funcExplanation: SNMP encountered the indicated errorfrom the indicated IUCV function.System Action: The request is aborted. If possible, thesystem continues operation.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:snmptask assemblesnmpiucvSNM104ESNMP task task has count IUCVinterrupts pending, path severedExplanation: 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.Source File:Procedure Name:SNM105Esnmptask assemblesnmpiucvSNMP task task ignored IUCV interrupt,unexpected IPTYPE typeExplanation: SNMP received an IUCV interrupt withan unexpected IPTYPE field.System Action: The interrupt is ignored. The systemcontinues operation.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that theversion and level of SNMP Query Engine are in syncwith the version of the SNMPIUCV task.Source File:Procedure Name:SNM106Esnmptask assemblesnmpiucvSNMP task task connection to QueryEngine ID now severedExplanation: 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.System Programmer Response:Source File:Procedure Name:snmptask assemblesnmpiucvNone.272 z/VM: TCP/IP Messages and Codes

SNMPLIB MessagesSNM107ESNMP task task received sever forpath=pathExplanation: 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.System Programmer Response:Support Center.Source File:Procedure Name:snmptask assemblesnmpiucvContact the IBMSNM121WExplanation:length.System Action:SNMP task task incoming packet hasinvalid packet length lengthSNMP received a packet with an invalidInvalid packets are ignored.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Ensure that you havea correct level of the SNMP Query Engine that is insync with the SNMPIUCV task on NetView side.Source File:Procedure Name:snmptask assemblesnmpiucvSNM108ESNMP 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that TCP/IPhas been installed correctly on your z/VM system.Source File:Procedure Name:SNM120Wsnmptask assemblesnmpiucvSNMP task task got error error onDSIGETExplanation: 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.User or Operator Response: If the error persists, tellthe system programmer about the problem.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.Source File:Procedure Name:snmptask assemblesnmpiucvSNM122WSNMP task task incoming packet hasinvalid character set valueExplanation: SNMP received a packet specifying aninvalid character set.System Action: The packet is ignored. The systemcontinues operation.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that theversion and level of SNMP Query Engine are in syncwith the version of the SNMPIUCV task.Source File:Procedure Name:SNM123WExplanation:packet type.snmptask assemblesnmpiucvSNMP task task incoming packet hasinvalid packet type valueSNMP received a packet with an invalidSystem Action: The packet is ignored. The systemcontinues operation.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Ensure that theversion and level of SNMP Query Engine are in syncwith the version of the SNMPIUCV task.Source File:Procedure Name:SNM127Wsnmptask assemblesnmpiucvSNMP task task got error error onDSIDKSExplanation: 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 systemChapter 18. SNMP Messages 273

SNMPLIB Messagesprogrammer about the problem.System Programmer Response: Use the err value todetermine the reason for the error. See NetViewCustomization: Using Assembler for DSIDKS error codes.Source File:Procedure Name:SNM128Wsnmptask assemblesnmpicuvSNMP task task found missing value orinvalid value for parameterExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:invalid value in SNMPARMS.Correct the missing orSource File:Procedure Name:SNM129Wsnmptask assemblesnmpiucvSNMP task task found invalidinitialization parameter valueExplanation: SNMP encountered an invalidinitialization parameter.System Action: The invalid initialization parameter isignored. Initialization continues and assumes thedefault value for the invalid parameter.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the invalidinitialization parameter in SNMPARMS.Source File:Procedure Name:snmptask assemblesnmpiucvSQESERV MessagesThis section contains SQESERV messagescannot open MIB description file: fileSeverity: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.System Programmer Response:Source File:Procedure Name:snmpdesc cNone.read_mib_desc_tblcreate_SNMP_port ::sockettcperrorSeverity:Fatal.Explanation: A socket() call failed attempting to createan SNMP port. The port could not be created.System Action:The SQESERV module is terminated.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmpsend ccreate_SNMP_portcreate_SNMP_port: bind tcperrorSeverity:Fatal.Explanation: A bind() call failed attempting to createan SNMP port. The port could not be created.System Action:The SQESERV module is terminated.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmpsend ccreate_SNMP_portmake_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. Processing274 z/VM: TCP/IP Messages and Codes

SQESERV Messagescontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.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:Procedure Name:snmppars cmake_SNMP_requestmake_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.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Increase the virtualstorage on the SNMPQE virtual machine.Source File:Procedure Name:snmppars cmake_SNMP_requestmake_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 Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Increase the virtualstorage on the SNMPQE virtual machine.Source File:Procedure Name:snmppars cmake_SNMP_requestmake_SNMP_packet: illegal SNMP request: requestSeverity:Warning.Explanation: The SQE server encountered an illegalSNMP request.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Source File:Procedure Name:snmppars cmake_SNMP_requestContact the IBMmake_SNMP_packet: no MIB type defined: nameSeverity:Error.Explanation: An application has tried to issue anSNMP Set request for an object for which no MIBdescription data is known.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Add the relevant datato the MIB description file and restart SQESERV. This isthe MIB_DESC DATA file.Source File:Procedure Name:snmppars cmake_SNMP_requestmake_SNMP_request: illegal object identifier: idSeverity:Warning.Explanation: The SQE server encountered an illegalobject identifier, which is ignored.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:snmppars cmake_SNMP_requestout 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:done.Processing continues. No caching isUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Increase the virtualstorage for the SNMPQE virtual machine.Source File:sqecache cChapter 18. SNMP Messages 275

SQESERV MessagesProcedure Name:cache_objectout of memory in cache_object nameSeverity:Warning.Explanation: The SQE server could not allocateenough memory to add an object to a list.System Action:done.Processing continues. No caching isUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Increase the virtualstorage for the SNMPQE virtual machine.Source File:Procedure Name:sqecache ccache_objectparse_SNMP_packet: cannot parse packet (decode)Severity:Warning.Explanation: The SQE server encountered an errordecoding an SNMP request.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Identify the agent thatsent the incorrect request and correct any problems atthat agent.Source File:Procedure Name:snmppars cparse_SNMP_packetparse_SNMP_packet: cannot parse packet (ps_alloc)Severity:Warning.Explanation: The SQE server could not parse anSNMP request because sufficient memory could not beallocated.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Increase the virtualstorage for the SNMPQE virtual machine.Source File:Procedure Name:snmppars cparse_SNMP_packetparse_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.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Source File:Procedure Name:snmppars cparse_SNMP_packetContact the IBMparse_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 Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: If the error persists, tellthe system programmer about the problem.System Programmer Response: Increase the virtualstorage for the SNMPQE virtual machine.Source File:Procedure Name:snmppars cparse_SNMP_packetparse_SNMP_packet: corrupted packetSeverity:Warning.Explanation: The SNMP server encountered acorrupted packet. There is a problem with the agentthat sent the request.System Action: The request is ignored. Processingcontinues with the next request.User or Operator Response: Identify the SNMP agentthat sent the incorrect packet and correct any errors.System Programmer Response:Source File:Procedure Name:snmppars cresolver not yet supportedSeverity:Warning.None.parse_SNMP_packetExplanation: The SQE server encountered aQ_RESOLVER_RESPONSE request, which is notcurrently supported.276 z/VM: TCP/IP Messages and Codes

SQESERV MessagesSystem Action: The request is ignored. Processingcontinues with the next request.User or Operator Response:System Programmer Response:Source File:Procedure Name:sqequeue cqueue_entryselect failed in await_queriesSeverity:Fatal.None.None.Explanation: The SQE server encountered an errorissuing a select function call to determine if any querieswere outstanding.System Action:exit code 1.The SQESERV module terminates withUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.Source File:Procedure Name:sqeserv cawait_queriesSQEE001 –– Can’t make UDP portSeverity:Fatal.Explanation: The SQE server could not make theSNMP UDP port.System Action:exit code 1.The SQESERV module terminates withUser or Operator Response: Tell the systemprogrammer about the problem.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.Source File:Procedure Name:sqeserv ccreate_portsSQEE002 –– Can’t make SNMP trap portSeverity:Fatal.Explanation: The SQE server cannot make the SNMPtrap port because of a socket call failure or a bindfailure.System Action:exit code 1.The SQESERV module terminates withUser or Operator Response: Ensure that anotherSQESERV program is not already running. Only oneSQESERV 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.Source File:Procedure Name:sqeserv ccreate_portsSQEE003 –– Can’t do TCP listenSeverity:Fatal.Explanation: The SQE server encountered an errorattempting a TCP listen.System Action:exit code 1.The SQESERV module terminates withUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.Source File:Procedure Name:sqeserv ccreate_portsSQEE004 –– Can’t do IUCV listenSeverity:Fatal.Explanation: The SQE server encountered an errorattempting an IUCV listen.System Action:exit code 1.The SQESERV module terminates withUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: For information aboutcorrecting socket problems, see Chapter 12, “RemoteProcedure Call Messages” on page 181.Source File:Procedure Name:sqeserv ccreate_portsSQEW001 –– Can’t make raw ICMP socketSeverity: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.Chapter 18. SNMP Messages 277

SQESERV MessagesSystem Programmer Response: Add SNMPQE to theOBEY list of PROFILE TCPIP, if it is not already there.Source File: sqeserv cProcedure Name: create_portsstore_SNMP_var: unknown MIB type: typeSeverity: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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Identify the agentsending the incorrect response and correct anyproblems with the agent.Source File:Procedure Name:snmppars cstore_SNMP_varunknown MIB type: typeSeverity:Warning.Explanation: The SQE server encountered anunknown type field in the MIB description file.System Action:Processing continues.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the MIBdescription file, the MIB_DESC DATA file, and restartSQESERV.Source File:Procedure Name:snmpdesc cread_mib_desc_tbl278 z/VM: TCP/IP Messages and Codes

Chapter 19. SSL MessagesThis chapter contains the SSL processing messages. It also contains lists of the SSLserver return codes and reason codes.DTCSSL001EAll cipher suites have been excludedExplanation: 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: commandExplanation: The SSLADMIN command was receivedat the SSL server.System Action:SSL processing continues.System Programmer Response:DTCSSL004ENone.No operands on SSLADMINExplanation: The SSLADMIN command was issuedwithout operands.System Action:terminated.The SSLADMIN command isSystem Programmer Response:with operands.DTCSSL005EReissue the commandpthread_create() error for thread_IDExplanation: A process thread could not be created.The message indicates whether the error was for themain SSL thread or a worker thread.System Action:System Programmer Response:SSL processing is terminated.Call IBM Service.DTCSSL006E Activity received by select() was notfrom SSLADMINExplanation: 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 serverExplanation:System Action:The SSL server is stopping.The SSL server stops.System Programmer Response:None.DTCSSL009E select() returned without a client orserver readExplanation: The select() call in the SSL worker threadreturned with a response that was not from either theclient socket or the server socket.System Action: None. The SSL server waits foranother response.System Programmer Response: Turn trace flow on,reproduce the problem, and call IBM Service.DTCSSL010ECall to select() failedExplanation: The select() call in the SSL worker threadreturned a negative return code.System Action:terminated.This SSL client-server conversation isSystem Programmer Response: Turn trace flow on,reproduce the problem, and call IBM Service.DTCSSL011ENo file descriptors are readyExplanation: The select() call in the SSL worker threadreturned a zero return code.System Action: None. The SSL server waits foranother response.System Programmer Response: Turn trace flow on,reproduce the problem, and call IBM Service.DTCSSL014EInvalid argument: argumentExplanation: 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© Copyright IBM Corp. 1987, 2002 279

SSL Messagesan SSLADMIN command, correct the argument andretry.DTCSSL015I SSL server has startedExplanation:System Action:The SSL server has started.The SSL server starts.System Programmer Response:None.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.System Action:terminated.System Programmer Response:This SSL client-server conversation isCall IBM Service.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.System Action:terminated.System Programmer Response:DTCSSL022EThis SSL client-server conversation isHandshake failed rc rcCall IBM Service.Explanation: The handshaking with a client failed. Foran explanation of the return code, see Table 2 onpage 291.System Action:terminated.System Programmer Response:of the failure and retry.This SSL client-server conversation isDetermine the causeDTCSSL036I Local connections will be protected bySSLExplanation: A local connection destined for a secureport or user ID will be routed to the SSL Server.System Action:SSL processing continues.System Programmer Response:None.DTCSSL037I Local connections will not be protectedby SSLExplanation: A local connection destined for a secureport or user ID will not be routed to the SSL Server.System Action:SSL processing continues.System Programmer Response:None.DTCSSL040I Trace has been turned offExplanation:was issued.System Action:The SSLADMIN NOTRACE commandSSL tracing is turned off.System Programmer Response:DTCSSL041EExplanation:System Action:None.Out of memory at locationA request for memory was denied.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_nameExplanation: An error was returned when a mutexlock was requested. For the meaning of errno values,see Table 3 on page 291.System Action:The SSL server is shut down.System Programmer Response: Turn trace flow on,reproduce the error, and call IBM Service.DTCSSL043E Error errno when unlocking mutexmutex_nameExplanation: An error was returned when unlocking amutex. For the meaning of errno values, see Table 3 onpage 291.System Action:The SSL server is shut down.System Programmer Response: Turn trace flow on,reproduce the error, and call IBM Service.280 z/VM: TCP/IP Messages and Codes

SSL MessagesDTCSSL047I Trace establishedExplanation:successful.System Action:The SSLADMIN TRACE command wasSSL tracing is turned on.System Programmer Response:DTCSSL048I Trace not changedNone.Explanation: The SSLADMIN TRACE command wasnot successful. The existing trace setting has not beenchanged.System Action:SSL processing continues.System Programmer Response:DTCSSL049ENone.Invalid IP address ipaddrExplanation: The IP address used in the SSLADMINTRACE command was in the wrong format.System Action:SSL tracing is turned off.System Programmer Response: Reissue the command,entering the IP address in dotted format (n.n.n.n).DTCSSL050Econnection failed with rc rc errno errnoExplanation: 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.System Programmer Response:DTCSSL051ECall IBM Service.Invalid connection number: numberExplanation: The connection number specified on anSSLADMIN TRACE command was not an integer. Onlyintegers are accepted for connection numbers.System Action:SSL tracing is turned off.System Programmer Response: Reissue the commandwith a valid connection number.DTCSSL052EOut of memory at location: errno errnoExplanation: A memory request for a Todo blockreturned a negative return code. For the meaning oferrno values, see Table 3 on page 291.System Action:The SSL server is shut down.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 errnoerrnoExplanation: 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.System Programmer Response:DTCSSL055ECall IBM Service.Connection to real server failedExplanation: The connection from the SSL server tothe application server could not be made.System Action:terminated.System Programmer Response:application server is running.That SSL client-server conversation isDTCSSL056I No sessions are activeMake sure theExplanation: An SSLADMIN QUERY SESSIONScommand was issued, and there were no activesessions.System Action:SSL processing continues.System Programmer Response:None.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.DTCSSL058EDTCPARMS are too longExplanation: 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.DTCSSL059EExplanation:Open error on file: pathnameThe DTCPARMS file could not be read.System Action: Default values are used; SSLprocessing continues.System Programmer Response:Call IBM Service.Chapter 19. SSL Messages 281

SSL MessagesDTCSSL060EExplanation:failed.System Action:Mutex instruction failedThe pthread_condition_signal() callSystem Programmer Response:The SSL server is shut down.Call IBM Service.DTCSSL061E Cache size of requested_size is not valid;cache size is set to set_sizeExplanation: 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_lifeExplanation: 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.DTCSSL063EPort number not validExplanation: The port number specified on theSSLADMIN TRACE command was not an integer. Onlyintegers are accepted for port numbers.System Action:SSL tracing is turned off.System Programmer Response:with a valid port number.DTCSSL072EExplanation:Monitor updates failedReissue the commandThe monitor records were not updated.System Action: The SSL server keeps running, but themonitor data is unreliable.System Programmer Response:DTCSSL073EExplanation:gone.System Action:Broken pipeCall IBM Service.The connection to the TCPIP stack isThe SSL server is shut down.System Programmer Response: Check to see if theTCPIP stack is started; if not, restart it. If the SSL serveris in the AUTOLOG list, it will be restarted; if not,restart the SSL server after TCPIP comes up.DTCSSL074ENETIUCV errorExplanation: The connection to the TCPIP stack couldnot be established.System Action:The SSL server is shut down.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.NONESystem Action:indicates that only the default VMSSLoperands, SSL administration port, andTCP/IP (stack) server are being used.SSL processing continues.System Programmer Response:DTCSSL092ELog file flush failedNone.Explanation: During the processing of the SSLADMINLOG command, the buffer could not be written to thefile on the SSL server machine.System Action:System Programmer Response:software Support Center.The SSLADMIN LOG command fails.Contact the IBM282 z/VM: TCP/IP Messages and Codes

SSL MessagesDTCSSL093ELog file copy (cp) failed rc: rcExplanation: During the processing of the SSLADMINLOG command, the copy function of the message logfailed. For the meaning of rc values see Table 2 onpage 291System Action:System Programmer Response:software Support Center.DTCSSL094EThe SSLADMIN LOG command fails.Contact the IBMLog file read failed rc: rc errno: errnoExplanation: 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.System Action:System Programmer Response:software Support Center.DTCSSL201EThe SSLADMIN LOG command fails.Contact the IBMInternal error--GSKKM error code.Explanation: An unexpected error occurred whileusing functions to manage certificates.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.DTCSSL204EA 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.DTCSSL205EAn I/O error occurred.Explanation: There was an error on a read or sendsocket call while processing an SSLADMIN command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:persists, contact IBM Service.DTCSSL206EPeer closed connection.Retry. If the errorExplanation: During SSLADMIN processing, theconnection was closed by the client before thecommand completed.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Reissue theSSLADMIN command. If the condition persists, callIBM Service.DTCSSL202EInternal 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:terminated.The SSL client-server conversation isSystem Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.DTCSSL203EDatabase 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.DTCSSL207EAn 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.System Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.DTCSSL208E An error occurred while writing datato a file.Explanation: There was an error while writing to theSSL certificate database password file.System Action: The other message(s) provide detailsabout the system action.System Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.Chapter 19. SSL Messages 283

SSL MessagesDTCSSL209EFailed 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.DTCSSL210ESSL server is shutting down.Explanation: A severe error occurred and the SSLserver cannot continue.System Action:The SSL server is shut down.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 Action:SSL processing continues.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 Action:SSL processing continues.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.System Action:SSL processing continues.System Programmer Response:None.DTCSSL314I CA certificate in certificate chain storedin the database. Label is: labelExplanation: An SSLADMIN STORE command wasissued for a certificate chain. A CA certificate from thechain was stored in the certificate database with theindicated label.System Action:SSL processing continues.System Programmer Response:None.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.System Action:SSL processing continues.System Programmer Response:None.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.System Action:SSL processing continues.System Programmer Response:None.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.System Programmer Response:None.DTCSSL319I Database regenerated.Explanation: The SSL certificate database wasregenerated as a result of an SSLADMINREGENERATE command.System Action:SSL processing continues.System Programmer Response:None.DTCSSL401E The label already exists in thedatabase.Explanation: The label specified on the SSLADMINcommand is already being used.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Reissue the commandusing a unique label. To determine what labels exist inthe certificate database, issue ssladmin query cert * orssladmin query req *.284 z/VM: TCP/IP Messages and Codes

SSL MessagesDTCSSL402ENo entry is found with this label.Explanation: The label specified on the SSLADMINcommand does not exist in the certificate database.System Action:terminated.The SSLADMIN command isSystem 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.System Action: The SSLADMIN command isterminated; the certificate is not stored.System Programmer Response:None.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 Action:terminated.The SSLADMIN command isSystem 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 Action: The SSLADMIN command isterminated; the certificate is not stored.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 Action: The SSLADMIN command isterminated; the certificate is not stored.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 Action:terminated.The SSLADMIN command isSystem 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 Action:terminated.The SSLADMIN command isSystem 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 thatChapter 19. SSL Messages 285

SSL Messagessent 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 Action:terminated.The SSLADMIN command isSystem 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.System Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.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.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.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.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Consult the previousmessages on the console that refer to this error. Ifneeded, contact IBM Service.DTCSSL417E An invalid password was encounteredor the database has been corrupted.Explanation: The SSL certificate database or itsinternal password is corrupted.System Action: The other message(s) provide detailsabout the system action.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.DTCSSL418EBad password file.Explanation: The SSL certificate database internalpassword file is corrupted. The certificates in thedatabase are not usable.System Action: The other message(s) provide detailsabout the system action.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.DTCSSL419EThe password file does not exist.Explanation: The SSL certificate database internalpassword file does not exist. The certificates in thedatabase are not usable.System Action: The other message(s) provide detailsabout the system action.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.DTCSSL420EExplanation:exist.System Action:The certificate database does not exist.The SSL certificate database does notSystem Programmer Response:The SSL server is shut down.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 Action: The other message(s) provide detailsabout the system action.System Programmer Response: Consult the successivemessages on the console that refer to this error. Try286 z/VM: TCP/IP Messages and Codes

SSL Messagesusing 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 *.DTCSSL502ECertificate 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.DTCSSL503ENo common cipher suites.Explanation: There is no cipher suite match betweenthe client and the SSL server.System Action:terminated.The SSL client-server conversation isSystem 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.System Action:terminated.System Programmer Response:DTCSSL2400EThe SSL client-server conversation isFile fn ft exists.None.Explanation: The indicated CMS file cannot alreadyexist when you issue the SSLADMIN command.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Select a unique labelto be used for SSLADMIN processing.DTCSSL2401EFile fn ft does not exist.Explanation: The specified CMS file must alreadyexist before you issue the SSLADMIN command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:file and reissue the command.Create the requiredDTCSSL2402E keyword keyword and value aremissing from X509INFO file.Explanation: A required keyword and value aremissing from the X509INFO file.System Action:terminated.The SSLADMIN command isSystem 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.System Action:SSL processing continues.System Programmer Response:DTCSSL2404INone.Request saved in file fn ft fm.Explanation: The SSLADMIN REQUEST commandsuccessfully stored the certificate request in theindicated CMS file.System Action:System Programmer Response:The SSLADMIN command completes.None.DTCSSL2405I Certificate stored in certificatedatabase.Explanation: The SSLADMIN STORE commandsuccessfully stored the certificate in the certificatedatabase.System Action:System Programmer Response:The SSLADMIN command completes.None.DTCSSL2406I {CERTIFICATE|REQUEST} deletedfrom database.Explanation: The SSLADMIN DELETE commandsuccessfully deleted the certificate or certificate requestfrom the certificiate database.System Action:System Programmer Response:The SSLADMIN command completes.None.Chapter 19. SSL Messages 287

SSL MessagesDTCSSL2407IUnknown command.Explanation: An unsupported operand was specifiedon the SSLADMIN command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:with the correct operands.Reissue the commandDTCSSL2408I 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.DTCSSL2409ICommand canceled.Explanation: The SSLADMIN REMOVE commandwas canceled because you did not respond ’YES’ tomessage DTCSSL2408I.System Action:terminated.System Programmer Response:DTCSSL2410EThe SSLADMIN command isNone.Error reading file fn ft fm.Explanation: An error was encountered while tryingto read the file.System Action:terminated.System Programmer Response:The SSLADMIN command isContact IBM Service.DTCSSL2412E {DATA|NODATA} is valid only forTRACE CONNections.Explanation: This operand can be used only on theSSLADMIN TRACE CONNECTIONS command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:with the correct syntax.DTCSSL2413EError writing file fn ft fm.Reissue the commandExplanation: 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 wasnot written to a CMS file. However, the certificate orcertificate request does exist in the certificate database.System Programmer Response:of the write error.DTCSSL2414ENo R/W disks available.Determine the causeExplanation: There are no R/W disks available towhich the certificate or certificate request can bewritten.System Action:terminated.The SSLADMIN command isSystem Programmer Response:and reissue the command.DTCSSL2415EProvide a R/W diskDisk 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 Action:terminated.The SSLADMIN command isSystem Programmer Response: Reissue the command,specifying a file mode that represents a R/W disk.DTCSSL2416ITrace started.Explanation: The selected trace of the SSL servervirtual machine has been started.System Action:SSL processing continues.System Programmer Response:DTCSSL2417INone.No sessions are active.Explanation: At the time the SSLADMIN QUERYSESSIONS command was issued, there were no activesessions.System Action:SSL processing continues.System Programmer Response:None.DTCSSL2418E Too many operands on theSSLADMIN TRACE command.Explanation: You have provided too many operandson the SSLADMIN TRACE command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:with the correct operands.Reissue the command288 z/VM: TCP/IP Messages and Codes

SSL MessagesDTCSSL2419E 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 Action:terminated.The SSLADMIN command isSystem Programmer Response:from an authorized user ID.DTCSSL2420EIssue the commandThe 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 Action:terminated.System Programmer Response:The SSLADMIN command isStart the SSL server.DTCSSL2421E The connection to the SSL server wasterminated.Explanation: While processing the SSLADMINcommand, the connection to the SSL server wasterminated.System Action:terminated.The SSLADMIN command isSystem 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 Action:terminated.The SSLADMIN command isSystem 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.System Action:terminated.The SSLADMIN command isSystem Programmer Response:Contact IBM Service.DTCSSL2424I Incorrect operand on SSLADMINcommand: operand.Explanation: You specified an incorrect operand onthe SSLADMIN command.System Action:terminated.The SSLADMIN command isSystem Programmer Response:with the correct syntax.Reissue the commandDTCSSL2425E Label length cannot be longer thanlength.Explanation: The label specified on the SSLADMINcommand cannot exceed the length indicated in theerror message.System Action:terminated.The SSLADMIN command isSystem Programmer Response: Reissue the commandwith a label of the correct length.DTCSSL2426EDisk 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.DTCSSL2427EDisk 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.System Action:None.System Programmer Response:None.Chapter 19. SSL Messages 289

SSL MessagesDTCSSL2429I 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:VDISK.System Programmer Response:The system attempts to establish aNone.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 Action:None.System Programmer Response:Restart the SSL server.DTCSSL2430IExplanation:Unable to use VDISK.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:a 3390, 3380, or FBA device.Place the 203 disk onDTCSSL2433I 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.290 z/VM: TCP/IP Messages and Codes

SSL MessagesSSL Server Return CodesTable 2. SSL Server Return CodesCode Meaning401 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.423 Internal error. Report problem to service.424 Internal error. Report problem 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 Meaning1 EPERM Operation not permitted2 ENOENT No such file or directory3 ESRCH No such process4 EINTR Interrupted system call5 EIO I/O error6 ENXIO No such device or address7 E2BIG Arg list too long8 ENOEXEC Exec format error9 EBADF Bad file number10 ECHILD No child processes11 EAGAIN Try again12 ENOMEM Out of memory13 EACCES Permission denied14 EFAULT Bad address15 ENOTBLK Block device required16 EBUSY Device or resource busy17 EEXIST File exists18 EXDEV Cross-device link19 ENODEV No such device20 ENOTDIR Not a directory21 EISDIR Is a directory22 EINVAL Invalid argument23 ENFILE File table overflow24 EMFILE Too many open files25 ENOTTY Not a typewriter26 ETXTBSY Text file busyChapter 19. SSL Messages 291

SSL MessagesTable 3. SSL Server Reason Codes (continued)Code Name Meaning27 EFBIG File too large28 ENOSPC No space left on device29 ESPIPE Illegal seek30 EROFS Read-only file system31 EMLINK Too many links32 EPIPE Broken pipe33 EDOM Math argument out of domain of func34 ERANGE Math result not representable35 EDEADLK Resource deadlock would occur36 ENAMETOOLONG File name too long37 ENOLCK No record locks available38 ENOSYS Function not implemented39 ENOTEMPTY Directory not empty40 ELOOP Too many symbolic links encountered42 ENOMSG No message of desired type43 EIDRM Identifier removed44 ECHRNG Channel number out of range45 EL2NSYNC Level 2 not synchronized46 EL3HLT Level 3 halted47 EL3RST Level 3 reset48 ELNRNG Link number out of range49 EUNATCH Protocol driver not attached50 ENOCSI No CSI structure available51 EL2HLT Level 2 halted52 EBADE Invalid exchange53 EBADR Invalid request descriptor54 EXFULL Exchange full55 ENOANO No anode56 EBADRQC Invalid request code57 EBADSLT Invalid slot59 EBFONT Bad font file format60 ENOSTR Device not a stream61 ENODATA No data available62 ETIME Timer expired63 ENOSR Out of streams resources64 ENONET Machine is not on the network65 ENOPKG Package not installed66 EREMOTE Object is remote67 ENOLINK Link has been severed68 EADV Advertise error69 ESRMNT Srmount error70 ECOMM Communication error on send71 EPROTO Protocol error72 EMULTIHOP Multihop attempted73 EDOTDOT RFS specific error74 EBADMSG Not a data message75 EOVERFLOW Value too large for defined data type76 ENOTUNIQ Name not unique on network77 EBADFD File descriptor in bad state78 EREMCHG Remote address changed292 z/VM: TCP/IP Messages and Codes

SSL MessagesTable 3. SSL Server Reason Codes (continued)Code Name Meaning79 ELIBACC Can not access a needed shared library80 ELIBBAD Accessing a corrupted shared library81 ELIBSCN .lib section in a.out corrupted82 ELIBMAX Attempting to link in too many shared libraries83 ELIBEXEC Cannot exec a shared library directly84 EILSEQ Illegal byte sequence85 ERESTART Interrupted system call should be restarted86 ESTRPIPE Streams pipe error87 EUSERS Too many users88 ENOTSOCK Socket operation on non-socket89 EDESTADDRREQ Destination address required90 EMSGSIZE Message too long91 EPROTOTYPE Protocol wrong type for socket92 ENOPROTOOPT Protocol not available93 EPROTONOSUPPORT Protocol not supported94 ESOCKTNOSUPPORT Socket type not supported95 EOPNOTSUPP Operation not supported on transport endpoint96 EPFNOSUPPORT Protocol family not supported97 EAFNOSUPPORT Address family not supported by protocol98 EADDRINUSE Address already in use99 EADDRNOTAVAIL Cannot assign requested address100 ENETDOWN Network is down101 ENETUNREACH Network is unreachable102 ENETRESET Network dropped connection because of reset103 ECONNABORTED Software caused connection abort104 ECONNRESET Connection reset by peer105 ENOBUFS No buffer space available106 EISCONN Transport endpoint is already connected107 ENOTCONN Transport endpoint is not connected108 ESHUTDOWN Cannot send after transport endpoint shutdown109 ETOOMANYREFS Too many references: cannot splice110 ETIMEDOUT Connection timed out111 ECONNREFUSED Connection refused112 EHOSTDOWN Host is down113 EHOSTUNREACH No route to host114 EALREADY Operation already in progress115 EINPROGRESS Operation now in progress116 ESTALE Stale NFS file handle117 EUCLEAN Structure needs cleaning118 ENOTNAM Not a XENIX named type file119 ENAVAIL No XENIX semaphores available120 EISNAM Is a named type file121 EREMOTEIO Remote I/O error122 EDQUOT Quota exceeded123 ENOMEDIUM No medium found124 EMEDIUMTYPE Wrong medium typeChapter 19. SSL Messages 293

SSL Messages294 z/VM: TCP/IP Messages and Codes

Chapter 20. TCP/IP Server MessagesUnnumbered MessagesThis chapter contains TCPIP server messages.The following message is the only unnumbered message.Error writing file fileid on disk — output haltedSeverity: 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 ofthe 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:Source File:Procedure Name:Output to the file terminates.TCUTIL PASCALReportIoErrorNumbered MessagesThis section contains the numbered messages.DTCATM002I ATM device name: Started sense ondevice; SIOCCcodeExplanation: 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 purposeExplanation: 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:virtual machine storage size.Increase the TCPIPDTCATM011E ATM device name: Unexpected SIOCCcode from Write IDX operation on deviceExplanation: The initial write to an ATM device failedbecause of 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.DTCATM012E IDX Activate failed on input deviceaddress with cause code failureExplanation: The activation of the ATM input deviceat address was rejected with a failure code.System Action:The device is shut down.System Programmer Response:the IBM Support Center.Report the problem toDTCATM021E ATM device name: Unexpected SIOCCcode from Read IDX operation on deviceExplanation: The initial read from an ATM devicefailed because of 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.DTCATM022E IDX Activate failed on output deviceaddress with cause code failureExplanation: The activation of the ATM output deviceat address was rejected with a failure code.System Action:The device is shut down.System Programmer Response:the IBM Support Center.Report the problem to© Copyright IBM Corp. 1987, 2002 295

TCP/IP Server MessagesDTCATM041I ATM device name: PackWrites flushingEnvelopeQueue - Device status: stateExplanation: 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 +1Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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 nameExplanation: More than one ATM physical address isassociated with device name.System Action:address.TCPIP uses the first ATM physicalDTCATM051I ToAtm: OSA reports local address nsapfor device nameExplanation: The ATM physical address for devicename is displayed.DTCATM066E ATM device name: ToAtmUnpackReads: Termination failure codefailureExplanation: OSA has terminated the operation ofATM device name because it detected a failurecondition.System Action:The device is shut down.System Programmer Response:code, take action as follows:CodeActionBased on the failure04 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.otherReport the problem to the IBMSupport Center.DTCATM069I ATM device name: ToAtm: DeferredSioCC code on deviceExplanation: 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM070I ATM device name: ToAtm: Sioreturned code on deviceExplanation: 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM071EExplanation:98.System Action:ToAtm: Diagnose 98 error code codeAn error code was reported by DiagnoseTCPIP continues.System Programmer Response: Determine the causeof the error using the information about Diag 98 errorcodes in the TCP/IP Diagnosis Guide and respond asindicated.296 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCATM073IATM device name: Stored CSW is: cswExplanation: 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM079E ATM device name: Unexpected SIOCCcode from SenseId operation on deviceExplanation: TCPIP was attempting to validate theATM device but received a nonzero condition code inresponse to a Sense ID operation.System Action:The device is shut down.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.DTCATM080IATM initializing:Explanation: TCP/IP is initializing the ATM devicedescribed in subsequent messages.DTCATM081E Link name specifies invalid networktype net_type - ATM will not beinitializedExplanation:ATM.System Action:A link for an ATM device is not of typeThe device is shut down.System Programmer Response:statement.DTCATM082EATM shutting down:Correct the LINKExplanation: 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 deviceExplanation: TCPIP was attempting to validate theATM device but received an unusual Channel StatusWord in response to a Sense ID operation.System Action:The device is shut down.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 deviceExplanation: TCPIP was attempting to validate theATM device but received sense_data in response to aSense ID operation.System Action:The device is shut down.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_dataExplanation: In response to a Unit Check condition ondevice, TCPIP issued a Sense operation and receivedsense_data in response.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.DTCATM089E ATM device name: Channel error ondeviceExplanation:TCPIP received a channel error on device.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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM091E ATM device name: ReceivedDEVICEend interrupt on device --probable OSA restartExplanation: TCPIP received an unsolicited DeviceEnd interrupt on OSA device.System Action:The device is restarted.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.Chapter 20. TCP/IP Server Messages 297

TCP/IP Server MessagesDTCATM092E ATM device name: Unit Check ondeviceExplanation:System Action:TCPIP received a Unit Check on device.The device is shut down.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM093E ATM device name: Unit Exception ondeviceExplanation:device.TCPIP received a Unit Exception onSystem 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM094E ATM device name: Unknown interrupton deviceExplanation:on device.System Action:TCPIP received an unidentified interruptNone.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCATM111I ToAtm: Incoming requests enabled fordevice nameExplanation: Device name is accepting requests toestablish switched virtual circuits.System Action:DTCATM112INone.ToAtm: Starting PVC pvc for link nameExplanation: Private Virtual Circuit pvc for link nameis being started.System Action:DTCATM113INone.ToAtm: Started PVC pvc for link nameExplanation: Private Virtual Circuit pvc for link namehas been established.System Action:None.DTCATM118I ToAtm: Stopping PVC pvc for linknameExplanation: Private Virtual Circuit pvc for link nameis being stopped.System Action:None.DTCATM120I ToAtm: Incoming requests disabledfor device nameExplanation: Device name is no longer acceptingrequests to establish switched virtual circuits.System Action:DTCATM208INone.AtmArpIn: AddTranslation failedExplanation: 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 errorExplanation: TCPIP attempted to get an envelope toreceive the data, but no envelopes were available. Thepacket is discarded.System Action:TCPIP continues.User or Operator Response:programmer about the error.Tell the systemSystem 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+1Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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.298 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesvReview the TCP/IP server configuration file DEVICEand LINK statements that correspond to this device,and ensure that all operands have been correctlyspecified.DTCA22009I A220 device device_name: PackWritesflushing EnvelopeQueue. Device status:statusExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCA22017I A220 device device_name: ToA220:Deferred SioCC rc on device deviceExplanation:System Action:A deferred condition code was received.TCPIP continues.User or Operator Response: If the condition code is 2or 3, check for hardware problems. If other problemsare indicated, you will receive more messages.System Programmer Response:None.DTCA22019I A220 device device_name: ToA220: Sioreturned rc on device deviceExplanation:System Action:A condition code was received.TCPIP continues.User or Operator Response: If the condition code is 2or 3, check for hardware problems. If other problemsare indicated, you will receive more messages.System Programmer Response:None.DTCA22020I A220 device device_name: ToA220: Sioreturned rc on device device Diag 98error code codeExplanation: A diagnostic call returned the indicatederror. For more information about Diag 98 error codes,see the book TCP/IP Planning and Customization.System Action:TCPIP continues.User or Operator Response: Consult the TCP/IPDiagnosis Guide for an explanation of Diag 98 errorcodes and take the indicated action.System Programmer Response:None.DTCA22021I A220 device device_name: Stored CSW is:channel_status_wordExplanation:displayed.System Action:The stored channel status word (CSW) isTCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCA22026I A220 device device_name: UnexpectedSIOCC rc from SenseSt operation.Explanation: A Sense Status command wasunsuccessful. Initialization of this device stops.System Action:TCPIP continues.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:necessary.DTCA22027I A220 initializing: deviceAssist the user asExplanation: The HYPERchannel A220 adapter isinitializing the indicated device.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCA22028I Link link specifies invalid network typenetwork_type. A220 will not be initializedExplanation: The indicated LINK statement specifies anetwork type not recognized by TCPIP. TheHYPERchannel A220 adapter is not initialized.System Action:TCPIP continues.User or Operator Response: Check the LINKstatement for the associated device in the PROFILETCPIP file to make sure that it specifies a valid networktype.System Programmer Response:necessary.DTCA22029EA220 shutting down:Assist the user asExplanation: 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.System Programmer Response:None.Chapter 20. TCP/IP Server Messages 299

TCP/IP Server MessagesDTCA22030I A220 device device_name: UnexpectedCSW from SenseStatistics command ondevice deviceExplanation: A SenseStatistics command wasunsuccessful. Initialization of this device stops.System Action:TCPIP continues.User or Operator Response: Check your hardwareand the PROFILE TCPIP files of the associated devicesfor errors.System Programmer Response:necessary.Assist the user asDTCA22034I A220 device device_name: Channel erroron device deviceExplanation: An unexpected channel error wasencountered. TCPIP expected to find the channel open,but the channel is closed or in use.System Action:TCPIP continues.User or Operator Response:None.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 resetExplanation: The indicated device was interrupted,which probably means the device was reset. A messageshould follow indicating that TCPIP is attempting torestart the device.System Action:TCPIP continues.User or Operator Response:None.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 deviceExplanation: The indicated device encountered anunexpected interrupt.System Action:TCPIP continues.User or Operator Response:errors.System Programmer Response:Check your hardware forNone.DTCA22041I A220 device device_name: Droppingtoo-large output packet length_of_databytesExplanation: The output packet exceeded the size ofthe HYPERchannel A220 adapter’s data buffer. TCPIPdropped the packet.System Action:TCPIP continues.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 knownExplanation: The HYPERchannel A220 adapter isdropping a packet for the indicated host because thehyperchannel address of the host is not known.System Action:TCPIP continues.User or Operator Response:programmer of the error.Notify the systemSystem 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_sizeExplanation: The HYPERchannel A220 adapterreceived a datagram that was too large to fit into anenvelope. The datagram was dropped.System Action:TCPIP continues.User or Operator Response:programmer of the error.Notify your systemSystem 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.300 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCA22044I A220 device device_name: Error gettingXA subchan id for input_address oroutput_addressExplanation: 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 Action:TCPIP continues.User or Operator Response:programmer of the error.Notify the systemSystem 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 deviceExplanation: TCPIP has exceeded the limit for thenumber of attempts to restart the specified device. Thedevice is not initialized.System Action:TCPIP continues.User or Operator Response:programmer of the error.Notify the systemSystem 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: senseinfoExplanation: This message displays sense informationfor the indicated device.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET003I ILANS device device_name: DispatchTr:Cannot process ARP packet; homehardware address not knownExplanation: The ARP packet cannot be processedbecause the IP address has not been found in the ARPcache.System Action:TCPIP continues.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.System Programmer Response:needed.Assist the user asDTCCET005I ILANS device device_name:SET_NET_PARMS.confirm:Explanation: CETI parameters are being checked. Astatus message will follow.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET006I Completion status status, ExtendedStatus statusExplanation: TCPIP completed checking the CETIparameters and is displaying status information.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET007I ILANS initialization aborted due toerrorExplanation: 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.System Programmer Response:None.DTCCET008I ILANS device device_name: SendingDLM_RTV_ATTRIB.requestExplanation: A request was sent to obtain thehardware address; a status message will follow inmessage DTCCET009I.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET009I ILANS device device_name:DLM_RTV_ATTRIB.confirm:Completion status statusExplanation: The hardware address is obtained andchecked, as requested (DTCCET008I) and the status isdisplayed.Chapter 20. TCP/IP Server Messages 301

TCP/IP Server MessagesSystem Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET010I ILANS initialization aborted due toerrorExplanation: Initialization ended because therequested hardware address was not confirmed.System Action:TCPIP continues.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.System Programmer Response:DTCCET011INone.Node address: addressExplanation: This message displays the address of thenode that is currently active and adds this nodeaddress to the IP translation tables.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET012I ILANS device device_name: SendingDL_ACTIVATE_SAP.requestExplanation: A request to open the Logical LinkControl Service Access Point (LLC SAP) to send andreceive unsequenced information frames is being sent.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET013I LengthOfLinkRelated lengthAddressNotRecognized addressFrameNotCopied frameExplanation: The length of the link and destinationaddress are displayed. The frame was not copiedbecause the specified address was not known.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCET014I TransmitStrip strip UnauthorizedApapplication UnauthorizedMf message fileExplanation: This message displays unauthorizedapplications or files.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCET015I SoftError error TransmitBeacon beaconIoaStatusOverrun status Framesdiscarded frames Spurious InterruptcountExplanation: 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.System Action:TCPIP continues.User or Operator Response: If the ring does notrecover, notify your LAN manager.System Programmer Response:None.DTCCET017I FramesTxed number FramesRxednumber MacFramesTxed numberMacFramesRxed numberExplanation: Displays frames (including MAC frames)that were transmitted and received.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET018I RiFramesTxed number RiFramesRxednumber LineError errorExplanation: This message displays frames that weresent by the ring station due to an error in framesequencing.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.302 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCCET019I Internal Error error BurstError errorAriFciError errorExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET020I AbortDelimiter delimiter LostFramenumber RxCongestion congestionExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET021I FrameCopiedError error FrequencyErrorerror TokenError errorExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET022I DmaBusError error DmaParityErrorerror AddressNotRecognized addressExplanation: The destination address was notrecognized due to an error in parity check.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET023I FrameNotCopiedError numberTransmitStripError errorUnauthorizedAp applicationExplanation: This message indicates that TCPIPencountered an unauthorized application whichresulted in an error with frames being transmitted.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET024I UnauthorizedMf message file SoftErrorerror TransmitBeacon beaconExplanation: An unauthorized message file wasdetected causing an interrupt.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET025I IoaStatusOverrun statusFramesDiscarded numberSpuriousInterrupts interruptsExplanation: This message displays the number offrames that were discarded as a result of anunauthorized interrupt.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET026INone.None.Threshold data entry record:Explanation: The following messages displayinformation about the threshold record:v ThresholdCounterId Idv Threshold values: valuesv Threshold counters: valueSystem Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET027INone.None.ThresholdCounterId IdExplanation: This message indicates the number offrames sent by the ring station.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET028IExplanation:values.System Action:None.None.Threshold values: valuesThis message displays the thresholdTCPIP continues.User or Operator Response:System Programmer Response:None.None.Chapter 20. TCP/IP Server Messages 303

TCP/IP Server MessagesDTCCET029IExplanation:counters.System Action:Threshold counters: valueThis message displays the thresholdTCPIP continues.User or Operator Response:System Programmer Response:DTCCET030INone.None.Measurement data entry record:Explanation: The following messages displayinformation about the data measurement record:v OverflowedCounterId valuev Measurement values:System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET031INone.None.OverflowedCounterId valueExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET032INone.None.Measurement values:Explanation: This message displays the message″Measurement values″ with information to follow.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET033INone.None.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’System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET034I NextUpstreamNeighbor address NodeaddressExplanation: This message displays information onthe beaconing ring station’s nearest active upstreamneighbor (NAUN).System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET035INone.None.BeaconTypeSubvector ‘type’Explanation: This message displays the beacon typesubvector. The subvector provides information as to thereason why the ring station is beaconing.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.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’)System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET037I StatusIdentifier ‘status’ StatusCode‘code’ ExtendedStatus ‘status’Explanation:information.System Action:This message displays statusTCPIP continues.User or Operator Response:System Programmer Response:DTCCET038INone.None.Unknown DataFormatType ‘type’Explanation: This message indicates that TCPIP hasencountered a data type it does not recognize.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET039I ILANS device device_name:DL_STATUS.indication received:Explanation: The following messages displayinformation about the status of the data error:DataLength length304 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesStatusType ‘type’ StatusIdentifier ‘identifier’StatusCode ‘code’ OriginalError ‘error’System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCET040INone.DataLength lengthNone.Explanation: This message displays the length of thedata information.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET041I StatusType ‘type’ StatusIdentifier‘identifier’ StatusCode ‘code’ OriginalError‘error’Explanation:on data.System Action:This message displays the status of checkTCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET045I ILANS initialization aborted due toerror.Explanation: ILANS initialization was stopped,possibly because a request to update control blocks wasnot completed.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET046I ILANS device device_name:DL_MSG.confirm: Completion statusstatusExplanation: This message displays the status of theupdating control blocks operation.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET047I ILANS device device_name: UnknownLLC primitive typeExplanation: TCPIP cannot update control blocksbecause of an unknown primitive type.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET049I ILANS device device_name: UnknownMAC primitive typeExplanation: For the MsgType MTYP_MAC, there is aprimitive type other than DLMrtvATTRconf orDLMstatusIND.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET050I ILANS device device_name: UnknownCeti MessageExplanation:unknown.System Action:The MsgType and primitive type areTCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:TCPIP continues.Chapter 20. TCP/IP Server Messages 305

TCP/IP Server MessagesUser 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.System Programmer Response:necessary.Assist the user asDTCCET054I 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.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCET056I ILANS device device_name: SendingSET_NET_Parms.requestExplanation: CETI sends a request to set networkparameters for Level 2 initialization. TCPIP sets thereturn code equal to CETIok.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCET057I ILANS device device_name: Droppingtoo large input, length bytes, max sizeExplanation: The data is too large for the envelopeprovided. The message length and size are displayed.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCE1003I 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE1010I CETI device_type device_name: CetiInitialization FailureExplanation: The I/O operation was not startedresulting in an unsuccessful initialization of the device.TCPIP logs the error.System Action:TCPIP continues.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 statusExplanation: A device error was detected for I/Ooperation. The device type is displayed, its status andthe status of the I/O ports are displayed.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCE1012I Stored CSW: cswNone.None.Explanation: The channel status word (CSW) providesinformation about the termination of I/O operation. Inthis message, CSWStored provides information as towhether data is forthcoming.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE1013I Sense data for device deviceExplanation: Displays status on check of whetherthere is data waiting for the CETI device.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.306 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCCE1014I CETI UNIT CHECK: device device SenseData SFLG: sflg STAT: status OTHR: otherACK: ackExplanation: The following table contains informationpertaining to the sense data of the CETI device.Message DescriptionCETI UNIT CHECKsense data status for the device.Sense Data SFLGsets flag for the sense data.STATstatus of the sense data flag.OTHR if no data has been sensed.ACKacknowledgment of information.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCE1018ENone.None.CETI shutting down:Explanation: The CETI device has shut down. Storagefor data port buffers and channel control words (CCW)is discarded.System Action:User or Operator Response:administrator.CETI halts. TCPIP continues.Inform the systemSystem 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 lengthMaxMsgLenExplanation: The message was rejected because it islarger than allowed by this adapter.System Action:TCPIP continues.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:needed.DTCCE1031I CETI device initializing.Explanation:initialization.System Action:Assist the user asThe CETI device is in the process ofTCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCE1033I DCB invalid for ILANS -- must haveone link of type IBMTRExplanation: The data format is not valid for thisILANS device; it should be in the IBM token ringformat.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCE1034I DCB invalid for X25ICA -- must haveone link of type X25ICAExplanation: The data format is not valid for thisX25ICA device; it should be in the X25ICA format.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCE1037I CETI device_type device_name: Ceti:Flushing output queue; state is devicestatusExplanation: The output queue is being emptied; theenvelopes are being freed.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.Chapter 20. TCP/IP Server Messages 307

TCP/IP Server MessagesDTCCE1038I Ceti driver will set PDSM flagExplanation: The port data status flag (PDSF) is set bythe CETI driver. This flag defines the state of theinbound and outbound ports.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE1039I Error getting XA subchan id fordev_addr+1 or dev_addr or dev_addr+3 ordev_addr+2Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one of thelisted addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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.DTCCE2001I ELANS device name:Explanation: This message displays the name of theEthernet device.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2003I Bad Ethernet trailer packet Type wastype length lengthExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.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.System Action:TCPIP continues.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.System Programmer Response:necessary.DTCCE2007I Net parms record:Assist the user asExplanation: The network parameters are checked andthe status is displayed in the following message(DTCCE2008I).System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2008I Version version Revision revision NetTypetype Flags flagsExplanation: This message displays information aboutthe network parameters. This message followsDTCCE2007I.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2009I Ethernet Address: addressExplanation: This message displays the Ethernetaddress of the message. The Ethernet address is addedto the IP translation table.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2010I Ceti Ethernet Statistics recordExplanation: 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.System Action:TCPIP continues.308 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesUser or Operator Response:System Programmer Response:None.None.DTCCE2011I Frames in number Frames Out numberFrames Lost numberExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2012I Runt Frames number CRC Errors numberCollisions numberExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2013I Multicast In value Broadcast In valueExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2014I Unaddressed frames numberUnaddressed Multi numberExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2015I Excess Collisions number Out of windowCollisions numberExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2016I Alignment errors number ShortedEthernet valueExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2017I Time Delay Reflectometer value Too-longpackets valueExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2018I Ceti Level 2 Error RecordExplanation: These messages display informationfrom the CETI Level 2 Error Record.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2019I Output stat number, ZeroField value,SeqNo numberExplanation: These messages display informationfrom the CETI Level 2 Error Record.System Action:TCPIP continues.Chapter 20. TCP/IP Server Messages 309

TCP/IP Server MessagesUser or Operator Response:System Programmer Response:None.None.DTCCE2020I FlushedSrcEther value,FlushedSetNetParms value,FlushedQueryNetParms valueExplanation: These messages display informationfrom the CETI Level 2 Error Record.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2021I FlushedQueryNetStats valueFlushedOther valueExplanation: These messages display informationfrom the CETI Level 2 Error Record.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.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)System Action:TCPIP continues.User or Operator Response:using a valid message type.System Programmer Response:required.Reissue the messageAssist the operator asDTCCE2025I Dropping packet on link link for firsthop address - ARP resent packet butaddress no goodExplanation: 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.System Action:TCPIP continues.User or Operator Response: Check the HOMEstatement in your PROFILE TCPIP file and make surethat 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:necessary.Assist the user asDTCCE2026I SetExHeader: Cannot send ARP packet;home hardware address not knownExplanation: The ARP packet cannot be processedbecause the home hardware address is not known.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCCE2028I Reading ELANS flags from file nameExplanation: The ELANS flags are read from a file.The file name is displayed.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2029I Using Ethernet flags ‘flags’Explanation:System Action:This message displays Ethernet flags.TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCE2030I Dropping too-large input, length bytes,max sizeExplanation: 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.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user as310 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCCLW004E CLAW device dev_name: Error gettingXA subchan id for dev_addr ordev_addr+1Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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.DTCCLW044E CLAW device name: Claw linkclaw_link_num has no associated LCBExplanation: A CLAW frame was read and the linknumber associated with the CLAW frame is notassigned to any LINK.User or Operator Response:System Programmer Response:None.None.System Action: The frame, and the IP datagram in theframe, is discarded.DTCCLW082EClaw 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 Programmer Response:System Action:None.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.User or Operator Response:None.System Programmer Response: Obtain the correctlevel of the PCA microcode and restart the PCAadapter. Then use the OBEYFILE command to restartthe CLAW device.System Action:The device is stopped.DTCCLW109E Claw device claw_name: Received hostname host_name adapter nameadapter_name, Expected host namehost_name adapter name adapter_nameExplanation: The CLAW device parameters do notmatch the RISC System 6000 PCA adapter configurationparameters.User or Operator Response:None.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.System Action:The device is stopped.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.User or Operator Response:None.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.System Action:The device is stopped.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.User or Operator Response:None.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.System Action:The device is stopped.Chapter 20. TCP/IP Server Messages 311

||||||TCP/IP Server MessagesDTCCLW115E Claw device claw_name: Confirm linklinkid does not match response link linkidExplanation: 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 Programmer Response:System Action:None.The invalid link is disconnected.DTCCTC002E CTCA device device: Started sense ondevice device. SIOCCvalueExplanation: TCPIP received a unit check and starteda sense channel control word (CCW) to get the senseinformation.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCTC004E CTC packet too big:bytestomove=numberExplanation: The CTC packet received is larger thanthe large envelope size.System Action:TCPIP continues.User or Operator Response:None.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 blockExplanation: TCPIP found an error in the packetwhile attempting to unpack the data received.312 z/VM: TCP/IP Messages and Codes||||System Action:TCPIP continues.User or Operator Response:None.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+1Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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.DTCCTC058E CTCA device device: UnexpectedNetwork type: type at positioninput_positionExplanation: The system encountered an unexpectednetwork type as the result of a configuration error.System Action:TCPIP continues.User or Operator Response:None.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, retryingExplanation: A possible configuration error occurredin the LINK statement; the system is retrying the link.The LINK adapter address value might not be valid.System Action:TCPIP continues.User or Operator Response:None.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.

TCP/IP Server MessagesDTCCTC060EError in initialization, no LCB foundExplanation: 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:continues.User or Operator Response:CTC initialization halts. TCPIPNone.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 deviceExplanation:received.System Action:A deferred SIO condition code wasTCPIP continues.User or Operator Response: If the condition code is 2or 3, check for hardware problems.System Programmer Response:None.DTCCTC070I CTCA device device: ToCTCA: Sioreturned rc on device deviceExplanation:System Action:A condition code was received.TCPIP continues.User or Operator Response: If the condition code is 2or 3, check for hardware problems.System Programmer Response:None.DTCCTC071E CTCA device device: Diag 98 errorcode codeExplanation:error.System Action:A diagnostic call caused the indicatedTCPIP continues.User or Operator Response:programming problem.System Programmer Response:Check for aNone.DTCCTC073I CTCA device device: Stored CSW is:cswExplanation: This message precedes the display of astored channel status word (CSW).System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCCTC079E CTCA device device: UnexpectedSIOCC rc from SenseId operation ondevice deviceExplanation: 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.System Action:TCPIP continues.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.System Programmer Response:DTCCTC080IExplanation:System Action:CTCA initializing:

TCP/IP Server MessagesDTCCTC087I CTCA device device: Sense data fordevice device: sense dataExplanation: Sense information was received for thespecified device as the result of a unit check.System Action:TCPIP continues.User or Operator Response:None.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 deviceExplanation:encountered.System Action:An unexpected channel error wasTCPIP continues.User or Operator Response:errors.System Programmer Response:Check your hardware forNone.DTCCTC091E CTCA device device: ReceivedDEVICEend interrupt on device device --probable CTCA restartExplanation: The indicated device was interrupted,which probably means the device was reset.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCCTC092EExplanation:System Action:None.None.Unit Check on device deviceA unit check occurred.TCPIP continues.User or Operator Response: Check the unit checkcode. Check your hardware if needed. Correct theerrors and restart the device.System Programmer Response:None.DTCCTC094EUnknown interrupt on device deviceExplanation: The indicated device encountered anunexpected interrupt.System Action:TCPIP continues.User or Operator Response:errors.System Programmer Response:DTCCTC095ECheck your hardware forNone.Sense ID: value for device deviceExplanation: Data is returned from a Sense ID, andany unexpected data is flagged.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCDIP006E Diag 98 error locking page: CondCodecode, Return code: rcExplanation: 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.ConditionReturn Code incode RY+1Meaning3 1(X‘01’) User is runningvirtual=real3 2(X‘02’) Invalid virtual address3 3(X‘03’) Page unavailable indynamic page area3 4(X‘04’) Page already locked.System Action:TCPIP continues.User or Operator Response:None.System Programmer Response: Respond as indicatedby the return code given in the message.DTCCTC093E Unit Exception on device deviceExplanation: A unit exception occurred on theindicated device.System Action: TCPIP continues.User or Operator Response: Check your hardware forerrors. Check that the opposite side is not out of sync.System Programmer Response: None.DTCDIP077I Discarding IDAW pointer pointer: crossespage boundaryExplanation: 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.System Action:TCPIP continues.User or Operator Response:None.314 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesSystem Programmer Response:None.DTCDIP078I Discarding CCW pointer pointer: crossespage boundaryExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCFPM001E Insufficient CMS storage available forFPSMExplanation: 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 pagesallocatedExplanation: 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.System Action:Processing continues.System Programmer Response:None.DTCFPM005I FPSM may allocate an additional xpages out of yExplanation: 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.System Action:Processing continues.System Programmer Response:None.DTCFPM007E FPSM encountered a Diag 98 errorlocking/unlocking pages: Global RC rcExplanation: 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:CodeReason / Action002 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.ActionThe 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.ActionContact IBM.004 Subfunction is not supported when issuedfrom a 370 virtual machine.ActionThe 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.Chapter 20. TCP/IP Server Messages 315

TCP/IP Server MessagesCodeReason / Action005 Invalid value specified in the Diagnose 98Multiple Request Block DIAG field.ActionContact IBM.006 Invalid value specified in the Diagnose 98Multiple Request Block FCN field.ActionContact IBM.007 Invalid value specified in the Diagnose 98Multiple Request Block LEGNTH field.ActionContact IBM.System Action: TCPIP initializes with default valuesand tries to run.User or Operator Response: Ensure that the PROFILEis properly installed. Reinitialize TCPIP.DTCIPI010IDiagnose 98 real channel programsupport NOT availableExplanation: 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 Action: Processing continues, but may berunning degraded.System Programmer Response:None..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 pageExplanation: 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 Action: Processing continues, but may berunning degraded.System Programmer Response:Contact IBM.DTCIPI001S Insufficient virtual memory availablefor TCP-IPExplanation:System Action:TCPIP has run out of virtual memory.TCPIP halts execution.User or Operator Response:programmer.Contact the systemSystem Programmer Response: Configure the TCPIPvirtual machine for more virtual storage.DTCIPI007E Cannot open a profile fileExplanation: TCPIP could not open its PROFILE file.It first tried to find node_name TCPIP *, thenPROFILETCPIP *, but could find neither file. The profile filespecifies TCPIP configuration information. See theTCP/IP Planning and Customization book for moreinformation.DTCIPI011ILCS devices will use virtual channelprograms via SIOFExplanation: 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.System Action:Processing continues.System Programmer Response:None.DTCIPI028W Not forcing you because you’reconnectedExplanation: 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:User or Operator Response:TCPIP execution continues.None.DTCIPI034S Fatal initialization configuration errordetected, terminating processingExplanation: 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:programmer.Notify the systemSystem Programmer Response: Determine the natureof the error and correct it. When the error is corrected,the TCPIP stack can be started316 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCIPI040S IDENTIFY cannot determine localsystem node name; terminating sinceTCP/IP services may not functionSystem Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.||||||||||||||||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.DTCIPI041IDiagnose 98 block request support NOTavailableExplanation: 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.System Action:Processing continues.System Programmer Response:None.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 andCustomizationSystem 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.DTCIPI053IIgmpHandle: Cannot get envelope topass IGMP to raw clientExplanation: 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 Action:TCPIP continues.||||||||||||||||DTCIPU086I A denial-of-service attack has beendetectedExplanation: 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: ErrorinIUCVoperation code, cc: condition_code, iprcode:IP_request_code, pathid: pathidSeverity:Recoverable error.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:programmer.Notify the systemsSystem 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 blockExplanation: TCPIP found an error in the packetwhile attempting to unpack the data received.System Action:TCPIP continues.User or Operator Response:None.System Programmer Response: Check for aprogramming error on the sending side.User or Operator Response:programmer about the error.Tell the systemChapter 20. TCP/IP Server Messages 317

TCP/IP Server MessagesDTCLDS116I Specific device address for LDSFINITIATE is invalidExplanation: The LDSF (DIAGNOSE X'7C') Initiatefunction was rejected with condition code 3 return code4.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 useExplanation: The LDSF (DIAGNOSE X'7C') Initiatefunction was rejected with condition code 3 return code5.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 yourselfExplanation: 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.User or Operator Response:None.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.System Action:TCPIP continues.User or Operator Response:None.DTCOCP092I Conn n: LU Name LuName LDEVLdevNumber has been dropped becauseTN3270E data string is too longSeverity:InformationalExplanation: 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 thatrepresents the clientldevnumberis the hexadecimal number of the Logicaldevice that represents the clientSystem Action: The offending client is disconnected.User or Operator Response:emulator level.Source File:CopyBuffers () PASCALCheck the client for a badDTCOSD011E OSD device name: Unexpected SIOCCCondition Code from Write IDX operationon deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction during the OSDdriver initialization sequence.System Action:The device is shutdownSystem 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 failureExplanation: The activation of the OSD input deviceat address was rejected with a failure code.System Action:The device is shutdownSystem Programmer Response:the IBM Support Center.Report the problem toDTCOSD020E OSD device name: Unexpected SIOCCCondition Code from Read operation ondeviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction on a Readoperation during the OSD driver initializationsequence.System Action:The device is shutdownSystem Programmer Response:Verify that the OSA318 z/VM: TCP/IP Messages and Codes

TCP/IP Server Messageshardware 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 deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction on a Read IDXoperation during the OSD driver initializationsequence.System Action:The device is shutdownSystem 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 failureExplanation: The activation of the OSD output deviceat address was rejected with a failure code.System Action:The device is shutdownSystem Programmer Response:the IBM Support Center.Report the problem toDTCOSD025E 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 deviceExplanation: TCPIP could not determine thesubchannel identifier for the indicated OSD device.System Action:shutdown.TCPIP continues but the device isSystem 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) 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.vReview the TCP/IP server configuration file DEVICEand LINK statements that correspond to this device,and ensure that all operands have been correctlyspecified.DTCOSD046E OSD Device name: UnexpectedSTSCH CC code for device deviceExplanation: Initial Store Subchannel failed withunexpected condition code.System Action:The device is shutdown.System Programmer Response: Ensure that the OSDdevice is attached to the TCPIP virtual machine.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 Action:The device is shutdown.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 Action:The device is shutdown.System Programmer Response: Ensure that the OSDdevice is configured to a QDIO capable adapter.DTCOSD049E OSD Device name: Device device doesnot have any available CHPIDsExplanation: The initialization process has found thatthe OSD device is not configured with availableCHPIDs (Channel Paths). The device is unusable.System Action:The device is shutdown.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 deviceExplanation: Initial Modify Subchannel instructionfailed with unexpected condition code. TCPIP wasattempting to enable this OSD device for I/Ooperations.System Action:The device is shutdown.Chapter 20. TCP/IP Server Messages 319

TCP/IP Server MessagesSystem Programmer Response: Ensure that the OSDdevice is attached to the TCPIP virtual machine.DTCOSD051EInvalid OSD device groupExplanation: 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 Action:The device is shutdown.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 Action:The device is shutdown.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 deviceExplanation: Initial Clear Subchannel failed withunexpected condition code. TCPIP was attemptingquiesce this OSD device for future I/O operations.System Action:The device is shutdown.System Programmer Response: Ensure that the OSDdevice is attached to the TCPIP virtual machine.DTCOSD054EQDIO queue format is not supportedExplanation: The QDIO hardware adapter supports aqueue format that is currently not supported by thisrelease of z/VM TCP/IP.System Action:The device is shutdown.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/IPExplanation: The QDIO hardware adapter supportsless that one input and or one output queue. z/VMrequires at least this amount to use the device.System Action:The device is shutdown.System Programmer Response: Configure thehardware adapter to support at least the minimumamount of queues required by TCP/IP.DTCOSD066E ToOsd: ProcessReadBuffer:Termination failure code failureExplanation: TCP/IP has received a fatal failure codefrom the adapter during control data exchange.System Action:The device is shutdown.System Programmer Response:the IBM Support CenterDTCOSD071EExplanation:98System Action:Report the problem toToOsd: Diagnose 98 error code codeAn error code was reported by DiagnoseThe 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 deviceExplanation: TCPIP was attempting to validate theOSD device but a nonzero condition code in response toa Sense ID operation.System Action:The device is shutdown.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.DTCOSD080Idev_type Initializing:Explanation: TCPIP is initializing a network devicedescribed in subsequent messages.DTCOSD081E Link name specifies invalid networktype net_type. dev_type will not beinitializedExplanation: A link for the specified device is not asupported link type.System Action:The device not initialized.320 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesSystem Programmer Response: Correct the LINKstatement.DTCOSD082Edev_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 deviceExplanation: 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 Action:The device is shutdown.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 deviceExplanation: TCPIP was attempting to validate thenetwork device but received incorrect senseid_data inresponse to a Sense ID operation.System Action:The device is shutdown.System Programmer Response: Ensure that thenetwork device that is configured in the TCPIPconfiguration file for device name is the correct physicaldevice.DTCOSD089EExplanation:Channel error on deviceTCPIP received a channel error on deviceSystem 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 deviceExplanation: 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 Action:The device is shutdown.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 restartExplanation: TCPIP received an unsolicited DeviceEnd interrupt on OSD deviceSystem Action:The device is restarted.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCOSD092E OSD device name: Unit Check ondeviceExplanation:System Action:TCPIP received a Unit Check on deviceThe device is shutdown.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 ondeviceExplanation:deviceTCPIP received a Unit Exception onSystem 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.DTCOSD094E OSD device name: Unknown Interrupton deviceExplanation:deviceTCPIP received an unknown interrupt onSystem 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.System Programmer Response: Ensure that the OSAhardware is operational. If the problem persists, reportit to the IBM Support Center.Chapter 20. TCP/IP Server Messages 321

TCP/IP Server MessagesDTCOSD100I Insufficient Fixed Page Storage PoolstorageExplanation: 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 Action:The device is shutdown.System Programmer Response: Make more FPSPblocks available by raising the limit fpsb_limit and/orincreasing the virtual machine storage of the TCP/IPvirtual machine.DTCOSD105E Secondary routing node alreadydefinedExplanation: 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 Action:The device is shutdown.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.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.System Action:The device is restarted.DTCOSD102I OSD device name: Restarting devicedevice through AUTORESTARTExplanation: 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 Action:The device is restarted.System Programmer Response: Examine the TCPIPconsole log to determine the cause of the original error.DTCOSD104EPrimary routing node already definedExplanation: 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 Action:The device is shutdown.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.DTCOSD106EOSA Multicast address table is fullExplanation: TCPIP receives this return code from theOSA Express adapter when attempting to register aMulticast address.System Action:continues.The address is not registered, TCPIPSystem 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 alreadyregisteredExplanation: TCPIP receives this return code from theOSA Express adapter when attempting to register aMulticast address.System Action:continues.The address is not registered, TCPIPSystem Programmer Response: Verify that allapplications that are currently connected to TCPIP arefunctioning properly.DTCOSD108E IP address is invalid or already in useby the adapterExplanation: 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 addressSystem Action:continuesSystem Programmer Response:in the TCPIP configuration file.The address is not registered, TCPIPVerify the HOME list322 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCOSD109EAdapter IP address table is fullExplanation: 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 continuesSystem 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.DTCOSD199I OSD device name: ToOsd: Receivedunexpected control data from theadapter for device deviceExplanation: 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.DTCOSD110EIP address was not foundExplanation: 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 continuesSystem 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 connectionExplanation: 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 continuesSystem 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 modeExplanation: TCP/IP recieved an error indication fromthe adapter when it attempted to set theLOCALRINGBCAST broadcast mode.System Action:The device is shutdown.System Programmer Response:the IBM Support Center.Report the problem toDTCOSD114E ToOsd: Unable to set the requestedToken Ring addressing modeExplanation: TCP/IP recieved an error indication fromthe adapter when it attempted to set the CANONICALaddressing mode.System Action:The device is shutdown.System Programmer Response:the IBM Support Center.Report the problem toDTCOSD204E OSD device name: ToOsd: Error statusestablishing a CM-CM connection fordevice deviceExplanation: TCPIP received a connection error statusduring its OSD driver initialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD210E ToOsd: Unexpected status on deviceestablishing CM-CM connection fordevice device_nameExplanation: TCPIP received an unexpected I/Ostatus attempting to establish a CM-CM connectionduring the OSD driver initialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD211E OSD device name: Unexpected SIOCCCondition Code from ENABLE operationon deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction whenattempting an ENABLE operation during the OSDdriver initialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.Chapter 20. TCP/IP Server Messages 323

TCP/IP Server MessagesDTCOSD212E OSD device name: Unexpected SIOCCCondition Code from SETUP operation ondeviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSETUP operation during the OSD driver initializationsequence.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.DTCOSD221E OSD device name: Unexpected SIOCCCondition Code from a START LANoperation on deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSTART LAN operation during the OSD driverinitialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD213E ToOsd: Unexpected status on deviceestablishing USER-USER connection fordevice device_nameExplanation: TCPIP received unexpected I/O statusattempting to establish a USER-USER connectionduring the OSD driver initialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD217E OSD device name: Unexpected SIOCCCondition Code from an ACTIVATEoperation on deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting anACTIVATE operation during the OSD driverinitialization sequence.System Action:The device is shutdownSystem Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.||DTCOSD222E ToOsd: Unexpected status on devicestarting a lan port for device device_nameExplanation: TCPIP received an unexpected I/Ostatus attempting to start a lan port 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.DTCOSD223E OSD device name: ToOsd: Receivedreturn code Return Code from a IPAcmdcommandExplanation: 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.DTCOSD218E ToOsd: Unexpected status on deviceactivating a USER connection fordevice_nameExplanation: TCPIP received unexpected I/O statusattempting to activate a USER connection during theOSD driver initialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD225E ToOsd: Attempt to allocate queues fordevice_name failed with with Return codercExplanation: 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 Action:The device is shutdownSystem 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.324 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCOSD226E ToOsd: Attempt to start queues fordevice_name failed with with Return codercExplanation: 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 Action:The device is shutdownSystem 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 deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aQUERY IP ASSIST operation during the OSD driverinitialization 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.DTCOSD230E OSD device name: Unexpected SIOCCCondition Code from a SET IP assistoperation on deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET IP assist operation during the OSD driverinitialization sequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD231E ToOsd: Unable to set assist assist fordevice_name Return code rcExplanation: 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 deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting a setIP operation during the OSD driver initializationsequence.System Action:The device is shutdown.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 deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET RTG operation during the OSD driver initializationsequence.System Action:The device shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD240E OSD device name: Unexpected SIOCCCondition Code from an IPM operation ondeviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting aSET IPM operation during the OSD driver initializationsequence.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.DTCOSD243E OSD device name: Unexpected SIOCCCondition Code attempting to retry aWrite I/O request on deviceExplanation: TCPIP received an unexpected conditioncode on a Start Subchannel instruction attempting toretry a WRITE operation that previously received anon-critical channel error.System Action:The device is shutdown.System Programmer Response: Verify that the OSAhardware is operational. If the problem persists, recordthe displayed error status and report it to the IBMSupport Center.Chapter 20. TCP/IP Server Messages 325

TCP/IP Server MessagesDTCOSD245I Multicast group address MulticastAddress is not registeredExplanation: TCPIP was unable to register thespecified Multicast Address.System Action:TCPIP continues.System Programmer Response: View the previouslydisplayed messages to determine the actual failure thatmight have prevented the address from beingregistered.DTCOSD246IAssigned IP address IpAddressExplanation: A successful request has been made toset the IpAddress in the OSA Express adapter’s IPaddress table.|||||||||||||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.DTCOSD306IReceived adapter-initiated Start LanExplanation: TCP/IP received a response from adevice indicating that the device is now ready.System Action: TCP/IP continues initializationprocessing for the device.System Programmer Response:None.System Action:TCPIP continuesSystem Programmer Response:None||DTCOSD307E MULTICAST not supported fordevice deviceDTCOSD247IUnassigned IP address IpAddressExplanation: A successful request has been made toremove the IpAddress from the OSA Express adapter’sIP address table.System Action:TCPIP continuesSystem Programmer Response:None|||||||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.|DTCOSD248EError processing IP address IpAddress|DTCOSD309WReceived adapter-initiated Stop Lan|||||||||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.System Action:TCPIP continuesSystem Programmer Response:None|||||||||||||||||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.DTCOSD310EMissing required port nameExplanation: 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.|||||DTCOSD305IWaiting for adapter-initiated Start LanExplanation: 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|||System Programmer Response: Correct the DEVICEstatement in the TCP/IP configuration file to specify aport name.326 z/VM: TCP/IP Messages and Codes

|||||||||||||||DTCOSD311EError in initialization, no LCB foundExplanation: 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:continues.User or Operator Response:Device initialization halts. TCPIPNone.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 Action:TCPIP continues.User or Operator Response:None.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=returncodeExplanation: This message indicates that theConnectExit returned an unsupported return code.System Action:User or Operator Response:The session is terminated.None.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 Action:User or Operator Response:The session is terminated.None.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 Action:User or Operator Response:The session is terminated.None.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.System Action:User or Operator Response:The session is terminated.System Programmer Response:Support Center.None.Contact the IBMDTCOTC043E 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.System Action:User or Operator Response:The session is terminated.System Programmer Response:Support Center.TCP/IP Server MessagesNone.Contact the IBMDTCOTC050I 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.Chapter 20. TCP/IP Server Messages 327

TCP/IP Server MessagesDTCPAR123ISeveral variations of this message existExplanation: This message indicates that an error wasdetected during TCP/IP initialization. The message isself explanatory.System Action:TCPIP continues.User or Operator Response: Correct the problem inthe TCP/IP server configuration file and restart theTCP/IP server.System Programmer Response:required.Assist the operator asDTCPAR129I BSDROUTINGPARMS omitted or inerror; using default routing for all linksExplanation: 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.System Action:None.User or Operator Response: Ensure that routing willbe performed correctly using default subnet masks.DTCPC3002I PCCA3 device name: Started sense ondevice device. SIOCCcodeExplanation: 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.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCPC3003I PCCA3 device name: Cannot getenvelope stringExplanation: TCPIP attempted to get an envelope toreceive the data but no envelopes were available.TCPIP discards the packet.System Action:TCPIP continues.User or Operator Response:programmer about the error.Tell the systemSystem 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: statusExplanation: 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.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCPC3044I PCCA3 device name: FindLinkNumberfails for NetType type AdapternumbernumberExplanation: 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 FDDISystem Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user as328 z/VM: TCP/IP Messages and Codes

TCP/IP Server Messages||||DTCPC3045E PCCA3 device dev_name: Error gettingXA subchan id for dev_addr ordev_addr+1Explanation: TCPIP could not determine thesubchannel identifier that corresponds to one (or both)of the listed addresses for the indicated device.System Action:shutdown.TCPIP continues but the device isSystem 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.DTCPC3046I No link found for count consecutivepackets and no packet received fordefined links - check link configurationExplanation: 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.System Action:The device is shut down.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 blockExplanation: TCPIP encountered an incorrect blockheader on the indicated device. The link on which theerror occurred is unknown. TCPIP drops the block.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCPC3066E PCCA3 device name: Unknown nettype from PCCA: typeExplanation: 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 FDDISystem Action:TCPIP continues.User or Operator Response: See the appropriateoperator’s manual for the device to determine thetroubleshooting procedure.System Programmer Response:necessary.Assist the user asDTCPC3069I PCCA3 device name: ToPcca3: DeferredSioCC rc on device deviceExplanation: 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.System Action:TCPIP continues.User or Operator Response: See the operationsmanual for the system to determine the troubleshootingprocedure.System Programmer Response:necessary.Assist the user asDTCPC3070I PCCA3 device name: ToPcca3: Sioreturned rc on device deviceExplanation: 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 errorIf rc is not 0, other messages follow containingadditional information.System Action:TCPIP continues.User or Operator Response: If rc is not 0, use thesubsequent messages to determine the troubleshootingprocedure.Chapter 20. TCP/IP Server Messages 329

TCP/IP Server MessagesSystem Programmer Response: Assist the user asnecessary.DTCPC3071E PCCA3 devicename: Diag 98 error codeerrorcodeExplanation: The Diag 98 routine generated theindicated error code while performing a diagnosticcheck on the PCCA device.System Action:TCPIP continues.User or Operator Response:None.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: cswExplanation: 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.System Action:TCPIP continues.User or Operator Response: See the Principles ofOperation Manual for the system to determine thetroubleshooting procedure.System Programmer Response:necessary.Assist the user asDTCPC3079E PCCA3 device name: UnexpectedSIOCC code from Senseld operation ondevice deviceExplanation: The indicated device returned anunexpected condition code. TCPIP halts deviceinitialization; the device is no longer available to TCPIP.System Action:TCPIP continues.User or Operator Response: See the operator’s guidefor the device to determine the troubleshootingprocedure.System Programmer Response:DTCPC3080I PCCA3 initializing:None.Explanation: TCPIP is initializing the Lan ChannelStation (LCS).System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCPC3081E Link name specifies invalid networktype networkname. PCCA will not beinitializedExplanation: 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 IBMTRSystem Action:TCPIP continues.User or Operator Response: Correct the LINKstatement. See the book TCP/IP Planning andCustomization for information on specifying the networkname in the LINK statement.System Programmer Response:necessary.DTCPC3082EPCCA3 shutting down:Assist the user asExplanation: The indicated Lan Channel Station (LCS)is shutting down. TCPIP will not use this device.System Action:TCPIP continues.User or Operator Response:None.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 deviceExplanation: TCPIP received an unexpected channelstatus word (CSW) from the indicated device. Thedevice shuts down.System Action:TCPIP continues.User or Operator Response: See the operator’smanual for the device to determine the troubleshootingprocedure.System Programmer Response:necessary.Assist the user asDTCPC3087I PCCA3 device name: Sense data fordevice device: dataExplanation: TCPIP received the indicated sense datafor this device, as a result of a unit check. The deviceshuts down.System Action:TCPIP continues.User or Operator Response: See the operator’smanual for this device to determine the troubleshootingprocedure.330 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesSystem Programmer Response: Assist the user asnecessary.DTCPC3089E PCCA3 device name: Channel error ondevice deviceExplanation: 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.System Action:TCPIP continues.User or Operator Response: See the Principles OfOperation Manual for the system to determine thetroubleshooting procedure.System Programmer Response:necessary.Assist the user asDTCPC3091E PCCA3 device name: ReceivedDEVICEend interrupt on device device --probable PCCA restartExplanation: 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 Action:TCPIP continues.User or Operator Response:None.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 deviceExplanation: TCPIP received a unit check unit statusfor the indicated device. The device shuts down.System Action:TCPIP continues.User or Operator Response: See the operator’smanual for the device to determine the troubleshootingprocedure.System Programmer Response:necessary.Assist the user asDTCPC3093E PCCA3 device name: Unit Exception ondevice deviceExplanation: TCPIP received a unit exception. Unitstatus was received for the indicated device. TCPIPpurges the output queue, if appropriate, and continuesusing the device.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCPC3094E PCCA3 device name: Unknowninterrupt on device deviceExplanation: TCPIP received an unrecognizedinterrupt from the indicated device. TCPIP continuesusing the device.System Action:TCPIP continues.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.System Programmer Response:necessary.Assist the user asDTCPDO036I ProcessIpOptions: unknown option:option source: addressExplanation: While processing an IP datagram, TCPIPdetected an IP option it does not recognize.System Action:User or Operator Response:TCPIP execution continues.None.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_nameExplanation: The FindRoute routine found a route forlink_name in the route table that was a match foraddress. The route is of type route_type, whereroute_typeis one of the following:route_typeDefaultRTEHostRTENetworkRTEDescriptionDefault Routing Table EntryHost Routing Table EntryNetwork Routing Table EntryChapter 20. TCP/IP Server Messages 331

TCP/IP Server MessagesSubnetFoundSupernetFoundSubnetted Routing Table EntrySupernet Routing Table EntryThis 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 foraddressExplanation: 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_nameExplanation: 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_typeDescriptionSubnetRTESubnetted Routing Table EntrySupernetRTESupernetted Routing Table EntryThis 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:addressExplanation: The FindRoute routine has been called tolocate a route to address.DTCPDO081E SOURCEVIPA parameter is notsupported by the current RouteD serverExplanation: 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.DTCPDO082IShutting down RouteD server nameExplanation: 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 datagramExplanation: TCPIP attempted to get an envelope toloopback a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent to theinternal loopback.System Action:TCPIP continues.User or Operator Response:programmer about the error.Tell the systemSystem Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.DTCPDO105IThe known networks:Explanation: The list of routes known by TCPIP isdisplayed after this message.System Action:TCPIP continues.System Programmer Response:None.DTCPDO107I MPRoute server active; equal-costmultipath support enabledExplanation: The EQUALCOSTMULTIPATHparameter was not specified in the ASSORTEDPARMSstatement, but MPROUTE does exploit equal-costmultipath support, so that support has been enabled.System Action:TCPIP execution continues.System Programmer Response:None.DTCPDO108I RouteD server active; equal-costmultipath support disabledExplanation: The ROUTED server does not supportthe EQUALCOSTMULTIPATH parameter specified in332 z/VM: TCP/IP Messages and Codes

TCP/IP Server Messages||||the ASSORTEDPARMS statement, so the support hasbeen disabled.System Action:TCPIP execution continues.System Programmer Response:None.DTCPDO089I SendIGMP: Cannot get envelope tosend IGMP reportExplanation: The routine SendIGMP is unable to getan envelope to send out an IGMP membership report.The IGMP membership is not sent.||||||||||DTCPKT089E Device devicename : LAN task net typetype adapter number number hasterminatedExplanation: 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.System Action:TCPIP continues.User or Operator Response: Stop and restart thedevice. Verify that the hardware is functioning correctly.System Action:TCPIP continues.User or Operator Response:programmer about the error.Tell the systemSystem Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.DTCPKT048E PCCA3 device devicename: Error nn ingetting home hardware address forlinkname number linknumberExplanation: 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 specifiedin PROFILE TCPIP.v a subchannel address pair mismatch.v a hardware error (faulty adapter).System Action:TCPIP execution continues.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-nameExplanation: The indicated device reported a MACaddress of 000000000000.DTCPKT100E Device devicename : Error nn in settingmulticast address for linkname numberlinknumberExplanation: The indicated device was unable to setthe multicast address with the Set IP Multicastcommand. The device will not receive datagramsdestined for this multicast address.System Action:TCPIP continues.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 linknumberExplanation: The indicated device was unable todelete the multicast address with the Delete IPMulticast command.System Action:TCPIP continues.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.System Action:TCPIP execution continues.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.DTCPKT102IReceived QIP assist packetExplanation: A response was received for the QueryIP Assist command.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.Chapter 20. TCP/IP Server Messages 333

TCP/IP Server MessagesDTCPKT103IReceived set ipm packetExplanation: A response was received for the Set IPMulticast command.System Action:TCPIP continues.User or Operator Response:System Programmer Response:DTCPKT104INone.None.Received delete ipm packetExplanation: A response was received for the DeleteIP Multicast command.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.None.DTCPKT105E Device devicename: No control packetreceived in response to Start LanCommandExplanation: 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..System Programmer Response:necessary.DTCPRS003EAssist the user asLine line: Device already startedExplanation: The device_name specified in a STARTstatement has already been started.System Action: TCPIP ignores the START statement;execution continues.User or Operator Response:None.DTCPRS004E Line line: Unable to accept furtherclient namesExplanation: 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 portreservationsExplanation: 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.System Action:TCPIP ignores the PORT statement.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 addressesExplanation: 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.DTCPRS010ILine line: No such userid: UserIDExplanation: You specified an invalid user_id in aPORT statement.System Action:TCPIP ignores the PORT statement.User or Operator Response: Correct the PORTstatement to specify a valid user_id field.DTCPRS011ELine line: Unexpected end of inputExplanation: TCPIP unexpectedly encountered the endof its configuration file.System Action:TCPIP execution continues.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 addressExplanation: TCPIP encountered a non-hexadecimalcharacter in a device address specification. Validcharacters are: 0 through 9, and A through F.System Action:User or Operator Response:TCPIP ignores this statement.Correct the entry.DTCPRS014E Line line: Invalid driver process inGATEWAY commandExplanation: The link_name specified in a GATEWAYstatement is not valid. Links specified in a GATEWAYstatement must be defined in a LINK statement.334 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesSystem Action:Execution continues.User or Operator Response:None.DTCPRS016E Line line: Gateway not directlyaccessible in GATEWAY commandExplanation: 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:statement.TCPIP ignores the GATEWAYUser or Operator Response: Correct the GATEWAYstatement to specify an accessible first_hop address. Forassistance if necessary, see the network administrator.System Action:statement.User or Operator Response:statementTCPIP ignores this GATEWAYCorrect the GATEWAYDTCPRS021E Line line: Zero internet addressspecified in TRANSLATEExplanation: You specified zero as the internet_addressin a TRANSLATE statement.System Action:statement.TCPIP ignores the TRANSLATEUser or Operator Response: Correct theinternet_address specification in this TRANSLATEstatement.DTCPRS017E Line line: Routing loop in GATEWAYcommandExplanation: 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:statement.Correct the GATEWAYDTCPRS018E Line line: Overflow of routing table inGATEWAY commandExplanation: TCPIP has experienced a routing tableoverflow while processing a GATEWAY statement.System Action:statement.TCPIP ignores the GATEWAYUser or Operator Response: Reduce the number ofGATEWAY statements in the configuration file orincrease the size of the IP routing table in theIPROUTEPOOLSIZE statement.DTCPRS022E Line line: No more room inTRANSLATE tableExplanation: The TCPIP translate table is full; youcannot insert any additional entries.System Action:statement.TCPIP ignores the TRANSLATEUser 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 portExplanation: You specified an invalidnumber_of_buffers in a DEVICE statement.System Action:User or Operator Response:statement.TCPIP ignores the DEVICE statement.Correct the DEVICEDTCPRS019E Line line: Unknown network forgateway in GATEWAY commandExplanation: TCPIP did not recognize the networkspecified in a GATEWAY statement.System Action:statement.User or Operator Response:statement.TCPIP ignores the GATEWAYCorrect the GATEWAYDTCPRS020E Line line: Subnet mask conflicts withprev instance of net # in GATEWAYcommandExplanation: The subnet_mask specified in aGATEWAY statement conflicts with a previouslyspecified network number.DTCPRS024E Line line: Invalid threshold field forport portExplanation: The threshold specification in a DEVICEstatement is not valid.System Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the DEVICEstatement.DTCPRS025E Line line: Invalid MyMsgGap field forport portExplanation: You specified an invalid MyMsgGap in aDEVICE statement.System Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the MyMsgGapfield in this statementChapter 20. TCP/IP Server Messages 335

TCP/IP Server MessagesDTCPRS026E Line line: Invalid YrMsgGap field forport portExplanation: You specified an invalid YrMsgGap in aDEVICE statement.System Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the DEVICEstatement.DTCPRS027E Line line: Missing name fieldExplanation: You did not specify a device_name in aDEVICE statement.System Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the DEVICEstatement.DTCPRS028E Line line: Missing type fieldExplanation: You did not specify a device type in aDEVICE statement.System Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the DEVICEstatement.DTCPRS029E Line line: Invalid type fieldExplanation: You specified an invalid device type in aDEVICE statement. Valid types are:v LCSv DDN1822v PVMIUCVv IUCVv SNAIUCVv X25NPSIv ELANSv ILANSv X25ICAv HCHv SHALU62v HIPPIv CLAWv CTCSystem Action: TCPIP ignores the DEVICE statement.User or Operator Response: Correct the DEVICEstatement.User or Operator Response:statement.Correct the DEVICEDTCPRS032E Line line: SNALINK program namemissingExplanation: You did not specify the program nameSNALINK, in a DEVICE statement. This field isrequired for devices of type SNAIUCV.System Action:User or Operator Response:statement.DTCPRS033ETCPIP ignores the DEVICE statement.Correct the DEVICELine line: Remote TCPIP vmid missingExplanation: You did not specify a rmt_tcpip_vmid in aDEVICE statement. This field is required for devices oftype PVMIUCV.System Action:User or Operator Response:statement.DTCPRS034ETCPIP ignores the DEVICE statement.Correct the DEVICELine line: Remote LU name missingExplanation: You did not specify a remote_lu_name in aDEVICE statement. This field is required for devices oftype SNAIUCV.System Action:User or Operator Response:statement.DTCPRS035ETCPIP ignores the DEVICE statement.Correct the DEVICELine line: PVM VM id missingExplanation: You did not specify a local_pvm_vmid in aDEVICE statement. This field is required for devices oftype PVMIUCV.System Action:User or Operator Response:statement.TCPIP ignores the DEVICE statement.Correct the DEVICEDTCPRS030ELine line: Missing device address fieldExplanation: You did not specify a device address inthe DEVICE statement. This field is required fordevices of type: LCS, DDN1822, and HCH.System Action:User or Operator Response:statement.TCPIP ignores the DEVICE statement.Correct the DEVICEDTCPRS036ELine line: SNALINK VM id missingExplanation: You did not specify the snalink_vmid in aDEVICE statement. This field is required for devices oftype SNAIUCV.System Action:User or Operator Response:statement.TCPIP ignores the DEVICE statement.Correct the DEVICEDTCPRS031ELine line: Remote PVM nodeid missingExplanation: You did not specify a rmt_pvm_node in aDEVICE statement. This field is required for devices oftype PVMIUCV.System Action:TCPIP ignores the DEVICE statement.DTCPRS037ELine line: Local PVM nodeid missingExplanation: You did not specify a local_pvm_node in aDEVICE. statement. This field is required for devices oftype PVMIUCV.System Action:TCPIP ignores the DEVICE statement.336 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesUser or Operator Response:statement.Correct the DEVICEUser or Operator Response:statement.Correct the LINKDTCPRS038E Line line: Missing base device addressfieldExplanation: You did not specify a base_device_addr ina DEVICE statement. This field is required for devicesof type: ELANS, ILANS and X25ICA.System Action:User or Operator Response:statement.DTCPRS039ETCPIP ignores the DEVICE statement.Correct the DEVICELine line: Invalid WaitTime fieldExplanation: You specified an invalid wait_time in aDEVICE statement.System Action:User or Operator Response:statementTCPIP ignores the DEVICE statement.Correct the DEVICEDTCPRS045E Line line: LINK statement: Invalid netnumber fieldExplanation: You specified an invalid link_number in aLINK statement.System Action: TCPIP ignores the LINK statement.User or Operator Response: Correct the LINKstatement.DTCPRS046E Line line: LINK statement: Missingdevice name fieldExplanation: You did not specify a device_name in aLINK statement.System Action: TCPIP ignores the LINK statement.User or Operator Response: Correct the LINKstatement.DTCPRS042E Line line: LINK statement: missingname fieldExplanation: 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 fieldExplanation: You did not specify a link type in aLINK statement.System Action: TCPIP ignores the LINK statement.User or Operator Response: Correct the LINKstatement.DTCPRS044E Line line: LINK statement: Invalid typefieldExplanation: You specified an invalid link type in aLINK statement. Valid types are:PRONETIUCVETHERNETHCHETHEROR802.3HIPPI802.3 IPIBMTROFFLOADLINK1FDDIOFFLOADAPIBROADDDN1822OFFLOADAPIPPX25ICAOFFLOADOTHERDTCPRS047E Line line: LINK statement: Duplicatelink nameExplanation: The link_name you specified in a LINKstatement has already been used. You must specifyanother, unique name.System Action:User or Operator Response:statement.TCPIP ignores the LINK statement.Correct the LINKDTCPRS048E Line line: LINK statement: Specifieddevice name not foundExplanation: 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.System Action:TCPIP ignores the LINK 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 deviceExplanation: The device specified in a LINK statementcannot accept additional links.System Action:TCPIP ignores the LINK statement.User or Operator Response: Remove one of the LINKstatements for the device specified in this LINKstatement.System Action:TCPIP ignores the LINK statement.Chapter 20. TCP/IP Server Messages 337

TCP/IP Server MessagesDTCPRS050E Line line: Unknown link name inGATEWAY cmdExplanation: The link_name specified in a GATEWAYstatement was not defined by a LINK statement.System Action:statement.TCPIP ignores the GATEWAYUser 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: valueExplanation: You specified an invalid max_packet_sizein a GATEWAY statement. The size must be a positiveinteger no larger than EnvLargeDatagramSize.System Action:statement.User or Operator Response:statement.TCPIP ignores the GATEWAYCorrect the GATEWAYDTCPRS052E Line line: Subnet mask not compatiblewith network addressExplanation: A GATEWAY statement contains asubnet_mask specification that is incompatible with thenetwork specified.System Action:statement.User or Operator Response:statement.TCPIP ignores the GATEWAYCorrect the GATEWAYDTCPRS053E Line line: Subnet value not compatiblewith subnet maskExplanation: A GATEWAY statement contains asubnet_value specification that is incompatible with thesubnet_mask specified.System Action:statement.User or Operator Response:statement.DTCPRS054ETCPIP ignores the GATEWAYCorrect the GATEWAYLine line: Pool size omittedExplanation: You did not specify a number_of_xxxs ina xxxPOOLSIZE statement.System Action:User or Operator Response:TCPIP ignores the statement.Correct the statement.DTCPRS062ELine line: Unexpected Boolean: wordExplanation: TCPIP expected a command rather thanthe referenced Boolean expression.System Action:statement.User or Operator Response:configuration file statement.TCPIP ignores this configuration fileCorrect the syntax of thisDTCPRS063E Line line: Pool size specifications mustappear before any other commands.Command ignoredExplanation: 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:specification.TCPIP ignores the pool sizeUser or Operator Response: Move the pool sizespecification to the top of the configuration file.DTCPRS064E Line line: Internal client name notvalid in AUTOLOG commandExplanation: 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:statement.TCPIP ignores the AUTOLOGUser or Operator Response: Correct the AUTOLOGstatement within the PROFILE file or the OBEYFILE inwhich this statement occurs.DTCPRS065E Line line: Missing userid inCLIENTPERFOPTIONS commandExplanation: 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 CLIENTPERFOPTIONScommandExplanation: The user ID specification in aCLIENTPERFOPTIONS represents an internal client ofTCPIP. Internal clients cannot be specified in aCLIENTPERFOPTIONS statement.System Action:TCPIP ignores the338 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesCLIENTPERFOPTIONS statement.User or Operator Response: Correct theCLIENTPERFOPTIONS statement in the PROFILEconfiguration file.DTCPRS067E Line line: CLIENTPERFOPTIONSstring too long, ignoredExplanation: 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.DTCPRS068ELine line: Per cent to drop omittedExplanation: 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:statement.Correct the DROPDTCPRS069I Line line: DROP has been disabled atcompilationExplanation: 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.User or Operator Response:None.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 FILEcommandExplanation: 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 HOMEcommandExplanation: You did not specify one or moreparameters in a HOME statement.System Action:User or Operator Response:statement.TCPIP ignores the HOME statement.Correct the HOMEDTCPRS074E Line line: Unknown link name inHOME cmdExplanation: The link_name specified in a HOMEstatement was not defined by a LINK statement.System Action:TCPIP ignores the HOME 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 RESTRICTcommandExplanation: 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: portExplanation: You specified an out-of-rangeport_number in a PORT statement.System Action:TCPIP ignores the PORT statement.User or Operator Response: Correct the PORTstatement in the PROFILE configuration file.DTCPRS077E Line line: The PORT command ismissing a protocolExplanation: You did not specify a protocolspecification in a PORT statement.System Action:User or Operator Response:statement.TCPIP ignores the PORT statement.Correct the PORTDTCPRS078E Line line: Unknown protocol for PORTcommandExplanation: You specified an unknown protocol in aPORT statement. Valid protocols are UDP and TCP.System Action:TCPIP ignores the PORT statement.Chapter 20. TCP/IP Server Messages 339

TCP/IP Server MessagesUser or Operator Response: Correct the PORTstatement.DTCPRS079E Line line: The PORT command ismissing a useridExplanation:statement.System Action:User or Operator Response:statementYou did not specify a user_id in a PORTTCPIP ignores the PORT statement.Correct the PORTDTCPRS080E Line line: No integer specified forSEED commandExplanation: 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:statement.DTCPRS081ECorrect the SEEDLine line: Missing device nameExplanation: You did not specify a device_name in aSTART statement.System Action:User or Operator Response:statement.DTCPRS082ETCPIP ignores the START statement.Correct the STARTLine line: Device not foundExplanation: 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 detailsExplanation: 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.DTCPRS086ELine line: Device not startedExplanation: 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.DTCPRS087ELine line: Missing X25 addressExplanation: You did not specify a net_address in aTRANSLATE statement, with address type X25ICA.System Action:statement.User or Operator Response:statement.DTCPRS088ETCPIP ignores the TRANSLATECorrect the TRANSLATELine line: Missing pronet addressExplanation: You did not specify a net_address in aTRANSLATE statement, with address type PRONET.System Action:statement.User or Operator Response:statement.DTCPRS089ETCPIP ignores the TRANSLATECorrect the TRANSLATELine line: Invalid pronet addressExplanation: The net_address specified in aTRANSLATE statement, with address type PRONET, isan invalid Pronet address.System Action:statement.User or Operator Response:statement.TCPIP ignores the TRANSLATECorrect the TRANSLATEDTCPRS090E Line line: Missing Ethernet, 802.3 orToken Ring addressExplanation: You did not specify a net_address in aTRANSLATE statement, with address type ETHERNET,IBMTR, FDDI, or HCH.System Action:statement.User or Operator Response:statement.TCPIP ignores the TRANSLATECorrect the TRANSLATE340 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCPRS091E Line line: Invalid network inTRANSLATE command: networkExplanation: You specified an invalid network in aTRANSLATE statement. Valid networks are:v X25ICAv PRONETv ETHERNETv IBMTRv FDDIv HCHv HIPPISystem Action:statement.TCPIP ignores the TRANSLATEUser or Operator Response: Correct the networkspecification in the TRANSLATE statement.DTCPRS092E Line line: Unimplemented command:commandExplanation: 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.DTCPRS093ELine line: Unexpected number: numberExplanation: 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:line in the configuration file.Correct the syntax of thisDTCPRS094E Line line: Unknown command:commandExplanation: 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 LUkeywordExplanation: You specified an invalid entry after thekeyword LU on this line of the configuration file.System Action:line.TCPIP ignores this configuration fileUser or Operator Response: Correct the appropriateline in the PROFILE configuration file.DTCPRS116E Line line: Invalid format of UseridUserIDExplanation: The user ID specified on this line of theconfiguration file is in an invalid format.System Action:statement.TCPIP ignores this configuration fileUser or Operator Response: Correct the user IDspecification on this line of the PROFILE configurationfile.DTCPRS117E Line line: Invalid format of LU namenameExplanation: 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 parameterprocessingExplanation: TCPIP encountered an invalid entry typebetween BeginVTAM and EndVTAM statements in theconfiguration file.System Action:User or Operator Response:PROFILE configuration file.TCPIP ignores the statement.Correct the entry in theDTCPRS121E Line line: Invalid entry followingdevice type typeExplanation: You specified an invalid entry followingthis device type on this line of the configuration file.System Action:PROFILE file.TCPIP ignores this line of theUser or Operator Response: Correct the appropriateline of the PROFILE configuration file.DTCPRS122E Line line: Invalid format of ModeTable Name nameExplanation: This mode table name entry in theconfiguration file is too long.System Action:entry.TCPIP ignores the mode table nameUser or Operator Response: Correct the mode tablename entry in the PROFILE configuration fileChapter 20. TCP/IP Server Messages 341

TCP/IP Server MessagesDTCPRS123E Line line: Unrecognized keyword wordprocessing VTAM parameters.Explanation: You referenced an invalid keyword as aVTAM parameter specification.System Action:statement.User or Operator Response:parameter specification.TCPIP ignores this configuration fileCorrect the VTAMDTCPRS124E Line line: Invalid entry followingDEFAULTAPPL keywordExplanation: The entry following a DEFAULTAPPLkeyword is not valid.System Action:statement.TCPIP ignores the DEFAULTAPPLUser or Operator Response: Correct theDEFAULTAPPL entry in the PROFILE configurationfile.DTCPRS125E Line line: Invalid format of DefaultApplication Name nameExplanation: A DEFAULTAPPL statement in thePROFILE configuration file specified a defaultapplication name in an invalid format.System Action:statement.TCPIP ignores the DEFAULTAPPLUser or Operator Response: Correct theDEFAULTAPPL statement in the PROFILEconfiguration file.DTCPRS127E Line line: Invalid format of TelnetApplication Name nameExplanation: The specified TELNET application nameencountered in the PROFILE configuration file is in aninvalid format.System Action:entry.User or Operator Response:configuration file entry.DTCPRS131ETCPIP ignores this configuration fileCorrect the PROFILECLAW host name missingExplanation: The CLAW host name is missing fromthe DEVICE statement.User or Operator Response:None.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:TCPIP.The CLAW device is not defined toDTCPRS132ECLAW adapter name missingExplanation: The CLAW adapter name is missingfrom the DEVICE statement.User or Operator Response:None.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.System Action:TCPIP.The CLAW device is not defined toDTCPRS133E CLAW may only be used with realchannel programsExplanation: CLAW requires the use of theDIAGNOSE X'98' interface and does not run unless theTCPIP virtual machine us authorized to use theinterface.User or Operator Response:None.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.System Action:TCPIP.DTCPRS134EThe CLAW device is not defined toInvalid CLAW read buffer countExplanation: The CLAW read buffer count is notvalid. It must be a positive decimal number.User or Operator Response:None.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.System Action:TCPIP.DTCPRS135EThe CLAW device is not defined toInvalid CLAW write buffer countExplanation: The CLAW write buffer count is notvalid. It must be a positive decimal number.User or Operator Response:None.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.System Action:TCPIP.The CLAW device is not defined to342 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCPRS136EInvalid CLAW read buffer sizeExplanation: The CLAW read buffer size is not valid.It must be one of the following positive decimalnumbers: 1024, 2048, 3172, or 4096.User or Operator Response:None.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.System Action:TCPIP.DTCPRS137EThe CLAW device is not defined toInvalid CLAW write buffer sizeExplanation: The CLAW write buffer size is not valid.It must be one of the following positive decimalnumbers: 1024, 2048, 3172, or 4096.User or Operator Response:None.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.System Action:TCPIP.The CLAW device is not defined toDTCPRS138E 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.User or Operator Response:None.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 TN3270EstatementExplanation: The address specified in a TN3270Eprinter definition in the TCP/IP configuration file is nota valid IP address.System Action:User or Operator Response:statement in error.The statement is ignored.Correct the TN3270EDTCPRS146E Invalid LU name (LUname) in TN3270EstatementExplanation: The LUname specified in a TN3270Eprinter definition in the TCP/IP configuration file is notan identifier of eight or fewer characters in length.System Action:User or Operator Response:statement in error.The statement is ignored.Correct the TN3270EDTCPRS147E Invalid user identifier (userid) inTN3270E statementExplanation: The userid specified in a TN3270E printerdefinition in the TCP/IP configuration file is not anidentifier of eight or fewer characters in length.System Action:User or Operator Response:statement in error.The statement is ignored.Correct the TN3270EDTCPRS148I 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:User or Operator Response:programmer.TCP/IP initialization stops.Notify the systemSystem 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:User or Operator Response:TCP/IP initialization continues.None.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.Chapter 20. TCP/IP Server Messages 343

TCP/IP Server MessagesDTCPRS151I 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 Action:User or Operator Response:TCP/IP initialization continues.None.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 Action:User or Operator Response:TCP/IP initialization continues.None.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 Action:User or Operator Response:TCP/IP initialization continues.None.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.DTCPRS160EMissing NSAP addressExplanation: A 40-hexadecimal-digit physical ATMnetwork address is required on a TRANSLATEstatement.System Action:ignored.System Programmer Response:address.The TRANSLATE statement isSupply the missing|||||||||DTCPRS173E MaxRestart value is missing or is notvalidExplanation: The value for the MAXRESTARTstatement was either missing or was not a numberbetwen 0 and 2,147,483,647.System Action:ignored.System Programmer Response:the MAXRESTART statement.The MAXRESTART statement isCorrect the value inDTCPRS200E LINK statement: Device and link typesare not consistentExplanation: 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.DTCPRS201EVirtual link not valid for GATEWAYExplanation: 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 orSTOPExplanation: 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 statementsExplanation: 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 of344 z/VM: TCP/IP Messages and Codes

variable length subnet masks.DTCPRS204E Subnet masks changed due to conflictsin the BSDROUTINGPARMS statementExplanation: 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 usedExplanation: 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 entryExplanation: 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 HOME list.The link_name is placed at the top ofSystem Programmer Response: Suppress this messageby placing the link_name first in the HOME list.DTCPRS207E Missing PVC name in ATMPVCstatementExplanation: 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.||||||||||||||DTCPRS208EDuplicate PVC name nameExplanation: An ATMPVC statement specifies thename of a PVC that is already defined.System Action:ignored.The duplicate ATMPVC statement isSystem Programmer Response: Correct the PVC nameor remove the duplicate PVC definition.DTCPRS209EMissing link nameExplanation: 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 GATEWAYstatementExplanation: 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.DTCPRS212EATM ARP server name missingExplanation: An ATMARPSERVER statement does notinclude the name of the ATMARP server.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the missingone- to 16-character ATMARP server name.DTCPRS213EDuplicate ATM ARP server name nameExplanation: An ATMARPSERVER statement specifiesthe name of an AMTARP server that is already defined.System Action:ignored.TCP/IP Server MessagesThe ATMARPSERVER statement isSystem Programmer Response: Correct the ATMARPserver name or remove the duplicate server definition.Chapter 20. TCP/IP Server Messages 345

TCP/IP Server MessagesDTCPRS214EATMLIS name missingExplanation: An ATMARPSERVER statement does notinclude the name of the logical IP subnet (defined byan ATMLIS statement) with which the ATMARP serveris associated.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the missingone- to 16-character logical IP subnet name.DTCPRS216E Missing ATM ARP server connectionspecificationExplanation: An ATMARPSERVER statement does notspecify the connection to the ATMARP server.System Action:ignored.The ATMARPSERVER statement isSystem 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).DTCPRS217EMissing PVC nameExplanation: An ATMARPSERVER statement does notinclude the name of the PVC that connects to it.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the one- toeight-character name of the PVC connection to theATMARP server.DTCPRS219EMissing ATM ARP server IP addressExplanation: An ATMARPSERVER statement does notinclude the IP address of the ATMARP server.System Action:ignored.System Programmer Response:of the ATMARP server.DTCPRS220EThe ATMARPSERVER statement isMissing ’NSAP’Supply the IP addressExplanation: An ATMARPSERVER statement does notinclude the word NSAP after the IP address for an SVCconnection.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the wordNSAP followed by the ATM physical address of theATMARP server.DTCPRS221EMissing NSAP addressExplanation: An ATMARPSERVER statement does notinclude the ATM physical address of the ATMARPserver.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the ATMphysical address of the ATMARP server.DTCPRS222EInvalid NSAP addressExplanation: An ATMARPSERVER statement specifiesan invalid ATM physical address for the ATMARPserver.System Action:ignored.The ATMARPSERVER statement isSystem Programmer Response: Supply the valid ATMphysical address of the ATMARP server.DTCPRS223E Invalid ATM ARP server connectionspecificationExplanation: An ATMARPSERVER statement specifiesan unrecognized form of ATMARP server connection.System Action:ignored.The ATMARPSERVER statement isSystem 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).DTCPRS224EMissing ATMLIS nameExplanation: 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.DTCPRS225EDuplicate ATMLIS nameExplanation: An ATMLIS statement specifies the nameof a logical IP subnet that is already defined.System Action:The ATMLIS statement is ignored.System Programmer Response: Correct the logical IPsubnet name or remove the duplicate logical IP subnetdefinition.346 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCPRS226EMissing or invalid subnet valueExplanation: An ATMLIS statement contains a subnetvalue that is not valid.System Action:System Programmer Response:dotted-decimal subnet value.DTCPRS227EThe ATMLIS statement is ignored.Supply theMissing or invalid subnet maskExplanation: An ATMLIS statement contains a subnetmask that is not valid.System Action:System Programmer Response:dotted-decimal subnet mask.The ATMLIS statement is ignored.Supply theDTCPRS228E Subnet mask incompatible withnetwork addressExplanation: An ATMLIS statement specifies a subnetmask that is incompatible with the network address.System Action:The ATMLIS statement is ignored.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 maskExplanation: An ATMLIS statement specifies a subnetmask and a subnet value that are incompatible.System Action:The ATMLIS statement is ignored.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.DTCPRS230EPORTNAME keyword missingExplanation: 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.DTCPRS231EMissing ATM port nameExplanation: A DEVICE statement for an ATM devicedoes not specify the OSA port name.System Action:System Programmer Response:The DEVICE statement is ignored.Supply the OSA portname. It must correspond to the port name defined inthe OSA configuration.DTCPRS232EInvalid ATM device parameterExplanation: A DEVICE statement for an ATM devicespecifies an unrecognized parameter.System Action:System Programmer Response:parameter in error.The DEVICE statement is ignored.Correct or remove theDTCPRS236E Unknown ATMLIS name lis referencedby ATMARP server serverExplanation: 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 serverExplanation: 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 namelinkExplanation: 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 linkExplanation: 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:or LINK statement in error.Correct the ATMPVCChapter 20. TCP/IP Server Messages 347

TCP/IP Server MessagesDTCPRS240E Platform services deficient for OSDdeviceExplanation: These services include the use of theDIAGNOSE X’98’ interface and CP enhancements thatexist in z/VM 3.1.0 and above.System Action:TCP/IP.The OSD device is not defined toSystem 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.DTCPRS241EInvalid OSD device parameterExplanation: A DEVICE statement for an OSD devicespecifies an unrecognized parameter.System Action:System Programmer Response:parameter in error.The device statement is ignored.Correct or remove theDTCPRS242E FPSBs fpsbs exceeds the specifiedFPSB_LIMIT fpsb_limitExplanation: 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.DTCPRS245EMissing OSD port nameExplanation: A DEVICE statement for an OSD devicedoes not specify the OSD port name.System Action:The DEVICE statement is ignored.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 statementExplanation: A DEVICE statement for an OSD devicedid not include the word PORTNAME.System Action:The DEVICE statement is ignored.System Programmer Response: Supply the wordPORTNAME followed by the OSD port name.DTCPRS247E Platform services deficient for OSDdevice supportExplanation: 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:terminated.OSD Device initialization isSystem 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 statementExplanation: 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.System Programmer Response:None.DTCPRS249E SECURE keyword not valid with UDPprotocolExplanation:System Action:User or Operator Response:statement.SSL can be used only with TCP protocol.System Programmer Response:The PORT statement is ignored.Correct the PORTNone.DTCPRS250E SECURE keyword must be specifiedwith port number ’*’Explanation: A port number of ’*’ indicates a secureuser ID, and the SECURE keyword must be used.System Action:The PORT statement is ignored.User or Operator Response: Provide the SECUREkeyword and a certificate label on the PORT statement.System Programmer Response:DTCPRS255ENONE.Missing HIPERS port nameExplanation: A DEVICE statement for a HIPERSdevice does not specify the HIPERS port nameSystem Action:The DEVICE statement is ignored.System Programmer Response: Supply the HIPERSport name. If this adapter is being shared, then use thename that is currently defined for the adapter.348 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||||||||DTCPRS256E PORTNAME keyword missing forHIPERS DEVICE statementExplanation: A DEVICE statement for a HIPERSdevice did not include the word PORTNAME.System Action:The DEVICE statement is ignored.System Programmer Response: Supply the wordPORTNAME followed by the HIPERS port name.DTCPRS257E Invalid PORTNAME specification indevice DEVICE statementExplanation: The PORTNAME parameter is invalid.For example, the port_name specified may be more thaneight characters in length.System Action:The DEVICE statement is ignored.System Programmer Response: Correct the DEVICEstatement to specify a valid port_name.DTCPRS258EDuplicate route ignoredExplanation: This route is a duplicate of one that hasalready been added to the routing tables.System Action:User or Operator Response:statement.The GATEWAY statement is ignored.Remove the GatewayDTCPRS259E Equal-cost route has an incorrect MTUsize; route ignoredExplanation: The MTU size must be the same acrossall multipath routes to one destination.System Action:User or Operator Response:this GATEWAY statement.The GATEWAY statement is ignored.Correct the MTU size inDTCPRS260E Maximum number of equal-cost routesis exceeded; route ignoredExplanation: The maximum number of equal-costroutes allowed to one destination is four. Additionalpaths to this destination are ignored.System Action:User or Operator Response:statement.DTCPRS291IThe GATEWAY statement is ignored.Remove the GatewayTelnet server: TN3270E disabledExplanation: TN3270E support is disabled because theNOTN3270E option was specified on theINTERNALCLIENTPARMS statement in the TCP/IPconfiguration file.System Action:User or Operator Response:TN3270E sessions are not allowed.None.DTCPUP039I XeroxAll failed for foreign internetaddress xx.xx.xx.xx. Setting TextLengthto nnExplanation: 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.System Action:TCPIP continues.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 StateExplanation: An Offload EOF notification has beenreceived while in SendingOnly, ClosingConnection stateand an Offload EOF was not pending.System Action:None.User or Operator Response:None.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 resetExplanation: 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:User or Operator Response:programmer.TCP/IP Server MessagesThe connection is reset.Contact your systemSystem 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.Chapter 20. TCP/IP Server Messages 349

TCP/IP Server MessagesDTCPUP099I Unrecognized TCP option option fromIP address xx.xx.xx.xx is ignoredExplanation:received.An unsupported TCP option has beenSystem Action: The unsupported option is ignored;processing continues with the next option.User or Operator Response:System Programmer Response:None.None.DTCQIO006E Insufficient FPSM storage is availableto allocate buffers for the QDIOHardware FacilityExplanation: 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 transfersExplanation: The specified device number eitherstarted or stopped using the Queued Direct I/OHardward Facility.System Action:Processing continues.System Programmer Response:NoneDTCQUE074I SnapPushPullQueue Don’t know whatqueue - should not be hereExplanation: One of TCPIP’s internal data structureshas been corrupted. The program variable FreeAcbPoolhas been overwritten with an invalid value.System Action:Execution continues.User or Operator Response:programmer.Tell the systemSystem 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 datagramExplanation: TCPIP attempted to get an envelope tosend out a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent.System Action:TCPIP continues.User or Operator Response:Tell the systemprogrammer about the error.System Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.DTCSHU003E No clients are active, so I’ll shutdown at onceExplanation: TCPIP is shutting down. Because TCPIPhas no active clients, it shuts down immediately.System Action:TCPIP shuts down.User or Operator Response:None.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.User or Operator Response:None.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, deviceaddressExplanation: The SNMP subagent sent a NETMANrequest for a 3172 Enterprise Specific MIB variable tothe 3172 at address address. The response that was350 z/VM: TCP/IP Messages and Codes

TCP/IP Server Messagesreceived 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.User or Operator Response:programmer.Contact the systemSystem 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 addressExplanation: 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response:programmer.System Programmer Response:Support Center.Contact the systemContact the IBMDTCSNM003W 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response:programmer.System Programmer Response:Support Center.Contact the systemContact the IBMDTCSNM004W 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response: Reissue the request. If theproblem persists, contact the system programmer.System Programmer Response:Support Center.Contact the IBMDTCSNM006W 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response:programmer.System Programmer Response:Support Center.Contact the systemContact the IBMChapter 20. TCP/IP Server Messages 351

TCP/IP Server MessagesDTCSNM007W 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response:programmer.System Programmer Response:Support Center.Contact the systemContact the IBMDTCSNM008W 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.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response:programmer.System Programmer Response:Support Center.Contact the systemContact the IBMSystem 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.System Action:terminated.User or Operator Response:DTCSTM118IThe incoming Telnet connection isNone.descriptive return code textExplanation: 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.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 physicallyunavailable2. Heavy network traffic that causes the 3172 to notrespond before the NETMAN request timed out3. The NETMAN request was sent to a device whichdoes not actually support the NETMAN request.System Action: The SNMP subagent returns an SNMPresponse of GEN_ERR for the requested mib variable.Processing continues.User or Operator Response: Check the 3172 forhardware problems. Issue the NETSTAT DEVLINKScommand to verify that this device is available toTCP/IP.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:informational message only.System Programmer Response:informational message only.None required;None required;352 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCSTM257E 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.User or Operator Response:programmer about the error.Tell the systemSystem 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 returnedcodeExplanation: The LDSF INITIATE presented by theTelnet server returned a bad return code.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone 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 returnedcodeExplanation: The LDSF INITIATE presented by theTelnet server returned a bad return code.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 rangeExplanation: The Logical device number to be usedfor this Telnet connection exceeds the maximum rangespecified in the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 rangeExplanation: The Logical device number to be usedfor this Telnet connection exceeds the maximum rangespecified in the LDEVRANGE parameters of theINTERNALCLIENTPARMS statement.System Action:terminated.User or Operator Response:The incoming Telnet connection isNone.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 valuesSystem Action:User or Operator Response:LDEVRANGE parm is ignored.None.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 limitExplanation: 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.System Action:None.User or Operator Response:None.DTCSTM267E Telnet server: Conn n: Unable toallocate a data buffer, sessionterminated.Explanation: This message indicates that Telnet wasunable to allocate a data buffer.Chapter 20. TCP/IP Server Messages 353

TCP/IP Server MessagesSystem Action:User or Operator Response:The session is terminated.None.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 Action:TCPIP continues.User or Operator Response:None.System Programmer Response: Correct theConnectExit parameter of theINTERNALCLIENTPARMS statement the the TCPIPconfiguration file.DTCSTM271E Telnet server: Load of ConnextExitfilename failed, Rc =returncodeExplanation: This message indicates that theConnectExit specified on theINTERNALCLIENTPARMS statement could not beloaded.System Action:TCPIP continues.User or Operator Response:None.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 loadaddressExplanation: This message indicates that aConnectExit is active.System Action:TCPIP continues.User or Operator Response:System Programmer Response:None.NoneDTCSTM273I Telnet server: ConnectExit filename isnow inactive, RC=nnExplanation: 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.System Action:TCPIP continues.User or Operator Response:None.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 = codeExplanation:be loaded.The printer management exit could notSystem 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 addressExplanation: The printer management exit calledexitname is loaded at the designated address.System Action: The printer management is invokedwhen TN3270 sessions start and end.User or Operator Response:None.DTCSTM294W Telnet server: Load of Tn3270eExitname is now inactive, Rc = codeExplanation: 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.354 z/VM: TCP/IP Messages and Codes

TCP/IP Server MessagesDTCSTM295I Telnet server: Erase All Unprotected(EAU) data will be ignoredExplanation: 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.User or Operator Response:None.DTCSTM297I Telnet server: Line mode input will bepresented immediatelyExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCSTM298I Telnet server: Line mode input will bepresented when requestedExplanation: 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.User or Operator Response:System Programmer Response:None.None.DTCSTM299I Telnet server: EOJTIMEOUT is valuesecondsExplanation: The INTERNALCLIENTPARMSconfigured value, in seconds, which determines howlong the Telnet server will wait before attempting tosend an EOJ to the TN3270E printer.System Action:None.User or Operator Response:None.DTCSTM300I Telnet server: EOJTIMEOUT valuennn is out of range (1 – 99,999,999);EOJTIMEOUT set to default of 120secondsSeverity:InformationalExplanation: The number of seconds specified for theEOJTIMEOUT operand is not within the indicatedrange of accepted values. Therefore, the stated defaultvalue is in effect.System Action:TCP/IP continues.User or Operator Response:programmer.Notify the systemSystem 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) secondsSeverity:InformationalExplanation: The number of seconds specified for theINACTIVE operand is not within the indicated range ofaccepted values. Therefore, the stated default value isin effect.System Action:TCP/IP continues.User or Operator Response:programmer.Notify the systemSystem 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 600secondsSeverity:InformationalExplanation: The number of seconds specified for theTIMEMARK operand is not within the indicated rangeof accepted values. Therefore, the stated default valueis in effect.System Action:TCP/IP continues.Chapter 20. TCP/IP Server Messages 355

TCP/IP Server MessagesUser or Operator Response: Notify the systemprogrammer.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 datagramExplanation: TCPIP attempted to get an envelope tosend out a multicast datagram but no envelopes wereavailable. The multicast datagram is not sent.System Action:TCPIP continues.User or Operator Response:programmer about the error.Tell the systemSystem Programmer Response: Increase the envelopepool size. See the TCP/IP Planning and Customizationbook for more information on increasing the pool size.DTCUTI001ESerious problem encountered: date timeExplanation: A serious problem was encounteredwhich will be further explained in messageDTCUTI002.System Action:TCP/IP continues.User or Operator Response:None.System Programmer Response: The action requireddepends on the next message which will describe theerror.DTCUTI002ESeveral variations of this message existExplanation: 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 Action:TCP/IP continues.User or Operator Response:None.System Programmer Response: If the problempersists, record the text of the error message andcontact the IBM Support Center.DTCUTI003ESeveral variations of this message existExplanation: This message augments the DTCUTI001Eand DTCUTI002E messages proeviously encounteredand is self explanatory.System Action:TCP/IP continues.User or Operator Response:None.System Programmer Response: If the problempersists, record the text of the error message andcontact the IBM Support Center.DTCUTI043I Diagnose DC error code codeExplanation: 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:records.User or Operator Response:programmer.TCPIP does not produce monitorContact the systemSystem 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.DTCVMS002EError code in command commandExplanation: 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.System Action:Execution continues.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: IDExplanation: 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.System Action:Execution continues.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 file356 z/VM: TCP/IP Messages and Codes

TCP/IP Server Messagesspecified an incorrect user ID. Suspect PROFILEstatements include:v AUTOLOGv CLIENTPERFOPTIONSv INFORMv OBEYv PORTCheck 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 20. TCP/IP Server Messages 357

TCP/IP Server Messages358 z/VM: TCP/IP Messages and Codes

Chapter 21. TCP/IP UtilitiesCONVXLAT MessagesThis chapter contains CONVXLAT, FTPPERM and NFSPERM, HOMETEST,IFCONFIG, IPWIZARD, OBEYFILE, and TCPRUN messages.This 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:Procedure Name:DTCCNX002ESeverity:Error.CMCONVXL PASCALGetParameters,DoItInput file file not foundExplanation: 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.Source File:Procedure Name:DTCCNX003ESeverity:Error.CMCONVXL PASCALDoItPremature EOF on input file fileExplanation: 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.Source File:Procedure Name:DTCCNX004ESeverity:Error.CMCONVXL PASCALDoOneTableError in input line: ″input_record″Explanation: The CONVXLAT command specified anSBCS input file that contained a data error in thespecified line. The line did not contain validhexadecimal codes.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 the TCP/IP Planning and Customization book formore information about customizing DBCS/SBCStranslation tables using CONVXLAT.Source File:Procedure Name:CMCONVXL PASCALDoOneTableDTCCNX005E 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.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 the TCP/IP Planning and Customization book formore information about customizing DBCS/SBCS© Copyright IBM Corp. 1987, 2002 359

CONVXLAT Messagestranslation tables using CONVXLAT.Source File:Procedure Name:CMCONVXL PASCALDoOneTableDTCCNX006E 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.Source File:Procedure Name:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesDTCCNX008W 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.Source File:Procedure Name:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesDTCCNX009W 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.Source File:Procedure Name:DTCCNX010ISeverity:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesCurrent code set is - code_fileInformational.Explanation: This message is displayed when theCODEFILE option of CONVXLAT is used. It indicateswhich codefile is currently being generated.System Action:User or Operator Response:Source File:Procedure Name:Program execution continues.None.CMCONVXL PASCALDoCodeFilesDTCCNX011W 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.Source File:Procedure Name:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesDTCCNX012W 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 about360 z/VM: TCP/IP Messages and Codes

CONVXLAT Messagescustomizing DBCS/SBCS translation tables for use byCONVXLAT.Source File:Procedure Name:DTCCNX013ISeverity:Error.CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesNo SBCS input data in input file fileExplanation: 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.Source File:Procedure Name:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesDTCCNX015I Error in first line of translation data:input_recordSeverity: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 customizingDBCS/SBCS translation tables for use by CONVXLAT.Source File:Procedure Name:DTCCNX016ISeverity:Error.CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesError in DBCS input line: input_recordExplanation: 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.Source File:Procedure Name:DTCCNX017ISeverity:Error.CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesError in SBCS input line: input_recordExplanation: 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.Source File:Procedure Name:CMCONVXL PASCALDoDbcsBinFile, DoCodeFilesFTPPERM and NFSPERM MessagesThis section contains FTPPERM and NFSPERM messages.0010 You do not have a RACF VMBATCHprofile, so you do not need to useprogram_nameSeverity: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.System Action:Command execution stops.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 12for 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.Chapter 21. TCP/IP Utilities 361

FTPPERM and NFSPERM MessagesSource File:FTPPERM EXEC, NFSPERM EXEC0011 User userid does not have a RACFVMBATCH profileSeverity: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.System Action:Command execution stops.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:0012 Syntax ErrorSeverity:Explanation:NFSPERM EXEC, FTPPERM EXECInformational.You have issued the NFSPERM orFTPPERM command incorrectly.System Action:Command execution stops.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.Source File:NFSPERM EXEC, FTPPERM EXEC0013 A RACF/VM error was encountered;ensure filemode A is accessed read/writeSeverity: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.System Action:User or Operator Response:read/write mode.Source File:Command execution stops.Access file mode A inNFSPERM EXEC, FTPPERM EXECHOMETEST MessagesThis section contains the HOMETEST messages.Cannot issue CP Query Userid CommandSeverity:Error.Explanation: The READtcpipDATAfile procedureissued a nonzero return code.System Action:The program halts.User or Operator Response: Determine the nature ofthe problem, correct it, and try again. If the problempersists, contact the IBM Support Center.Source File:Procedure Name:HOMETEST PASCALTestError: Address is not in the HOME ListSeverity:Error.Explanation: The listed IP address could not be foundin the HOME list.System Action:The program continues.User or Operator Response: Correct the IP address inthe HOME list, the name server, or the site tables, andrerun HOMETEST.Source File:Procedure Name:HOMETEST PASCALTestCannot use TCP/IP: ReturnCodeSeverity: Error.Explanation: TCPIP is not available because of thelisted reason.System Action: The program halts.User or Operator Response: Determine the nature ofthe problem, correct it, and try again.Source File: HOMETEST PASCALProcedure Name: TestError: Found no IP addresses corresponding to TCPHost Name: NameSeverity:Error.Explanation: The listed TCP host name could not beresolved because there are no corresponding IPaddresses.System Action:The program continues.User or Operator Response: Correct the HOSTNAMEvariable in the TCPIP DATA file, or the records in thename server or sites tables, and rerun HOMETEST.Source File:Procedure Name:HOMETEST PASCALTest362 z/VM: TCP/IP Messages and Codes

HOMETEST MessagesError: Name resolution through Nameserver wasunsuccessful. Reason: ReturnCodeSeverity:Error.Explanation: The TCP host name could not beresolved using the name server for the listed reason.System Action:The program continues.User or Operator Response: Determine whyHOMETEST cannot communicate with the name server,and rerun HOMETEST.Source File:Procedure Name:HOMETEST PASCALTestInitEmulation failed, try again with ECMODE ONSeverity:Explanation:successful.Error.System Action:TCPIP emulation testing was notThe program halts.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.Source File:Procedure Name:HOMETEST PASCALTest||||||||||||||||||||||||||||||||||||IFCONFIG MessagesDTCIFC2601E Unexpected return code fromcommand; RC=rcThis section contains the IFCONFIG messages.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=rcExplanation: The requested function could not becompleted because of an unexpected return code fromthe indicated command.System Action:Processing continues.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 functionnameExplanation: The IFCONFIG command hasencountered an unexpected condition.System Action:User or Operator Response:Center.Command processing stops.Contact the IBM SupportDTCIFC2603E A read/write minidisk is required touse this functionExplanation: IFCONFIG requires you to have aminidisk accessed read/write so that it can create a||||||||||||||||||||||||||||||||||temporary file used by the TCP/IP OBEYFILEcommand.System Action:Command processing stops.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 functionExplanation: 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.System Action:Command processing stops.User or Operator Response: Update the OBEYstatement and try the command again.DTCIFC2605ETCP/IP stack userid is not availableExplanation: The target TCP/IP stack virtual machineis not logged on.System Action:Command processing stops.User or Operator Response: Start the indicated virtualmachine and try the command again.DTCIFC2606E operand cannot be {specified |changed} for this interfaceExplanation: 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.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andChapter 21. TCP/IP Utilities 363

|||IFCONFIG MessagesDTCIFC2607E {operand | Home IP address} can bespecified only once|||DTCIFC2613E Device {number devno does | numbersdevno1–devno2 do} not exist|||||||||Explanation: The indicated operand or home IPaddress appears more than once in the command thatwas entered.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2608E The type interface specification is notcomplete|||||||||Explanation:System Action:The specified devices do not exist.Command processing stops.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: Required information on the interfacespecification has not been provided.||Explanation: The indicated value is not a recognizedIFCONFIG operand or option.|System Action:Command processing stops.|System Action:Command processing stops.||||||||||||||||||||||||||||||||||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.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2610E The {operand | operand1 or operand2}operand is required, but {has not beenspecified | neither has been specified}Explanation:System Action:User or Operator Response:try the command again.DTCIFC2611EA required operand is missing.Command processing stops.Correct the condition andInterface name already existsExplanation: The specified name is already assignedto another interface.System Action:User or Operator Response:and try the command again.DTCIFC2612EExplanation:System Action:User or Operator Response:try the command again.Command processing stops.Choose another nameUnknown interface: nameThe specified interface does not exist.Command processing stops.364 z/VM: TCP/IP Messages and CodesCorrect the condition and||||||||||||||||||||||||||||||||||User or Operator Response:try the command again.Correct the condition andDTCIFC2615E ″text″ is not a valid CLAW adapternameExplanation: The specified CLAW adapter name is toolong. The name is limited to 16 characters.System Action:User or Operator Response:try the command again.DTCIFC2616ECommand processing stops.Correct the condition and″text″ is not a valid IP addressExplanation: The specified value is not a valid IPaddress. The IP address must be in the range 0.0.0.1 to223.255.255.255.System Action:User or Operator Response:try the command again.DTCIFC2617ECommand processing stops.Correct the condition and″text″ is not a valid CLAW host nameExplanation: The specified CLAW host name is toolong. The name is limited to 8 characters.System Action:User or Operator Response:try the command again.DTCIFC2618ECommand processing stops.Correct the condition and″text″ is not a valid LAN nameExplanation: The specified guest LAN name is toolong. The name is limited to 8 characters.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition and

||||||||||||||||||||||||||||||||||||||||||||||||DTCIFC2619E ″text″ is not a valid minidiskpasswordExplanation: The specified password is too long. Thepassword is limited to 8 characters.System Action:User or Operator Response:try the command again.DTCIFC2620ECommand processing stops.Correct the condition and″text″ is not a valid MTU sizeExplanation: 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.System Action:Command processing stops.User or Operator Response: Consult the device orproduct documentation to determine the correct value.DTCIFC2621E″text″ is not a valid interface nameExplanation: The indicated interface name is not valid.An interface name cannot begin with a dash (—), endwith a colon (:), or contain a semicolon (;).System Action:Command processing stops.User or Operator Response: Try the command againspecifying a valid interface name.DTCIFC2624E″text″ is not a valid port nameExplanation: The specified value is not a valid IBMOpen Systems Adapter port name. The port name islimited to 8 characters.System Action:User or Operator Response:try the command again.DTCIFC2625ECommand processing stops.Correct the condition and″text″ is not a valid port numberExplanation: 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 LCSmode, specify 0 or 1.v For all other LCS devices, specify a number in therange 0-255.v Do not specify a port number for other device types.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition and||||||||||||||||||||||||||||||||||||||||||||||||||DTCIFC2626E″text″ is not a valid device numberExplanation: 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'.System Action:User or Operator Response:try the command again.DTCIFC2627ECommand processing stops.Correct the condition and″text″ is not a valid user IDExplanation: The VM user ID that was specified islonger than 8 characters or contains a semicolon (;) oran asterisk (*).System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2628E operand1 and operand2 are conflictingoperandsExplanation: The indicated operands cannot bespecified at the same time on the IFCONFIG command.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2629E IP address (ipaddr) cannot be abroadcast addressExplanation: The indicated IP address is a broadcastIP address. All of the host bits in the IP address, asdefined by the subnet mask, are ″on.″System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2630E IP address (ipaddr) cannot be the sameas the peer IP addressExplanation:identical.System Action:User or Operator Response:try the command again.DTCIFC2631EIFCONFIG MessagesThe home and peer IP addresses areCommand processing stops.Correct the condition and″mask″ is not a valid subnet maskExplanation: 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.Chapter 21. TCP/IP Utilities 365

IFCONFIG Messages||||||||||||||||||||System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2632E IP address (ipaddr) cannot be the sameas the subnet valueExplanation: 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.″System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2633E MTU size mtu is larger than thatallowed for the corresponding maximumframe size (mfs) for the adapterExplanation: 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).||||||||||||||||||||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: messageExplanation: The requested function could not becompleted because of an unexpected response from theOBEYFILE command.System Action:Processing continues.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 0Explanation: All of the network bits in the indicatedIP address, as defined by the subnet mask, are zero.System Action:Command processing stops.||||||||The MFS for real HiperSocket adapters is controlled bythe IOCDS. The MFS for virtual HiperSocket adaptersis controlled by the CP DEFINE NIC command.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2634E Port number must be 0 or 1||||||||User or Operator Response:try the command again.Correct the condition andDTCIFC2638E Devices devno1–devno2 must be on thesame CHPIDExplanation: All of the device numbers for this devicemust reference the same real device.System Action:Command processing stops.||Explanation: The port number for this device must bespecified as 0 or 1.||User or Operator Response: Correct the problem orspecify the -FORCE option and try the command again.||||||||||||||||||||System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2635E Port number is not within the range0-255Explanation: The port number for this device must bewithin the range 0-255.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2636E An unexpected error was encounteredwhile attempting to modify the activeTCP/IP configuration: messageExplanation: The requested function could not becompleted because of an unexpected response from theOBEYFILE command.System Action: The interface is not defined.Command processing stops.||||||||||||||||||||DTCIFC2639EDevice devno is not of type typeExplanation: 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.DTCIFC2639WDevice devno is not of type typeExplanation: 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,366 z/VM: TCP/IP Messages and Codes

|||||||||||||||||||||||but no communication takes place. An error file fromz/VM TCP/IP is returned.User or Operator Response:start the device.Correct the problem andDTCIFC2640E Network mask 255.255.255.255 is validonly for point-to-point interfacesExplanation: The indicated subnet mask does notconform to the rules for subnet masks for interfacesthat are not point-to-point.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2641W Connection cannot be established;user userid is not logged onExplanation: 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:establish the connection.The indicated user must|||||||||||||||||||||||DTCIFC2644WConnection cannot be establishedExplanation: An unexpected condition wasencountered while trying to establish the requestedconnection. This message is followed by messageDTCIFC2601W.System Action:Processing continues.User or Operator Response: Examine messageDTCIFC2601W to determine the cause of the problem.DTCIFC2645EVirtual interface cannot be createdExplanation: An unexpected error was encounteredwhile creating a needed virtual device. This message isfollowed by message DTCIFC2601E.System Action:Command processing stops.User or Operator Response: Examine messageDTCIFC2601E to determine the cause of the problem.DTCIFC2646E Devices devno1–devno2 are not allattached to user useridExplanation: Some but not all of the real devices thatare needed are attached to the indicated user.System Action:IFCONFIG MessagesCommand processing stops.||||||||||||||||||||||||||DTCIFC2642W Connection cannot be established;virtual CTC devices devno1–devno2 arenot all defined on user useridExplanation: The indicated VM user has not defined avirtual channel-to-channel (CTC) on the indicateddevice numbers. Therefore, the connection cannot beestablished.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 mustdefine a virtual CTC device for the specified devicenumbers to establish the connection.DTCIFC2643W Connection cannot be established;device devno isbusyonuseruseridExplanation: A temporary busy condition has beendetected while trying to establish a virtualchannel-to-channel connection.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 devices must bemanually connected using the CP COUPLE command.|||||||||||||||||||||||||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 typeExplanation: 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.System Action:User or Operator Response:try the command again.Command processing stops.Correct the condition andDTCIFC2648E Interface type (type) is not supportedby IFCONFIGExplanation: You have attempted to display or modifya TCP/IP interface not support by IFCONFIG.System Action:Command processing stops.User or Operator Response: Use the OBEYFILEcommand to change the settings of this interface. Usethe NETSTAT command to display details about theinterface.Chapter 21. TCP/IP Utilities 367

|||||||||||||||||||||||||||||||||IFCONFIG MessagesDTCIFC2649E Device numbers devno1–devno2 areattached to user userid withdiscontiguous virtual device numbersExplanation: All of the listed devices have beenattached to the indicated user, but they are not attachedin a contiguous range of virtual device numbers.System Action:Command processing stops.User or Operator Response: Detach all of the devicesfrom the indicated user and try the command again.DTCIFC2650EDevice number devno is offlineExplanation: The indicated device is defined to thesystem, but is not online.System Action:Command processing stops.User or Operator Response: Choose another device oruse the CP VARY ONLINE command to bring thedevice online and try the command again.DTCIFC2651EDevice number devno is already in useExplanation: The indicated device is already in use bysome other user or by the system.System Action:Command processing stops.User or Operator Response: Choose a different deviceor make the device available, and try the commandagain.DTCIFC2652E Device devno cannot be attached touser useridExplanation: An unexpected error was encounteredwhile attempting to attach the indicated real device.This message is followed by DTCIFC2601E.System Action:Command processing stops.|||||||||||||||||||||||||||||||||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 filemodeExplanation: The z/VM TCP/IP stack virtual machinecannot link to the minidisk which contains thetemporary obey file created by IFCONFIG.System Action:Command processing stops.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 existExplanation: The requested connection cannot beestablished because you specified a user ID that is notdefined to the system.System Action:User or Operator Response:try the command again.DTCIFC2656EExplanation:System Action:Command processing stops.Correct the condition andDevice devno is not availableThe indicated device did not respond.Command processing stops.User or Operator Response: Determine the status ofthe device. Correct the condition or choose anotherdevice and try the command again.DTCIFC2657ELAN name name is of type type||User or Operator Response: Examine messageDTCIFC2601E to determine the cause of the problem.||Explanation: The indicated LAN type does not matchthe requested interface type.|||||||||DTCIFC2652W Device devno cannot be attached touser useridExplanation: An unexpected error was encounteredwhile attempting to attach the indicated real device.This message is followed by DTCIFC2601W.System Action:Processing continues.User or Operator Response: Examine messageDTCIFC2601W to determine the cause of the problem.|||||||||System Action:Command processing stops.User or Operator Response: Choose another LAN oranother interface type and try the command again.DTCIFC2658E Cannot determine device type fordevice devnoExplanation: IFCONFIG cannot verify that yourrequest is valid because the indicated device did notidentify itself to the system.||||DTCIFC2653EDevice devno is attached to user useridExplanation: The indicated device is already attachedto another user.||||System Action:Command processing stops.User or Operator Response: Choose another device,or try the command again with the —Force optionspecified.|System Action:Command processing stops.368 z/VM: TCP/IP Messages and Codes||

||||||||||||||||||||||||||||||||||||||||||||||||||DTCIFC2659E No suitable virtual device numbersare available for useExplanation: There are no usable virtual devicenumbers available on the z/VM TCP/IP stack virtualmachine. You cannot define anymore TCP/IPinterfaces.IPWIZARD MessagesSystem Action:Command processing stops.User or Operator Response: Delete unneeded virtualdevices from the TCP/IP stack virtual machine and trythe command again.This section contains the IPWIZARD messages.|DTCIPW0000E Message repository DTCUME TEXT | DTCIPW2504E Error attempting to FORCE useridcannot be loaded| Explanation: An error occurred while attempting toExplanation: The TCP/IP message repository file | FORCE the specified user ID. The CP FORCE(DTCUME TEXT) is required so messages can be issuedby this program, but this file was not found in the CMS||completed without error, but the user ID was notsuccessfully logged off.search order.| System Action: This message is followed bySystem Action: Command processing stops.| DTCIPW2509E.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:DTCIPW2512E.User or Operator Response:This message is followed byNone.DTCIPW2503E {Pipe command | Command} cmdfailed with return code RC=rcExplanation: The requested function could not becompleted because of an unexpected return code fromthe indicated command.System Action:DTCIPW2509E.This message is followed byUser or Operator Response: Consult the relevantcommand reference to determine the cause of theproblem. After correcting the condition, enter thecommand again.||||||||||||||||||||||||||||||||||||||User or Operator Response: Manually restart thestack and verify its connectivity.DTCIPW2505EError reading data file: datafileExplanation: An error occurred while attempting toread the specified file, which provides informationnecessary for creating configuration files for yourinstallation.System Action:DTCIPW2509E.User or Operator Response:is accessible and readable.This message is followed byVerify that the listed fileDTCIPW2506E 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.System Action:DTCIPW2509E.This message is followed byUser or Operator Response: Consult the TCP/IPserver console log to determine the reason for the error.DTCIPW2507E Error linking TCP/IP 198 and 592disksExplanation: An error occurred while attempting tolink the TCP/IP 198 or 592 disk.System Action:IFCONFIG MessagesCommand processing stops.User or Operator Response: Verify that you canestablish write access to the TCP/IP 198 and 592 disks,and try the command again.Chapter 21. TCP/IP Utilities 369

|||IFCONFIG MessagesDTCIPW2508I execname is attempting to create thenecessary configuration files.|||DTCIPW2517E Connectivity verification was notsuccessful||Explanation: Indicates the program has startedcommand processing.||Explanation: Configuration files have been created butone or more of the connectivity verification tests failed.|System Action:Command processing begins.|System Action:Command processing stops.|||||||||||||||User or Operator Response:None.DTCIPW2509E Unexpected error encountered byexecnameExplanation: An unexpected error occurred duringcommand processing.System Action:Command processing stops.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.|||||||||||||||User or Operator Response:the command again.Modify the data, and tryDTCIPW2518W Configuration files created;connectivity has not been verifiedExplanation: 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.System Action:User or Operator Response:Command processing stops.None.DTCIPW2519I Configuration complete; connectivityhas been verified||||||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.System Action:DTCIPW2509E.This message is followed by|||||Explanation: Configuration files for your installationhave been created, and connectivity verification wassuccessful.System Action:User or Operator Response:Command processing stops.None.|||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.|System Action:Command processing stops.|User or Operator Response:None.||DTCIPW2513EError creating file fn ft fm||Explanation: An error occurred while attempting towrite the specified file to disk.||System Action:DTCIPW2509E.This message is followed by||User or Operator Response: Verify write access to thespecified disk, and enter the command again.|370 z/VM: TCP/IP Messages and Codes

|OBEYFILE MessagesThis section contains the OBEYFILE messages.OBEYFILE MessagesInvalid mode: modeSeverity: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.System Action:The program halts.User or Operator Response: The user should input afile name, file type, and a file mode before entering thepassword.Mode mode is not a minidiskSeverity: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.System Action:The program halts.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 rcSeverity: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.System Action:User or Operator Response:Source File:Server initialization stops.TCPRUN EXECCorrect the error.1002 File file was not found on any accesseddisk or directorySeverity: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.Source File:TCPRUN EXEC1003 :tagname.value specified in fn ft is notvalidSeverity:Explanation:value.Error.System Action:The indicated tag does not have a validServer initialization stops.User or Operator Response: Update the file or exec toprovide a valid value for the tag.Source File:TCPRUN EXEC1004 Missing value for tag :tag. in fn ftSeverity: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.System Action:Server initialization stops.User or Operator Response: Update the DTCPARMSfile or exit exec to include a value for the indicated tag.Source File:TCPRUN EXEC1005 Required tag :tag. was not found in fn1ft1 [or fn2 ft2]Severity:Explanation:Error.The indicated tag was not included inChapter 21. TCP/IP Utilities 371

TCPRUN Messagesthe indicated DTCPARMS file or exit exec, but isrequired.Source File:TCPRUN EXECUser or Operator Response: Update the DTCPARMSfile or exit exec to include the indicated tag and tagvalue.System Action:Source File:Server initialization stops.TCPRUN EXEC1006 Filemode fm is not read/write, but wasspecified on :Diskwarn. in fn ftSeverity: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.System Action:User or Operator Response:mode read/write.Source File:Server initialization stops.TCPRUN EXECAccess the indicated file1007 One or more required libraries were notfoundSeverity:Error.Explanation: The C or Pascal runtime library,SCEERUN or TCPRTLIB LOADLIB, respectively, wasnot found on any accessed disk or directory.System Action:Server initialization stops.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).Source File:TCPRUN EXEC1008 Server [class] name is not defined inuserid, nodeid, SYSTEM or IBMDTCPARMS fileSeverity: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 virtualmachineSeverity:Error.Explanation: An attempt was made to start the serverin a 370-mode virtual machine. This configuration isnot supported.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response: Ensure the server has aMACHINE XA or MACHINE XC statement in its VMdirectory entry.Source File:TCPRUN EXEC1010 userid is not authorized to issue thecommand commandSeverity:Error.Explanation: The server must be able to issue theindicated CP command, but does not have the correctCP privilege class.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response:necessary privilege class.Source File:TCPRUN EXECGive the server the1011 Server started at time on date (weekday)Running "program"Severity:Explanation:System Action:Informational.The server program is starting.Processing continues.User or Operator Response:Source File:TCPRUN EXECNone.1012 Password validation routine name couldnot be foundSeverity:Error.Explanation: The program specified on the:ESM_Validate. tag in DTCPARMS could not be found.The program must be a relocatable MODULE file.System Action:Server initialization stops.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.Source File:TCPRUN EXEC372 z/VM: TCP/IP Messages and Codes

TCPRUN Messages1013 RACROUTE security manager interfacename could not be foundSeverity:Error.Explanation: The program specified on the:ESM_Racroute. tag in DTCPARMS could not be found.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response: Ensure the tag value iscorrect and that the program is on a disk accessed bythe server.Source File:TCPRUN EXEC1014 Server ended normally at time on date(weekday)Severity:Explanation:Informational.The server ended with return code zero.System Action: Processing continues. Server profileexits are called with call type END.User or Operator Response:Source File:TCPRUN EXECNone.1015 Server ended with RC=rc at time on date(weekday)Severity:Explanation:code.Informational.User or Operator Response:The server ended with a nonzero returnNone.System Action: Processing continues. Server profileexits are called with call type END.Source File:TCPRUN EXEC1016 Attempting to define the requiredminimum of {nnK |nnM} of virtualstorageSeverity:Informational.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.Source File:TCPRUN EXEC1017 Filemode fm is nn% fullSeverity: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)System Action:Source File:Processing continues.TCPRUN EXEC1018 No rexec agents found for userid -anonymous rexec not allowedSeverity: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.Source File:TCPRUN EXEC1019 Server will not be logged off becauseyou are connectedSeverity:Informational.Explanation: When you are logged on to the servervirtual machine, server termination will not perform aCP LOGOFF.System Action:Processing continues.User or Operator Response:Source File:TCPRUN EXECNone.1020 :Exit.name specified in fn ft does notexistSeverity:Error.Explanation: The indicated server profile exit, nameEXEC, could not be run because it does not exist.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response: Server profile exitsshould be placed on TCPMAINT 198. Alternatively,remove the :Exit. tag from the DTCPARMS file.Source File:TCPRUN EXECChapter 21. TCP/IP Utilities 373

TCPRUN Messages1021 To cancel server startup, type anynon-blank character and press ENTER.To continue startup, just press ENTERSeverity: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.Source File:TCPRUN EXEC1022 Console log will be sent to user useridSeverity:Informational.Explanation: A server console log will be generatedand sent to the indicated user ID.System Action:Processing continues.User or Operator Response:Source File:TCPRUN EXECNone.1023 Console log has been cancelledSeverity:Informational.Explanation: A blank :Owner. tag has been specifiedin DTCPARMS.System Action: Processing continues. No console logis created; any partial console log is purged.User or Operator Response:Source File:TCPRUN EXECNone.1024 Unable to send console log to user useridSeverity:Informational.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.Source File:TCPRUN EXEC1025 Server program name could not be foundSeverity:Error.Explanation: The command defined on the:Command. tag in DTCPARMS could not be found andthe server could not be started.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response: Ensure the correct disksare accessed and that the server program is available.Source File:TCPRUN EXEC1026 fn EXEC {SETUP | BEGIN} returned"data"Severity:Informational.Explanation: A server profile exit SETUP or BEGINprocessor has returned DTCPARMS override data.System Action:Processing continues.User or Operator Response:Source File:TCPRUN EXECNone.1027 Server will use TcpipUserid useridSeverity:Informational.Explanation: The TCPIP DATA file used by this servercontains a TcpipUserid statement specifying a TCP/IPstack user ID other than the default, TCPIP.System Action:Processing continues.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.Source File:TCPRUN EXEC1028 :Stack.userid1 specified in fn ft does notmatch "TcpipUserid userid2" intheTCPIP DATA fileSeverity: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.System Action: Server initialization stops. Serverprofile exits are called with call type ADMIN.User or Operator Response: If userid2 is correct,change DTCPARMS to specify :Stack.userid2. Ifuserid2is not correct, ensure that the correct 592 (TCP/IPclient) disk is linked and that there are no extraneousTCPIP DATA files in the search order.374 z/VM: TCP/IP Messages and Codes

TCPRUN MessagesSource File:TCPRUN EXEC1029 :tagname option value specified in fn ftfm is not validSeverity:Error.Explanation: The indicated option is not valid for thespecified tag.System Action:Server initialization stops.User or Operator Response: Update the DTCPARMSfile or exit exec to include a valid option and restart theserver. :Source File:TCPRUN EXEC1099 Server not started - correct problem andretrySeverity:Error.Explanation: This message is preceded by one or moremessages that indicate the reason the server was notstarted.System Action:Server initialization stops.User or Operator Response: Correct the indicatedproblem and restart the server.Source File:TCPRUN EXEC1030 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.System Action:Server initialization stops.User or Operator Response: Update the DTCPARMSfile or exit exec to correct the format of the tag andrestart the server.Source File:TCPRUN EXEC1097 Server startup cancelled by fn EXEC,RC=rcSeverity:Informational.Explanation: A server profile exit (SETUP or BEGINprocessing) returned a nonzero return code, signallingthat the server should not be started.System Action:Server initialization stops.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.Source File:TCPRUN EXEC1098 Server startup cancelled at user requestSeverity: Informational.Explanation: The user at the virtual console entered anon-blank value in response to message DTC1021R.System Action: Server initialization stops.User or Operator Response: None.Source File: TCPRUN EXECChapter 21. TCP/IP Utilities 375

TCPRUN Messages376 z/VM: TCP/IP Messages and Codes

Chapter 22. TFTP MessagesCannot load translate table@SayFileName(TranslateTableSpec) : ReturnCodeSeverity:Warning.Explanation: Possible user input or system problem.The requested translation table cannot be found.System Action:None.User or Operator Response: Check the requestedtranslation table file name, and the ReturnCode. Correctyour input and try again.Source File:Procedure Name:TFTP PASCALInitializeProcedure Name: InitializeMissing parm after TRANSLATESeverity: Warning.Explanation: You did not specify a TRANSLATEparameter in the TFTP command.System Action: None.User or Operator Response: Correct your input andtry again.Source File: TFTP PASCALProcedure Name: InitializeCommand Command not known.Severity:Explanation:to TFTP.Warning.System Action:You input a command that is unknownNone.User or Operator Response: Examine your input forerrors and resubmit file transfer request.Source File:Procedure Name:File transfer aborted.Severity:TFPARSE PASCALWarning.HelpExplanation: The requested file transfer wasunsuccessful.System Action:None.User or Operator Response: If other messages are notdisplayed, try the file transfer again. If other messagesfollow this message, take appropriate actions.Source File:Procedure Name:TFTP PASCALTFTPInvalid option word ignoredSeverity:Warning.Explanation: TFTP did not understand the listedoption you specified.System Action:None.User or Operator Response:try again.Source File:TFTP PASCALCorrect your input andNot ConnectedSeverity:Warning.Explanation: You have not established a connectionwith a foreign host. TFTP file transfers are not possiblewith an unconnected system.System Action:None.User or Operator Response: Check to see if the serveron the foreign host is active. Resubmit your TFTPrequest again with a host name.Source File:Procedure Name:TFTP PASCALTFTPTFTP: bad packet count - packet count remains:MaxBlockResentSeverity:Warning.Explanation: The parameter you specified with theMAXPKT command is not valid.System Action:None.User or Operator Response: Check the value youspecified with the MAXPKT command and try again.Source File:Procedure Name:TFTP PASCALTFTPTFTP: bad rexmit interval - rexmit interval remains:RexmitIntervalSeverity:Warning.Explanation: The parameter you specified with theMAXPKT command is not valid.System Action:None.User or Operator Response:Check the value you© Copyright IBM Corp. 1987, 2002 377

TFTP Messagesspecified with the MAXPKT command and try again.Source File:Procedure Name:TFTP PASCALTFTPTFTP: Host address not known.Severity:Warning.Explanation: The requested foreign host address is notin the host ID table.System Action:None.User or Operator Response:try again.Source File:Procedure Name:TFTP PASCALTFTPTFTP: Host Host not known.Severity:Warning.Correct your input andExplanation: The requested foreign host name is notin the host ID table.System Action:None.User or Operator Response:try again.Source File:Procedure Name:TFTP: MessageSeverity:Error.TFTP PASCALInitializeCorrect your input andExplanation: This informational message precedesTFUTIL messages.System Action:None.User or Operator Response:Source File:Procedure Name:TFUTIL PASCALTFTPTFTP: Unknown mode.Severity:Warning.None.Explanation: The transfer mode you specified isunknown to TFTP.System Action:None.User or Operator Response: Ensure that you specifiedeither ASCII or OCTET mode; these are the only validmodes.Source File:Procedure Name:TFTP PASCALTFTPUdpSend: ReturnCodeSeverity:Error.Explanation: This message displays any nonzeroreturn code from the file transfer procedure.System Action:None.User or Operator Response:Source File:Procedure Name:TFUTIL PASCALDispatchUnknown tftp command.Severity:Explanation:Error.System Action:None.You input an unknown command.None.User or Operator Response: Examine your input forerrors and resubmit the command.Source File:Procedure Name:TFTP PASCALTFTPWhereBlock Number = BlockNumberSeverity:Error.Explanation: This message displays the packet in thespecified file where an error caused the file transfer tofail.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintPacketWhereBufsize: bufsize Recfm: recfmSeverity:Error.Explanation: This message displays the buffer sizeand record format of the file in which the transferfailed.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintFscbWhereBytecount: bytecount Longpos: longposSeverity:Error.Explanation: This message displays whether a valuewas specified for longpos and what that value was.378 z/VM: TCP/IP Messages and Codes

TFTP MessagesSystem Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintFscbWhereCommand: command Filename: filename Filetype:filetypeSeverity:Error.Explanation: This message displays the file name andfile type of the file in which the transfer failed.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintFscbWhereError Code = ErrorCodeSeverity:Error.Explanation: Displays the error code at the time thefile transfer failed.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintPacketWhereFilemode: filemode(.1.) filemode(.2.)Severity:Error.Explanation: Displays the minidisks that were linkedwhen the file transfer failed.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:Procedure Name:TFUTIL PASCALPrintFscbWhereFlag: flag ShortRecCount: ShortRecCountSeverity:Error.Explanation: This message displays the value of theShortRecCount parameter.System Action:None.User or Operator Response: Use this message todebug your file transfer request.Source File:TFUTIL PASCALProcedure Name: PrintFscbWhereLongRecCount: LongRecCountSeverity: Error.Explanation: This message displays the value of theLongRecCount parameter.System Action: None.User or Operator Response: Use this message todebug your file transfer request.Source File: TFUTIL PASCALProcedure Name: PrintFscbWhereShortpos: shortposSeverity: Error.Explanation: This message displays the value of theUnsignedHalfWordType parameter.System Action: None.User or Operator Response: Use this message todebug your file transfer request.Source File: TFUTIL PASCALProcedure Name: PrintFscbWhereUnknown packet typeSeverity: Error.Explanation: Trace did not find the block number.System Action: None.User or Operator Response: Use this message todebug your file transfer request.Source File: TFUTIL PASCALProcedure Name: PrintPacketWhereWriteptr: writeptr Readptr: readptrSeverity: Error.Explanation: Displays the position of the read andwrite pointers at the time the file transfer failed.System Action: None.User or Operator Response: Use this message todebug your file transfer request.Source File: TFUTIL PASCALProcedure Name: PrintFscbChapter 22. TFTP Messages 379

TFTP Messages380 z/VM: TCP/IP Messages and Codes

Chapter 23. TFTPD MessagesThis 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.Severity:Informational.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.User or Operator Response:Source File:TFTCMD PLXOption option requires a value.Severity:Error.None.Explanation: An option keyword was specifiedwithout the required option value.System Action:The server shuts down.User or Operator Response: Reissue the TFTPDcommand with the option value included.Source File:TFTCMD PLXPathname specified for CREATION is not validSeverity: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:RC=rc RE=re opening fileSeverity:Explanation:Error.TFTCMD PLX and TFTCON PLXAn unexpected return code and reasoncode 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:PLXTFTHLP PLX, TFTPFL PLX, and TFTUIDRC=rc starting APPLDATA monitoringSeverity:Informational.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 PLXSyntax: CREATION NO or pathnameSeverity:Informational.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 PLXSyntax: DROPFILE pathnameSeverity: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.Source File:TFTCON PLX© Copyright IBM Corp. 1987, 2002 381

TFTPD MessagesSyntax: subcommandSource File:TFTCMD PLXSeverity:Error.Explanation: The indicated subcommand wasspecified with additional operands. The subcommandshould have no operands.System Action:The subcommand ends.User or Operator Response: Reissue the subcommandwithout specifying operands.Source File:TFTCON PLXSyntax: XFERMODE OCTET or RESPECTSeverity:Informational.Explanation: An incorrect number of operands or anincorrect operand was specified on the XFERMODEsubcommand.System Action:The subcommand ends.User or Operator Response: Reissue the XFERMODEsubcommand with the operands specified correctly.Source File:TFTCON PLXUnrecognized value for option operandSeverity: 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 correctlySource File: TFTCMD PLXUnrecognized operand operand -- continuingSeverity: Error.Explanation: An unrecognized operand wasencountered on the TFTPD command line.System Action: The server shuts down.User or Operator Response: Reissue the TFTPDcommand with the operands specified correctly.Source File: TFTCMD PLXUnrecognized option option - continuingSeverity: 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.Source File: TFTCMD PLXUnrecognized port number.Severity: Error.Explanation: An invalid port number was specified.System Action: The server shuts down.User or Operator Response: Reissue the TFTPDcommand with the port number specified correctly.382 z/VM: TCP/IP Messages and Codes

Chapter 24. UFTD MessagesThis chapter contains UFTD messages. Follow the User Response, as appropriate,within each message area to resolve the problem.UFT1200ECode level mis-match: expected level1but found level2Explanation: 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.System Action:User or Operator Response:mismatch and restart UFTD.Source File:UFT8387EThe server shuts down.UFTD EXECCorrect the levelMissing value for statement statementExplanation: A value required on the UFTDconfiguration file statement is missing.System Action:The server shuts down.User or Operator Response: Correct the configurationfile statement and restart UFTD.Source File:UFT8388ETCPSHELI EXECInvalid statement: statementExplanation: The UFTD configuration file statement isunknown or incorrect.System Action:The server shuts down.User or Operator Response: Correct the configurationfile statement and restart UFTD.Source File:UFT8389ETCPSHELI EXECInvalid operand: operandExplanation: An invalid operand was encounteredwhen this command was entered.System Action: The command is not executed, serveroperation continues.User or Operator Response:enter the command again.Source File:TCPSHELL EXECCorrect the operand andUFT8390EInvalid value value for statementstatementExplanation: The UFTD configuration file statementcontains an incorrect value.System Action:The server shuts down.User or Operator Response: Correct the configurationfile statement and restart UFTD.Source File:UFT8391ETCPSHELI EXECMissing keyword: keyword for statementstatementExplanation: The UFTD configuration file statement ismissing a required keyword.System Action:The server shuts down.User or Operator Response: Correct the configurationfile statement and restart UFTD.Source File:UFT8560ITCPSHELI EXECThis UFTD server is not defined inTCPIP DATAExplanation: 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:UFT8564EUFTD EXECCONFIGURATION file: filename filetypenot foundExplanation: The UFTD configuration file UFTDCONFIG was not found on any available file mode.System Action:The server shuts down.User or Operator Response: Locate or create theUFTD CONFIG file and make it available on a UFTDserver visible file mode.© Copyright IBM Corp. 1987, 2002 383

UFTD MessagesSource File:UFT8564ETCHSHELI EXECTRANSLATE file: filename filetype notfoundExplanation: The translation file’s file name and filetype specified by the TRANSLATE statement in theUFTD configuration file was not found on anyavailable file mode.System Action:The server shuts down.User or Operator Response: Correct the configurationfile TRANSLATE statement and restart UFTD.Source File:UFT8565ETCHSHELI EXECError from command command RC=rcExplanation: 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 REXXUFT8566EUser exit filename EXEC not foundExplanation: 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:UFT8567ETCPSHELL EXEC and TCPSHELI EXECUnexpected return from user exitfilename EXEC, RC=rcExplanation: 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:UFT8568ETCPSHELL EXEC and UFTD REXXUnknown UFTD commandExplanation: 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:and enter it again.Source File:UFT8569ETCPSHELL EXECCorrect the commandUnable to establish the Event MonitorEnvironmentExplanation: An error prevented the enablement ofthe event monitor environment.System Action:User or Operator Response:server.Source File:UFT8570IThe server shuts down.TCPSHELL EXECIPL CMS and restart theexit-type exit name has turned off exit-typefunctionExplanation: 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:UFT9002IUFTD REXXFile (*UFT) spooled to userid1 -- origindomain(userid2) date time timezoneExplanation: 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.User or Operator Response:None.384 z/VM: TCP/IP Messages and Codes

UFTD MessagesSource File:UFTD REXXChapter 24. UFTD Messages 385

UFTD Messages386 z/VM: TCP/IP Messages and Codes

Chapter 25. X.25 MessagesX25IPICSeverity:-- Prior command pendingWarning.Explanation: An attempt to post a command to a taskfailed because a previous command is active. When theprevious command completes, the command can bereissued.System Action:The command is ignored.User or Operator Response: Wait for the previouscommand to complete, and reissue the command.Source File:Procedure Name:X25IPICSeverity:Error.xnx25cmd assembleNone.-- Program name must be specifiedExplanation: 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.Source File:Procedure Name:X25IPICSeverity:Error.xnx25cmd assembleNone.-- Task has not been startedExplanation: 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.System Action:The command is ignored.User or Operator Response: Issue the STARTcommand before other commands.Source File:Procedure Name:X25IPICSeverity:Fatal.xnx25cmd assembleNone.-- Task has terminated, user=usersystem=systemExplanation: An attempt to post a command to a taskfailed, because the task had terminated. The taskcompletion codes are reported.System Action:The command is ignored.User or Operator Response:restarted.The task must beSystem Programmer Response: Use the completioncodes to determine the cause of termination.Source File:Procedure Name:X25IPICSeverity:Error.xnx25cmd assembleNone.-- Task is already startedExplanation: This interface task is still active; anothertask cannot run until the current task terminates.System Action:The command is ignored.User or Operator Response: Terminate the previoustask before starting a new one.Source File:Procedure Name:X25IPI099Txnx25cmd assembleNone.WTO text overflowExplanation: XNX25IPI encountered an overflow inthe Write To Operator (WTO) area, which is used todisplay informational and error messages.System Action:X'099' message.The program abends with an ABENDUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the causeof the overflow and submit the ABEND dump to theIBM Support Center.X25IPI911WRefusing IUCV connectionExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.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.© Copyright IBM Corp. 1987, 2002 387

X.25 MessagesX25IPI921ILogon exit refusing sessionExplanation: XNX25IPI is refusing a logon sessionbecause:v The logon was not initiated by X.25 NPSIv 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 expectedv 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.X25IPI931ENetwork services exit: Unrecognizedrequest typeExplanation: 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:not handled.VTAM is notified that the NS RU wasUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Obtain a VTAM traceto determine the Network Services RU type.X25IPI932IExplanation:received.System Action:Network services exit: Cleanup sessionnotification postedA VTAM Cleanup Session RU wasThe VTAM session is terminated.User or Operator Response: None. A failure messagefor the MCH or virtual circuit (VC) session follows.X25IPI933WNetwork services exit: Session initiationfailure notification postedExplanation: 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.X25IPI941TSession control exit: Unrecognized orunexpected request typeExplanation: An unexpected VTAM Session ControlRU was received.System Action:message.X25IPI abends with an ABEND X'941'User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the sourceof VTAM session control request. Submit the ABENDdump to the IBM Support Center.X25IPI942ISession control exit: UNBINDnotification postedExplanation: 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.User or Operator Response:X25IPI981ENone.VTAM terminating, reason unknownExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:of the Shutdown notification.X25IPI982IExplanation:Determine the sourceVTAM HALT issued, drain flag setA 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.X25IPI988IVTAM HALT QUICK or VARY INACT,application issuedExplanation: A VTAM HALT QUICK or VARY INACTrequest was issued.System Action:X25IPI terminates.User or Operator Response: Restart X25IPI, ifappropriate, after VTAM resumes.388 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI989IExplanation:issued.System Action:VTAM HALT CANCEL issuedA VTAM HALT CANCEL request wasX25IPI terminates.User or Operator Response: Restart X25IPI, ifappropriate, after VTAM resumes.X25IPI002EUnrecognized command: commandExplanation: X25IPI encountered an unrecognizedcommand in the console input.System Action:The command is ignored.User or Operator Response: Enter the desiredcommand correctly. See the TCP/IP Planning andCustomization for the X25IPI command syntax.X25IPI003Rprogram name {VM} update level levelExplanation: The version of X25IPI currently runninghas the indicated program name (usually X25IPI) andthe indicated update level.System Action:Execution continues.User or Operator Response:System Programmer Response:when reporting problems.X25IPI011RNone.IP VM userid state stateUse the update levelExplanation: 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 Action:Execution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI011RNone.Use the status inMCH lu state link_state session_stateExplanation: X25IPI status for the indicated MCH isdisplayed. Link_state fields are:FieldX'00'X'10'X'20'X'30'DescriptionRestart neededReadyRestart request sentRestart indication receivedVTAM session_state fields are:FieldX'20'X'30'X'40'DescriptionEnabled for LOGAPPL logonlogon pendingOpeningX'50'X'60'X'70'System Action:Open (ready)ClosingFailedExecution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI011RNone.Use the status inVC vc LU lu DTE address state call_statesession_stateExplanation: X25IPI status for the indicated virtualcircuit is displayed. The call_state fields are:FieldX'00'X'10'X'20'X'30'X'40'X'41'X'42'X'43'X'44'X'50'X'60'X'70'DescriptionWaiting for restart on MCHAvailable for connectionsCall request sentCall request receivedReady for data transferReset request sentReset request receivedInterrupt request sentInterrupt request receivedCall collisionClear request sentClear request receivedThe VTAM session_state fields are:FieldX'00'X'10'X'20'X'30'X'40'X'50'X'60'X'70'System Action:DescriptionDisabled until restart on MCHAvailable for connectionsEnabled for NPSI LU logonLogon pendingOpeningOpen (ready)ClosingFailedExecution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI012RNone.MCH lu SDA at addressUse the status inExplanation: The contents of the session data area(SDA) for this MCH are dumped.System Action:Execution continues.User or Operator Response:System Programmer Response:problem determination.None.Use the data forChapter 25. X.25 Messages 389

X.25 MessagesX25IPI012RVC vc SDA at addressExplanation: The contents of the session data area(SDA) for this VC are dumped.System Action:Execution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI013RNone.Use the data forMCH lu RC: name IP: name SN: name TX:nameExplanation: In response to an EVENTS command,the internal subroutine names handling eventsassociated with this MCH are displayed.SubroutineRCIPSNTXSystem Action:DescriptionVTAM request completeVTAM input pendingVTAM session notificationTimer expiryExecution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI013RNone.Use the data forVC vc RC: name IP: name SN: name TX:nameExplanation: In response to an EVENTS command,the internal subroutine names handling eventsassociated with this virtual circuit is displayed.SubroutineRCIPSNTXSystem Action:DescriptionVTAM request completeVTAM input pendingVTAM session notificationTimer expiryExecution continues.User or Operator Response:System Programmer Response:problem determination.X25IPI014RMCH luNone.Use the data forExplanation: The following X25IPI014R VC messagesapply to virtual circuits on this MCH.System Action:Execution continues.User or Operator Response:X25IPI014RNone.VC vc DTE_address S send_count Rreceive_count D drop_count Q queue_sizeExplanation: The traffic counts for this virtual circuitare displayed.System Action:Execution continues.User or Operator Response:X25IPI014RNone.IP VM user_id S send_count Rreceive_count D drop_count Q queue_sizeExplanation: The traffic counts on the IUCVconnection to the TCPIP virtual machine are displayed.System Action:Execution continues.User or Operator Response:X25IPI021RMCH lu restartingNone.Explanation: X25IPI is restarting this MCH, inresponse to a RESTART command.System Action: A VTAM session is initiated for theNPSI MCH LU.User or Operator Response:X25IPI022ENone.MCH lu unavailableExplanation: 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:through VTAM.Activate the MCH LUSystem Programmer Response: Determine the reasonwhy VTAM refused session initiation.X25IPI023EMCH lu already startedExplanation: X25IPI could not restart this MCH,because it is already active.System Action:Execution continues.User or Operator Response:X25IPI031ENone.MCH mch unknownExplanation: 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.X25IPI077EPosted ECB at address had no handlerExplanation: The X25IPI event control block at thisaddress did not specify an event handler routine.System Action:Execution continues.User or Operator Response: Tell the systemprogrammer about the problem.390 z/VM: TCP/IP Messages and Codes

X.25 MessagesSystem Programmer Response: If the error recurs,obtain a dump of the X25IPI virtual machine.X25IPI085IHALT notice accepted type typeExplanation: 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.User or Operator Response:X25IPI088ITerminatingNone.Explanation: X25IPI is terminating its execution andshutting down.System Action:User or Operator Response:X25IPI090IExplanation:System Action:The VTAM ACB is closed.EndedUser or Operator Response:X25IPI091TNone.X25IPI has finished execution.The X25IPI program exits.None.Stack overflow at frame addressExplanation: X25IPI encountered a stack overflow atthe indicated address.System Action:message.User or Operator Response:programmer.X25IPI abends with an ABEND X'091'Notify the systemSystem Programmer Response: Determine the causeof overflow and submit the ABEND dump to the IBMSupport Center.X25IPI092TBuffer 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:User or Operator Response:programmer.X25IPI abends with return code X'92'.Notify the systemSystem Programmer Response: Determine the causeof the consistency failure and submit the ABEND dumpto the IBM Support Center.X25IPI093SNPSI SEND completion, pending packet= packet numberExplanation: A program flag indicating a deferredcontrol packet to be sent has an unacceptable value.System Action:The pending condition is reset.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:the IBM Support Center.X25IPI101EReport the problem toUnable to open configuration file,DDNAME=X25IPIExplanation: X25IPI encountered an error opening itsconfiguration file.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the FILEDEFor DD for the X25IPI configuration file.X25IPI102EUnrecognized configuration entry:keywordExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:the X25IPI CONFIG file.X25IPI103ECorrect the entry inMissing configuration entry: LINKExplanation: 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 Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Add a Link definitionto the configuration file for each NPSI MCH to be usedfor TCP/IP traffic.X25IPI103EMissing configuration entry: VTAMExplanation: X25IPI could not find a VTAM entry inits configuration file. You must have one VTAM entryto specify the VTAM application ID and password.System Action:X25IPI does not start.Chapter 25. X.25 Messages 391

X.25 MessagesUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Add a Link definitionto the configuration file for each NPSI MCH to be usedfor TCP/IP traffic.X25IPI104EBuffer storage not available (count bytesrequired)Explanation: X25IPI could not allocate sufficientstorage during initialization.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Increase the X25IPIregion or virtual machine memory size by cnt bytes.X25IPI106IUnable to open TCPIP DATA file,DDNAME=X25IPITD; default TCPIPuserid usedExplanation: 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.X25IPI108EIUCV Declare program X25IPI failedR15=valueExplanation: X25IPI encountered an error issuing aGCS IUCVINI SET macro.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Check the VM userdirectory entry for the X25IPI virtual machine.X25IPI109TProgramming error: not enough buffersallocatedExplanation: The calculation of the number of buffersto allocate was incorrect.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Notify the IBMX25IPI111EUnrecognized trace level: levelExplanation: 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:entry in the configuration file.X25IPI201IExplanation:ACB.System Action:Correct the TraceVTAM ACB application openedsuccessfullyX25IPI successfully opened the VTAMExecution continues.User or Operator Response:X25IPI121ENone.Repeated VTAM record ignored: recordExplanation: X25IPI encountered more than oneVTAM entry in the configuration file.System Action: The repeat VTAM record is skipped;initialization continues.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:VTAM record.X25IPI122ERemove the repeatVTAM application name missingExplanation: The VTAM application ID is missing onthe VTAM entry in the configuration file.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Specify the VTAMapplication ID and password on the VTAM entry.X25IPI123EVTAM application password missingExplanation: The VTAM application password ismissing on the VTAM entry in the configuration file.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Specify the VTAMapplication password on the VTAM entry.392 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI129EVTAM ACB application open failedExplanation: X25IPI encountered an error opening theVTAM ACB. This message is preceded by a X25IPI201Eor X25IPI202E message reporting the VTAM error code.System Action:X25IPI does not start.User or Operator Response:application in VTAM.Activate the X25IPISystem Programmer Response: Use the VTAM errorcode from the X25IPI201E or X25IPI202E message todetermine the reason for the failure of the VTAM ACBOPEN macro.X25IPI131EDDN and non-DDN links cannot bemixedExplanation: X25IPI encountered Link statements inits configuration file specifying both DDN andnon-DDN links.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: DDN and non-DDNlinks must be segregated into two X25IPI virtualmachines.X25IPI132ELink LU name missingExplanation: The NPSI MCH LU name is missing onthe Link entry in the configuration file.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Linkentry. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI133ELink DTE address missingExplanation: X25IPI encountered a Link statementwithout a DTE address specified. This field is requiredfor all non-DDN links.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Linkentry. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI134ELink window size missing or notnumericExplanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericdefault window size specification.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the windowsize. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI135ELink window size not in range 1..7 or1..127Explanation: X25IPI encountered a Link statement inits configuration file with an invalid default windowsize specification. The window size must be in therange 1—7 or1—127.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.X25IPI136ECorrect the windowLink packet size missing or not numericExplanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericdefault packet size.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the packetsize. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI137ELink packet size unacceptableExplanation: 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 Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.Correct the packetChapter 25. X.25 Messages 393

X.25 MessagesX25IPI138ELink logical channel count missing ornot numericExplanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericlogical channel count field.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the channelcount. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI139ELink logical channel count not in range1..1023Explanation: X25IPI encountered a Link statement inits configuration file with an invalid logical channelcount field. The count must be in the range 1—1023.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:count.X25IPI140ECorrect the channelLink reserved channel count missing ornot numericExplanation: X25IPI encountered a Link statement inits configuration file that had a missing or nonnumericreserved channel count.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the reservedchannel count. See TCP/IP Planning and Customizationfor the format of the Link definition.X25IPI141ELink reserved channel count not inrange 1..LCCExplanation: 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 Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the reservedchannel count. See TCP/IP Planning and Customizationfor the format of the Link definition.X25IPI142ELink data network code missingExplanation: 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).System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Linkentry. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI143EData network identifier code notdecimalExplanation: X25IPI encountered a Link statement inits configuration file that specified a nondecimal datanetwork identifier code (DNIC). The DNIC must bedecimal.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the DNICnumber. See TCP/IP Planning and Customization for theformat of the Link definition.X25IPI144ELink DTE address not decimalExplanation: X25IPI encountered a Link statement inits configuration file that contained a nondecimal DTEaddress.System Action: The Link entry is discarded; furthererrors can result.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address.X25IPI151ECorrect the DTEDest record not preceded by Link recordExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Move the Dest recordafter the corresponding Link record.394 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI152EDest IP address missingExplanation: X25IPI encountered a Dest record in itsconfiguration file that did not specify an IP address.System Action:The Dest entry is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Destentry. See TCP/IP Planning and Customization for theformat of the Dest record.X25IPI153EDest IP address must be decimalExplanation: X25IPI encountered a Dest record in itsconfiguration file specifying a nondecimal destinationaddress. The destination address must be indotted-decimal form.System Action:The Dest entry is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the IPaddress. See TCP/IP Planning and Customization for theformat of the Dest record.X25IPI154EDest DTE address missingExplanation: 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 Action:The Dest entry is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Destrecord with the X.25 DTE address. See TCP/IP Planningand Customization for the format of the Dest record.X25IPI155EDest DTE address must be decimalExplanation: 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 Action:The Dest entry is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:address.Correct the DTEX25IPI156EDest call user data must be hexadecimalExplanation: X25IPI encountered a Dest record in itsconfiguration file specifying nonhexadecimal call userdata (CUD) protocol ID. The CUD must behexadecimal.System Action:The Dest entry is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:data.X25IPI161ECorrect the call userDatagram size limit missing or notnumericExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Buffersrecord with the datagram size limit. See TCP/IPPlanning and Customization for the format of the Destrecord.X25IPI162EDatagram size limit not in range576...2048Explanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size limit.X25IPI163ECorrect the datagramExtra buffer count missing or notnumericExplanation: X25IPI encountered a Buffers record inits configuration file that had a missing or nonnumericbuffer count field.System Action:The extra buffer count is ignored.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:count.Correct the bufferChapter 25. X.25 Messages 395

X.25 MessagesX25IPI164EVC send queue limit missing or notnumericExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:limit.X25IPI171ECorrect the queueInactivity timeout missing or notnumericExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Complete the Timersrecord with the inactivity time-out. See TCP/IP Planningand Customization for the format of the Dest record.X25IPI182EOption name not recognized nameExplanation: X25IPI encountered an Options record inits configuration file with an unrecognized optionname.System Action:is skipped.The remainder of the Options recordUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the optionname. See TCP/IP Planning and Customization for theformat of the Options record.X25IPI183EOption packet size missing or notnumericExplanation: X25IPI has encountered an Optionsstatement in its configuration file that has a missing ornonnumeric packet size specification.System Action:is skipped.The remainder of the Options recordUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.Correct the packetX25IPI172EMinimum call timer missing or notnumericExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:call time.Correct the minimumX25IPI184EOption packet size unacceptableExplanation: 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.System Action:is skipped.The remainder of the Options recordUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.Correct the packetX25IPI181EOptions record not preceded by LinkrecordExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Move the Optionsrecord after the corresponding Link record.X25IPI185EOption window size missing or notnumericExplanation: XNX25IPI encountered an Optionsstatement in its configuration file that had a missing ornonnumeric window size.System Action:is skipped.The remainder of the Options recordUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.Correct the window396 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI186EOption window size not in range 1..7 or1..127Explanation: XNX25IPI encountered an Optionsstatement in its configuration file that specified aninvalid window size. The window size must be in therange 1—7 or1—127.System Action:is skipped.The remainder of the Options recordUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:size.X25IPI201ECorrect the windowVTAM GENCB failed, R15=valueR0=valueExplanation: A VTAM GENCB call failed, with theindicated R15 and R0 values.System Action:X25IPI does not start.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Reassemble X25IPIwith the most recent VTAM macro library.X25IPI202EVTAM ACB OPEN failed, R15=valueACBERFLG=valueExplanation: A VTAM OPEN request failed, with theindicated R15 and ACBERFLG values.System Action:X25IPI does not start.User or Operator Response:application in VTAM.Activate the X25IPISystem Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB OPEN macro.X25IPI215EVTAM SETLOGON QUIESCE failed,RTNCD=value FDB2=valueExplanation: A VTAM SETLOGON QUIESCE requestfailed with the indicated return code and FDB2 values.System Action:X25IPI termination continues.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM SETLOGON macro.X25IPI221EVTAM ACB CLOSE failed, R15=valueACBERFLG=valueExplanation: A VTAM CLOSE request failed with theindicated return values.System Action:X25IPI termination continues.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM CLOSE macro.X25IPI241EVTAM CLSDST RELEASE lu failed,RTNCD=value FDB2=valueExplanation: A VTAM CLSDST RELEASE failed withthe indicated return code and FDB2 values.System Action: Execution continues. The virtualcircuit can become unusable.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI241EVTAM OPNDST ACCEPT lu failed,RTNCD=value FDB2=valueExplanation: A VTAM OPNDST ACCEPT failed withthe indicated return code and FDB2 values.System Action: Execution continues. The virtualcircuit can become unusable.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI241EVTAM OPNDST ACQUIRE lu failed,RTNCD=value FDB2=valueExplanation: 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 forUser or Operator Response: Activate the NPSI MCHin VTAM. Use the X25IPI RESTART command toreacquire the MCH LU.Chapter 25. X.25 Messages 397

X.25 MessagesSystem Programmer Response: Use the VTAM errorcode to determine the reason for the failure of theVTAM ACB OPNDST macro. manual restart.X25IPI241EVTAM RECEIVE lu failed,RTNCD=value FDB2=valueExplanation: 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.X25IPI241EVTAM SEND lu failed, FDB2=valueExplanation: A VTAM SEND REQ failed with theindicated FDB2 value.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 SEND macro.X25IPI241EVTAM SEND RESP EX lu failed,RNTCD=value FDB2=valueExplanation: A VTAM SEND RESP EX 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 SEND macro.X25IPI241EVTAM SEND RESP NEX lu failed,RTNCD=value FDB2=valueExplanation: A VTAM SEND RESP NEX failed withthe indicated 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 SEND macro.X25IPI255EVTAM 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 CodeX'17'X'1F'X'22'X'23'DescriptionOPNDSTCLSDSTSENDRECEIVESystem 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 OPEN macro.X25IPI313IMCH lu restartingExplanation: An X.25 restart exchange has beenstarted on the NPSI MCH.System Action:Execution continues.User or Operator Response:X25IPI315ENone.MCH lu open failedExplanation: 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.398 z/VM: TCP/IP Messages and Codes

X.25 MessagesUser 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.X25IPI316EMCH lu OPNDST did not completeExplanation: 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.System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for manual restart.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.X25IPI320IExplanation:connections.System Action:MCH lu packet level readyX25IPI has initialized this MCH forExecution continues.User or Operator Response:X25IPI322INone.MCH lu discarded packet during restartExplanation: X25IPI received an invalid packet whilerestarting this MCH.System Action:discarded.User or Operator Response:X25IPI323IThe invalid packet is dumped andNone.MCH lu restart indication, cause=valuediagnostic=valueExplanation: 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.25User or Operator Response: None. restart procedureis used to place the MCH back in operation.X25IPI324IExplanation:this MCH.System Action:connections.MCH lu restart confirmationUser or Operator Response:X25IPI330IX25IPI received a restart confirmation forThe MCH is marked ready for newNone.MCH lu restart completeExplanation: X25IPI has completed terminating virtualcircuits on an MCH undergoing restart.System Action: An X.25 restart confirmation is sent tocomplete the restart procedure.User or Operator Response:X25IPI331INone.MCH lu restart indication, cause=cause,diagnostic=diagnosticExplanation: 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.User or Operator Response:X25IPI332INone.MCH lu restart confirm packet sentExplanation: X25IPI transmitted a restart confirmationpacket for this MCH.System Action:dumped.User or Operator Response:X25IPI334IExplanation:The restart confirmation packet isMCH lu restartingNone.X25IPI is restarting the indicated MCH.System Action: X25IPI waits to receive a restartconfirmation on the MCH.User or Operator Response:X25IPI342INone.MCH lu diagnostic packetExplanation: X25IPI received an X.25 diagnosticpacket on this MCH.System Action:discarded.User or Operator Response:The diagnostic packet is dumped andNone.Chapter 25. X.25 Messages 399

X.25 MessagesSystem Programmer Response: Use the diagnosticpacket to obtain additional information about X.25network problems.X25IPI342IMCH lu orphan packet receivedExplanation: X25IPI received a packet for which itcould find no associated connection.System Action:virtual circuit.User or Operator Response:X25IPI343IAn X.25 clear request is sent on theNone.MCH lu clear request sentExplanation: X25IPI sent a clear request on theindicated MCH, to recover from an error situation.System Action:Execution continues.User or Operator Response:X25IPI345ENone.MCH lu no free path available forincoming call 345I MCH lu checknumber of logical channels on LinkrecordExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Increase the virtualcircuit count on the Link record to match the numberof virtual circuits defined in the NPSI configuration.X25IPI347WMCH lu orphan packet discardedExplanation: X25IPI received a packet that it could notassociate with any connection.System Action:The packet is dump and discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the type ofX.25 packet from the dump. A clear confirmation (X'17')can be discarded harmlessly.X25IPI349EMCH lu unrecognized packet receivedExplanation: X25IPI did not recognize the type codein a packet received from NPSI.System Action:and discarded.User or Operator Response:The unrecognized packet is dumpedTell the systemprogrammer about the problem.System Programmer Response: Determine the packettype from the dump; notify the IBM Support Center.X25IPI350IMCH lu terminatingExplanation: 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.User or Operator Response:X25IPI355IMCH lu closedNone.Explanation: X25IPI received a CLSDST completionindication for this MCH, indicating that this MCH hasclosed.System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for manual restart.User or Operator Response:X25IPI365ENone.MCH lu session loss code codeExplanation: X25IPI received the indicated MCHstatus change code while the MCH was notoperational. See message X25IPI391E for the loss codes.System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for manual restart.User or Operator Response:X25IPI367INone.VC vc packet discarded on failedsessionExplanation: X25IPI discarded a packet received aftera session was closed.System Action:User or Operator Response:X25IPI371EThe packet is dumped and discarded.None.MCH lu unexpected request completionExplanation: X25IPI received a VTAM requestcompletion notification for this MCH. This indicates aprogram error, because MCH sends are donesynchronously.System Action:The notification is ignored.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Notify the IBM400 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI381IMCH lu DATE error reportcommand=command error=errorExplanation: 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:error.User or Operator Response:X25IPI389EX25IPI attempts to recover from theNone.MCH lu DATE error reportcommand=command error=errorExplanation: X25IPI encountered a DATE errorbecause of an incorrect logical channel number. SeeNPSI Host Programming for the error codes.System Action:User or Operator Response:X25IPI discards the error indication.None.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.X25IPI411IVC ID incoming call from address userdata valueExplanation: X25IPI has received an incoming call onthis virtual circuit from the indicated address, with theindicated user data (protocol ID).System Action:User or Operator Response:The call is accepted or refused.None.System Programmer Response: Use the address todetermine the source of the connection.X25IPI391EMCH lu session loss code codeExplanation: X25IPI received a session statusnotification, with the indicated session loss code, forthis MCH.CodeLess than 50DescriptionVTAM LOSTERM exit codes50 VTAM SCIP exit UNBIND64000 VTAM NS exit CLEANUP64001 VTAM NS exit session initiationfailure64002 VTAM NS exit session initiationnegative response.System Action: The MCH LU is enabled for automaticrecovery by LOGAPPL, or for manual restart.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.X25IPI460IVC vc call to address refused, cause=causediagnostic=diagnosticExplanation: 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.X25IPI414IVC vc call collisionExplanation: X25IPI detected a call collision on thisvirtual circuit.System Action:initiated.User or Operator Response:X25IPI415WThe X.25 call collision procedure isNone.VC vc incoming call cleared: caller notknownExplanation: X25IPI received a call on this virtualcircuit from an address not present in the Dest entriesfor the associated MCH.System Action:The incoming call is cleared.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI416WVC vc incoming call cleared: drainingExplanation: 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.Chapter 25. X.25 Messages 401

X.25 MessagesX25IPI417EVC vc incoming call cleared: reasonExplanation: 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 theassociated LinkSystem Action:The incoming call is cleared.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI431IVC vc outgoing call to addressExplanation: 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.User or Operator Response:None.System Programmer Response: Use the address todetermine the destination of the connection.X25IPI445WVC vc call timer expiredExplanation: 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.X25IPI451IVC vc call accepted by address user datavalueExplanation: An outgoing call on this virtual circuitwas accepted by the remote system at the indicatedaddress with the indicated user data (protocolspecifier).System Action:User or Operator Response:Queued datagrams are sent.None.System Programmer Response: Use the address todetermine the destination of the connection.X25IPI455IVC vc retrying call with packet size sizeExplanation: 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.X25IPI456EVC vc outgoing call cleared: reasonExplanation: 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 acceptableSystem Action:The outgoing call is cleared.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI471IVC vc NPSI logon LU luExplanation: NPSI generated a VTAM session logonfrom the indicated LU for the virtual circuit.System Action:User or Operator Response:System Programmer Response:NPSI problem determination.X25IPI472EThe NPSI LU logon is accepted.None.VC vc session loss code codeUse the LU name forExplanation: 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.System Action:None.User or Operator Response:None.402 z/VM: TCP/IP Messages and Codes

X.25 MessagesX25IPI482EVC vc OPNDST did not completeExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the state ofthe NPSI VC LU using the VTAM DISPLAY command.X25IPI483IVC vc LU lu readyExplanation: The virtual circuit LU session is readyfor data transfer.System Action:Execution continues.User or Operator Response:X25IPI511INone.VC vc facilities: facilitiesExplanation: A list of facilities for this virtual circuitfollows. Facilities codes that can be noted are:CodespriorityrevchgpktwdwstandardprecedenceSystem Action:connection.DescriptionUser or Operator Response:Priority handling and charging isappliedReverse charging is appliedThe noted packet size is usedThe noted window size is usedDDN standard service is usedThe noted DDN precedence is appliedThe noted facilities are applied to theNone.System Programmer Response: Use the informationto determine the X.25 network facilities being used onthe connection.X25IPI515EVC vc facilities field unacceptable atoffset offsetExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Correct the remotesystem that is generating the invalid facilities. The X.25address of the remote system was noted in thepreceding X25IPI411I or 431I message for the VC ID.X25IPI521IVC vc call completeExplanation: The virtual circuit connection is ready fordata transfer.System Action:Data transfer begins.User or Operator Response:X25IPI548ENone.VC vc oversize data packet received,length=lengthExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI549EVC vc unrecognized packet receivedExplanation: X25IPI did not recognize the type codein a packet received from NPSI GATE.System Action:and discarded.The unrecognized packet is dumpedUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the packettype from the dump; notify the IBM Support Center.X25IPI551IVC vc call reset, cause=causediagnostic=diagnosticExplanation: 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.User or Operator Response:None.Chapter 25. X.25 Messages 403

X.25 MessagesX25IPI552IExplanation:circuit.System Action:circuit.VC vc reset collisionUser or Operator Response:X25IPI553IA reset collision occurred on this virtualData transfer resumes on the virtualNone.VC vc reset confirmedExplanation: A reset on this virtual circuit wasconfirmed by the remote system.System Action:circuit.User or Operator Response:X25IPI554WData transfer resumes on the virtualNone.VC vc qualified data packet discardedExplanation: A qualified data packet was received onan IP connection. Qualified data packets are notspecified for use on IP connections.System Action:and discarded.The qualified data packet is dumpedUser or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI555WVC vc interrupt indication receivedExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI556EVC vc interrupt confirmedExplanation: 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.User or Operator Response:Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI561ENotify the IBMVC vc DATE error reportcommand=command error=errorExplanation: 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.System Action:error.User or Operator Response:X25IPI566EX25IPI attempts to recover from theNone.VC vc GATE error reportcommand=command error=errorExplanation: 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.System Action:error.User or Operator Response:X25IPI571IX25IPI attempts to recover from theNone.VC vc call cleared, cause=causediagnostic=diagnosticExplanation: 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.User or Operator Response:None.System Programmer Response: Use the cause anddiagnostic codes to determine the reason the call wascleared.X25IPI581EVC vc session loss code value on LU luExplanation: A session loss status notification wasreceived for this virtual circuit, with the indicated losscode.CodeLess than 50DescriptionVTAM LOSTERM exit codes50 VTAM SCIP exit UNBIND64000 VTAM NS exit CLEANUP64001 VTAM NS exit session initiationfailure404 z/VM: TCP/IP Messages and Codes

X.25 Messages64002 VTAM NS exit session initiationnegative responseSystem Action:closed.User or Operator Response:The virtual circuit connection isNone.System Programmer Response: Use the VTAM errorcode to determine the reason for the session failure.X25IPI591IVC vc inactivity timer expiredExplanation: The inactivity time for this virtual circuitpassed with no data transferred.System Action:closed.User or Operator Response:X25IPI610IThe virtual circuit connection isNone.VC vc connection terminated for address:sent count received count dropped countExplanation: 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:User or Operator Response:X25IPI611IThe VC LU session is closed.VC vc closedNone.Explanation: The call on the virtual circuit wascompletely terminated.System Action:calls.User or Operator Response:X25IPI615IExplanation:completed.System Action:events to occur.The virtual circuit is reused for newNone.VC vc close pendingUser or Operator Response:X25IPI616WA close of this virtual circuit is partiallyX25IPI waits for the remaining closeNone.VC vc unable to clear GATE call in stateP2Explanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe call request.X25IPI618EVC vc clearing limit exceededExplanation: No clear response was received from theremote system after four clear requests.System Action:cleared.The virtual circuit is marked asUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe clear request.X25IPI621ISeverity:VC vc clear confirmedInformational.Explanation: The remote system responded to a clearrequest on this virtual circuit.System Action: Virtual circuit termination continues;message X25IPI611I should follow.User or Operator Response:X25IPI631INone.VC vc discarded packet packet in statestateExplanation: The indicated packet was discarded onthis virtual circuit to accomplish error recovery. Seemessage X25IPI011R VC for the call state codes.System Action:completed.User or Operator Response:X25IPI632EVirtual circuit error recovery isNone.VC vc received packet packet invalid instate stateExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the reasonthe X.25 network or remote system sent the invalidpacket.X25IPI641WVC vc clearing timer expiredExplanation: The remote system did not respond to aclear request within 180 seconds.System Action:User or Operator Response:The clear request is retried four times.Tell the systemChapter 25. X.25 Messages 405

X.25 Messagesprogrammer about the problem.System Programmer Response: Determine the reasonthe remote system did not respond to the clear request.X25IPI648EVC vc clearing limit exceededExplanation: No clear response was received from theremote system after four clear requests.System Action:cleared.The virtual circuit is marked asUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: Determine the reasonthe X.25 network or remote system did not respond tothe clear request.X25IPI651IVC vc clear confirmation sentExplanation: A clear request from the remote systemwas confirmed on this virtual circuit.System Action: Virtual circuit termination continues;message X25IPI611I should follow.User or Operator Response:X25IPI652IExplanation:circuit.VC vc clear sentNone.A clear request was sent on this virtualSystem Action: Virtual circuit termination continues;message X25IPI611I should follow.User or Operator Response:X25IPI680INone.VC vc reuse delay endedExplanation: The timer expired for NPSI cleanup forthis virtual circuit. A new call can now be made on thisvirtual circuit.System Action:call.User or Operator Response:X25IPI681IThe virtual circuit is used for a newNone.VC vc retry busy callExplanation: X25IPI retries a call that previouslyreceived a busy indication from NPSI.System Action:User or Operator Response:the system programmer.An outgoing call request is repeated.If the error recurs, notifySystem 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.X25IPI682EVC vc inactive: VTAM requestcompletion REQ=requestExplanation: A VTAM request has completed for thisvirtual circuit after the connection has been terminated.System Action:Execution continues.User or Operator Response:X25IPI683ENone.VC vc inactive: session loss code codeExplanation: 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:User or Operator Response:Source File:X25IPI684IThe notification is ignored.xnx25ipi assembleNone.VC vc inactive: session cleanupExplanation: Session cleanup is in progress for thisinactive virtual circuit.System Action:User or Operator Response:X25IPI685EThe VC LU session is closed.None.VC vc inactive: VTAM logon refusedExplanation: A late logon from a NPSI VC LU wasrefused after a call was cleared.System Action:The logon is rejected.User or Operator Response:X25IPI686INone.VC vc packet discarded on deadconnectionExplanation: A packet was received on this virtualcircuit after the connection was terminated.System Action:User or Operator Response:X25IPI700IThe packet is discarded.None.IP VM path accepted for userid UserIDExplanation: An IUCV connection from the TCPIPvirtual machine was accepted.System Action:User or Operator Response:X25IPI701EIP datagrams are transferred.None.Unexpected IUCV interrupt type=typeExplanation: An unexpected type code was found onan IUCV interrupt before the connection to the TCPIPvirtual machine was established.System Action:The interrupt is ignored.406 z/VM: TCP/IP Messages and Codes

X.25 MessagesUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI702INotify the IBMIP VM UserID path refused for useridUserID, drainingExplanation: 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.X25IPI711EUnexpected IUCV interrupt type=typeExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI712ENotify the IBMDestination address address notconfiguredExplanation: 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.User or Operator Response: Tell the systemprogrammer about the problem.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.X25IPI713EIP VM userid rejected message:parameter list data 713E IP VM useridrejected message: two-wayExplanation: An IUCV message was received from theTCPIP virtual machine with unexpected messageoption flags.System Action:The message is rejected.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Notify the IBMX25IPI714EIP VM UserID rejected message: toolong714E IP VM UserID rejected message:too shortExplanation: An IUCV message was received from theTCPIP virtual machine that was too long or too short.System Action:The message is rejected.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI715ENotify the IBMIP VM UserID rejected message:blocking errorExplanation: An IUCV message was received from theTCPIP virtual machine that contained inconsistentlength fields.System Action:The message is rejected.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI716WNotify the IBMIP VM UserID discarded empty messageExplanation: An empty IUCV message was receivedfrom the TCPIP virtual machine.System Action:The message is discarded.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI749TNotify the IBMIP VM UserID programming error onIPVMSNDTExplanation: An IUCV send completion interrupt wasreceived, but the IUCV send queue is empty.System Action:X'749' message.The program abends with an ABENDUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.X25IPI750INotify the IBMIP VM UserID disconnected: sent countreceived count dropped countExplanation: The number of datagrams sent, received,and dropped on the IUCV connection to the TCPIPvirtual machine are shown when the connection isterminated.Chapter 25. X.25 Messages 407

X.25 MessagesSystem Action: The IUCV connection is severed andX25IPI terminates.User or Operator Response: None.X25IPI760EIP VM UserID inactive: IUCV functioncompletionExplanation: An IUCV completion interrupt wasreceived after the path has been severed.System Action:The interrupt is ignored.User or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response:Support Center.Notify the IBMX25IPI780EIUCVCOM function failed R15=valueExplanation: 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:for the IUCV error.Determine the reasonX25IPI781E IUCVCOM function failed: reasonExplanation: The indicated IUCV function failed forthe indicated reason.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.X25IPI782EIUCV function failed, audit flags=flagsExplanation: 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.User or Operator Response: Restart the TCPIPX25NPSI device to reestablish the IUCV path.System Programmer Response:for the IUCV error.Determine the reason408 z/VM: TCP/IP Messages and Codes

Chapter 26. Miscellaneous MessagesCommon MessagesThis chapter contains miscellaneous DTC messages that are common to all TCP/IPclients and servers.This section contains messages that are common to TCP/IP.0001 TCP/IP installation error: DTCUMETEXT not foundSeverity:Error.Explanation: The TCP/IP message repository isrequired, but was not found.System Action:Server initialization stops.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 orCEESTARTSeverity: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:DTCINISCEERUN 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:DTCINI0004 Abend detected by DTCINISeverity: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:DTCINI0003 One or more required libraries notfoundSeverity:Explanation:Error.The C or Pascal runtime library,COMMTXT MessagesError 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: CMSCommand 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:Procedure Name:CMEMULP PASCALInitEmulation© Copyright IBM Corp. 1987, 2002 409

COMMTXT Messagesemulator 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:Procedure Name:CMEMULP PASCALInitEmulationFile not found, or file cannot be readSeverity: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:Procedure Name:CMPRCOMSayCalReHad a rejected message completion, msg lostSeverity: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:User or Operator Response:programmer.TCPIP continues execution.See the systemSystem 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 indicatethat all IUCV read buffers are full.Source File:Procedure Name:CMIUCSOC Cin nextbuf with type typeSeverity:Explanation:Error.System Action:descarray_save_iucvbufAn internal program error has occurred.Execution continues.User or Operator Response:programmer.Contact systemSystem 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.Source File:Procedure Name:CMIUCSOC Cdescarray_nextbufInvalid keyword in file file: tokenSeverity:Error.Explanation: The indicated TCPIP DATA file containsan invalid keyword. See the TCP/IP Planning andCustomization for more information about this file.System Action:continues.The keyword is ignored and executionUser or Operator Response: See the TCP/IP Planningand Customization, if necessary. Correct any misspelledor invalid keywords and reinitialize TCPIP.Source File:Procedure Name:CMHOSTN PASCALReadTCPIPdataFILEInvalid or missing parameter for statement orprevious statementSeverity: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 of410 z/VM: TCP/IP Messages and Codes

COMMTXT Messagesthe 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:problem resolution, as required.Source File:Procedure Name:CMHOSTN PASCALReadTCPIPdataFILEAssist the user withMessage Complete audit field: value value valueSeverity: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:message is lost.TCPIP continues execution; theUser or Operator Response: Tell the systemprogrammer about the problem.System Programmer Response: See the z/VM: CPProgramming Services book for information about IUCVerrors and audit field values. Troubleshoot the IUCVerror.Source File:Procedure Name:CMIUCSOC Ccheck_auditprogram: illegal option -- optionSeverity:Explanation:illegal.Error.System Action:The indicated command line option isExecution continues.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 cProcedure Name:getoptprogram: option requires and argument -- optionSeverity:Error.Explanation: This option requires an argument, butnone was found on the command line.System Action:Execution continues.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:Procedure Name:getopt cgetoptRc=code on IUCV_function to user, fd=fd, path=path,iprcode=code, iucvname=nameSeverity: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.Source File:Procedure Name:CMIUCSOC CdoiucvReadKanjiTable : Invalid char was read.: index, indexReadKanjiTable : c1, c2 : c1, c2Severity: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:Procedure Name:kjxlate pascalReadKanjiTableChapter 26. Miscellaneous Messages 411

COMMTXT MessagesReadKanjiTable: 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:Procedure Name:kjxlate pascalReadKanjiTableSever Pending Connection from user, forreasonSeverity: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:problem.Source File:Procedure Name:CMIUCSOC CTroubleshoot thedescarray_save_iucvbufShould not be in sock_request_iucv for functionSeverity: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:Center.Source File:Procedure Name:cmiucsoc csock_request_iucvContact the IBM SupportSyntax errors found in file file, continuing.Severity:Explanation:file.Error.Syntax errors were found in the listedSystem Action: The parser State is set to IgnoreState,and program operation continues.User or Operator Response:This message is issuedwhen the parser did not find one of the followingexpected strings:HOSTNAMEDOMAINORIGINTCPIPUSERIDNSINTERADDRNSPORTADDRRESOLVEVIACOMMUNICATEVIARESOLVERTIMEOUTOPENTIMEOUTRESOLVERUDPRETRIESMAXUDPRETRYSNSUSERIDTRACEThe operator should ensure that the configuration filecontains the correct syntax and valid information.Correct the input file to ensure correct programoperation.System Programmer Response:problem resolution, as required.Source File:Procedure Name:CMHOSTN PASCALReadTCPIPdataFILETCPHOS012E No Valid Dbcs Option forLOADDBCSTABLES in fileSeverity:Error.Assist the user withExplanation: 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.Source File:Procedure Name:CMHOSTN PASCALReadTCPIPdataFILETCPDBC000I DbcsEtoA : First Double ByteCharacter Invalid ord(firstchar)Severity:Informational.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 PASCAL412 z/VM: TCP/IP Messages and Codes

COMMTXT MessagesProcedure Name:DbcsEtoATCPDBC001I DbcsEtoA : Second Double ByteCharacter Invalid ord(firstchar)ord(secondchar)Severity:Informational.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.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:Procedure Name:CMDBCSCV PASCALDbcsEtoATCPDBC002I DbcsAtoE : Character after ESCAPEInvalid ord(AsciiEscape) ord(nextchar)Severity:Informational.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(Bor 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.Source File:Procedure Name:CMDBCSCV PASCALDbcsAtoETCPDBC003I DbcsAtoE : Character after $ Invalidord(AsciiEscape) ord(AsciiDollar)ord(nextchar)Severity:Informational.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(Bor ESC(J. The character afterthe $, with the specified ordinal value, is not valid for aJIS Kanji shift-out 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.Source File:Procedure Name:CMDBCSCV PASCALDbcsAtoETCPDBC004I DbcsAtoE : Character after ( Invalidord(AsciiEscape) ord(AsciiBraceL)ord(nextchar)Severity:Informational.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(Bor ESC(J. The character afterthe (, with the specified ordinal value, is not valid for aJIS Kanji 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.Source File:Procedure Name:CMDBCSCV PASCALDbcsAtoETCPDBC005I DbcsAtoE : Second Double ByteCharacter Invalid ord(firstchar)ord(secondchar)Severity:Informational.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.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 valid ASCIIdouble-byte characters for the selected conversion type.Source File:Procedure Name:CMDBCSCV PASCALDbcsAtoEChapter 26. Miscellaneous Messages 413

COMMTXT MessagesTCPDBC006I DbcsAtoE : First Double ByteCharacter Invalid ord(firstchar)Severity:Informational.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(Bor ESC(J. The first characterof a double-byte character, with the specified ordinalvalue, is not in the valid range for JIS Kanjidouble-byte characters.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.Source File:Procedure Name:TCPDBC010ESeverity:Error.CMDBCSCV PASCALDbcsAtoEInvalid Data in file : Loading Stopped.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.Source File:Procedure Name:CMDBCSCV PASCALExitErrorwith problem resolution, as required.Source File:Procedure Name:CMHOSTN PASCALuser severed IUCV path.Severity:Explanation:Warning.ReadTCPIPdataFILEYou 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.Source File:Procedure Name:CMIUCSOC Cdescarray_save_iucvbufuser severed IUCV path. Reason reasonSeverity: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.Source File:Procedure Name:CMIUCSOC Cdescarray_save_iucvbufUnable 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 operator414 z/VM: TCP/IP Messages and Codes

NoticesIBM 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, JapanThe 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.© Copyright IBM Corp. 1987, 2002 415

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 RequestSuch 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.416 z/VM: TCP/IP Messages and Codes

TrademarksThe following terms are trademarks of International Business MachinesCorporation in the United States, or other countries, or both:BookManager DATABASE 2DB2DFSMS/VMDirMaintIBMIBMLinkLanguage EnvironmentMVSNetViewOpenEdition/VMOS/390OpenExtensionsSP S/370S/390 System/370System/390TivoliVTAMVM/ESAz/VMzSeriesOther company, product, and service names may be trademarks or service marksof others.Notices 417

418 z/VM: TCP/IP Messages and Codes

BibliographyThis 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 recordsVM 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 PublicationsEvaluationz/VM: General Information, GC24-5991z/VM License Information, GC24-6033z/VM: Migration Guide, GC24-5996Installation and Servicez/VM: Installation Guide, GC24-5992z/VM: Service Guide, GC24-5993z/VM: VMSES/E Introduction and Reference,GC24-5994Planning 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-6034Customizationz/VM: CP Exit Customization, SC24-5953Operationz/VM: System Operation, SC24-6000z/VM: Virtual Machine Operation, SC24-6036Application 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© Copyright IBM Corp. 1987, 2002 419

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-0806End 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-0018Diagnosisz/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-6030z/VM: System Messages and Codes - OtherComponents, GC24-6032z/VM: VM Dump Tool, GC24-6037Publications for z/VM AdditionalFacilitiesDFSMS/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-6051Language 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-1943OSA/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-7476420 z/VM: TCP/IP Messages and Codes

zSeries 900: Planning for the Open SystemsAdapter-2 Feature, GA22-7477TCP/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-6020Publications for z/VM OptionalFeaturesDirMaint 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-6024PRFz/VM: Performance Reporting Facility FunctionLevel 410, SC24-6027RTMz/VM: RealTime Monitor Function Level 410,SC24-6028RACF ® 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-1343External Security Interface (RACROUTE) MacroReference for MVS and VM, GC28-1366Other 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-6146v 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

422 z/VM: TCP/IP Messages and Codes

IndexBBOOTPDmessages 1CCMSRESOLV messages 15Common Messages 409Commtxt messages 409CONVXLAT messages 359DDHCPDmessages 1Domain Name Server messages 15FFile Transfer Protocol (FTP) messages 33FTPPERM messages 361GGDDMXD/VMabend codes 83messages 83HHOMETEST messages 362IIFCONFIG messages 363Internet Message Access Protocol (IMAP)messages 85IPWIZARD messages 369LLPD messages 161LPQ messages 168LPR messages 170LPRM messages 178LPRSET messages 170MMiscellaneous messages 409MPROUTEmessages 99NNETSTATmessages 119Network File System (NFS)messages 125NFSPERM messages 361OOBEYFILE messages 371PPING messages 155PORTMAPmessages 159RRemote Printing messages 161LPD 161LPQ 168LPR 170LPRM 178LPSET 170Remote Procedure Call messagesRPCGEN messages 188RPCILIB messages 181RPCINFO messages 186REXEC messages 191REXECD messages 193ROUTEDmessages 199SSecure Socket Layer (SSL)messages 279SSL Return Codes 291SSL Server Reply Codes 291, 292, 293Simple Mail Transfer Protocol (SMTP)Reply Code messages 243Server messages 223SMTPRSCS messages 253Simple Network Management Protocol(SNMP)SNMPD messages 265SNMPLIB messages 269SQESERV messages 274SNALINKmessages 257TTCP/IPserver messages 295TCP/IP Utilities messagesCONVXLAT messages 359TCP/IP Utilities messages (continued)FTPPERM messages 361HOMETEST messages 362IFCONFIG messages 363IPWIZARD messages 369NFSPERMmessages 361OBEYFILE messages 371TCPRUN messages 371TCPRUN messages 371Trivial File Transfer Protocol (TFTP)messages 377Trivial File Transrer Program (TFTP)TFTPD messages 381UUniversal File Transfer (UFT)UFTD messages 383XX.25messages 387© Copyright IBM Corp. 1987, 2002 423

424 z/VM: TCP/IP Messages and Codes

Readers’ Comments — We’d Like to Hear from Youz/VM TCP/IP Level 430Messages and CodesVersion 4 Release 3.0Publication No. GC24-6022-02Overall, how satisfied are you with the information in this book?Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfiedOverall satisfaction h h h h hHow satisfied are you that the information in this book is:Very Satisfied Satisfied Neutral Dissatisfied VeryDissatisfiedAccurate h h h h hComplete h h h h hEasy to find h h h h hEasy to understand h h h h hWell organized h h h h hApplicable to your tasks h h h h hPlease tell us how we can improve this book:Thank you for your responses. May we contact you? h Yes h NoWhen 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.NameAddressCompany or OrganizationPhone No.

Readers’ Comments — We’d Like to Hear from YouGC24-6022-02GC24-6022-02_________________________________________________________________________________________Fold and Tape Please do not staple Fold and TapeBUSINESS REPLY MAILFIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORKPOSTAGE WILL BE PAID BY ADDRESSEEIBM CorporationInformation DevelopmentDepartment G60G1701 North StreetEndicott, New York13760-5553NO POSTAGENECESSARYIF MAILED IN THEUNITED STATES_________________________________________________________________________________________Fold and Tape Please do not staple Fold and Tape___________________________________________________________________________________________________Cut or FoldAlong LineCut or FoldAlong Line

File Number: S370/4300/30XX-50Program Number: 5739-A03Printed in U.S.A.GC24-6022-02

Spine information: z/VM TCP/IP Messages and Codes Version 4 Release 3.0