9 4 1 Build List of Developer Messages

You are here:

9.4.1 Build List of Developer Messages

Build a list of Developer Messages allows you to specify the type of developer messages you wish to appear on the "Work with Developer Messages" menu, whether it be all the developer messages relating to a user (Sent to or Sent from), a specific object (Field, File, Function or Process) or "SYSTEM" developer messages.

The "Build List of Developer Messages" facility will be invoked when the "Work with Developer Messages" option has been selected from the "Developer Services" menu and when the "Build list" Function key has been pressed on the "Work with Developer Messages" menu.

The example below shows what may result when the "Build List of Developer Messages" facility has been invoked:

Build List of Developer Messages

Specify search criteria and press Enter .....

Sent by User . . . __________ name, *ALLUSR

Sent to User . . . __________ name, *ALLUSR

For FIELD . . . . __________ +

For FILE . . . . . __________ +

For PROCESS . . . __________ +

AND/OR

For FUNCTION . . . _______ +

For SYSTEM . . . . YES YES, NO

Fnn=Help Fnn=Prompt Fnn=Create Fnn=Cancel

Only one search criterion may be specified, upon which a list of all developer messages matching the specified search criteria will be generated for use in the "Work with Developer Messages" menu.

Working from this screen you can build a developer message list by specifying one of the following:

Sent by User must be a valid user/group profile name or "*ALLUSR".

Sent to User must be a valid user/group profile name or "*ALLUSR".

The "Sent by User" and the "Sent to User" values will be validated by the user defined "User Profile validation" program specified in the extended information data area DC@A07.

Refer to 9.11 Developer Services Configuration for more information on how to define a user defined "User Profile Validation" program in the extended definition data area DC@A07.

For FIELD must be a valid field name that exists within the LANSA data dictionary. If you wish to perform a search for a field name then press the Prompt function key, a pop-up window will then be displayed providing you with the option to search for and select the required field name. If the current/last object being worked with is a/was a field, then the "For FIELD" field will be defaulted to the name of that object (field name).

For FILE must be a valid file name that exists within LANSA. If you wish to perform a search for a file name then press the Prompt function key, a pop-up window will then be displayed providing you with the option to search for and select the required file name. If the current/last object being worked with is a/was a file, then the "For FILE" field will be defaulted to the name of that object (file name).

For PROCESS must be a valid process name that exists within LANSA. If you wish to perform a search for a process name then press the Prompt function key, a pop-up window will then be displayed providing you with the option to search for and select the required process name. If the current/last object being worked with is a/was a process, then the "For PROCESS" field will be defaulted to the name of that object (process name).

For FUNCTION must be a valid function name that exists within LANSA, if a Process name has also been specified then the function name must exist within the specified process. If you wish to perform a search for a function name then press the Prompt function key, a pop-up window will then be displayed providing you with the option to search for and select the required function name. If the current/last object being worked with is a/was a function, then the "For FUNCTION" field will be defaulted to the name of that object (function name) and the "For PROCESS" field will be defaulted to the extended name of that object (process name).

For SYSTEM must be either "YES" or "NO". If no objects have been selected to work with in this session of LANSA, then the "For SYSTEM" field will be defaulted to "YES", if objects have been worked with the "For SYSTEM" field will be defaulted to "NO".