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.

Description Parameter Field Parameter Value Passed<br />

Object Code Object code<br />

Function '*PROMOTE'<br />

Action Value of the Action field in subfile<br />

Considerations With OS/400 and <strong>Implementer</strong><br />

Considerations With OS/400 and <strong>Implementer</strong><br />

PRD Environment *PRD environment of FROM environment<br />

PRD Library *Blanks<br />

This section covers iSeries system information as it relates to <strong>Implementer</strong> and <strong>Implementer</strong><br />

Receiver.<br />

Operating System Upgrades<br />

The following considerations apply to installing a new release of the OS/400 operating<br />

system. No special considerations are required for PTF installation.<br />

Before you upgrade to a new release of the operating system, contact your distributor or<br />

<strong>MKS</strong> Customer Care to determine any impact the new release may have on your version<br />

of <strong>Implementer</strong>. At publication of this guide, <strong>Implementer</strong> required no changes for<br />

compatibility with the versions of OS/400 currently supported.<br />

If you use <strong>Implementer</strong> Receiver to distribute changes to a remote system, you may have<br />

changed communication entries when you initially installed <strong>Implementer</strong>. After the<br />

operating system upgrade, you must verify and reapply the changes as needed—this<br />

step is frequently overlooked.<br />

By default, an OS/400 upgrade does not retain the <strong>Implementer</strong> communication entry<br />

because the default communications subsystem QCMN is in library QSYS, and the<br />

objects in library QSYS are replaced during the operating system upgrade/installation.<br />

Before the upgrade, you can move subsystem QCMN to another library such as QGPL,<br />

or after installing the new release, you must reapply the communications entry to the<br />

QCMN subsystem.<br />

If you upgrade the host system to a release level later than the release level of the remote<br />

system, verify <strong>Implementer</strong> is set up to distribute using the previous release support<br />

feature of OS/400. To do this, in <strong>Implementer</strong>’s Network Configuration, change the<br />

target release to the version of the operating system on the remote system. To determine<br />

the previous versions the host OS/400 version allows, verify the allowed values for the<br />

Target Release (TGTRLS) parameter on the Restore Library (RSTLIB) command.<br />

153

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

Saved successfully!

Ooh no, something went wrong!