When migrating or copying custom COBOL programs, it is often necessary to also migrate messages and work file definitions (aka metadata).

First, dump the messages and work file definitions using the following syntax:

metadumpmsg <productline> <messagecategory>

metadumpwrk <productline> <programcode> <workfilename>

 

For example, metadumpmsg prod ZC186 and metadumpwrk prod ZC186 ZC186_ERROR-RPT

The messages will be dumped to a file <messagecategory>.msg.

The work files will be dumped to a file <program_workfile>.wrk.  Work file names can be found in workdef.

 

After all the metadata elements are dumped, copy them to the other server/productline.  Using a command line utility or LID, navigate to the location where you placed the files, then run the commands to load them.

 

Loading messages syntax is metaloadmsg <productline> <filename>.msg

Loading work syntax is metaloadwork <productline> <filename>.wrk

If you want to use filters with a user, you can enable filtering when you create a user. Follow these steps below:

 

Enabling users for filtering

  1. Open a user and then select the “Is Filter Enabled” check box.
  2. Click Save.

 

Enabling tasks for filtering

  1. Open a Task and select a User Task.
  2. Select the “Is Filter Enabled” check box when you link a task to a user.

Note that a user must also be filter-enabled to use filtering associated with tasks.

 

Often times a user is responsible for updating dozens of LBI report schedules that generate daily, weekly, and monthly report instances.

A parameter might have been set incorrectly and is now generating the incorrect data for a bunch of instanced reports that now are useless and no one noticed until several report instances existed.

Today we are going to go over how to easily fix those report instances assuming one has admin access and crystal reports installed.

Here is an example of a report a user was viewing that contains no bursting data for that user because it has the incorrect parameters:

First thing to note is the Report ID and Instanced ID as highlighted below.

Let’s now export the report as a Crystal report as shown by the arrow below.

Open the exported report in Crystal and press F5 >> Prompt for new parameter values >> OK

This should pull up the incorrect saved parameters. Change it to the proper values and press OK to generated the report with data. (you may be prompted for credentials, you’ll need some sort of db read access).

After the data is generated go to File >> Save and make sure “Save Data with Report” is highlighted:

Now go to the report instance that you exported this from and click details:

Under Report Actions >> Republish >> Choose File >> Find the updated crystal report, select >> Save

Now view the report again and see if it shows the correct data. Do this for the rest of the reports.

Numerous organizations choose to leverage Lawson consultant teams to oversee their Lawson Security and LBI systems. These expert teams provide managed services at a predictable monthly rate, offering extensive knowledge and specialized expertise. This solution is ideal for larger organizations, while smaller entities seeking efficient management without the need for full-time on-site staff can also benefit. Nogalis delivers these services, and additional details can be obtained by contacting us through our dedicated contact page.

In Lawson, your users may be experiencing a GL190 job in recovery.

 

You may be getting this error:

This is due to the GL190 job being ran when another GL190 job is running in the same jobqueue.

 

Locate the job in recovery (notice the Job Queue below *********):

Go to GLMONITOR, inquire on GL190 program. This will bring back all jobs in recovery here, only delete the one you plan on recovering, then do so for the remaining.

Once the GLMONITOR is cleared of that specific job, lets recover it and see if it completes (make sure no other GL190 jobs are active).

 

That’s it, hopefully this helped resolve your issue!

We recently had an issue with a new install where all batch jobs were going into recovery with the error “Unable to log in <username>”.  The can often be attributed to an incorrect password in the BATCH privileged identity, but in this case it was due to a typo in lajs.cfg.  The “RUNUSERKEY” field was misspelled.  So, if you ever encounter this issue, you can save yourself some time and get a couple of sets of eyes on the lajs.cfg file!  After making the change, reboot the Lawson server or stop/start services. You should now be able to log in.

 

 

When it comes to IPA security access, you can assign the following Lawson delivered roles to IPA users:

 

Delivered role Intended for use by Contains these security classes
InbasketUser_ST Normal end-users who receive work items in the Inbasket BasicProductLineAccess_ST

ProductLineAccess_ST

InbasketUser_ST

Lpa_ST

ProcessSchedulingAllAccess_ST

