When you enter data you can:
- Choose an item from a selection list. For example you could select
ENABLED or DISABLED from a selection list of file status values.
- Type a value into an entry box.
When you are modifying attributes or filtering data, you should
be aware of the following conventions governing the entry of data
into a Web User Interface field.
- Character values
- A character value is represented directly but you should note
the following points:
- Fields marked
with the icon
are case sensitive, and
therefore the values for these fields are also case sensitive. For
example, in a case sensitive field transaction IDs PAY1, Pay1, and
pay1 all represent different transactions.
- You may use generic characters in filters. See Selection criteria.
- Special characters, that is quotes and non-printable characters,
should be handled as follows:
- If the character string includes a single quote, you should enclose
the string in single quotes and repeat the character like this:
'Transaction for ''Payroll'' Application'
- Character fields containing non-printable characters should be
typed in using hexadecimal notation enclosed in single quotes and
followed by the character X. For example:
'DDFF0400DDFF0400DDFF0400'X
- Non-printable characters should be separated from printable segments
of a string using a plus sign, '+'. For example:
'HI'+'0000'X+'THERE'
This
does not apply to quotes.
- If a non-printable segment contains a generic character such as
an asterisk or plus sign, the character can be entered directly. For
example:
'00*'X is equivalent to '005C'X and
'00+00'X is equivalent to '004E00'X
- Trailing spaces are removed. If the string starts or ends with
a significant space, you should enclose the string in single quotes.
- CVDA or EYUDA values
- Type in the value. These values are not case sensitive and can
be typed in any combination of upper and lower case.
- Date
- Type in the date using the format and date separator configured
for your Web User Interface server. The format and date separator
are defined using the DATEFORMAT and DATESEPARATOR Web User Interface
server initialization parameters, respectively. For information about
the DATEFORMAT and DATESEPARATOR parameters see CICS® Transaction Server for z/OS® Installation Guide.
Notes:
- Leading zeroes may be used but are optional.
- All date elements must be specified that is, day, month, and year.
- If the 2-digit year format is specified on the DATEFORMAT
parameter, the 2-digit input will be assumed to range between
1980 and 2079, inclusive.
- Time
- Type in the time using the time separator and decimal separator
configured for your Web User Interface server. The time and decimal
separators are defined using the TIMESEPARATOR and DECIMALSEPARATOR
Web User Interface server initialization parameters, respectively.
For information about the TIMESEPARATOR and DECIMALSEPARATOR parameters
see CICS Transaction Server for z/OS Installation Guide.
Notes:
- Leading zeroes may be used but are optional.
- Missing fields are assumed to be zero. For example, "9" means
"9:00:00".
- Numbers
- Type in the required number in one of the following formats:
- As a decimal integer value. For example, 100000 would be displayed
as 100000.
- As a decimal integer value , using the thousand separator configured
for the server. If thousand separators are used they must be exactly
three digits apart. For example, 100000 would be displayed as 100,000.
This
format is applicable for fullword attributes only.
- As a decimal value to one or three decimal places, using
the decimal separator configured for the server. For example, 100000
would be displayed as 100000.0 to one decimal place and 100000.000
to three decimal places.
- As a decimal value to one or three decimal places, using the decimal
separator and thousand separator configured for the server. If thousand
separators are used they must be exactly three digits apart. For example,
100000 would be displayed as 100,000.0 to one decimal place and 100,000.000
to three decimal places.
This format is applicable for fullword
attributes only.
- Using a suffix such that the displayed integer will be the smallest
non-zero value and the thousand separator configured for the server.
Kilobytes, megabytes, and gigabytes are supported. For example, 100000
would be displayed as 98KB.
This format is applicable for fullword
attributes only.
- As a rounded value to one decimal place using the decimal separator
configured for the server. Kilobytes, megabytes, and gigabytes are
supported. For example, 100000 would be displayed as 97.7KB.
This
format is applicable for fullword attributes only.
- As a rounded value to three decimal places using the decimal separator
configured for the server. Kilobytes, megabytes, and gigabytes are
supported. For example, 100000 would be displayed as 97.656KB.
This
format is applicable for fullword attributes only.
- Hexadecimal fields
- There are two ways to deal with hexadecimal strings.
- Use the same method as used for non-printable characters in character
strings
- If the first character is a single quote the field is displayed
as a character string otherwise it is displayed in hexadecimal format.
See Table 5 for examples of generic characters and
their implications in character and hexadecimal filters.
[[ Contents Previous Page | Next Page Index ]]