IBM Support

IV19089: "CONFIGURE EVENT ADAPTER" TASK APPENDS THE LOGGING LEVEL TRACE VALUE TO THE EXISTING VALUE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Using the "Configure Event Adapter" task to change the "Trace"
    value for the "Logging Levels", the new trace value is appended
    to the existing trace value, instead of replacing the old value
    with the new value.  If this is repeated, the new values
    continue to be appended. For example:
    .
    If the existing trace level was VERBOSE, as seen in the
    TEC-<appserver triplet>-<SYSLOG|CCMS|IDOC>.conf file was:
    ABH_TracingLogLevel=VERBOSE
    .
    Changing the Logging Levels Trace to LOW, results in
    ABH_TracingLogLevel=VERBOSELOW
    .
    This does not generate any erros in the adapter logs.
    .
    RECREATE INSTRUCTIONS:
    .
    To set the event adapter trace level:
    - Run the "Configure Event Adapter" task.
    - For the "Logging Levels", set to NORMAL, VERBOSE, or LOW.
    - Select "Set and Execute".
    .
    The trace level value as seen in the TEC-<appserver
    triplet>-<SYSLOG|CCMS|IDOC>.conf file:
    ABH_TracingLogLevel=<oldValue><newValue>.
    .
    LOCAL FIX:
    On the endpoint, on UNIX in
    $LCF_BINDIR/../../generic_unix/TME/ABH/adapters or on Windows in
    %LCF_BINDIR%\..\..\bin\generic_unix\TME\ABH\adapters, edit the
    TEC-<appserver triplet>-<SYSLOG|CCMS|IDOC>.conf file:
    .
    Find the ABH_TracingLogLevel= line.
    Remove the excess trace value(s).
    Approver Initials:    LD
    

Local fix

Problem summary

  • Using the "Configure Event Adapter" task to change the "Trace"
    value for the "Logging Levels", the new trace value is appended
    to the existing trace value, instead of replacing the old value
    with the new value.  If this is repeated, the new values
    continue to be appended.
    
    This does not generate any errors in the adapter logs but the
    effective trace level is not changed.
    

Problem conclusion

  • The fix for this APAR will be included in the following
    maintenance vehicle:
    
       | interim fix | 5.1.0-TIV-ITM_SAP-IF0021
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV19089

  • Reported component name

    ITMF AP:MYSAP.C

  • Reported component ID

    5724B97SP

  • Reported release

    510

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-06

  • Closed date

    2013-06-30

  • Last modified date

    2013-06-30

  • 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

    ITMF AP:MYSAP.C

  • Fixed component ID

    5724B97SP

Applicable component levels

  • R510 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"510","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 July 2021