The history file is large so we would prefer to avoid creating a third file and copying the records from each of the first two files into it.
For example, if your transaction file is named TRANSFILE and your archived file is HISTTRANS, the following SQL statement would create the appropriate view:
CREATE VIEW view all_trans AS
(SELECT * from histtrans
SELECT * FROM transfile)
This view can be used for both native record level access and SQL access. Bear in mind that SQL views are equivalent to non-keyed logical files.
Dig Deeper on iSeries SQL commands and statements
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading