If you implement SQL, each model library list and associated job description must reference an SQL collection. Parameter SQLLIB creates and sets the name of the SQL collection.
If you accept the default option *DBFGEN, CA 2E looks at the value for the DBFGEN parameter and, if it is set to *SQL, creates the collection and builds a name from the model library name according to the following rules:
If you implement DDL, each model library list and associated job description must reference an SQL collection. Parameter SQLLIB creates and sets the name of the SQL collection.
If you accept the default option *DBFGEN, CA 2E looks at the value for the DBFGEN parameter and, if it is set to *DDL, creates the collection and builds a name from the model library name according to the following rules:
Note: Irrespective of the value of the YSQLFMT model value and if the generation mode is *DDL, the RCDFMT keyword is generated.
Limitations:
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.
|
Copyright © 2014 CA.
All rights reserved.
|
|