Keywords

The following keywords are supported for a profile statement:

Volume serial number to allocate output data sets

To place the IOCP, HCPRIO, and JES3 INISH stream checker data sets to a specific volume within HCD, you can specify this target volume via two profile options:

HCDDECK_VOL

Specifies the volume serial number for allocating a new IOCP, HCPRIO or other data set containing I/O configuration statements.

HCDJES3_VOL

Specifies the volume serial number for allocating a new JES3 initialization stream checker input data set.

In a non-SMS managed environment, the generated corresponding output data set is placed on the indicated volume. The profile option is ignored if the specified output data set already exists on a different volume. In this case, the new output data set replaces the existing data set on this volume. In an SMS-managed environment this option is ignored. 

The two options have no effect in an SMS managed environment since SMS overrules the VOLUME parameter.

If the keywords are omitted, the placements of the IOCP, HCPRIO, JES3 INISH, and other I/O configuration data sets are controlled via SMS or ESOTERIC system defaults (ALLOCxx of SYS1.PARMLIB or the UADS, respectively).

Volume serial numbers to allocate log data sets and HCM MCF data set

ACTLOG_VOL

If the dataset names are not managed by SMS, this keyword specifies the up to 6 characters long volume serial number to allocate a new activity log. Using an asterisk (*) indicates that the activity log file will be placed on the same volume where the associated IODF resides.

CHLOG_VOL

If the dataset names are not managed by SMS, this keyword specifies the up to 6 characters long volume serial number where to allocate the change log data set. Using an asterisk (*) indicates that the change log file will be placed on the same volume where the associated IODF resides.

MCF_VOL

If the data set names are not managed by SMS, this keyword specifies the up to 6 characters long volume serial number where to allocate the MCF data set. Using an asterisk (*) indicates that the MCF data set will be placed on the same volume where the associated IODF resides.

Automatic activity logging

CHANGE_LOG

YES/NO. Specifies whether you want to activate change logging (YES). The default is NO.

If enabled, and HCD additionally maintains an activity log file for the IODF, then HCD logs all updates applied to the IODF in a change log file, and automatically generates activity log entries for updates on HCD objects, for example, add, delete, update or connect, disconnect. These entries are proposals and are shown in the activity log panel where you can modify them before you exit the IODF (see also Activity logging and change logging).

A change of the value setting for this keyword will not be active until the next start of HCD.

Allow or prohibit mixed esoterics

MIXED_ESOTERIC

YES/NO. Specifies whether you want to allow or prohibit mixed devices (DASD and TAPE) under the same esoteric name. If you specify NO, which is the default, and your configuration contains an esoteric with mixed DASD and TAPE devices, the request to build a production IODF will fail with error message CBDA332I. If you specify YES, HCD issues message CBDA332I as warning message and continues the request.

HLQ for exporting IODFs

EXPORTED_HLQ

By default, when exporting an IODF, the generated sequential data set is written with the high-level qualifier (HLQ) of the userID that issued the Export IODF function. If this convention is not suitable for your installation, you can use the keyword EXPORTED_HLQ to specify a different HLQ (up to 8 characters).

Allocation space for data sets allocated due to HCM requests

ALLOC_SPACE

This HCD profile option lets you overwrite the default allocation (CYL,50,50) for data sets that are temporarily allocated in response to HCM requests, such as HCDASMP, HCDRPT, HCDIN. For example, specify: ALLOC_SPACE = HCDASMP,nn where nn is the size (decimal number) used for primary and secondary allocation (in CYL).

Extending allocation space

MCF_EXTENSION

This HCD profile option lets you define additional space when allocating the MCF data sets to allow for updates.

With this keyword, you specify the percentage of additional space that is to be allocated when defining an MCF data set. Per default an MCF data set is allocated with 30 percent additional space than actually needed to hold the MCF data. You can use this space for updates that consume data space without the need to allocate a new MCF and delete the old one. For example, MCF_EXTENSION = 50 allocates 50% additional space.

CHLOG_EXTENSION

This HCD profile option lets you define additional space when allocating the change log data set.

With this keyword, you specify the percentage of additional space that is to be allocated when defining a change log data set. By default, a change log data set is allocated with the same size as the associated IODF. For example, a value set to 50 allocates 50% additional space.

