MONDEF (Monitor definitions)

A monitor definition qualifies a resource type identified in a monitor specification by indicating the occurrences of the resource that are to be included in or excluded from monitoring. A monitor definition also identifies which resources are to be reported to the resource status facility.

Examples of how to use this view can be found in:

To display information about existing monitor definitions, issue the command:

   MONDEF [mondef]

where mondef is a specific or generic monitor definition name. If you omit this parameter, the view, illustrated in Figure 59, includes information about all existing monitor definitions within the current context.

Figure 59. The MONDEF view
 27FEB2005  19:33:23 ----------- INFORMATION DISPLAY ---------------------------
 COMMAND  ===>                                                 SCROLL ===> PAGE
 CURR WIN ===> 1        ALT WIN ===>
  W1 =MONDEF============EYUPLX01=EYUPLX01=27FEB2005==19:33:23=CPSM=========11===
 CMD Def      Resource Resource Include Res  Monitor Definition
 --- Name---- Name---- Type---  Data--- Stat Description------------------
     EYUMOD01 *        MCONN    YES     YES  SSet - All Connections
     EYUMOD02 CO*      MTRAN    YES     NO   SSet - All CO* Transactions
     EYUMOD03 CO*      MTDQS    YES     NO   SSet - TDQs CO*
     EYUMOD04 EQ*      MTDQS    NO      YES  SSet - TDQs EQ*
     EYUMOD05 DFHCSD   MFILE    YES     YES  SSet - DFHCSD Files
     EYUMOD06 *        MJRNL    YES     YES  SSet - All Journals
     EYUMOD07 SP*      MTERM    YES     YES  SSet - All SP* Terminals
     EYUMOD08 CEMT     MTRAN    YES     YES  SSet - CEMT Transaction
     EYUMOD09 EYUF*    MFILE    YES     YES  SSet - EYUF* files
     EYUMOD10 ET*      MTRAN    YES     YES  SSet - ET* Transations
     EYUMOD11 EYU*     MPROG    YES     YES  SSet - EYU* Programs
 

Action commands and overtype fields

Table 37 summarizes the action commands you can use with the MONDEF view. Table 38 identifies the overtype fields you can modify when you use the SET action command.

Table 37. MONDEF view action commands
Primary command Line command Description
n/a ADD Add an association between a monitor definition and a monitor group, as described in topic Adding an association to a monitor group.
n/a BRO Browse a monitor definition in the data repository.

The format of the resulting panel is similar to that shown in Figure 60. The panel fields are not modifiable.

CREate CRE Create a monitor definition and add it to the data repository, as described in topic Creating a monitor definition.

When you use the primary command CREate, some fields in the new view may contain values supplied by CICSPlex® SM; you may change these values. When you enter the line command CRE next to the name of a monitor definition, fields in the new view contain values to be modelled (from the existing monitor definition).

n/a INS Install a monitor definition into a CICS® system or CICS system group, as described in topic Installing a monitor definition.
n/a MAP Display a visual map of resource monitoring definitions using the specified definition as a starting point.
n/a REM Remove a monitor definition from the data repository.
n/a SET Change a monitor definition using overtype fields (see Table 38).
Note:
The value you specified in the Require Set field on the CICSPlex System Manager entry panel determines whether or not you must use the SET command when you overtype a field.
TEMPMP cmasid n/a Change the temporary maintenance point CMAS to a specific CMAS or display a selection list based on a generic CMAS ID.
n/a UPD Update a monitor definition in the data repository.

The format of the resulting panel is similar to that shown in Figure 60. You can change the contents of any field in the panel except Definition Name.

Table 38. MONDEF view overtype fields
Field name Value
Resource Name Specific or generic name of a resource occurrence.
Resource Type Type of resource to be monitored.
Include Data YES|NO
Note:
YES is the default.
Res Stat YES|NO
Description 1- to 30-character description of the definition.

Hyperlink fields

There are no hyperlink fields in the MONDEF view.

Creating a monitor definition

