ANDing Patterns Together - ironstream_for_servicenow_service_mp - 1.0

Ironstream for ServiceNow® Service Mapping for IBM Z® Guide

Product type
Product family
Ironstream > Ironstream for ServiceNow® Service Mapping
Product name
Ironstream for ServiceNow Service Mapping for IBM Z
Ironstream for ServiceNow® Service Mapping for IBM Z® Guide
First publish date

All patterns that have the same Pattern Name and CI Type will have their criteria AND’ed together; that is, for a CI to be part of a Service it must meet the criteria from all the Patterns with the same name.

This allows more flexible pattern matching, for example: you may have two DB2 Subsystems with a DB2 database of the same name, however only one is part of a given Service. Using ANDed Patterns you can ensure that only one of the two DB2 databases is added to the Service.

To achieve this, all the Patterns that you wish to be ANDED together must have the name Pattern Name and CI Type. ANDing patterns together is simple to do through the UI either by using of the Copy Existing Pattern dropdown or by typing in the pattern name into the Pattern Name input.

There are certain restrictions on ANDing patterns together; each of the following fields must remain the

same between all AND’ed Patterns:

  • Pattern Name

  • Service Name

  • Traversal

  • Max Depth

If these fields don’t match between the patterns, the Service Map may be produced incorrectly, or not at all. These restrictions ensure that the ANDed patterns are always capable of adding at least one CI to a Service.

If a set of patterns contains multiple CI Types, they will be processed by CI Type only. This means if the pattern contained two patterns for CICS CIs and two patterns for DB2 CIs, then the CICS and DB2 patterns would form two separate set of criteria. Both CI Types would be associated with the service.

There is no OR functionality implemented currently; however, multiple patterns of different names can belong to one service. When Ironstream Mapping runs, it will associate all matching CIs for either patterns to the same service regardless of if the CI didn’t meet both patterns’ criteria. For example, if you have two different patterns names for DB2 Database, where Pattern1 has DB2 Database Name=ABC and Pattern2 has DB2 Database Name=DEF, then DB2 Databases matching either Pattern1 or Pattern2 will be present in the service.