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.

Object Version Stamping<br />

number to the right of the decimal increments by one. When promoted to production, the<br />

number to the left of the decimal increments by one and the number to the right of the<br />

decimal resets to zero.<br />

NOTE Promoting without locks causes the version number to increment only when<br />

the object is promoted to a *PRD environment.<br />

Scenario Example<br />

Object A in *PRD environment is version 2.0. Object A is checked out to *TST<br />

environment. Object A in *PRD is still 2.0. Object A in *TST is version 2.1.<br />

Object A version 2.1 is promoted to *QAC environment.<br />

Object A is concurrently checked out to *TST environment, making it version 2.2.<br />

Object A in *PRD is still version 2.0. Object A in *QAC is still version 2.1.<br />

Object A version 2.2 is promoted to *QAC environment. Object A now has two lock<br />

records in the *QAC environment—one is version 2.1 and the other is version 2.2.<br />

Object A version 2.2 in *QAC is promoted to *PRD. Object A in *PRD environment is<br />

now version 3.0.<br />

Method 3: User-Defined Version<br />

You can define a program with a versioning scheme of up to 30 characters, which is the<br />

length of the Revision field that displays on various panels in <strong>Implementer</strong>. However,<br />

because the field updated in the actual object description is only seven characters long, only<br />

the first seven characters of the version number are recorded in the object’s description. Thus,<br />

to update the object description parameter on the actual object, define your program with a<br />

number scheme of seven characters or less. To apply object versioning without actual object<br />

stamping, the versioning scheme can be up to 30 characters.<br />

The versioning program must exist in the same library on all host and remote systems. If the<br />

program references objects, for example, files or data areas, the library containing the objects<br />

must be in the user’s interactive library list and in the library list of the <strong>Implementer</strong> job<br />

description MWIJOBD.<br />

Define your versioning program with an entry parameter group as described next.<br />

Parameter Length Description<br />

Description 512, alpha Data passed into the versioning program. See format<br />

requirements in the next table.<br />

Version Number 30, alpha Parameter the version number is returned in.<br />

Return Value 10, alpha Returns blanks if no errors occur. If a value is returned, the<br />

version number is ignored.<br />

149

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

Saved successfully!

Ooh no, something went wrong!