02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Ending Promotions Based on Message ID<br />

LANSA Integration<br />

<strong>Implementer</strong> provides the IMLNMSG data area that allows you to store the message IDs of<br />

errors you want to force a promotion to fail on if the error is encountered. Fatal messages<br />

automatically cause the promotion to fail.<br />

During promotion processing, <strong>Implementer</strong> compares the message IDs written in the export<br />

list spool file to the message IDs recorded in the IMLNMSG data area. When a match is<br />

found, it ends the processing of the promotion job.<br />

This data area is blank by default. When adding multiple message IDs, separate the message<br />

ID values with one blank space.<br />

LANSA Object Codes<br />

<strong>Implementer</strong> provides the following object codes for checking out and promoting LANSA<br />

definitions. Before using the object codes for the first time, you must run the Build List for<br />

each LANSA environment to update the repository.<br />

<strong>Implementer</strong> uses the object code’s special characteristic to derive logic. The special<br />

characteristic matches the object code name and assigns the object authority *KEEP. You can<br />

change the name of an object code, but you cannot change the special characteristic.<br />

Object Code Description<br />

LANFLD LANSA fields.<br />

LANFIL LANSA files.<br />

LANFLDT LANSA files with data.<br />

LANPROC LANSA process.<br />

LANFNC LANSA functions.<br />

LANWEBC LANSA Web components.<br />

LANXMLC LANSA XML components.<br />

LANSVAR LANSA system variables.<br />

LANMVAR LANSA multi-lingual system variables.<br />

<strong>Implementer</strong> supports having the same file name in a single partition that exists in two<br />

different libraries. This feature requires using separate object codes for each file library. In<br />

addition, each separate object code must have the object library specified at the environment<br />

level. For information on setting up object codes, see page 127. For information on overriding<br />

a default library for an object code and environment, see “Environment Overrides” on<br />

page 133.<br />

331

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!