IBM Support

PK92412: ENHANCE SNMP MANAGER API TO SUPPORT SPECIFYING THE ENGINEID

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • SNMP Manager API does not create a known engineID.  When sending
    encrypted traps the receiver needs the userid and engineID to
    identify the private key for decryption.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Releases 9, 10, & 11 IP:  *
    *                 SNMP Manager API.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: The SNMP Manager API needs to provide   *
    *                      a way to specify an engine ID when      *
    *                      sending a trap to a remote recipient.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The z/OS Communications Server SNMP manager API does not provide
    a way to specify an engine ID when sending a trap to a remote
    recipient.  Because the same username could be defined on
    different hosts, a remote SNMP agent needs both the username
    and engine ID prior to looking up the user's security
    information.
    +-------------------------------------------------------------+
    + 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 problem has been rectified in the Version 1 Release 12 of
    the IBM Communications Server for z/OS.  Therefore, this APAR
    will close without a PTF, as agreed with the submittor.
    

APAR Information

  • APAR number

    PK92412

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    190

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-07-27

  • Closed date

    2010-01-05

  • Last modified date

    2010-01-08

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK52651 UK52652 UK52653 UK52654

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1A0 PSN

       UP

  • R1B0 PSN

       UP

  • R190 PSN

       UP

  • R199 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":"190","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":"190","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 January 2010