Step 10. Perform an Initial Program Load (IPL)

IPL your system. After IPL, type the q hcd command on your z/VM console to see the active IODF. In the example response, you can see that only dynamic HW changes are enabled and that HCD is not controlling the software configuration, because no osconfig parameter had been specified in the SYSTEM CONFIG file.

HCD is currently active: IODF = IODF71 PRODIODF
HCD is enabled for dynamic hardware changes
HCD is not controlling the software configuration
HCD recovery is not currently required
Ready; T=0.01/0.01 09:53:09

You can enter the CP QUERY TOKEN command to see the current or target configuration tokens:

q token current

The current HCD configuration token is:
POL1....m.o.................10-03-1007:50:15SYS4  IODF71
Ready;

q token target

The target HCD configuration token is:
POL1....m.o.................10-03-1007:50:15SYS4  IODF71
Ready;

Note: The HCD token does not contain VM-TOKEN. It contains the name of the processor (POL1) and of the production IODF (IODF71).

Go to the SE (Support Element), then go to Input/Output (I/O Configuration). This screen shows the active IOCDS. Go to the tab, view Dynamic. On the Dynamic Information screen on the HMC console (Figure 1) you can check the configuration Data set token and the Hardware system area token. If HCD should be enabled for dynamic activation changes, both must be identical.

Screen shot of Information display from the support element — Figure 1. Information display from the support element

Note: Now your system is up and running according to your applied setup. As you provided for software and hardware changes, your system is also prepared for dynamic configuration changes. For more information, refer to topic Activate a Configuration Dynamically in z/VM I/O Configuration.