When you’re logged into Lawson, in order to compile all the programs invoked by one program, make sure that the syntax reads: lstinvk -q <pdl> <program>.

 

By doing this it will compile anything that is invoked by the program. After, you do this, then you will need to also compile the program itself. (See screenshot below for reference)

 

That’s all there is to it!

If your Lawson PR160 job status is in “Needs Recovery” or “Is currently running” (because it’s in recovery), see below for the potential fix.

Another error you may encounter is “Ern2 Record Exceeded limit size of 15000”

 

 

Resolution:

  1. Rerun PR140 (If you encounter an error indicating that PR160 is currently running when rerunning PR140, you should restart PR00 by performing a “double delete.”)
    1. “Double Delete” means going to PR00 and hitting the delete button twice until you clear out * and R flags
  2. Run PR160 with the Earnings Record NOT equal to blank after clearing flags in PR00

 

Hope this was helpful!

Problem:

So you’re running a Lawson PR160 job (Payment Print) and encounter the “Bad File Status 9 009 error on File TAPE-FILE” error. What do you do?

 

Resolution:

First, understand that the error message “Bad File Status 9 009” signifies that either the directory is full or doesn’t exist.

What you will need to do is simple: ensure that a valid path is specified in the PR160 parameters. If there is, double-check that the path is correctly spelled and has sufficient available space in the default location (along with any folder permissions). See the screenshot below for guidance. That’s all there is to it!

 

Problem:

After adding a view to a productline database and adding it to the application productline using dbdef, blddbdict and dbreorg, the blddbdict created  a +dictionary, but the dbreorg -lc does not show anything as being added.

 

Resolution:

Files added in dbdef and assigned a database space defined as “Is View Yes” are treated as views by the dbreorg.

Views are not created or modified in the database by the dbreorg process, therefore, they will not show up in the output list from dbreorg -lc.

The dbreorg -lc only lists structure changes that the dbreorg makes to the database.

Any non-structure changes made to the file definitions are not shown in the dbreorg -lc output.  Non-structure changes are file relation definitions and fields defined as compute, conditional or string.

If you’ve ever come across the following problem below, follow this quick guide to solve it.

 

Problem:

Users receive error messages when they are running jobsf. The errors are indicating that the CKPOINT table does not exist after the system admin completed a productline copy.

 

Resolution:

Simply put, the CKPOINT file did not get copied over during the copy procedure. Run the following commands to add the CKPOINT table into the productline:

bldckp productlinename

blddbdict productlinename

 

Stop the WebSphere Application Server

dbreorg productlinename

Have the users login and try to run their jobs again. Your error message is now resolved.

 

As a Lawson Managed Service provider, we see many different Lawson v10 systems (even v9 systems) and often we find users with CheckLS = No but get asked if this should be set to Yes.

In the past when migrating clients from LAUA to v9 or v10, CheckLS to Yes would put them on v9 or v10 security instead of LAUA security.

 

Today if you’re on later versions of v10, it’s still the best practice to set CheckLS to Yes in the users RM info but the official Infor documentation reads as follows:

“When you upgrade to 10.0.x, the system will treat this field (checkLS) as set to Yes in all cases”

 

So if you’re scratching your head, what this means is that in v10 and forward, checkLS field Yes or No still puts you on v10 Security. However, setting it to Yes can also give users the ability to access LID if needed (assuming they have ENV access to specific LID command tokens).

 

The BATCH privileged user will only be used for standard Lawson batch programs. If the LSF environment is configured to use the BATCH privileged user and a batch job executes a user token with a script goes into “Needs recovery” status with the error: “execjob(laStartProcess): Unable to log in DOMAIN\USERNAME StartStep failed: Overlapped I/O operation is in progress”, then its possible that the users password has been changed or expired on the network.

 

The user’s password for their environment identity found in Lawson Security under User Management MUST match the user’s domain/network/AD password. This is required by user tokens. To resolve this issue so user tokens run to completion, the Lawson Security Administrator will need to update the environment identity password for the user running the job so it matches their OS/AD password, OR the system would need to be configured so the user could enter their own password so it matches their OS/AD password.

There may be an instance when you are getting an error in Lawson Security Administrator (LSA) stating that the “Data area has been suspended”. This happens when you are adding a rule to a security class. This error usually occurs after running dbreorg without stopping your LSF WebSphere Application Server prior to the execution of dbreorg.

To resolve this issue, follow the steps below:

  1. Stop LSF WebSphere Application Server
  2. Stop LSF WebSphere Node Agent
  3. Stop LSF WebSphere Deployment Manager
  4. Make sure that there are no java processes
  5. Stop your LSF environment
  6. Start LSF WebSphere Deployment Manager
  7. Start LSF WebSphere Node Agent
  8. Start LSF WebSphere Application Server
  9. Start your LSF environment

There may be a time when you want to remove a URL from the cached URLs list in Lawson Security Administrator (LSA).  This could help clear storage space and run your programs faster and would not hurt to clear your cache regularly.

If you want to clear your LSA cached URLs, on your desktop where you use the program, you will need navigate to %programdata%/LawsonHttpClient.  Next, edit the list as needed and save it. The changes will be immediate after you click save. Your LSA URLs have now been cached! You can refer to the screenshots below for a visual guide.