000-221 · Question #169
What additional NIM functionality is gained by installing the optional dsm.core fileset?
The correct answer is C. NIM can initiate an automated bos_inst install operation of an LPAR. Installing the optional dsm.core fileset grants NIM the ability to autonomously initiate a full automated BOS installation against an LPAR without manual operator steps.
Question
What additional NIM functionality is gained by installing the optional dsm.core fileset?
Options
- ANIM can query the WWPN of an uninstalled LPAR.
- BNIM can initiate DLPAR operations against an installed LPAR.
- CNIM can initiate an automated bos_inst install operation of an LPAR.
- DNIM can automate a TSM backup before applying APARs or patches
How the community answered
(20 responses)- A5% (1)
- B15% (3)
- C70% (14)
- D10% (2)
Why each option
Installing the optional dsm.core fileset grants NIM the ability to autonomously initiate a full automated BOS installation against an LPAR without manual operator steps.
Querying an LPAR's WWPN is an HMC or VIOS-level SAN fabric management function and is not a capability added to NIM by installing dsm.core.
Initiating DLPAR operations is controlled through the HMC API or the RSCT (Reliable Scalable Cluster Technology) subsystem, not through NIM or any NIM optional fileset.
The dsm.core fileset integrates NIM with IBM's Dynamic Systems Management layer, enabling NIM to programmatically trigger a bos_inst operation on an LPAR end-to-end. Without this fileset NIM can define and serve installation resources but cannot independently start the installation workflow. This capability is critical for large environments that require unattended, repeatable LPAR provisioning at scale.
Automating TSM backups before patch application is handled by the TSM client scheduler and its own filesets, not by dsm.core or the NIM framework.
Concept tested: NIM dsm.core fileset automated BOS installation capability
Source: https://www.ibm.com/docs/en/aix/7.3?topic=nim-installing-optional-nim-filesets
Topics
Community Discussion
No community discussion yet for this question.