IBM Support

PI13102: FPEV1340W TCP/IP PROTOCOL VIOLATION DETECTED ISSUED WHEN RUNNING PE CLIENT

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer gets "FPEV1340W TCP/IP PROTOCOL VIOLATION DETECTED"
    error message seen in the OMPE Server STC joblog even though
    each port is assigned a unique value in each RKD2PAR(OMPEssid)
    member.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
    *                 users of component                           *
    *                 - PE Server subtask                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: When the PE Client user interface is    *
    *                      used to monitor a DB2 subsystem, the    *
    *                      monitoring PE Server subtask            *
    *                      sporadically issues message FPEV1340W.  *
    *                      The same problem can show up when DB2   *
    *                      Performance Expert Extended Insight     *
    *                      Feature or SQL Statements Dashboard is  *
    *                      in use.                                 *
    ****************************************************************
    * RECOMMENDATION: Apply this PTF                               *
    ****************************************************************
    PROBLEM SUMMARY:
    When a user performs a logon from the PE Client user interface
    and the PE Server subtask does not get enough CPU cycles to
    process the logon request in time, the PE Client gets an
    internal timeout. The PE Client continues processing with
    default settings and sends a consecutive request to the PE
    Server subtask while the previous request is still beeing
    processed on PE Server side. The PE Server subtask detects the
    collision of both requests as protocol violation and issues
    message FPEV1340W.
    The DB2 Performance Expert Extended Insight Feature and
    SQL Statements Dashboard perform the same logon sequence as
    the PE Client and can experience the same problem.
    
    PROBLEM CONCLUSION:
    The code has been corrected. The PE Server subtask will no
    longer issue message FPEV1340W. Instead the PE Client will
    display a timeout message and discontinue the logon processing.
    The logon can be retried and if the timeout condition persists,
    the timeout value in the properties file db2pm.prop for the PE
    Client must be increased.
    The timeout settings for DB2 Performance Expert Extended
    Insight Feature and SQL Statements Dashboard must be increased
    accordingly.
    
    KEYWORDS:
    FPEV1340W PE CLIENT LOGON TIMEOUT EXTENDED INSIGHT
    SQL STATEMENT DASHBOARD
    
    CIRCUMVENTION:
    If the user logon from the PE Client fails with the pop up of
    a message window displaying a timeout message, retry the logon
    from the PE Client user interface. Increase the timeout value
    in the properties file db2pm.prop for the PE Client.
    

Problem conclusion

  • The code has been corrected. The PE Server subtask will no
    longer issue message FPEV1340W. Instead the PE Client will
    display a timeout message and discontinue the logon processing.
    The logon can be retried and if the timeout condition persists,
    the timeout value in the properties file db2pm.prop for the PE
    Client must be increased.
    The timeout settings for DB2 Performance Expert Extended
    Insight Feature and SQL Statements Dashboard must be increased
    accordingly.
    
    KEYWORDS:
    FPEV1340W PE CLIENT LOGON TIMEOUT EXTENDED INSIGHT
    SQL STATEMENT DASHBOARD
    
    CIRCUMVENTION:
    If the user logon from the PE Client fails with the pop up of
    a message window displaying a timeout message, retry the logon
    from the PE Client user interface. Increase the timeout value
    in the properties file db2pm.prop for the PE Client.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI13102

  • Reported component name

    OM XE DB2PE/PM

  • Reported component ID

    5655OPE00

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-03-05

  • Closed date

    2014-03-18

  • Last modified date

    2014-04-02

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

    PI06314

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

    UI16140

Modules/Macros

  • DGOVMSTR DGOVTCPD DGOVTCPL
    

Fix information

  • Fixed component name

    OM XE DB2PE/PM

  • Fixed component ID

    5655OPE00

Applicable component levels

  • R510 PSY UI16140

       UP14/03/20 P F403

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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
02 April 2014