The CICSPlex® SM Web User Interface selection criteria appear in the selection criteria and refresh area of a view and the selection criteria area of a menu. The selection criteria are used to specify the objects against which a query operates. These criteria are:
This is the CICSplex name and is used for almost all views.
This is the CMAS name. This is used only when you are viewing CMAS level configuration data such as CMAS status and the CICSplexes connected to a CMAS.
This is a CICSplex, CICS® group, MAS, or logical scope name. The scope is a subset of the context, and limits the effects of CICSPlex SM commands to particular CICS systems or resources. If the CMAS context is being used, the scope is ignored. The scope is only used for certain resource types.
Parameter filters are only required for some resources. For each parameter you define a value. For example, you need to enter a workload name in order to access a view for the WLMAWTOR object.
Attribute filters are optional for all resources. Attribute filters enable a comparison between a single attribute and a single value (or a pattern, if the attribute is a character string). Relational operators, such as equality or inequality can be used.
Either the context or CMAS context is used for all operations.
Selection criteria may be specified at a number of levels. As you navigate around the views and menus, the selection criteria are defined at each level and will be propagated down, if appropriate. Additionally, some views and menus allow you to dynamically change the selection criteria for the current display.
Note that changing the selection criteria (either explicitly or implicitly through a link) affects only the current view or menu and any subsequent views or menus. If you go back to a previous view or menu the selection criteria are restored.
The CMAS context, context, and scope fields allow you to define the limits of the data to be displayed in any particular view.
The Web User Interface selects the appropriate context for the type of data being displayed in each view. You can use the View Editor to choose whether to display the CICSplex name, the CMAS name, or both, on a view.
You use the View Editor (see Customizing the Web User Interface for information about the View Editor) to define whether the context and scope fields are to be display only, modifiable, or hidden. For example you might have:
An example of the context and scope fields is shown in Figure 7.
You can change the context and scope on any views that allow it. To change the context and scope:
You cannot clear context and scope fields; if present they must always contain a value.
The context and scope settings are inherited by default but may be overridden by the link to a menu or view. The values, once set, are used by all subsequent views or menus until you change them. Changed context and scope settings apply only to the current view and all subsequent views. If you go back to a previous view or menu, the context and scope values are restored.
A request for CICSPlex SM managed object data can produce a large number of managed object records. Without filters, the Web User Interface returns all of the managed object records that exist within the current context and scope. You can use a filter to limit the number of resources retrieved by a request.
You use the View Editor (see Customizing the Web User Interface for information about the View Editor) to choose the filters that will be available on a view, and to determine the order in which the filters appear.
There are two types of filter:
There are some situations when filtering of attribute values can sometimes lead to unexpected results:
To apply a filter, select the Refresh button.
To clear a filter, delete the contents of the field or select the blank option from a selection list and press the Refresh button.
Once the selection criteria have been set you are presented with an appropriate menu or the appropriate data in a view.
Filters on tabular views can take up large amounts of screen space restricting the data that can be displayed. You can mitigate this by collapsing the filters when you are not altering them. You can expand them again when you want to change them.
To collapse the filter, click the collapse (minus sign) icon at the top left of the filter area.
To expand the filters, click the Expand filter (plus sign) icon.
In order to determine whether filters should be displayed in their expanded or collapsed state by default use the optional WUI server initialization parameter:
FILTERSTYLE(EXPAND/COLLAPSE)
If you do not specify this parameter, the WUI displays filters in the expanded state by default.
When you navigate away from a view with filters in a non-default state, the filter area in the new view reverts to the default filter setting as specified in the FILTERSTYLE parameter.
If you navigate away from a view and then return in the same WUI session, the filters remain in the state you left them when the view was last displayed.
A relational operator is specified only for attributes. Relational operators are shown in Table 4.
Operator | Meaning |
---|---|
= | Equal to |
<> | Not equal to |
> | Greater than |
< | Less than |
>= | Greater than or equal to |
<= | Less than or equal to |
A value may be specified for both parameters and attributes. There are two types of values:
'AB*'X is equivalent to AB5C.
If
the filter contains a generic character immediately following the
hexadecimal string, this is considered to be a generic string. For
example:
'AB'X* is equivalent to AB*.
You cannot use a plus sign (+) as a filter character in a hexadecimal string.
See Table 5 for examples of generic characters and their implications in character and hexadecimal filters.
HEX attributes | CHAR attributes | |
Generic in quotes
|
Literal match
|
Generic match
|
Generic outside quotes
|
Generic match
|
Invalid |
Generic without quotes
|
Generic match
|
Generic match
|
Setting record count warnings makes the WUI issue a warning if a request to open a view will result in a larger than expected amount of data. This provides an opportunity to alter the filters on the view and confirm or cancel the request before the request is executed.
This feature does not apply to all WUI views. It applies to the views associated with the following resources:
CMDT | FEPINODE | PROGRAM |
CONNECT | FEPIPOOL | REMFILE |
DB2CONN | FEPITRGT | REMTDQ |
DB2ENTRY | INDTDQ | REMTRAN |
DB2TRN | INTRATDQ | RQMODEL |
DOCTEMP | JOURNAL | SMFJRNL |
DSKJRNL | JRNLNAME | SYSDUMP |
DSNAME | LOCFILE | TAPEJRNL |
ENQMODEL | LOCTRAN | TCPIPS |
EXITGLUE | MODENAME | TERMNL |
EXITTRUE | PARTNER | TRAN |
EXTRATDQ | PROCTYP | TRANDUMP |
FEPICONN | PROFILE | TSMODEL |
See Menus, views and related resourcesfor a complete list of WUI views and their associated resources.
There are two ways of specifying the number of records required to trigger the warning mechanism:
In both cases the default value is 0 meaning that no warnings are issued.
A value set in a user group takes precedence over a value set in DEFAULTWARNCNT. Before a warning is issued the WUI checks to determine whether or not the signed on user is associated with a user group (this can occur only if the WUI is running with security switched on). If so, the WUI uses any value for the warning count specified in that user group. If the user does not belong to a user group, or no maximum value is set, the WUI uses any value set in the DEFAULTWARNCNT parameter.
If the value for the warning count is greater than 0, the WUI checks the size of the potential set of records to be returned. This gives an indication of the maximum number of records that could be returned. It is not always accurate as any filters other than that associated with the first part of the primary key field are ignored. If this potential value is greater than the value of the warning count, a warning screen like the one in Figure 8 is displayed. If the returned value is less than or equal to the warning count value, the WUI view is displayed in the usual way
Clicking Refresh drives a new request. This allows you to alter the primary key field, which is included in the Warning count screen, to test a new filter value in order to produce a smaller set of results. Any other filters remain in place from the original request. If the set of results returned is not below the warning count limit, the warning count screen is redisplayed with the original warning count message. If the size is below the warning count limit, the warning count screen is redisplayed.
Clicking OK at the bottom of the screen performs the current request regardless of the number of results to be returned.
Clicking Cancel is the equivalent of pressing the back link on the browser; the previous screen is redisplayed.