4.4.1 Specify the New Function's Details

When the option to create a new process definition has been chosen from the process control menu the Create New Process Definition screen is displayed. It requests that the name, description and other basic details of the process to be created are specified:


 CRTPROCES             Create New Process Definition                   


 New process name  . . . . .                                   

 Description . . . . . . . .                                         


 Copy from process . . . . .                                           


 Initial public access . . . NORMAL     NORMAL, ALL, NONE              

 Anticipated usage . . . . . LIGHT      HEAVY, LIGHT                   

 Process/menu style  . . . . SAA/CUA R  SAA/CUA, ACT/BAR,              

                                        CURSOR, NUMBER, FUNCTION       


 Exit/System funct key . . .  1    <---                                

 Menu          "    "  . . .  2        :                               

 Messages      "    "  . . .  7        :   These details do not appear 

 Add           "    "  . . .  9        :   in full SAA/CUA systems.    

 Change        "    "  . . . 10        :                               

 Delete        "    "  . . . 11    <---                                



 Fnn=Help  Fnn=Exit  Fnn=Cancel  Fnn=Messages                          



After details requested by this screen have been supplied the process definition menu will be displayed. This allows the specification of the various components of the process definition (i.e. functions required in the process, special entries on the menu, parameters, etc). The specification of these components is described in the following sections.

Input Options

New Process Name

Specifies the name by which the new process is to be known. Must be a valid object name. Refer to Valid Names on the IBM i in Common Input Options. Maximum length for a process name is 10 characters. Name specified must be unique within entire LANSA system. It is recommended that a naming standard be developed for process names.


Specifies the description to be associated with the process. A brief description must be specified for every process created. The description aids other users of this process in identifying what it can be used for. See selecting required processes earlier in this chapter.

Copy from Process

Optionally specifies an existing process that is to be copied when creating this new process. This facility is useful when a process is to be changed. It can be copied to a new name, changed and tested without any disruption to users. A new process that is copied from an existing process is identical to the copied process except for details that are specified on this screen (i.e. name, description, etc).

Initial Public Access

Specifies what access other system users are to be given to the process initially. The access to the process can be changed at any time later using the option available on the housekeeping menu Mandatory. Pre-filled to NORMAL. Allowable values are:


Other users can use (execute) this process but they cannot modify its definition in any way.


Other users can use this process and can modify or even delete its definition.


Other users cannot use this process, nor can they modify its definition in any way.

Anticipated Usage

Specifies what amount of usage of the process is anticipated. This value can be changed later (see miscellaneous process details). Mandatory field. Pre-filled to LIGHT. Allowable values are:


Anticipated usage is LIGHT. The process will not be used repeatedly and continuously. Most processes are considered to be LIGHT usage.


Anticipated usage is heavy. The process will be used repeatedly and continuously. This option is normally only used in repetitive data entry applications.

In technical terms this value indicates whether or not the RPG programs created for the functions in this process should set on the LR (last record) indicator and close all files when terminating.

This value can be changed dynamically (without having to recompile any programs) so it may be worthwhile experimenting with it to modify system performance/throughput.

Process/Menu Style

Specifies the "style" of the process that is to be created. Pre-filled to SAA/CUA in an SAA/CUA partition, otherwise it is pre-filled to CURSOR. Allowable values are:


All menus and screen formats used by this process and any of its associated functions are to conform to the SAA (Systems Application Architecture) and/or CUA (Common User Access) standards defined for the partition in which the process is being defined. Refer to Partition Definitions in SAA/CUA Implementation in the LANSA Application Design Guide for more details of what the SAA/CUA standards are for a partition and how they apply.


The process is to act as an "Action bar" as defined by the CUA (Common User Access) standards defined by IBM and for this partition. To use this option these prerequisites must be satisfied:

- The current partition must be SAA/CUA enabled.

- You must be totally committed to the CUA 1989 standard for the "look" and "feel" of your application software.

Please read all relevant information in the LANSA Application Design Guide and in the IBM supplied CUA 1989 Basic Interface Design Guide.

Note: The following list of menu styles are now considered to be obsolete and their use is not recommended for new systems. They are supplied purely to allow compatibility with existing systems.


Entries are to be selected from the process menu by positioning the screen cursor on the same line as the entry.


Each entry on the menu is to be assigned a number. An entry is selected by entering the number associated with the entry into a field at the bottom of the screen. This is the "traditional" style of menu and is the most commonly used in other IBM i application systems.


Entries on the menu are to be displayed with their associated function name. An entry is selected by entering the name of the associated function into a field at the bottom of the screen. This style of menu processing is called "next function" processing and allows the users to go from function to function without having to return to the process menu. Refer to the 4.18 Function Control Table for more details.

Exit Function Key ........ Delete Function Key

Specifies the assignment of function keys to functions within this process. The pre-filled values are the installation standards and correspond to the function key assignments within LANSA itself.

This information only appears on the screen when creating a new process in a non-SAA/CUA partition, or when specifically creating a non-SAA/CUA process. In an SAA/CUA style process all function key assignments exactly follow those defined for the associated partition.

If desired change the function key number assigned to the function. Function key number specified for any of the functions must be in the range 1 to 24. The same function key cannot be assigned to more than one function.

Function key assignments can be changed dynamically (without having to recompile any programs). Refer to 4.23 Miscellaneous Process Details for a description of how function key assignments can be changed.