You are here: LANSA for i User Guide > 9. Developer Services > 9.8 Export Developer Messages > 9.8.2 Steps to Perform after Exporting Developer Messages

9.8.2 Steps to Perform after Exporting Developer Messages

These examples provide some guidelines on what to do with the export developer messages files when the EXPORTMSGS job has completed normally:

Example 1

If the export developer message files are to be saved on a tape or diskette device, perform the following IBM i Control Language command:

SAVOBJ OBJ(AAAAAAAAAA BBBBBBBBBB)

       LIB(CCCCCCCCCC)

       DEV(DDDDDDDDDD) OBJTYPE(*FILE)

replacing:

'AAAAAAAAAA' with the name of the file which contains the exported developer message header details.

'BBBBBBBBBB' with the name of the file which contains the exported developer message text details.

'CCCCCCCCCC' with the name of the library where the exported developer message files have been created.

'DDDDDDDDDD' with the name of the device where the exported developer message files will be saved.

Example 2

If the export developer message files are to be sent to another system using SNADS, perform the following IBM i Control Language command:

SNDNETF FILE(BBBBBBBBBB/AAAAAAAAAA) 

        TOUSRID((CCCCCCCC DDDDDDDD))

replacing:

'AAAAAAAAAA' with the name of the file which contains the exported developer message header details.

'BBBBBBBBBB' with the name of the library where the exported developer message header file is resident.

'CCCCCCCC' and 'DDDDDDDD' with the two-part user ID of one or more users to whom the exported developer message header file is being sent.

then:

SNDNETF FILE(BBBBBBBBBB/AAAAAAAAAA)

        TOUSRID((CCCCCCCC DDDDDDDD))

replacing:

'AAAAAAAAAA' with the name of the file which contains the exported developer message text details.

'BBBBBBBBBB' with the name of the library where the exported developer message text file is resident.

'CCCCCCCC' and 'DDDDDDDD' with the two-part user ID of one or more users to whom the exported developer message text file is being sent.

The complete EXPORTMSGS procedure can be performed manually, but it is recommended that this procedure be executed within an IBM i Control Language program.

If LANSA/MESSAGES is being run in a multi-machine environment it is recommended that the EXPORTMSGS job should be executed on a daily basis as part of a start of day/day end procedure.