IBM SC41-5210-04 manual Running a default query in Query for iSeries

For example, the language sequence is used to initialize the Define Collating Sequence display if there is no previously defined sequence for the query and the default sequence from the query-user’s profile is converted with warnings about the use of substitution characters.

Query for iSeries warns you on the Select Collating Sequence display when the sequence previously defined for this query cannot be converted. You can find out why the language sequence or a user-defined default sequence was not used by pressing F15 (Language sequence) or F16 (Use default) on the Define Collating Sequence display.

Getting a list of formats or members with text in Query for iSeries

If a member or format-text description cannot be converted to the job CCSID, blanks are shown.

If the descriptive text is not displayed in a list display, press F11.

Saving a Query for iSeries query definition

Conversion may be required when an access plan is built to be saved with the query. This can cause previously undetected compatibility problems, and you are asked to confirm saving the query definition with errors.

Running a Query for iSeries query

Each position of every value that cannot be converted to the job or document CCSID is printed or displayed as a plus sign (+). Each position of a text string that cannot be converted is printed or displayed as a dot (.). An edit word that cannot be converted is ignored (edit code J is used instead). This happens regardless of the method used to run the query.

Note: The job CCSID is the CCSID of the job. It can be changed by the command CHGJOB CCSID().

Neither data nor text is converted when the output is directed to an existing file. If a field receiving data has a different CCSID, output processing stops with a diagnostic before any records are added.

If you have done an override to a database file selected for input, Query for iSeries uses the new file information, including the CCSID markings. This can cause the same kind of errors that would be diagnosed at definition time.

If you do nothing to cause the access plan to be rebuilt (see “Access plans in Query for iSeries” on page 232), you can get errors if a file is replaced with a file in a format that requires no level check, but has different CCSID characteristics.

Running a default query in Query for iSeries

When you run the default query for a file, the job or document CCSID and other conversions can fail. For example, the file could be a logical file involving concatenation of fields with different CCSIDs or you may be using a query profile with an incompatible collating sequence default.

Selecting records at run time in Query for iSeries

You can do run-time record selection if the process (job) CCSID and the query definition CCSID are the same, if either is marked with a CCSID of 65535 (do not convert), or if the query definition is not marked.

Table 12 on page 252 shows when record selections can be changed at run time and how the constants are treated.

Appendix E. Coded character set identifiers (CCSIDs) in Query for iSeries 251