Creating a new configuration from scratch

When building a configuration from scratch, you must create an empty IODF file as well as a new configuration file. From the File menu, choose IODFs... to display the IODFs dialog. Click on the Create... button to open the Create IODF dialog to create the new IODF on the host.

After a successful creation, the new IODF is added to the list of IODFs displayed in IODFs dialog.

Then, on the same dialog, with the new IODF selected, press the Load… button. This offers you a dialog to specify and save an HCM configuration file which is associated to the new HCD IODF. Now you are ready to create configuration objects. More information is in Loading the IODF.

z/OS:

For z/OS, HCM follows TSO/E data set naming rules. In addition, the IODF name must have the following format

    hhhhhhhh.IODFcc.yyyyyyyy.yyyyyyyy

where:

hhhhhhhh: is the TSO/E high level qualifier. If the name is enclosed in quotation marks then it must begin with a high-level qualifier. Otherwise, it must not and your user ID is used as the high-level qualifier.
cc: is a set of any two hexadecimal characters (0..9 or A..F)
yyyyyyyy: are optional qualifiers.

You must allocate enough space for the IODF. The minimum work size is 16; the default is 1024, which allows you to define at least 4000 devices, in general. You cannot change the space for an IODF later. If the configuration expands beyond this size, the IODF must be copied to a larger data set, using the Copy… button on the IODFs dialog (see Copying an existing IODF).

After you have entered the information, press OK to create the new IODF. Now select the IODF and load it as described in Loading the IODF.

z/VM

For z/VM, the name of an IODF is given by the file identifier of the CMS file. z/VM requires a certain naming convention in order to identify IODFs and accompanying files.

The CMS file name of an IODF must be IODFxx, where xx are two hexadecimal digits.

The CMS file type is:

WORKIODF: for a work IODF
PRODIODF: for a production IODF
BACKIODF: for a backup IODF

The file ID of the corresponding activity log consists of the CMS file name of the IODF and one of the following file types:

WORKACTL: for the activity log file of a work IODF
PRODACTL: for the activity log file of a production IODF
BACKACTL: for the activity log file of a backup IODF
WORKCLOG: change log file for automatic activity logging

Examples:

IODF01 WORKIODF A
IODF01 PRODIODF A

For more information about naming conventions for z/VM HCD refer to z/VM: I/O Configuration (SC24-6100).

To populate a new configuration file with data from an existing IODF, see Creating a new configuration from an IODF.