AS400 recdef jobs are submitted but not completing

, ,

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:

  1. call lawenv
  2. qsh
  3. dbadmin idleAll (this will stop your idle cdriver jobs in the subsystem for this environment)

Update Infor OS Certificate

, ,

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!

How to find your lawappinstall version on AS400

, ,

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.

Lawson Users – How to change the default application in Lawson Mingle

, ,

When logging into Lawson Mingle as a user, by default, you load into the Infor Mingle app but maybe you want to load into Lawson Business Intelligence or Lawson Portal by default always.

 

To change the default application, first login to Infor Mingle

Once, logged in, open the waffle icon on the top left

You should see all the Lawson apps you have access to here

Infor Lawson gives access to Lawson Portal and very common. In order to make that the default application, click and drag that icon to the left of the Infor Ming.le App and drop:

The first icon in the top left will always load by default.

Now reload the page and watch it load Lawson portal first.

Hope this little tip was helpful!

AS400 Lawson IBMDB program CDRIVER

, ,

On the iSeries/AS400, A CDRIVER is a Lawson IBMDB program written in “C Language” and runs on the System i platform.

Its primary use is to retrieve data from DB2 using Structured Query Language (SQL)/Call Level Interface (CLI) Application Program Interfaces (APIs).

Furthermore, Lawson Jobs are using CDRIVER. Each Lawson Job has its own CDRIVER per Data Area or Product Line. Its purpose is to run SQL commands to retrieve database records requested by the job connected to it. The job name will be automatically registered in the CDRIVER joblog and the job that is attached to it may change if REUSE is set to “ON” in the ladb.cfg.

Benefits of Infor’s Multi-Tenant Cloud

, ,

With Microsoft’s end-of-life for Windows 2012, and Lawson’s end-of-life coming up in 2026, many organizations are considering a move to a cloud solution.  And Infor’s Multi-Tenant cloud is a true contender.  Here are just a few of the benefits of choosing to move into the Infor Cloud.

Flexibility

Once per year, customers have the ability to request a swap in Infor products.  Swappable Infor products include any multi-tenant products that the customer has subscribed to for at least one year.  Talk about flexible!

If you are already in the cloud, and looking for a technology swap, contact your Infor Account Executive today!  Your AE’s contact information can be found in the Contact widget on your Concierge home page.

Transparency

Pricing for storage, additional non-production environments, and programmatic access can always be found on Infor’s web page.  Non-production environments can be used temporarily as-needed (a minimum of 6 months) to save on costs.  Storage can be requested subject to a minimum amount and time.  Programmatic access, or the interaction between Infor products and third-party programs, will use the Infor OS service and is priced separately.  Again, this pricing is always available on the Infor Docs website.

Support

Severity 1 issues are covered by customer support 24x7x365.  Response times are within 30 minutes from Infor’s receipt of the logged request, and they are working to decrease that SLA all the time.  They are currently working toward a goal of increasing support for Severity 2 issues to 24×7.  And they are improving their response templates to make sure customers are receiving the most accurate and detailed information possible on each ticket.

Availability

Infor offers credits if the Multi-Tenant cloud availability dips below a specified threshold.  This credit would be calculated by the month.

Infor refers to these ideals as the customer’s “Bill of Rights”.  And as great as they are, Infor is constantly working toward improving on these “rights”.  Stay tuned!  More good news is coming!

 

Changes with MSCM v11

, ,

There are some important changes to MSCM v11 that will impact the way handhelds and admins interact with it.

First, the handheld URL has changed.  To connect to MSCM, the handheld should connect to mscm_server/mscm.  Note that the “mscm” appended to the end of the URL is new.

The configuration has also been moved off the file system and into the database.  The configuration can be edited at this URL: http(s)://mscmserver:port/mscm/service/app/login.jsp

Finally, if you are having trouble printing labels, go to the administrator and check for the flag “Use Printer Agent For Printing Documents And Labels”.  This should be unchecked.