Uproc conditionning created per CLI does not work

Document ID : KB000086098
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
No error.

Patch level detected:Dollar Universe 6.2.00
Product Version: Dollar.Universe 6.2.0

Description :To add a conditionning to an existing uproc per command line following commands were executed

====================================================================================================
uxupd upr app upr=UPR_0001 vupr=* nopartage depcon add condno=01 dep=UPR_0002 mu=SAME pdate=same sess=any status=terminated user=any expect nofatal one

uxupd upr app upr=UPR_0001 vupr=* nopartage depcon add condno=02 dep=UPR_0003 mu=SAME pdate=same sess=any status=terminated user=any expect nofatal one

uxupd upr app upr=UPR_0001 vupr=* nopartage depcon add condno=03 dep=UPR_0004 mu=SAME pdate=same sess=any status=terminated user=any expect nofatal one
====================================================================================================

Uxshw UPR ... confirms that conditions have been taken in account.

However the conditions are NOT displayed in the properties of the Uproc in UVC. (Launch formula section) They are not considered by DUAS in production, as jobs are immediately started when they are launched without any condition check.
Environment:
OS: All
Cause:
Cause type:
Configuration
Root Cause: Reason is that to make conditionning operational two steps are necessary
1. creating the condition with uxupd upr ..... depcon add command
Resolution:
If step 2 above, who determines the logical combining of all created conditions, is omitted, conditions will not be taken in account by DUAS.

Following the description above to make the condition operation, launch formula must be created per CLI as follows:

./uxupd UPR APP UPR=UPR_0001 FORMULA LFORM=\"=C01 AND =C02 AND =C03\"

Fix Status: No Fix

Additional Information:
Workaround :
N/A