There must be one or more monitor definitions for each resource type identified in a monitor specification. You create the appropriate monitor definitions for all resource types except Region, Global, and DB2/DBCTL. CICSPlex SM automatically generates and maintains monitor definitions for the Region, Global, and DB2/DBCTL resource types.

Figure 60 shows the format of the panel produced when you use the create primary (CREate) or line (CRE) action command from the MONDEF view.

Figure 60. Creating a monitor definition
 ------------------------ Create Monitor Definition for EYUPLX01 ---------------
 COMMAND  ===>
 
 Definition Name ===>
 Description     ===> Monitor all files
 
 Resource Definition:
  Name             ===> *      Resource Name
  Type             ===> MFILE  MCONN/MFILE/MJRNL/MPROG/MTDQS/MTERM/MTRAN
  Include          ===> YES    Include for monitoring (NO, YES)
  Resource Status                Operational status for resource
         Facility  ===> NO         status facility (NO, YES)
 
 Press Enter to create Monitor Definition.
 Type END or CANCEL to cancel without creating.

Provide the following information, as appropriate.

Definition Name
Specify a 1- to 8-character name for the monitor definition. The name can contain alphabetic, numeric, or national characters. However, the first character must be alphabetic.
Description
(Optional.) Specify a 1- to 30-character description of the resource occurrence that is to be monitored.
Name
Indicate the specific or generic name of a resource occurrence.

Table 39 shows the alphabetic, numeric, and special characters that you can use to identify a resource occurrence. In addition to these characters, you may also include the generic characters + (plus sign), * (asterisk), or both.

Table 39. Resource occurrence naming standards
Resource type A-Z 0-9 @ # $ _ . / % & ? ! " = , : < > ¬ ¢
MCONN Yes Yes Yes
MFILE Yes Yes Yes
MJRNL Yes
Note:
If the monitor definition is to be installed in a system running the CICS TS, all of these characters are valid in the journal name.
MPROG Yes Yes Yes
MTDQS Yes Yes Yes Yes
MTERM Yes Yes Yes Yes Yes
MTRAN Yes Yes Yes Yes Yes
Type
Specify the type of resource to be monitored, where:
Type
Means
MCONN
Connections and LU 6.2 modenames
MFILE
Files
MJRNL
Journals
MPROG
Programs
MTERM
Terminals
MTRAN
Transactions
Note:
Start of change
If the MAS has history datasets (EYUHISTx) available, an MTRAN MONDEF will also include or exclude (depending on the MONDEFs 'Include' attribute) historical task (HTASK) data collection for the transactions specified on the 'Name' attribute.
End of change
MTDQS
Transient data queues
Note:
When specifying a resource type, consider the CICS systems in which this monitor definition will be installed. Not all resource types are supported in all of the CICSPlex SM managed CICS systems. You may specify any resource type in the monitor definition. However, prior to installing the definition, CICSPlex SM verifies that the resource type is supported in each target CICS system. For those systems that do not support the resource type, CICSPlex SM issues a message indicating that the definition is not installed.
Include
Specify YES or NO to indicate whether the designated resource is to be included in or excluded from CICSPlex SM monitoring.

You can use this field to tailor resource monitoring. For example, to monitor all transactions except those with transaction identifiers starting with PAY, you would define two monitor definitions, where one definition includes all transactions in resource monitoring and the other definition identifies the generic group of transactions to be excluded, as in:

   Definition ===> DEF1
 
     Name         ===> *
     Type         ===> MTRAN
     Include      ===> Yes
 
   Definition ===> DEF2
 
     Name         ===> PAY*
     Type         ===> MTRAN
     Include      ===> No

Alphabetic characters take precedence over special characters when CICSPlex SM is determining whether the name of a specific resource occurrence matches a monitor definition. Thus, you must be careful when identifying a resource occurrence. For example, suppose you created the following two monitor definitions.

   Definition ===> DEF3
 
     Name         ===> +++R*
     Type         ===> MFILE
     Include      ===> No
 
   Definition ===> DEF4
 
     Name         ===> PAY*
     Type         ===> MFILE
     Include      ===> Yes

