Access Paths

Following are some suggestions for creating access path names:

When you add an extra access path, create a meaningful name. Avoid including redundant information. Where possible, indicate selection and sequence details. The name of a span file should indicate the two files the span is over. If necessary, abbreviate the file name rather than reduce other information. For example, Customers Active by Postcode, Orders US by Product.
It may be useful to set a convention that indicates where a procedure is being followed to control the implementation of joins within separate logical files.