You can set the Access Method’ option on the Edit Access Path Details panel to specify how data is to be accessed for a specific access path. Specify G to access data using a view; specify T to access data directly from the table; M uses the YDBFACC model value.
EDIT ACCESS PATH DETAILS SYMDL File name . . . . . . . . : Customer Attritue . : REF Access path name. . . . . : Retrieval index Type . . . : RTV Unique or duplicate order : U (U-Unique, F-FIFO, L-LIFO, C-FCFO, ‘ ‘-Undefined) Index maintenance option : I (I-IMMED, D-DLY, R-REBLD) Alternate collating table : Allow select/omit . . . . : (S-Static, D-Dynamic, ‘ ‘None) Generation mode . . . . . : S (M-MDLVAL, D-DDS, S-SQL, L-DDL) Source member name. . . . : UUADREL1 Source member text. . . . : Customer Retrieval index Data access method. . . . : T (M-MDLVAL, G-DBFGEN, T-TABLE) Format GEN Format text Associated ? Seq name pfx (Based on file) Update access path 1 FADREA0 AD Customer Update index SEL: Z-Entries, R-Relations, S-Select/omit, A-Assoc.acps, T-Trim, V-Virtualize F3=Exit F7=Auxiliaries F8=Change name F20=Narrative.
Only functions in which the generation mode is SQL/DDL use this access path option.
Note: If you specify *TABLE as the data access method, be sure that the access path does not contain a join; in other words, be sure it contains no virtual fields. Otherwise, either compile or run time errors may occur.
When you specify direct table access, no SQL DDL is generated to create the view. As a result, you can use this feature to suppress the view and generate SQL DDL for an index only.
Note: Current implementation of DDL, allows database access method of *TABLE only.
|
Copyright © 2014 CA.
All rights reserved.
|
|