Displaying auto-configuration data

7.1 LPAR mode

The lszdev command can display auto-configuration data.

Use the lszdev command with the --auto-conf option to display a list of devices for which auto-configuration data is available.

Example:

# lszdev --auto-conf
TYPE       ID        AUTO
dasd-eckd  0.0.ec30  yes
dasd-eckd  0.0.ec31  yes

Auto-configuration settings can be overridden with settings in the persistent configuration. Omit the --auto-conf option to find out for which devices auto-configuration is effective:

Example:

# lszdev
TYPE         ID                          ON   PERS   NAMES
dasd-eckd    0.0.ec30                    yes  yes    dasda
dasd-eckd    0.0.ec31                    yes  auto   dasdb
dasd-eckd    0.0.ec32                    yes  no     dasdc
qeth         0.0.f5f0:0.0.f5f1:0.0.f5f2  yes  no     enccw0.0.f5f0
generic-ccw  0.0.0009                    yes  no

In the example, auto-configuration data is effective for only one device, 0.0.ec31. Effective auto-configuration data is indicated through the value auto in the PERS column of the command output.

The lszdev output for detailed information about a device includes a separate column, AUTOCONF, for auto-configuration data, if available.

Example:

# lszdev -i 0.0.ec31
DEVICE dasd-eckd 0.0.ec31
Names                : -
Modules              : dasd_eckd_mod dasd_mod
Online               : no
Exists               : yes
Persistent           : no
Auto-configured      : yes

ATTRIBUTE                     ACTIVE   PERSISTENT  AUTOCONF
cmb_enable                    "0"      -           -
eer_enabled                   "0"      -           -
erplog                        "0"      -           -
failfast                      "0"      -           -
last_known_reservation_state  "none"   -           -
online                        "1"      -           "1"
raw_track_access              "0"      -           -
readonly                      "0"      -           -
reservation_policy            "ignore" -           -
use_diag                      "0"      -           -

If the AUTOCONF column is omitted, no auto-configuration data is available for this device. You can force the column with the --auto-conf option.

For debugging or testing purposes, you can access the raw auto-configuration data that DPM provides to Linux through the sysfs attribute /sys/firmware/sclp_sd/config/data. This data is not human‑readable, but you can import it into the chzdev tooling by using the chzdev --import command. Importing the data allows Linux to interpret the raw auto‑configuration information as if it were supplied directly through the zdev interface. For example:

# chzdev --import /sys/firmware/sclp_sd/config/data --auto-conf

After importing the raw data, you can modify the resulting auto‑configuration using additional chzdev commands together with the --auto-conf option. These modifications affect only the currently running system, and Linux applies them immediately. However, any changes made through chzdev are temporary and are lost on the next reboot.

To make persistent changes to the auto‑configuration, you must adjust the underlying device configuration on the DPM hardware interface, through the HMC panels or APIs. DPM generates updated auto‑configuration data from this hardware‑level configuration, and Linux processes the new data during the next boot of the partition.