9.8.1 Steps Required to Export Developer Messages
The basic requirements to ensure an EXPORTMSGS job completes normally is that the library name specified in PARM03 exists and the export date specified in PARM04 is a valid date in CCYYMMDD format, the two export files specified in PARM01 and PARM02 are (re)created each time an EXPORTMSGS job is executed.
To Export Developer Messages perform the following command:
LANSA REQUEST(EXPORTMSGS) PARM01(AAAAAAAAAA)
PARM02(BBBBBBBBBB) PARM03(CCCCCCCCCC)
PARM04(CCYYMMDD)
replacing:
- 'AAAAAAAAAA' in PARM01 with the name of the file to receive the export developer message header details. Use UPPERCASE characters only.
- 'BBBBBBBBBB' in PARM02 with the name of the file to receive the export developer message text details. Use UPPERCASE characters only.
- 'CCCCCCCCCC' in PARM03 with the name of the library where the exported developer message files will be created. Use UPPERCASE characters only.
- 'CCYYMMDD' in PARM04 with the export start date, the export start date must be in CCYYMMDD format Century, Year, Month and Day). All developer messages that were first created/subsequently changed on or after the export start date will be exported.
For example, this command:
LANSA REQUEST(EXPORTMSGS) PARM01(MSGFIL1)
PARM02(MSGFIL2) PARM03(EXPLIB)
PARM04(19911231)
will result in all the developer messages that have a create date greater than or equal to "19911231" (31st of December 1991) being exported to the export developer message files "MSGFIL1" and "MSGFIL2" in library "EXPLIB".