Typically when you click on an LBI report that’s been setup on the dashboard, it will show you data of the last generated instance. To add a refresh is incredibly easy.
First login to LBI and go to the dashboard you want to modify a report on. When you click it, you’ll see something like:
To allow the report to refresh data, select the plus sign >> Edit
You’ll see a URL field, all you need to do is add &Refresh=True to the end of the URL and click save.
The URL may look something like this:
FSRemote%3Ffsid%3DRS%3ARS-COMPANY%20Reporting%20Services%3A25%26
Now add %Refresh=True at the end of it like below:
FSRemote%3Ffsid%3DRS%3ARS-COMPANY%20Reporting%20Services%3A25%26&Refresh=True
Done! Now the report will always pull up the parameters (if any) so you can see the latest data:
If your organization still heavily relies on LBI today, which is harder and harder to find individuals who support it, we recommend organizations look into hiring a Lawson consultant team who offer managed services at a fixed monthly rate.
These Lawson teams have a wider range of expertise and knowledge and are ideal for larger organizations but also are great for smaller ones that don’t need a dedicated Lawson employee on-site that may only be an expert in 2-3 portions of Lawson.
There is not a delivered report that you can run to list out your recdef jobs. The file that holds the recdef data is called recurjob in your Gen Database Collection.
To get a report of all recurring jobs that are set up in recdef on AS400, follow these instructions:
From the AS400 command line type; CALL LAWENV hit enter and choose the subsystem in which you want to dump the records from.
qsh
rngdbdump -c GEN recurjob > /home/userprofile/recdef.csv (a dump of all recurring jobs that exist in recdef)
You can now use the wrklnk command to look in the directory listed in the rngdbdump command above to see the csv file that was created with these recurjob records.
wrklnk ‘/home/userprofile/recdef.csv’ place a 2 next to the file and hit enter
or
map a drive to your IBM i root directory via Windows Explorer and open the .csv file from there.
or
use the System i Navigator to open the file
When clicking on an LBI report, LBI prompts for credentials even though the user has LBI access already granted:
This is not an uncommon occurrence, and can easily be fixed.
First, on the LBI server, check the ODBC connection (partially hidden)
In LBI >> Manage Datasource, select data source and verify the Server field matches the ODBC connection.
Run the Test Saved Connection link after saving to validate (partially hidden in screenshots)
Once you are validated, make sure the report itself is defaulting to this LBI Datasource. If so, then you should no longer be prompted for credentials. Hope this helps!
If your Lawson System Foundation software is installed on an AS/400 and your recdef jobs are submitted, but just sit in an active status. View the examine log.
If the Examine Log/joblog for the batch job that was kicked off due to the schedule in RECDEF says this:
BEGIN: Recurring Job Submitted: Day Month XX TimeStamp
Step1: xx999 Started. . . . . . : Day Month XX TimeStamp
**Creating .prt and .dtl files
To understand the solution you need to be an IBM i admin that understands how to check and change both ownership and permission on files within the IFS directory.
Check your LAWDIR/Productline/IBM files for the application productline (ex. “lawapp10”, “logan” and for the “gen” productline.) They should be owned by LAWSON and both LAWSON and *PUBLIC should have *RW and all data and object authorities, except for “Execute” on the object authorities.
If they are not set that way, change the authority of the two IBM files to match what was just described above. Next take these steps:
- call lawenv
- qsh
- dbadmin idleAll (this will stop your idle cdriver jobs in the subsystem for this environment)
Updating the Infor OS certificate is an important housekeeping task and it is as simple as adding your new certificate to the binding on the InforOS websites. There are two website where this can be performed. The two websites in question are InforPlatformBackend and InforPlatformUI. Follow these quick steps below to easily update your Infor OS Certificate.
First, you will need to navigate to these two sites in IIS. Once there, next you will need to edit the bindings and select your new certificate. After you select your new certificate simply perform an iisreset, and you are all done!
Hope this article was helpful!
Want to know how to check your lawappinstall system version on AS400? This quick guide explains how you can find out what version of the AS400 you are using on your operating system. There may be more than one way of doing this but this, we’ve found, to be a very simple solution.
To find your version of lawappinstall, you will need to run the command(s) below that correspond:
- IBM® i®:
call lawenv [envName]
qsh
grep LaVersion $GENDIR/bin/lawappinstall | sed “s/.*8-)@(#)@//”
If ran correctly, the screen will display your system’s version. Here is an example version output from each platform:
10.0.9.0.1807 2020-09-17 18:28:22
That’s it! Hope you found this article helpful.