The default extension is 0.

Name and volume serial number for UIM library

UIM_LIBNAME

Specifies the name of the data set containing the UIMs, the associated UDTs, and any help members for the UIMs. If the keyword is omitted, SYS1.NUCLEUS is assumed (Note: only UIMs residing in SYS1.NUCLEUS are read during IPL!).

When UIM_LIBNAME is specified, HCD does not implicitly access SYS1.NUCLEUS for loading the UIMs.

If you specify an asterisk (*) as data set name, HCD assumes that the UIM data set (including SYS1.NUCLEUS) is part of the ISPF load library concatenation chain, contained in the JOBLIB/STEPLIB concatenation chain, or specified in the active LNKLSTxx member.

You can only define one data set with the UIM_LIBNAME statement. If you want to specify several data sets, specify an asterisk (*) as data set name and specify the data sets in the JOBLIB/STEPLIB concatenation chain.

UIM_VOLSER

Specifies the volume serial number of the UIM library. Required only if the data set is specified via keyword UIM_LIBNAME and is uncataloged.

Load VM UIMs

VM_UIM

YES/NO. Specifies whether VM UIMs will be loaded. The default is YES. Installations without VM should specify NO to gain some performance improvement during HCD initialization.

Options for text reports

LINES_PER_REPORT_PAGE

Specifies the maximum number of lines per page for reports. The default value is 55.

UPPERCASE_ONLY

YES/NO. Specifies whether all HCD reports will be written in uppercase or not. This is useful when using printers that do not have the English codepage. The default is NO.

Layout of graphical reports

GCR_SCALE

Specifies the scaling factor for graphical reports when using BookMaster. The default is GCR_SCALE=.6.

GCR_COMPACT

YES/NO. Allows more objects to be displayed in a graphical report. The default is NO. Depending on the report type, a different maximum number of objects is shown on one page:

Report Type	COMPACT=NO	COMPACT=YES
CU	12 channels, 8 control units	16 channels, 10 control units
LCU	8 channels, 8 control units	8 channels, 8 control units
CHPID	8 channels, 64 control units	16 channels, 64 control units
Switch	1 switch	1 switch
CF	1 coupling facility	1 coupling facility

GCR_FORMAT

Specifies the formatting type:

BOOKIE

For BookMaster. This is the default.

DCF

creates a data set for DCF containing script commands.

GML

creates a data set for DCF containing GML tags.

GDF

creates one or more members in GDF format for printing with GDDM (not for batch).

GCR_FONT

Specifies the font to be used for printing; applicable only if GCR_FORMAT=DCF or GCR_FORMAT=GML was specified. Specify the appropriate font supported by your installation. For information on how to create a graphical report, see Create or view graphical configuration reports.

Color settings for graphical display function

(The following colors are valid specifications: green, red, blue, black, purple, pink, yellow, brown, and white.)

COLOR_NORM

Specifies the color used when drawing the picture. Make sure that the color is visible on defaulted or specified background. The default is GREEN.

COLOR_TEXT

Specifies the color used for any text in the picture. The default is GREEN.

COLOR_HIGH

Specifies the color to be used when identifying a focused object. The default is RED.

COLOR_BACKGROUND

Specifies the background color. If nothing is specified, the graphical display function uses the standard background of the terminal.

Support of TSO option NOPREFIX

TSO_NOPREFIX

YES/NO. Specifies whether the TSO profile option NOPREFIX is recognized by HCD. The default is NO. If you specify TSO_NOPREFIX=YES, and the TSO option NOPREFIX is active, all data set names specified in the HCD dialog are taken as is, i.e. HCD does not add a high-level qualifier. Data set names that are generated by HCD act independent of the TSO option NOPREFIX, and the user ID is added as the high-level qualifier.

Esoteric token when migrating MVSCP input data sets

ESOTERIC_TOKEN

YES/NO. YES specifies that HCD will assign esoteric tokens in ascending order when migrating an MVSCP input data set. NO (which is the default) specifies that no tokens will be assigned.

Control unit type when migrating IOCP input data sets

MAP_CUTYPE

Specifies how a control unit type in an IOCP input data set is mapped to a control unit type in the IODF. Specify one or more of the following mappings:

