Default Exception Definitions

The Default Exception Definitions screen lists the exception definitions distributed with TMON for z/OS. As an authorized user, you can examine the function of each default exception definition and decide which definitions (if any) you want to load into the TMON Repository and/or move into your repository.


  JOBNAME:                 DEFAULT Exception Definitions        DATE:   
  SYSID  :                                                      TIME:   
  COMMAND:                                                      CYCLE: MMSS     
 
                                                             User ID: TMONMVS   
   Target POS: TMVSV045.TDVPHC.POS                           Ex Date: 09/06/16  
   Defaults  : GLOBAL                          NEW: GLOBAL                      
   Collection: P45CFG                            C: P45CFG                      
   Instance  : SYSA                              I: SYSA                        
   Over-Write: NO     Existing Exception Definitions?                           
  LINES: 1 TO 11 OF 214                 SORT COL: MC SEQ: A               >  1  
  ?? NAME     QUAL     DESCRIPTION                         L COLLECT  INSTANCE  
  _  CHIACBSY DEFAULT  AVERAGE CHANNEL PATH PERCENT BUSY * G                    
  _  CIPCTCSA DEFAULT  PERCENT CSA (BELOW 16MB) IN USE     G                    
  _  CIPCTECS DEFAULT  PERCENT ECSA (ABOVE 16MB) IN USE    G                    
  _  CIPCTESQ DEFAULT  PERCENT ESQA (ABOVE 16MB) IN USE    G                    
  _  CIPCTSQA DEFAULT  PERCENT SQA (BELOW 16MB) IN USE     G                    
  _  DVIACONN DEFAULT  DASD AVERAGE CONNECT TIME > THRESHO G                    
  _  DVIADISC DEFAULT  DASD AVERAGE DISCONNECT TIME > THRE G                    
  _  DVIAODCB DEFAULT  AVG # OF OPEN DATA SETS > THRESHOLD G                    
  _  DVIAPEND DEFAULT  DASD AVERAGE PENDING TIME > THRESHO G                    
  _  DVIARESP DEFAULT  DASD AVERAGE RESPONSE TIME > THRESH G                    
  _  ENCHNRDY DEFAULT  CHPID HAS CHANGED STATUS            G                    
   HELP INFORMATION = PF1                            PF KEY ASSIGNMENTS = PA1

See GRF Screens for information on data filtering and sorting capabilities of this screen.

Note: This screen supports 3270 Mod 5 formats.

This screen eliminates the need to run a batch job to perform this function.

Note: The ability to use this screen is governed by the EXCPTDEF secured function. For detailed information on product security, see Security Definitions in the TMON Strategic Services Documentation.

This screen also lets you suppress the writing of the definitions if you have previously loaded them. This capability enables you to easily manage exception definitions when installing a new version of TMON for z/OS or applying and implementing default definitions added or modified through PTFs.

Once the exception definitions are imported into the TMON Repository, you can use the Refresh Exception Definitions screen to reload the definitions into TMVMSTR address spaces.

Use the LEFT and RIGHT commands or cursor-select the left (<) and right (>) scroll arrows to access all the fields displayed on this screen.

Accessing this Screen

To access this screen

  • On the command line, enter =2.7.1.

Primary Commands

Product-specific commands.
Enter these commands on the command line:

Command

Description

CLEARALL

Clears all line commands and status indicators from the ?? field, including import (M) markers. This command also resets the status indicators for any exception definition processed by the GO command, including:

  • Definitions newly added (N) to the repository
  • Definitions updated (U) in the repository
  • Definitions not updated because a duplicate (*) exception definition was found in the repository and the Over-Write field was set to No.

After you issue the CLEARALL command, you can respecify definitions to be imported into your repository.

DEFAULT

Updates the roster fields with the system default values.

GO

