In some situation, an event that includes a correct event class becomes PARSING_FAILED but in other situation it is treated as PROCESSED event. What is the possible cause?
If a slot that has numeric type, it can be treated as PARSING_FAILED or PROCESSED.
The numeric typical attribute can be expressed as DECIMAL, HEX and OCTAL.
If the value is started with '0', the value is treated as an OCTAL value. And if the value is started with '0x', it is treated as HEX.
For example, if 'PROD_Code slot has INTEGER type, the 'PROD_Code=1234' is treated as DECIMAL (1234) but 'PROD_Code=01234' is treated as OCTAL(668) . Each values are not same.
So, if the 'PROD_Code=0128' is set, the event becomes PARSING_FAILED because '8' is not allowed in OCTAL .
This can be applicable other attributes REAL and INT32 and ENUM.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.