Impact on Other Areas of the Product

Extended SQL naming affects the following areas of the product:

Impact Analysis and Change Type—Because CA 2E file and field names are used in generated DDL and DML, when you change a field name you now need to regenerate any SQL‑implemented functions and access paths that use the field. In other words, the type of change caused by changing a field name becomes *PRIVATE rather than *OBJONLY when you use extended SQL naming.
Use option 94 (Simulate *PRIVATE change) on the Display Model Object Usages panel to identify the functions and access paths you need to regenerate.
National Languages—Because names of files and fields in non-English models often contain inflections and other "invalid" characters, you might experience difficulty when using extended SQL naming.
Note: Extended SQL naming is not valid for models using DBCS (double byte character set).
DRDA Applications—Because view names are still limited to ten characters and CA 2E still uses the existing member name in the distributed configuration file table, extended SQL naming does not affect DRDA (Distributed Relational Database Architecture) Applications.