CRITERIASET (for reporting)

Purpose

Defines criteria for the journal records to be included in the report requested by the preceding REPORT batch command.

You can specify multiple CRITERIASET commands, each defining one or more conditions. Conditions within a CRITERIASET are implicitly combined by a logical AND operator. Multiple CRITERIASET commands are implicitly combined by a logical OR operator.

Figure 1. Defining selection criteria for journal records to be included in batch reports

Format

Read syntax diagramSkip visual syntax diagram
>>-CRITERIASET-------------------------------------------------->

   .-,------------------------------------------------------------------------------------.   
   V                                                                                      |   
>----COND=(-+-| Condition for CICS Resource Definition Changes Report package view |--+-)-+-><
            +-| Condition for CICS Resource Definition Changes Report resource view |-+       
            '-| Condition for CICS Runtime Resource Changes Report |------------------'       

Read syntax diagramSkip visual syntax diagram
Condition for CICS Resource Definition Changes Report package view

|--+-DATE--+-EQ-+--+-yyyy/mm/dd-------+-----+-------------------|
   |       +-NE-+  '-TODAY-+--------+-'     |   
   |       +-GT-+          '- -days-'       |   
   |       +-LT-+                           |   
   |       +-GE-+                           |   
   |       '-LE-'                           |   
   +-CPID--+-+-EQ-+--specific_value-+-------+   
   |       | +-NE-+                 |       |   
   |       | +-GT-+                 |       |   
   |       | +-LT-+                 |       |   
   |       | +-GE-+                 |       |   
   |       | '-LE-'                 |       |   
   |       '-+-EQ-+--masked_value---'       |   
   |         '-NE-'                         |   
   '-+-SCHEME-+--+-EQ-+--+-specific_value-+-'   
     '-USER---'  '-NE-'  '-masked_value---'     

Read syntax diagramSkip visual syntax diagram
Condition for CICS Resource Definition Changes Report resource view

|--+-DATE--+-EQ-+--+-yyyy/mm/dd-------+------------+------------|
   |       +-NE-+  '-TODAY-+--------+-'            |   
   |       +-GT-+          '- -days-'              |   
   |       +-LT-+                                  |   
   |       +-GE-+                                  |   
   |       '-LE-'                                  |   
   +-+-CONFIGURATION-+--+-EQ-+--+-specific_value-+-+   
   | +-GROUP---------+  '-NE-'  '-masked_value---' |   
   | +-NAME----------+                             |   
   | '-USER----------'                             |   
   +---TYPE----+-EQ-+--specific_value--------------+   
   |           '-NE-'                              |   
   +-+-CSD-----+--+-EQ-+--+-specific_value-+-------+   
   | '-CONTEXT-'  '-NE-'  +-masked_value---+       |   
   |                      '-<BLANK>--------'       |   
   '-CPID--+-+-EQ-+--+-<BLANK>------+-+------------'   
           | '-NE-'  '-masked_value-' |                
           '-+-EQ-+--specific_value---'                
             +-NE-+                                    
             +-GT-+                                    
             +-LT-+                                    
             +-GE-+                                    
             '-LE-'                                    

Read syntax diagramSkip visual syntax diagram
Condition for CICS Runtime Resource Changes Report

|--+-DATE--+-EQ-+--+-yyyy/mm/dd-------+------------+------------|
   |       +-NE-+  '-TODAY-+--------+-'            |   
   |       +-GT-+          '- -days-'              |   
   |       +-LT-+                                  |   
   |       +-GE-+                                  |   
   |       '-LE-'                                  |   
   +-+-TARGET--------+--+-EQ-+--+-specific_value-+-+   
   | +-CONFIGURATION-+  '-NE-'  '-masked_value---' |   
   | +-GROUP---------+                             |   
   | +-NAME----------+                             |   
   | '-USER----------'                             |   
   +---TYPE----+-EQ-+--specific_value--------------+   
   |           '-NE-'                              |   
   +-+-CSD-----+--+-EQ-+--+-specific_value-+-------+   
   | '-CONTEXT-'  '-NE-'  +-masked_value---+       |   
   |                      '-<BLANK>--------'       |   
   '-CPID--+-+-EQ-+--+-<BLANK>------+-+------------'   
           | '-NE-'  '-masked_value-' |                
           '-+-EQ-+--specific_value---'                
             +-NE-+                                    
             +-GT-+                                    
             +-LT-+                                    
             +-GE-+                                    
             '-LE-'                                    

A masked_value can use a plus sign (+) to represent a single character and an asterisk (*) to represent zero or more characters, in any combination.

