Kinds of Generated Files
This section includes reference information about the kind of files that are generated by Lawson.
Job and Program Logs
Log files detail the execution of jobs and programs. There are two kinds of logs:
-
The lapm.pid and lapm.pid.username (pid stands for process ID while username stands for the user's security user name) files created whenever lapm runs
-
The job log files (jobname.pid) created when the batch program runs
The directory $LAWDIR/system/joblog contains both the job logs (for batch jobs) and the lapm.pid and lapm.pid.username files (for online programs run through lapm).
The /EnvironmentDirectory/law/system/joblog directory in the IFS contains both the job logs (for batch jobs) and the lapm.pid files (for online programs run through lapm).
To find the file name of a job log for a batch job, on any of the Job Scheduler forms, select the Examine form action, select the job whose log you want to view, and press Enter. The file name appears in the upper left corner of the form.
Print Files
Print files are a report of the execution of programs.
Print File Types:
| Type | Description |
|---|---|
| .dtl | Detail file. Describes the data used in a report. |
| .prt | Left-to-right print file |
| .rtl.prt |
Right-to-left print file. Note that the .rtl.prt file type is the same as the .prt file type. However, it is converted to a right-to-left format with labels and text right-justified. This file type also includes additional language translation if bldxxfiles was used with the -l language option.
|
| .rtl.prm | Right-to-left parameters file. This file
contains the report’s parameter page in right-to-left followed by the parameters in
left-to-right enclosed by HTML tags. This file will be used by bldxxfiles and Lawson Portal
webrpt.exe routines and is not intended for user
viewing or use. |
The print file that is created is also a text file. The print file is in:
/EnvironmentDirectory/law/print/username/jobname/step#/jobnumber/formID.prt
For example, /law9/law/print/judy/empprmtrs/1/486723954/HR211.prt is the print file in the IFS for a job that has the following characteristics:
-
Job was sent by a user named Judy
-
Job is named "empprmtrs"
-
Job is the first step, perhaps the only step, in a multi-step job
-
Job has the ID of 486723954
-
Job runs Employee Listing (HR211)
Detail Files
Some reports generate a detail file, formID.dtl. It contains the information that enables the Drill Around feature for the report.
Report Map Archive Files
Report map archive files are copies of the report maps. They include a reference to the timestamp on report files, so that when you want to drill on the data in a print file or want to create a CSV file from a print file, the system has a version of the report map that matches the print file. If a report map changed when you recompiled your reports - for example, because of an application service pack - any already existing print files would use the archived report maps for Drill Around and CSV file creation. Any new print files would use the most current report map.
The report map archive files are stored in $LAWDIR/productline/rptmap/default/archive. If the folder contains report map archive files for print files that have become obsolete, you can manually delete the report map archive files for those print files. You can turn off the archiving feature by creating the ARCHIVEOFF touch file in the $LAWDIR/productline/rptmap/default/archive directory. However, if you turn off this feature and then recompile report programs, you may not be able to use the Drill Around or CSV file creation features for older print files.
Log File Entries
When Lawson processes are run, entries are made for significant events, such as error messages, or stopping and starting servers. The ladb, lajs, latm, and LAWCOMPQ servers have log files that contain entries for every significant event.
When the dbreorg utility is run, it creates entries in the file called reorg.hist.
Clean out these files on a regular basis. Delete or archive (depending on your organization's archive policies) all but the most recent entries.
Work Files
Some programs create work files that you can copy to a storage device (tape, disk, and so on), or that users can manipulate in some other way. For example, work files are commonly used as input files to specific application programs, such as a check reconciliation program.
Work files for applications are stored in directories in IFS within the directory
/EnvironmentDirectory/law/Productline/work/WorkfileDirectory
where EnvironmentDirectory is the top-level directory in the IFS for the Environment, Productline is the product line, data area, or data ID, and WorkfileDirectory is a directory name based on the name of the work file.
After the application uses these work files, you can remove them. However, you must ensure that users are finished using the work files before deletion. You will then need to delete work files manually; the Delete Job History utility (deljobhst) does not remove them.