BSI - Taxfactory

What release of BSI are you using? 8.0.j?

Maybe this will help:
I had a similar problem with the PR140 after a BSI upgrade. In the msgmnt program called from LID, there is a 400 type message that was being logged. This message was added during our BSI upgrade for troubleshooting purposes, but never removed. It caused significant performance issues all around. The PR140 went from 10 minutes to over 1 hour. If this message exists, remove it, and all should be back to normal. If it does not exist, I suggest the following:

I created the following steps to troubleshoot the PR140 before finally finding a solution above. Use the same steps for the PR13.8 Submit all log files to the GSC for review:

Compiling the PR140 in Profile Mode

All the steps below are to be performed by user Lawson.

1. Do a bldsh against the program. This will generate a .cbl that will be used in step 3 below:
bldsh PR PR140

2. Remove the programs .gnt executable. This will ensure the .int created will be executed instead of the .gnt:
rm $LAWDIR//obj/PR140.gnt

3. Move the programs .cbl file from the source directory to the obj directory:
mv $LAWDIR//prsrc/PR140.cbl $LAWDIR//obj

4. Perform a Microfocus cob compile on the PR140 using the following syntax. Execute the command from the $LAWDIR//obj directory:
cob -C nolist -C warning=1 -C QUAL -c -C profile vsc2 PR140.cbl –a

5. This will generate a .int and a .idy files associated with the program. From the $LAWDIR//obj directory, do an ls to see if the two files were created:
PR140.int
PR140.idy

6. Run the program (submit the PR140 batch job) normally. Upon completion, a .ipf file will be created in the $LAWDIR//obj directory:
PR140.ipf

7. From the $LAWDIR//obj directory, run the following command to translate the .ipf trace log into a text file that can be read, edited, printed, etc…
cobprof PR140 +list > PR140.out

8. Send the output of the cobprof command to Lawson support.

Multiple runs of the program in TIMESTATS mode can be executed, but be sure to delete the .ipf file between runs as the profiler adds to the end of the output if it exists.

What you will see are paragraph names, the number of times you entered the paragraph, and the time spent in the paragraph.

Activating the Lawson dbadmin utility, Timestats
The timestats function is activated using the dbadmin utility. To show current settings, run 'dbadmin get' from a LID command prompt.

Run dbadmin get after setting the options to check that the desired options are enabled.

1. dbadmin set dataareafilter test – no need for dataarea filter. If you are gathering statistics, you want stats files for gen and logan as well as the 'test' productline.
2. dbadmin set timestatsdir /home/lawson/timestats
3. dbadmin set programfilter PR140 - no need to set, programfilter does not work, fixed in SP5 LSF9
4. dbadmin set userfilter medinar
5. dbadmin set reuse off
6. dbadmin idle test
7. dbadmin set timestats on
8. dbadmin get

• Current Value for REUSE=OFF
• Current Value for DEBUG=OFF
• Current Value for DBAPIERRORS=ON
• Current Value for TIMESTATS=ON
• Current Value for USERFILTER=medinar
• Current Value for PROGRAMFILTER=
• Current Value for DATAREAFILTER=
• Current Value for TIMESTATSDIR=/home/lawson/timestats
• Current Value for IDLETIME=1

To disable timestats and re-enable driver re-use:

1. dbadmin set timestats off
2. dbadmin set reuse on

Once data has been collected send all files to the Lawson GSC for review.
1. All files in the timestats output directory.
2. The PR140.out file.