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.

Chapter 5: <strong>MKS</strong> Integrity Integration<br />

258<br />

In the event an issue being processed does not exist, the change package entry log is updated<br />

to indicate that no updates were performed for the issue and no future updates will occur for<br />

the issue. Although no updates occur, the change package entry log is updated to reflect the<br />

issue posted to ensure further updates are not attempted.<br />

If an invalid action or workflow conflict occurred while the emergency update mode was<br />

active, for example, a promotion that would not normally be allowed based on the current<br />

state of an issue, the update to <strong>MKS</strong> Integrity does not occur during the update because it<br />

will only fail. This is a warning condition; as such, it is left for the administrator to ensure the<br />

issue is set to the proper state.<br />

After successfully applying the pending updates, a message of the update results is sent to<br />

the user defined as the iSeries Notify User. If no pending updates exist, a message at the<br />

bottom of the panel confirms this.<br />

Apply Pending Changes Command Option<br />

You can apply pending changes by using a menu interface or by using the Apply Pending<br />

Changes (IAPYPNDCHG) command. You can issue the command from the command line or<br />

embed into a user-defined program. The command has no parameters.<br />

IMPORTANT Before applying pending changes, you must ensure the emergency<br />

update mode is not active.<br />

To apply pending changes, use one of the following options<br />

From a command line, issue the following command:<br />

APYPNDCHG<br />

From the <strong>Implementer</strong> Menu, type option 47, <strong>MKS</strong> Integrity, and press ENTER or issue<br />

the command STRIM *INTMGRSET. The <strong>MKS</strong> Integrity Setup panel displays.<br />

a) Determine whether <strong>MKS</strong> Integrity is available by the value in the System Available<br />

field.<br />

b) Determine if pending changes exist by the value in the Pending Changes field. If<br />

pending changes exist, press F9=Apply Pending Changes.<br />

Apply Pending <strong>MKS</strong> Integrity Changes Report<br />

The Apply Pending <strong>MKS</strong> Integrity Changes report generates automatically when you apply<br />

pending changes by using the menu interface or the command interface. The report generates<br />

to the spool file of the user profile who ran the apply pending changes job. The spool file<br />

name is IMPNDCHG.<br />

The report includes the following information:<br />

date and time the update ran

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

Saved successfully!

Ooh no, something went wrong!