Build I/O configuration data
This utility function allows you to build I/O configuration statements
from an IODF and to store them in a data set. The statements describe:
- Operating system configurations
- Processor configurations
- Switch configurations
The data sets created can be edited and re-migrated into the
IODF.
In addition, you can build:
- JES3 initialization stream checker data
- CONFIGxx members (from production IODF only)
- FCP device data
You invoke this function by passing the following parameter string:
Build I/O configuration
data
|--CONFIG--,--+-OS--,--+-osid-+----------------+----------------|
| '-*----' |
+-PR--,--+-procid-+--------------+
| '-*------' |
+-SW--,--+-swid-+----------------+
| '-*----' |
+-FCP--,--procid-----------------+
+-JES--,--osid--,--edt_id--------+
'-XX--,--| CONFIGxx_parameters |-'
CONFIGxx_parameters:
.-U-.
|--xx--,--procid--,--+--------------+--,--osid--,--+---+--,--+--------+--,--+---------+--|
'-partition_id-' '-R-' '-backup-' '-sysplex-'
- OS | PR | SW | FCP |JES | XX
- Function indicator:
- OS
- Build OS configuration statements
- osid
- OS configuration ID (up to 8 characters)
- *
- If you specify * in place of an OS configuration ID,
HCD searches for a list of OS configuration IDs in a data set allocated
to HCDCNTL. If no data set has been allocated to DD name HCDCNTL,
statements are built for all operating systems in the IODF.
- PR
- Build processor configuration statement
- procid
- Processor ID (up to 8 characters)
- *
- If you specify * in place of a processor ID, HCD searches
for a list of processor IDs in a data set allocated to HCDCNTL. If
no data set has been allocated to DD name HCDCNTL, statements are
built for all processors in the IODF.
If only the coupling facility
partition and CF receive channels are to be generated for a particular
processor, the respective processor ID in the list has to be qualified
by the keyword CF, according to the following syntax:
|--procid--+-------+--------------------------------------------|
'-,--CF-'
- SW
- Build switch configuration statements
- swid
- Switch ID (2 hexadecimal characters)
- *
- If you specify * in place of a switch ID, HCD searches
for a list of switch IDs in a data set allocated to HCDCNTL. If no
data set has been allocated to DD name HCDCNTL, statements are built
for all switches in the IODF.
Furthermore, specifying
an asterisk (*) as switch ID, and setting the profile keyword
SHOW_CONFIG_ALL to YES, additionally generates configuration statements
for control units and devices without a processor and OS connection.
- FCP
- Export FCP device data into CSV output format
- procid
- Processor ID (up to 8 characters) for which to export the FCP
device data.
- JES
- Build JES3 initialization stream checker data
- osid
- OS configuration ID (up to 8 characters)
- edt_id
- EDT ID (2 hexadecimal characters)
- XX
- Build CONFIGxx members
- xx
- Suffix of the CONFIGxx member to be built
- procid
- Processor ID (up to 8 characters)
- partition_id
- Partition name; required entry, if the processor is in LPAR
mode (up to 8 characters).
- osid
- OS configuration ID (up to 8 characters)
- U/R
- U updates the current CONFIGxx member. The CHP and
DEVICE statements are replaced and all other statements remain unchanged.
This is the default.
R deletes the current CONFIGxx member
and generates new CHP and DEVICE statements.
- backup
- Name for the backup copy of the current CONFIGxx member (up
to 8 characters).
- sysplex
- Name of the sysplex used for setting managed channel paths to
ONLINE.
Batch invocation
A data set must be allocated to the following DD names when invoking
the batch utility.
DD name | Description |
---|
HCDIODFS | Source IODF | HCDDECK | Generated output data set
For CONFIGxx
this must be a data set name of a partitioned data set. | HCDMLOG | HCD Message Log data set | HCDCNTL | Optional for specifying a list of
operating systems, processors, or switches
Not applicable for building
CONFIGxx member or JES3 inish data set | HCDTRACE | Optional for capturing the trace
if trace is activated. |
Example 1:
The following example shows a job to build a configuration data
set containing processor configuration PROC1 including its CF connections
to processor PROC2.
//BWINJOB JOB (3259,RZ-28),'BWIN',NOTIFY=BWIN,CLASS=A,
// MSGCLASS=Q,MSGLEVEL=(1,1),REGION=4M
//*
//* BUILD Processor configuration statement
//*
//BUILD EXEC PGM=CBDMGHCP,PARM='CONFIG,PR,*'
//HCDIODFS DD DSN=BWIN.IODF03,DISP=SHR
//HCDDECK DD DSN=BWIN.IODF.03.DECKS(PROC1),DISP=SHR
//HCDMLOG DD DSN=BWIN.HCD.LOG,DISP=OLD
//HCDCNTL DD *
PROC1
PROC2,CF
/*
//
Example 2:
The following example shows a job to update CONFIG03 in data
set SYS1.PARMLIB from processor configuration PROC1, partition LPAR1
and OS configuration MVS1 while saving the existing member under the
name CONFBK03.
//BWINJOB JOB (3259,RZ-28),'BWIN',NOTIFY=BWIN,CLASS=A,
// MSGCLASS=Q,MSGLEVEL=(1,1),REGION=4M
//*
//* BUILD CONFIGxx
//*
//BUILD EXEC PGM=CBDMGHCP,PARM='CONFIG,XX,03,PROC1,LPAR1,MVS1,U,CONFBK03'
//HCDIODFS DD DSN=BWIN.IODF03,DISP=SHR
//HCDDECK DD DSN=SYS1.PARMLIB,DISP=SHR
//HCDMLOG DD DSN=BWIN.HCD.LOG,DISP=OLD
/*
//
|