JobQueueServer_ST Users who must perform actions on the Landmark job queue. BasicProductLineAccess_ST

ProductLineAccess_ST

JobQueueAccess_ST

ProcessDesigner_ST Process developers BasicProductLineAccess_ST

ProductLineAccess_ST

Lpa_ST

ProcessDesigner_ST

ProcessSchedulingAllAccess_ST

ProcessServerAllAccess_ST IPA system administrators BasicProductLineAccess_ST

ProductLineAccess_ST

Lpa_ST

LpaAdmin_ST

ProcessServerAllAccess_ST

ProcessSchedulingAllAccess_ST

ScheduledActionsAccess_ST

ProcessServerReadAccess_ST IPA assistant administrators, power users, developers ProductLineAccess_ST

ProcessServerReadAccess_ST

 

Searching JXplorer can be cumbersome when you have thousands of Lawson users and possible issues with “rogue” or “orphaned” identities being stored when trying to update identity information.

Below we are going to show how you can easily search for this information vs manually scanning thousands of users.

 

First Select the part of the LDAP tree to search from:

CTRL + F

 

Notice the “Starting Searching From” field, this search will search all trees below this.

Now go into your Text Filter tab and type in parenthesis the field and value you want, click search

 

It will automatically switch to the Results field and show your results:

You can then do another search within these results or go back to Explorer tab and CTRL+F again and it will bring your previous search up.

You can also get creative and search multiple fields and values with an “OR” search:

(|(cn=*jon.doe*)(mail=*jon.doe*)(uid=*jon.doe*)(lwsnssoListOfIDs=*jon.doe*))

This is an AND search:

(&(cn=*jon.doe*)(mail=*jon.doe*)(uid=*jon.doe*)(lwsnssoListOfIDs=*jon.doe*))

 

The | means OR, & means AND. So each field cn, mail, uid etc. have to all bring back a result for it to work. It’s best to use an OR search on average.

Remember, you can also save your searches:

As mentioned above, this is especially useful when finding users in JXplorer to remove any duplicate or “orphaned” RMIDs and Identities not showing up in Lawson Security.

 

Good luck!

To do a full manual recompile of a Lawson Program, follow these simple steps:

  1. Open a LID session
  2. Navigate to <LAWDIR>/<prodline>/map/default
  3. Run the command scrgen <prodline> <system code> <program code>
    1. for example: scrgen prod PO PO54
  4. Run the command xscrgen <productline> <program code>
    1. For example: xscrgen prod PO PO54
  5. Run the command lstinvk -q <prodline> <program code>
    1. For example: lstinvk -q prod PO54
  6. Run the command qcompile <prodline> <system code> <program code>
    1. For example: qcompile prod PO PO54
  7. Use the command qstatus to check the status of the compile

 

Once the compile is complete, check your program again. That’s all there is to it!

 

IPA Service definitions can be used to cause or trigger a process to run.

If your site has an event for which work units are delayed or not running for any reason, you can trigger a process to run using the Service Definition in Process Server Administrator.

A process, which is created using Infor Process Designer, routes and tracks the sign-offs that need to occur. In this case, a service, which is delivered with Lawson applications, triggers the launching of the process. It is also possible to create your own service.

  1. Access the Process Server Administrator and select Scheduling > By Service Definition.
  2. From the displayed list of services, double-click the name of the service that you want to trigger the process.
  3. Specify this information:

Work Title

Specify a name for the work item.

Filter Key

If filters have been enabled for users and tasks associated with this service, select an option.

Filter Value

If you are using a filter key, specify a filter value.

For example, if you selected City for a Filter Key, then Chicago might be a valid value.

Apps Key

Specify an application key.

Apps Value

Specify a value for the selected apps key.

  1. Optionally, on the Criteria tab, specify up to three levels of criteria.
  2. If variables are enabled for the service, the Variables tab is active.
  3. If links to documents or other information is available for use with this service, the Related Links tab is active.
  4. When you are finished defining the circumstances, click Actions > Save.

To trigger a work unit to process, follow these simple steps below:

 

First, you will need to access the Process Server Administrator screen and then select Scheduling > By Process Definition.

 

Next, select the process name and double click on it.

 

Then Select Actions > Start. You should now be able to trigger a work unit to process!