MAP_CUTYPE = xxxxx,yyyy-yy

xxxxx

is the control unit type specified in an IOCP input data set

yyyy-yy

is the control unit type and model to be used in the IODF.

For example parameters, see the sample profile in Figure 12.

Extended migration

MIGRATE_EXTENDED

YES/NO. Specify YES to exploit the extended migration possibilities as described in Changing I/O configurations by editing data sets.

If you specify NO (which is the default), the additional keywords are not generated during IOCP build and when re-migrating IOCP input data sets, the migration function ignores the commented *$HCDC$ and *$HCD$ tags.

Bypass IODF information update for SNA processor

BYPASS_UPD_IODF_FOR_SNA

YES/NO. This provides a possibility of bypassing the attempt to update the IODF information for SNA processors after having successfully built the IOCDS.

If you specify YES, then no attempts will be made to update the IODF with IOCDS status information, which will usually fail as a result of the IODF being in an exclusive access mode with the dialog.

If you specify NO (which is the default), then for SNA and non-SNA processors, an attempt is made to update IOCDS information in the IODF after the IOCDS has been built successfully.

Display information during ACTIVATE

SHOW_IO_CHANGES

YES/NO. This option applies to dynamic activate. When performing both a hardware and software change, specify YES (which is the default) to get information about the channel paths, control units, and devices that are deleted, modified, or added.

Loading an IODF into a data space

IODF_DATA_SPACE

YES/NO. If you specify YES (which is the default), the IODF is loaded into a data space.

If you specify NO, the IODF is loaded into the user address space.

IODF name verification for batch jobs

BATCH_IODF_NAME_CHECK

YES/NO. If you specify YES (which is the default), HCD checks if the IODF specified for a batch job conforms to the naming convention as described in IODF naming convention. Processing of IODFs with invalid names is limited to deletion.

If you specify NO, HCD does not check the IODF names specified for batch jobs.

IODF checker automation

CHECK_IODF

YES/NO. If you specify YES, HCD checks an IODF for consistency and structural correctness whenever the IODF accessed in update mode is unallocated. This corresponds to the TRACE ID=IODF command and will consume processing time depending on the size of the IODF.

If you specify NO (which is the default), HCD does not check the IODF automatically..

Delay device regrouping

DELAYED_GROUPING

YES/NO. If you specify YES, HCD performs any necessary device regrouping after a device group split only when the IODF is closed. This gives a better response time in the HCD dialog for large IODFs.

If you specify NO (which is the default), HCD performs a necessary device regrouping each time when users exit the I/O Device List, or, in case the I/O Device List was called from either the Operating System Configuration List or the Channel Subsystem List, when leaving these lists.

Default settings for OS parameters

OS_PARM_DEFAULT

This keyword overrides a parameter default value set by the UIM. The value is used as a default on the HCD Define Device Parameters/Features panel. The syntax is:

OS_PARM_DEFAULT = xxxxxx,yyyyyy

where:

xxxxxx is the parameter keyword
yyyyyy is the new parameter default value

Example: The LOCANY default value is NO. You can change it to YES by specifying the HCD profile option:

OS_PARM_DEFAULT = LOCANY,YES

Note:

Default values cannot be set differently for different device types. Features, for example SHARED, cannot be defaulted using this keyword.

Extension of the attachable device list of a control unit

CU_ATTACHABLE_DEVICE

This keyword allows the attachable device list of a control unit to be extended to include additional device types. Both the control unit type and the device type must be defined via UIMs. The value syntax is:

xxxxxx,yyyyyy

where:

xxxxxx is the control unit type
yyyyyy is the additional device type

Note that more than one device type can be added to the same control unit type.

Example:
  CU_ATTACHABLE_DEVICE = RS6K,3174
  CU_ATTACHABLE_DEVICE = RS6K,3274

A change of the value settings for this keyword will not be active until the next start of HCD.

Show partition defaults in IOCP statements

SHOW_IOCP_DEFAULTS

YES/NO. Use this option to write comment lines into the generated IOCP deck which show the partition assignments in effect for those CHPID and IODEVICE statements which make use of the IOCP defaults for the PARTITION and NOTPART values.

