BMC Software Primary Subsystem parameters


The following table includes descriptions of each of the parameters that can be used to control the BMC Software Primary Subsystem (BMCP).

These parameters are provided either through execution parameters or through an operator response. If the subsystem is being restarted, the previous value for SUBSYSID, SVCNO, and SMFRECID is unconditionally used. An IPL is required to change these values. Only one primary subsystem can be active on an MVS system at any time. All consolidated subsystems use the services of the BMCP.

BMC Software Primary Subsystem parameters

Parameter

Description

REFRESH(default value)

During subsystem startup, modules that are currently loaded into common storage are checked for upgrades. If a different version of the module is found in the normal system search, the module is reloaded into common storage. This option can be used to load new versions of common storage modules without the need for an IPL.

Note

Some common storage modules cannot be upgraded by using the REFRESH parameter; in these cases, Customer Support will issue a statement stating that the upgrade requires an IPL.

DEBUG

The subsystem writes diagnostic trace information to the system logs.

Note

Use of this parameter can cause extremely heavy console traffic, so use it with caution.

NODEBUG (default value)

No diagnostic messages are issued. Only normal processing and error messages are issued.

This mode is the normal operation mode of the BMC Software Subsystems.

PROMPT

The operator is prompted to correct errors or provide required parameters if they are omitted from the parameter lists.

CAPS (default value)

Console messages are issued in all uppercase letters.

This mode satisfies the CUA language support for console operations as defined by IBM.

MIXED

Console messages are issued in mixed case. This case makes messages easier to read; however, international language sites might not be able to view the entire message because of DBCS constraints.

SMFRECID (0)

For BMC products that request the BMCP to create a BMC common SMF record, this number is the SMF record ID that is used in the SMF records.

This number must be

  • a valid user SMF value as defined by IBM
  • a decimal number between 200 and 255
  • not in use by any other products

SUBSYSID (BMCP)

The primary subsystem uses this subsystem name during its startup and operation.

  • The name must be a unique subsystem name on the MVS image.
  • The name cannot exceed four characters in length.
  • The first character must be alphabetic.

Example

SUBSYSID=BMCP sets the subsystem name to BMCP.

SVCNO

The primary subsystem uses this SVC number to service MVS services intercepts.

Change this value only when instructed to by Customer Support.

 

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