Nice suggestion for the "listCommands" command. I agree that something like that would definitely be useful and have forwarded this on to Product Management.
Regarding the jobResultKey, I believe the only way to get at this today via the BLCLI is to use the 'blcli SnapshotJob executeJobGetJobResultKey' command, which returns the jobResultKey for the job run. This of course assumes that you are executing the job as part of the script that is attempting to gain access to the job run.
The 'JobRun' namespace is not published and really isn't for external consumption. We strongly urge people to stick to supported commands, but if what I've mentioned above doesn't work for you, I'd suggest getting in touch with your BladeLogic PS person, who should be able to work something out.
Thanks for the info Tim.
The 'blcli SnapshotJob executeJobGetJobResultKey' command is fine for what I need in the script. I was attempting to test the script against previous snapshots, and realised there didn't seem to be an easy way to get the JobResultKey.
I agree. There should be a way to get at previous runs. I'll ask Support to log a ticket for this, as well as an enhancement request for the previous suggestion you had regarding the "listAllCommands" command.
FYI...I was just informed that in 6.3.2 there will be a command Job findAllRunKeysByJobKey, as well as an example in the docs explaining how to find a particular run.