CSDL Mapping To ASDL Condition Evaluation Logic Issues

(Doc ID 988748.1)

Last updated on MARCH 03, 2015

Applies to:

Oracle Communications ASAP - Version 7.0.0 to 7.0.0 [Release 7.0.0]
Information in this document applies to any platform.
***Checked for relevance on 09-SEP-2012***
***Checked for relevance on 3-MAR-2015***

Symptoms

For ASAP 7.0.0, in the SARM when mapping CSDLs to ASDLs, the condition evaluation logic is wrong when:

1. There is double parenthesis in the evaluation condition. For instance, for:

(OLD_SMS LIKE "0")OR((NEW_SMS LIKE OLD_SMS)AND(NEW_DIR_NUM !LIKE OLD_DIR_NUM))


it is translated into

'OLD_SMS "0" LIKE NEW_SMS OLD_SMS LIKE OR NEW_DIR_NUM OLD_DIR_NUM !LIKE AND'


which sounds not correct.

In 4.7.1, it is translated into:

'OLD_SMS "0" LIKE NEW_SMS OLD_SMS LIKE NEW_DIR_NUM OLD_DIR_NUM !LIKE AND OR'


2. There is only a simple one level evaluation compared by LIKE or !LIKE, for instance,

'NEW_MIN LIKE OLD_MIN' is translated into 'NEW_MIN OLD_MIN', which missed LIKE.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms