Mainframe pattern: Mainframe.Software


Overview

This module contains the pattern for bulk discovery of software on a Mainframe based on information returned by the zOS Agent.

Software Pattern Model

Pattern Trigger

Pattern

Node Kind

Attribute

Op

Value

MainframeBulkSoftware

DiscoveredMainframeViewResultList

discovery_method

in

['getApplicationServer',
'getCommServer',
'getDatabaseServer',
'getMessageServer',
'getPrintServer',
'getResourceServer',
'getSecurityServer',
'getTransactionServer']

SI Creation

The MainframeBulkSoftware pattern creates a series of SoftwareInstance nodes where the key of each is based on result.Name.

Clustered Software Identification

The MainframeBulkSoftware pattern attempts to identify clustered software by testing to see if the mfpart_id is contained in the software name:

result.Name Format

Meaning

<model>-<mfpart_id>-<server_id>

This shows that the software is specifically running on a single LPAR.

<model>-<sysplex_name>-<server_id>

This shows that the software is clustered and is currently running on the reported LPAR, but could be moved to another LPAR when next scanned.

Relationship

If the software is not clustered, then ensure a HostedSoftware relationship is created between the SoftwareInstance node and the MFParts.

If the software is clustered, then ensure the SoftwareInstance node is only related, via a unique HostedSoftware relationship, to the reported MFPart nodes and remove any old relationships to MFPart nodes where the software was previously running.

If the SoftwareInstance node is related to the reported Sysplex node, ensure a dependency relationship is created between the SoftwareInstance node and the sysplex.


 

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

BMC Discovery content reference