NEC Code Master An Open Application Interface Installation Guide

							NDA-30013   Revision 6.0Page 21
Code Master Installation Guide Initialization and Termination
Chapter 5 Initialization and Termination
Once Code Master and its databases are created, it is ready to be initialized. Enter 
the APM Operations Menu and initialize Code Master through the Non-CRT 
Application Control option, according to instruction provided in the APM 
Operations Manual. An “*” will appear next to the application name once Code 
Master runs successfully.
If an error occurs during initialization, verify that the application is configured 
correctly in the APM, and that its databases are defined and contain valid data. Also 
verify that the PBX is configured correctly to support OAI and Code Master.
Code Master can be terminated at any time. From the Non-CRT Application 
Control option of the APM Operations Menu, select the Terminate command, 
followed by the Code Master application, as instructed in the APM Operations 
Manual. Once Code Master has terminated, the “*” disappears and the PBX will 
refer to its own table of authorization codes (AATC command) to determine the 
validity of call attempts. 
						

							Initialization and Termination Code Master Installation Guide
Page 22NDA-30013   Revision 6.0
This Page Left Blank. 
						

							NDA-30013   Revision 6.0Page 23
Code Master Installation Guide Error Messages
Appendix A Error Messages
#1    “errno =  reading .” 
The specified UNIX error occurred while trying to read the specified database 
file. Perhaps there are no records in the database, the UNIX permissions are 
wrong for the file, or the file name is wrong.
#2    “Invalid mask -- ”
An invalid format was detected in a record of the Tenant/Mask Database.The 
criteria for a valid mask is: (1) length of 10 characters or less; (2) only a 
combination of digits, the letter I (upper or lower case), or the letter V (upper or 
lower case); and (3) two Vs cannot be separated by any Is.
#3    “No authorization codes in data base.”
The Authorization Code Database does not contain any records. Verify that the 
master database has records and that the application database has been 
processed and installed.
#4    “No memory allocated for authorization codes.” 
There was insufficient memory for the program to use for the storage of data 
from the Authorization Code Database. 
#5    “DB load failed -- error = ”
The specified UNIX error occurred while trying to read the records of the 
Authorization Code Database. It is possible that the file has gotten corrupted or 
does not have the correct UNIX permissions. Verify that the application 
database has been processed and installed correctly.
#6    “ records loaded.”
This is an informative message letting you know the quantity of authorization 
codes that have been loaded from the database.
#7    “Write of pipe fails!”
The program was unable to send a report of a call attempt to the Recorder. 
Terminate and restart the application.
#8    “Cannot set timer (timerset).”
The program could not set a timer managed by the APM. Terminate the 
application and the OAI system, then re-initialize the OAI system and the 
application. If necessary, halt and restart the entire APM system instead.
#9    “Cannot cancel timer (timerdel).”
The program could not cancel a timer managed by the APM. Terminate the 
application and the OAI system, then re-initialize the OAI system and the 
application. If necessary, halt and restart the entire APM system instead.
#10   “Open of pipe fails! No recording.”
The program was unable to establish a means of communicating with the 
Recorder (via a pipe). If recording is still desired, terminate and restart the 
application.
#11   “Cannot spawn child process! No recording.”
The program was unable to create the Recorder process. If recording is still 
desired, terminate and restart the application. 
						

							Page 24NDA-30013   Revision 6.0
Error Messages Code Master Installation Guide
#12   “Recorder is killed.”
For an unknown reason, the Recorder did not respond to a command to stop 
itself, so the parent process “killed” it instead. Any unwritten reports were lost.
#13   “Close of pipe fails!”
The program could not close the pipe to the Recorder. This error is harmless. 
#14   “Recorder process begins.”
This is an informative message letting you know that authorization codes from 
call attempts can now be recorded (one “report” per call attempt). 
#15   “No memory allocated for reports.”
There was insufficient memory for the program to use for the recording of 
authorization codes.
#16   “Recorder stops.”
This is an informative message letting you know that no more authorization 
codes can be recorded. Any reports in memory have been written to disk.
#17   “Out of space or file deleted.”
The Recorder could not close the log file that contains the recorded 
authorization codes, probably due to a lack of disk space or the inadvertent 
deletion of the file.
#18   “Hang-up signal detected. Recorder stops.”
The Recorder received a signal indicating that the application has lost 
communication with the PBX and is terminating. Any reports in memory have 
been written to disk.
#19   “Cannot open .”
The specified database or log file could not be opened. Verify that the pathname 
is the application database for the Tenant/Mask Database or Authorization 
Code Database. Verify that the databases have been processed and installed. 
(See Chapter 3 for assistance.) If this message originated from the Recorder, 
verify that User-defined Parameter #3 refers to an existing directory.
#20   “No memory allocated for tenant structures.”
There was insufficient memory for the program to use for the storage of data 
from the Tenant/Mask Database.
#21   “Invalid tenant number ().”
The specified tenant number of an authorization code from a call attempt did 
not match any record in the Tenant/Mask Database. The call was restricted.