Archive for category: Articles

This article will demonstrate how to clear out a Lawson system so that you can start a completely fresh compile of the full productline.

First, open a command line utility with the Lawson environment variables set.  Then, navigate to LAWDIR\<pdl>.

Next, run the following command: rm -rf on the following directories (for visual reference, look at the screenshot below and make sure that your screen matches all of the commands):

• obj\*
• map\default\*
• map\intmap\*
• int\*
• *src\int\wslib\*
• *src\int\pdlib\*
• sdlib\*

Finally, run the command combcmp <pdl>.  If everything was run correctly, then this will recompile every program in the productline and create fresh compiled code.

 

If you need to update Lawson database tables to match custom form field changes, follow these steps:

 

First update your .scr forms, kndef, skndef fields if creating new columns. Updated your .sr file to include any additional fields if needed.

Then in dbdef <productline>

F6 (Define) >> Files and update the database table names

Once done, follow these procedures:

You can run a bldddbdict <productline>

Then dbreorg -l <productline> to see affected tables.

Then dbreorg <productline> to complete the dbreorg.

NOTE: If DBReorg fails, make sure websphere apps are down and java processes are not running, try and restart server then perform dbreorg again if needed.

Qcompile your file and clear cache/ios cache, then test changes.

If you need to update your SQL Tables after a data refresh, follow the simple steps below:

 

First, open up the properties for the DB that was just refreshed and you can see that the DB tables have the PROD name instead of TEST.

 

Next, run the following SQL query for the TEST DB:

ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_DATA NAME = INFORLAWTEST10_DATA

ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_INDEX NAME = INFORLAWTEST10_INDEX

Your SQL tables should now be updated after doing a data refresh. Continue to repeat these steps whenever you do refreshes.

When testing the FTP connection on a Lawson Back-office data source in LBI, you may receive the error message “System Directory Not Available”.  You may also see this message in the SystemOut.log on the LBI server when the system is testing the connection.

Here are some troubleshooting steps when you encounter this issue:

1. Open a Windows command prompt on LBI server
2. ftp <lawson application hostname>
3. log in as <ftp user>
4. cd <application home path>
5. ls (You should see the ‘system’ directory listed here.  If not, that is the source of the “system directory not available” error). If you see the system directory, continue:
6. cd /system/ers/backoffice/<pdl>
7. get published.csv
8. del published.csv
9. put published.csv
10. cd <application home path>/print/username/jobname/1 (use a username and job name for a published report, or any job if you have nothing published yet.)
11. get <JOBNAME>.prt
12. del <JOBNAME>.prt
13. put <JOBNAME>.prt

NOTE you can also use an ftp client such as Filezilla to check for the file

Once you have ensured access to all of the above directories over ftp, you should find the following message when you test the FTP connection.