APAR status
Closed as fixed if next.
Error description
When using SNMP to get the value for the MIB object ibmTcpipMvsPktTraceTable, errors such as "No such object" might be returned. If using NETVIEW to initiate a OSA and PKT trace, the following error is shown: ibmTcpipMvsPktTraceTable: Unknown Object Identifier (Sub-id id not found: (top) -> ibmTcpipMvsPktTraceTable)
Local fix
In the local copy of SEZAINST(MIBDESC), change the following entries from: ibmMvsPktTraceTable 1.3.6.1.4.1.2.6.19.2.2.3.4. table 0 ibmMvsPktTraceEntry 1.3.6.1.4.1.2.6.19.2.2.3.4.1. table 0 to: ibmTcpipMvsPktTraceTable 1.3.6.1.4.1.2.6.19.2.2.3.4. table 0 ibmTcpipMvsPktTraceEntry 1.3.6.1.4.1.2.6.19.2.2.3.4.1. table 0 KEYWORDS: SNMP MIB MIBDESC NETVIEW ibmMvsPktTraceTable ibmMvsPktTraceEntry ibmTcpipMvsPktTraceTable ibmTcpipMvsPktTraceEntry SEZAINST UNKNOWN OBJECT EZABZ003
Problem summary
**************************************************************** * USERS AFFECTED: All users of the IBM Communications Server * * for z/OS Version 1 Release(s) 11, 12, and * * 13 IP: SNMP * **************************************************************** * PROBLEM DESCRIPTION: NETVIEW initiated trace collection for * * OSA and PKT traces, but the following * * messages was received: * * * * ibmTcpipMvsPktTraceTable: Unknown * * Object Identifier (Sub-id not found: * * (top) ->ibmTcpipMvsPktTraceTable) * * * **************************************************************** * RECOMMENDATION: * **************************************************************** The MIB object ibmTcpipMvsPktTraceTable is supported by the z/OS CS IP SNMP agent and subagents. But it does not exist in the SEZAINST(MIBDESC) library. +-------------------------------------------------------------+ + 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
This APAR is being closed FIN (Fixed If Next) with concurrence from the submitting customer. This means that a fix to this APAR is expected to be delivered from IBM in a release (if any) to be available within the next 24 months. This problem will be tracked as Story 8234 in RTC by Communications Server for z/OS Development. The solution for this APAR is included in CS for zOS Version 2 Release 1.
APAR Information
APAR number
PM71103
Reported component name
TCP/IP V3 MVS
Reported component ID
5655HAL00
Reported release
1C0
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-17
Closed date
2012-08-27
Last modified date
2013-09-16
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
R1C0 PSN
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1C0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
16 September 2013