nerdexam
IBM

000-221 · Question #198

When updating a device attribute utilizing the -P flag with the chdev command, which of the following is true?

The correct answer is D. The device attribute is updated only in the ODM and does not take affect until after the next system boot. The -P flag with chdev updates the device attribute only in the ODM database, making the change persistent across reboots but not active until the system is restarted.

System Management

Question

When updating a device attribute utilizing the -P flag with the chdev command, which of the following is true?

Options

  • AThe device attribute will be updated for the parent of the device specified.
  • BThe device attribute is updated forcibly and will result in the device changing to the defined state.
  • CThe device attribute is updated immediately and will not be maintained after the next system boot.
  • DThe device attribute is updated only in the ODM and does not take affect until after the next system boot.

How the community answered

(59 responses)
  • A
    3% (2)
  • B
    8% (5)
  • C
    15% (9)
  • D
    73% (43)

Why each option

The -P flag with chdev updates the device attribute only in the ODM database, making the change persistent across reboots but not active until the system is restarted.

AThe device attribute will be updated for the parent of the device specified.

The -P flag operates on the specified device itself, not its parent device; there is no flag behavior that redirects changes to a parent.

BThe device attribute is updated forcibly and will result in the device changing to the defined state.

Forcibly changing a device to a defined state immediately describes a different behavior, closer to chdev without the -P flag or using -f.

CThe device attribute is updated immediately and will not be maintained after the next system boot.

This is the opposite of -P behavior; an immediate change that is not persistent would apply to the running system only and be lost at reboot.

DThe device attribute is updated only in the ODM and does not take affect until after the next system boot.Correct

AIX uses the Object Data Manager (ODM) as its configuration database. The chdev -P flag writes the attribute change solely to the ODM without applying it to the running device driver. This means the device continues operating with its current in-memory attribute value until the next boot, at which point the ODM value is applied during device configuration.

Concept tested: AIX chdev -P flag and ODM persistent attribute update

Source: https://www.ibm.com/docs/en/aix/7.3?topic=c-chdev-command

Topics

#chdev#ODM#device management#system reboot

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 000-221 Practice