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 />

66<br />

3 When you have finished entering the information, press ENTER to update the<br />

information and return to the <strong>Implementer</strong> Menu.<br />

System Control Maintenance Field Descriptions: Panel 1<br />

Field Description<br />

Company name Specify the name to display on the <strong>Implementer</strong> Menu and on <strong>Implementer</strong><br />

reports (usually the <strong>Implementer</strong> licensee name).<br />

Next request number Specify the next request number to issue. A request number is the unique,<br />

four-character alphanumeric identifier assigned by <strong>Implementer</strong> when you<br />

create a new promotion request.<br />

Beginning with number 0001, the number increments by one for each new<br />

promotion request. When 9999 is reached, the left most position changes<br />

to an alpha character and the other positions reset to 0 (zero). Reading<br />

from right to left, the cycle continues until each position goes through the<br />

range 0–9, and A–Z. When number ZZZZ is reached, the number scheme<br />

automatically resets to number 0001. The maximum number of available<br />

request numbers before resetting is 1,200,000.<br />

Delete compile<br />

listings<br />

Message queue<br />

delivery<br />

CAUTION You usually do not change this value. If you change it, you must<br />

specify a number that does not overwrite existing request numbers.<br />

Specify whether to delete compile listings after successful promotions.<br />

Compile listings are located in the output queue specified by the interactive<br />

job when a request is submitted to compile.<br />

Y: Cancels all successful compile listings and retains all unsuccessful<br />

compile listings. Eliminates the disk space requirements of retaining all<br />

compile listings. Successful compiles ensure source-to-object integrity;<br />

typically, you do not need to retain these job logs.<br />

N: Retains all successful and unsuccessful compile listings. Use with<br />

caution; can cause excessive spool files.<br />

Specify how to deliver messages to the user workstation.<br />

*BREAK: Displays messages immediately.<br />

*NOTIFY: Notifies the user of pending messages. Includes turning on a<br />

message light and sounding a buzzer (if available).<br />

*HOLD: Retains messages in the message queue for the user to display.<br />

*SAME: Uses the same message notification as the previous message.<br />

*DFT: Answers messages requiring a reply with the default message<br />

reply. Does not add messages to the message queue.

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

Saved successfully!

Ooh no, something went wrong!