Setting Default Options for Your Functions › Model Values Used in Building Functions › YSNDMSG

YSNDMSG

For new functions, the Send Error Message (YSNDMSG) model value specifies whether to send an error message for only the first error found or for every error. In either case, outstanding messages clear when the end user presses Enter. The shipped default value is *NO, do not send all error messages; send only the first error message.

YSQLCOL

The Generate SQL Collection/Library Name (YSQLCOL) model value specifies whether a hard coded SQL Collection/Library name should be generated for tables, indexes and views. The possible values are *YES and *NO. The shipped default is *YES.

If YSQLCOL is specified as *YES, the SQL Collection/Library specified for the YSQLLIB model value is generated into the tables, indexes and views, by default, as is the case now. Subsequently when YEXCSQL is executed to create tables, indexes and views, they are created into the hard coded SQL Collection/Library. If YSQLCOL is specified as *NO, the SQL Collection/Library specified for the YSQLLIB model value is not generated into the tables, indexes and views. However, when YEXCSQL is executed subsequently, the tables, indexes and views are generated into the SQL Collection/Library specified for the YSQLLIB model value.

Note: If YSQLCOL is set to *NO and the access paths are generated, another change that can seen in the source, apart from the absence of hard coded SQL collection/Library name is, the previously generated Z* line "Z* YEXCSQL NAMING(*SQL)" is now generated as "Z* YEXCSQL NAMING(*SYS)".

YSQLFMT

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.