NEC Attendant Management System Operations Manual
Have a look at the manual NEC Attendant Management System Operations Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1168 NEC manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
NDA-30046 Revision 3.0Page B-3 Attendant Management System Operations Manual AMS Database Maintenance Procedures 5. Before reorganizing the database, it is useful to find the exact number of extents in each of the fragmented tables. This way, once you reload the data, you can rerun this step to see the improved number. To determine the exact number of extents for the fragmented tables, type tbcheck -pt amsdb | more and press Enter. You can type /extension to skip all of the internal informix tables and display AMS tables, including the extension, directory, and attendant tables. You should note the “Number of extents” once you find the table(s) in question. You can issue the same command to find the number of extents used by the statistics by changing the database name: tbcheck -pt statsdb | more. Type / callprc to skip to the pertinent table. Press the space bar to scroll down through the output until you return to the “$” prompt. Note: If you have more than 5000 records in any table (i.e. callprc), the reloading of the data may take several hours. Your system will be down until the load completes. If only callprc is large, you may choose to delete the lines that reload that table from the loadstat script as described later in the procedure. You will loose any current call statistics for the last week. 6. Terminate the Ams_Daemon via the APM as described in “Step 3: Terminating the Ams_Daemon” on page A-2. 7. Make sure all attendants are logged off as described in “Step 1: Verifying Operators Are Logged Off” on page A-1. 8. Make sure that all of the AMS logins that are configured to always run on the SunRiver terminals are turned off as described in “Halting Auto-Configured SunRiver Stations” on page A-8. 9. Make a tape backup as described in “Performing a Tape Backup” on page B-2 in case any dropped data cannot be restored. Note: The next step is to note the number of records (rows) in each table so that you can verify the unload of the data is not corrupt before dropping the database. 10. Log in at the login prompt by typing amsadm. Log in at a separate login prompt by typing statsadm. 11. Enter d to select the Display Table Count command on both the amsadm and statsadm screens. 12. Write down the number of rows for all tables on the stats menu and for the following tables from the AMS: attendant directory employee extension external internal orbit_number route speed
Page B-4NDA-30046 Revision 3.0 AMS Database Maintenance Procedures Attendant Management System Operations Manual Next we will unload the database. Even after this step, we have not removed any data from the database. We are only saving it to temporary files. 13. If you do not have the “Informix dbaccess Utility” option on your amsadm or statsadm menu, log out of amsadm and statsadm and log in as informix on two screens. Otherwise, enter x to activate dbaccess and skip the next step. 14. Type dbaccess. 15. Choose Query Language then amsdb on one screen and statsdb and Choose on the other. 16. The unlams appears as an option on one screen and unlstat on the other. Select this script. 17. After a list of unload statements is displayed, select Run. 18. If you get an error regarding permissions, check /tmp and make sure it is writable by the Informix. Also check to see if any of the files we are trying to unload into already exist. If they exist, make sure they are writable by everyone by logging in at a UNIX prompt as root and typing chmod 666 /tmp/ for each file we are attempting to write such as “chmod 666 /tmp/ directory” “chmod 666 /tmp/extension”, etc. 19. If you get any other error, consult your Informix manual or call NTAC. If necessary, bring the Ams_Daemon online and reinitialize the disabled operator terminals by typing enable followed by each tty such as “enable tty00a”. 20. If the unload is successful, the message “1 row(s) unloaded” is displayed. Press e twice to exit dbaccess on both screens. 21. Type cd /tmp at the UNIX prompt. 22. Type wc -l * | more to display the line count of each file. Verify that the number of lines in each table matches the number of lines that you noted earlier for these tables, including the directory table and the employee table. If these numbers do not match, the data did not get properly unloaded. Do not continue with the dropping of the database. Reenable the Ams_Daemon and the operator ttys. 23. You can also type more , where is “directory”, “callprc”, etc. You should see an ASCII dump of that table with fields separated by “!”s. 24. If all files look alright, make a tape backup, if you have not already done so. 25. Log out of UNIX by typing Exit. Log back in by typing amsadm on one screen and statsadm on another. 26. Enter r to select the Remove the Database command on each screen. Type y and press Enter when prompted to verify your choice. 27. Enter i to select the Install the Database command on each screen. This does not load any data; it simply creates the description for each table. 28. Enter b to select the Build the Database Indices command on each screen. If you do not do this, your queries will be extremely slow. 29. Enter Informix dbaccess utility by selecting from the menu or by logging off and logging in as informix and typing dbaccess on both screens.
NDA-30046 Revision 3.0Page B-5 Attendant Management System Operations Manual AMS Database Maintenance Procedures 30. Choose Query Language then amsdb on one screen and statsdb then Choose on the other. Then choose loadams on one screen and loadstat on the other. Note: Note that if you Run the loadstat and you have many thousands of records in callprc, this may take several hours. 31. If you do not need to restore the attendant statistics for the last week, you can edit the loadstat script and delete the 4 lines associated with loading the callprc table. Choose Modify and press Ctrl+D followed by ESC to delete the following 4 lines: begin work; lock table callprc in exclusive mode; load from “/tmp/callprc” delimiter “!” insert into callprc; commit work; 32. Choose Run. The message “Data committed” displays at the bottom of the screen. 33. Exit dbaccess, and log into amsadm and statsadm if you have not already. 34. On both screens, choose c to select the Cluster the Database command. 35. Enter d to display the number of records in each table. These numbers should match those that you wrote down in Step 12. However, the numbers for the callprc table will not match if it was not reloaded. 36. If the data did not get successfully reloaded, you must restore the database from tape. 37. Perform Step 5 again to see the new number of extents associated with each table. If the number of extents is more than 5 on any given table, or if the number of extents was originally more than 20, you should increase the next extent size for that table as follows: Log in as informix. Type dbaccess. Choose Query-Language. If callprc is the table in question, choose statsdb as the database; otherwise, select amsdb. Choose New and type alter table tablename modify next size kbytes , where tablename is the table for which you are increasing the extent size, and kbytes is the new next extent size. Typically, users double the existing extent size. 38. Log in as root and enter the root password. Type enable tty, where is the number of the tty(s) you disabled in inittab (i.e., enable tty00a, enable tty00b, etc.) 39. Log in as apm and reinitialize the Ams_Daemon.
AMS Database Maintenance Procedures Attendant Management System Operations Manual Page B-6NDA-30046 Revision 3.0 This Page Left Blank.
NDA-30046 Revision 3.0Page C-1 Attendant Management System Operations Manual AMS Database Import Capabilities Appendix C AMS Database Import Capabilities The initial AMS database is created by either manually entering the information through the MAS input menus or by importing data from ASCII files. The utilities used to import this information into the AMS database requires the information to be in a predefined format. There are 4 different types of ASCII files from which data can be imported: extension, external numbers, other internal numbers (for example, cafeteria), and employees. The following tables identify the record format for each type of file. Please note: The information should be in upper case. Each field must be enclosed by double quotes (example “X”). Each field must be followed by a comma. Null fields are indicated as ““. Enter a null field for those fields not used or for those fields for which no information will be supplied. The number of characters in each field of the supplied data can be larger than the size noted in the table, but only the first size number of characters will be imported. The ASCII files can be supplied on either a DOS or UNIX formatted diskette. If UNIX is used, please use the tar command to copy the files to the diskette. Extension Record Format You need to name the extension record format file extn.txt. Table C-1 Extension Record Format Field Description Size Extension 5 CCIS Index 5 Station Type (“s” for Singleline, ““ or any other character entry sets type to DTERM1 Tenant (1-255) 3 Department 25 Address 30 City 25 State 2 Zip Code 10 Fax # 10 User Definable 1 25 User Definable 2 25
Page C-2NDA-30046 Revision 3.0 AMS Database Import Capabilities Attendant Management System Operations Manual External Record Format You need to name the external record format file extl.txt. Internal Record Format You need to name the extension record format file intl.txt. Table C-2 External Record Format Field Description Size External Name (Location/person) 30 Number to Display 15 Number to Call 21 ANI Number 21 Account # 10 Address 30 City 25 State 2 Zip Code 10 User Definable 1 25 User Definable 2 25 User Definable 3 25 User Definable 4 25 Table C-3 Other Internal Record Format Field Description Size Name 30 Extension 5 User Definable 1 25 User Definable 2 25 User Definable 3 25 User Definable 4 25
NDA-30046 Revision 3.0Page C-3 Attendant Management System Operations Manual AMS Database Import Capabilities Employee Record Format You need to name the employee record format file empl.txt. * If the Location Status Information (LSI) application is to be used in conjunction with the AMS, these fields are reserved for LSI. Table C-4 Employee Record Format Field Description Size Employee Name 30 Extension 5 Title 25 ID 10 Beeper 15 Message Count 4 Account # 10 E-Mail Address 50 Vo i c e M a i l b o x 1 5 Car Phone 15 Home Phone 15 Home Address 30 Home City 25 Home State 2 Home Zip Code 10 User Definable 1* 25 User Definable 2* 25
AMS Database Import Capabilities Attendant Management System Operations Manual Page C-4NDA-30046 Revision 3.0 This Page Left Blank.