- Text about the member *
- Data (the CCSID tag or tags are in the format definition)
Notes:
1. The CCSID of the query definition is shown on displays that show the query name, like the Define the
Query display.
2. The CCSID of the user-defined collating sequence is shown on the Define Collating Sequence display.
3. The CCSID of the character data in an output file is shown on a line above the record format in a
printed query definition if all the character-data CCSIDs match (single and mixed-byte versions of a
CCSID are considered matching).
4. The CCSIDs of the character fields in an output file are shown in a column of the record format in a
printed query definition if individual CCSIDs do not match.
5. When text parts from an input file definition, such as column headings, field text, and file definition text,
are used to create an output file definition, the CCSIDs of those parts are carried over to the output file
definition. The CCSIDs of fields are also carried over. You can use the Display File Field Description
(DSPFFD) command to determine the CCSID of fields. You can dump the file to determine the CCSID
of field text or file definition text.
6. The original CCSID of the query definition is shown in an informational message on the Define the
Query display. If this CCSID is 65535 and the CCSID shown at the top of the display differs, text and
constants in the query definition will start to be treated as though marked with the latter CCSID.
7. The original CCSID of the collating sequence used to initialize the Define Collating Sequence display is
shown in the second level text of the informational message about how the sequence was initialized. If
this CCSID is 65535 and the CCSID shown at the top of the display differs, the sequence, whether or
not you reorder it, will start to be treated as though marked with the latter CCSID.
8. Some diagnostic messages about CCSID conversion problems show the incompatible CCSIDs.
9. The CCSID of the collating sequence resolved for the current collating choices is shown in a message
at the bottom of the Select Collating Sequence display.
CCSIDs and collating sequences in Query for iSeries
Within Query for iSeries you can specify hexadecimal (the default), the language sequence, a user-defined
sequence, a translation table, or system sort sequence to specify a collating sequence. The collating
sequence is used for join tests, record selection, sorting, grouping report-breaks, and determining
minimum and maximum values. Collating sequence tables are only used for SBCS characters.
A CCSID is associated with each of the collating sequences supported by Query for iSeries. Query for
iSeries assumes that a translation table has a CCSID of 65535. A user-defined sequence has the job
CCSID of the defining user.
Note:
If you select the hexadecimal sequence or use a collating sequence with a CCSID of 65535 for
ordering marked data, the results you get may seem inconsistent. For example:
v
The value that sorts to the lowest position may not be the minimum summary value for a
displayed or printed column. This can happen because sort comparisons are done before, and
minimum comparisons after, any conversion to the job CCSID occurs.
v
The minimum and maximum values saved in summary-only output to a database file may differ
from the corresponding values in a printed or displayed report, even though the same job CCSID
is used to run the query. This happens only if values for a minimum or maximum field are
converted to the job CCSID in order to be printed or displayed.
When you save a user-defined collating sequence as the default in your Query profile, the job CCSID is
saved with it. If you choose to save the language option as your default, only the option is saved in the
profile—
not
the language sequence or its CCSID.
248
Query for iSeries Use V5R2
Summary of Contents for @server iSeries
Page 1: ...iSeries Query for iSeries Use Version 5 SC41 5210 04 ERserver ...
Page 2: ......
Page 3: ...iSeries Query for iSeries Use Version 5 SC41 5210 04 ERserver ...
Page 12: ...x Query for iSeries Use V5R2 ...
Page 14: ...2 Query for iSeries Use V5R2 ...
Page 32: ...20 Query for iSeries Use V5R2 ...
Page 38: ...26 Query for iSeries Use V5R2 ...
Page 44: ...32 Query for iSeries Use V5R2 ...
Page 116: ...104 Query for iSeries Use V5R2 ...
Page 122: ...110 Query for iSeries Use V5R2 ...
Page 146: ...134 Query for iSeries Use V5R2 ...
Page 150: ...138 Query for iSeries Use V5R2 ...
Page 174: ...162 Query for iSeries Use V5R2 ...
Page 178: ...166 Query for iSeries Use V5R2 ...
Page 196: ...184 Query for iSeries Use V5R2 ...
Page 198: ...186 Query for iSeries Use V5R2 ...
Page 204: ...192 Query for iSeries Use V5R2 ...
Page 205: ...Part 4 Appendixes Copyright IBM Corp 2000 2002 193 ...
Page 206: ...194 Query for iSeries Use V5R2 ...
Page 210: ...198 Query for iSeries Use V5R2 ...
Page 242: ...230 Query for iSeries Use V5R2 ...
Page 256: ...244 Query for iSeries Use V5R2 ...
Page 270: ...258 Query for iSeries Use V5R2 ...
Page 272: ...260 Query for iSeries Use V5R2 ...
Page 292: ...280 Query for iSeries Use V5R2 ...
Page 293: ......
Page 294: ... Printed in U S A SC41 5210 04 ...