Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Parameters

This section describes the parameters that the XBM procedure accepts.

CONFIG

The first time that you start XBM, you do not have a configuration file to specify. Consequently, XBM activates the DEFAULT_CONFIG configuration. During subsequent restarts, if you do not specify a CONFIG parameter, XBM activates the last active configuration.

MS

The first time that you start XBM, you do not have a management set (MS) to specify. Because management sets do not have default values, a management set does not activate automatically. During subsequent restarts, XBM activates a management set only if you specify it or add the ACTIVATE commands to your XBMXINIT data set.

XBMGROUP

This parameter specifies the name of the cross-system coupling facility (XCF) group that you want this XBM subsystem to join when the PSS component is started, if applicable. This name must match the first level of the structure name for the XBM structures defined in your coupling facility resource manager (CFRM) policy. The first time that you start XBM, the default for this parameter is XBMGROUP.

If you specify an XCF group name by using this parameter, you must perform the following tasks before the XBM subsystem can join the group:

  1. Set the Join sysplex group when PSS started option to Yes on the PSS Options subpanel.
  2. Start the PSS component.

Note

The XBMGROUP parameter overrides any XCF group name that you enter in the Sysplex group name field on the PSS Options subpanel. If you enter an XCF group name on the MVS command to start the XBM started task, that group name overrides the XBMGROUP parameter and the group name on the PSS Options subpanel.

SYS

The XBM subsystem name (identified as XBMID by DB2 utilities, or XBMSSID by IMS utilities) is the first four characters of the started-task procedure, or it is the name specified with the SYS parameter (a maximum of four characters). The SYS parameter takes higher precedence.

This subsystem name must:

  • Start with a letter
  • Be two to four characters in length
  • Contain only the letters A-Z, the numbers 0-9, $, or #

Note

Note the following considerations when setting up your system name:

  • If you specify an invalid value in the SYS parameter, XBM starts the subsystem by using the first four characters of the name of the started task or job as the XBM subsystem name. For example, if your site has naming conventions that require you to name the started task DB2AXBM (where DB2A is a valid DB2 subsystem name), the SYS parameter lets you name your XBM subsystem so that it does not conflict with the DB2 subsystem name, another XBM subsystem name, or an MVS command.
  • You can use a single PROC for multiple subsystems if you want to use XBM in a data sharing environment and you use the &SYSCLONE symbolic from MVS system symbols. For more information, see Defining-PROCs-for-use-with-multiple-XBM-subsystems.
  • You can use the same XBM SSID on multiple XBM subsystems in a non-datasharing environment.

XBM uses systems-wide enqueues in order to add an extra layer of protection for the XBM repository and to provide data sharing capability. If you do not intend to use XBM in a data sharing environment with shared repositories, you can use the same XBM ID on each LPAR/JES SSID. To do so, you must update the GRSRNLxx member in SYS1.PARMLIB and correctly modify the SYSTEMS EXCLUSION LIST.

Any resource named in this list is treated as a local resource when an ENQ, DEQ, or RESERVE macro is issued for the resource and is specified with a scope of SYSTEMS.

If you are not running with shared repositories, you must ensure that each repository has unique names to avoid ENQ conflicts.

You can use the &SYSNAME parameter (D SYMBOLS) to differentiate the repository from a single PROC. For example, after you use IDCAMS to define the data sets for your XBM started tasks, use the following example in the PROC to allocate the different repository on each LPAR.

//XBMREP01 DD DISP=SHR,DSN=HLQ.XBM.&SYSNAME..XBMREP01

Example

Assume that you have an XBM SSID of XBMP. You would update the SYSTEMS EXCLUSION LIST in SYS1.PARMLIB(GRSRNLxx) with the QNAME of BMCXBM, the RNAME value of XBMP, and the TYPE value of SPECIFIC, as follows:

RNLDEF RNL(EXCL) TYPE(SPECIFIC)
  QNAME(BMCXBM)
  RNAME(XBMP)

You can use TYPE(SPECIFIC) only for a 4-byte XBM SSID.

If you have a 3-byte SSID name (for example, XBM), use a generic resource name entry to match a portion of a resource name. A match occurs whenever the specified portion of the generic resource name entry matches the beginning of the same portion of an input search argument.

RNLDEF RNL(EXCL) TYPE(GENERIC)
  QNAME(BMCXBM)
  RNAME(XBM)

You can dynamically activate the updated RNL by using the SET GRSRNL=xx IBM z/OS operator command. You must restart any active XBM subsystems to pick up the change.

To show all resources for the BMCXBM major QNAME, issue the following DISPLAY command:

D GRS,RES=(BMCXBM,*)
Warning

The SYS parameter on the started task JCL (or on the XBM START command) names the XBM subsystem only. Do not use any MVS subsystem name, DB2 subsystem name, or MVS subsystem command for the SYS parameter.

XDB2, XIMS, XVSAM, XSSI, XPSS, XZIIP

These parameters specify whether the indicated component will start when the XBM subsystem starts.

By default, all components with a valid password start when you start the XBM subsystem the first time. Upon subsequent starts of the XBM subsystem, XBM components will try to resume the state that they were in when the XBM subsystem stopped. Authorized components that were running will restart, but components that were stopped or disabled will not start. If you do not want a component to start, specify N or NO for the corresponding parameter value.

For example, if you do not want the SSI component to start, enter XSSI='NO' as a parameter for the PROC. If you want to restart the component later, you can use the XBM ISPF interface or the START console command.

Note

If you are using SUF and are not planning to use hardware snapshots or Instant Snapshots, BMC recommends that you specify not to start the SSI component. Doing so bypasses the device discovery phase and reduces startup times.

Related topic

Starting-the-XBM-subsystem


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*