IY34342: SPACES WITHIN TEMS EVENTS CAUSING PARSING FAILURE BECAUSE THE CLASS IS NOT DEFINED.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as Permanent restriction.

Error description

  • In the baroc file which is sent with the TEMS product, the
    classes which
    are generated have spaces within them.  In TEC a space is a
    delimeter
    and when an event is received by TEC, it fails because of a
    parsing
    error.
    .
    This is an example of the parsing error.
    .
    "PARSING_FAILED~'Line 1: Class Security undefined'
    .
    Example event:
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    ### EVENT ###
    Security;source="TEMS";sub_source="Object
    Access";origin=TWBDS1420;hostname=TWBD
    S1420;date="May 03 20:00:13
    2002";status=OPEN;severity=UNKNOWN;msg="Handle Close
    d:^M^M  Object Server:  Security^M^M    Handle ID:      4700^M^M
    Process
    ID:     2163821728";repeat_count=0;type=NT;sub_type="Audit
    Success";user="SYSTEM
    ";handle_no=0;full_text="Handle Closed:^M^M     Object Server:
    Security^M^M
    Handle ID:      4700^M^M        Process ID:
    2163821728";event_id="SECURITY";
    END
    .
    ### END EVENT ###
    PARSING_FAILED~'Line 1: Class Security undefined'
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    .
    The ^M characters are not the issue.  The class security is not
    defined
    within the baroc file correctly.
    .
    Another error you may receive is for the SQL Server evetns
    themselves.
    Because a space is a delimeter within TEC you might receive a
    pasring
    error with a "Class SQL undefined".
    .
    This is because the rules sent with TEMS, send TEC events which
    state
    for example "SQL SERVER 2000".  Because of this we get a
    failure.  As a
    workaround we remove the spaces in every rule, or replace the
    space with
    a "_".  And then edit the baroc file to reflect this.
    .
    ============================
    For each valid class in TEMS there should be line into the
    referenced
    *.baroc files showing
            "..." ISA TEMS
    example
            Security ISA TEMS
    The failure with SQL is because the class is defined as
            SQL SERVER
    and should be
            SQLSERVER
    or
            SQL_SERVER
    It should have no spaces embedded.
    Look for it in statements like in the class definition files.
            Class=SQL SERVER
    Change it to
            Class=SQLSERVER
    or
            Class=SQL_SERVER
    .
    The choice should match what is put in the robomon.baroc file.
    

Local fix

  • The workaround for the moment is to edit every rule and remove
    the spaces between rule arguments.
    .
    For example "SQL SERVER 2000" would be changed to
    "SQLSERVER2000" or "SQL_SERVER_2000".
    .
    The baroc file would also need to be edited and recompiled for
    TEC so the changes would take effect.
    .
    Also you could add a comment in the robomon.baroc file for each
    event sent from TEMS, to make TEMS events a superclass, such as
    .
    Security ISA TEMS
    .
    This will allow TEC to process the Security events because it
    will know which class it belongs to.  But this must be done for
    every TEC event TEMS sends out.  And then you must recompile the
    robomon.baroc file.
    

Problem summary

  • In the baroc file which is sent with the TEMS product, the
    classes which
    are generated have spaces within them.  In TEC a space is a
    delimeter
    and when an event is received by TEC, it fails because of a
    parsing
    error.
    

Problem conclusion

  • The workaround for the moment is to edit every rule and remove
    the spaces between rule arguments.
    .
    For example "SQL SERVER 2000" would be changed to
    "SQLSERVER2000" or "SQL_SERVER_2000".
    .
    The baroc file would also need to be edited and recompiled for
    TEC so the changes would take effect.
    .
    Also you could add a comment in the robomon.baroc file for each
    event sent from TEMS, to make TEMS events a superclass, such as
    .
    Security ISA TEMS
    .
    This will allow TEC to process the Security events because it
    will know which class it belongs to.  But this must be done for
    every TEC event TEMS sends out.  And then you must recompile the
    robomon.baroc file.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY34342

  • Reported component name

    TIV MGMT SOL MS

  • Reported component ID

    5698MSQ00

  • Reported release

    110

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-08-29

  • Closed date

    2003-09-15

  • Last modified date

    2003-09-15

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

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

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Management Solution for Microsoft SQL

Software version:

110

Reference #:

IY34342

Modified date:

2003-09-15

Translate my page

Machine Translation

Content navigation