9 4 4 Create a Developer Message

LANSA for i

9.4.4 Create a Developer Message

Create a Developer Message allows you to create a new developer message.

This example shows what may result when the "Create a Developer Message" option has been chosen from the "Work with Developer Messages" screen:

 

 

                      Create a Developer Message                     

   Message ID : 012345670000001DC@PGMLIB                             

   From user  : QOTHPRDOWN  Date/Time : 27/07/91 12:22:33            

   Subject . . . . . ____________________                           

   To user . . . . . __________  name, *ALLUSR                       

   Category  . . . . ___                                             

   Perm/Temp . . . . _  P, T                                         

   Type  . . . . . . ________  FIELD, FILE, FUNCTION, PROCESS, SYSTEM  

   Object Name . . . __________ +                                    

     Extension . . . __________ +                                    

   Message Text                                                      

  _________________________________________________________ 

  _________________________________________________________ 

  _________________________________________________________ 

                                                             More..  

  Fnn=Help  Fnn=Prompt  Fnn=Cancel                                   

 

 

 

 

Default Values when Creating a New Developer Message

These default values are automatically set by the system when a new developer message has been created:

Message Identifier

Is the unique identifier of the developer message. The message identifier is  25 characters containing 3 items, as in this example:

012345670000001DC@PGMLIB

where

  • the first 8 characters represent the IBM i system value QSRLNBR of the machine where the message originated.
  • the next 7 characters contain the next message number to be allocated from the DC@A09 data area.
  • the last 10 characters contain the LANSA program library name.

From User

Is the user profile name of the current user who has created the new developer message.

Date/Time

Is the date and time at which the new developer message was created.

Input Options When Creating a New Developer Message

These input options apply when creating a new developer message:

Subject

Is the brief description which relates to the developer message.

To User

Is the user profile name of the user to which the developer message should be "sent to" or marked as "for the attention of". Valid entries are as follows:

  • A user profile name
  • A group profile name
  • "*ALLUSR" - all users

The "To User" value will be validated by the user defined "User Profile validation" program which determines whether the user or group profile is valid.

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

Category

Is the category of the developer message. The category must be a valid category code from the category code table defined within the extended information data area DC@A07.

Refer to 9.11 Developer Services Configuration later in this chapter for more information on how to define a user defined "Category Code" table in the extended definition data area DC@A07.

If the category code's "Send Message Flag" is set to "Y" then the message will be sent to the user nominated in "To User" field by the user defined "Send Developer Message" program which is also specified in the extended information data area DC@A07.

If the category code's "Notify User Flag" is set to "Y" then the user will be notified of the developer message each time the object is accessed.

Perm/Temp

Is the flag that indicates whether the developer message is permanent or temporary. Valid entries are:

"P"= Permanent developer message

"T"= Temporary developer message

If a developer message is flagged as permanent, then it will remain on the system until it has been selected for deletion.

If a developer message is flagged as temporary, it will remain on the system until it has been purged, unless the developer message is changed to a permanent developer message.

Type

Is the type of message or object for which the developer message relates to. Valid entries are:

FIELD

Message relates to a specific Field

FILE

Message relates to a specific File

FUNCTION

Message relates to a specific Function

PROCESS

Message relates to a specific Process

SYSTEM

Message is a System-wide developer message which is intended to be sent from one user to another user/s.

 

This field will be defaulted to the object type of the last object that was worked with.

Object Name

Is the name of the object for which the developer message relates to. If you wish to perform a search for an object then ensure the "Type" field contains a valid object type (FIELD, FILE, FUNCTION or PROCESS) and 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 object.

This field must be blank if the message type is set to "SYSTEM".

This field will be defaulted to the object name of the last object that was worked with.

Extension

Is the object extension name of the object for which the developer message relates to.

This field must contain an entry if the message type is set to "FILE" (file library name) or "FUNCTION" (process name in which the function resides).

This field must be blank if the message type is set to "SYSTEM", "FIELD" or "PROCESS".

This field will be defaulted to the object extension of the last object that was worked with.

Message Text

Is the message text for the developer message. Up to 200 lines of message text may be entered.

When you have completed entering the developer message details, you will be returned to the "Work with Developer Messages" screen.