Conditions remain after deleting conditions attribute and importing updated JIL file

Document ID : KB000116783
Last Modified Date : 02/10/2018
Show Technical Document Details
Issue:
After deleting the condition attribute from a JIL file, an attempt to update the existing job definition via the JIL command successfully updates the job, yet the conditions remain in place. 
Environment:
Any OS
Any Database
Resolution:
This is expected behavior. The condition attribute must remain in the JIL file but have nothing defined to the attribute; as shown below, in order to effectively remove the conditions.

insert_job: my_test_job   job_type: CMD
command: sleep 60
machine: redhat-1136sp6
owner: root
permission:
date_conditions: 0
condition:
alarm_if_fail: 1