Edward, As you stated, the name of the image profile must match the name of the LPAR and so there can only be one image profile per LPAR.
However, if you need to have different versions of the image profile, such as when CBU is active and when it is not, then you do have some option. First, the Export/Import Activation Profiles task does let you export and import the entire set of activation profiles. In addition to letting you export/import using media, an HMC (or SE) can hold a set of activation profiles for a given system. Up to 8 different sets can be saved and each one can have a name. You could update the activation profiles and export the set and give it a name of "CBU" for example and then update the activation profiles again and export the set with a name of "Normal" and then you can use the task to quickly change the set of activation profiles on an SE between "CBU" and "regular", for example. The only drawback is that the entire set of activation profiles must be exported or imported. Another option is that the HMC offers both SNMP and WS APIs that can be used to query and to update image profiles. You could write scripts that run on your favorite server and that used SNMP or WS APIs to update the image profiles. In addition, GDPS/BCPii and z/OS BCPii offer z/OS based APIs that in turn use the SNMP APIs (sometimes referred to as BCPii v1) or the WS APIs (sometimes referred to as BCPii v2). This can be more work than just exporting or importing a full set of activation profiles but the big advantage is that you can use the APIs (either directly or thru z/OS) to update just one image profile and even just one image profile property of one image profile. And if you are already using z/OS and BCPii to do things like activating LPARs or IPLing LPARs, then it shouldn't be too difficult to create scripts to update image profiles. Tom Mathias ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