Processes all exception definitions marked for import (M) into your repository. The actions taken depend on the setting of the Over-Write field.

  • If the Over-Write field is set to Yes, the GO command will update the existing exception definition found in your repository with the same exception definition name/qualifier. In this case, the ?? field will be set to U to indicate that the existing exception definition was updated at the scope (that is, global, collection, or instance) indicated for that exception. If a duplicate exception definition name/qualifier is not found in your repository, the marked exception will be imported and the ?? field will be set to N to indicate that a new exception definition was imported. The TMVS31304I message will specify the total number of new (N) definitions imported into your repository and the total number of definitions updated (U) in your repository.
  • If the Over-Write field is set to No, the GO command creates new exceptions as the specified level, but does not update existing exceptions.

The new and updated exception definitions are not active until a refresh request is issued or TMVSMSTR is restarted. If you want to make changes to the default exceptions, you should do so after the GO command is issued and before the exceptions are refreshed in TMVSMSTR. Use the Exception Definition screen (accessed via option 2.2) to change anything other than the scope of the exception.

IMPORTALL

Marks all the exception definitions for import.

RESET

Resets the roster fields for all exception definitions to their original values.

SETALL

Updates the roster fields for all exception definitions, based on the scope specified in the NEW field:

  • If NEW=GLOBAL, this command sets the L field to G and both the Collection and Instance fields to blanks.
  • If NEW=COLLECTION, this command sets the L field to C, the Collection field to the new collection name specified in the C field, and the Instance field to blanks.
  • If NEW=INSTANCE, this command sets the L field to I and both the Collection and Instance fields to the new values specified in the C and I fields, respectively.
GRF commands.

Enter GRFCMDS on the command line for a list of the GRF Commands that you can issue on this screen.

For syntax and descriptions of all commands, see TMON Commands.

Line Commands

Enter these commands in the ?? field:

Command

Description

C

Assigns a collection scope to the exception definition, resulting in these actions:

  • The L field is set to C (collection).
  • The COLLECT field is set to the new collection name specified in the C field.
  • The INSTANCE field is set to blanks.

D

Sets the L, COLLECT, and INSTANCE fields to their default values for the selected exception definition.

G

Assigns a global scope to the exception definition, resulting in these actions:

  • The L field is set to G (global).
  • The COLLECT and INSTANCE fields are set to blanks.

I

Assigns an instance scope to the exception definition, resulting in these actions:

  • The L field is set to G (global).
  • The COLLECT field is set to the new collection name specified in the C field.
  • The INSTANCE field is set to the new instance name specified in the I field.

M

Marks the exception definition with an M to indicate that it should be imported into the repository when you issue the GO command. Enter this command in the ?? field next to the exception definition(s) you want to import. Once you have marked all the desired exception definitions, issue the GO command.

R

Resets the L, COLLECT, and INSTANCE fields for the exception definition to their original values.

Z

Clears the import (M) mark for the exception definition.

For syntax and descriptions of all commands, see TMON Commands.

Fields

The < > n, (filter area), FA=, LINES: nnnnn TO nnnnn OF nnnnn, SEQ, and SORT COL fields are GRF fields and are described in GRF Screens.

Field

Description

??

Lets you issue the C, D, G, I, M, R, and Z line commands, described in Default Exception Definitions.

After you issue the GO command, all rows marked with M are written to the repository. If the Over-Write field is set to No, marked exceptions are not written. If it is set to Yes, all existing exception definitions are overwritten.

The TMVS31309I message reports the number of exception definitions currently marked for import (M) into your repository.

Once you issue the GO command, the ?? field for each previously marked definition shows the status indicator for the action performed by the command. Valid values are:

  • D indicates that a duplicate exception definition was found in the repository. TMON for z/OS does not import the marked definition because the Over-Write field was set to No when you issued the GO command.
  • N indicates that a duplicate exception definition was not found in the repository, and the marked definition was imported as a new exception definition.
  • * indicates that a duplicate exception definition was found in the repository, and TMON for z/OS updated the existing definition with the marked definition. This action is taken only if the Over-Write field is set to Yes when you issue the GO command.

C

