after you get the sub job headers, i think you need to convert them to dbkeys, so run:
then something like
to make it a list you can loop through
you'll need to run w/ the unreleased commands enabled. (use the nsh performance commands)
Worked like a charm. Had to steal a couple comments from the previous thread about 'Utility setTargetObject', but I got all the information I needed. You are my personal savior!
Thank you again,
ideally you should write your own "complex command" w/ this command string... that's the next level :)
We're big on the scripting and automation here. Running things through the CLI were never part of the plan. :) I used another of your posts to help with that as well.
well, remember that you can put this all into nsh scripts and then run it through the gui...
As you are "big in scripting and automation" (and hopefully still active here in the community ;-) ) could you tell me, if it's possible to create a complex command in an own namespace, i.e. no namespace already provided by BMC BladeLogic?
For what purpose?
If you name the file w/ the new namespace, and have that in the xml, it may work..
Also – I’ve found that w/ the unreleased commands enabled in the nsh performance commands, it’s much eaiser just to do the unreleased bits in my scripts directly instead of writing and maintaining the custom xml.
Thank you Bill. We want to build a command for retrieving the "file-server"-path to some nsh-script. This could be done with two blcli-commands which we want to "bundle". Ok, it's one command instead of two, but for people not so familiar with blcli this is already an easement.
but why would this be a new namespace? i would think it would still be in NSHScript ?