You’re right views aren’t the same as joins.
A view contains the rules for selecting records — rules no keys (indexes)
SQL Indexes can be created on the physical files. Indexes are keys – no rules (some rules in v6r1).
If the indexes needed don’t exist SQL will create temp indexes.
SQL will analyze the request and select or make the best indexes to do the job.
SQL gives you lots of ways to get data other than joins.
When your request can return more than one record you –> must <– use a cursor.
Alternative – Native I/O still works fine, really.
SQL is often faster but not always.
Indexes are critical for performance and these can be determined with the analyzer on Navigator.
You can do your joins in views or right in the SQL.
Shop standards are important.