Resolver reason codes

This section describes the resolver reason codes, listing them by decimal and hexadecimal value.

The hexadecimal reason code is made up of 4 bytes in the following format: 
cccc rrrr
Reason code qualifier Reason code value
cccc rrrr
  • cccc is the reason code qualifier. If cccc is in the range of X'7800' through X'78FF', the reason code is defined by the Resolver.
  • rrrr is the reason code value. If cccc is in the range of X'7800' through X'78FF', the value is described in the following table. If cccc is outside of that range, it is not a Resolver reason code. Those reason codes are described in the z/OS UNIX System Services Messages and Codes.
Table 1. Resolver reason codes
Decimal value Hexadecimal value Reason code Description
0—4095 0000—0FFF defined by UNIX System Services See the z/OS UNIX System Services Messages and Codes.
4096 1000 RSN_NotUp Resolver service is not available.
4097 1001 RSN_BadEnv Resolver service does not support SRB mode.
4098 1002 RSN_NoSpace Resolver service output buffer is too small.
4099 1003 RSN_BadValue Resolver service input parameter value is not valid.
4100 1004 RSN_NotFound Resolver service did not find the specified host name.
4101 1005 RSN_BadAnswer Resolver service received a bad answer from the nameserver, or did not receive an answer from the nameserver.
4102 1006 RSN_BadParm Resolver service was unable to access an input or output parameter.
4103 1007 RSN_BadSrv Resolver service requested is not supported.
4104 1008 RSN_NoStorage Resolver service received a negative answer from the nameserver, or did not receive an answer from the nameserver.
4105 1009 RSN_EintrRcv Resolver service was interrupted by a signal.
4106 100A EZB_RSN_NameIsAddr An IP address was passed a name that was expected.
4107 100B EZB_RSN_NoOmvsAuth Service invoker not authorized to use USS.
4108 100C EZB_RSN_NoLatches Unable to obtain GRS latch set.
4109 100D EZB_RSN_NameLenErr Incorrect name length passed.
4110 100E EZB_RSN_NestedAPI Resolver service detected that there is still an outstanding resolver API request in the same task.
4111 100F EZB_RSN_ServLenErr Resolver service detected incorrect service name length.
4112 1010 EZB_RSN_SocketLenErr Resolver service detected incorrect socket length.
4113 1011 EZB_RSN_NoData No data was passed to Resolver service.
4114 1012 EZB_RSN_ServiceNotFound Resolver service detected service name is not found.
4115 1013 EZB_RSN_PortNotFound Resolver service detected port number is not found.
4116 1014 EZB_RSN_NoSocket Resolver service detected there is no socket.
4117 1015 EZB_RSN_BadAddrinfo Resolver service detected there is a bad input addrinfo.
4118 1016 EZB_RSN_InvalidSeq Resolver service detected that freeaddrinfo was invoked without any addrinfos having been created.
4119 1017 EZB_RSN_BadProtocol Resolver service detected invalid protocol.
4120 1018 EZB_RSN_SockLookup Resolver service detected invalid socktype.
4121 1019 EZB_RSN_InvalidHostname The host name input on a Getaddrinfo call contained only scope information.
4122 101A EZB_RSN_ScopeNotPermitted Scope information was specified on a Getaddrinfo call that has incompatible search options.
4123 101B EZB_RSN_UnresolvedScope The scope information specified on a Getaddrinfo or Getnameinfo call did not resolve to valid interface information on this system.
4124 101C EZB_RSN_HostnameBuffer The buffer passed on the Getnameinfo call was too small for the resolved host name information; the application does not support receiving truncated information as a response.
4125 101D EZB_RSN_ServicenameBuffer The buffer passed on the Getnameinfo call was too small for the resolved service name information; the application does not support receiving truncated information as a response.
4216 101E EZB_RSN_InvalidScopeValue Scope information was specified on a Getaddrinfo call but was not in the correct format.