Abend can occur when attempting to use any type of deployed configuration that contains security credentials

Date:20 March 2012
Product/Release:LANSA Composer - All versions
Abstract:Processing sequence abends after importing configuration
Submitted By:LANSA Technical Support

Description:

A processing sequnce run on an IBM i server abends when it attempts to reference a configuration containing security credentials (such as an FTP configuration used with the FTP_INBOUND activity or a database configuration used with a Transformation map) if the configuration has recently been imported and the password has not been re-entered.

The joblog may contain error messages such as:
MCH3601 Pointer not set for location referenced

The x_err.log for a LANSA Composer version 3.0 system may include messages like this:

============================================================================
Thu Mar 20 10:45:42 2012
Release 12.0.0 Build 4042 iSeries
Component : DXACTMP01
Activity - execute transformation map
Statement : 182
Message : INSTALLATION ERROR : Standard Bundle File lpcmn.bnd not found.
Routine : File lpstate at line 293.
Job Number: 372878 OS User : LICPGMLIB
PROC=*IRPG PART=LC3 LANG=ENG DATS=S ROOT=/LANSA_licpgmlib
============================================================================

Or like this:

============================================================================
Tue Mar 20 13:38:48 2012
Release 12.0.0 Build 4042 iSeries
Component : DXACTMP01
Activity - execute transformation map
Statement : 182
Message : Unexpected or unhandled runtime error - Failure( *NULL_REFERENCE ) ReportedBy( File:x_varevaluations Line:9306 ) Reason( Unexpected or unhandled null component reference returned by lResult - Failure( *NULL_REFERENCE ) ReportedBy( File:lpcrdisp Line:4171 ) )
Routine : X_VarEvaluations
Job Number: 734149 OS User : LICPGMLIB
PROC=*IRPG PART=LCP LANG=ENG DATS=S ROOT=/LANSA_licpgmlib
============================================================================

Reason:

This can happen with LANSA Composer versions 3.0 or 4.0. It may occur on an attempt to use any type of configuration that contains a password. It can only happen as a consequence of deploying (importing) a configuration. Further it is only known to happen when the Processing Sequence is executed using the COMPOSER command on an IBM i server. It does NOT occur when the Processing Sequence is executed from the LANSA Composer client. Nor does it happen when executed on the server using LANSA X_RUN with a run control file.

The LANSA Composer export format excludes passwords for configurations that may contain them. This is deliberate (in order to protect security of customers' data) and documented in the LANSA Composer guide. Refer to 6.1 Deployment Considerations, Security Credentials for Transport and Database Configurations.

Note: The Processing Sequence should usually end in error (in a controlled fashion) in the case where valid security credentials are not present in a configuration it uses. This issue concerns only the case where the Processing Sequence abends (ends in an uncontrolled fashion).

Solution:

To correct this error, enter or re-enter the password for the configuration after importing it. Then re-run the Processing Sequence.