Message stating LPCMN.BND not found when executing RDMLX function/WAM/component on IBM i

Date:31 August 2010
Product/Release:LANSA V12
Abstract:LANSA can issue an error stating LPCMN.BND is missing even though it does exist
Submitted By:LANSA Technical Support

Description:

In V12 EPC851, when executing RDMLX on the IBM i, an error can be generated stating that LPCMN.BND does not exist. This can effect RDMLX functions, RDMLX Webevent functions, RDMLX components running on System i, and WAMs executing on a System i application server.

Check the x_err.log on the IFS to see if it contains:

==================================================================
Tue Aug 31 11:35:31 2010
Release 12.0.0 Build 4042 iSeries
Process : MYPROC
My Test Process
Function : RDXFUNC
RDMLX Function that uses Intrinsics
Statement : 3
Message : INSTALLATION ERROR : Standard Bundle File lpcmn.bnd not found.
Routine : File lpstate at line 293.
Job Number: 180453 OS User : S01PGMLIB
ITRO=N ITRL=9 ITRM=99999999 PROC=*IRPG PART=DEX LANG=ENG DATS=S
ROOT=/LANSA_s01pgmlib

The Joblog may also contain the following message:

CPF9898 Diagnostic 40 31/08/10 11:35:31.778492 DCXS86XX S01COMLIB *STMT *EXT *N
         From module . . . . . . . . : DCXP8602
         From procedure . . . . . . : DCXP8602AH
         Statement . . . . . . . . . : 4
         Message . . . . : Fatal Error : Process : MYPROC My Test Process
           Function : RDXFUNC RDMLX Function that uses Intrinsics Statement : 3
           Message : INSTALLATION ERROR : Standard Bundle File lpcmn.bnd not found.
           Routine : File lpstate at line 293..
         Cause . . . . . : This message is used by application programs as a general
           escape message.

This message may appear even though the file does exist in the IFS with correct authorities. To make matters confusing, executing the same code a second time, may work without any problems.

Cause:

This issue is caused by the way in which LANSA determines where to find this LPCMN.BND file. In certain combinations of RDML/RDMLX interaction, LANSA can produce this error message.

Solution:

This issue will be fixed in an EPC for V12. A hotfix is available from your local LANSA vendor if an immediate solution is required.