Analysis

Use the following checklist to check incorrect variable format:
  1. Is the variable contained in the hlq.MIBDESC.DATA data set or MIBS.DATA file?
    1. The SNMP query stack uses the hlq.MIBDESC.DATA data set to determine the display syntax of the variable value. NetView® SNMP requires that all MIB object names be included in the hlq.MIBDESC.DATA data set.
    2. snmp searches the MIBS.DATA file for a MIB name definition. If it is not found, the value in the compiled MIB is used.
  2. Is the value listed in the syntax position of the hlq.MIBDESC.DATA data set or MIBS.DATA file record for this variable the correct syntax?

    The value specified for syntax (for NetView) is case-sensitive and must be specified in lowercase.

  3. For NetView SNMP, is the variable value type specified in message SNM043I Variable value type: correct?

    See the z/OS Communications Server: IP System Administrator's Commands section about "Managing TCP/IP Network Resources Using SNMP" for the meanings of the variable value types.

If the problem still occurs after checking the preceding and making any needed changes, obtain the following documentation:
  • For the TCP/IP subagent, subagent ITRACE level four output to show that the subagent returned to the SNMP agent.
  • For the OMPROUTE subagent, syslogd output obtained by starting OMPROUTE with the -s1 option or by issuing the MODIFY SADEBUG command to start OMPROUTE subagent tracing.
  • For the Network SLAPM2 subagent, syslogd output obtained by the Network SLAPM2 subagent with the -d 131 option or the MODIFY DEBUG,LEVEL command to start Network SLAPM2 subagent tracing. .
  • For user-written subagents, DPIdebug(2) output, which is sent to the syslogd. For more information about reading the syslogd traces, see the z/OS Communications Server: IP Configuration Guide.
  • SNMP query stack level 4 trace output or z/OS® UNIX snmp command trace level -d 4.
  • SNMP manager command output showing the incorrectly formatted variable.
  • SNMP agent level 31 trace output shows the DPI packet exchanges between the agent and subagent, as well as the value returned to the manager.
  • For the TN3270E Telnet subagent, syslogd output from TNSATRACE keyword on TNSACONFIG profile statement to show what the subagent returned to the SNMP agent.
In the traces, verify that the variable value and syntax are passed correctly in the SNMP GetResponse-PDU from the agent to the SNMP manager.
The following documentation might also be needed in some cases, but it is suggested that the IBM® Software Support Center be contacted before this documentation is obtained:
  • Dump of the TCP/IP address space (for TCP/IP and TN3270E Telnet subagent problems)
  • Dump of SNMP agent address space
  • Dump of SNMP query stack address space
  • Dump of OMPROUTE address space (for OMPROUTE subagent problems)
  • Dump of Network SLAPM2 subagent address space (for Network SLAPM2 subagent problems)

Information about obtaining a dump can be found in z/OS MVS Diagnosis: Tools and Service Aids. Obtaining SNMP traces is discussed in SNMP traces.

Parent topic: Variable format incorrect