Okay, thank you for your look into this.
I assumed that it is 'just' due to the implementation that was chosen.
But I think it's not intuitive,
and renders the usage of the device list to not always usable - for cases the
sequence is relevant.
There is fortunately a workaround, that is to (be on
=== Comment by Jan H. (copied&pasted manually as the mirroring
from IBM bugzilla <-> Canonical LP currently doesn't seem to work)
Responding to comment 7 [1] specifically in regards to the order of
device processing:
The order of processing when multiple devices are specified on the comman
The chzdev man page does not provide details on how the positional DEVICE
argument is processed:
DEVICE
Use the DEVICE positional argument of chzdev to select a single device
or a range of devices by device ID as target for a tool action. To se‐
lect a range of devices, spec
After having had a longer debug session (thx to Chris) it turned out
that this issue here is caused by an unexpected behaviour of the chzdev
command (part of s390-tools).
If one for example configures the following three DASDs during an interactive
installation in the following sequence and way:
