11.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DNS <strong>and</strong> Resolver <strong>Messages</strong>User 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, <strong>and</strong>may 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 <strong>TCP</strong>connection 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, <strong>and</strong>may 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 comm<strong>and</strong>, 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/<strong>VM</strong>: <strong>TCP</strong>/<strong>IP</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!