MFPart nodes in the Discovery model are mapped to the Common Data Model as shown in this automatically-generated diagram:
The CIs created are described below.
 | 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 created with CMDB 7.6.03 and later, since the CMDB automatically maintains them itself.
- With the "CMDB 7.6.03 and later with impact relationships" data model, BMC_Impact relationships are created with Name ImpactOnly rather than IMPACT.
- CMDB versions prior to 7.6.03 require a Mainframe extension that adds a number of mainframe-specific classes. In 7.6.03, some of these have been brought into the core model, and others have been replaced by generic core classes, as noted below.
|
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 key attribute |
| Name |
MFPart key attribute |
| NameFormat |
"Mainframe" |
| ShortDescription |
MFPart name attribute |
| Description |
MFPart description attribute |
| CapabilityList |
Server |
| ComponentAliases |
Component alias from mainframe discovery |
| isVirtual |
Yes |
| LastScanDate |
MFPart last_update_success – the date and time the host was last scanned |
| ManufacturerName |
MFPart vendor – the manufacturer of the mainframe |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
MFPart model |
| PrimaryCapability |
Server |
| VirtualSystemType |
LPAR or VM/VM Guest |
| Category |
"Hardware" |
| Type |
"Processing unit" |
| Item |
"Server" |
BMC_OperatingSystem
The root MFPart is also mapped to a single BMC_OperatingSystem CI, with the following attributes:
| Attribute |
Details |
| Name |
MFPart __mfpart_id |
| NameFormat |
"Mainframe" |
| ShortDescription |
OS type followed by OS serial number |
| Description |
"OS-__mfpart_id |
| ComponentAliases |
Component alias from mainframe discovery |
| ManufacturerName |
MFPart vendor |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
MFPart os_type – "z/OS" or "z/VM" |
| OSType |
z/OS or z/VM OS |
| SerialNumber |
MFPart os_serial |
| VersionNumber |
MFPart os_version |
| Category |
"Software" |
| Type |
"Operating System Software" |
| Item |
"Standard OS" |
Operating system relationships
| Relationship |
Name |
Source |
Destination |
| BMC_HostedSystemComponents |
SYSTEMOS |
BMC_ComputerSystem |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_OperatingSystem |
BMC_ComputerSystem |
BMC_MFSoftwareServer / BMC_SoftwareServer
Each SoftwareInstance 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 |
SoftwareInstance key |
| NameFormat |
"Mainframe" |
| ShortDescription |
SoftwareInstance name |
| Description |
SoftwareInstance key |
| BuildNumber |
SoftwareInstance build |
| ComponentAliases |
Component alias from mainframe discovery |
| JobName |
SoftwareInstance job_id CMDB versions prior to 7.6.03 |
| MFJobName |
SoftwareInstance job_id CMDB versions 7.6.03 and later |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
SoftwareInstance short_type CMDB versions prior to 7.6.03 |
| Model |
SoftwareInstance type CMDB versions 7.6.03 and later |
| OtherSoftwareServerType |
SoftwareInstance type |
| PatchNumber |
SoftwareInstance patch |
| ServicePack |
SoftwareInstance service_pack |
| ServerID |
SoftwareInstance server_id CMDB versions prior to 7.6.03 |
| MFServerID |
SoftwareInstance server_id CMDB versions 7.6.03 and later |
| VersionNumber |
SoftwareInstance version |
| Category |
"Software" |
| Type |
"Application" |
| Item |
"BMC Discovered" |
BMC_MFSofwareServer / BMC_SoftwareServer relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
APPLICATIONSYSTEMCOMPUTER |
BMC_ComputerSystem |
BMC_MFSoftwareServer |
| BMC_Component |
APPLICATIONSYSTEMHIERARCHY |
BMC_MFSoftwareServer (containing) |
BMC_MFSoftwareServer (contained) |
| BMC_Impact |
IMPACT |
BMC_ComputerSystem |
BMC_MFSoftwareServer |
| BMC_Impact |
IMPACT |
BMC_MFSoftwareServer |
BMC_MFSoftwareServer |
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 key |
| Description |
Mainframe description |
| ShortDescription |
Mainframe name |
| CapabilityList |
Mainframe |
| ComponentAliases |
Component alias from mainframe discovery |
| InstalledCPUs |
Mainframe num_processors |
| ManufacturerName |
Mainframe vendor |
| MFIntegrationID |
Mainframe mf_integration_id – MainView identifier used for launch in context |
| Model |
Mainframe model |
| PrimaryCapability |
Mainframe |
| Category |
Hardware |
| Type |
Processing unit |
| Item |
Mainframe |
Mainframe relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Component |
SYSTEMPARTITION |
BMC_Mainframe |
BMC_ComputerSystem |
| BMC_Impact |
IMPACT |
BMC_Mainframe |
BMC_ComputerSystem |
BMC_VirtualSystemEnabler
For Native LPARs, the MFPart and Mainframe nodes are mapped to a BMC_VirtualSystemEnabler CI as follows:
| Attribute |
Details |
| Name |
Mainframe key with suffix "-VSE" |
| ShortDescription |
MFPart part_type |
| ComponentAliases |
Component alias from mainframe discovery |
| Description |
MFPart part_type followed by Mainframe key |
| EnablerType |
MFPart __cdm_enabler_type |
| ManufacturerName |
MFPart vendor |
| MFIntegrationID |
Mainframe mf_integration_id – MainView identifier used for launch in context |
| Model |
MFPart part_type |
| Category |
"Software" |
| Type |
"Operating System Software" |
| Item |
"Virtualization OS" |
For zVM LPARs, the Discovery model represents the virtualization as a SoftwareInstance node connected to the containing Native LPAR. That SoftwareInstance is mapped to a BMC_VirtualSystemEnabler as follows:
| Attribute |
Details |
| Name |
SoftwareInstance __cdm_component_alias |
| NameFormat |
"Mainframe" |
| ShortDescription |
SoftwareInstance vm_id |
| Description |
"z/VM-" followed by SoftwareInstance __cdm_component_alias |
| BuildNumber |
SoftwareInstance build |
| ComponentAliases |
Component alias from mainframe discovery |
| EnablerType |
SoftwareInstance cdm_vm_enabler_type |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
SoftwareInstance type |
| PatchNumber |
SoftwareInstance patch |
| ServicePack |
SoftwareInstance service_pack |
| VersionNumber |
SoftwareInstance version |
| Category |
"Software" |
| Type |
"Operating System Software" |
| Item |
"Virtualization OS" |
BMC_VirtualSystemEnabler relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
VIRTUALSYSTEMOS |
BMC_VirtualSystemEnabler |
BMC_ComputerSystem (contained) |
| BMC_HostedSystemComponents |
HOSTEDSYSTEMCOMPONENTS |
BMC_Mainframe / BMC_ComputerSystem (containing) |
BMC_VirtualSystemEnabler |
| BMC_Impact |
IMPACT |
BMC_VirtualSystemEnabler |
BMC_ComputerSystem (contained) |
| BMC_Impact |
IMPACT |
BMC_Mainframe / BMC_ComputerSystem (containing) |
BMC_ComputerSystem (contained) |
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 key |
| NameFormat |
"Mainframe" |
| ShortDescription |
Cluster name |
| Description |
Cluster description |
| ComponentAliases |
Component alias from mainframe discovery |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
"Sysplex" |
| Types |
"Sysplex" |
| Category |
"Software" |
| Type |
"Cluster" |
| Item |
"Mainframe" |
BMC_Sysplex / BMC_Cluster relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Component |
CLUSTEREDSYSTEM |
BMC_Sysplex / BMC_Cluster |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_Sysplex |
BMC_OperatingSystem |
BMC_MFCouplingFacility
The MFPart and Cluster are both related to a number of CouplingFacility nodes. Each one is mapped to a BMC_MFCouplingFacility CI as follows:
| Attribute |
Details |
| Name |
CouplingFacility key |
| NameFormat |
"Mainframe" |
| Description |
CouplingFacility description |
| ShortDescription |
CouplingFacility name |
| CFRMName |
CouplingFacility cfrm_name |
| ComponentAliases |
Component alias from mainframe discovery |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
"CF" |
| NodeDescriptor |
CouplingFacility node_descriptor |
| Storage |
CouplingFacility storage |
| Category |
Hardware |
| Type |
Processing unit |
| Item |
Mainframe |
BMC_MFCouplingFacility relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
COUPLINGFACILITYOS |
BMC_MFCouplingFacility |
BMC_OperatingSystem |
| BMC_HostedSystemComponents |
SYSPLEXCOUPLINGFACILITY |
BMC_Sysplex / BMC_Cluster |
BMC_MFCouplingFacility |
| BMC_Impact |
IMPACT |
BMC_MFCouplingFacility |
BMC_OperatingSystem |
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 key |
| NameFormat |
"Mainframe" |
| ShortDescription |
StorageCollection name |
| Description |
StorageCollection key |
| ComponentAliases |
Component alias from mainframe discovery |
| ManufacturerName |
StorageCollection vendor |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
StorageCollection type |
| PrimaryCapability |
StorageSubsystem |
| Category |
"Hardware" |
| Type |
"Disk device" |
| Item |
"Disk array" |
BMC_StorageSubsystem relationships
| Relationship |
Name |
Source |
Destination |
| BMC_Dependency |
STORAGESUBSYSTEMOS |
BMC_StorageSubsystem |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_StorageSubsystem |
BMC_OperatingSystem |
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 key |
| NameFormat |
"Mainframe" |
| ShortDescription |
Storage name |
| Description |
Storage key |
| ComponentAliases |
Component alias from mainframe discovery |
| ManufacturerName |
Storage vendor |
| MediaType |
1 (fixed hard disk) |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
Storage model |
| PNPDeviceID |
Storage device_id |
| SerialNumber |
Storage volume_id |
| Category |
"Hardware" |
| Type |
"Disk device" |
| Item |
"Disk drive" |
Tape drives are mapped to BMC_TapeDrive CIs as follows:
| Name |
Storage key |
| NameFormat |
"Mainframe" |
| ShortDescription |
Storage name |
| Description |
Storage key |
| ComponentAliases |
Component alias from mainframe discovery |
| ManufacturerName |
Storage vendor |
| MediaType |
0 (removable media) |
| MFIntegrationID |
MFPart mf_integration_id – MainView identifier used for launch in context |
| Model |
Storage model |
| PNPDeviceID |
Storage device_id |
| Category |
"Hardware" |
| Type |
"Tape device" |
| Item |
"Tape drive" |
BMC_DiskDrive / BMC_TapeDrive relationships
| Relationship |
Name |
Source |
Destination |
| BMC_HostedSystemComponents |
STORAGESUBSYSTEMDASD |
BMC_StorageSubsystem |
BMC_DiskDrive |
| BMC_Dependency |
DASDOS |
BMC_DiskDrive |
BMC_OperatingSystem |
| BMC_HostedSystemComponents |
STORAGESUBSYSTEMTAPE |
BMC_StorageSubsystem |
BMC_TapeDrive |
| BMC_Dependency |
TAPEOS |
BMC_TapeDrive |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_DiskDrive |
BMC_OperatingSystem |
| BMC_Impact |
IMPACT |
BMC_TapeDrive |
BMC_OperatingSystem |
Tideway Blog