With these definitions, files containing an R in the fourth position of their names will be excluded from monitoring. However, because alphabetic characters have precedence, any file name starting with PAY, including PAYR, will be included in monitoring. To prevent this from happening, you must create another monitor definition that explicitly excludes file names starting with PAYR.

Resource status facility
Specify YES or NO to indicate whether the designated resource should be identified to the resource status facility.

Press Enter to add the monitor definition to the data repository.

Adding an association to a monitor group

Figure 61 illustrates the panel produced when you use the add (ADD) line action command from the MONDEF view.

Figure 61. Adding an association between a monitor group and a monitor definition
 ------------------ Add Monitor Definition to Group for EYUPLX01 ---------------
 COMMAND  ===>
 
  Definition Name         EYUMON01
  Description             Programs
  Type                    MPROG
  Resource Name           *
  Include                 YES
  Resource Status
       Facility           NO

  Monitor Group Name ===>              Monitor Group or Generic
  Active Period      ===>              Period Definition or Generic
 
 
 Press Enter to add Monitor Definition to Group.
 Type END or CANCEL to cancel without adding.

Provide the following information, as appropriate.

Monitor Group Name
Enter the specific or generic name of an existing monitor group. If you specify a generic value, a list of valid monitor groups is displayed.
Active Period
(Optional) Enter the specific or generic name of a period definition that identifies the range of hours during which the monitor definition is to be active. If you specify a generic value, a list of valid period definitions is displayed.

If the name you specify does not belong to an existing period definition, you can create that period definition later. If you leave this field blank, the monitor definition remains active for as long as the CICS system is running, or until you discard it.

To add the monitor group and interval to the designated monitor definition, press Enter.

You can use the MONINGRP view, as described in topic MONINGRP (Monitor definitions in monitor groups), to remove a monitor definition from a monitor group.

If an appropriate monitor group does not currently exist, you must first create the group, as described in topic Creating a monitor group. Then you can add the monitor definition to it using either that ADD action command, or the ADD action command described in Adding a monitor definition to a monitor group.

Installing a monitor definition

You can install a monitor definition into one or more active CICS systems that are within the CICSplex identified as the context. You can do this whether or not the monitor definition is associated with a monitor group that is also associated with a monitor specification. However, before attempting to install a monitor definition, you should review the requirements described in Activating resource monitoring.

A monitor definition can be automatically installed in a CICS system when that system starts. For this to occur, associate the definition with a monitor group. Then associate that monitor group with a monitor specification that is associated with the CICS system.

Figure 62 illustrates the panel produced when you use the install (INS) line action command from the MONDEF view.

Figure 62. Installing a monitor definition
 ------------------- Install Monitor Definition for EYOPLX01 -------------------
 COMMAND  ===>
 
  Definition Name      EYUMON02
  Description          Monitor all files
  Type                 MFILE
  Resource Name        *
  Include              YES
  Resource Status
    Facility Status    NO

 
  Scope           ===>           System Group, CICS System, or Generic
  Active Period   ===>           Blank, PERIODEF, or Generic
 
 Press Enter to install Monitor Definition.
 Type END or CANCEL to cancel without installing.

Provide the following information:

Scope
Enter the specific or generic name of a CICS system or CICS system group for which the monitor definition is to be installed. The CICS system or CICS system group must be within the CICSplex identified as the current context. If you specify a generic value, a list of valid CICS systems and CICS system groups is displayed.
Active Period
(Optional) Enter the name of an existing period definition or a generic name that identifies the range of hours during which the monitor definition is to be active. If you specify a generic value, a list of valid period definitions is displayed.

If you leave this field blank, the monitor definition remains active for as long as the CICS system is running, or until you discard it.

To install the monitor definition into the designated CICS system or into all of the CICS systems associated with the designated CICS system group, press Enter.

When the monitor definition you install:

If you install a monitor definition that specifies a 1- to 8-character journal name (for use in a system running the CICS TS) in a system that does not support such journal names, monitoring does not occur, as the specified journal will not exist.

You can use the MONACTV view, as described in Table 3, to deactivate an installed monitor definition.

[[ Contents Previous Page | Next Page Index ]]