CDM Mapping for MFPart
This topic provides information about CDM mapping for MFPart nodes. The CIs created are described in this topic.
Data models
CMDB version differences
The default mapping works with CMDB versions 7.5, 7.6, and 7.6.03 and later. The data model in each is slightly different.
BMC_Impact
relationships are not normally created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself. See the information about impact relationships for more details.
BMC_ComputerSystem
The MFPart node is used to model a logical server within the mainframe. The root MFPart node is mapped to a root BMC_ComputerSystem CI with the following attributes:
Attribute | Details |
---|---|
TokenId | MFPart |
Name | MFPart |
NameFormat | " |
ShortDescription | MFPart |
Description | MFPart |
CapabilityList | Server |
ComponentAliases | Component alias from mainframe discovery |
isVirtual |
|
LastScanDate | MFPart |
ManufacturerName | MFPart |
MFIntegrationID | MFPart |
Model | MFPart |
PrimaryCapability | Server |
VirtualSystemType | LPAR or VM/VM Guest |
Category | " |
Type | " |
Item | " |
BMC_OperatingSystem
The root MFPart
is also mapped to a single BMC_OperatingSystem
CI, with the following attributes:
Attribute | Details |
---|---|
Name | MFPart |
NameFormat | " |
ShortDescription | OS type followed by OS serial number |
Description | " |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | MFPart |
MFIntegrationID | MFPart |
Model | MFPart os_type — "z/OS" or "z/VM OS" |
OSType | z/OS or z/VM |
SerialNumber | MFPart |
VersionNumber | MFPart |
Category | " |
Type | " |
Item | " |
Operating system relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_Mainframe
An MFPart corresponding to a Native LPAR is directly connected to a Mainframe node. The Mainframe is mapped to a BMC_Mainframe
CI as follows:
Attribute | Details |
---|---|
Name | Mainframe |
Description | Mainframe |
ShortDescription | Mainframe |
AvailableCPs | Mainframe |
CapabilityList | Mainframe |
ComponentAliases | Component alias from mainframe discovery |
InstalledCPUs | Mainframe |
ManufacturerName | Mainframe |
MFIntegrationID | Mainframe |
Model | Mainframe |
PrimaryCapability | Mainframe |
Category |
|
Type |
|
Item |
|
Mainframe relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_VirtualSystemEnabler
For Native LPARs, the MFPart and Mainframe nodes are mapped to a BMC_VirtualSystemEnabler
CI as follows:
Attribute | Details |
---|---|
Name | Mainframe |
ShortDescription | MFPart |
ComponentAliases | Component alias from mainframe discovery |
Description | MFPart |
EnablerType | MFPart |
InstanceName |
where Introduced in the November 2019 TKU to support integrations. |
ManufacturerName | MFPart |
MFIntegrationID | Mainframe |
Model | MFPart |
Category | " |
Type | " |
Item | " |
For zVM LPARs, the Discovery model represents the virtualization as a Software Instance node connected to the containing Native LPAR. That Software Instance is mapped to a BMC_VirtualSystemEnabler
as follows:
Attribute | Details |
---|---|
Name | Software Instance |
NameFormat | " |
ShortDescription | Software Instance |
Description | " |
BuildNumber | Software Instance |
ComponentAliases | Component alias from mainframe discovery |
EnablerType | Software Instance |
MFIntegrationID | MFPart |
Model | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
VersionNumber | Software Instance |
Category | " |
Type | " |
Item | " |
BMC_VirtualSystemEnabler relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_Sysplex / BMC_Cluster
The root MFPart is related to a Cluster node to represent its sysplex. This is mapped to BMC_Sysplex
in CMDB versions prior to 7.6.03, and to BMC_Cluster
in version 7.6.03. In either case, the attributes are populated as follows:
Attribute | Details |
---|---|
Name | Cluster |
NameFormat | " |
ShortDescription | Cluster |
Description | Cluster |
ComponentAliases | Component alias from mainframe discovery |
MFIntegrationID | MFPart |
Model | " |
Types | " |
Category | " |
Type | " |
Item | " |
BMC_Sysplex / BMC_Cluster relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_MFCouplingFacility
The MFPart and Cluster are both related to a number of Coupling Facility nodes. Each one is mapped to a BMC_MFCouplingFacility
CI as follows:
Attribute | Details |
---|---|
Name | Coupling Facility |
NameFormat | " |
Description | Coupling Facility |
ShortDescription | Coupling Facility |
CFRMName | Coupling Facility |
ComponentAliases | Component alias from mainframe discovery |
MFIntegrationID | MFPart |
Model | " |
NodeDescriptor | Coupling Facility |
Storage | Coupling Facility |
Category |
|
Type |
|
Item |
|
BMC_MFCouplingFacility relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_StorageSubsystem
The root MFPart can be related to a number of StorageCollection nodes. Each node is mapped to a BMC_StorageSubsystem
CI as follows:
Name | StorageCollection |
NameFormat | " |
ShortDescription | StorageCollection |
Description | StorageCollection |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | StorageCollection |
MFIntegrationID | MFPart |
Model | StorageCollection |
PrimaryCapability | StorageSubsystem |
Category | " |
Type | " |
Item | " |
BMC_StorageSubsystem relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
BMC_DiskDrive / BMC_TapeDrive
Both the root MFPart and the StorageCollection nodes are related to Storage nodes, representing disk and tape drives. Disk drives are mapped to BMC_DiskDrive
CIs as follows:
Name | Storage |
NameFormat | " |
ShortDescription | Storage |
Description | Storage |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | Storage |
MediaType | 1 (fixed hard disk) |
MFIntegrationID | MFPart |
Model | Storage |
PNPDeviceID | Storage |
SerialNumber | Storage |
Category | " |
Type | " |
Item | " |
Tape drives are mapped to BMC_TapeDrive
CIs as follows:
Name | Storage |
NameFormat | " |
ShortDescription | Storage |
Description | Storage |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | Storage |
MediaType | 0 (removable media) |
MFIntegrationID | MFPart |
Model | Storage |
PNPDeviceID | Storage |
Category | " |
Type | " |
Item | " |
BMC_DiskDrive / BMC_TapeDrive relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BMC_MFSoftwareServer / BMC_SoftwareServer
Each Software Instance related to the root MFPart is mapped to a corresponding CI. In CMDB versions prior to 7.6.03, the CI has the extension class BMC_MFSoftwareServer
; in CMDB version 7.6.03, the CI has the base BMC_SoftwareServer
class. In both cases, the attributes are as follows:
Attribute | Details |
---|---|
Name | Software Instance |
NameFormat | " |
ShortDescription | Software Instance |
Description | Software Instance |
BuildNumber | Software Instance |
InstanceName |
where Introduced in the November 2019 TKU to support integrations. |
ComponentAliases | Component alias from mainframe discovery |
JobName | Software Instance |
ManufacturerName | Publisher specified in the maintaining Pattern or on the Software Instance — from TKU 2014-Apr-1 onwards |
MFJobName | Software Instance |
MFIntegrationID | MFPart |
Model | Software Instance |
Model | Software Instance |
OtherSoftwareServerType | Software Instance |
PatchNumber | Software Instance |
ServicePack | Software Instance |
ServerID | Software Instance |
MFServerID | Software Instance |
VersionNumber | Software Instance |
Category | " |
Type | " |
Item | " |
BMC_MFSoftwareServer / BMC_SoftwareServer relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
BMC_ApplicationService
SoftwareComponent
is mapped to BMC_ApplicationService
.
Attribute | Details |
---|---|
Name | Software Component |
ShortDescription | Software Component |
Description | Software Component |
Model | Software Component |
VersionNumber | Software Component |
ApplicationServiceType | Enumeration value representing the service type |
Category | " |
Type | " |
Item | " |
Application service relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
| CLUSTERSERVICES (for clustered components) |
| BMC_ApplicationService Impacted |
BMC_Application
BusinessApplicationInstance
is mapped to BMC_Application
. Contained SoftwareInstance
and BusinessApplicationInstance
nodes are mapped to corresponding BMC_Component
relationships.
Name | Business Application Instance |
ShortDescription | Business Application Instance |
Description | Business Application Instance |
MarketVersion | Business Application Instance |
Model | Business Application Instance |
VersionNumber | Business Application Instance |
Category | " |
Type | " |
Item | " |
Application relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
Impacted |
|
|
|
Impacted |
|
BMC_DataBase
DatabaseDetail
nodes representing logical databases are mapped to BMC_DataBase
:
Attribute | Details |
---|---|
Name | DatabaseDetail |
NameFormat | " |
ShortDescription | DatabaseDetail |
Description | DatabaseDetail |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | " |
MFIntegrationID | MFPart |
Model | DatabaseDetail |
SerialNumber | DatabaseDetail |
Category | " |
Type | " |
Item | " |
BMC_DataBase relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
Impacted |
BMC_SystemResource
Resources such as table spaces inside databases are represented as DatabaseDetail nodes. These are mapped to BMC_SystemResource
CIs:
Attribute | Details |
---|---|
Name | DatabaseDetail |
NameFormat | " |
ShortDescription | DatabaseDetail |
Description | DatabaseDetail |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | " |
MFIntegrationID | MFPart |
Model | DatabaseDetail |
SerialNumber | DatabaseDetail |
Category | " |
Type | DatabaseDetail |
Item | " |
MQ resources are represented as Detail nodes related to MQ Software Instance nodes. These are also mapped to BMC_SystemResource
CIs:
Attribute | Details |
---|---|
Name | Detail |
NameFormat | " |
ShortDescription | Detail |
Description | Detail |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | " |
MFIntegrationID | MFPart |
Model | Detail |
SerialNumber | Detail |
Category | " |
Type | Detail |
Item | " |
BMC_SystemResource relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
(Database detail) |
|
|
|
Impacted (MQ resources) |
|
|
|
Impacted |
|
|
|
Impacted |
|
|
|
Impacted |
BMC_Transaction
Transactions within IMSTM and CICS are represented as Detail nodes related to Software Instance nodes. These are mapped to BMC_Transaction
:
Attribute | Details |
---|---|
Name | Detail |
NameFormat | " |
ShortDescription | Detail |
Description | Detail |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | " |
MFIntegrationID | MFPart |
Model | Detail |
SerialNumber | Detail |
Category | " |
Type | " |
Item | " |
Details nodes not created by default
Details nodes are not created by default.To enable their creation, you must enable the transaction discovery method described in Enabling the remaining mainframe discovery methods.
BMC_Transaction relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
Impacted |
BMC_Activity
Programs within Transactions are represented as further Detail nodes contained inside the Transaction Detail nodes. These are mapped to BMC_Activity
:
Attribute | Details |
---|---|
Name | Detail |
NameFormat | " |
ShortDescription | Detail |
Description | Detail |
ComponentAliases | Component alias from mainframe discovery |
ManufacturerName | " |
Model | Detail |
SerialNumber | Detail |
Category | " |
Type | " |
Item | " |
BMC_Activity relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
Impacted |
BMC_ConcreteCollection
FunctionalComponent
nodes representing CAM Functional Components are mapped to BMC_ConcreteCollection
.
Attribute | Details |
---|---|
Name | Functional Component |
ShortDescription | Functional Component |
Description | Functional Component |
Model | Functional Component |
Company | MFPart |
Category | " |
Type | " |
Item | " |
Functional Component relationships
Relationship | Name | Source | Destination |
---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| BMC_Cluster |
|
|
|
|
|
|
|
|
|
|
|
|
The relationship between BMC_Application
and BMC_ConcreteCollection
is used for Functional Components reached from any of the following node kinds:
- SoftwareInstance (first or second order)
- SoftwareComponent
- SoftwareCluster
- DatabaseDetail
- BAI
Comments
Log in or register to comment.