Build an IOCDS or an IOCP input data set
This utility function builds the IOCDS or the IOCP input data set using the definitions of a production IODF. This function is invoked by passing the following parameter string.
Build an IOCDS or an IOCP input data set
- iocds
- is a two-character IOCDS identifier, if building an IOCDS
- procid
- Processor ID
- D | I | W | S | T
- One-character request code:
- D
- Build an IOCP input data set
- SA
- The generated IOCP statements can be used for the stand-alone IOCP program (default).
- NOSA
- Depending on the HCD profile option MIGRATE_EXTENDED=YES, the
generated IOCP statements have additional information that can be
used for the extended migration. This information is shown as comments
to IOCP. Note: An IOCP input data set generated with operand NOSA may not be accepted by the stand-alone IOCP program, because of differences between the IOCP program running in z/OS® and the stand-alone IOCP program.
- I
- Build an IOCDS
- NOCHKCPC
- Write an IOCDS regardless of the type of the receiving processor. Refer to Supported hardware report for a list of processor types that can receive an IOCDS in preparation for a processor upgrade and for processor types for which such an IOCDS can be written.
- LOCALWRT
- This parameter enforces a local IOCDS write. A defined SNA address which is normally used by HCD to initiate a remote IOCDS build to the support element with the designed SNA address, is ignored in this case.
- W
- Build an IOCDS with dual-write option (optionally with NOCHKCPC and LOCALWRT, see option I).
- S
- Build an IOCDS and set the IOCDS active for next POR
- T
- Build an IOCDS with dual-write option and set the IOCDS active for next POR