Discovery Mechanism

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

The Mainframe by EView discovery is an agent-based discovery solution. To discover infrastructure resources and applications on z/OS LPARs, an agent component must be deployed on every LPAR that has to be discovered.

A high-level architectural diagram for this discovery solution is illustrated in the following image:

The discovery process works as follows:

Connection job:

The EView Connection job is the first job that discovers CIs for this discovery. It triggers against all the configured Probe Gateway CIs in the UCMDB.
On the Data Flow Probe, the eview_connection.py discovery script first looks for the presence of the EView/390z Discovery Client in the pre-configured EView/390z Discovery Client installation path in the discovery job. It then looks for the z/OS LPAR nodes that have been configured in the EView/390z Discovery Client.
For every configured z/OS LPAR node in the EView/390z Discovery Client, the discovery job creates an eview agent CI connected to a zOS CI along with a CI for its primary IP address.

Resource and application discovery jobs:

The remaining jobs are all activated on the TQL query eview_agent, which invokes the job against all discovered eview agent CIs.
The discovery scripts execute various MVS commands against the z/OS LPAR using the EView/390z Agent, parse the returned output, and create the relevant CI types.