Specifies the collection name that you want to use for the current exception. Overtype this value to specify a new collection name that TMON for z/OS will apply to the exception(s) when specifically requested via primary or line command. (See Default Exception Definitions and Default Exception Definitions for complete information.)

A collection name can be up to 26 bytes long. Due to the limited space allotted for this value on the screen, the displayed collection name is truncated to eight bytes; however, the full name is assigned to the exception(s) when imported.

COLLECT

Displays the collection name for the exception if its scope is collection (L=C) or instance (L=I). Otherwise, it contains blanks.

Collection

Displays the default collection name for the current system.

You cannot change this field value; you must use the C field to specify a new collection name.

Defaults

Displays the default level (scope) at which data is stored and retrieved in the TMON Repository. Valid values are GLOBAL, COLLECTION, and INSTANCE.

See The TMON Repository for complete information on each scope.

DESCRIPTION

Provides a brief explanation of the nature of the exception definition.

Ex Date

Displays the date the exceptions were exported from the source repository, in MM/DD/YY format. Use this field to verify that you are importing the correct exception definitions.

I

Specifies the instance name that you want to use for the current system. Overtype this value to specify a new name. An instance name can be up to eight bytes long.

Instance (top)

Displays the default instance name for the current system.

You cannot change this field value; you must use the I field to specify a new instance name.

INSTANCE (column)

Displays the instance name for the exception if it has an instance scope (L=I). Otherwise, it contains blanks.

L

Indicates the level (scope) of the exception definition. Valid values are G (global), C (collection), and I (instance).

NAME

Displays the name of the exception definition. This name along with the exception qualifier (the QUAL field) form the repository key name.

Note: If the exception definition is based on a TMON Log File Services field, this name is the same as the data dictionary field name.

NEW

Specifies the new scope at which you want the data to be stored in the TMON Repository:

  • Enter G to change the scope to GLOBAL and override the default value specified in the Defaults field.
  • Enter C to change the scope to COLLECTION and override the default value specified in the Defaults field.
  • Enter I to change the scope to INSTANCE and override the default value specified in the Defaults field.

Over-Write

Indicates whether you want to overwrite existing exception definitions in your repository with these revised exception definitions. Valid values are Yes and No; No is the default.

QUAL

Displays the name of the exception qualifier. This name along with the exception definition name (the NAME field) form the repository key name.

T Critical A ?

Displays information about the critical threshold segment in the exception definition, which is made up of these items:

  • The TESTER. Valid values are >, <, =, or /.
  • The threshold value.
  • The active setting. Valid values are Y (segment is active) and N (segment is inactive).

If the segment is not defined, --- is displayed for the threshold value. If the threshold type is character, N/A is displayed for the threshold value.

When a critical threshold segment triggers an exception event, the warning and informational segments are not evaluated. The critical segment information is displayed in red on color screens.

T Info A ?

Displays information about the informational threshold segment in the exception definition, which is made up of these items:

  • The TESTER. Valid values are >, <, =, or /.
  • The threshold value.
  • The active setting. Valid values are Y (segment is active) and N (segment is inactive).

If the segment is not defined, --- is displayed for the threshold value. If the threshold type is character, N/A is displayed for the threshold value.

The informational segment is examined when the critical and warning segments did not trigger an event. The informational segment information is displayed in green on color screens.

T Warning A ?

Displays information about the warning threshold segment in the exception definition, which is made up of these items:

  • The TESTER. Valid values are >, <, =, or /.
  • The threshold value.
  • The active setting. Valid values are Y (segment is active) and N (segment is inactive).

If the segment is not defined, --- is displayed for the threshold value. If the threshold type is character, N/A is displayed for the threshold value.

When a warning threshold segment triggers an exception event, the informational segment is not evaluated. The warning segment is examined when the critical segment did not trigger an event. The warning segment information is displayed in yellow on color screens.

Target POS

Displays the dataset name of the repository to which you want the exception definitions imported.

User ID

Displays the ID of the user requesting the export from the source repository. Use this field to verify that you are importing the correct exception definitions.