02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6: Third Party Integrations<br />

Support for EXCUSRSRC and EXCUSRPGM<br />

308<br />

By default, <strong>Implementer</strong> allows you to promote the AllFusion 2E EXCUSRSRC and<br />

EXCUSRPGM functions separately from their associated implementation 3GL source and<br />

objects. This is called “Independent EXCUSRSRC and EXCUSRPGM”.<br />

You can also automatically promote the 3GL source and objects associated with EXCUSRSRC<br />

and EXCUSRPGM functions when these functions are promoted. When enabled, the<br />

implementation objects for EXCUSRSRC and EXCUSRPGM function types are derived and<br />

included on the promotion request. With this feature, the implementation source and/or<br />

objects may not be checked out or promoted separately from this model object. This is called<br />

“Dependant EXCUSRSRC and EXCUSRPGM”.<br />

This feature is controlled by the User source and user program promotion method field in<br />

Work with Environments. When upgrading AllFusion 2E CM, the existing default method of<br />

independent EXCUSRSRC and EXCUSRPGM is retained. Enabling this feature provides<br />

capabilities that were available prior to AllFusion 2E CM release 6.0.<br />

Considerations for EXCUSRSRC and EXCUSRPGM<br />

When promoting EXCUSRSRC and EXCUSRPGM, even though the Remove source field is<br />

set to Y, the source for the user programs is not removed.<br />

Storing Source and Object Outside the Generation Library<br />

There are three common ways to store EXCUSRPGM source and objects outside the test<br />

model generation library. The following paragraphs briefly describe the scenarios and<br />

implementation steps. Each scenario uses the XCB target HLL object attribute in AllFusion 2E<br />

(see note) to create a new, corresponding object code in <strong>Implementer</strong>. The examples assume<br />

the EXCUSRPGMs are type CLP. If they are other HLL types, copy the appropriate shipped<br />

object code instead of CLP.<br />

For each of the following scenarios, define the XCB object code. Copy the shipped CLP code<br />

to XCB, and change its source file value to YXCBLSRC.<br />

1 Source in an alternate source file in the generation library with object in the generation<br />

library.<br />

Create an XCB object code.<br />

2 Source in an alternate source file in the generation library with objects in a library other<br />

than the generation library.<br />

Create an XCB object code.<br />

On the Environment Object Code Override panel, change the object library to the<br />

library you want to store the EXCUSRPGM object in.

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

Saved successfully!

Ooh no, something went wrong!