You have to set up an alias for the member first. This gives that specific member a unique name that SQL can relate to.

<pre>
Create alias mylib/myalias for mylib/mypf (mbr)
Select * from mylib/myalias
</pre>

==================================================

Since CREATE ALIAS is a SQL statement, you might not have the authority. Or you might want or need to avoid creating permanent SQL objects in the database catalog. For me, usually it’s just easier to issue an OVRDBF MBR() command to point to the desired member before running a SQL SELECT.

It requires no SQL statement authorization. It doesn’t create a SQL object that needs to be deleted elsewhere. It has no effect on any other job. And it goes away by itself if I sign off. Further, I can issue different overrides at different times to see different members.

An ALIAS is much more appropriate, though, when you want to make a member explicitly available to everyone for an extended time.

Tom