IBM Support

OA40243: SERVICEABILITY APAR FOR OMEGAMON XE FOR MAINFRAME NETWORKS V420

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Serviceability enhancements for OMEGAMON XE for Mainframe
    Networks V420
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All OMEGAMON XE for MAINFRAME NETWORKS       *
    *                 V420 users.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Serviceability enhancements for         *
    *                      OMEGAMON XE for Mainframe Networks      *
    *                      V420.                                   *
    ****************************************************************
    * RECOMMENDATION: Apply the PTF.                               *
    ****************************************************************
    OMEGAMON XE for Mainframe Networks V420 requires serviceability
    enhancements.
    

Problem conclusion

Temporary fix

Comments

  • The following serviceability enhancements for OMEGAMON XE
    for Mainframe Networks V420 are added by this APAR:
    1. Build date and time added to KN3ACTCS via message KN3CT051.
    2. Build date and time added to KONACTCS via message KONCT051.
    3. Build date and time added to KN3ANMON via message KN3N015I.
    4. Improved tracing in KN3ACTCG for channel data.
    5. Improved tracing in KN3ACTCH for LPAR information
    6. Corrected start time for TN3270 server connections when
    multiple TN3270 servers manage the same stack.
    7. Corrected start time for TN3270 server connections when the
    connection is started prior to Mainframe Networks startup.
    
    New or changed messages:
    
    KN3CT051 SNMP MANAGER INITIALIZED.
    RC=<return_code>, BUILD: KN3ACTCS
    <date> <time>
    Explanation:
    The SNMP manager was started with the
    return code specified by <return_code> using build
    KN3ACTCS at <date> and <time>, where date and time
    are in the following format: month day year hours
    minutes seconds, as in Sep 11 2012 14:29:12, where:
    <return_code>
    is the return code from the SNMP Manager
    task initialization request.
    <date>
    is the date that the C preprocessor compiled
    the SNMP Manager task source code,
    displayed in the format mmm dd yyyy.
    <time>
    is the time that the C preprocessor compiled
    the SNMP Manager task source code,
    displayed in the format hh:mm:ss.
    This message is written to the KN3ACTCS log.
    System action:
    The SNMP manager starts.
    Programmer response:
    This is an informational message.  If you received
    an RC=0 return code, no action is required. If you
    receive a different return code, try to determine
    the reason for the error. If you cannot, log the
    information for problem diagnosis and contact IBM
    Software Support.
    Message type:
    Information.
    
    KONCT051 SNMP MANAGER INITIALIZED.
    RC=<return_code>, BUILD: KONACTCS
    <date> <time>
    Explanation:
    The SNMP manager was started with the
    return code specified by <return_code> using build
    KONACTCS at <date> and <time>, where date and time
    are in the following format: month day year hours
    minutes seconds, as in Sep 11 2012 14:29:12, where:
    <return_code>
    is the return code from the SNMP Manager
    task initialization request.
    <date>
    is the date that the C preprocessor compiled
    the SNMP Manager task source code,
    displayed in the format mmm dd yyyy.
    <time>
    is the time that the C preprocessor compiled
    the SNMP Manager task source code,
    displayed in the format hh:mm:ss.
    This message is written to the KONACTCS log.
    System action:
    The SNMP manager starts.
    Programmer response:
    This is an informational message.  If you received
    an RC=0 return code, no action is required. If you
    receive a different return code, try to determine
    the reason for the error. If you cannot, log the
    information for problem diagnosis and contact IBM
    Software Support.
    Message type:
    Information.
    
    KN3N015I THE DATA COLLECTION SERVER IS
    INITIALIZED AND READY TO
    COLLECT DATA. BUILD: KN3ANMON
    <date><time>
    Explanation:
    The program that collects data from
    z/OS Communications Server network management
    interfaces has been initialized successfully
    using build: KN3ANMON at <date> and <time>
    (for example, BUILD: KN3ANMON Sep 11 2012 14:29:12),
    where:
    <date>
    is the date that the C preprocessor compiled
    the NMI task source code, displayed in the
    format mmm dd yyyy.
    <time>
    is the time that the C preprocessor compiled
    the NMI task source code, displayed in the
    format hh:mm:ss.
    The process is ready to collect z/OS Communications
    Server data. This message is written to the
    KN3ANMON log.
    System action:
    None.
    Programmer response:
    This is an informational message. No action is required.
    

APAR Information

  • APAR number

    OA40243

  • Reported component name

    OMEGAMON XE MF

  • Reported component ID

    5608A4000

  • Reported release

    420

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-08-29

  • Closed date

    2012-10-02

  • Last modified date

    2012-11-01

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

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

    UA66808

Modules/Macros

  • KN3ACTC4 KN3ANMON
    

Fix information

  • Fixed component name

    OMEGAMON XE MF

  • Fixed component ID

    5608A4000

Applicable component levels

  • R420 PSY UA66808

       UP12/10/31 P F210

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS2JL7","label":"Tivoli OMEGAMON XE for Mainframe Networks"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.2.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
01 November 2012