| (required) The <OPTIONS> element contains the DBCPARMS values. Data type: Not applicable.Parent element: <DBCPARMS>Child elements: <SSID>, <GROUP>, <WTOUPPERCASE>, <XCFGROUP>, <MODE>, <WLM>, and <DPRREPOS> | (optional) The <SSID> element specifies the SSID of the DBC subsystem. The SSID is a required DBC startup parameter. You must specify the SSID either through the DBCPARMS XML document or in the EXEC statement; otherwise, initialization fails. Consider the following requirements for the value of the <SSID> element: - BMC recommends that you use different names for the DBC SSID and the DBC started task.
- The SSID value must not conflict with any MVS command verbs. If it does, DBC issues an error message and terminates.
- The SSID value can contain A–Z, 0–9, #, or $. Any other characters are invalid and cause the DBC subsystem to issue an error message and terminate.
- The SSID value should not begin with a numeric character (0–9). You can use the SSID to issue system commands to the DBC subsystem; consequently, if the SSID value started with a number, the system could misinterpret the value as the short form of the REPLY system command. (For more information about issuing system commands, see DBC-commands.)
- The SSID value should not conflict with any JES commands. This recommendation ensures that only the DBC subsystem processes system commands that you are issue to the DBC subsystem by using the DBC SSID value.
Data type: VARCHAR(4)Parent element: <OPTIONS>Child elements: None. |
|---|
| (optional) The <GROUP> element specifies the name of the DBC XCF group that relates DBC subsystems on different LPARs within the SYSPLEX. Note You can also specify the DBC XCF group through the EXEC PGM=DBCMAIN,PARM='parms' JCL statement. Consider the following requirements for the value of the <GROUP> element: - The GROUP value must not conflict with any MVS command verbs. If it does, DBC issues an error message and terminates.
- The GROUP value must not contain embedded blank characters.
- The GROUP value should not begin with a numeric character (0–9). You can use the group name to issue system commands to the DBC subsystem; consequently, if the group name started with a number, the system could misinterpret the value as the short form of the REPLY system command. (For more information about issuing system commands, see DBC-commands.)
- The GROUP value should not conflict with any JES commands. This recommendation ensures that only the DBC subsystem processes system commands that you issue to the DBC subsystem by using the GROUP value.
Note A DBC XCF group can contain only one DBC subsystem per LPAR. The default value is DBCGROUP. Data type: VARCHAR(8)Parent element: <OPTIONS>Child elements: None. |
|---|
| (optional) By default, DBC uses the <GROUP> element as the name of an XCF group to join at startup. In rare situations, this behavior might not be acceptable. Use the <XCFGROUP> element to specify a different XCF group for DBC to join. Data type: VARCHAR(8)Parent element: <OPTIONS>Child elements: None. |
|---|
| MODE controls whether to initialize products stored in the repository when starting. Valid values for the <MODE> element are SAFE and NORMAL. - SAFE mode tells the DBC subsystem to start without automatically initializing products stored in the repository.
- NORMAL mode (the default value) initializes products stored in the repository.
You can also specify the value for MODE through start arguments to DBCMAIN. If DBC starts in SAFE mode, DBC issues the following message to the system log: BMCDBC0250 ssid DBC has been requested to ignore INITPROD commands from the repository If starting in default NORMAL mode, DBC issues the following message: BMCDBC0234I DBC operating in NORMAL mode. Data type: VARCHAR(6)Parent element: <OPTIONS>Child elements: None. |
|---|
| The <WLM> element sets the subsystem type to use for workload management. The default is BMCS. Data type: Not applicable.Parent element: <OPTIONS>Child elements: <SUBSYSTYPE> | The <SUBSYSTYPE> element contains the name of the subsystem type. Data type: VARCHAR(8)Parent element: <OPTIONS>Child elements: <SUBSYSTYPE> |
|---|
|
|---|
| (optional) The <WTOUPPERCASE> element indicates whether to convert console messages to uppercase. Printed messages remain in mixed case. The default value is YES. Valid values are YES and NO. Data type: VARCHAR(3)Parent element: <OPTIONS>Child elements: None. |
|---|
(PTF BQU0315 applied)
REQUIREREPOS | (optional) The <REQUIREREPOS> element determines DBC behavior when the repository is unavailable. <REQUIREREPOS>YES</REQUIREREPOS> indicates that DBC should terminate if the repository is not available. <REQUIREREPOS>NO</REQUIREREPOS> indicates that DBC should only issue a warning message in this case. The default is <REQUIREREPOS>YES</REQUIREREPOS>. Data type: VARCHAR(3)Parent element: <OPTIONS>Child elements: None. |
|---|
| (optional) The <DPRREPOS> element contains the DBC repository name. If you do not specify this element, DBC repository services are not available. Unless you also specified <REQUIREREPOS>NO</REQUIREREPOS>, DBC terminates. If you did specify <REQUIREREPOS>NO</REQUIREREPOS>, DBC issues a warning message during initialization and DBC subsystem services that do not require a repository, function normally. Data type: Not applicable.Parent element: <OPTIONS>Child elements: <NAME>, <STORCLAS>, <VOLUMES>, <MGMTCLAS>, <DATACLAS>, and <IGNORE> | (optional) The <NAME> element specifies the data set name for the DBC repository VSAM cluster. This value must specify a valid data set name: - If the value specifies the name of an existing DBC repository VSAM cluster, DBC uses that cluster for the repository.
- If the specified data set does not exist, DBC defines the new cluster automatically by using the <STORCLAS> or <VOLUMES> options to determine physical allocation attributes.
Only one active DBC subsystem can use a given DBC repository VSAM cluster. You can share a single DBCPARMS parameters file for multiple DBC instances. To do so, specify DBC system variables in the <NAME> element to ensure that each DBC subsystem uses a unique repository data set name. DBC resolves the variables to their symbolic values. To enable variable substitution, prefix the system variables with an ampersand (&) and suffix them with a period (.). Example Assume that you use the system variables in a <NAME> element as shown in the following statement: <NAME>BMC.&SSID..&SMFID..&MVSNAME..REPOS</NAME> Also, assume that the symbolic values of SSID, SMFID, and MVSNAME are DBC1, SYSP, and MVSPROD, respectively. The variable substitution resolves to the following data set name: BMC.DBC1.SYSP.MVSPROD.REPOS Data type: VARCHAR(44)Parent element: <DPRREPOS>Child elements: None. |
|---|
| (optional) The <STORCLAS> element specifies the SMS storage class to be used for the DBC repository VSAM cluster when the DBC defines the cluster. The DBC defines the cluster automatically if the <NAME> element specifies the name of a cluster that has not yet been defined. Specify this element only if SMS is active and the cluster is to be SMS-managed. For more information, see the STORAGECLASS parameter of the DEFINE CLUSTER command in the IBM DFSMS Access Method Services documentation. Data type: VARCHAR(8)Parent element: <DPRREPOS>Child elements: None. |
|---|
| (optional) The <VOLUMES> element specifies the volumes on which the DBC repository VSAM cluster is to be defined when the DBC defines the cluster. The DBC defines the cluster automatically if the <NAME> element specifies the name of a cluster that has not yet been defined. Note This element is required only if you do not specify if a value for <STORCLAS>. The <VOLUMES> value can specify up to 59 volumes, where each volume is delimited by a comma (,). The value can specify a volume serial number or, if the cluster is to be SMS-managed, an asterisk (*), which lets SMS choose the volume. For more information, see the VOLUMES parameter of the DEFINE CLUSTER command in the IBM DFSMS Access Method Services documentation. Data type: VARCHAR(412)Parent element: <DPRREPOS>Child elements: None. |
|---|
| (optional)The <MGMTCLAS> element specifies the management class for the repository data set to be created. The <MGMTCLAS> element is used only if the repository data set does not yet exist. Data type: VARCHAR(8)Parent element: <DPRREPOS>Child elements: None. |
|---|
| (optional) The <DATACLAS> element specifies the data class for the repository data set to be created. The <DATACLAS> element is used only if the repository data set does not yet exist. Data type: VARCHAR(8)Parent element: <DPRREPOS>Child elements: None. |
|---|
| (optional) The <IGNORE> element tells DBC to ignore the repository entries for the identified product at startup. Doing so allows the rest of the products running within the DBC subsystem to start normally without starting the specified product. You can include multiple <IGNORE> elements. when DBC is started Data type: Not applicable.Parent element: <DPRREPOS>Child elements: <PRODUCT>, <FMID>, and <PIID> | (required) The <PRODUCT> element identifies a unique BMC product code. Data type: CHAR(3)Parent element: <IGNORE>Child elements: None. |
|---|
| (required) The <FMID> element identifies the FMID of the product code release. Data type: CHAR(7)Parent element: <IGNORE>Child elements: None. |
|---|
| (optional) The <PIID> element is optional and identifies a unique product instance within the context of one product code and FMID. Data type: VARCHAR(16)Parent element: <IGNORE>Child elements: None. |
|---|
|
|---|
|
|---|
|
|---|