Generating and Compiling › Implementing › Generating an Access Path

Generating an Access Path

You must generate and compile the source members for your access paths before you can run your application. The following steps provide you with instructions to generate your access path.

1. Go to the Services Menu. At the Edit Database Relations panel, press F17.

   The Display Services Menu appears.

2. Select access paths. Type 8 at the bottom of the screen and press Enter.

   The Display All Access Paths panel appears with a list of all of the access paths in your model.

3. Generate the access path. Type J next to each of the access paths you want to generate and press Enter.

   The Display All Access Paths panel reappears with messages at the bottom of the panel that say the source generation requests have been accepted.

   Note: Selecting either J for batch generation or G for interactive generation generates your access paths. However, selecting G has an impact on system performance. Generating interactively negatively impacts other interactive users.

4. Press F3 to return to the Services Menu panel.

Note: An alternative to this procedure is to use option 14 (generate in batch) or 15 (generate interactively) from the Edit Model Object List panel.

Limitation:

When you take the G / J option to generate the access paths from the Display All Access Paths panel or take the G / J option to generate the access paths from the Edit File Details panel or take option 14 / 15 from the Edit Model Object List panel against a *DDL-based access path and the access path has either of the four DDL limitations, the generation is prevented. The access path source is not generated and no entry is added to the job list.

• The current implementation of the DDL generation mode is not valid for the following cases:
  • Access paths that have virtual fields
  • SPN access path
  • QRY access path
  • Multi-member files

  Workaround for Virtual Fields, SPN, and QRY Access Paths: If the earlier generation mode is *DDS, revert to it and regenerate the access path. You need not regenerate the functions that use this access path. If you want to have an SQL type database, regenerate the access path using *SQL generation mode. The functions using this access path must be regenerated.

  Workaround for Multi-Member Files: If you want to have more than one member for the access paths, revert to *DDS generation mode.

Note: If you want to change an access path, which is previously defined as *DDS with a MAXMBR compiler override, to *DDL, you must revert to *DDS generation mode and must remove the compiler override, and then change back to *DDL generation mode.

For more information:

• On the Edit Model Object List panel, see the Editing Model Object Lists section in the "Managing Model Objects" chapter of Generating and Implementing Applications.
• On the following topics, see Generating and Implementing Applications:
  • Generating Request Panels/Displays
  • Generating Access Paths
  • Changing Generation Mode
  • Verifying Results
  • Checking Code Generation Errors
  • Identifying Common Errors