APAR status
Closed as fixed if next.
Error description
After a OMVS segment is defined and that the SNMPQE started task is permitted to BPX.SUPERUSER, the procedure for the SNMPQE started task failed with: EZA6289W Can't make raw ICMP socket - can't do PING. The failure occurred because the assigned UID for SNMPQE was was greater than 65535 which is considered to be incorrect. With the UID's halfword length being exceeded, the resulting value (that could be non-existent) mismatches the assigned UID for SNMPQE. To display the assigned SNMPQE's UID, issue the following USS shell command for the SNMPQE's user name: . id snmpqe_user . The output will show the UID value in decimal. After conversion to hexidecimal for the fullword display, the UID value exceeds x'FFFF' (65535).
Local fix
Re-assign the UID value for SNMPQE to be less than 65535. KEYWORDS: SNMPQE EZAAD0B2 SQESERV EZA6289W RAW SOCKET ICMP PING UID
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release 13 and Version 2 * * Release 1 IP: SNMP Query Engine (SNMPQE) * **************************************************************** * PROBLEM DESCRIPTION: The SNMP Query Engine (SNMQE) issued * * error message, EZA6289W, indicating * * that it was unable to open a RAW * * socket for its ping function. It * * was not defined with a UID of 0 * * (superuser) but its user ID was * * permitted to the * * BPX.SUPERUSER resource. * **************************************************************** * RECOMMENDATION: * **************************************************************** SNMPQE uses an unsigned short variable in which to save its UID value so it can only save a value <= 65535. The customer had defined a UID value larger than 65535 for SNMPQE. SNMPQE successfully obtained its original UID value and then successfully invoked seteuid() to switch to UID 0 so it could open a RAW socket. But when it invoked seteuid() again to return to its original UID value this function call failed because the saved original UID value only contained the last 2 bytes of the real value. +-------------------------------------------------------------+ + Please check our Communications Server for OS/390 homepages + + for common networking tips and fixes. The URL for these + + homepages can be found in Informational APAR II11334. + +-------------------------------------------------------------+
Problem conclusion
Temporary fix
Comments
The solution for this APAR is included in CS for zOS Version 2 Release 2.
APAR Information
APAR number
PI27344
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1D0
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-10-09
Closed date
2014-10-27
Last modified date
2015-09-25
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
30 April 2020