Build a production IODF
Although HCD validates configuration data as it is entered, a complete
validation may not be performed, because data may not be defined at
this time. Therefore, a "post-validation" is performed at "Build Production
IODF" time. This validation might issue messages you have to deal
with, according to their severity. The production IODF is not created
if any errors with a severity higher than 'warning' are produced.
During the validation HCD invokes the IOCP program to perform checking
of the channel packaging rules. Therefore, note that the correct version
of the IOCP program must be accessible.
Depending on what is defined in the configuration, the work IODF
must contain a definition for at least one operating system, or one processor, or one
switch.
Note
A production IODF must have a single extent. If the production
IODF has multiple extents, the IPL process results in a WAIT state
(wait state code '0B1', reason code '002'). HCD issues error message
CBDA009I if a production IODF cannot be built in a single extent.
You can use production IODFs with multiple extents for
dynamic activation only. In this case, HCD warns you with message
CBDA009I that an IPL with this IODF is not possible, but dynamic activation
continues.
To build a production IODF, perform the following steps:
- On the HCD entry panel, select Activate
or process configuration data.
Figure 87. Activate or Process Configuration Data
*------ Activate or Process Configuration Data ------*
| |
| |
| Select one of the following tasks. |
| |
| __ 1. Build production I/O definition file |
| 2. Build IOCDS |
| 3. Build IOCP input data set |
| 4. Create JES3 initialization stream data |
| 5. View active configuration |
| 6. Activate or verify configuration |
| dynamically |
| 7. Activate configuration sysplex-wide |
| 8. *Activate switch configuration |
| 9. *Save switch configuration |
| 10. Build I/O configuration data |
| 11. Build and manage System z cluster IOCDSs, |
| IPL attributes and dynamic I/O changes |
| 12. Build validated work I/O definition file |
| |
| * = requires TSA I/O Operations |
| F1=Help F2=Split F3=Exit F9=Swap |
| F12=Cancel |
*----------------------------------------------------*
- From the resulting panel, select Build production I/O definition file. Prior to actually building the production or validated
work IODF, HCD updates the work IODF in the following way:
- For processors, that must be defined for a maximum HSA, it extends
the processor configuration to its maximum. This means, HCD ensures
that all logical channel subsystems as well as all partitions are
defined for the processor, and that each channel subsystem allows
for the maximum number of devices per subchannel set.
- For every primary operating system configuration that specifies
the name of a disaster recovery (D/R) site operating system configuration,
HCD generates the D/R site OS configuration.
Thereafter, HCD validates the configuration data in the work
IODF. If the work IODF is valid, then a production IODF or
validated work IODF can successfully be built.
HCD
also invokes the IODF checker function that performs a health check
of the IODF. In case of defects, HCD issues a severe warning message.
For work IODFs containing XMP processor
definitions, before you can build a production IODF, the correct PCHIDs
must be defined in the work IODF. You can use the CHPID Mapping Tool to achieve
the task to either insert missing PCHIDs or to update PCHIDs in a
work IODF. However, inserting or updating PCHIDs into an IODF using
the CHPID Mapping Tool is only possible with a so-called validated
work IODF that you can get in one of two ways:
- Use the task Build validated work I/O
definition file. This task validates a work IODF for correctness
and completion, and may issue messages that describe incomplete or
erroneous logical definitions. Missing PCHID values are not flagged
as errors. If errors occur, correct them an restart this task. As
soon as no more errors occur, the output from this task is a validated
work IODF.
- If you tried to build a production IODF without being aware of
one or more missing PCHIDs for XMP processors, but the work IODF satisfies
all other validation rules, then the output from Build
production I/O definition file, too, is a validated work IODF.
A message will show all CHPIDs for which the required PCHIDs are missing.
With a validated work IODF, you can use the CHPID Mapping Tool to accomplish
the task to update or insert required PCHIDs. Input to this tool is
an IOCP input data set. To get this input, now use the task Build IOCP input data set from the panel
shown in Figure 87. This leads you to the Build IOCP Input Data Set panel shown in Figure 95. Because the input to the CHPID Mapping Tool must be a stand-alone
IOCP, in this panel, specify the appropriate option as shown:
Input to Stand-alone IOCP? Yes (Yes or No)
How
to proceed using the CHPID Mapping Tool to get PCHIDs inserted or updated in
the validated work IODF, see How to interact with the CHPID Mapping Tool. As soon as all
PCHIDs are correct in the validated work IODF, the production IODF
can be built.
- If you initially requested activity logging, a panel like the
one shown in Activity logging and change logging is displayed. Enter the activity
logging details your installation requires. The Build Production
I/O Definition File screen is displayed.
Figure 88. Build Production I/O Definition File
*-------------- Build Production I/O Definition File --------------*
| |
| |
| Specify the following values, and choose how to continue. |
| |
| Work IODF name . . . : 'DOCU.IODF01.WORK' |
| |
| Production IODF name . 'DOCU.IODF01' |
| Volume serial number . DATA01 + |
| |
| Continue using as current IODF: |
| 2 1. The work IODF in use at present |
| 2. The new production IODF specified above |
| |
| |
| |
| F1=Help F2=Split F3=Exit F4=Prompt F9=Swap F12=Cancel|
*------------------------------------------------------------------*
The selection of option Continue using as current IODF controls
which IODF is in access after the production IODF has been built.
In addition, if you select option 1, The work IODF in use as
present, the content of the currently built production IODF
is copied to the work IODF. This ensures that the work IODF contains
the latest configuration tokens of the IODF, and you can continue
to use the work IODF for further updates. If you select option 2, The
new production IODF specified above, the content of the production
IODF is not mapped into the work IODF. In that case, you should start
from the newly built production IODF when performing further changes
to the I/O configuration.
- Specify the name and volume serial number (if applicable) for
the production IODF. IODF naming convention describes the syntax of
a production IODF name. If you choose a name without complying to
the prescribed syntax of a production IODF name, that IODF can not
be used for the IPL and dynamic activate. Moreover, to perform a dynamic
activate, the high-level qualifier of the production IODF has to be
the same as the one of the IODF used for the previous IPL or dynamic
activate.
If the data set name for the production IODF does not
adhere to the naming convention for a production IODF, the Confirm
Production IODF Name panel is displayed, and you must confirm the
IODF name.
Figure 89. Confirm Production IODF Name
*------------------- Confirm Production IODF Name -------------------*
| |
| |
| The data set name you specified does not follow the naming |
| convention for production IODFs. You will not be able to IPL |
| or ACTIVATE a system configuration from an IODF with this data |
| set name. |
| |
| Confirm the specified IODF name . . 1_ 1. Yes |
| 2. No |
| |
| F1=Help F2=Split F3=Exit F9=Swap F12=Cancel |
*--------------------------------------------------------------------*
If you use the same name for the new IODF as for an existing
IODF, you can replace the existing IODF. In that case, the Confirm
Delete I/O Definition panel is shown. Select yes, to confirm
deletion of the IODF. Be careful, not to delete the active IODF.
If you have specified the name of the active IODF, another confirmation
panel is shown that warns you once more about the effect of the chosen
name.
Figure 90. Confirm Delete I/O Definition File
*--------------- Confirm Delete I/O Definition File ----------------*
| |
| |
| To confirm delete request, select Yes. To cancel delete request, |
| select No. |
| |
| Delete request confirmed . . . __ 1. Yes |
| 2. No |
| |
| Creation date . . : 1997-06-10 |
| Last update . . . : 1997-09-10 14:19 |
| Volume . . . . . . : SMS012 |
| |
| Description . . . : IODF for raised floor 710 |
| For systems D0, D2, D4 and D6 |
| incl. sensed data and mig. SW data |
| |
| |
| F1=Help F2=Split F3=Exit F9=Swap F12=Cancel |
*-------------------------------------------------------------------*
- After pressing Enter, the Define Descriptor Fields panel appears.
Figure 91. Define Descriptor Fields
*-------------------- Define Descriptor Fields --------------------*
| |
| |
| Specify or revise the following values. |
| |
| Production IODF name . : 'DOCU.IODF01' |
| |
| Descriptor field 1 . . . DOCU |
| Descriptor field 2 . . . IODF01 |
| |
| F1=Help F2=Split F3=Exit F5=Reset F9=Swap F12=Cancel |
*------------------------------------------------------------------*
Specify the descriptor field 1, 2,
or leave the default values. The descriptor fields describe the IODF
and will be part of the HSA token. Attention: If
you specify asterisks (**), equals (==), pluses (++), or minuses (--)
for the IODF suffix in LOADxx, never change the default descriptor
field values, because z/OS uses these values to find the current
IODF during IPL. Take this relationship also into consideration, if
you copy the IODF to a different data set name. For further details
refer to z/OS HCD Planningz/OS HCD Planning. After the production IODF is built,
HCD displays a message.
- If the work IODF has an activity log file defined for the work
IODF, it is copied. After the production IODF has been built, HCD
informs you that the production IODF has been created.
You can also create a production IODF using the HCD batch facility
(for details see Build a Production IODF).
Note:
If the work IODF has an associated MCF, the MCF data set is copied
and associated to the production IODF.
|
z/OS HCD User's Guide
Copyright IBM Corporation 1990, 2014