You have to know the name of the member. CREATE ALIAS on the PF to the specific member name. Then in SQL just SELECT FROM ALIAS. =========================================================== OVRDBF is appropriate for individual jobs. The override is temporary and does not affect other jobs. CREATE ALIAS creates a permanent "override" to a specific member. An ALIAS would be created for each member; each ALIAS would have a unique name within the schema; and all jobs would use the same ALIAS for the same member. (You could create multiple ALIASes over the same member if you wanted to.) One is temporary and limited in scope. The other is permanent (until you DROP ALIAS) and available system-wide. SQL does not have a concept for "member". In general, if you're going to use SQL, then don't use members. OVRDBF and CREATE ALIAS provide two methods to use when member access is required. Note that "partitioned" TABLEs may provide a form of "member" access for new TABLEs. The DB2 Multisystem product enables partitioned TABLEs on AS/400s, I think as of V5R3. Tom rajgoaj: The SQL syntax for this would be CREATE ALIAS aliasname FOR tablename(membername)

You have to know the name of the member. CREATE ALIAS on the PF to the specific member name. Then in SQL just SELECT FROM ALIAS. =========================================================== OVRDBF is appropriate for individual jobs. The override is temporary and does not affect other jobs. CREATE ALIAS creates a permanent "override" to a specific member. An ALIAS would be created for each member; each ALIAS would have a unique name within the schema; and all jobs would use the same ALIAS for the same member. (You could create multiple ALIASes over the same member if you wanted to.) One is temporary and limited in scope. The other is permanent (until you DROP ALIAS) and available system-wide. SQL does not have a concept for "member". In general, if you're going to use SQL, then don't use members. OVRDBF and CREATE ALIAS provide two methods to use when member access is required. Note that "partitioned" TABLEs may provide a form of "member" access for new TABLEs. The DB2 Multisystem product enables partitioned TABLEs on AS/400s, I think as of V5R3. Tom rajgoaj: The SQL syntax for this would be CREATE ALIAS aliasname FOR tablename(membername)