Build an IOCDS

When a production IODF has been created, you can build an IOCDS (it can be built only from a production IODF). Processors may have varying numbers of IOCDSs. A particular IOCDS is used at POR time to make the configuration data known to the CSS.

The following procedure is only recommended for processors that do not have an SNA address defined, including processors configured in a processor cluster. For processors in a processor cluster with an SNA address defined, use the procedure described under Build processor cluster IOCDSs.

While building IOCDSs HCD internally calls the IOCP program. Therefore, note that HCD must be installed in an APF-authorized library.

On the Primary Task Selection panel, specify the name of a production IODF and select Activate or process configuration data.
From the resulting panel select Build IOCDS. HCD displays the Processor List.

On the Processor List, select the processor and press the Enter key. HCD displays the IOCDS List.

Figure 1. IOCDS List for locally building the IOCDS

                          IOCDS List 
   Goto  Backup  Query  Help                                       
 ----------------------------------------------------------------  
                                                        Row 1 of 4 
                                                                   
 Select one or more IOCDSs, then press Enter.                      
                                                                   
 Processor ID . . : P101                                           
                                                                   
                           --Last IOCDS Update--                   
 / IOCDS  Name     Format  Date         Time                       
 _ A0                                                              
 _ A1     IODF05   BASIC   2010-01-28   14:27:38                   
 _ A2     IODF03   BASIC   2010-02-21   16:41:19                   
 _ A3

The IOCDS list shows those IOCDSs that are built using the currently accessed production IODF.

Whenever the IOCDS list is invoked, HCD tries to get actual IOCDS data (e.g. date and time of last update) for processors with SNA addresses directly from the support element (SE) and displays it.
IODF data is shown only if the SE does not provide information or where an SNA address is not defined.

A production IODF is updated with data retrieved from the SE if discrepancies between that data and the stored IODF data are detected.
On the IOCDS List, select the IOCDSs that you want to update and select Update IOCDS from the context menu (or action code u ). HCD displays the Build IOCDS panel.
Figure 2. Build IOCDS
```
 Build IOCDS 
                                                                             
                                                                             
 Specify or revise the following values.                                     
                                                                             
 IODF name . . . . . . . . . : 'SYS1.IODF02'                                 
 Processor ID  . . . . . . . : PROC2        IOCDS  : A0                      
                                                                             
 Title1  . _________________________________________________________________ 
 Title2  : SYS1.IODF02 - 2009-12-12 14:52                                    
                                                                             
 Dualwrite  . . . . . . . . . . . . . . No          Remote Write   No        
 Switch IOCDS for next POR  . . . . . . No                                   
 Write IOCDS in preparation of upgrade  No                                   
                                                                             
 Job statement information                                                   
 //WIOCDS  JOB (ACCOUNT),'NAME'                                              
 //*                                                                         
 //*                                                                         
 //*                                                                         
 //*                                                                         
 //*                                                                         
  F1=Help     F2=Split    F3=Exit     F5=Reset    F9=Swap    F12=Cancel      
                                                                             
```
On this panel, you can:
- Into the Title1 field enter identification information you want to be written on the first header line of the IOCP input data set. The first eight characters are used as IOCDS name. This input is used as the MSG1 parameter value of the IOCP ID statement. The batch job passes the MSG1 parameter to the IOCP input data set via the HCDCNTL DD statement (see Figure 1 and Figure 2).
- Specify the Dualwrite option that describes whether the IOCDS is to be updated on both sides of a physically partitioned processor.
- Specify whether you want to perform a remote or local write of an IOCDS for a processor that has a SNA address defined. The Remote Write option is initialized with 'Yes' if a SNA address is defined to the selected processor. In such a case, HCD initiates a remote IOCDS build and write to the support element with the designated SNA address. If the option is changed to 'No', a local IOCDS build is performed.
- Specify the Switch IOCDS for next POR option, that means whether you want to make this IOCDS the active one for the next power-on reset (POR).
- Specify whether to Write IOCDS in preparation of upgrade. This specifies whether an IOCDS is to be written regardless of processor type. This is useful to prepare for a processor upgrade.
  If Yes is specified, an IOCDS for the selected processor is written regardless of the processor type. For a list of processors that support writing an IOCDS, in preparation for a processor upgrade, or for which such an IOCDS can be written, see Supported hardware report.
  Note: If, as a result of a processor upgrade, an IOCDS download is not possible you can, after having built the production IODF, create an IOCP input data set that can be used with the stand-alone IOCP to generate an IOCDS for use with POR.
- Change the job statement information to meet the installation needs. Note that a batch job to build an IOCDS must run on the processor on which the IOCDS is to be updated. (See Job statement information used in panels for a description of the job control information that you need to specify when you build an IOCDS.)
  In a multiprocessor JES environment, be sure to specify the JES command and/or job class to ensure that the job runs on the correct processor(s).
  
  The recommended region size is 2 MBytes more than the IOCP needs. For the region size required by IOCP, refer to the IOCP User's Guide for your processor.
When an IOCDS is built, a record is written for the processor configuration. If you build a new IODF from an existing IODF, the records are copied to the new IODF. When you build IOCDSs from this new IODF, the IOCDSs from the old IODF are also shown on the IOCDS list. Because the batch job requires exclusive use of the production IODF for processors that have no SNA address specified, you have to either leave the HCD session or change the currently accessed IODF to run the submitted job.

You can also invoke the Build IOCDS task in batch mode, see Build an IOCDS or an IOCP input data set.

Note:

Unlike writing an IOCDS using the IOCP program, the HCD process generates no IOCP report when using the Build IOCDS function.
When a processor has been upgraded in the IODF, the old IOCDS status data in the IODF is deleted.

Using this procedure for processors with an SNA address:

If you use this procedure for processors in a processor cluster with an SNA address defined, HCD does the following:

HCD writes the IOCDS for that processor to the support element with the designated SNA address (remote IOCDS build).
If you run the job under z/OS®, HCD writes the IOCDS for that processor to the support element with the designated SNA address.

To run the batch job, you do not have to leave the HCD session. If the processor has defined an SNA address, HCD assumes that it is part of a processor cluster. In this case, the job can immediately start without the need to free the currently accessed IODF.

HCD tries to update the IOCDS record but is not able to because the IODF is still allocated by the HCD dialog. This results in an error message on the console log. To avoid this error message, HCD offers the profile option of bypassing the IODF information update (see Bypass IODF information update for SNA processor).