IBM Support

PM45834: Step with filter applied always passes upon a timeout, regardless of filter match status - regression

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a step used a filter set, but the filter set made no matches,
    AND the step timed out - the step would be marked
    as passing.
    Without using filters, the timeout would fail the step, and if
    there are no matches the step _should_ behave as if there were
    no filter sets used.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Symptom:
    A step with a filter applied and times out does not fail, it
    passes.
    
    Cause:
    The engine only looks for certain returns from the agent for
    application of a filter. The timeout event, or TMO, is not
    one of them. This timeout event has a special case applied
    where the filter code looks for TMO, only in the wrong
    place. The agent response looks like:
    320 EXEC ExecStart["/tmp","server.ibm.com"]
    300 HEARTBEAT 1
    320 TMO ExecTimeout[+10]
    251 RESULT 999
    260 EOR
    
    The TMO entry is the type, not the log line. The filter code
    was errantly looking for TMO in the line.
    

Problem conclusion

  • Fix:
    Adjust the filter code to look for TMO in the type of log
    line, not the log line itself. Also made it possible to
    filter on the TMO type...if one should want to.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM45834

  • Reported component name

    BUILD FORGE EE

  • Reported component ID

    5724S2701

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-16

  • Closed date

    2011-10-19

  • Last modified date

    2011-10-19

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

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

Fix information

  • Fixed component name

    BUILD FORGE EE

  • Fixed component ID

    5724S2701

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSB2MV","label":"Rational Build Forge"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
19 October 2011