BMC BladeLogic can apply patches to global and local zone setups where no lib or
var is shared between the global and local zones. BMC BladeLogic does not support
patching on whole-root and sparse-root zones.
BL does not stop local zones before applying patches to a global zone. Its
recommended to stop local zone before zone patching and users should try doing
this using a separate deploy command.
Are you talking about Patch Clusters ? If yes, they are supported, patch clusters can be specified as filters in Patch Catalogs and analysis and remeidiation can be run against the same.
We were not trying to patch Whole root zones and sparse zones as individual entities.
However, we wwere just trying to patch a global zones (on top of them, sparse/whole root zones were hosted).
Applying patches to Global zone helped and it also patched hosted sparze/whole root zones on it automatically.
It is recommended to configure pdo.conf file in /etc/patch for a better parallel performance in case if zones are hosted on global zone. If we dont configure it, BL follows sequential patching and takes little more time.