Archive for category: Articles

You may be used to deleting users jobs through jobdef.

This works, though you must select each job individually and press delete. So it’s not very efficient.

A better way do to this is jobinq

In lid >> jobinq <DOMAIN\UserName>

This will open up a window listing all the jobs of the user:

Now you can select multiple jobs with the HOME key:

If you want to select ALL jobs and delete them, select first job with HOME key.

Scroll all the way to the bottom of the job list and press END key on the very last Job and press F9 to delete:

Done. Good luck!

Login and get to the main menu of websphere

Then go to Resources >> JDBC >> Data sources:

Select New to create a new DataSource:

Type in the name of your DataSource and your database name as so (place the jndi\ in jndi name field):

Select existing JDBC provider >> Microsoft SQL Server JDBC Driver (Most common)

Enter in your database name and the server your database sits on:

Select your Admin user for Component-managed authentication alias.

Review your setup and click Finish:

Go test your newly created DataSource in from a SmartNotification or LBI Report that uses that DataSource.

Enjoy!

Every time an employee makes a benefits change, a new record is stored in the benefits table.  Additionally, a new record is stored in the employee’s deduction master table for each deduction related to that benefit.  If these records are allowed to accumulate unchecked, this can slow down payroll processing and even cause errors.  The larger the benefits and deductions table become, the slower payroll batch jobs will run.  These batch jobs, such as PR140, loop through each record in these benefits and deductions tables so that the correct deductions are applied.  Some of these batch jobs have a limit of the number of records allowed, so if an employee has deductions that exceed that limit, the job will error out.  Also, traversing through these records can greatly slow down processing.

To help alleviate these issues, we recommend running the BN430 benefits purge program periodically.  When you are processing payroll, if you see an error similar to “26 20591 PRDED-DED-TABLE must be increased; Cur size 0500”, chances are you have an employee with too many benefits changes, and need to run the BN430.  But, before you receive this error, you should make the benefits purge part of a normal maintenance process.  Ideally, payroll users would make this part of the payroll process each pay period, and choose a “Purge Through Date” corresponding to your company’s record retention period.

1. Open Infor Rich Client 
2. At the login prompt, enter the Lawson username and password
3. The canvas is now open. Look in the upper left corner and make sure you are pointing to the prod or test data area (not gen) 
4. In the upper right corner, click “Start > Applications > Process Server Administrator > Administration > Channels Administrator”
   1. At this point, you can click, HOLD, and drag the “Channels Administrator” link to the canvas. That way, it will create a shortcut on the canvas. 
5. Once you are in Channels Administrator, click on the File Channels tab, and you should see a list of File Channels that have been set up
6. Locate the channel for which you wish to scan
7. Right click on the channel and select “Scan Now”

8. This will scan the file configured in the Channels Administrator, and kick off any processes that use the files in that directory (the processes are configured in the File Channel Receivers section)

Lawson programs, especially batch jobs, can sometimes take hours to complete. In rare instances, a badly written 4GL batch job can even take days to complete depending on the number of records it has to process and how it goes about doing so. Depending on your skill set, you may be able to optimize the code directly and use a debugger to find out how to speed things up. But if you want some statistics about what the program is doing and a quick shortcut, then there’s a utility for that.

The utility is actually several different utilities wrapped into one.

dbadmin utility to set some parameters. The main parameter you want to set is the TIMESTATS parameter. The timestats function is activated using the dbadmin utility.

Before you go changing stuff, to show current settings, run ‘dbadmin get’ from a LID command prompt or a qsh command prompt in System i.

#Example:
dbadmin get
Current Value for REUSE=ON
Current Value for DEBUG=OFF
Current Value for DBAPIERRORS=ON
Current Value for TIMESTATS=OFF
Current Value for USERFILTER=
Current Value for PROGRAMFILTER=
Current Value for DATAREAFILTER=
Current Value for TIMESTATSDIR=/tmp
Current Value for IDLETIME=1

Save this off for future reference.

#To enable timestats, run the following commands:

dbadmin set timestats on
dbadmin set programfilter programcode   (optional, specify a program code. e.g. AP175.  The default is all programs)
dbadmin set timestatsdir pathname  (optional, ex. /home/username or C:\timestats.  If not specified, stats files are created in /tmp or %TMPDIR% for Windows)
dbadmin set dataareafilter productline  (optional, specify a productline name.  The default is all productlines)
dbadmin set userfilter username   (optional, the default is all users)
dbadmin set reuse off

#Clear the active database drivers so that the changes become effective
dbadmin idleall
tmcontrol -rp productline programcode  (For online programs only)

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

#After should look like this:

Current Value for REUSE=OFF
Current Value for DEBUG=OFF
Current Value for DBAPIERRORS=ON
Current Value for TIMESTATS=ON
Current Value for USERFILTER=
Current Value for PROGRAMFILTER=HR211
Current Value for DATAREAFILTER=test
Current Value for TIMESTATSDIR=d:\lawson\temp\timstats
Current Value for IDLETIME=1

Now you’re ready to submit your job again. Once the job is submitted, you should be able to see the stat files get created in the timestatsdir directory.
Wait until the job has completed before viewing the file(s).

You can view the files after the job is complete but they aren’t all that easy to understand. To make them easier to digest:

Go to the stats directory and run:
analyze_stats -o > stats.out

You’ll notice that you now have two new files in this directory.

stats.out and a cfg file.

The stats.out file will give you a really great view of what’s going on with your program while the cfg file can be place in the xxsrc directory of your code and compiled with the program to optimize it based on the timestats results.

After you’re done:

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

dbadmin set timestats off
dbadmin set reuse on