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.

<strong>Implementer</strong> Data Areas<br />

This value affects jobs evoked on the host after a remote initiated move is submitted on the<br />

remote. The valid data area values are *YES or *NO enclosed in single quotes. The default<br />

value ‘*NO’ allows logging as currently defined. The value *YES changes the job to log CL<br />

instructions with the maximum message logging level 4 0 *SECLVL. This ensures logging of<br />

all messages and retains the job log upon job termination.<br />

Submit Multiple Jobs (IMMULTJOB)<br />

The IMMULTJOB data area allows you to submit multiple jobs when submitting promotion<br />

requests. Valid values for the data area are *YES or *NO enclosed in single quotes. The<br />

default value ‘*YES’ allows the submission of multiple jobs. The value *NO does not submit<br />

multiple jobs.<br />

Once a promotion request is submitted <strong>Implementer</strong> determines whether the request was<br />

submitted to multiple jobs or a single job. This requires:<br />

The Add related objs to request field set to N (in Work with Environments) for all target<br />

environments on the request.<br />

The Compile required field set to N (in Work with Environments) for all target<br />

environments on the request. If Compile required=Y, the compile phase must be<br />

complete.<br />

For requests that target multiple environments or an environment group, you cannot use<br />

the Move Request by System/Environment option to override the request and submit<br />

the move on a per-environment basis.<br />

For requests that target a specific system, you cannot use the Move Request by System/<br />

Environment options 10=Distribute all, 11=Move all, or 12=Distribute and move all, to<br />

submit the distribution or move.<br />

Multiple Object Single Source Check Out (IMMULTOBJ)<br />

The IMMULTOBJ data area allows you to check out multiple objects that have single source<br />

members, allowing the single source member to create multiple objects. This practice, most<br />

common with physical files, works for all source-based objects.<br />

The valid values for the data area are *YES or *NO enclosed in single quotes. The default<br />

value ‘*NO’ does not allow checking out an object that has multiple objects with the same<br />

source member. Set the value to *YES to allow checking out an object that has multiple objects<br />

with a single source member.<br />

IMPORTANT Checking out a single source member with multiple objects is not<br />

considered a concurrent development condition. Therefore, if you enable<br />

IMMULTOBJ, be aware you could easily overwrite changes to work in process—<br />

that is, objects checked out and changed but not promoted through to production.<br />

407

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

Saved successfully!

Ooh no, something went wrong!