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 3: <strong>Implementer</strong> <strong>Administration</strong><br />

128<br />

Control source archiving in <strong>MKS</strong> Source (requires active integration between<br />

<strong>Implementer</strong> and <strong>MKS</strong> Source). For details, see “<strong>Implementer</strong> and <strong>MKS</strong> Source<br />

Integration” on page 259.<br />

Key Considerations<br />

You can define object codes at three levels: object code, environment, and system. Object<br />

codes defined at the object code level and environment level can be activated or<br />

deactivated for one or all environments. Object codes defined at the system level can be<br />

activated or deactivated at the system or environment level.<br />

Object codes must be active and enabled to the specific environment before you can use<br />

them. Inactive object codes cannot be used within <strong>Implementer</strong>.<br />

When you make an object code inactive, <strong>Implementer</strong> retains any existing environment<br />

overrides. To reactivate, simply change the value of the Activity flag field. Reactivating<br />

the object code also reactivates the environment overrides.<br />

When defining object codes for source members and corresponding objects with<br />

different names, object codes that use a creation command with the SRCMBR parameter<br />

(for example, CRTPLIPGM) must specify the keyword #SRCMBR in the Source Member<br />

Name parameter. In the Creation command field, add SRCMBR(#SRCMBR.<br />

After editing object codes for an environment that has source and object with different<br />

names, run the Build List, option 30 in Work with Environments. For details, see<br />

“Environment Repository Build” on page 117.<br />

When using the SQLTABL (for physical files) and SQLINDX (for logical files) object<br />

codes, you must check out all related PFs and LFs together—implicit LF processing does<br />

not occur.<br />

To create or change an object code<br />

1 From the <strong>Implementer</strong> Menu, select option 44, Object Codes, or type STRIM<br />

(*WRKOBJCDE) at the command line, and press ENTER.<br />

2 Do one of the following:<br />

To add a new object code, press F6=Add. The Create Object Code panel displays.<br />

To copy an existing object code, type 3 in the Opt field and press ENTER. The Create<br />

Object Code panel displays.<br />

To change an existing object code, type 2 in the Opt field and press ENTER. The<br />

Change Object Code panel displays.

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

Saved successfully!

Ooh no, something went wrong!