You are here: LANSA for i User Guide > 9. Developer Services > 9.11 Developer Services Configuration > 9.11.3 User Defined Send a Developer Message Program

9.11.3 User Defined Send a Developer Message Program

The user defined "send a developer message" program is used to send developer messages from within the "Work with Developer Messages" facility and the "Import Developer Messages" job.

The default program provided with the LANSA system to send developer messages is defined in the extended information data area DC@A07 and is called "DC@P9102", however the user has the option to change the default program to the name of his/her own "send a developer message" program.

To enable a user defined send developer message program to be invoked these steps must be taken:

Step 1

Change the extended information data area DC@A07 by inserting the name of the user defined "send developer message" program into positions 151 to 160, using the following command:

CHGDTAARA DTAARA(DC@A07 (151 10)) 

          VALUE('AAAAAAAAAA')

Replace 'AAAAAAAAAA' with the user defined send a developer message program name. Use UPPERCASE characters only.

Step 2

The user defined send developer message program must be set up to receive 19 parameters which are:

Parameter Number

Type

Length

Description

1

A

25

Message Identifier - is the unique identifier of the developer message.

2

A

10

Created by User - is the user/group profile name of the user who created the developer message.

3

A

8

Created on date - is the date when the developer message was created.

*Note: "created on date" will be in system date format and separated by the system date separator character.

4

A

6

Created at time - is the time when the developer message was created.

5

A

10

Created by Job Name - the name of the job where the developer message was created.

6

A

6

Created by Job Number - the number of job where the developer message was created.

7

A

20

Subject - is the brief description which relates to the developer message.

8

A

10

User to receive message - is the user/ group profile name of the user who the developer message should be "sent to".

9

A

3

Category code - is the category of this developer message.

10

A

15

Category code description - is the description of the category for the developer message.

11

A

1

Category code send flag - indicates whether the developer message should be sent on creation.

Values "Y" = Send developer message "N" = Do not send developer message

12

A

1

Category code notify flag - indicates whether the user should be notified of the developer message when accessing the object assigned to the message.

Values "Y" = Notify user
"N" = Do not notify user

13

A

1

Perm/Temp flag - indicates whether the developer message is permanent or temporary.

Values "P" = Permanent developer message
"T" = Temporary developer message

14

A

20

Perm/Temp Narrative - is a brief description relating to the value of the Perm/Temp flag.

15

A

8

Object/Message type - is the type of message or object for which the developer message relates to.

16

A

10

Object name - is the name of the object for which the developer message relates to.

17

A

10

Extension - is the object extension name of the object for which the developer message relates to.

18

A

varies

Message Text - contains the complete message text for the developer message.

19

A

1

Return code - indicates whether the developer message was sent successfully.

Values "Y" = Send message successful
"N" = Send message failed

 

Tip

The default "send a developer message" program "DC@P9102" receives all the message details and message text for a developer message and sends a standard format message to the user ("To user") the message is intended for, however it is possible to achieve a similar result as "DC@P9102" by designing and implementing your own "send a developer message" program to perform a much more specific purpose such as: