Siemens Saturn Epabx Oc1e Dyad Digital Telephone User Instructions

							SATURN EPABX A30808-X5051-E120-I-8919 - 
CMU Procedures Issue 1, December 1984 
SECTION 1 .OO 
1.01 Purpose. This practice is intended as an aid to the user 
responsible for establishing and maintaining the customer 
memory portion of the SATURN Electronic Private Automatic 
Branch Exchange (EPABX); this process is called “Customer 
Memory Updating (CMU).” Descriptive data is provided herein 
to allow the user to make changes to the customer portion 
of the system memory. Table 1.00 lists the mnemonics used 
in this practice. 
When .DPI appears in text or CMU prompts, it refers to the 
Siemens line of Digital Premium Instrument (DPI) telephones. 
1.02 Scope. Section 2.00 presents oeneral information per- 
INTRODUCTION 
vides reference data that is required in some of the CMU 
procedures. Section 4.00 of this practice itemizes the equip- 
ment and documentation that is required to initiate the CMU 
session. The methods of implementation, and examples of 
each, are provided in Section 5.00. 
Following Section 5.00, a glossary of CMU-procedure terms 
is presented in Appendix A; Appendix B provides the proce- 
dures for accessing the system via a data terminal, to enable 
the user to input the CMU procedures, as well as an exam- 
ple of a typical CMU procedure. 
Finally, Appendixes C, D, and E respectively provide an in- 
dex to all of the CMU orocedures bv title and command. and 
the actual SATURN CMU procedures. 
taining tothe system and the CMU process. Section 3.00 pro- 
Table 1.00 Mnemonics Used in This Practice 
MNEMONIC 
ASCII 
CAS 
CMU 
cos 
CPU 
DCI 
DISA 
Kl 
DTMF 
EIA 
EPABX 
LSI 
MMLP 
MS 
oc II 
PCB 
PEF 
PEN 
SLT 
SMDR 
UCD DEFINITION 
American Standard Code for Information Interchange 
Centralized Attendant Service 
Customer Memory Updating 
Class of Service 
Central Processing Unit 
Data Communications Interface 
Direct Inward System Access 
Dial Pulse 
Digital Premium Instrument 
Dual-Tone Multifrequency 
Electronics Industries Association 
Electronic Private Automatic Branch Exchange 
Large-Scale Integration 
Man-Machine Language Processor 
Main-Satellite 
Office Communications II 
Printed Circuit Board 
Plain English Format 
Port Equipment Number 
Single-Line Telephone 
Station Message Detail Recording 
Uniform Call Distribution 
l-1 (1-2 blank)  
						

							SATURN EPABX A30808-X5051-ElZO-Z-B919 
CMU Procedures Issue 2, May 1986 
Tabie 1.01 Customer Memory Update Matrix Chart 
CUSTOMER CUSTOMER MEMORY UPDATE ISSUE NUMBERS FOR 
MEMORY SATURN III AND IIE SOFTWARE RELEASES 
UPDATE 
PROCEDURE SATURN III SATURN IiE 
NAMES ’ Ref Release 13.1 Release 1.1 COMMENTS 
ACDGRP 205 1 1 
ACDSCAN 810 2 2 
ALMDATA 522 1 1 
ATTASSN 303 3 3 4 
ATTMAP 304 2 2 
I AUDIT 524 1 1 
I 1 I 
I 
I , I 
AUTHCODE 406 1 1 
I COMMAND 590 1 1 
I ’ I I 
CONFASSN 507 1 1 
I 1 I I 
I 
COSASSN 
CUSTDATA 551 1 
DATAASSN 261 1 1 
-. 
DATACOS 460 2 2 
DIDCONV 103 1 1 
DPIASSN 216 1 1 
I LCRDPLN 900 I 
1 
I 1 I 
LCRODR 903 1 1 
LCRROUTE 902 1 1 
LCRSCC 906 2 2 
:_ 
LCRSCHD 904 1 1 
MODMASSN 561 1 1  
						

							I - ___ 
SATURN EPABX 
CMU Procedures A30808-X5051-E120-2-6919 
Issue 2, May 1986 
Table 1.01 Customer Memory Update Matrix Chart (Continued) 
PROCEDURE 
1-3 (l-4 blank)  
						

							SATURN EPABX 
CMU Procedures A30808-X5051-E120-l-B919 
Issue 1, December 1984 
SECTION 2.00 THE SATURN SYSTEM 
2.01 General. The SATURN EPABX uses software- 
programmed switching techniques. The system software is 
contained in two basic areas: generic and customer memory. 
Switching control, performed by the Central Processing Unit 
(CPU), uses data which is stored in the generic software. The 
system includes a wide range of features to satisfy a variety 
of telephone system requirements. The software that controls 
these features resides in the customer memory area, and is 
alterable via the CMU procedures. (The generic software may 
not be altered by the customer.) 
Because the features may be controlled by the customer, an 
extremely flexible selection and arrangement of the large num- 
ber of features is possible. In most cases, the features are 
provided and controlled exclusively by the software routines 
and require no additional hardware. These features may be 
added, changed, or deleted by entering the appropriate in- 
put commands. In some cases, hardware modifications may 
be required. These modifications may require the installation 
of one or more Printed Circuit Boards (PCBs), or strapping 
modifications to existing hardware. Activation of the feature 
via software is done after completion of any such hardware 
or wiring changes. 
Changes to the system may be made by inputting coded in- 
structions via a data entry terminal. The instructions consist 
primarily of actions and commands, and alphameric 
responses to questions. 
2.02 Customer Memory Update Prgcedures. Each of the 
CMU procedures is identified by title and by a command name 
mnemonic. The various CMU procedures include routines for 
implementing changes in the following areas: 
‘* Centralized Attendant Service (CAS) 
l Main Satellite (MS) 
l Office Communication (OC IE) 
l Trunks 
l Stations 
l Attendant Console(s) 
l System Features l Station Message Detail Recording 
l . Traffic Metering 
l Least Cost Routing 
l Maintenance 
Some procedures consist of closely-related functions 
that 
need to be considered together to maintain data base con- 
sistency. Therefore, if a change is made to the data base by 
a procedure within a certain category, other procedures in the 
same category may also need to be used, particularly dur- 
ing initial programming of the system. The system prompts 
the user, via error messages, about the other procedures 
to 
ensure that an inconsistency is not accidentally introduced 
into the data base. 
Within each of the above categories, one or more CMU 
proce- 
dures comprise a group pertaining to a specific alterable area, 
to allow complete flexibility of assignment within that category. 
Examples of such groups include: definitions; group variables 
and night service; feature access code assignments; and, 
mis- 
cellaneous assignments. There is no strict ordering of these groups because the various CMU procedures may change 
from time to time, or new CMU procedures may be added. 
The administrable features of the SATURN system are 
cate- 
gorized into individual operational procedures, using the above scheme. Each procedure is identified by a distinct CMU 
procedure command name mnemonic. 
2.03 Siemens Customer Support Services. Siemens 
main- 
tains a nationwide network of field service offices. Contact 
the Siemens regional office for any assistance which may 
be 
required.  
						

							SATURN’EPABX 
CMU Procedures A30808-X5051-E120-I-8919 - 
Issue 1, December 1984 
SECTION 3.00 REFERENCE DATA 
3.01 Requirements. Certain reference data should be on 
hand prior to beginning the CMU session. Some of this data 
(e.g., trunk type definitions) is required information when in- 
putting certain CMU procedures. The following paragraphs 
describe the reference data that should be available. 
3.02 Siemens SATURN Practices. A current copy of this prac- 
tice, or a working knowle.dge of its contents, is required plus 
the latest field change information affecting this practice. (This 
may consist of one or more addendums or other supplemen- 
tal information.) Supporting practices, such as Data Base 
Preparation, Feature Descriptions, etc., should also be avail- 
able for reference, particularly for the inexperienced user. The 
practices issue numbers and dates for the SATURN 111111 
EPABX are listed in the appropriate Practices Documentation 
Index: 
l SATURN II Practices Documentation Index 
A30808-X5049-AlgO- * -8987 
l SATURN III Practices Documentation Index 
A30808-X5050-AlgO- * -8987 
3.03 Timers. The SATURN System contains a variety of timers 
for various call-processing functions and-feature operations. 
Most of their values may be changed via the CMU procedures. 
Six trunk group timers may be changed via the Trunk Group 
(TRKGRP) procedure, all remaining timers may be changed 
via the System Timer (SYSTIMER) procedures. 
3.04 Access Levels and Security Keys. All areas of the 
SATURN EPAPX memory are protected against unauthorized 
access. The customer memory has been divided into five ac- 
cess levels. Levels 1 to 4, as indicated in the individual CMU 
procedures, are available to the customer for the addition, deletion, or change of data. The “Display,” “End,” and “Help” 
actions may be accessed by any security level. Level 5 is re- 
served for Siemens use. A character security key is assigned 
to each access level. Entering the correct security key for an 
access level provides access to that level and all lower lev- 
els. For example, proper (authorized) access to level 3 per- 
mits the user to access levels 1, 2, and 3, but not level 4. The 
required access level is specified on each CMU procedure. 
The SATURN EPAPX is delivered with security keys assigned 
by Siemens in the supplied feature program disk. The secu- 
rity keys are assigned by the Siemens marketing activity, who 
should be contacted for anything pertaining to this subject. 
Because of their obvious protective purpose, th?,security keys 
are intended to be given to the exclusive custody of the proper 
customer authority, who may then assign accessibility to differ-. 
ent levels of the data base to system users on a selective 
basis. 
The user is required to enter the security key at the begin- 
ning of each CMU session, during the logon procedure. This 
action is required for each CMU session. The key is then com- 
pared against a list stored in the memory. A “match” must 
occur in order for the user to proceed. (The key code is not 
“echoed” to the printer to prevent unauthorized users from 
obtaining same.) If the key code is accepted by the system, 
the program advances to an initial prompting statement on 
the printout, which requests further procedure information to 
be entered. 
Security keys that are not assigned to the system (invalid 
keys), unassigned procedures, or mismatched key-to- 
procedure command information results in error conditions 
which halt the CMU program and require that the correct in- 
formation be entered as directed by the system prompts. 
3-l (3-2 blank)  
						

							SATURN EPABX 
CMU Procedures A30808-X5051-E120-l-B919 
Issue 1, December 1984 
SECTION 4.00 PREPARATION 
4.01 Reference Items. The user making the CMU changes 
may wish to have certain items on hand prior to beginning 
the CMU session. The following paragraphs list the items 
which might be helpful. 
4.02 Data Entry Terminal. A standard keyboard/printer data 
terminal that provides alphameric input is recommended for 
inputting the CMU procedures. The terminal must be e- 
quipped with an appropriate interface corresponding to Elec- 
tronic Industries Association (EIA) specification RS-232-C. 
The user may enter the CMU changes as described in Ap- 
pendix B. Further, the CMU software includes instructions for 
automatic line feed during data entry, thus reducing the num- 
ber of operations required to input data. 
4.03 Security Key Data. The necessary security key data list- 
ed in the applicable site documentation must be known for 
access to the appropriate level (or levels) during the CMU 
session. 
4.04 Data Base Preparation Tables. The data base prepa- 
ration tables that were completed for this site should be avail- 
able. These tables list all of the various changeable system 
features, trunk and station assignments, toll restrictions, etc., 
and therefore may be used to determine if the proposed CMU 
changes are compatible with the system and the installation. 
Any changes implemented should be documented in these 
tables. 
4.05 Site Configuration Documentation. The specific site 
configuration documentation should be available. This docu- 
mentation ,includes any hardware layout drawings, cabling 
information, and other system assignment data. As with the 
data-base tables, this documentation may be used to deter- 
mine if the proposed CMU changes are compatible with the 
system and the installatiqn. 
4.06 Local Entry of Data. The CMU process can be made 
at the on-premises location by connecting the data terminal 
to the service terminal connector. 
4.07 Remote Entry of Data. Remote entry of data may be 
made via a modem. For detailed information, refer to the Sie- 
mens Installation and Maintenance practices. 
Once the remote data connection is established, the key- 
board/printer receives its first prompt message. The user can 
now proceed with the CMU process. 
NOTE: If the initial prompt is not printed after establishing 
the connection at a remote location but other data 
is received, do not make further entries via the ter- 
minal. This situation may occur when CMU proce- 
dures, diagnostic testing, or traffic metering is being 
performed locally at the SATURN EPAPX. 
Remote operation can be resumed when the initial prompt 
is received. 
4-1 (4-2 blank)  
						

							SATURN EPABX 
CMU Procedures A30808-X5051-E120-l-B919 - 
Issue 1, December 1984 
SECTION 5.00 IMPLEMENTATION 
5.01 User Information. The following paragraphs describe 
the nature of how to access the system (known as “logon”), 
selecting the mode of input to be used, information on prompt- 
ing and commands available, error messages, functions of 
the service terminal, and examples of actual CMU inputs to 
the system. Because a number of terms may be unfamiliar 
to the user, Appendix A provides a list or glossary of such 
terms that are common to the CMU procedures used in the 
SATURN EPAPX. 
5.02 Service Terminal Functions. Certain functions must be 
provided by the service terminal in order for some CMU proce- 
dures to be run. Table 5.00 is a list of those functions and the 
American Standard Code for Information Interchange (ASCII) 
codes associated with them. 
5.03 Accessing the System. After the terminal is connected 
to the system, and the system is operational, the system ini- 
tially prompts the user with a message indicating the system 
software release level and the customer site identification. An 
example of this message is shown in Figure 5.00. 
NOTE: The security key is not printed (nor displayed) dur- 
ing entry, to prevent unauthorized users from ob- 
serving same. 
AC-SAT AOS 8.06-DB 8.1-PL:055 SITE: ESS-CHICAGO 
PLEASE ENTER PASSWORD ) 
Figure 5.00 Initial System Prompt for Password 
The system then responds with the two-line response mes- 
sage shown in Figure 5.01. The response includes the date 
(YY-MM-DD), representing the year, month, and day, and the 
time (HH:MM:SS), representing the hour, minute, and se- 
conds, based on a 24-hour clock. For example, 1:00:00 PM 
is represented by 13:OO:O0. The second line of output prints 
the character ‘I)“, which indicates that the system is ready 
for the next input by the user. 
YY-MM-DD HH:MM:SS 
> 
Figure 5.01 System Response to Proper Password 5.04 Prompting. The CMU procedures use plain English 
prompting, consisting of words and phrases that are readily 
understood. Figure 5.02 shows an example of a prompt for 
“Class of.Service Number” after the user has inputted the 
action and command “CHANGE COSASSN” (to change a 
class of service definition). 
> CLASS OF SERVICE NUMBER (O-31)= 
Figure 5.02 Example of Plain English Prompt 
5.05 Actions and Commands. The system provides complete 
flexibility for the display, addition, change, and deletion of data 
(actions) within the customer memory, plus a number of other 
functions. These actions are associated with specific CMU 
procedure names (commands). Each command may allow 
one or more of these actions. The actions allowed in the sys- 
tem are shown in Table 5.01. The commands are listed in Ap- 
pendix D. 
Not all of these actions are appropriate for each CMU com- 
mand; however, those actions which are appropriate for a 
given command are specified within the procedure at the end 
of this practice. Note that either the first three characters of 
the action may be entered, or the complete action name. The 
system is arranged to accept either entry. 
5.06 System Help File. The system also includes a “help” 
file to aid the user. With this file, the user need only enter the 
action “HELP” followed by a space and the appropriate com- 
mand name, and the system outputs all of the actions, 
parameter types, and ranges of data requested as input for 
that particular command. This arrangement is useful when 
a user is familiar with the system, but has not used a particu- 
lar command for some time. For example, to obtain general 
information pertaining to the CMU procedure for System 
Timers, the user enters “HELP SYSTIMER”, and the system 
responds appropriately, as shown in Figure 5.03. 
) HELP SYSTIMER 
ACTION = DISPLAY 
*** PROMPT *** 
VARIABLE SYSTEM TIMER 
ACTION = CHANGE 
*** PROMPT *** 
VARIABLE SYSTEM TIMER 
TIMER VALUE (O-65535 TENTH SECS) 
ACTION = SAVE 
ACTION = CANCEL 
> PARAMETER MlNl MAX VALID RESPONSES 
I/ 10 MNEMONICS 
PARAMETER MlNl MAX VALID RESPONSES 
REQUIRED l/ 1 MNEMONICS 
REQUIRED I/ O-65535 NUMERIC VAL 
Figure 5.03 Example of Help File - Without Parameter Variables 
5-l  
						

							SATURN EPABX A30808-X5051-E120-i-B919 
CMU Procedures 
Issue 1, December 1984 
Table 5.00 Service Terminal Functions 
ASCII CODE 
FUNCTION 
NAME 
(HEX) 
CONTROL 
Cancel session (logoff) 
Cancel previous character 
Enter contents of input line 
Return to start of procedure 
Request next portion of output 
Reprint last entry (all data inputted since last prompt) 
Cancel current input line (must be used prior to 
depressing the RETURN key) CONTROL + C 
BACKSPACE 
CARRIAGE RETURN 
ESCAPE 
ENTER or RETURN 
CONTROL + E 
CONTROL + U 03 
08 
(CR) OD 
WC) 1B 
U-F) OA 
WQ) 05 
(NW 15 
DATA 
Numeric digits 
Alphabetic characters o-9 30 - 39 
A-Z 41 - 5A 
Table 5.01 Actions for CMU Procedures 
INPUT CHARACTERS 
DIS -or- DISPLAY 
ADD DESCRIPTION 
DISPLAY. Prints out the existing values contained in the system data base. If the command 
is followed by a specific value, the system displays the data for that value. NOTE: The majority 
of CMU procedures allow a carriage return (CR>, or RETURN key, to represent “display all.” 
ADD. Adds one or more values to data base. If the value(s) should be unique and already 
exists, the user is alerted via an appropriate output message. 
DEL -or- DELETE 
DELETE. Removes a value from the system data base. (Certain resources must be placed 
out of service prior to being deleted.) 
CHA -or- CHANGE 
CHANGE. Substitutes one or more new values for existing value(s). 
INS -or- 
INSERT 
INSERT. Adds one or more values to data base following specified position(s); used when 
necessary to maintain a strict order of values in data base. 
SAV -or- SAVE 
SAVE. “Saves” the changes made to this point during this CMU session, by making it im- 
possible to do a “Cancel.” NOTE: The SAV CUSTDATA CMU procedure must still be per- 
formed to save these changes to disk. 
CAN -or- CANCEL 
CANCEL. Ignores all changes performed during the current CMU command session since 
the last SAVE command was used. NOTE: the CANCEL function is not applicable after leav- 
ing a CMU command. 
HEL -or- HELP 
HELP Provides a printout of the various parameters and their value ranges within the par- 
ticular CMU procedure code. 
BEG -or- BEGIN 
BEGIN. Initiates a particular function (e.g. SMDR) within the system that may be activated 
or deactivated by the user. 
END 
END. Terminates a particular function within the system that may be activated or deactivat- 
ed by the user. 
ST0 -or- STOP 
STOP Halts a particular function (e.g. SMDR) within the system that has been activated 
by the user. Some routines allow the function to be halted temporarily. 
As a further enhancement of the Help file, the same proce- 
dure as described above, plus the appending of the question 
mark (?) after the command name, provides the same data 
as described plus the actual mnemonics (or other symbols, 
such as Y for Yes, N for No, etc.) that are acceptable for input for each parameter. Figure 5.04 provides an example of the 
same input as described above (and reflected in Figure 5.03), 
plus the appending of the question mark, and the resulting 
output by the system. Note that the system indicates whether 
parameters are optional (OPT) or required (REQ). 
5-2  
						

							SATURN EPABX 
CMU Procedures A30808-X5051-E120-l-B919 - 
Issue 1, December 1984 
)HELP SYSTIMER ? 
ACTION = DISPLAY 
*** PROMPT *** 
PARAMETER MlNl MAX VALID RESPONSES 
VARIABLE SYSTEM TIMER OPTIONAL 1/ 10 MNEMONICS 
INTRDGT TRKANSPRI DTDELAY CBACT CBRING STANDBYQ LOWTONE FWDNOANS CWTONE DISADELAY 
ATTGONE NOANSADV ATTHOLDRCL STNHOLDRCL PARKRCL CAMPRCL NOANSRCL LOCKOUT ANSUPV 
VOICEREJ OVRDAUTO SERIAL TRKDISC INCPTREC UCDREC DATASPEED DATACONN STNHFMIN MODEMRESP 
DATACODE IGNOREHF CBDELRNG SZACKFAIL TRKRLS LCRONHKQ LCRONHKQTN LCRONHKFIL LCRRETRY 
LCREXTCB TRKTRBL STNONHK CALLWAITON CALLWAITOFF RNGBURST RLTNOANS NOANSOUTG CODECALL 
DIALTONE TlWTNOALM LPSDISC AUDMSG 
ACTION = CHANGE 
*** PROMPT *** 
PARAMETER MlNl MAX VALID RESPONSES 
REQ VARIABLE SYSTEM TIMER REQUIRED I/ 1 MNEMONICS 
INTRDGT TRKANSPRI DTDELAY CBACT CBRING STANDBYQ LOWTONE FWDNOANS CWTONE DISADELAY 
ATTGONE NOANSADV A-I-THOLDRCL STNHOLDRCL PARKRCL CAMPRCL NOANSRCL LOCKOUT ANSUPV 
VOICEREJ OVRDAUTO SERIAL TRKDISC INCPTREC UCDREC DATASPEED DATACONN STNHFMIN MODEMRESP 
DATACODE IGNOREHF CBDELRNG SZACKFAIL TRKRLS LCRONHKQ LCRONHKQTN LCRONHKFIL LCRRETRY 
LCREXTCB TRKTRBL STNONHK CALLWAITON CALLWAITOFF RNGBURST RLTNOANS NOANSOUTG CODECALL 
DIALTONE TlWTNOALM LPSDISC AUDMSG 
TIMER VALUE (O-65535 TENTH SECS) REQUIRED I/ 1 O-65535 NUMERIC VAL 
ACTION = SAVE 
ACTION = CANCEL 
Figure 5.04 Example of Help File - With Parameter Variables 
Table 5.02 Error Messages and Recommended User Action 
NO. ERROR MESSAGE RECEIVED RECOMMENDED USER ACTION 
1 
INVALID PASSWORD ENTERED Reenter PASSWORD; no spaces or characters are allowed. 
2 
INVALID ACTION ENTERED User entered an ACTION which was not valid for the COMMAND 
specified. Check and reenter ACTION and COMMAND. 
3 
OVERLAY FILE NOT AVAIlABLE File is unreadable from disk, either because the file is not present, 
or it cannot physically be read from disk. 
4 
OVERLAY MEMORY NOT AVAILABLE Another overlay is currently active, and resides in the overlay memory 
area. Perform an “END” on the current active overlay in order to load 
in the new command. 
5 INVALID COMMAND NAME 
User entered a COMMAND that is not supported for this system. 
Check and reenter ACTION and COMMAND. 
6 
INVALID I UNKNOWN KEYWORD User made an entry that is inappropriate or is not recognized for this 
COMMAND. Check and reenter. 
7 
INVALID PARAMETER VALUE 
User entered value for a parameter that is not valid; check and reenter 
parameter value. 
8 
EXCESS PARAMETER VALUES 
User entered too many values for a parameter; check and reenter 
allowed value(s) only. 
9 
MISSING PARAMETER VALUES User has not entered a value, or too few values when a range is 
specified. 
10 
CONFLICTING COMMAND EXECUTING User has entered a COMMAND to the system while the system is 
currently acting upon another COMMAND. 
11 
COMMAND EXECUTION UNAUTHORIZED User password level does not allow execution of command; only a 
higher-level password may execute the command. 
12 
“SAVE” INVOKED DUE TO “DISK ERROR” The CMU procedure was unable to retain a “CANCEL” record of the 
changes and has therefore “SAVED” the changes in system memory. 
These changes cannot be cancelled by performing the CANCEL 
action. The SAVE CUSTDATA CMU procedure must still be performed 
to save these changes to disk. 
5-3  
						

							SATURN EPABX 
CMU Procedures A30808-X5051-E120-l-8919 
Issue 1, December 1984 
5.07 Inputting Changes. Inputting CMU changes makes 
extensive use of alphameric actions and commands. This 
format has been arranged for both the novice and the 
experienced user, who will find the routines easier to remember, 
providing significant reductions in CMU entry time. The input 
instruction is entered sequentially, using prompting, followed 
by the depression of the RETURN key. The system states that 
the operation was successful or an error condition occurred, 
after each input. The general input form is: 
a. Key in the procedure action and command, and depress 
the RETURN key. 
b. Key in the appropriate parameters requested by each 
prompt, separating the multiple parameters, when 
appropriate, with spaces. 
c. Following the entry of data for each required parameter, 
depress the RETURN key. 
NOTE: When inputting data that represents a PEN of the 
form WXYZ, all leading zeroes must be keyed in, as 
appropriate. Leading zeroes are not required for other 
types of entries. For example, PEN 0007 (WXYZ = 
0007) requires the keying of digits 0, 0, 0, and 7, 
whereas station number 37 (AAAA = 0037) requires 
the keying of digits 3 and 7 only. 
Additional guidance is found in the Data Base 
Preparation Tables. 
5.08 User Shortcuts. The software provides some “shortcuts” 
to aid the user during lengthy CMU sessions. Special use is 
made of the semicolon (“;“) during the entering of data, and, 
in some cases, just the RETURN key. For example, if the user 
is in the middle of a routine that includes many optional 
parameters (e.g., STNCOS), and the user requires to make only 
a few changes near the beginning of the CMU procedure, the 
semicolon is appended to the last inputted character prior to 
depressing the RETURN key. If there are no more additional 
required parameters, the user is returned to the initial prompting 
point within that CMU procedure, indicated by the I‘).” However, 
if the additional parameters are required, the system outputs 
an error message and reprompts the user for the proper input. 
Upon completion of all data entries within a CMU procedure, 
the user may wish to perform additional entries within that same 
CMU action and command. For example, if the user is inputting 
a number of Station Assignments (using ADD STNASSN) as 
each complete station assignment is complete, the user may 
reinitiate prompting at the beginning of that same action (e.g., 
ADD STNASSN) by just depressing the RETURN key. Prompt- 
ing begins at the same point with the procedure as after the 
inputting of the action and CMU command. 
The use of the question mark (?) within the “Help” file has 
already been noted. 
5.09 Error Messages. Most errors during message entry do 
not cause an exit from the CMU procedure. If an exit does not 
occur, the system provides a Plain English Format (PEF) error 
message and expects a retry of the user action just attempted. 
If an exit does occur, the system reverts the user back to the 
command prompt level, indicated by the character I‘)“. Figures 
5.05 through 5.07 show typical examples of error messages. 
Other command level error messages may also occur, and are 
shown in Table 5.02. The table also provides recommended 
user action in response to the error message received. In addition to the error messages at this level, error messages 
pertaining to the individual inputs within a CMU procedure may 
occur at any time during a CMU procedure. These error 
messages indicate such items as incorrect parameters, invalid 
ranges of data, improper parameter input sequences, etc. Error 
messages within a CMU procedure usually require the user 
to reinput the correct data.  
: 
PER ERROR # 1 
INVALID PASSWORD ENTERED 
1 PLEASE ENTER PASSWORD > 
Figure 5.05 Error Message Example 
Invalid Password 
This message indica: s that the security key entered contained 
an error, or is not authorized. The correct security key may be 
reentered on the line following the symbol “>“. 
Figure 5.06 Error Message Example 
Invalid Action Specified 
This message indicates that the ACTION entered is not valid 
with respect to the command entered. The correct value may 
be reentered on the line following the symbol “)“. 
Figure 5.07 Error Message Example 
Invalid Command Name 
This message indicates an incorrect COMMAND name has 
been entered. The correct action and command name may 
be entered on the line beginning with the symbol “)“. 
In most cases, correct parameters and parameter values that 
were entered for the command are retained by the system, 
therefore only the value(s) in error need be reentered. The error 
message reflects the current entry, thus any successful entries 
made during the procedure are still valid; if desired, these 
changes can be ignored by use of the CANCEL action (refer 
to Table 5.01). 
5.10 Input Examples. Appendix B provides examples of 
inputting CMU changes and the corresponding results These 
examples show the prompting of the user, the input actions, 
commands and associated parameters and parameter values, 
and the response of the system to these entries. 
During the initial prompting, the system prints out a string of 
characters as shown in Figure 5.08. These are defined as 
follows: 
pp-AOS w. rr-DB w. rr-PL:nnn -SITE:sss 
PLEASE ENTER PASSWORD > 
Figure 5.08 Initial Prompt with System-Level Designators 
5-4