IBM SC41-5210-04 manual Conceptual Differences, Operational Differences

Appendix A. Differences between Query for iSeries and Query/36

This appendix describes the differences between Query for iSeries and Query/36. The Query for iSeries differences described in this appendix are limited to the differences that may cause you some inconvenience if you did not know about them before working with Query for iSeries. This appendix defines these differences as:

vConceptual

vOperational

vCommand

vMigration

Conceptual Differences

The following list identifies the concepts that are different on the iSeries system along with an explanation of the differences as they apply to the listed concepts:

Subroutines

Queries were subroutine members in a library on System/36. On the iSeries system, queries are a unique object type called a query definition (*QRYDFN) stored within a library. This change is important to understand since some System/36 commands that work with subroutines may not work on the iSeries system.

Files Files are stored in libraries on the iSeries system, so a library name needs to be specified for Query for iSeries in order for a file to be located. System/36 did not store files in libraries.

Operational Differences

The following list identifies the operations that are different on the iSeries system along with an explanation of the differences as they apply to each listed item:

Linked files

If an IDDU-defined file that is migrated from System/36 is not linked, you can still run a query against the file. However, the file will show as a one-field file (that is, if you were to run a default query against the file, the file would appear as though all of the fields were run together).

File IDs

In Query/36, file IDs are one of the letters A through E. If a Query/36 query is migrated to the iSeries system, all file IDs for files selected for that query remain the same. All files selected for a query on Query for iSeries have a 1- to 3-character file ID that you specify, or it defaults to Tnn, where nn is in the range of 01 to 32.

Joining files

In Query/36, you can join up to five files, and only one type of file join (matched records) is allowed. In Query for iSeries, you can join up to 32 files, and three types of file join are allowed:

vMatched records

vMatched records with primary file

vUnmatched records with primary file

In Query/36, the maximum combined length of character fields used to join files is 120; in Query for iSeries, the maximum is 2000.

Report breaks

Report breaks for printed requests may be different in spacing. In Query/36, the report skips one line for report breaks unless it is defined to skip to a new page or defined to use double or triple

© Copyright IBM Corp. 2000, 2002 195