[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1229
  • Last Modified:

Lawson screens lock-up

We have a 10 year old Lawson Insight II Financial suite version 7.2. The users screens lockup solidly and they have to kill the session and log back in to continue. For example, it happens when they try to page through many PO lines in PO30 to receive. This problem happens in many other PO, RQ screens.  I can reproduce the problem myself. This has been going on a few months and is a nightmare during monthly closing.
Please Help!
0
JohnBaby
Asked:
JohnBaby
  • 12
  • 10
1 Solution
 
tbsgadiCommented:
Have you been in contact with their Support?
http://www.lawson.com/wcw.nsf/pub/support_online

Gary
0
 
JohnBabyAuthor Commented:
We've been unsupported since 2005. This was done as part of a cost savings measure (and saved a job or two).
0
 
wakeyladCommented:
Have you tried running the same programs through the animator? (Debugging tool).
When was the last time you did a reboot?

0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
JohnBabyAuthor Commented:
We did a reboot this week. I'm trying to get the animator working now with cobdebug for PO30. I get an error message "191 Terminal type not defined". LATERM is set to univwin.
0
 
wakeyladCommented:
You most likely need to set your Terminal Type to pt80-e

0
 
wakeyladCommented:
What is your COBTERMINFO environment variable set to? Ours is set as follows but we're on the latest Lawson version:

COBTERMINFO=/usr/share/lib/terminfo

0
 
JohnBabyAuthor Commented:
The COBTERMINFO directory has single digit directories like this:
dr-xr-xr-x   2 bin           1024 May 11  2002 x/
dr-xr-xr-x   2 bin           2048 May 11  2002 v/
dr-xr-xr-x   2 bin           2048 May 11  2002 t/
dr-xr-xr-x   2 bin           1024 May 11  2002 r/
dr-xr-xr-x   2 bin           2048 May 11  2002 w/
dr-xr-xr-x   2 bin           1024 May 11  2002 u/
dr-xr-xr-x   2 bin           1024 May 11  2002 p/
dr-xr-xr-x   2 bin           1024 May 11  2002 g/
dr-xr-xr-x   2 bin           1024 May 11  2002 s/
dr-xr-xr-x   2 bin           2048 Sep  2  2007 I/

Here's env:
COBTERMINFO=/usr/lib/terminfo
TERM=pt80-e
LAWDIR=/lawson/law
LATERM=univwin
PWD=/home/systems/intrface
TZ=EST5EDT
ENV=/home/systems/intrface/.kshrc
LINES=26
0
 
wakeyladCommented:
This is for release 8.0.3:

COBOL animator error: "191 Terminal type not defined"
 

Description:  
When I attempt to animate a program, using cobanim or batchanim, in the Lawson Terminal or Lawson Insight Desktop (LID), the following message displays:

Execution error : file’/opt/cobolse/dynload/animchr.lbr/dispatch.gnt’

Error code: 191, pc=0, call=1, seg=0

191 Terminal type not defined

How can I resolve this issue?

 
Resolution:  
This error message occurs, because the animator does not recognize the terminal type value defined.

For LID with Server Express 2.0.11 or 2.2:

Set the TERM environment variable to "univwin" or "pt80-e".   Run the command:  export TERM=univwin

For LID with Server Express 4.0 and higher:

Set the TERM environment variable to "pt80-e".   Run the command:  export TERM=pt80-e
Set the LATERM environment variable to "univwin".  Run the command:  export LATERM=univwin
For Lawson Terminal (Browser based terminal) with any version of Server Express:

Set the TERM environment variable to "vt100".  Run the command:  export TERM=vt100
Set the LATERM environment variable to "ltrm".  Run the command:  export LATERM=ltrm

Important Note: When using the terminal type of ltrm in an animator session, the Escape key does not function. You must press Shft+Esc to perform the escape function.

AIX only. Perform the following steps to configure animation.  If the above doesn't work, it may be a configuration issue specific to AIX.

Please try the following:
Create an environment variable for the system location for terminfo. At a command prompt, type:  
export COBTERMINFO=/usr/share/lib/terminfo

Run the mftic program against the terminal type for debugging. At a command prompt, type:
mftic $COBDIR/terminfo/mfdebug.src
   
Additional Information:  
 
Keywords:  
animate 191 terminal type animation se server express cobterminfo terminfo mftic mfdebug.src lid lawterm lawson terminal vt100 pt80-e univwin ltrm terminfo
 
0
 
wakeyladCommented:
I also found this on one of the forums in response to the same problem:

You are correct. LIS referred me to the appropriate KB article this morning. I had ran into it before. The initial terminal type problem blinded me. I was looking for something new related to it. Anyway, after replacing the $COBDIR/bin/rts32 and setting the TERM environment variable to "vt100", the animator seems to work fine. Just FYI on the terminal type. I had problems when I set LATERM to "ltrm" as suggested in the original KB article. I tried "univwin" instead. It allowed me to use the same session for LID while leaving TERM set for the animator.
0
 
wakeyladCommented:
John:

Out of curiosity, did you check the log files?
0
 
JohnBabyAuthor Commented:
OK thanks! - export TERM=univwin works and the animator is running.
Now let me start debugging to see what the program is trying to do when the hang-up occurs. I have a test case that fails every time in PO30 on a PO when paging through its 24 line items (happens other ways, but this is always reproduceable and simple.
0
 
wakeyladCommented:
Let me know how it goes
0
 
JohnBabyAuthor Commented:
Thanks - I've got to wait till late tonight or over the weekend when the users are off.
0
 
wakeyladCommented:
Were you able to do anything with this over the weekend?

0
 
JohnBabyAuthor Commented:
Yes - I've attached some snapshots in a zipped .doc file. Thanks getting back.
debug-result-from-prd.zip
0
 
wakeyladCommented:
I usually perform my debuggin in character mode. (LATERM=pt80-e).  I would set the breakpoint at the first statement in the 700-GET-TRANSACTION which should be the CALL "GetTransaction". Also set a breakpoint for the statement right after that statement. If I remember correctly, that should be the statement that gets the date/time. (I set this just in case I accidently Zoom into the GetTransaction).
When you get to the breakpoint that call for the CALL "Get Transaction", don't Zoom but Step into the transaction. Once the program returns from the CALL "GetTransaction" you can then Zoom through the rest of the program until you again hit the CALL "GetTransaction". I found that Zooming into the CALL causes problems whereas Stepping does not. I have no idea why.
0
 
wakeyladCommented:
BTW, where are you located?
0
 
JohnBabyAuthor Commented:
I'm in Norwalk, CT. But most users that are affected are in Ohio and Oregon (Norwalk is HQ for Siemens IT Solutions and Services, North America). The Lawson servers are in Ohio. BTW we're scheduled to go live with SAP July 1. I'm not a developer in SAP (although I took the ABAP couses 10 years ago when we were also supposed to migrate!) since the Basis group is centralized for North America in Atlanta (with ties to India). But I'm a Power User instead (don't feel like one yet) and have a role as User Creator, and have been travelling to Atlanta for over a year now. Do you do SAP also?
0
 
wakeyladCommented:
I'm in New York (Queens). Purely a Lawson Technical Consultant (Developer). I've no experience with SAP. Are you/were you doing any development under Lawson? How long has the SAP implentation been going on?
0
 
JohnBabyAuthor Commented:
Hey - we're practically neighbors. Yes, I've done some development over the years, but nothing too fancy. The SAP project has been going on maybe 1.5 years now - we are leveraging an existing template with customizations, so the cost is not so bad. We actually sell SAP implementations as part of our services, but I'm not involved.
0
 
wakeyladCommented:
I believe Seimens also does Lawson implementations. I remember writing an XML interface for a Seimens clients, in Florida, a few years back.
.
0
 
JohnBabyAuthor Commented:
I haven't got a chance to do the debugging steps yet as recommened (monthly closing), but did want to mention that the screens do not hang up when using pt80-e. So it could be a temporary solution, but one user rejected it becasue she says the buttons on her GL screens are different.
0
 
JohnBabyAuthor Commented:
Thanks!
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 12
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now