Filter
Top Products
spacing. In Query for iSeries, the report skips an extra line for report breaks unless it is defined to
skip to a new page. This means the first detail line after a control break has an extra blank line
printed between it and the last detail line before the break.
Character fields
In Query/36, character fields that were defined in IDDU with a length greater than 256 bytes were
truncated at 256 bytes. Query for iSeries supports character fields up to 32 766 bytes in length.
Record selection tests that use these fields will now use the entire field for the comparisons
instead of just the first 256 bytes.
Sort sequence
If no sorting was specified in the query, the order in which records are printed in the report may be
different than the order they were printed in Query/36. Also, if sorting is specified but the field(s)
being sorted contain the same value in multiple records, the order in which these records appear
may be different from Query/36.
Result fields
Result fields that use multiplication or division operations in Query for iSeries may have a slightly
different result in the farthest right decimal positions as compared to Query/36. This occurs
because multiplication and division are carried out to a much greater precision in Query for
iSeries.
Calculation results
The results of multiplication and division operations are truncated according to the field length for
queries that are migrated from System/36. For queries defined using Query for iSeries, you can
specify that the results of multiplication and division operations be either truncated or rounded.
Output to file
When the output of a query is being sent to a file, Query for iSeries builds the file as a database
file with a definition. It is no longer necessary to build the IDDU definition and link that definition to
the file, as was needed on Query/36, unless the QRY or QRYRUN procedure was used to run the
query.
Summary-only output
When sending summary-only output to a file using Query for iSeries, each report break field
whose break level number is greater than the break level that this record was created for will
contain blanks for character fields and zeros for numeric fields. On System/36, these fields
contained binary zeros. The iSeries system operates this way to avoid putting incorrect data into
numeric fields.
Library default
The library default for the input file on the Specify File Selections display and the output file on the
Define Database File Output display is the library that was set up at configuration time for the
System/36 environment files.
Decimal data
In Query/36, decimal data errors were tolerated. When running a query using Query for iSeries,
decimal data errors are tolerated depending on the value specified on the Processing Options
display. For default queries and queries without the specified processing option value, Query
tolerates decimal data errors in the System/36 environment and does not tolerate them in the
OS/400 environment. See Chapter 14, “Specifying Query for iSeries processing options”, for more
information.
Message response
On System/36, a user could have an automatic response file set up to handle Query/36
messages. An automatic response file of this type does not handle Query for iSeries messages.
Printing
Printing with spooling set to N=NO does not operate the same on the OS/400 as it did on the
System/36. For more information see the Printer Device Programming book.
196 Query for iSeries Use V5R2