The SQL Naming (YSQLVNM) model value specifies whether to use the extended SQL naming capability. The valid values are:
Use DDS names. The shipped default.
Use the names of the CA 2E objects in the model.
Use the long names of the CA 2E objects in the model along with the DDS or implementation names.
Use the long field names of the CA 2E objects in the model along with the DDS or implementation names.
Use the long table names of the CA 2E objects in the model along with the DDS or implementation names.
It is up to you when and whether to use extended SQL naming. It is anticipated that most designers will choose to convert all tables, views and indexes, including the functions built over them, as a unit; however, incremental migration is also possible with careful planning.
The Generate SQL RCDFMT clause (YSQLFMT) model value specifies whether the RCDFMT keyword must be generated for SQL tables, views, and indexes. The possible values are *NO, and *YES. The shipped default is *NO.
If YSQLFMT is specified as *NO, the record format is the same as the table, index, or view name (if YSQLVNM (*DDS) is specified) or will be generated by the system (if YSQLVNM(*SQL) is specified). If YSQLFMT is specified as *YES, the RCDFMT value is calculated using the same rules as are used when DDS files are generated.
Note: Irrespective of the value of the YSQLFMT model value and if the generation mode is *DDL, the RCDFMT keyword is generated.
Important!
If YSQLFMT is set to *YES or *NO and a DDL index is generated and created, the index is created with LVLCHK(*NO).
If YSQLFMT is set to *YES and an SQL index is generated and created, the index is created with LVLCHK(*NO).
If YSQLFMT is set to *NO and an SQL index is generated and created, the index is created with LVLCHK(*YES).
If you want to change the LVLCHK attribute of the index to LVLCHK(*YES), the model value YLVLCHK must be set to *YES, and the corresponding index-related access path must be regenerated and re-created. Upon regeneration of the access path, an additional line "Y* CHGLF LVLCHK(*YES)" is generated in the header portion, which informs YEXCSQL to create the corresponding index with LVLCHK(*YES).
Note: If YSQLFMT is set to *YES, YLVLCHK is set to *YES and RUNSQLSTM is used to create an index (SQL or DDL), the index would still be created with LVLCHK(*NO). The current functionality does not cater to the RUNSQLSTM command. Tables and Views (SQL) and Tables (DDL) are created with LVLCHK(*YES) by default, irrespective of the YSQLFMT model value. Therefore, YSQLFMT and YLVLCHK model values have no effect on tables and views regarding the LVLCHK attribute.
|
Copyright © 2014 CA.
All rights reserved.
|
|