Setting this option to YES causes the suppressed PARTITION / NOTPART keywords to be generated as comments prefaced by the tag *$DFLT$*.

The default is NO.

Export/import additional configuration objects

SHOW_CONFIG_ALL

YES/NO. Use this option to write additional configuration objects during export of switch configuration statements.

Setting this option to YES affects the Build I/O configuration data dialog and batch utility to write configuration statements for unconnected control units and devices in addition to those for switches, if the Configuration/Switch ID is specified as *.

The default is NO.

Unconditional generation of D/R site OS configurations

UNCOND_GENERATE_DROS

YES/NO. If you change a generated D/R site OS configuration before building a new production IODF, it loses the generated attribute and therefore is not regenerated when the production IODF is built (see also D/R site OS configurations). Instead, you must manually delete the D/R site OS configuration and rebuild the production IODF to get the configuration regenerated automatically.

Setting the UNCOND_GENERATE_DROS option to YES affects that HCD regenerates D/R site OS configurations whenever a new production IODF is built, independent from whether the configurations have been previously modified or not. This helps to avoid manual user interventions in cases where changes on the primary configuration are not automatically applied to the D/R site OS configuration.

The default is NO.

HMC-wide activation

CONNECTION_TABLE

Use this profile option to specify the name of a data set that contains the connection table for establishing connectivity to HCD on the remote systems via TCP/IP.

RCALL_LOG

YES/NO. Use this profile option to activate logging of remote calls into a data set.

Setting this option to YES allocates a new data set named HLQ.CBDQCLNT.LOG, if it does not yet exist. Otherwise an existing data set is used. The default is NO.

RCALL_TIMEOUT

Use this profile option to set the timeout value for the initial connection to a remote system.

Specify the timeout value in seconds using a decimal number. Specifing zero causes HCD to use the default. The default is 60.

Example

The following figure shows a profile with sample data:

/* ****************************************************************** */
/*                                                                    */
/* HCD Profile                                                        */
/* Created :  2012-11-27  16:09:15  by user : DOCU                    */
/*                                                                    */
/* ****************************************************************** */
/* ****************************************************************** */
/*                                                                    */
/*    HCD Profile Section for Standard Profile Options                */
/*                                                                    */
/* ****************************************************************** */
ACTLOG_VOL = *                    /* ACTlog on same volume as IODF    */
ALLOC_SPACE = HCDASMP,60
BATCH_IODF_NAME_CHECK = NO        /* changed to non-default NO        */
BYPASS_UPD_IODF_FOR_SNA = YES     /* No IODF update with IOCDS data   */
CHANGE_LOG = YES                  /* CHANGE LOG REQ. ACTIVITY LOG = O */
CHLOG_VOL = *
COLOR_NORM = BLACK                /* default was GREEN                */
COLOR_TEXT = BLUE                 /* default was GREEN                */
CONNECTION_TABLE = DOCU.HCD.CONN(TABLE) /* HMC wide activate          */
CU_ATTACHABLE_DEVICE = RS6K,3274  /* extend attachable device list    */
ESOTERIC_TOKEN = YES              /* Esoteric token: ascending order  */
GCR_FONT = X0GT20
HCDDECK_VOL = D83WL2              /* Vol for configuration data set   */
HCDJES3_VOL = D83WL4              /* Vol for JES3 output data set     */
LINES_PER_REPORT_PAGE = 60        /* Max. number of lines per page    */
MAP_CUTYPE = 3705,3745            /* Replace CU type during migration */
MAP_CUTYPE = 3880,3880-23         /* Replace CU type during migration */
MIGRATE_EXTENDED = YES            /* Enable migration enhancements    */
MIXED_ESOTERIC = YES              /* Allow mixed dev. w same esoteric */
OS_PARM_DEFAULT = LOCANY,YES      /* Default for parameter LOCANY     */
RCALL_TIMEOUT = 10                /* Default is 60                    */
SHOW_CONFIG_ALL = YES             /* write additional config objects  */
SHOW_IOCP_DEFAULTS = YES          /* show IOCP default for partitions */
TSO_NOPREFIX = YES                /* Enable TSO Noprefix (Default NO) */
UNCOND_GENERATE_DROS = YES        /* regenerate D/R site OS config    */
******************************** Bottom of Data ************************