Miscellaneous

This section provides you with solutions to messages you might receive when you work with other Lawson products.

Message

Cannot access the lacase menu. Database jobs stopped. “Close dbfile bad file handle(15)” error in lajs.log.

Solution

Stop and start the Lawson system.

__________________________________________________________

Message

“Cluster Node Definition Not Found” error when running blddbdict.

Solution

Run rmdbloc -a dictionary .

__________________________________________________________

Message

“Filename: Must Be Installed setuid root.”

Solution

__________________________________________________________

Message

"File unsafe."

Solution

Stop the Lawson system, remove file.i, run startladb, run rebuild -f file , and then start the Lawson system.

__________________________________________________________

Message

“500-ALPHA-STRING not found.”

Possible cause

STRRTNS and STRWS are missing.

Solution

Add STRRTNS and STRWS to the $LAWDIR/pdlib directory and recompile the programs.

__________________________________________________________

Message

"lacobrts terminated: press any key: lapm # file <productline> <filename> OPEN DBFILE error is dictionary/program timestamp mismatch."

Solution

Recompile the form.

__________________________________________________________

Message

"Print cannot make pipe. Data table overflow."

Possible cause

The job queue is full.

Solution

Run deljobhst to delete completed jobs.

__________________________________________________________

Message

“Secdict: Security Class XXX not in dictionary” error when trying to form-transfer.

Solution

Run bldsecdict -d productline .

_________________________________________________________

Message

"TCP error - cannot connect to remote host."

Possible cause

The Lawson remote database server cannot get a connection to the remote machine. The most common cause of this problem is that the full path for the server in the inetd.conf file is incorrect.

Solution

Check the information available in the ladb.log file. Check that all setup procedures were completed correctly for distributed computing. Make sure a symbolic link is not used in the path name.

__________________________________________________________

Message

"Tranmap.hlp i/o error or Tranmap error fatal version."

Solution

Remove $LAWDIR/obj/Tranmap, and then run scrgen.

__________________________________________________________

Message

"Window does not allow form transfer."

Solution

Run scrgen on the product line, and then recompile the program.

__________________________________________________________

Message

“latm (Configladb): PMMsgBuf: memory allocation failed System Message: Not enough space.”

Possible cause

This message might appear when running Lawson on a Dynix operating system. The address location picked by the kernel for the shared memory address is too close to the heap. This might cause programs that allocate large amounts of memory off the heap to run out of heap space.

Solution

To move the shared memory address away from the heap, define the UNIX environment variable LADBADR in $GENDIR/bin/startlatm.

__________________________________________________________

Message

“ProductLine has been upgraded and no longer uses SuperElements”

“Invalid Product Line.”

As of the 8.0.0 Environment release, element groups and super elements are not available with new product lines (they are still available on existing product lines through the 8.0.2 application release). The functionality they provided is available instead through fields and elements, because in new product lines in 8.0.0 or later Environments an element (if linked to more than one field) functions in effect like a super element. If you attempt to use the Element Group utility within a product line that was created with a Lawson technology release of 8.0.x or greater, these messages will appear.

Solution

In new product lines created within 8.0.0 or later Environments, you can link an element to more than one field, where each field has a different name without the use of super elements and element groups. For more information, see the Doc for Developers: Application Development Workbench manual.

__________________________________________________________

Message

Product line productline has more than mFiles (4000) defined.

Solution

A system code should have a maximum of 200 files and a product line can have a maximum of 512 system codes.