1 of 1 people found this helpful
blcli_execute NSHScriptJob findByGroupAndName "/Group" "Job Name"
blcli_execute Utility storeTargetObject job
blcli_execute Job clearNotificationList
blcli_execute Job update NAMED_OBJECT=job
Thanks Bill. That was it. I would have never figured that one out. !
there's some info about this here: Best Practice Using the BLCLI [Detailed]
when you see the unreleased commands that don't take any input or any args for what object to act on (eg a set command that takes just the value but not a dbkey of an object) those are going to act on an object in memory. generally the 'find' command will load the object into memory. then you do the set or clear or whatever, then the save/update.