The special value <BLANK> denotes a blank or null value. If you use <BLANK> in a condition, use the 2-letter code EQ or NE with spaces before and after; do not use sign operators with <BLANK>.

You must specify at least one COND parameter in each CRITERIASET. Each COND parameter must appear on a separate input line, except for the first, which may appear on the same line as CRITERIASET. To specify comparison operators, you can use 2-letter codes or signs:
EQ or =
Equal to
GE or >=
Greater than or equal to
GT or >
Greater than
LE or <=
Less than or equal to
LT or <
Less than
NE or ¬= or <>
Not equal to
If you use a 2-letter code, such as EQ, then you must insert one or more blanks before and after the code. If you use a sign, such as =, then do not insert blanks before or after the sign. All parameter values are case-insensitive and are converted to uppercase prior to processing.

For the NAME keyword, the specified value matches all resource definitions of similar names regardless of case sensitivity. Resource definitions of lowercase, uppercase, or mixed case names may match the value.

You can use the same keyword, such as DATE, in more than one COND parameter. For example, the following combination of COND parameters selects journal events that occurred in January 2007:

CRITERIASET COND=(DATE GE 2007/01/01),
            COND=(DATE LE 2007/01/31)

Condition keywords

You can specify the following keywords in conditions, depending on the particular report. Condition keywords typically correspond to column headings in the report; not all keywords apply to all reports.

CONFIGURATION, CONTEXT, or CSD
(Applies only to the CICS Resource Definition Changes Report resource view and the CICS Runtime Resource Changes Report.) For a CICS Resource Definition Changes Report, these attributes refer to the location of the changed resource definitions.

For a CICS Runtime Resource Changes Report:

  • CONFIGURATION refers to the CICS configuration associated with the resource definition used as the based for change processing
  • CONTEXT refers to the CICSPlex® SM context in which the change occurred.
  • CSD refers to the CSD file associated with the resource definition used as the based for change processing

The CSD value is the fully qualified data set name of a CSD file without enclosing quotes. The CONFIGURATION value is the name of a CICS configuration, and the CONTEXT value is the name of a CICSPlex SM context.

For CONTEXT and CSD, you can use the special value <BLANK> to denote a blank or null value. For example, the condition CONTEXT EQ <BLANK> excludes from the report any changes to resource definitions in contexts. CSD EQ <BLANK> is equivalent to CONTEXT NE <BLANK>, and CSD NE <BLANK> is equivalent to CONTEXT EQ <BLANK>.

CPID
The CPID keyword corresponds to the Package column heading in a report, identifying the change package that caused the change to the resource definition.

In a resource view report, you can use the special value <BLANK> to denote a blank or null value. For example, the condition CPID EQ <BLANK> excludes changes caused by change packages, while CPID NE <BLANK> excludes changes not caused by change packages.

DATE
Specifies the date that the journal record was created. You can specify this date as either:
  • A 4-digit year, 2-digit month, and 2-digit day, separated by either forward slashes (/) or hyphens (-). For example, 2005/04/29 represents 29 April 2005.

    or

  • The keyword TODAY optionally followed by a hyphen (-) and a number of days, 0366. For example, DATE GE TODAY-1 selects journal records created today (the day that you run the batch program) and yesterday. For a weekly report, specify DATE GE TODAY-7. TODAY and TODAY-0 are equivalent: they select journal records created today.
GROUP
(Applies only to the CICS Resource Definition Changes Report resource view and the CICS Runtime Resource Changes Report.) Group that the resource definitions belong to (or ResGroup, for context-based resource definitions).
NAME
(Applies only to the CICS Resource Definition Changes Report resource view and the CICS Runtime Resource Changes Report.) Name of the resource definitions.
Package
Package is a report column heading, but is not a valid condition keyword. To set criteria for change package IDs, use the CPID keyword.
SCHEME
(Applies only to the CICS Resource Definition Changes Report package view and the CICS Runtime Resource Changes Report.) Migration scheme used by the change package.
TARGET
(Applies only to the CICS Runtime Resource Changes Report.) CICS region or CICSPlex SM target scope where the change occurred.
TYPE
(Applies only to the CICS Resource Definition Changes Report resource view and the CICS Runtime Resource Changes Report.) Resource type of the resource definitions. You can specify the resource type using either the CSD naming convention or the CICSPlex SM naming convention. For example, you can specify either TRANSACTION or TRANDEF. For a list of resource types, see Table 1.
USER
ID of the user who invoked the API command.

Reference Reference

Feedback


Timestamp icon Last updated: Friday, 1 November 2013


http://pic.dhe.ibm.com/infocenter/cicsts/v5r1/topic//ccv-batch-cmd-report-criteriaset.htm