4.1.2 Process & Function Naming

The following naming recommendations are provided for "in house" application development as opposed to vendor "package" development.

• Process should be in the format:     ooooPRnn

• Functions should be in the format:   ooooaaa

• The oooo part of the name indicates the basic or primary object that the process or function uses (based on the data model entity). For example, CUST - Customer or ORDR- Order.

• The nn portion of the process name is a sequentially assigned number within the OOOO grouping. For example, CUSTPR01 - Online Customer Maintenance, or CUSTPR02 - Batch Customer Maintenance.

• The aaa portion of the function name indicates the action to be taken on the object by functions within the process. For example, MNT- maintenance, or REP- reports (use R01, R02, R03 for multiple reports).

• Names should not contain the '#' or '@' symbol.

We strongly recommend that you enforce a set of standards for object naming at your site. For more details, refer to Processes and Functions in the LANSA Application Design Guide.

Please review the LANSA Object Names in the LANSA Technical Reference Guide.

Platform Considerations

• IBM i: A process name must be unique within the entire LANSA partition. A function name must be unique within the process it is created. It is possible to have two functions with the same name in a single partition if they are located in different processes.

• Windows: A process name must be unique within the entire LANSA system. All functions must be defined as type *DIRECT. Functions names must be unique in the partition.