- Hewlett-Packard Printer Owner's Manual

ManualsBrandsHP ManualsPrinterR4.2

585-313-507

Comcode 108725904

April 2000

Issue 3

UCS 1000

R4.2

Administration

Summary of content (745 pages)

PAGE 1
UCS 1000 R4.
PAGE 3
Copyright and legal notices Copyright Copyright © 2000 by Lucent Technologies. All rights reserved. Printed in the USA. This material is protected by the copyright laws of the United States and other countries.
PAGE 4
Copyright and legal notices Trademarks Lucent Technologies has made every effort to supply the following trademark information about company names, products, and services mentioned in the UCS 1000 R4.2 documentation library: • Adobe Systems, Inc. — Trademarks: Adobe, Acrobat. • Enhanced Software Technologies, Inc. — Trademark: Quickstart. • Equinox Systems, Inc.
PAGE 5
Copyright and legal notices Limited Warranty • Oracle Corporation — Trademarks: OBJECT*SQL, ORACLE, ORACLE*Terminal, PRO*C, SQL*FORMS, SQL*Menu, SQL*Net, SQL*Plus, SQL*ReportWriter. • PCI Industrial Computer Manufacturers Group — Registered trademarks: CompactPCI and PICMG. • Santa Cruz Operation, Inc. — Registered trademarks: UnixWare. • Sun Microsystems — Registered trademarks: Sun, Sun Microsystems, Sun Workstation, Solaris (computer and peripherals).
PAGE 6
Copyright and legal notices United States FCC Compliance Information Part 15: Class A statement. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
PAGE 7
Copyright and legal notices Your Responsibility for Your System’s Security You and your system manager are responsible for the security of your system and for preventing unauthorized use. You are also responsible for reading all installation, instruction, and system administration documents provided with this product in order to fully understand the features that can introduce risk of toll fraud and the steps that can be taken to reduce that risk.
PAGE 8
Copyright and legal notices Documentation Ordering Information Call or Write Lucent Technologies Publications Center 2855 N. Franklin Road Indianapolis, IN 46219 Voice FAX 1 800 457-1235 1 800 457-1764 International Voice 317 322-6791 International FAX 317 322-6699 To Order To order a document, contact the Lucent Technologies Publications Center and specify the 9-digit document number, the issue number, and the issue date.
PAGE 9
Contents Copyright and legal notices About This Book iii xxii Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii Intended Audiences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii How This Book Is Organized. . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii Administration Procedures and Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv Reference Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 10
User Interface Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 UCS 1000 R4.2 User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Cursor Movement Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Menus and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Message Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 11
Port Access Services and Monitors . . . . . . . . . . . . . . . . . . . . . . . . . 47 Printer Configuration and Services . . . . . . . . . . . . . . . . . . . . . . . . . 47 Restore from Backup Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Basic Restore Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Extended Restore Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Schedule Automatic Task .
PAGE 12
Adding Message Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Removing Message Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Adding Thresholds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Removing Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Modifying Message Priorities. . . . . . . . . . . . . . . . . . . . .
PAGE 13
4 Switch Interface Administration 141 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switch Interfaces Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Switch Interfaces Menu . . . . . . . . . . . . . . . . . . . . . . Digital Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Digital Interfaces Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 14
EVENTS Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EVSUM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRASUM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLDCDH View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Relationship Between the CALL, SERVICE, and EVENT Tables . . . . .
PAGE 15
Completing ORACLE Environment Setup if Server is Not a UCS 1000 R4.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing a Remote Database Using PRO*C or SQL*PLUS . . . . . . . . . . . . . . Removing a Database Access ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SQL*PLUS Database Administration . . . . . . . . . . . . . . . . . . . . . . . Monitoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Commands . . . . . .
PAGE 16
Administering the Remote Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295 7 Common Administration 297 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Accessing the Command Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 17
addhdr . . . . . . . . alarm_cutoff . . . . . annotate . . . . . . . assign card/channel . assign_permissions . assign service/startup attach . . . . . . . . autoreboot . . . . . . bbs . . . . . . . . . . ccarpt . . . . . . . . cddrpt . . . . . . . . cdsrpt . . . . . . . . codetype . . . . . . . configure_tam . . . . copy . . . . . . . . . cpuType . . . . . . . cvis_mainmenu . . . cvis_menu . . . . . . dbcheck . . . . . . . dbfrag . . . . . . . . dbfree . . . . . . . . dbused . . . . . . . . UCS 1000 R4.
PAGE 18
decode . . . . . . . . defService . . . . . . delete card/channel . delete eqpgrp . . . . delete service/startup detach . . . . . . . . diagnose bus 1. . . . diagnose card . . . . dip_int . . . . . . . . display assignments . display card . . . . . display channel . . . display dnis . . . . . display eqpgrp/group. display equipment . . display messages . . display_permissions . display services . . . display_tam . . . . . dspActAlarms . . . . dspRetAlarms . . . . edExplain . . . . . . UCS 1000 R4.
PAGE 19
encode . . . . . . erase . . . . . . . explain . . . . . . findHomes . . . . fixLogFile. . . . . iCk, iCkAdmin . . logCat . . . . . . lComp . . . . . . list . . . . . . . . logCat . . . . . . logDstPri . . . . . logEvent/logMsg . logFmt . . . . . . mkAlerter. . . . . mkheader . . . . mkimage . . . . . newscript . . . . . pkgadd . . . . . . pkginfo . . . . . . pkgrm . . . . . . reinitLog . . . . . remove . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 20
restore . . . . . . . . . retireAlarms . . . . . . rmdb . . . . . . . . . . show_sys . . . . . . . soft_disc . . . . . . . . soft_szr. . . . . . . . . spadc. . . . . . . . . . spar . . . . . . . . . . spsav. . . . . . . . . . spStatus . . . . . . . . spVrsion . . . . . . . . start_vs. . . . . . . . . stop_vs. . . . . . . . . striphdr . . . . . . . . . sysmon. . . . . . . . . tas . . . . . . . . . . . trace . . . . . . . . . . trarpt . . . . . . . . . . unassign_permissions . vfyLogMsg . . . . . . .
PAGE 21
vusage . . wl_copy . wl_edit . . wl_gen . . wl_init . . wl_install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 22
About This Book Overview This document describes the procedures needed to perform full system administration for the following areas: • The UNIX operating system • The voice system • Databases • Switch interfaces This document also describes the procedures needed to create and access system reports and to monitor the system. UCS 1000 R4.
PAGE 23
About This Book Intended Audiences Intended Audiences The primary audience for this document are system administrators. This includes: • On-site technicians who perform system administration at the customer site • End customers who choose to administer their own systems Secondary audiences include the field support personnel. We assume that the primary users of this book have completed the UCS 1000 R4.2 hardware installation and maintenance training course.
PAGE 24
About This Book How This Book Is Organized Administration Procedures and Information See Chapter 1, Administration Overview , to familiarize yourself with the user interface and the system administration process including the user interface and the menus. See Chapter 2, UNIX Administration , for information about how to access the SYSADM menu and the procedures to perform basic UnixWare-level administration.
PAGE 25
About This Book Conventions Used in This Book See Chapter 7, Common Administration , for quick-reference information for some of the more common administrative tasks. Daily administration includes running system reports; performing common procedures such as system monitoring, media formatting, and backups; and administering the date and time. Reference Material See Appendix A, Summary of Commands, for an alphabetical list of the commands in the UCS 1000 R4.2 command language.
PAGE 26
About This Book Conventions Used in This Book Note: Terminology • The screens shown in this book are examples only. The screens you see on your system may be similar, but not exactly the same in all cases. The word “type” means to press the key or sequence of keys specified. For example, an instruction to type the letter “y” is shown as Type y to continue. • The word “enter” means to type a value and then press the EN TER key on the keyboard.
PAGE 27
About This Book Conventions Used in This Book • The system displays menus, screens, and windows. Menus (Figure 1) present options from which you can choose to view another menu, or a screen or window. Screens and windows both show (Figure 2 on page xxviii and Figure 3 on page xxix) and request (Figure 4 on page xxix and Figure 5 on page xxx) system information. Figure 1. Example of a UCS 1000 R4.2 Menu UCS 1000 R4.
PAGE 28
About This Book Conventions Used in This Book Figure 2. Example of a UCS 1000 R4.2 Screen Showing Information UnixWare Installation Primary Hard Disk Partitioning In order to install LINCS, you should reserve a UNIX system partition (a portion of your hard disk’s space) containing 100% of the space on your primary hard disk.
PAGE 29
About This Book Conventions Used in This Book Figure 3. Example of a UCS 1000 R4.2 Window Showing Information Figure 4. Example of a UCS 1000 R4.2 Screen Requesting Information UNIX System Installation Set Slice Sizes Please select whether you would like the recommended slice sizes or would like to customize the slice sizes. Your choices are: 1. Recommended Slice Sizes 2. Customize Slice Sizes Press ’1’ or ’2’ followed by ’ENTER’: 1 UCS 1000 R4.
PAGE 30
About This Book Conventions Used in This Book Figure 5. Keyboard and Telephone Keypad Representations • Example of a UCS 1000 R4.2 Window Requesting Information Keys that you press on your terminal or PC are represented as capitalized BO LD text. For example, an instruction to press the Enter key is shown as Press EN TE R .
PAGE 31
About This Book Conventions Used in This Book • Keys that you press on your telephone keypad are represented as bold text. For example, an instruction to press the first key on your telephone keypad is shown as Press 1 to record a message. Screen Displays • System messages, field names, and prompts that appear on the screen are shown in typewriter text, as shown in the following examples: ~ Enter the number of ports to be dedicated to outbound traffic in the Maximum Simultaneous Ports field.
PAGE 32
About This Book Conventions Used in This Book In this example, you would access the Voice System Administration menu and select the Reports menu. From the Reports menu, you would then select the Message Log Report window. Some Screen Simulations Text in a simulated screen display appears in typewriter text. Example: QuickStart - Data Recovery Rescue Copyright(c) 1997-1999 by Enhanced Software Technologies, Inc. Serial# 8200-999 Version: 1.3.
PAGE 33
About This Book Conventions Used in This Book Other Typography Command Text • Literal values, commands, and text that you type in or enter appear in bold type, as in the following examples: Example 1: Enter change-switch-time-zone at the Enter command: prompt. Example 2: Type high or low in the Speed: field.
PAGE 34
About This Book Safety and Security Alert Labels Safety and Security Alert Labels This book uses the following symbols to call your attention to potential problems that could cause personal injury, damage to equipment, loss of data, service interruptions, or breaches of toll fraud security: ! CAUTION: Indicates the presence of a hazard that if not avoided can or will cause minor personal injury or property damage, including loss of data.
PAGE 35
About This Book Related Resources Related Resources Updates to the Product The following Web site displays any updates or exceptions to the product that have occurred after the publication of this document: http://glsdocs.lucent.com Training For more information on UCS 1000 R4.
PAGE 36
About This Book Related Resources You can also order the printed documents by calling 1-888-582-3688 or visiting the Customer Information Center (CIC) website at: http://www.lucent.com/cgi-bin/CIC_store.cgi Using the CD-ROM Documentation Lucent Technologies ships the documentation in electronic form. Using the Adobe Acrobat Reader application, you can read these documents on a Windows PC, on a Sun Solaris workstation, or on an HP-UX workstation.
PAGE 37
About This Book Related Resources chapter you are viewing. You can control the appearance of bookmarks by selecting View | Page Only or View | Bookmarks and Page. Using the Button Bar The button bar can take you to the book’s Index, table of contents, main menu, and glossary. It also lets you update your documents. Click the corresponding button to jump to the section you want to read. Using Hypertext Links Hypertext-linked text appears in blue, italics, and underlined.
PAGE 38
About This Book Related Resources If you would want to read the documentation in paper form rather than on a computer monitor, you can print all or portions of the online screens. Printing an Entire Document To print an entire document: 1 From the documentation main menu screen, select one of the print- optimized documents. Print-optimized documents print two-screens to a side, both sides of the sheet on 8.5x11-in or A4 paper. 2 Select File | Print.
PAGE 39
About This Book How to Comment on This Book How to Comment on This Book A comment card is included at the back of this book. While we have tried to make this document fit your needs, we are interested in your suggestions for improving it and urge you to complete and return a comment card to us. If the comment card has been removed from this book, send you comments to the address below. Be sure to include the name and document number of this book, UCS 1000 R4.2 Administration, 585-313-507.
PAGE 40
1 Administration Overview Overview This chapter provides an overview of system administration and is designed to familiarize you with the UCS 1000 R4.2 user interface and the system administration process including: • User interface overview • User interface components • The administration menus User Interface Overview A user interface is a method by which a computer user accesses the information on the computer. For example, Microsoft Windows is a graphical user interface (also known as GUI).
PAGE 41
1 Administration Overview UCS 1000 R4.2 User Interface active. To return to the previous menu or window, you can cancel the active one. UCS 1000 R4.2 User Interface Administering the voice system through the administrative screens involves many activities, and all share a common user interface. Although the information on the screen changes often, the information arrangement does not change.
PAGE 42
1 Administration Overview UCS 1000 R4.2 User Interface Figure 6. Sample UCS 1000 R4.2 System Screen Menu or Window Message Line Function Key Labels UCS 1000 R4.
PAGE 43
1 Administration Overview UCS 1000 R4.2 User Interface Cursor Movement Keys Table 1 lists the keys used to maneuver within a menu or window. They are referred to throughout this book as the cursor movement keys. Table 1.
PAGE 44
1 Administration Overview UCS 1000 R4.2 User Interface Menus and Windows You use menus and windows to exchange information with the voice system. This exchange may involve activities such as making menu selections or populating fields. Since the display may contain more than one menu or window at the same time, each menu/window is outlined so that it is clear what information it contains. At any given time, only one menu or window on screen is designated as active.
PAGE 45
1 Administration Overview UCS 1000 R4.2 User Interface The components of a menu include: • Title — The title describes the information contained within the menu, or the tasks you can accomplish using it. In this book, titles are shown with the first letter of each word capitalized, followed by the word menu, such as the Configuration Management menu. • Scroll Indicator — The scroll bar indicates whether there is additional text to be displayed.
PAGE 46
1 Administration Overview • UCS 1000 R4.2 User Interface Type the first character(s) of the menu line. The system highlights the first menu item beginning with that letter. For example, in Figure 7 on page 5, type S to select System Control. If there is another menu item beginning with “s,” type more characters. The menu items are not case-sensitive; that is, typing A is the same as typing a. If you type a letter for which there is no matching item, the system “beeps” and does not move the highlight bar.
PAGE 47
1 Administration Overview UCS 1000 R4.2 User Interface Figure 9. Sample Window The components of a window include: • Title — The title describes the information contained within the window, or the tasks you can accomplish using it. In this book, titles are shown with the first letter of each word capitalized, followed by the word window, such as Voice Equipment window. • Scroll Indicator — The scroll bar indicates whether there is additional text to be displayed.
PAGE 48
1 Administration Overview UCS 1000 R4.2 User Interface Populating Fields There are three ways to enter information in a field, as described below. • Type the first character or first few characters of the entry. With the cursor positioned on the field, begin to type the entry. As soon as you type enough characters to uniquely identify the desired entry, the system automatically supplies the remaining characters. If the entry is invalid, the system beeps and removes the invalid characters.
PAGE 49
1 Administration Overview UCS 1000 R4.2 User Interface Figure 10. Fields in the Call Data Summary Report Window • Type the entire entry. Move to the desired field and type the entire entry. While in a field, you can also edit the entry. • Use the CHOICES screen selections. Press F 2 (Choices) to open a menu that shows the available choices for a field. Select an option as you would in a standard menu. The content of the CHOICES menu varies depending on the situation.
PAGE 50
1 Administration Overview UCS 1000 R4.2 User Interface Function Keys Your keyboard has eight to twelve function keys. The system uses the first eight function keys, labeled F 1 through F 8 . The boxed labels at the bottom of the display correspond to the function keys on your keyboard. Function keys are the means by which you command the system to perform a function within the active menu or window.
PAGE 51
1 Administration Overview UCS 1000 R4.2 User Interface Figure 11. Function Key Labels — System Monitor Window Standard Function Key Labels Standard function key labels remain constant regardless of the active menu or window. They represent commands that are valid for every menu or window in the system. See Table 2 on page 13 for a description of standard function key labels. UCS 1000 R4.
PAGE 52
1 Administration Overview Table 2. Optional Function Key Labels UCS 1000 R4.2 User Interface Standard Function Key Labels Key Description F1 Help Opens an online help window. See Online Help on page 17 for more information about online help. F6 Cancel Closes the active screen and cancels any additions, deletions, or changes made. The screen that immediately precedes the just-closed screen becomes the active screen.
PAGE 53
1 Administration Overview Table 3. UCS 1000 R4.2 User Interface Optional Function Key Labels Function Key Label Description F 2 (Choices) Opens a menu screen containing choices for the current field, if there is a finite set of choices for a particular field. Move the cursor to the field you want to fill and press F2 (CHOICES). The CHOICES menu opens, displaying the options available for that field.
PAGE 54
1 Administration Overview Table 3. UCS 1000 R4.2 User Interface Optional Function Key Labels Function Key Label Description F 5 (Bottom) Scrolls toward the bottom of a page. F 6 (Print) Prints the information provided by the active screen, such as a report. F 7 (Frm-Mgmt) Opens the Frame Management Menu. See Command Menu on page 297 in Chapter 7, Common Administration , for more information. Options include list, move, refresh, and UNIX system.
PAGE 55
1 Administration Overview UCS 1000 R4.2 User Interface Figure 12. Change Keys — System Monitor Screen Note: In Figure 12, the H ost M on function key selection does not appear if host software is not installed. UCS 1000 R4.
PAGE 56
1 Administration Overview Online Help Online Help Most screens and windows have a companion text window that contains helpful reference information. Figure 13 shows the help screen associated with the Database Access ID Table window. The system online help windows are not designed to be a substitute for this book. They briefly describe each of your options for a given menu or window. Press F1 to access online help. Figure 13. Sample Online Help Screen, Database Access ID Table UCS 1000 R4.
PAGE 57
1 Administration Overview Accessing the Administration Menus Accessing the Administration Menus To access the administration menu: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter one of the following commands at the prompt: ~ To display the administration menu, enter cvis_mainmenu The system displays the administration menu (Figure 14). Figure 14.
PAGE 58
1 Administration Overview Accessing the Administration Menus ! CAUTION: Do not create multiple simultaneous cvis_menu processes. This could severely impact performance and may lock up the system. The system displays the Voice System Administration menu (Figure 15). Figure 15. Voice System Administration Menu See Chapter 3, Voice System Administration , for more information and procedures on voice system administration. UCS 1000 R4.
PAGE 59
1 Administration Overview Accessing the Administration Menus Administration Menu Options From the administration menu, you can initiate UNIX System Administration and Voice System Administration, or you may exit. UNIX System Administration From the UNIX System Administration menu, you can set up a variety of generic software operations including backups, printer operations, and peripheral setup. See Chapter 2, UNIX Administration , for more information and procedures on UNIX administration.
PAGE 60
1 Administration Overview Note: Accessing the Administration Menus F 6 (Cancel) does not exit from the UNIX System Administration menus. See Exit UNIX System Administration Menu on page 57 in Chapter 2, UNIX Administration , for the procedure to exit from the UNIX System Administration menus. UCS 1000 R4.
PAGE 61
2 UNIX Administration Overview This chapter describes the UnixWare™ system administration user interface, the procedures to access the UnixWare administration menu, and the procedures to perform basic UnixWare-level administration. The sections in this chapter are arranged in the same order as the administration services in the UnixWare administration main menu. UnixWare Documentation For additional information on UnixWare administration, see the UnixWare documentation.
PAGE 62
2 UNIX Administration UNIX System Administration Access UNIX System Administration Access To access SYSADM (the OA&M menu interface of UnixWare): 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cvis_mainmenu The system displays the Administration menu (Figure 16). Figure 16. Administration Menu UCS 1000 R4.
PAGE 63
2 UNIX Administration UNIX System Administration Access 4 Select: > UNIX System Administration The system displays the UNIX System V Administration menu (Figure 17 on page 24). Figure 17. UNIX System V Administration Menu UCS 1000 R4.
PAGE 64
2 UNIX Administration Application Administration All of the procedures in this book assume that you are using the user interface menus. The procedures provide references to the books detailing command line interfaces when possible. Application Administration The Application Administration menu provides menus and tasks for administering custom applications. Application developers can use this option to place menus from which to administer add-on or custom applications.
PAGE 65
2 UNIX Administration Backup Scheduling, Setup and Control The basic backup services allow you to: • Display the date and time of the last system and incremental backup. • Conduct a backup of all files or only selected files in your HOME directory. • Add, change, delete, or display backup requests. • Back up all system and user files that have been modified or created since your voice system was installed. The extended backup services allow you to: • Determine the backup rotation period.
PAGE 66
2 UNIX Administration Backup Scheduling, Setup and Control To access backup services: 1 Start at the UNIX System V Administration menu (Figure 17 on page 24) and select: > backup_service The system displays the Backup Service Management menu (Figure 18). Figure 18. Backup Service Management Menu UCS 1000 R4.
PAGE 67
2 UNIX Administration Backup Scheduling, Setup and Control Basic Backup To perform a basic backup: 1 Start at the Backup Service Management menu (Figure 18 on page 27) and select: > basic The system displays the Backup to Removable Media menu (Figure 19). Figure 19. Backup to Removable Media Menu Use the procedures below to access the different menu options of the Backup to Removable Media menu. UCS 1000 R4.
PAGE 68
2 UNIX Administration Backup History Backup Scheduling, Setup and Control The Backup History menu option displays the date and time of the last system and incremental backup. To view the backup history: 1 Start at the Backup to Removable Media menu (Figure 19 on page 28) and select: > Backup History The system displays the Backup History window (Figure 20). Figure 20. Backup History Window 2 Press F3 (Cont) to return to the Backup to Removable Media menu (Figure 19 on page 28). UCS 1000 R4.
PAGE 69
2 UNIX Administration Backup of All Personal Files Backup Scheduling, Setup and Control A personal backup copies all the files in your HOME (or personal) directory to either tape or formatted diskettes. To back up all files in your personal directory: 1 Start at the Backup to Removable Media menu (Figure 19 on page 28) and select: > Personal Backup > Backup Files under / The system displays the Select Removable Media menu (Figure 21). Figure 21. Select Removable Media Menu UCS 1000 R4.
PAGE 70
2 UNIX Administration Backup Scheduling, Setup and Control 2 Select the removable media type. The system displays a message showing the approximate number of diskettes or tapes, and the time required to backup the HOME directory. The system prompts you to insert the first diskette or tape. The system periodically prompts you to insert more diskettes or tapes until the backup is complete. 3 Press EN TE R when the backup is complete.
PAGE 71
2 UNIX Administration Backup Scheduling, Setup and Control The system displays the Select Removable Media menu (Figure 21 on page 30). 2 Select the removable media type. The system displays the Selective Backup of Files under / window (Figure 22). Figure 22. Selective Backup of Files under / Window 3 Enter the file names and directory names to be backed up. Separate each entry with a space in the Files or directories to back up: field.
PAGE 72
2 UNIX Administration Backup Scheduling, Setup and Control The system prompts you to insert the first diskette or tape. The system periodically prompts you to insert more diskettes or tapes if they are needed until the backup is complete. 5 Press EN TE R when the backup is complete. The system redisplays the Backup to Removable Media menu (Figure 19 on page 28). Schedule a Backup to Tape The Schedule Backup to Tape menu option allows you to: • Add a system or incremental backup.
PAGE 73
2 UNIX Administration Backup Scheduling, Setup and Control Add a Backup To schedule a new backup to tape: 1 Start at the Backup to Removable Media Menu (Figure 19 on page 28) and select: > Schedule Backup to Tape > Add The system displays the Schedule a System Backup window (Figure 23). Figure 23. Schedule a System Backup Window UCS 1000 R4.
PAGE 74
2 UNIX Administration Backup Scheduling, Setup and Control 2 Press F2 (Choices) to toggle between System Backup and Incremental System Backup in the Type of Backup: field. A system backup (field default) performs a back up of all system and user files installed or modified since the voice system was first installed. An incremental backup performs a back up of all system and user files since the last backup.
PAGE 75
2 UNIX Administration Backup Scheduling, Setup and Control ~ Type two numbers separated by a hyphen to indicate a range of days. For example, type 14-20 to instruct the system to perform a backup every day from day 14 through day 20 of the month. ~ Press F2 (Choices) and press F2 (Mark) to select one or more days. Press F3 (Enter) to save the selected day or days and return to the Day(s) of the Month: field. The default is “all,” to back up all days of the month.
PAGE 76
2 UNIX Administration Backup Scheduling, Setup and Control 6 Set the Time of Day: field: a Type a number in the Hours portion of the field to indicate the hour, where 00 is midnight and 23 is 11:00 p.m. Or, press F 2 (Choices) to select from a menu. . b Press The system places the cursor in the minutes portion of the field. c Type a number from 0 to 59 to indicate the minutes past the hour. The default time is 02:00, to start the backup at 2:00 a.m. 7 Press F3 (Save).
PAGE 77
2 UNIX Administration Backup Scheduling, Setup and Control Change Scheduled Backup Settings To change scheduled backup settings: 1 Start at the Backup to Removable Media menu (Figure 19 on page 28) and select: > Schedule Backup to Tape > Change The system displays the Change Scheduled Backup window (Figure 24). Figure 24. Change Scheduled Backup Window 2 Select the scheduled backup to be changed and press F2 (Mark). 3 Press F3 (Enter).
PAGE 78
2 UNIX Administration Backup Scheduling, Setup and Control Figure 25. Change Scheduled Backup Information Window 4 Change the information as appropriate. See step 2 through step 6 in Add a Backup on page 34 for information on how to add data to the fields in this window. 5 Press F3 (Save). The system displays a confirmation window that asks whether you want to continue to schedule the backup. UCS 1000 R4.
PAGE 79
2 UNIX Administration Backup Scheduling, Setup and Control 6 Do one of the following: ~ To confirm the backup schedule, press F3 (Cont). The system returns to the Schedule Backup to Tape menu. ~ To cancel the backup schedule, press F6 (Cancel). The system returns to the Schedule Backup to Tape menu.
PAGE 80
2 UNIX Administration Backup Scheduling, Setup and Control Figure 26. Delete Scheduled Backups Window 2 Select the scheduled backup to be deleted and press F 2 (Mark). Select as many of the entries as necessary. 3 Press F3 (Enter). The system displays a confirmation window to confirm the backups marked for deletion. 4 Do one of the following: ~ To confirm the backup deletion, press F3 (Cont). The system returns to the Schedule Backup to Tape menu. ~ To cancel the backup deletion, press F6 (Cancel).
PAGE 81
2 UNIX Administration Backup Scheduling, Setup and Control Display Scheduled Backups To display a list of scheduled backups: 1 Start at the Backup to Removable Media menu (Figure 19 on page 28) and select: > Schedule Backup to Tape > Display The system displays the Display Scheduled Backup window (Figure 27). Figure 27. Display Scheduled Backups Window 2 Press F3 (Cont) or F6 (Cancel) to return to the Schedule Backup to Tape menu (Figure 19 on page 28). UCS 1000 R4.
PAGE 82
2 UNIX Administration File System Creation, Checking, and Mounting Performing Extended Backup Services See “Backing Up the UCS 1000 R4.2 System” in Chapter 3, “Common System Procedures," in UCS 1000 R4.2 System Reference, 585-313-210, for information on when and how to conduct extended backups. File System Creation, Checking, and Mounting File Systems administration allows you to: • Check for and repair errors on a file system. • Set file system defaults. • Monitor disk usage for all file systems.
PAGE 83
2 UNIX Administration Machine Configuration, Display, and Shutdown Figure 28 shows the options available for file system administration. See System Files and Devices Reference in the Novell UnixWare documentation set for additional information about each of these options. Figure 28. Manage File Systems Menu Machine Configuration, Display, and Shutdown Machine administration allows you to: • Display system configuration information. • Shut down the machine. UCS 1000 R4.
PAGE 84
2 UNIX Administration Machine Configuration, Display, and Shutdown • Reboot the machine. • Display a list of users who are logged on. Figure 29 shows the options available for machine administration. See System Files and Devices Reference in the Novell UnixWare documentation set for additional information about each of these options. Figure 29.
PAGE 85
2 UNIX Administration Network Services Administration Network Services Administration Network Services administration allows you to: • Make network selections. • Manage distributed file systems. • Perform name-to-address translations. • Manage basic networking. Figure 30 displays the options available for network services administration. See Network Administration in the Novell UnixWare documentation set for additional information about each of these options. Figure 30.
PAGE 86
2 UNIX Administration Port Access Services and Monitors Port Access Services and Monitors Ports administration allows you to monitor and service ports, set up quick terminal, and manage terminal line (tty) settings. Figure 31 shows the options available for ports administration. See System Administration Volume 1 in the Novell UnixWare documentation set for additional information about each of these options. Figure 31.
PAGE 87
2 UNIX Administration Restore from Backup Data Restore from Backup Data Restore service administration allows you to perform basic and extended restore services. Note: If you want to back up and restore speech files, see the spsav command in Appendix A, Summary of Commands. Figure 32 shows the options available for restore service administration. Figure 32. Restore Service Management Menu Basic Restore Services Basic restore services allow you to perform a personal restore or a system restore.
PAGE 88
2 UNIX Administration Restore from Backup Data Extended Restore Services Extended restore services allow you to: • Specify the login of the operator who should be notified when a request that requires operation intervention is queued. • Respond to restore requests. • Restore files, directories, file systems, or a data partition from a backup archive. • Display or modify the status of pending restore requests. Figure 34 shows the options available for the Extended Restore Service. Figure 34.
PAGE 89
2 UNIX Administration Schedule Automatic Task Schedule Automatic Task Schedule task administration allows you to add, change, delete, and display a task scheduled through cron. Figure 35 shows the options available for schedule task administration. See System Administration Volume 1 in the Novell UnixWare documentation set for additional information about each of these options. Figure 35. Schedule Automatic Task Menu UCS 1000 R4.
PAGE 90
2 UNIX Administration Security Management Security Management Security management allows you to manage the security features on the system. Currently, this includes only the audit trail facility management. Figure 36 shows the options available for audit trail facility management.
PAGE 91
2 UNIX Administration Software Installation and Removal Software Installation and Removal Software administration allows you to install software, display information about software packages, store software without installing it, and remove software. Figure 37 shows the options available for software administration. See System Files and Devices Reference in the Novell UnixWare documentation set for additional information about each of these options. Figure 37.
PAGE 92
2 UNIX Administration Storage Device Operations and Definition Storage Device Operations and Definition Storage devices administration allows you to: • Copy information from one volume to another. • Display storage device information. • Erase the contents of a volume. • Configure a storage device on the system. • Reconfigure a storage device on the system. A storage device may be integral disks, diskettes, SCSI data storage devices, nine-track tapes, and other devices configured on the system.
PAGE 93
2 UNIX Administration System Name, Date and Time, and Initial Password Setup Figure 38. Storage Device Operations and Definitions Menu System Name, Date and Time, and Initial Password Setup System setup administration allows you to administer the following system characteristics: • Environment (date, time, time zone) • Passwords • Machine name • Network node name • Initial user logins UCS 1000 R4.
PAGE 94
2 UNIX Administration System Name, Date and Time, and Initial Password Setup ! CAUTION: Your system’s machine name is used by the Feature Licensing software. Call your support center before changing the machine name to avoid losing any of your feature licenses. Figure 39 shows the options available for system setup administration. Figure 39. System Name, Date, Time and Initial Password Setup Menu UCS 1000 R4.
PAGE 95
2 UNIX Administration User Login and Group Administration User Login and Group Administration Users administration allows you to manage logins and groups on your system, including: • Adding users or groups • Defining defaults for adding users • Listing users or groups • Modifying attributes of users or groups • Redefining user password information • Removing users or groups Figure 40 shows the options available for users administration.
PAGE 96
2 UNIX Administration Exit UNIX System Administration Menu Exit UNIX System Administration Menu To exit Unix System Administration: 1 Press F7 (Cmd-Menu). The system displays the Command Menu (Figure 41). Figure 41. Command Menu 2 Select: > Exit The system returns you to the system prompt #. UCS 1000 R4.
PAGE 97
3 Voice System Administration Overview The Voice System Administration menu provides access to many administrative options. This chapter describes how to access the Voice System Administration menu, and describes all of the administrative options. This chapter contains the reference and procedural information for the Configuration Management option.
PAGE 98
3 Voice System Administration Overview Figure 42. Voice System Administration Menu Voice System Administration Menu Options From the Voice System Administration menu, you have access to all of the major administrative features of the voice system. This section provides a brief overview of each of the administrative options on this menu. Application Package Administration The Application Package Administration menu provides administrative access to the applications currently installed on your system.
PAGE 99
3 Voice System Administration Backup/Restore Overview The Backup/Restore menu simplifies the backup and restore procedures by providing a user interface for differential and full backups. See “Common System Procedures," in UCS 1000 R4.2 System Reference, 585-313-210, for more information on performing backup and restore procedures.
PAGE 100
3 Voice System Administration Overview Feature Packages The Feature Packages menu provides administrative access to the optional feature packages currently installed. Reports The Reports menu allows you to generate and customize reports for: • Call classification and data • System messages • System traffic See Chapter 7, Common Administration , for more information on using the Reports menu. Switch Interfaces The Switch Interfaces menu provides access to administer digital switch parameters.
PAGE 101
3 Voice System Administration Unix Management Configuration Management The Unix Management menu provides capabilities to format diskettes and tapes, administer printers and modems, install and remove software, and modify the system time and date. See Chapter 6, Peripheral Administration , for more information on administering printers, modems, and terminals.
PAGE 102
3 Voice System Administration Configuration Management Figure 43. Configuration Management Menu The Configuration Management menu contains the following options: • Feature licensing (display Feature Licensing only) • Message administration • Remote alarming administration Note: Remote alarming is not supported on UCS 1000 R4.2 systems. • System control • Voice equipment See Chapter 5, Database Administration , for information on Database Administration.
PAGE 103
3 Voice System Administration Feature Licensing Feature Licensing Feature Licensing allows customers to purchase features on a per–channel basis. Only Lucent services personnel can activate and change the feature licenses. Feature licenses cannot be modified by the administrator. An administrator can display and print a report of the current feature licenses. ! CAUTION: Your system’s machine name is used by the Feature Licensing software.
PAGE 104
3 Voice System Administration Note: Feature Licensing Figure 44 is a sample window. Your Display Feature Licensing window may look different depending on the feature packages you purchased. Figure 44. Display Feature Licensing Window UCS 1000 R4.
PAGE 105
3 Voice System Administration Feature Licensing Printing a Feature License Report To print a report of the current system feature licenses: 1 Start at the Display Feature Licensing window (Figure 44 on page 65) and press F8 (Actions). The system displays the Actions menu (Figure 45). Figure 45. Actions Menu 2 Select: > Print The system prints a copy of the Display Feature Licensing window (Figure 44 on page 65).
PAGE 106
3 Voice System Administration Message Administration Message Administration Messages are used to provide information about events and errors during system operations. System messages vary in content, priority, destination, and threshold parameters. Use the System Message Administration window to: • List all the parameters associated with a particular system message. • Add or remove a new destination to or from the current list of destinations for the current system message.
PAGE 107
3 Voice System Administration Message Administration Accessing Message Administration To access message administration: 1 Start at the Configuration Management menu (Figure 43 on page 63) and select: > Message Administration The system displays the System Message Administration window (Figure 46). Figure 46.
PAGE 108
3 Voice System Administration Message Administration 3 Press F3 (Save). The system displays the System Message Display window (Figure 47). Figure 47. System Message Display Window Table 4 on page 70 describes the fields in this window. UCS 1000 R4.
PAGE 109
3 Voice System Administration Table 4. Message Administration Field Descriptions for the System Message Display Window Field Description Message ID: Specifies a unique name for each message in the system. Message Priority: Specifies the urgency level of the message. The Message Priority may be NONE or – (for none), * (for minor), ** (for major), or *C (for critical). Message Destinations: Specifies a list of destinations where the message should be sent.
PAGE 110
3 Voice System Administration Table 4. Message Administration Field Descriptions for the System Message Display Window Field Description Threshold: Specifies the number of messages to be generated within the threshold period necessary to trigger the threshold action. Threshold Message ID: Specifies the ID of the message to be generated when a threshold is reached. The priority and the destinations for the threshold message should be meaningful as a thresholding action.
PAGE 111
3 Voice System Administration Message Administration Adding Message Destinations The system’s message log provides a complete account of all messages generated by the voice system. All system messages are assigned to the appropriate destination during installation. Note: If a message is changed from the event destination to the alarm destination, a similar change should be made on the message priority from none (–) to minor (*) and vice versa.
PAGE 112
3 Voice System Administration Message Administration 3 Enter the destination for the message you want to add in the Message Destination: field or press F2 (Choices) to select from a menu. Valid message destinations are: ~ stderr — The standard error of the process generating the message. Since most system processes redirect standard error to the system console, specifying this destination may result in the message being sent to the system console. ~ console — The system console or /dev/console.
PAGE 113
3 Voice System Administration Message Administration ~ event — Specifies that the delivery system send all event level messages (priority “–”) to the event log. The event log may be accessed via the display messages command or the Message Log Report window. 4 Press F3 (Save). The system redisplays the System Message Display window (Figure 47 on page 69) showing the new message destination. 5 Complete the Saving Changes and Exiting Message Administration on page 83 procedure.
PAGE 114
3 Voice System Administration Message Administration The system displays the Remove Message Destination window (Figure 49). Figure 49. Remove Message Destination Window 3 Enter the Message Destination that you want to remove in the Message Destination: field, or press F 2 (Choices) to select from a menu. Note: The destination on log is not a valid choice since this destination cannot be removed using the Remove Message Destination window. 4 Press F3 (Save).
PAGE 115
3 Voice System Administration Message Administration Adding Thresholds Message thresholds are triggering devices that alert operations personnel to take action when a certain number of messages are generated over a certain period of time. Message thresholding allows for escalation of message priority or criticality. A system message may be of little concern when it occurs in small numbers over long time intervals.
PAGE 116
3 Voice System Administration Message Administration 2 Press F3 (Add–Thsh). The system displays the Add Threshold window (Figure 50). Figure 50. Add Threshold Window 3 Enter a nonnegative integer threshold value or none in the Threshold: field. 4 Enter THR001 (for none), THR002 (for minor), THR003 (for major), or THR004 (for critical) in the Threshold Message Id: field, or press F2 (Choices) to select from a menu. 5 Press F3 (Save).
PAGE 117
3 Voice System Administration Message Administration Removing Thresholds This procedure allows you to remove a threshold or a threshold message ID pair from the list of thresholds for the current system message. To remove a message threshold: 1 Start at the System Message Display window (Figure 47 on page 69) for a given message, and press F8 (Chg-Keys). The system displays the alternate set of function keys. 2 Press F4 (Rem-Thsh). The system displays the Remove Threshold window (Figure 51). Figure 51.
PAGE 118
3 Voice System Administration Message Administration 5 Complete the Saving Changes and Exiting Message Administration on page 83 procedure. The system installs the changes on the voice system. Modifying Message Priorities This procedure allows you to modify message priority. When the system is installed, each message is assigned a particular priority. In most cases, these priorities are appropriate and do not need to be modified.
PAGE 119
3 Voice System Administration Message Administration To modify a message priority: 1 Start at the System Message Display window (Figure 47 on page 69) for a given message, and press F8 (Chg-Keys). The system displays the alternate set of function keys. 2 Press F5 (Msg–Prio). The system displays the System Message Priority window (Figure 52). Figure 52. System Message Priority Window 3 Enter a priority in the Message Priority: field or press F 2 (Choices) to select from a menu. 4 Press F3 (Save).
PAGE 120
3 Voice System Administration Message Administration Modifying Threshold Periods This procedure allows you to modify the system message threshold period, or the interval of time over which messages are counted for a given threshold. To modify a threshold period: 1 Start at the System Message Display window (Figure 47 on page 69) for a given message, and press F8 (Chg-Keys). The system displays the alternate set of function keys. 2 Press F6 (Thsh-Per).
PAGE 121
3 Voice System Administration Message Administration You must enter the threshold period as a time interval with the following syntax: number[dimension] number[dimension] where number is a positive integer and dimension is one of the following single characters: ~ w for weeks ~ d for days ~ h for hours ~ m for minutes ~ s for seconds Table 5 provides examples of threshold periods and the required syntax. Table 5.
PAGE 122
3 Voice System Administration Message Administration The system displays the System Message Display window (Figure 47 on page 69) showing the new threshold period. 5 Complete the Saving Changes and Exiting Message Administration on page 83 procedure. The system installs the changes on the voice system. Saving Changes and Exiting Message Administration ! CAUTION: You MUST perform this procedure if you want to save your message administration changes.
PAGE 123
3 Voice System Administration System Control System Control Use the System Control menu to: • Display the status of the UCS 1000 R4.2 system • Start and stop the voice system • Diagnose circuit cards, channels, and buses To access the System Control menu: 1 Start at the Configuration Management menu (Figure 43 on page 63) and select: > System Control The system displays the System Control menu (Figure 54). Figure 54. System Control Menu UCS 1000 R4.
PAGE 124
3 Voice System Administration System Control Diagnose The Diagnose menu allows you to perform diagnostics on system equipment. Diagnose Equipment You can run diagnostics on E1/T1, LSPS, and SSP circuit cards. Run diagnostics whenever the system displays a message indicating circuit card failure. To diagnose equipment: 1 Start at the System Control menu (Figure 54 on page 84) and select: > Diagnose > Diagnose Equipment The system displays the Diagnose Equipment window (Figure 55). Figure 55.
PAGE 125
3 Voice System Administration System Control Table 6 describes the fields in this window. Table 6. Field Descriptions for Diagnose Equipment Window Field Description Equipment to diagnose: Specifies whether the type of equipment to be diagnosed is a circuit card or a bus. Enter card or bus, or press F2 (Choices) to select from a menu. There is no default value for this field. This is a required field. Equipment number: A number that identifies each E1/T1, LSPS, or SSP circuit card.
PAGE 126
3 Voice System Administration System Control 2 Enter the information as described in Table 6 on page 86. 3 Press F3 (Save). The system displays a report showing the status of the specified equipment. 4 Press F6 (Cancel) repeatedly until you return to the System Control menu. For more information on diagnostics, see Chapter 2, "Diagnostics," of UCS 1000 R4.2 System Reference, 585-313-210.
PAGE 127
3 Voice System Administration System Control ! CAUTION: Renumbering voice channels shuts the system down immediately and restarts it. When you select this option, a warning is displayed and you are given the option of continuing with the procedure or returning to the System Control menu. To renumber voice channels: 1 Start at the System Control menu (Figure 54 on page 84) and select: > Renumber Voice Channels The system displays the Renumber Voice Channels window (Figure 56). Figure 56.
PAGE 128
3 Voice System Administration System Control Reporting Voice System Status To see whether the voice system is running or stopped, and to view the current voice system run level. 1 Start at the System Control menu (Figure 54 on page 84) and select: > Report Voice System Status The system displays the Status of Voice System window (Figure 57). Figure 57. Status of Voice System Window 2 Press F1 (Acknowledge Message). The system returns to the System Control menu (Figure 54 on page 84). UCS 1000 R4.
PAGE 129
3 Voice System Administration System Control Stopping the Voice System This procedure stops the voice system by taking all system channels out of service with the option to wait for in-progress calls to end. Stopping the system is usually done when you are performing some type of routine service such as backup and restore.
PAGE 130
3 Voice System Administration System Control 2 Enter a time interval between 60 and 600 seconds in the Seconds: field, or press F2 (Choices). The default is 180. Note: During this wait time, all calls in progress are completed, but no new calls are accepted. 3 Press F3 (Save). The system displays a message telling you it will stop the voice system if you press EN TE R . Note: To return to the System Control menu without stopping the system, press F 6 (Cancel) 4 Press EN TE R .
PAGE 131
3 Voice System Administration System Control To shut down the system: 1 Start at the System Control menu (Figure 54 on page 84) and select: > Shut Down the Voice System The system displays the Wait Time window (Figure 59). Figure 59. Wait Time Window 2 Enter a time interval between 60 and 600 seconds in the Seconds: field or press F2 (Choices). 3 Press F3 (Save). The system waits the amount of time indicated, and then shuts the system down.
PAGE 132
3 Voice System Administration System Control Starting the Voice System This procedure allows you to start or restart the voice system. When this process is invoked, all channels that were deactivated when you stopped the voice system are returned to service in the maintenance state they had when the voice system was last running. To start the voice system: 1 Start at the System Control menu (Figure 54 on page 84) and select: > Start the Voice System 2 Press EN TE R .
PAGE 133
3 Voice System Administration Voice Equipment Voice Equipment Voice equipment includes those circuit cards and their associated channels in the system that provide voice system functionality. To access the Voice Equipment menu: 1 Start at the Configuration Management menu (Figure 43 on page 63) and select: > Voice Equipment The system displays the Voice Equipment menu (Figure 60). Figure 60. Voice Equipment Menu UCS 1000 R4.
PAGE 134
3 Voice System Administration Note: Voice Equipment The LSPS Functions and SSP Functions menu items appear only if you have the ASP Driver and LSPSset packages, respectively, installed.
PAGE 135
3 Voice System Administration Voice Equipment The system displays the Display Equipment window (Figure 61). Figure 61. Display Voice Equipment Window This window, by default, displays all channels currently in the system, including: ~ Channel circuit card and port (CD.PT) ~ Channel number (CHN) ~ Channel state (STATE) ~ Time of last state change (STATE_CHNG_TIME) ~ Associated service name (SERVICE_NAME) UCS 1000 R4.
PAGE 136
3 Voice System Administration Voice Equipment ~ Telephone number (PHONE) ~ Group number (GROUP) ~ Options (OPTS) ~ Circuit card type (TYPE) This window can be several pages long, depending on the display parameters for the window, and the equipment installed in the system. Press F2 (Prev Page) and F3 (Next Page) to move up and down through the pages of this window. Press F4 (First Page) to view the first page of the window. Press F 5 (Last Page) to view the last page of the window.
PAGE 137
3 Voice System Administration Voice Equipment Modifying the You can tailor the Display Voice Equipment window to show a full range of Display Voice channels or a subrange. The parameters you specify are saved in a file and Equipment Window remain in effect until you change them. Parameters To change the display parameters: 1 Start at the Display Voice Equipment window (Figure 61 on page 96) and press F8 (Actions). The system displays the Actions menu (Figure 62). Figure 62.
PAGE 138
3 Voice System Administration Voice Equipment The system displays the Modify Display Voice Equipment window (Figure 63). Figure 63. Modify Display Voice Equipment Window 3 Enter one of the following in the Equipment: field, or press F 2 (Choices) to select from a menu. ~ card — This parameter displays the version of software running on each circuit card (in the FUNCTION: field), circuit card options, and the circuit card O.S. Index (slot number) for each of the voice system circuit cards installed.
PAGE 139
3 Voice System Administration • Voice Equipment E1/T1: The circuit card parameter also shows all channel information (with the first two columns in the order CHAN, then CD.PT), since these types of circuit cards also have associated channels. ~ channel (default) — Information displayed with the channel and card parameters is almost identical.
PAGE 140
3 Voice System Administration Voice Equipment 6 (Optional) In the State: field, enter a maintenance state, or press F2 (Choices) to select from a menu. This field limits the voice equipment display to circuit cards or channels in a particular state. If you leave this field blank, all maintenance states are displayed. See Equipment State on page 103 for a list and description of each maintenance state. 7 (Optional) In the Service: field, enter a service name, or press F2 (Choices) to select from a menu.
PAGE 141
3 Voice System Administration Note: Voice Equipment All the digital (E1/T1) circuit cards should be set to tdm. It is the only valid setting. To change voice equipment options for digital circuit cards: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > Equipment Options The system displays the Change Options of Voice Equipment window (Figure 64). Figure 64.
PAGE 142
3 Voice System Administration Voice Equipment Note that background speech plays at a lower volume than foreground speech. 3 Enter circuit card or channel in the Equipment: field, or press F2 (Choices) to select from a menu. If you specify a circuit card, the option is set for all channels of that circuit card. 4 Enter a single number or range of numbers to select the voice circuit cards or channels to change in the Equipment Number: field, or enter all (default). 5 Press F3 (Save).
PAGE 143
3 Voice System Administration Voice Equipment and cannot be used for channels. The following is a description of the different maintenance states for voice equipment: • MANOOS (manual out-of-service) — Indicates that the circuit card or channel has been taken out of service with a command that was issued manually. Note: Change SSP and/or LSPS circuit cards to the MANOOS state only when there are no active calls on the system.
PAGE 144
3 Voice System Administration Voice Equipment • HWOOS (hardware out-of-service) — Indicates the circuit card or channel is out of service due to one or more of its dependencies being out of service, broken, or not physically connected. • NETOOS (network out-of-service) — For digital circuit cards or channels only: Indicates that the system is ready for the channel to go inserv, but is waiting for the network switch to also be ready for the channel to go inserv.
PAGE 145
3 Voice System Administration Table 7. Voice Equipment Valid Equipment State Changes If a Card/Channel is . . . You May Change It to . . . For Equipment Type . . . MANOOS INSERV circuit cards or channels. INSERV MANOOS circuit cards or channels. FOOS MANOOS circuit cards or channels. NETOOS MANOOS digital circuit cards or channels. HWOOS MANOOS circuit cards or channels. BROKEN MANOOS circuit cards or channels.
PAGE 146
3 Voice System Administration Voice Equipment The system displays the Change State of Voice Equipment window (Figure 65). Figure 65. Change State of Voice Equipment Window 2 Enter the state to which the designated equipment should be changed in the New State: field or press F2 (Choices) to select from a menu. Valid choices are inserv (in service) and manoos (manual out–of–service). 3 Enter channel or card for the type of equipment in the Equipment: field, or press F2 (Choices) to select from a menu.
PAGE 147
3 Voice System Administration Voice Equipment 6 Press F3 (Save). The system changes the maintenance state of the selected voice equipment. Suggestions for Changing the Maintenance State of Channels Use the following information to help you determine why a channel may be placed in a given maintenance state. Manoos E1/T1 Channels Using E&M Protocol The following suggestions apply only to individual MANOOS E1/T1 channels using the E&M protocol.
PAGE 148
3 Voice System Administration Voice Equipment again at the beginning. Consequently, the caller could receive a busy signal even though there might be other idle channels that are in service. Ideally, the switch should use all inserv channels before attempting to use any MANOOS channels. You can force the switch to use inserv channels before using MANOOS channels by requesting a switch hunting pattern that always scans for idle channels starting at the beginning of the hunt group.
PAGE 149
3 Voice System Administration Assigning Groups to Channels Voice Equipment To assign an equipment group to channels: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > Groups to Channels > Assign The system displays the Assign Channels to Groups window (Figure 66). Figure 66. Assign Channels to Groups Window 2 Enter the channel or range of channels that you want to assign to equipment groups in the Channels: field.
PAGE 150
3 Voice System Administration Voice Equipment 3 Enter the equipment group or groups to which you want to assign the channels in the Groups: field. Type a single equipment group number, or a range of equipment group numbers separated by commas or spaces. Valid equipment group numbers are 0 to 30. Note: Equipment group 31 is a reserved group. It is used to specify channels that the system should ignore when it executes a soft seizure (soft_szr command).
PAGE 151
3 Voice System Administration Voice Equipment Unassigning To unassign an equipment group to channels: Groups to Channels 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > Groups to Channels > Unassign The system displays the Unassign Channels From Groups window (Figure 67). Figure 67. Unassign Channels From Groups Window 2 Enter the channel or range of channels that you want to unassign to equipment groups in the Channels: field.
PAGE 152
3 Voice System Administration Voice Equipment 3 Enter the equipment group or groups to which you want to unassign the channels in the Groups: field. Type a single equipment group number, or a range of equipment group numbers separated by commas or spaces. Valid equipment group numbers are 0 to 30, with equipment group 31 used as a reserved group. 4 Press F3 (Save). The system unassigns the specified channels from the selected equipment groups.
PAGE 153
3 Voice System Administration Assigning LSPS Functions Voice Equipment To assign functions to LSPS circuit cards: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > LSPS Functions > Assign/Change LSPS Functions The system displays the Assign LSPS Functions window (Figure 68). Figure 68. Assign LSPS Functions Window UCS 1000 R4.
PAGE 154
3 Voice System Administration Voice Equipment ! CAUTION: Be careful when making assignments and reassignments. Assignments made in the Assign LSPS Functions window overwrite any other assignments that are currently in effect on the specified circuit cards. 2 Enter a single number or press F2 (Choices) to select from a menu in the Card Number: field. After entering the card number, the current settings are displayed. 3 In the remaining fields, enable the function with Yes or disable with No.
PAGE 155
3 Voice System Administration Table 8. Displaying LSPS Functions Voice Equipment Valid LSPS Function Combinations Function Valid for LSPS? Text-to-Speech Yes Code + Play Yes Code + FlexWord Yes Code + WholeWord Yes Code + WholeWord + Echo Cancellation Yes WholeWord + Echo Cancellation Yes To view the current assignments for the LSPS cards in your system: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > LSPS Functions > Display LSPS Functions UCS 1000 R4.
PAGE 156
3 Voice System Administration Voice Equipment The system displays the Display LSPS Functions window (Figure 69). Figure 69. Display LSPS Functions Window 2 In the Card Number: field, enter a single number or press F2 (Choices) to select from a menu. After entering the card number, the current settings are displayed (Figure 70 on page 118). UCS 1000 R4.
PAGE 157
3 Voice System Administration Voice Equipment Figure 70. Example Display LSPS Functions Window 3 Press F6 (Cancel) twice to return to the Voice Equipment menu (Figure 60 on page 94). SSP Functions Using the SSP Functions menu option, you can assign functions to SSP circuit cards or to change the functions that are currently assigned. The SSP card is in the UNASSIGNED state when it is first installed. The card cannot be put into service while in the UNASSIGNED state.
PAGE 158
3 Voice System Administration Assigning SSP Functions Voice Equipment To assign functions to SSP circuit cards: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > SSP Functions > Assign/Change SSP Functions The system displays the Assign/Change Functions to SSP Cards window (Figure 71). Figure 71. Assign/Change Functions to SSP Cards Window UCS 1000 R4.
PAGE 159
3 Voice System Administration Voice Equipment ! CAUTION: Be careful when making assignments and reassignments. Assignments made in the Assign Functions to SSP Cards window overwrite any other assignments that are currently in effect on the specified circuit cards. 2 Enter a single number or press F2 (Choices) to select from a menu in the Card Number: field. After entering the card number, the current settings are displayed. 3 In the remaining fields, enable the function with Yes or disable with No.
PAGE 160
3 Voice System Administration Displaying SSP Functions Voice Equipment To view the current assignments for the SSP cards in your system: 1 Start at the Voice Equipment menu (Figure 60 on page 94) and select: > SSP Functions > Display SSP Functions The system displays the Display SSP Functions window (Figure 72). Figure 72. Display SSP Functions Window UCS 1000 R4.
PAGE 161
3 Voice System Administration Voice Equipment 2 In the Card Number: field, enter a single number or press F2 (Choices) to select from a menu. After entering the card number, the current settings are displayed (Figure 73). Figure 73. Example Display SSP Functions Window 3 Press F6 (Cancel) twice to return to the Voice Equipment menu (Figure 60 on page 94). Voice Services The Voice Services menu option allows you to assign, display, and unassign channel and number services.
PAGE 162
3 Voice System Administration Voice Equipment > Voice Services The system displays the Voice Services menu (Figure 74). Figure 74. Channel Services Voice Services Menu The Channel Services menu option allows you to assign, display, and unassign channel services. To access the Channel Services menu: 1 Start at the Voice Services menu (Figure 74 on page 123) and select: > Channel Services UCS 1000 R4.
PAGE 163
3 Voice System Administration Voice Equipment The system displays the Channel Services menu (Figure 75). Figure 75. Channel Services Menu Assign Service The Assign Services to Channels window allows you to specify the service or application to use for incoming calls on one or more channels. To assign services to channels: 1 Start at the Channel Services menu (Figure 75 on page 124) and select: > Assign Service UCS 1000 R4.
PAGE 164
3 Voice System Administration Voice Equipment The system displays the Assign Services to Channels window (Figure 76). Figure 76. Assign Services to Channels Window 2 In the Channel Numbers: field, enter the channel number or range of numbers. Valid numbers range from 0 to the maximum number of channels in the system. You can enter multiple channels separated by commas or a range of channels using a dash. For example, an entry of 1, 3–5, 10 specifies channels 1, 3, 4, 5, and 10.
PAGE 165
3 Voice System Administration Voice Equipment special services are required for specific callers. DNIS (called party) is available with E1/T1 (E&M) and PRI. Another special service name “ANI” (calling party) is available with PRI. 4 Leave the Startup Service: field blank. 5 Press F3 (Save Assign). The system assigns the indicated services to the selected channel or range of channels. Display Channel Services The Display Channel Services window displays all currently assigned channel services.
PAGE 166
3 Voice System Administration Voice Equipment The system displays the Display Channel Services window (Figure 77). Figure 77. Display Channel Services Window UCS 1000 R4.
PAGE 167
3 Voice System Administration Voice Equipment Table 9 describes the columns in this window. Table 9.
PAGE 168
3 Voice System Administration Voice Equipment The system displays the Unassign Services from Channels window (Figure 78). Figure 78. Unassign Services from Channels Window 2 Enter the channel number or range of numbers to be unassigned in the Channel Numbers: field. Valid numbers range from 0 to the maximum number of channels in the system. You can enter multiple channels separated by commas or a range of channels using a dash. For example, an entry of 1, 3–5, 10 specifies channels 1, 3, 4, 5, and 10.
PAGE 169
3 Voice System Administration Number Services Voice Equipment The Number Services menu option allows you to assign, display, and unassign numbers services. To access the Number Services menu: 1 Start at the Voice Services menu (Figure 74 on page 123) and select: > Number Services The system displays the Number Services menu (Figure 79). Figure 79. Number Services Menu UCS 1000 R4.
PAGE 170
3 Voice System Administration Voice Equipment Assign Number Service The Assign Services to Number window allows you to specify a service or application to use for incoming calls on the called number (DNIS) or calling number (ANI). It is only valid for channels assigned to *DNIS_SVC. To assign number service: 1 Start at the Number Services menu (Figure 60 on page 94) and select: > Assign Service The system displays the Assign Number Service window (Figure 80). Figure 80.
PAGE 171
3 Voice System Administration Voice Equipment 2 Enter a number, range of numbers, or any in the Called Numbers: field. This number or range represents the telephone number or numbers to dial to reach the specified service. The number of digits must match those that the switch provides. You can enter numbers with a comma, a dash, or a space as delimiters. The first column contains a single number, the word any, or the first number in the range. The second column contains the last number in the range.
PAGE 172
3 Voice System Administration Voice Equipment 4 Enter a string of 16 characters or less in the Service Name: field or press F2 (Choices) to select from a menu. This field represents the name of the service that handles the incoming call on the channel or channels. 5 Press F3 (Save). The system assigns a service to the specified number or numbers. Displaying Number Services The Display Number Services window displays all currently assigned number services.
PAGE 173
3 Voice System Administration Voice Equipment The system displays the Display Number Services window (Figure 81). Figure 81. Display Number Services Window UCS 1000 R4.
PAGE 174
3 Voice System Administration Voice Equipment Table 10 describes the columns in this window. Table 10.
PAGE 175
3 Voice System Administration Voice Equipment The system displays the Unassign Number Service window (Figure 82). Figure 82. Unassign Number Service Window 2 Enter a number, range of numbers, or any in the Called Numbers: field. This number or range represents the telephone number or numbers to dial to reach the specified service. The number of digits must match those that the switch provides. You can enter numbers with a comma, a dash, or a space as delimiters.
PAGE 176
3 Voice System Administration Voice Equipment This number or range represents the caller’s (or calling party) number or numbers. The number of digits must match those that the switch provides. You can enter numbers with a comma, a dash, or a space as delimiters. The first column contains a single number, the word any, or the first number in the range. The second column contains the last number in the range.
PAGE 177
3 Voice System Administration FAX Administration 2 Select: > Print Note: You cannot print this report if a printer is not configured for use with the voice system. See Printer Administration on page 278 in Chapter 6, Peripheral Administration , for more information about printer administration. FAX Administration With the Next Generation FAX feature package, you can send and receive faxes. IRAPI commands are used to control the process.
PAGE 178
3 Voice System Administration FAX Administration Log messages FAX001 (FAX print operation filed) and FAX002 (FAX record operation failed) are described in UCS 1000 R4.2 System Reference, 585313-210, along with possible causes for the condition. Product ID Required The NGFAX feature package requires a unique identification number. To supply this number, access the Alarm Management window and, in the Product ID field, enter a 10-digit number starting with a "2".
PAGE 179
3 Voice System Administration FAX Administration The Alarm Management window is displayed (Figure 83). Figure 83. Alarm Management Window 2 In the Product ID field, enter a 10-digit number starting with a "2" that is unique within other UCS 1000 R4.2 systems that will be sending or receiving faxes. Do not enter information in the Alarm Destination field, even if the system prompts you for that information, and do not alter the information in the remaining fields. 3 Save before exiting. UCS 1000 R4.
PAGE 180
4 Switch Interface Administration Overview This chapter provides procedural information and reference information for administering the supported digital switch interfaces. The Switch Interfaces menu allows you to define the interaction between the system and the switches connected to it by allowing you to modify switch interface parameters and protocol options for digital interfaces. Switch Interfaces Hardware The circuit cards that provide digital interfaces have a unique card number (Card 1, Card 2...
PAGE 181
4 Switch Interface Administration Accessing the Switch Interfaces Menu Accessing the Switch Interfaces Menu To access the Switch Interfaces menu: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cvis_menu The system displays the Voice System Administration menu (Figure 84). Figure 84. Voice System Administration Menu UCS 1000 R4.
PAGE 182
4 Switch Interface Administration Accessing the Switch Interfaces Menu 4 Select: > Switch Interfaces 5 Press EN TE R . The system displays the Switch Interfaces menu (Figure 85). Figure 85. Switch Interfaces Menu UCS 1000 R4.
PAGE 183
4 Switch Interface Administration Digital Interfaces Digital Interfaces Digital interfaces are administered on a card-by-card basis; that is, digital parameters apply to individual digital circuit cards installed in the system.
PAGE 184
4 Switch Interface Administration Digital Interfaces To access the Digital Interfaces menu: 1 Start at the Switch Interfaces menu (Figure 85 on page 143) and select: > Digital Interfaces The system displays the Digital Interfaces menu (Figure 86). Figure 86. Digital Interfaces Menu Note: Figure 86 displays the installed digital protocol packages. A package must be installed before it is displayed in this menu.
PAGE 185
4 Switch Interface Administration Digital Interfaces Displaying Digital Interface Assignments The Display Digital Interface Assignments window displays the E1/T1 circuit cards installed in the voice system and the function to which each is assigned.
PAGE 186
4 Switch Interface Administration Digital Interfaces Figure 87. Display Digital Interface Assignments By default, a circuit card is marked unassigned. A protocol must be installed on the voice system before it can be assigned to an E1/T1 card (CWB2). See “E1/T1 Circuit Cards,” in Chapter 2, “Installing or Replacing Circuit Cards,” in UCS 1000 R4.2 Maintenance, 585-313-126, for more information on configuring the CWB2.
PAGE 187
4 Switch Interface Administration Table 11. Digital Interfaces Valid Parameter and Default Values for E1/T1 Digital Protocols Protocol Name Field Name Valid Parameter Values Framing/ Line Coding T1 A/B Robbedbit E&M Default ISDNPRI Layer 1 E1 CAS D4ZCS, ESFB8ZS, CEPTHDB3 D4ZCS ESFB8ZS CEPTHDB3 DTMF Muting Yes, No Yes Yes Yes CSU Distance 0–666 feet 0–133 feet 0–133 feet — Wink Time 10–2550 msec 230 msec — — Post Wink Delay1 10–2550 msec 80 msec — — Max.
PAGE 188
4 Switch Interface Administration Table 11.
PAGE 189
4 Switch Interface Administration Digital Interfaces T1 A/B Robbed-bit E&M Protocol Make sure that the switch to which the system is connected is programmed with the following options: Accessing T1 A/B Robbed-bit E&M Menu • The T1 interface uses wink start robbed-bit E&M signaling on a link using D4 framing with zero code suppression (ZCS).
PAGE 190
4 Switch Interface Administration Digital Interfaces The system displays the T1 A/B Robbed-bit E&M menu (Figure 88). Figure 88. Assigning T1 A/B Note: Robbed-bit E&M to Digital Circuit Cards T1 A/B Robbed-bit E&M Menu Before a new protocol can be assigned to a circuit card, any existing protocol must first be unassigned. See Unassigning T1 A/B Robbed-bit E&M to Digital Circuit Cards on page 161 below for more information.
PAGE 191
4 Switch Interface Administration Digital Interfaces To assign the T1 A/B Robbed-bit E&M protocol to a digital circuit card: 1 Start at the T1 A/B Robbed-bit E&M menu (Figure 88 on page 151) and select: > Assign Card The system displays the Assign Card: T1 A/B Robbed-bit E&M window (Figure 89 on page 153). UCS 1000 R4.
PAGE 192
4 Switch Interface Administration Figure 89. Digital Interfaces Assign Card: T1 A/B Robbed-bit E&M Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. The Card Number: field is blank in Figure 89. After you enter the circuit card number, certain E1-only fields disappear (Idle Code:, A-LAW or MU-LAW:, and CRC:). UCS 1000 R4.
PAGE 193
4 Switch Interface Administration Digital Interfaces 3 Enter Yes to enable or No to disable in the DTMF Muting: field, or press F2 (Choices) to select from a menu. Yes is the default. Enter Yes to use dual-tone multifrequency (DTMF) muting to reduce false DTMF recognitions. Such false recognitions sometimes result from the network echoing back sounds that the voice system falsely recognizes as touchtones. Enter No when the interface is used for bridging; DTMF needs to pass through without muting.
PAGE 194
4 Switch Interface Administration Digital Interfaces 8 Enter the type of addressing to be used with outgoing calls, either DTMF, MF, or DECADIC in the Outgoing Addressing Type: field. The default is DTMF. 9 Enter the type of addressing to be used with incoming calls, either DTMF, MF, or DECADIC in the Incoming Addressing Type: field. The default is DTMF. 10 Enter the type of signaling to be used with outgoing calls, either Wink or Immediate in the Outgoing Signaling Type: field. The default is Wink.
PAGE 195
4 Switch Interface Administration Digital Interfaces speech before it is coded, 2000 doubles it a second time, 2828 doubles it a third time, and so on. To decrease the incoming speech volume, multiply by 0.707 to approximately half the value or decrease it by 3 dB. Therefore, a value of 707 in the field reduces the volume by half, 500 by half a second time, and so on. See Table 15 on page 192 for the relationship between the volume number and the actual change in volume expressed in decibels.
PAGE 196
4 Switch Interface Administration Digital Interfaces 15 Ignore the last two fields: Idle Code: and A-LAW or MU-LAW:. 16 Press F3 (Save). The system assigns the protocol to the selected circuit card. Change T1 A/B Robbed-bit E&M Parameters The circuit card must first be assigned to the T1 A/B Robbed-bit E&M protocol to use this procedure. See Assigning T1 A/B Robbed-bit E&M to Digital Circuit Cards on page 151 for more information about making the initial assignment.
PAGE 197
4 Switch Interface Administration Digital Interfaces The system displays the Change Parameters: T1 A/B Robbed-bit E&M window (Figure 90). Figure 90. Change Parameters: T1 A/B Robbed-bit E&M Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. UCS 1000 R4.
PAGE 198
4 Switch Interface Administration Digital Interfaces The Card Number: field is blank in Figure 90 on page 158. After you enter the circuit card number, certain E1-only fields disappear (Idle Code:, ALAW or MU-LAW:, and CRC:). 3 Change any of the parameters as described in Assigning T1 A/B Robbed- bit E&M to Digital Circuit Cards on page 151. 4 Press F3 (Save). The system changes the protocol parameters on the selected circuit card.
PAGE 199
4 Switch Interface Administration Digital Interfaces The system displays the Display Parameters: T1 A/B Robbed-bit E&M window (Figure 91). Figure 91. Display Parameters: T1 A/B Robbed-bit E&M Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. UCS 1000 R4.
PAGE 200
4 Switch Interface Administration Digital Interfaces The Card Number: field is blank in Figure 91. After you enter the circuit card number, certain E1-only fields disappear (Idle Code:, A-LAW or MU-LAW:, and CRC:). The system displays the parameter values for the selected circuit card. 3 Press F6 (Cancel) to return to the T1 A/B Robbed-bit E&M menu.
PAGE 201
4 Switch Interface Administration Digital Interfaces The system displays the Unassign Card: T1 A/B Robbed-bit E&M window (Figure 92). Figure 92. Unassign Card: T1 A/B Robbed-bit E&M Screen 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. The system displays the current parameter values for the selected circuit card. UCS 1000 R4.
PAGE 202
4 Switch Interface Administration Digital Interfaces 3 Press F3 (Save). The system removes the T1 A/B Robbed-bit E&M assignment from the selected circuit card. 4 Press F6 (Cancel) repeatedly to return to the Digital Interfaces menu. E1 CAS Protocols The UCS 1000 R4.2 supports the E1 Channel Associated Signaling (CAS) protocol Mexico for use with the DEFINITY switch.
PAGE 203
4 Switch Interface Administration Digital Interfaces The system displays the Digital R2 MFC Protocol - Mexico menu (Figure 93). Figure 93. Digital R2 MFC Protocol - Mexico Menu Use the procedures below to assign or unassign the Digital R2 MFC - Mexico protocol to or from digital circuit cards, and administer the switch interface parameters.
PAGE 204
4 Switch Interface Administration Digital Interfaces If you also change digital protocol assignments on the voice system, you must make the change on the switch. To assign the Mexico protocol to an E1 circuit card: 1 Start at the Digital R2 MFC Protocol - Mexico menu (Figure 93 on page 164) and select: > Assign Card UCS 1000 R4.
PAGE 205
4 Switch Interface Administration Digital Interfaces The system displays the Assign Card: Digital R2 MFC Protocol - Mexico window (Figure 94). Figure 94. Assign Card: Digital R2 MFC Protocol - Mexico Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. 3 Enter the values as shown in Table 12 on page 167 for each of the fields in the window.
PAGE 206
4 Switch Interface Administration Table 12. Digital Interfaces Parameter Values for Assign Card: Digital R2 MFC - Mexico Window Field Name Value Framing/Line Coding: CEPTHDB3 Idle Code: 01010100 DTMF Muting: Yes A-LAW or MU-LAW: A-LAW CRC: Yes Max. Digits in Called Number: 4 Outgoing Addressing Type: MFC Incoming Addressing Type: MFC Incoming Speech Volume: 1414 Outgoing Speech Volume:1 707 1 This field is displayed only if the optional SSP Text-to-Speech package is installed.
PAGE 207
4 Switch Interface Administration Digital Interfaces Changing Digital R2 MFC - Mexico Parameters The E1 circuit card must first be assigned to the Digital R2 MFC - Mexico protocol to use this procedure. See Assigning the Digital R2 MFC - Mexico Protocol to E1 Circuit Cards on page 164 for more information about making the initial assignment. Note: Before attempting to make any assignment changes to circuit cards, they must be in the “manoos” state.
PAGE 208
4 Switch Interface Administration Figure 95. Digital Interfaces Change Parameters: Digital R2 MFC Protocol - Mexico Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the current values for the circuit card number entered. 3 Change any of the parameters described in Assigning the Digital R2 MFC - Mexico Protocol to E1 Circuit Cards on page 164. 4 Press F3 (Save).
PAGE 209
4 Switch Interface Administration Digital Interfaces Displaying Digital R2 MFC - Mexico Parameters The E1 circuit card must first be assigned to the Digital R2 MFC - Mexico protocol to use this procedure. See Assigning the Digital R2 MFC - Mexico Protocol to E1 Circuit Cards on page 164 for more information about making the initial assignment.
PAGE 210
4 Switch Interface Administration Figure 96. Digital Interfaces Display Parameters: Digital R2 MFC Protocol - Mexico Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. The system displays the parameter values for the selected circuit card. 3 Press F6 (Cancel) to return to the Digital R2 MFC Protocol - Mexico menu. UCS 1000 R4.
PAGE 211
4 Switch Interface Administration Digital Interfaces Unassigning the Digital R2 MFC - Mexico Protocol to E1 Circuit Cards Note: Before attempting to make any assignment changes to circuit cards, they must be in the “manoos” state. See Equipment State on page 103 in Chapter 3, Voice System Administration , for additional information.
PAGE 212
4 Switch Interface Administration Figure 97. Digital Interfaces Unassign Card: Digital R2 MFC Protocol - Mexico Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. The system displays the current parameter values for the selected circuit card. UCS 1000 R4.
PAGE 213
4 Switch Interface Administration Digital Interfaces 3 Press F3 (Save). The system removes the Digital R2 MFC - Mexico protocol assignment from the selected circuit card. 4 Press F6 (Cancel) repeatedly to return to the Digital Interfaces menu. ISDN-PRI Layer 1 Protocol Accessing the ISDN-PRI Layer 1 Menu Note: All selected options must match the corresponding options on the network switch. If they do not, service problems can occur.
PAGE 214
4 Switch Interface Administration Figure 98. Assigning an ISDN- Note: PRI Layer 1 to Digital Circuit Cards Digital Interfaces ISDN-PRI Layer 1 Menu Before a new protocol can be assigned to a circuit card, any existing protocol must first be unassigned. See Unassigning T1 A/B Robbed-bit E&M to Digital Circuit Cards on page 161 for more information. Before attempting to make any assignment changes to circuit cards, they must be in the MANOOS state.
PAGE 215
4 Switch Interface Administration Digital Interfaces To assign the ISDN-PRI Layer 1 to a digital circuit card: 1 Start at the ISDN-PRI Layer 1 menu (Figure 98 on page 175) and select: > Assign Card The system displays the Assign Card: ISDN-PRI Layer 1 window (Figure 99). Figure 99. Assign Card: ISDN-PRI Layer 1 Window UCS 1000 R4.
PAGE 216
4 Switch Interface Administration Digital Interfaces 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. 3 Enter the framing/line coding in the Framing/Line Coding: field, or press F 2 (Choices) to select from a menu. The valid values for T1 PRI are D4ZCS or ESFB8ZS. ESFB8ZS is the default.
PAGE 217
4 Switch Interface Administration Digital Interfaces Up to 13 PRI T1 circuit cards can have a D-channel. The voice system supports up to 13 23B+D interfaces (each with its own D-channel and each set to Yes in this field) or up to 311 B+D (where one card has the Dchannel and the other twelve cards are controlled by that D-channel and are set to No in this field since they do not have a D-channel). The system also supports configurations with 2 to 12 D-channels.
PAGE 218
4 Switch Interface Administration Digital Interfaces To decrease the incoming speech volume, multiply by 0.707 to approximately half the value or decrease it by 3 dB. Therefore, a value of 707 in the field reduces the volume by half, 500 by half a second time, and so on. See Table 15 on page 192 for the relationship between the volume number and the actual change in volume expressed in decibels. Note: The incoming speech volume value is set on a per-card basis for digital circuit cards.
PAGE 219
4 Switch Interface Administration Digital Interfaces 10 Enter the cable distance, in feet, between the Channel Service Unit (CSU) and the voice system in the CSU Distance: field, or press F2 (Choices) to select from a menu. Valid values are 0–133, 134–266, 267–399, 400–533, and 534–666. The default is 0–133. If there is no CSU, the value entered in this field should be the cable distance between the voice system and the equipment to which it is connected.
PAGE 220
4 Switch Interface Administration PRI Layer 2 and Layer 3 Parameters Digital Interfaces Your PRI service provider may need to know some Layer 2 and Layer 3 parameters used by the voice system. Table 13 and Table 14 on page 182 provide a list of the most commonly requested parameters. Incoming calls to the voice system should be provisioned so that the channel number is exclusive and not preferred.
PAGE 221
4 Switch Interface Administration Digital Interfaces Table 14. PRI Layer 3 Parameters Layer 3 Parameter Value (seconds) Timer T302 15 Timer T303 4 Timer T305 4 Timer T308 4 Timer T310 10 Timer T313 4 Timer T316 120 Timer T3M1 120 Timer T309 30 Changing ISDN-PRI The circuit card must first be assigned to the ISDN-PRI Layer 1 protocol to Layer 1 Card use this procedure.
PAGE 222
4 Switch Interface Administration Digital Interfaces To change the ISDN-PRI Layer 1 parameters: 1 Start at the ISDN-PRI Layer 1 menu (Figure 98 on page 175) and select: > Change Parameters The system displays the Change Parameters: ISDN-PRI Layer 1 window (Figure 100). Figure 100. Change Parameters: ISDN-PRI Layer 1 Window UCS 1000 R4.
PAGE 223
4 Switch Interface Administration Digital Interfaces 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. 3 Change any of the parameters as described in Assigning an ISDN-PRI Layer 1 to Digital Circuit Cards on page 175. 4 Press F3 (Save). The system changes the specified parameters for the selected circuit card.
PAGE 224
4 Switch Interface Administration Digital Interfaces The system displays the Display Parameters: ISDN-PRI Layer 1 window (Figure 101). Figure 101. Display Parameters: ISDN-PRI Layer 1 Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. Initially, all fields are populated with the default values for the circuit card number entered. The system displays the parameter values for the selected circuit card.
PAGE 225
4 Switch Interface Administration Unassigning ISDNPRI Layer 1 Card Note: Digital Interfaces Before attempting to make any assignment changes to circuit cards, they must be in the MANOOS state. See Equipment State on page 103 in Chapter 3, Voice System Administration , for additional information. If you change digital protocol assignments on the voice system, you must also make the change on the switch.
PAGE 226
4 Switch Interface Administration Figure 102. Digital Interfaces Unassign Card: ISDN-PRI Layer 1 Window 2 Enter the circuit card number in the Card Number: field, or press F2 (Choices) to select from a menu. The system displays the current parameter values for the selected circuit card. 3 Press F3 (Save). The system removes the ISDN-PRI Layer 1 assignment from the selected circuit card. 4 Press F6 (Cancel) repeatedly to return to the Digital Interfaces menu. UCS 1000 R4.
PAGE 227
4 Switch Interface Administration Digital Interfaces T1 for 4ESS Applications The following options should be used when connecting a the system to a 4ESS switch via an E1/T1 line when using the E&M protocol. Note: • Some parameters on the switch side may require that you stop and restart the voice system once you have made changes. For example, when changing the frame format from D4ZCS to ESF, your PRI link to the switch may not come up if you have not stopped and started the voice system.
PAGE 228
4 Switch Interface Administration • Incoming/Outgoing Start Dialing: wink/wink • Incoming/Outgoing Addressing: DTMF/DTMF Digital Interfaces ~ Timing Source: Looped Timed • 4ESS Options The following information is requested by AT&T when provisioning the 4ESS switch for an E1/T1 connection: ~ TYPE CPE: DIGITAL PBX/ACD (WITH DS1 INTERFACE) • 4E NETWORK SWITCHED BASED SERVICES: MEG (Megacom), MEG8 (Megacom 800), or MULTIQUEST* as desired • ACCESS TYPE: T1 • TRUNK OPERATION: The voice system always
PAGE 229
4 Switch Interface Administration Digital Interfaces • START DIAL SIGNALING PROVIDED BY CPE: WK • START DIAL SIGNALING PROVIDED TO CPE: WK (senderized operation) • CPE DOES NOT SUPPORT DIFFERENT SIGNALING BIDIRECTIONALLY • NUMBER OF DIGITS OUTPULSED TO CPE: This number should match the number selected in the “Maximum Digits in Called Number” E1/T1 option • THE CPE CAN ACCEPT “O” AS THE FIRST DIGIT • GLARE CONTROL: CPE WILL YIELD (WILL RELEASE) • DIRECT INWARD DIAL (DID): N • PBX ANSWER SUP
PAGE 230
4 Switch Interface Administration Changing Switch System Parameters Changing Switch System Parameters To change the switch system parameters: Note: You must stop the voice system before changing the switch system parameters. 1 Start at the Switch Interfaces menu (Figure 85 on page 143)and select: > Change Switch System Parameters The system displays the Change Switch System Parameters window (Figure 103). Figure 103. Change Switch System Parameters UCS 1000 R4.
PAGE 231
4 Switch Interface Administration Changing Switch System Parameters 2 Change the field values using the information in Table 15 and Table 16 on page 193. Table 15. DTMF Tone Table Keys on the Telephone Keypad UCS 1000 R4.
PAGE 232
4 Switch Interface Administration Changing Switch System Parameters Table 16. Switch System Parameters Field Name Description Valid Values Background Output Volume: This parameter specifies the adjustment to the output volume level in percent for the speech being played in the background. A numeric entry for the percentage Hunt Group Method: This parameter specifies the order of hunting for idle channels. Ascending (default), descending, or random Press F2 (Choices) to select from a menu.
PAGE 233
4 Switch Interface Administration Displaying Switch System Parameters Displaying Switch System Parameters The Display Switch System Parameters window allows you to view the current setting for the switch system parameters. To display the switch system parameters: Note: You must stop the voice system before changing the switch system parameters.
PAGE 234
4 Switch Interface Administration Figure 104. Displaying Switch System Parameters Display Switch System Parameters Window 2 Press F6 (Cancel) to return to the Switch Interfaces menu. UCS 1000 R4.
PAGE 235
5 Database Administration Overview This chapter provides information and procedures on how to administer ORACLE databases for use with the voice system. The information in this chapter is applicable only if you have the ORACLE 7 software installed on your system. This chapter includes procedures for determining database space requirements, sizing the databases, and administering database tables. This chapter also reviews the SQL*PLUS software program, a tool used to access the ORACLE database.
PAGE 236
5 Database Administration Call Data Tables Call Data Tables The base ORACLE software package creates the following database tables to store call data (Table 17). Note: All these tables are created and owned by the sqlplus user sti/sti. Table 17. ORACLE Call Data Tables Table Name Table Description CCA Call classification analysis data (contains one record for each attempted transfer or outdial).
PAGE 237
5 Database Administration Table 17. Call Data Tables ORACLE Call Data Tables Table Name Table Description EVENTS Event data defined for a service (contains one record per event). There can be more than one EVENTS records per SERVICE record. EVSUM Summary data for the EVENTS table (contains one record per hour and event number). TRASUM Overall traffic summary data (contains one record per hour and channel). 2 of 2 1 The CALL and SERVICE tables replace the CDH table.
PAGE 238
5 Database Administration Call Data Tables CCA Table The CCA table contains the following information: • START_TIME is a date field that specifies the starting time of each attempted transfer or outdialed call. • PHONE_NUM is a variable-length character field that specifies the telephone number of an attempted transfer or outdialed call. This field can be up to 16 characters in length. • RESULT_CODE is a variable-length character field that indicates the disposition of the call.
PAGE 239
5 Database Administration Call Data Tables • SUM_TOT is a numeric field that indicates the number of calls transferred or outdialed in this period with this disposition and associated telephone number. • RESULT_CODE is a variable-length character field that indicates the disposition of the call. This field can be 1 or more characters in length. Note: Records are generated on a per-hour, per-telephone number, and per-result_code basis.
PAGE 240
5 Database Administration Call Data Tables SERVICE Table The SERVICE table contains the following information: • CID is a numeric field that specifies a non-unique identification number that joins multiple SERVICE.CID to one CALL.CID. Each call creates one or more SERVICE records, depending on the number of services used to handle the call. All SERVICE records associated with a call have the same SERVICE.CID as the CALL.CID in the CALL record.
PAGE 241
5 Database Administration Call Data Tables CDHSUM Table The CDHSUM table contains the following information: • SUMID is a numeric field that specifies a unique identification number that joins CDHSUM.SUMID to EVSUM.SUMID. • SERVICE is a variable-length character field that specifies the service (application) name. This field can be up to 16 characters in length. • START_TIME is a date field that specifies the start of the hour (for example, 10:00:00).
PAGE 242
5 Database Administration Call Data Tables records associated with this call have the same SID number as the SID field of the corresponding SERVICE record. See Relationship Between the CALL, SERVICE, and EVENT Tables on page 204 for more information. EVSUM Table The EVSUM table contains the following information: • SUMID is a numeric field that specifies a unique identification number. Note: The values in this field are related to the SUMID values in the CDHSUM table.
PAGE 243
5 Database Administration Call Data Tables TRASUM Table The TRASUM table contains the following information: • START_TIME is a date field that specifies the start of hour (for example, 10:00:00). • CHANNEL is a numeric field that indicates the channel number. This field can be up to 3 digits in length. • CALL_TOT is a numeric field that specifies the total number of calls. • DUR_TOT is a numeric field that specifies the total duration in seconds.
PAGE 244
5 Database Administration Call Data Tables • Each record in the CALL table is linked to one or more records in the SERVICE table. • Each record in the SERVICE table is linked to zero or more records in the EVENTS table. Figure 105. Relationship Between the CALL, SERVICE and EVENTS Tables UCS 1000 R4.
PAGE 245
5 Database Administration Call Data Tables Resizing Call Data Tables The sizes of the call data handling tables are defined in the /oracle/dist/cdh/sql file. Although the sizes are carefully engineered, it is possible that one or more of the tables should be increased to accommodate the heavier traffic on your system or the greater number of events defined in your applications. The most likely candidates for resizing are the EVENTS, SERVICE, and CALL tables, and their index tables.
PAGE 246
5 Database Administration Call Data Tables 6 Write down this number. 7 Use the UNIX editor vi to modify the cdh.sql file as follows: a Find the create table xxx statement block, where xxx is the table name (for example, CALL, SERVICE or EVENTS). b Modify the statement storage (initial 999k) to a bigger number, where 999 is the current initial size for the table and k stands for kilobytes (1024 bytes).
PAGE 247
5 Database Administration Call Data Tables 9 Enter systblsav file The system saves the table storage information, where file is a UNIX file or a device name where the data will be saved, such as, /dev/rmt/c0s0. 10 Enter sqlplus \@ /oracle/dist/cdh.sql The system reinitializes the table or tables. 11 Enter systblres file The system restores the table storage information from the UNIX file or device name where it was saved in step 9, such as, /dev/rmt/c0s0.
PAGE 248
5 Database Administration Call Data Tables 2 Enter your root password. The system displays the system prompt #. 3 Enter sqlplus sti/sti The system starts a sqlplus session. 4 Enter describe CCA Note: If the table name is lowercase, do not use the describe command.
PAGE 249
5 Database Administration Call Data Tables Table Searches Think of a database table as a book. If you want to find information on a subject, you must search the book to find it. However, checking the index first helps you to locate the information in the book much more quickly than paging through the book. The same is true for finding data in a database table. Indexes and Key Fields For large databases, you can use indexes on key fields to greatly reduce the time necessary to search the tables.
PAGE 250
5 Database Administration Call Data Tables A SQL statement may have more than one key field, as in the following example: SELECT * from “table_name” where “FIELD1” = ‘data1’ AND “FIELD2” = ‘data2’; In this example, FIELD1 and FIELD2 are key fields. Create an index for each of these fields to enhance system performance. Unique Indexes Unique indexes on fields enforce uniqueness of the data in that field across the entire table of records.
PAGE 251
5 Database Administration Call Data Tables 4 Enter create unique index index_name on table_name (“FIELD1”); The system creates a unique index for FIELD1 in the table. Non-Unique Indexes Non-unique indexes do not prevent the same data from appearing in that field in several records in the same table.
PAGE 252
5 Database Administration Database Interface Process 5 Enter create index index_name on table_name (“FIELD2”); The system creates a non-unique index for FIELD2 in the table. Database Interface Process A voice system application accesses the database tables through a single database interface process (DIP). A DIP is a software program that connects to the database and provides the only interface between the application and the database.
PAGE 253
5 Database Administration Database Interface Process the machine not operating, the machine operating slowly, an application query of a large non-indexed table, network congestion, and so on. While the DIP is waiting for a response from the machine, the message queue of the DIP may back up. A full message queue (the current maximum is 255) may result in performance problems for the voice system. To prevent this, the DIP is equipped with a timeout mechanism.
PAGE 254
5 Database Administration Database Interface Process Database Cursors An internal data structure called a database cursor is used to monitor the point from which the DIP is reading in a specific database table. One cursor is allocated for each read of each database table by each channel running a service that requires access to that database. The cursor remains assigned to that table until the service ends on the channel for which the cursor was allocated.
PAGE 255
5 Database Administration Database Interface Process ~ read = the number of read table operations performed on different tables by applications (per channel) ~ cursor = the number of cursors involved in the read table Note: Multiple reads of the same table use only one cursor. The following are sample calculations using various configurations and numbers of read table operations.
PAGE 256
5 Database Administration Increasing Database Storage Size In this case, if all 48 channels are performing five read table operations, some database operations may fail because of the multiple read table operations on the same channels. • An application developer wants to develop an application that executes six read table operations on six different tables per channel: 500 / (6 × 1) = 83.33 Therefore, the application can run on as many as 80 channels before it encounters database access problems.
PAGE 257
5 Database Administration Increasing Database Storage Size To increase the database size: Note: It is not necessary to stop the voice system while you are resizing the database. 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter /vs/bin/util/dbfrag The system displays the number of free database blocks.
PAGE 258
5 Database Administration Increasing Database Storage Size 8 Enter connect internal 9 Enter alter tablespace system 10 Enter add datafile ‘/oracle/dbs/dbsA2.dbf’ Note: The file name dbsA2.dbf is a recommended name. If this file already exists in this directory, use dbsA3.dbf 11 Enter size number where number is the number of bytes calculated in step 6 that you want to add to the database. 12 Enter exit Note: We recommend that you use the above commands as written.
PAGE 259
5 Database Administration Decreasing the Database Storage Size Decreasing the Database Storage Size To minimize database storage and access problems, the voice system provides two ways to minimize the storage space required for call data: • Reduce the amount of call data stored. • Reduce the number of days for which data is stored. Reducing the Amount of Call Data Stored You can decrease the amount of database space needed by reducing the number of stored call data events.
PAGE 260
5 Database Administration Decreasing the Database Storage Size The following is a sample croncdh file: # Start the ORACLE DBMS VSUTIL=/vs/bin/util ORACLE_SID=A;export ORACLE_SID ORACLE_HOME=‘/usr/lbin/dbhome $ORACLE_SID‘ PATH=$PATH:$ORACLE_HOME/bin;export PATH ulimit 2113674 if /usr/lbin/orastat -s >/dev/null then : else ulimit 2113674; ior w fi # perform the cron jobs $VSUTIL/cdhsum $VSUTIL/cdhdel $VSUTIL/ccasum $VSUTIL/ccadel # cleanout the unwanted ORACLE log files $VSUTIL/logdel UCS 1000 R4.
PAGE 261
5 Database Administration Decreasing the Database Storage Size Changing the Data Storage Number of Days Currently, the only report produced for the call classification data is the Call Classification Summary report. Therefore, saving zero days worth of call classification data saves database space without affecting the reports produced by the voice system.
PAGE 262
5 Database Administration Increasing the Shared Pool Size if /usr/lbin/orastat -s >/dev/null then : else ulimit 2113674; ior w fi # perform the cron jobs $VSUTIL/cdhsum $VSUTIL/cdhdel -2 $VSUTIL/ccasum $VSUTIL/ccadel -4 # cleanout the unwanted ORACLE files $VSUTIL/logdel /vs/bin/util/dbcheck -w 15,20 Increasing the Shared Pool Size Perform this procedure to allocate additional memory resources for ORACLE.
PAGE 263
5 Database Administration Rollback Segment 1 Check the message log for ORA-04031. The text portion of this message indicates there is not enough shared memory space. 2 Access the /oracle/dbs/initA.ora file. 3 Place a pound sign (#) in front of the value shared_pool_size=3500000. 4 Remove the pound sign (#) from the front of the value shared_pool_size=6000000. 5 Save and exit the file. 6 Enter /oracle/bin/ior c to stop the database system. 7 Enter /oracle/bin/ior w to start the database system.
PAGE 264
5 Database Administration Rollback Segment This section provides information on verifying and reducing the size of this rollback segment. Verifying or Reducing the Size of the Rollback Segment Note: The procedure to reduce the size of the R1 rollback segment requires that the voice system and the database system be stopped. If possible, avoid reducing the size of the rollback segment when call traffic is heavy.
PAGE 265
5 Database Administration Rollback Segment 3 Enter /vs/bin/util/rb_init to display the current size of the rollback segment, R1. The system displays a message similar to the following: Rollback segment R1 is currently 653312 bytes in size, would you like to reduce the size of this rollback segment? (y/n) The original size of the rollback segment was set to 653312 bytes.
PAGE 266
5 Database Administration Rollback Segment 6 Enter y to shut down the voice system and continue with the procedure to reduce the size of the rollback segment. The system displays the following message if the database system is running: The database system is running. Is it OK to shutdown the database? (y/n) 7 Enter y The system stops the database system and executes the rb_init command.
PAGE 267
5 Database Administration Voice System Database Administration Voice System Database Administration To access the Database Administration window: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cvis_menu The system displays the Voice System Administration menu (Figure 106). Figure 106. Voice System Administration Menu UCS 1000 R4.
PAGE 268
5 Database Administration Voice System Database Administration 4 Select: > Configuration Management > Database Administration The system displays the Database Access ID Table window (Figure 107). Figure 107. Database Access ID Table Window UCS 1000 R4.
PAGE 269
5 Database Administration Voice System Database Administration Database Access ID Table Window The Database Access ID Table window displays currently recognized database IDs. Use the Database Access ID Table window to perform the following tasks: • Add a local or remote database access ID • Remove a local or remote database access ID Table 18 describes each field in the Database Access ID Table window. Table 18.
PAGE 270
5 Database Administration Database Access IDs Voice System Database Administration Each ID listed in the Database Access ID Table window represents an established local or remote connection to an ORACLE database. This connection is used by the voice system’s applications to access a customer’s database tables. The database ID, then, represents each local or remote database to the voice system.
PAGE 271
5 Database Administration Figure 108. Voice System Database Administration Add A Database Access ID Menu 4 Select: > Add a Local Database Access ID The system displays the Add a Local Database Access ID window (Figure 109). Figure 109. Add a Local Database Access ID Window 5 Enter the local database access ID in the Database Access ID: field, or press F2 (Choices) to select from a menu. Valid values are DB2_local, DB3_local, DB4_local, and DB5_local.
PAGE 272
5 Database Administration Voice System Database Administration 6 Press F3 (Save) to save the database access ID and exit the window. The Add a Database Access ID menu remains active, allowing you to add other database access IDs, if desired. 7 If you are finished adding database access IDs, press F6 (Cancel) twice to return to the Configuration Management menu. 8 Stop and start the voice system.
PAGE 273
5 Database Administration • Voice System Database Administration The $ORACLE_HOME/network/admin/tnsnames.ora configuration file on the UCS 1000 R4.2 has been updated to provide system information for the system. The system software automatically attempts to update the existing tnsnames.ora file (or to create a new file if none exists), but manual alterations are sometimes necessary. For assistance with this requirement, see the database administrator. See “Configuring the TNS Listener: LISTENER.
PAGE 274
5 Database Administration Voice System Database Administration 4 Select: > Add a SQL*Net V2 Remote Database Access ID The system displays the Add V2 Remote Database ID window (Figure 111). Figure 111. Add V2 Remote Database Access ID Window UCS 1000 R4.
PAGE 275
5 Database Administration Voice System Database Administration 5 Complete the fields in this window using the information in Table 19. Table 19. Field Descriptions for the Add V2 Remote Database Access ID Window Field Name Description Valid Values V2 Database Access ID: This field specifies the name by which you want to refer to this connection. — Remote DB’s Connect Descriptor: This field specifies the database instance on the remote database server to which you want to connect.
PAGE 276
5 Database Administration Table 19. Voice System Database Administration Field Descriptions for the Add V2 Remote Database Access ID Window Field Name Description Valid Values Remote Server’s Network Name: This field specifies the network name or TCP/IP address of the remote database server. If the network name is entered, it must already exist in the local /etc/hosts file. Contact the network administrator for this name or TCP/IP address.
PAGE 277
5 Database Administration Table 19. Voice System Database Administration Field Descriptions for the Add V2 Remote Database Access ID Window Field Name Description Valid Values Will this CONVERSANT be a DB server? This field indicates whether this is a database server. Yes or No Note: It is strongly recommended that the local system not be used as a database server due to performance considerations. If No, the system can only be a client to a remote database server.
PAGE 278
5 Database Administration Voice System Database Administration 8 Stop and start the voice system. See Stopping the Voice System on page 90 and Starting the Voice System on page 93 in Chapter 3, Voice System Administration , for the procedures. Completing ORACLE Environment Setup if Server is Not a UCS 1000 R4.2 If the database server is a UNIX-based system running ORACLE V7 but not a UCS 1000 R4.
PAGE 279
5 Database Administration Voice System Database Administration 2 Start the listener process. 3 Provide the server’s network name and database instance name (ORACLE_SID) to each UCS 1000 R4.2 client system. Accessing a Remote Database Using PRO*C or SQL*PLUS The following are application development issues related to accessing a remote database using PRO*C or SQL*PLUS programs.
PAGE 280
5 Database Administration Voice System Database Administration Shell Wrapper Approach Perform the following: 1 Compile the original source file that communicates with the database along with all the other source files. 2 Rename the executable file using the move command, but keep it in the same directory. 3 Using your favorite editor, edit a file with the same name as the original executable file.
PAGE 281
5 Database Administration Voice System Database Administration 7 Change the mode of shell file with the original name to rwxr_xr_x. 8 Add the original executable file name along with all the other executable files to /etc/inittab file as before using the same tools as before. The following example is used to illustrate these steps. The executable file that communicates with the database is called get_pin_uac. The name of the instance of the ORACLE database is “A”.
PAGE 282
5 Database Administration Voice System Database Administration 8 Place the /home/gar/irapi/get_pin_uac entry along with all the other executable files in the /etc/inittab file as before using the same tools as before. putenv Approach The following describes the putenv approach. The putenv function call permits the developer to directly place the ORACLE_SID and the ORACLE_HOME environmental shell variables into a Pro*C program.
PAGE 283
5 Database Administration Voice System Database Administration 4 Recompile this source code file along with all the source files that make up the custom software. The following example is used to illustrate these steps. The name of the instance of the ORACLE database is “A”. The name of the ORACLE_HOME directory is /oracle. /* start of header files */ ... #include ... /* end of header files */ ... ... main (argc,argv) int argc; char *argv[]; { /* start of local variables */ ...
PAGE 284
5 Database Administration Voice System Database Administration Removing a Database Access ID The Remove a Database Access ID window allows you to remove one or more existing database access IDs, thereby dropping the connection to the associated ORACLE database. ! CAUTION: When you remove a remote database access ID, make sure that no applications use that database access ID. If an application uses an ID that has been removed, the application fails when it tries to access data stored in that database.
PAGE 285
5 Database Administration Figure 112. SQL*PLUS Database Administration Remove a Database Access ID Window 4 Enter the access ID of the database you want to remove in the Database Access ID: field, or press F 2 (Choices) to select from a menu. 5 Press F3 (Save). The system saves the ID of the remote database connection to be deleted. 6 Stop and start the voice system.
PAGE 286
5 Database Administration Monitoring the Database ! CAUTION: Do not alter any data, schema, logins, or passwords using SQL*PLUS. Doing so may corrupt the voice system and result in the need for maintenance. The ORACLE right-to-use license is restricted solely to UCS 1000 R4.2 applications, that is, not covered under the warranty. If you use SQL*PLUS to drop a table or change a table schema, you must reverify and reinstall the application that refers to the table.
PAGE 287
5 Database Administration The dbcheck Command Monitoring the Database The dbcheck command checks space usage and rollback segment growth. dbcheck Command Options The dbcheck command has three different options: • -i installs cron entries and error messages. The cron job can be placed in either the root cron file or added to the end of /vs/bin/util/croncdh job that runs once a day.
PAGE 288
5 Database Administration Monitoring the Database The command, by default, sends warning messages to the error log indicating a threshold was exceeded (the -i option must be run first). The e option disables entries from going into the log file. The -s option prints the warning messages to standard output. The -m user option allows for the messages to be mailed to user. Multiple users can be sent the mail by separating the user names with a tilde (~).
PAGE 289
5 Database Administration Monitoring the Database dbfree Command Options The -h option removes the column headers. The dbfree Command Output The dbfree program returns the following values: The dbfrag Command • 0 — Success • 1 — Processing error The dbfrag command is a shell script that reports on database allocation, usage, and fragmentation. The block size reported is in ORACLE blocks (2048 bytes).
PAGE 290
5 Database Administration Monitoring the Database The dbfrag Command Output The dbfrag program returns the following values: The dbused Command • 0 - Success • 1 - Processing error The dbused command is a shell script that displays the amount of space used by each object for a given user. Objects are tables, indexes, clusters, rollback, and cache. The default user is sti/sti. dbused Command Options The dbused command has three options: • -h prints the listing without a header.
PAGE 291
5 Database Administration Monitoring the Database Database Trace Files ORACLE creates a trace file in the /oracle/rdbms/log directory each time the system is rebooted. These trace files are not automatically removed by ORACLE and must be removed by the user or administrator if the files are no longer wanted. In addition, ORACLE creates a log file /oracle/tcp/log/orasrv.log that contains all of the remote login information that is automatically created and appended by ORACLE.
PAGE 292
6 Peripheral Administration Overview This chapter provides the information and procedures needed to configure and administer the peripheral equipment connected to your voice system, namely modems, printers, and remote terminals. Accessing the Unix Management Menu To access the Unix Management menu: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. UCS 1000 R4.
PAGE 293
6 Peripheral Administration Accessing the Unix Management Menu 3 Enter cvis_menu The system displays the Voice System Administration menu (Figure 113). Figure 113. Voice System Administration Menu 4 Select: > Unix Management UCS 1000 R4.
PAGE 294
6 Peripheral Administration Modem Administration The system displays the Unix Management menu (Figure 114). Figure 114. Unix Management Menu The procedures in this chapter detail administration for modems, terminals, and printers. The other menu options in the UNIX Management menu are discussed in Chapter 7, Common Administration . Modem Administration This section describes the procedures to configure and administer a 3820 or 3920 Plus modem for use with your voice system. UCS 1000 R4.
PAGE 295
6 Peripheral Administration Modem Administration Installing the Modem To install the modem: 1 Physically connect the modem to the system. See “Connecting the 3820 Modem to the Platform,” in Chapter 4, “Completing System Installation," in UCS 1000 R4.2 New System Installation, 585-313-127, for the procedure to physically connect the modem.
PAGE 296
6 Peripheral Administration Configuring the Modem Using the Modem Control Panel Modem Administration The 3820 and 3920 Plus modems have a Diagnostic Control Panel (DCP) that is the user interface to the modem. Use the procedures below to configure the 3820 modem via its control panel: Activate the Unix Dial Default Factory Configuration To activate the UNIX Dial default factory setting: 1 Turn the modem off and then back on. 2 Press or on the modem to display Configure.
PAGE 297
6 Peripheral Administration Modem Administration 7 Press F2 (Select). Modem response: Choose Function Edit and Save. 8 Press F3 (Save). Modem response: Sav EditArea to Active. 9 Press F1 (Save). ~ 3820 modem response: Command Complete ~ 3920 Plus modem response after a power reset. Idle: 288 10 Press to return to the top-level menu. UCS 1000 R4.
PAGE 298
6 Peripheral Administration Modem Administration Setting the Async DTE Rate To set the Async DTE rate to the required speed: 1 Press or on the modem to display Configure. 2 Press the function key under Configure (F1 or F2 ). Modem response: Ld EditArea frm. 3 Press or to display Active. 4 Press F1 (Save). Modem response: Choose Function Edit and Save 5 Press F1 (Edit). Modem response: Edit StrapGroup DTE Interface 6 Press F1 (Edit). Modem response: Async/Sync Mode UCS 1000 R4.
PAGE 299
6 Peripheral Administration Modem Administration 7 Press F1 (Next) to display Async DTE Rate. 8 Press or to display the baud. 9 Press F2 (Select). The LCD displays the baud. 10 Continue with the next procedure, Setting the DTR Action and DSR Control to Standard RS-232 on the Modem on page 260. Do not return to the top-level menu.
PAGE 300
6 Peripheral Administration Modem Administration 7 Press the single . Modem response: Edit StrapGroup 8 Press or to display DTE Dialer. 9 Press F1 (Edit). Modem response: DTE Dialer Type 10 Press F1 (Next) to display AT Escape Char. 11 Use 12 Press or and F 2 (Select) to adjust the number to 128 ASCII. . Modem response: Edit StrapGroup 13 Press or to display Dial Line. 14 Press F1 (Edit). Modem response: Dial Line Rate 15 Press or UCS 1000 R4.2 Administration 585-313-507 to display baud.
PAGE 301
6 Peripheral Administration Modem Administration 16 Press F2 (Select). The LCD displays the baud. 17 Press the single . Modem response: Edit StrapGroup 18 Continue with the next procedure, Setting the Error Control Mode to Buffer Mode on the 3820 Modem on page 262. Do not return to the top-level menu. Setting the Error Control Mode to Buffer Mode on the 3820 Modem To set the error control mode to buffer mode: 1 Press or to display V42/MNP/Buffer. 2 Press F1 (Edit).
PAGE 302
6 Peripheral Administration Modem Administration 6 Press or to display CTS_to_DTE. 7 Press F2 (Select). 8 Press . Modem response: Edit StrapGroup 9 Press . Modem response: Choose Function Edit and Save 10 Press F3 (Save). Modem response: Sav EditArea to Active 11 Press F1 . Modem response: Command Complete 12 Press to return to the top-level menu. UCS 1000 R4.
PAGE 303
6 Peripheral Administration Configuring the Modem Using a Terminal Modem Administration To configure the modem terminal: 1 Connect a terminal to the 3820 modem. Note: See the documentation provided with the terminal for connection instructions. 2 Verify that the terminal is acting as a DTE. 3 Set the terminal line to 8 bits, no parity, and 1 stop bit. 4 Set the baud of the terminal line to the required modem speed. 5 Enter AT from the terminal.
PAGE 304
6 Peripheral Administration Modem Administration ~ 6 = 2400 ~ 7 = 200, V.22 ~ 8 =1200, 212A ~ 20 = 19200 For example, to set the 3820 modem to use COM1, where the baud is 19200, enter 20 as the dial line rate as shown below: AT&TF3L0&D2&S1\N0\Q3S41=20S2=128&W0 Modem response: OK 7 Disconnect the terminal. 8 Connect the modem to COM port 1. Note: COM port 2 (COM2) is reserved for the TAM. The system activates the RTS, CTS, and LSD indicators. UCS 1000 R4.
PAGE 305
6 Peripheral Administration Modem Administration Administering the Modem For the 3820 or 3920 plus modem to work properly with the voice system, you must administer the voice system to recognize the modem port. To administer the voice system to recognize the modem: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #.
PAGE 306
6 Peripheral Administration Modem Administration The system displays the Install Modem/Terminal window (Figure 115). Figure 115. Install Modem/Terminal Window 5 Enter modem in the Device: field. 6 Press F2 (Choices) to display a list of valid port numbers for the Serial Port Number: field. a Select COM port 1, /dev/tty00 Note: COM port 2 (COM2) is reserved for the TAM. 7 Enter 19200 in the Speed: field. 8 Press F3 (Save). The system displays a confirmation window.
PAGE 307
6 Peripheral Administration Setting Up UnixWare to Use a Modem for Outgoing Calls Modem Administration To configure UnixWare for a modem: 1 Start at the UNIX System V Administration menu (Figure 17 on page 24) and select: > network services > basic networking > devices > add The system displays the Adds a Device for Use by Basic Networking window (Figure 116). Figure 116.
PAGE 308
6 Peripheral Administration Modem Administration 3 Press F3 (Save). The system displays the Add a Modem Device for use by Basic Networking (1) window (Figure 117). Figure 117. Add a Modem Device for use by Basic Networking (1) Window 4 Enter ACU in the Device Type: field. 5 Enter the appropriate modem in the Modem Type: field, or press F2 (Choices) to select from a menu. If your modem uses the “atdt” command set, select one of the Hayes modems. 6 Press F3 (Save). UCS 1000 R4.
PAGE 309
6 Peripheral Administration Modem Administration The system displays the Add a Modem Device for use by Basic Networking (2) window (Figure 118) with several of the fields already filled in. Figure 118. Add a Modem Device for use by Basic Networking (2) Window 7 Enter /dev/tty00 for COM port 1. Note: COM port 2 (COM2) is reserved for the TAM. 8 Enter 19200 in the Speed: field, or accept the default. 9 Press F3 (Save). The system displays the following message: Entry was added to the system.
PAGE 310
6 Peripheral Administration Setting Up UnixWare to Use a Modem for Incoming Calls Modem Administration To configure UnixWare for a modem that can process incoming calls: 1 Start at the UNIX System V Administration menu (Figure 17 on page 24) and select: > ports > port_monitors > add UCS 1000 R4.
PAGE 311
6 Peripheral Administration Modem Administration The system displays the Add A Port Monitor window (Figure 119). Figure 119. Add A Port Monitor Window 2 Enter ModemMon in the Port monitor tag: field. 3 Enter ttymon in the Port monitor type: field. 4 Enter /usr/lib/saf/ttymon in the Command to start the port monitor: field. 5 Enter 2 in the Version number: field. UCS 1000 R4.
PAGE 312
6 Peripheral Administration Modem Administration 6 Enter Yes in the Start port monitor immediately: field. 7 Enter Enabled in the Start state: field. 8 Enter 0 in the Restart count: field. 9 Press F3 (Save). The system displays the Service Access Management menu (Figure 120). Figure 120. Service Access Management Menu UCS 1000 R4.
PAGE 313
6 Peripheral Administration Modem Administration 10 Select: > port services > add > add to one > ModemMon UCS 1000 R4.
PAGE 314
6 Peripheral Administration Modem Administration The system displays the Add Port Services to Port Monitor window (Figure 121). Figure 121. Add Port Services to Port Monitor Window 11 Enter Modem in the Service Tag: field. 12 Enter login in the Identification & Authentication Scheme: field. 13 Leave the Service invocation identity: field blank. 14 Enter ENABLED in the Port/service State: field. UCS 1000 R4.
PAGE 315
6 Peripheral Administration Modem Administration 15 Enter YES in the utmp entry to be created for this service: field. 16 Enter 2 in the Version number: field. Leave the remaining fields blank. 17 Press F3 (Save). The system displays the Add Port Services for ttymon window (Figure 122). Figure 122. Add Port Services for ttymon Window UCS 1000 R4.
PAGE 316
6 Peripheral Administration Modem Administration 18 Enter /dev/tty00 in the Name of TTY device: field. 19 Enter 19200 in the ttylabel: field. 20 Enter /usr/bin/shserv in the Service command: field. 21 Enter No in the Hangup: field. 22 Enter No in the Connect-in-Carrier: field. 23 Enter Yes in the Bidirectional: field. 24 Enter No in the Wait-read Count: field. 25 Enter 0 in the Timeout: field. 26 Enter login: in the Prompt Message: field. 27 Enter ldterm in the Modules to be Pushed: field.
PAGE 317
6 Peripheral Administration Printer Administration The system returns to the Port Service Management menu (Figure 123). Figure 123. Port Service Management Menu 31 Press F6 (Cancel) repeatedly to return to the UNIX System V Administration menu. Printer Administration This section describes how to configure and administer the printer for use with the voice system. Installing the Printer See “Connecting the Printer,” in Chapter 4, “Connecting Peripherals and Powering Up," in UCS 1000 R4.
PAGE 318
6 Peripheral Administration Printer Administration Configuring the Printer on the Voice System Lucent Technologies supports the standard parallel printers that have the UnixWare 2.1.7 driver. Contact your field support personnel if you want to connect a serial printer to the system. To configure a local parallel printer: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #.
PAGE 319
6 Peripheral Administration Printer Administration 4 Select: > UNIX System Administration > printers > printers > add The system displays the Add a New Printer window (Figure 125). Figure 125. Add a New Printer Window UCS 1000 R4.
PAGE 320
6 Peripheral Administration Printer Administration 5 Enter the name of the new printer in the Printer Name: field. 6 Enter the local system name in the System Name: field. 7 Enter oki-320 in the Printer Type: field. 8 Enter none in the Similar printer to use for defaults: field. 9 Enter no in the Do you want to use standard configurations? (eg alerts, banners): field. 10 Enter yes in the Do you want to use standard port settings? (eg baud rate, parity): field.
PAGE 321
6 Peripheral Administration Printer Administration The system displays the Configure New Printer window (Figure 126). Figure 126. Configure New Printer Window 14 Enter none in the Class: field. 15 Enter printer one in the Description of the printer: field. 16 Enter simple in the File types printable without filtering: field. 17 Enter yes in the Can a user skip the banner page? field. UCS 1000 R4.
PAGE 322
6 Peripheral Administration Printer Administration 18 Enter Use printer defaults in the following fields: ~ ~ ~ ~ Default Default Default Default char. pitch: line pitch: page width: page length: 19 Enter mail lp in the Command to run for alerts: field. 20 Enter once in the Frequency of alert (in minutes): field. 21 Enter beginning in the Printer recovery method: field. 22 Enter no in the Is Printer also a login terminal: field. 23 Press F3 (Save). UCS 1000 R4.
PAGE 323
6 Peripheral Administration Printer Administration The system displays the Printer: Successfully Added window (Figure 127). Figure 127. Printer: Successfully Added Window 24 Press F8 (Cont). The system displays the Setup Printer Access window (Figure 128). Figure 128. Setup Printer Access Window UCS 1000 R4.
PAGE 324
6 Peripheral Administration Printer Administration 25 Enter all in the Users who are allowed access to this printer: field. Note: Do not press EN TE R until all of the fields are complete. 26 Enter none in the Users who are denied access to this printer: field. 27 Enter all in the Forms allowed on this printer: field. 28 Enter none in the Forms denied on this printer: field. 29 Press F3 (Save). The system displays the Configure Printers for the Printer Service window (Figure 129). Figure 129.
PAGE 325
6 Peripheral Administration Printer Administration 30 Press F6 (Cancel). The system displays the Line Printer Services Configuration and Operations window (Figure 130). Figure 130. Note: Line Printer Services Configuration and Operations Window Wait at least 10 minutes before continuing with step 31. 31 Select: > operation > accept UCS 1000 R4.
PAGE 326
6 Peripheral Administration Printer Administration The system displays the Allow Classes/Printers to Accept Requests window (Figure 131). Figure 131. Allow Classes/Printers to Accept Requests Window 32 Enter the name of the printer in the Printer(s) and/or Class(es): field, or press F2 (Choices) to select from a menu. If you select from the Choices menu, you must press F 2 (Mark) to mark each class or printer you want to accept print requests, then press F 3 (Enter). 33 Press F3 (Save).
PAGE 327
6 Peripheral Administration Printer Administration The system displays the Enable Printer(s) for Printing window (Figure 132). Figure 132. Enable Printer for Printing Window 36 Enter the name of the printer in the Printer(s): field, or press F2 (Choices) to select from a menu. If you select from the Choices menu, you must press F2 (Mark) to mark each printer you want to enable, and then press F3 (Enter). 37 Press F3 (Save). 38 Press F6 (Cancel).
PAGE 328
6 Peripheral Administration Printer Administration The system displays the Set Default Print Destination window (Figure 133). Figure 133. Set Default Print Destination Window 40 Enter the name of the printer in the Default Printer or Printer Class: field, or press F2 (Choices) to select from a menu. 41 Press F3 (Save). The system saves the printer configuration information.
PAGE 329
6 Peripheral Administration Printer Administration > UNIX Management > Printer Administration > Install Okidata 320 Printer Software OR > UNIX Management > Printer Administration > Install Okidata Laser Printer Software The system installs the printer software. 5 Press F6 (Cancel) to finish and return to the Printer Administration menu. UCS 1000 R4.
PAGE 330
6 Peripheral Administration Printer Administration Setting Up the Printer To set up a parallel printer for use with the system: 1 Log on to the system as root. 2 Enter cd /etc/uucp 3 Edit the Systems file to add an entry for the printer. This entry must include the hex representation for the printer IP address and port.
PAGE 331
6 Peripheral Administration Remote Terminal Administration 8 Do one of the following: ~ If you want a banner page to print, skip the following steps a through c and continue with step 9. ~ If you do not want a banner page to print, complete the following steps a through c. a Enter /usr/lib/lp/model b Enter cp standard LANHP c Edit the LANHP file and change nobanner=”no” to nobanner=”yes”.
PAGE 332
6 Peripheral Administration Remote Terminal Administration Configuring the Remote Terminal Use the following procedure to configure a terminal (monitor): 1 Start at the UNIX System V Administration menu (Figure 17 on page 24) and select: > ports > quick_terminal > add UCS 1000 R4.
PAGE 333
6 Peripheral Administration Remote Terminal Administration The system displays the Quick Terminal Setup window (Figure 134). Figure 134. Quick Terminal Setup Window 2 If you know the name of the port monitor, enter the name in the Port Number(s): field, or press F 2 (Choices) to select from a menu. 3 Enter the speed in the Speed: field, or press F2 (Choices) to select from a menu. The default is 19200. 4 Press F3 (Save).
PAGE 334
6 Peripheral Administration Remote Terminal Administration Administering the Remote Terminal To administer the voice system to recognize the modem: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cvis_menu 4 Select: > UNIX Management > Modem/Terminal Administration > Install Modem/Terminal Software UCS 1000 R4.
PAGE 335
6 Peripheral Administration Remote Terminal Administration The system displays the Install Modem/Terminal window (Figure 135). Figure 135. Install Modem/Terminal Window 5 Enter terminal in the Device: field. 6 Enter a serial port number or press F2 (Choices) to display a list of valid port numbers for the Serial Port Number: field. 7 Enter 19200 in the Speed: field. 8 Press F3 (Save). The system displays a confirmation window.
PAGE 336
7 Common Administration Overview The procedures in this chapter are organized together to facilitate quick reference for some of the more common, or daily, administrative tasks. Common administration includes running system reports, and performing procedures such as system monitoring, media formatting, backups, and administering the date and time. Command Menu The Command Menu enables you to quickly access the System Monitor and Trace services, and exit the voice system.
PAGE 337
7 Common Administration Command Menu Accessing the Command Menu To access the Command Menu: 1 Once you have accessed the Voice System Administration menus (as described in Chapter 3, Voice System Administration , from almost any menu or window, press F7 (Cmd-Menu). The system displays the Command Menu (Figure 136). Figure 136.
PAGE 338
7 Common Administration Accessing the System Monitor Command Menu To access the System Monitor window from the Command Menu: 1 Start at the Command Menu (Figure 136 on page 298) and select: > System Monitor The system displays System Monitor-Voice Channels window (Figure 137). Figure 137. System Monitor-Voice Channels Window UCS 1000 R4.
PAGE 339
7 Common Administration Command Menu Table 20 describes the columns in the System Monitor-Voice Channels window. Table 20. Columns in the System Monitor Window Column Description Channel Lists the existing channels on the voice system. Virtual channels have the letter v appended to the channel number. These channels are not voice channels but are instead used for “data-only” applications. The number of virtual channels in the system depends on the software applications installed.
PAGE 340
7 Common Administration Command Menu Table 20. Columns in the System Monitor Window Column Description Service Status Indicates the state of each channel in the voice system. All hardware states (for example, On Hook, Foos, Manoos, Broken) are marked with an asterisk (*). This field is blank for virtual channels except when a transaction with a DIP is running. See Table 21 for a description of the status entries. Caller Input Indicates the last set of digits entered by the caller.
PAGE 341
7 Common Administration Service Status Column Command Menu Table 21 describes the possible entries in the Service Status column and their meanings. Note: All hardware states are marked with an asterisk (*). Table 21. Entries for the Service Status Column Service Status Entry Description *BROKEN The channel is broken. CCA The channel is in process of call classification. Coding The channel is performing voice coding. Collect The channel is waiting for caller input.
PAGE 342
7 Common Administration Table 21. Command Menu Entries for the Service Status Column Service Status Entry Description *D-MANOOS (PRI feature only) The D-channel is manually out-of-service. D-NETOOS (PRI feature only) The D-channel network is out-of-service. D-NONEX (PRI feature only) The D-channel is nonexistent. DIP <0 34> The channel is processing a request from a data interface process. *FOOS The channel is facility out of service. Host The channel is currently accessing a host.
PAGE 343
7 Common Administration Table 21. Command Menu Entries for the Service Status Column Service Status Entry Description *NETOOS (PRI feature only) The channel is in a network that is out of service. Offhook The channel is in service and has answered a call. *ON HOOK The channel is in service and is waiting for a call. Pending The channel is going into or leaving an operational state. Talking The channel is playing speech.
PAGE 344
7 Common Administration Changing the System Monitor Refresh Rate Command Menu By default, the system updates the voice channel status every 5 seconds. To change the refresh rate to a specified amount of time: 1 Start at the System Monitor-Voice Channels window (Figure 137 on page 299) and press F 8 (Chg-Keys). The system displays the alternate set of function keys. 2 Press F1 (Chg-Rate). The system displays the Change Refresh Rate window (Figure 138). Figure 138.
PAGE 345
7 Common Administration Command Menu Printing the System To print a System Monitor-Voice Channel report: Monitor-Voice 1 Start at the System Monitor-Voice Channels window (Figure 137 on page Channel Report 299) and press F 8 (Chg-Keys). The system displays the alternate set of function keys. 2 Press F6 (Print). The system prints the System Monitor-Voice Channel Report. Trace Service A trace is a record of the events that occur on a voice channel, the voice system, or a host system.
PAGE 346
7 Common Administration Command Menu The system displays the Trace Service window (Figure 139). Figure 139. Trace Service Window 2 Enter a single channel or session number, or all in the Channel or Session: field. 3 Press F3 (Save). The system displays the Trace Output window (Figure 140). Figure 140. Trace Output Window UCS 1000 R4.
PAGE 347
7 Common Administration Reports Administration 4 Select one of the following options while in the Trace Output window: ~ Press F1 (Pause) to stop the information from scrolling. ~ Press F2 (Prev Page) and F3 (Next Page) to move around within the display. ~ Press F1 (Resume) to continue scrolling through the trace output. ~ Press DE LE TE to stop the trace. ~ Press F2 (Print) from the Trace Service window to print the last 250 lines of output.
PAGE 348
7 Common Administration Reports Administration Accessing the Reports Administration Menu To access the Reports Administration menu: 1 At the Console Login: prompt, enter root The system prompts you for a password. 2 Enter your root password. The system displays the system prompt #. 3 Enter cvis_menu The system displays the Voice System Administration menu (Figure 42 on page 59). 4 Select: > Reports UCS 1000 R4.
PAGE 349
7 Common Administration Reports Administration The system displays the Reports menu (Figure 141). Figure 141. Reports Menu Use the procedures in this section to access and run the various reports in this menu.
PAGE 350
7 Common Administration Reports Administration ~ Rang with no answer ~ Experienced network problems • Displaying the Call Classification Report Summary statistics To display the Call Classification Report: 1 Start at the Reports menu (Figure 141 on page 310) and select: > Call Classification Report The system displays the Call Classification Report window (Figure 142). Figure 142. Call Classification Report Window UCS 1000 R4.
PAGE 351
7 Common Administration Reports Administration Table 22 defines the columns in this window. Table 22. Column Description for the Call Classification Report Column Name Description Dialed Number Specifies the telephone number from the transfer attempt. Telephone numbers have a 16-digit maximum, however only 12 digits are displayed in the report. Longer numbers are truncated and displayed with an asterisk (*). Total Specifies the total transfer attempts to connect to the Dialed Number.
PAGE 352
7 Common Administration Table 22. Reports Administration Column Description for the Call Classification Report Column Name Description Busy Specifies the number of transfer attempts that were busy. This number corresponds to call dispositions equal to B. Ring Specifies the number of transfer attempts that rang with no answer. This number corresponds to call dispositions equal to N. Other Specifies the number of times the network is busy and cannot complete a call (fast busy).
PAGE 353
7 Common Administration Reports Administration The system displays the Actions Menu (Figure 143). Figure 143. Actions Menu 2 Select: > Modify The system displays the Modify Call Classification Report window (Figure 144). Figure 144. Modify Call Classification Report Window UCS 1000 R4.
PAGE 354
7 Common Administration Reports Administration 3 Enter the beginning and ending dates for the report in the Start Date: and End Date: fields using the format of mm/dd/yyyy for month, day, and year to limit the report to a certain date range. If you do not specify the year, the report uses the current year. A start date of 04/01/2000 and an end date of 04/30/2000 means that the voice system displays call classification information on calls made in the month of April 2000.
PAGE 355
7 Common Administration Printing the Call Classification Report Reports Administration The print option provides a complete printout of the Call Classification report. Note: You cannot print this report if a printer is not configured for use with the voice system. See Printer Administration on page 278 in Chapter 6, Peripheral Administration , for more information about printer administration.
PAGE 356
7 Common Administration Updating the Call Classification Report Reports Administration Use the Update function to redisplay the report. The report reflects the values last saved to the voice system. To update the Call Classification Report: 1 Start at the Call Classification Report window (Figure 142 on page 311) and press F8 (Actions). The system displays the Actions Menu (Figure 143 on page 314). 2 Select: > Update The system updates the report and displays the values last saved.
PAGE 357
7 Common Administration Displaying the Call Data Detail Report Reports Administration To display the Call Data Detail Report: 1 Start at the Reports menu (Figure 141 on page 310) and select: > Call Data Detail Report The system displays the Call Data Detail Report window (Figure 145). Figure 145. Call Data Detail Report Window UCS 1000 R4.
PAGE 358
7 Common Administration Reports Administration Table 23 defines the columns on this window. If multiple applications are invoked during a call, the report displays a line of summary data for the call, followed by a line of data for each application in the call. Table 23. Column Description for the Call Data Detail Report Column Name Description Record Specifies the database record number of each call made to the voice system. Channel Specifies the channel on which the call was made.
PAGE 359
7 Common Administration Modifying the Call Data Detail Report Reports Administration You can tailor the Call Data Detail Report to limit the display by changing one or more of the following parameters: • Number of most recent call records you want to include • Date of the data to include in the report • Service associated with the call data To modify the Call Data Detail Report: 1 Start at the Call Data Detail Report window (Figure 145 on page 318) and press F8 (Actions).
PAGE 360
7 Common Administration Reports Administration The system displays the Modify Call Data Detail Report window (Figure 146). Figure 146. Modify Call Data Detail Window 3 Enter a number, range of numbers, or all in the Number of Call Records: field to specify the number of most recent records to include in the report. The default is all. 4 Enter the date to which you want to limit the report information, or all, in the Date: field. Use the format of mm/dd/yyyy for month, day, and year.
PAGE 361
7 Common Administration Reports Administration For example, if the system contains 10 records for yesterday and 10 records for today and you enter 6 in the Number of Call Records: field and enter yesterday’s date in the Date: field, the Call Data Detail Report displays no records. This is because the last six records were created for the current day, not for yesterday’s date.
PAGE 362
7 Common Administration Reports Administration The system displays the Actions Menu (Figure 150 on page 337). 9 (Optional) Select: > Update The system redisplays the Call Data Detail Report window with the new parameters. Printing the Call Data Detail Report The print option provides a complete printout of the Call Data Detail report. Note: You cannot print this report if a printer is not configured for use with the voice system.
PAGE 363
7 Common Administration Reports Administration 2 Select: > Print The system prints the Call Data Detail Report using the last set of options that was saved to the voice system. Updating the Call Data Detail Report Use the Update function to redisplay the report. The report reflects the values that were last saved to the voice system. See Modifying the Call Data Detail Report on page 320 for how to modify this output.
PAGE 364
7 Common Administration Reports Administration Call Data Summary Report The Call Data Summary Report provides an hourly summary of the calls made to the voice system. This report is similar to the Call Data Detail Report, except that the Call Data Summary Report shows the calls on an hourly basis by service. The system maintains approximately 7 days worth of data. Note: Displaying the Call Data Summary Report Call data summary information is prepared at midnight for the entire day.
PAGE 365
7 Common Administration Reports Administration The system displays the Call Data Summary Report window (Figure 147). Figure 147. Call Data Summary Report Window UCS 1000 R4.
PAGE 366
7 Common Administration Reports Administration Table 24 describes the columns on this window. Table 24. Column Description for the Call Data Summary Report Column Name Description Period Time, in hourly increments, when calls were made to the voice system. Service Script associated with a group of calls made during the specified time. Average Hold Time Average duration of a call for the specified time in minutes and seconds. Calls Total number of calls for the specified time.
PAGE 367
7 Common Administration Table 24. Reports Administration Column Description for the Call Data Summary Report Column Name Description Comment Event No Identifying number for each call data message. Appears only when the Include Call Data Fields?: field is set to Yes. See Modifying the Call Data Summary Report.
PAGE 368
7 Common Administration Reports Administration The system displays the Actions Menu (Figure 143 on page 314). 2 Select: > Modify The system displays the Options for Call Data Summary Report window (Figure 148). Figure 148. Options for Call Data Summary Report Window 3 Enter the day of the week, Monday through Sunday, for which you want to obtain report information in the Day: field, or press F2 (Choices) to select from a menu.
PAGE 369
7 Common Administration Reports Administration If you enter a range between 9 and 16, the system displays call data for calls made between 9 a.m. and 5 p.m. The default is all, meaning that the system displays call data for the entire 24 hour period for the day. Note: Hourly Call Data Summary Reports are not processed until midnight of each day. If you make a request for information on Tuesday, the information will not be displayed until the following day, Wednesday.
PAGE 370
7 Common Administration Reports Administration > Update The system redisplays the Call Data Summary Report window with the new parameters. Printing the Call Data Summary Report The print option provides a complete printout of the Call Data Summary report. Note: You cannot print this report if a printer is not configured for use with the voice system. See Printer Administration on page 278 in Chapter 6, Peripheral Administration , for more information about printer administration.
PAGE 371
7 Common Administration Reports Administration 2 Select: > Print The system prints the Call Data Summary Report using the last set of options saved to the voice system. Updating the Call Data Summary Report Use the Update function to redisplay the report. The report reflects the values last saved to the voice system. See on page 327 for how to modify this report. To update the Call Data Summary Report: 1 Start at the Call Data Summary Report window (Figure 145 on page 318) and press F8 (Actions).
PAGE 372
7 Common Administration Reports Administration Message Log Report The Message Log Report allows you to access voice system error messages including the: Displaying the Message Log Report • Priority level of the error • Date and time the error occurred • Source of the message • Type of circuit card associated with the message, as well as the circuit card number and channel number • Descriptive text To display the Message Log Report: 1 Start at the Reports menu (Figure 141 on page 310) and sele
PAGE 373
7 Common Administration Reports Administration The system displays the Message Log Report window (Figure 149). Figure 149. Message Log Report Window Use F2 (Prev Page) and F3 (Next Page) to scroll through the report. UCS 1000 R4.
PAGE 374
7 Common Administration Reports Administration Table 25 defines the information in the Message Log Report. Table 25. Entry Description for the Message Log Report Entry Description Pr Priority classification of error messages. The priority is identified by one of the following codes: ~ *C (critical) — the problem is interrupting service and immediate action is needed. ~ ** (major) — a potentially serious problem exists that should be fixed soon.
PAGE 375
7 Common Administration Reports Administration Table 25. Entry Description for the Message Log Report Entry Description Source Originating software process; messages are divided into subgroups according to the software process that outputs the messages. The following is a sample of possible sources: • The call data handler (CDH) process accumulates generic call statistics and application messages. • The data interface process (DIP). • The maintenance (MTC) process runs temporary diagnostics.
PAGE 376
7 Common Administration Explaining a Message in the Message Log Report Reports Administration The Explain option on the Actions Menu allows you to display more information about a specific message. To get additional information about a particular message in the Message Log Report window: 1 Start at the Message Log Report window (Figure 149 on page 334) and press F8 (Actions). The system displays the Actions Menu (Figure 150). Figure 150. Message Log Report Actions Menu UCS 1000 R4.
PAGE 377
7 Common Administration Reports Administration 2 Press F3 (Explain). The system displays the Explain Message ID window (Figure 151). Figure 151. Explain Message ID Window 3 Enter the ID of the message for which you want more information in the Message ID: field. 4 Press F3 (Save). The system displays additional information about the specified message.
PAGE 378
7 Common Administration Reports Administration • Message ID • Number of most recent messages to be displayed By default, the Message Log Report is configured to display every message. To limit what is displayed in the Message Log Report window: 1 Start at the Message Log Report window (Figure 149 on page 334) and press F8 (Actions). The system displays the Actions Menu (Figure 150 on page 337). 2 Select: > Modify UCS 1000 R4.
PAGE 379
7 Common Administration Reports Administration The system displays the Modify Message Log Report window (Figure 152). Figure 152. Modify Message Log Report Window 3 Enter *C (critical), ** (major), * (minor), alarms, all, or events in the Priority: field to limit the type of messages you want to see based on priority, or press F2 (Choices) to select from a menu. The default is all.
PAGE 380
7 Common Administration Reports Administration 5 Enter a single circuit card number or multiple circuit card numbers separated by commas in the Card: field to limit the display to specific circuit cards. There is no default value and the Choices menu is not available. If you specify all in the Card: field, the display is limited to messages about voice system circuit cards only.
PAGE 381
7 Common Administration Reports Administration 8 Enter the ID of the messages to be displayed in the Message ID: field. Enter a single ID, multiple IDs separated by commas (for example, TSM001,TWIP003), or all. 9 Enter a single number from 1 to 999, or all in the Number of Messages to be Displayed: field to specify the number of most recent messages to be displayed. If you enter all, the report displays all messages maintained by the log.
PAGE 382
7 Common Administration Reports Administration The system updates the report and displays the values last saved. Printing the Message Log Report The print option provides a complete printout of the Message Log Report. Note: You cannot print this report if a printer is not configured for use with the voice system. See Printer Administration on page 278 in Chapter 6, Peripheral Administration , for more information about printer administration.
PAGE 383
7 Common Administration Reports Administration To update the Message Log Report: 1 Start at the Message Log Report window (Figure 149 on page 334) and press F8 (Actions). The system displays the Actions Menu (Figure 150 on page 337). 2 Select: > Update The system updates the report and displays the values last saved.
PAGE 384
7 Common Administration Commands and Activities Included in the Report Content of the Administrative Commands Log Report The following administrative commands and activities are monitored for inclusion in this report: • Digital switch interface changes • Voice equipment commands: spfunc, t1prot, eqprot, hconfig • System control commands: start_vs, stop_vs, disable, autoreboot, delete, remove, restore, hdelete, trace, erase, diagnose, vs_enable • Talkfile (speech files) commands: add phrase, copy
PAGE 385
7 Common Administration Reports Administration > Message Log Report The system displays the Message Log Report window (Figure 149 on page 334). 2 Press F8 (Actions). The system displays the Actions Menu (Figure 150 on page 337). 3 Select: > Modify UCS 1000 R4.
PAGE 386
7 Common Administration Reports Administration The system displays the Modify Message Log Report window (Figure 153). Figure 153. Modify Message Log Report Window 4 Enter admin in the Priority: field. 5 Enter a software process source in the Source: field, or enter all to include all software process sources. 6 Leave the Card: field blank. 7 Enter the start time for the message search in the Start Time: field, that is, enter the time of the first entry to be displayed.
PAGE 387
7 Common Administration Reports Administration Use the format of MM/DD HH:MM for month, day, hour, and minute. If the Start Time: field is left blank, the beginning of the administrative command log is used. 8 Enter the stop time for the message search in the Stop Time: field, that is, the time of the last message to be displayed. Use the format of MM/DD HH:MM for month, day, hour, and minute. If the Stop Time: field is left blank, the end of the administrative command log is used.
PAGE 388
7 Common Administration Reports Administration 11 Press F3 (Save). The system displays the Message Log Report window, now with the Administrative Commands Log Report data (Figure 154). Figure 154. Administrative Commands Log Report Window (Displayed under the Message Log Report Window) Use F2 (Prev Page) and F3 (Next Page) to scroll through the report. The list below describes the entries in the Administrative Commands Log window: UCS 1000 R4.
PAGE 389
7 Common Administration Reports Administration ~ Time — Date and time when the command or activity was executed ~ Source — Name of the originating software process that executed the command or activity ~ Login ID — Login ID that executed the command or activity (if applicable).
PAGE 390
7 Common Administration Reports Administration Chapter 6, Peripheral Administration , for more information about printer administration. To print the Administrative Commands Log Report: 1 Start at the Administrative Commands Log Report window (Figure 154 on page 349) displayed under the Message Log Report window and press F8 (Actions). The system displays the Actions Menu (Figure 150 on page 337).
PAGE 391
7 Common Administration Reports Administration 1 Start at the Administrative Commands Log Report window (Figure 154 on page 349) displayed under the Message Log Report window and press F8 (Actions). The system displays the Actions Menu (Figure 150 on page 337). 2 Select: > Update The system updates the report and displays the values last saved.
PAGE 392
7 Common Administration Displaying the Traffic Report Reports Administration To display the Traffic Report: 1 Start at the Reports menu (Figure 141 on page 310) and select: > Traffic Report The system displays the Traffic Report window (Figure 155). Figure 155. Traffic Report Window UCS 1000 R4.
PAGE 393
7 Common Administration Reports Administration Table 26 describes the information in this report. Table 26.
PAGE 394
7 Common Administration Reports Administration The system displays the Actions Menu (Figure 143 on page 314). 2 Select: > Modify The system displays the Modify Traffic Report window (Figure 156). Figure 156. Modify Traffic Report Window 3 Enter a day of the week, Monday through Sunday, or Yesterday in the Day: field, or press F2 (Choices) to select from a menu. The default is Yesterday.
PAGE 395
7 Common Administration Reports Administration 5 Enter Yes or No in the Summarize?: field to specify whether you want to see a Traffic Summary Report. The default is No, meaning that the system displays the Traffic Report instead of the Traffic Summary Report. The two reports are described below: ~ The Traffic Summary report provides information on the total traffic volume for each channel for the range of hours specified in the Traffic Report window.
PAGE 396
7 Common Administration Printing the Traffic Report Reports Administration The print option provides a complete printout of the Traffic Report. Note: You cannot print this report if a printer is not configured for use with the voice system. See Printer Administration on page 278 in Chapter 6, Peripheral Administration , for more information about printer administration. To print the Traffic Report: 1 Start at the Traffic Report window (Figure 155 on page 353) and press F8 (Actions).
PAGE 397
7 Common Administration Reports Administration To update the Traffic Report: 1 Start at the Traffic Report window (Figure 155 on page 353) and press F8 (Actions). The system displays the Actions Menu (Figure 143 on page 314). 2 Select: > Update The system updates the report and displays the values last saved. Signal Processing Activity Report The Signal Processing Activity report is not part of the Reports Administration menu. It is generated through the use of commands.
PAGE 398
7 Common Administration Reports Administration The data in the Signal Processing Activity report is collected by the spadc command. The spar command then summarizes and displays the data in an ASCII file. Data Collection for The spadc command collects data for the day of the week on which the the Signal command is executed, and outputs the data to an ASCII file named mm-ddProcessing Activity yyyy (for example, 09-12-2000).
PAGE 399
7 Common Administration Reports Administration ~ FAX ~ Text-to-Speech ~ Dial Pulse Recognition ~ Play ~ Code ~ CELP See spadc on page 574 and spar on page 575 in Appendix A, Summary of Commands, for more information about creating a Signal Processing Activity report.
PAGE 400
7 Common Administration Common Administrative Procedures Common Administrative Procedures See “Common System Procedures," in UCS 1000 R4.2 System Reference, 585-313-210, for information and procedures to perform the following common administrative tasks: • Format diskettes and cartridge tapes • Create a system backup • Restore the system from backup • Change the system date or time UCS 1000 R4.
PAGE 401
A Summary of Commands Overview This appendix provides an alphabetical list and brief description of all commands. Table 27 lists all the commands. Table 27. Command Synopsis Command Function add Adds a phrase to a UNIX talkfile (SSP only). addhdr Adds a voice or code header to a speech file (SSP only). alarm_cutoff Turns off a buzzer on the TAM unit. annotate Annotates a TSM trace stream with a message. assign card/channel Assigns a group number to a card or channel.
PAGE 402
A Summary of Commands Table 27. Overview Command Synopsis Command Function attach Attaches a unit. autoreboot Changes or displays the parameters associated with the autoreboot feature. bbs Reports the status of the voice system Bulletin Board. ccarpt Generates a call classification data summary report. cddrpt Generates a call data detail report. cdsrpt Generates a call data summary report for a specific date. checktf Checks for the existence of talkfiles in the voice system.
PAGE 403
A Summary of Commands Table 27. Overview Command Synopsis Command Function dbcheck Checks the resources available in the database. dbfrag Lists fragmentation information on the database. dbfree Checks the space available in the database by partition. dbused Provides database use by oracle user. decode Converts adpcm16 or adpcm32 files to pcm64 files (SSP only). defservice Defines an IRAPI service. delete card/channel Removes a card or channel from a service or an equipment group.
PAGE 404
A Summary of Commands Table 27. Overview Command Synopsis Command Function display assignments Displays the services assigned to channels. display card Displays information about specified cards. display channel Displays channel information. display dnis Displays the services assigned to DNIS and ANI numbers. display eqpgrp/group Displays an equipment group report. display messages Displays system messages.
PAGE 405
A Summary of Commands Table 27. Overview Command Synopsis Command Function erase Deletes a phrase from a UNIX talkfile (SSP only). explain Displays online error message explanations. faxit Queues or sends a fax. faxlog Displays a status of the fax transmissions. findHomes Populates a user’s home directory with files saved as part of an assisted upgrade. fixLogFile Upgrades existing logging files. iCk Performs various integrity checks based on the rules in a script file.
PAGE 406
A Summary of Commands Table 27. Overview Command Synopsis Command Function logEvent/logMsg Allows shell scripts to log a specific message. logFmt Displays and changes the parameters used to display messages and explanation texts. mkAlerter Reads an alerter description and generates the code that implements the description. mkheader Allocates user memory for script variables. mkimage Performs a complete system backup. msgadm Facilitates the administration of system messages.
PAGE 407
A Summary of Commands Table 27. Overview Command Synopsis Command Function remove Places a unit in the manual-out-of-service (MANOOS) state. removepkg Removes a software package. restore Restores a unit to the in-service (INSERV) state. retireAlarms Turns off minor, major, and critical alarms on the TAM unit. rmdb Displays the state of the resource manager and modify debug levels. show_sys Allows you to retrieve configuration and administration information from customer sites.
PAGE 408
A Summary of Commands Table 27. Overview Command Synopsis Command Function spsav Backs up speech (SSP only). spStatus Displays information about the pack file running on an SSP card. spVrsion Prints the version of the SSP driver currently installed on a machine. start_vs Brings the voice system up to a fully operational state. stop_vs Stops the voice system software gracefully. striphdr Strips voice or code headers from a speech file (SSP only).
PAGE 409
A Summary of Commands Table 27. Overview Command Synopsis Command Function upg Provides automated assistance in upgrading the system software to the latest release. vfyLogMsg Verifies the information associated with a specific logging message format. vsdisable Disables the automatic restarting of the voice system. vsenable Enables the automatic starting of the voice system at system reboot. vusage Displays the current load on the voice system (SSP only).
PAGE 410
A Summary of Commands add add The add command adds a phrase to a Unix talkfile (SSP only). Synopsis add phrase to talkfile from Description The add command adds phrases to the specified talkfile that were previously extracted from another talkfile using the copy command. The path name for the file may be the full pathname or the relative pathname. If no path is specified, the file is created in the current working directory.
PAGE 411
A Summary of Commands Note: add The add command adds a phrase to the SPEECHDIR default directory, which is /home2/vfs/talkfiles. To add a phrase, the conventional naming scheme must be followed. Files /speech/talk/*.pl Examples The following example adds phrase number 275 to talkfile 25 from the phrase stored in the UNIX file phr275 in the directory /tmp/junk.
PAGE 412
A Summary of Commands addhdr addhdr The addhdr command adds a voice or code header to a speech file (SSP only). Synopsis addhdr [voice/pcm64/adpcm32/adpcm16/sbc24/sbc16/celp16] [tag] Description The addhdr command is a filter that adds a header to a speech file. Two mutually exclusive types of headers are supported: voice and code. A voice header identifies a file as being editable, and includes an optional identifying tag.
PAGE 413
A Summary of Commands alarm_cutoff alarm_cutoff The alarm_cutoff command disables the buzzer on the TAM unit. Synopsis alarm_cutoff There are no arguments for this command. Description The alarm_cutoff command disables the buzzer on the TAM unit. annotate The annotate command annotates the transaction state machine (TSM) trace stream with a message. Synopsis annotate [channel] <“message”> UCS 1000 R4.
PAGE 414
A Summary of Commands assign card/channel Description The annotate command sends a message to TSM requesting that the given message be put into TSM’s trace stream. This command is useful for testing and debugging scripts. If a channel is specified, the message is associated with the channel’s trace stream. The message must be fewer than 160 characters. The annotate trace message is displayed in the trace output if a trace is running when the annotate command is executed.
PAGE 415
A Summary of Commands assign card/channel Synopsis assign card to [eqpgrp] [grpname] assign channel to [eqpgrp] [grpname] Description The assign card/channel command is used when a system is installed, the number of channels or cards changes, scripts are added or deleted, telephone numbers change, or the user wants to reconfigure the system. The system uses the card and channel assignments to route an incoming call to the group.
PAGE 416
A Summary of Commands assign_permissions Examples The following example assigns channels 0 through 47 to equipment group 1. assign chan 0-47 to eqpgrp 1 See Also assign service/startup display eqpgrp/group delete eqpgrp assign_permissions The assign_permissions command assigns voice system security permissions to a user. Synopsis assign_permissions Description The assign_permissions command assigns voice system security permissions to a user.
PAGE 417
A Summary of Commands assign_permissions system that the user can access. See Chapter 2, UNIX Administration , for more information on creating user logins. The user login argument represents the user who is to be assigned security permissions. The permissions level argument is the specific security class permission to be assigned.
PAGE 418
A Summary of Commands assign service/startup See Also unassign_permissions display_permissions assign service/startup The assign service/startup command assigns an installed service to DNIS and ANI numbers or directly to a channel.
PAGE 419
A Summary of Commands assign service/startup The chan_list variable indicates channel numbers or channel number ranges in the form chan1-chan2. A comma or space should be used to separate channel numbers in the list of channel numbers or ranges. The phone_list variable indicates telephone numbers or telephone number ranges in the form phone1:phone2. A comma or space should be used to separate the list of telephone numbers or ranges (for example, phone1:phone2).
PAGE 420
A Summary of Commands assign service/startup The following example assigns the service stdout and startup service stdin to channels 4 through 7. assign startup stdin service stdout to chan 4-7 The following example assigns the service stdout to DNIS 5000 through 5008 and ANI any. assign service stdout to dnis 5000:5008 The following example assigns the service stdout to DNIS 5000 through 5008 and ANI 6000.
PAGE 421
A Summary of Commands attach attach The attach command attaches a unit (card). Synopsis attach unit number [-i] [-n] Description The attach command is used to attach a card that has been “detached.” Use the attach command to allow the voice system to use a card that has just been replaced by hot swapping (that is, like-for-like replacement). To put the card into service, use the restore command.
PAGE 422
A Summary of Commands attach • -n — This option disables prompting from the system whether to wait until a conflict has been resolved (see the -i option below) or to terminate the request to attach. • -i — This option is used to enable secondary command registration. If T1 diagnostics are being run, this option allows the “attaching” of another card.
PAGE 423
A Summary of Commands autoreboot Examples The following example attaches a card 2. attach card 2 The following example attaches port 1 of card 2. attach card 2.1 The following example attaches a card to channel 2, port 1. attach card 2.1 See Also detach restore remove autoreboot The autoreboot command provides a means of changing or displaying the parameters associated with the autoreboot feature. UCS 1000 R4.
PAGE 424
A Summary of Commands autoreboot Synopsis autoreboot [enable|disable] [reboots ] [window ] [uptime ] autoreboot [status|s] autoreboot [help|h] Description The autoreboot command can be used to change parameters associated with the auto-reboot feature and to monitor the status of these parameters. The following options are recognized: • enable|disable — This option specifies whether to enable or disable the autoreboot feature. The default is enable.
PAGE 425
A Summary of Commands autoreboot • uptime — This option specifies the amount of time that the system must be in service before the automatic reboot feature is activated. The default is 5 minutes. • status — This option shows the current values of the automatic reboot parameters, plus the number of unanticipated reboots that occurred in the window minutes preceding the most recent system boot.
PAGE 426
A Summary of Commands bbs Example The following example enables autoreboot feature and changes window to two hours: autoreboot enable window 120 Caveat This command must be run from ksh (KORN shell). bbs The bbs command reports status of the voice system Bulletin Board (BB). Synopsis bbs [-d] [-h] [-l] Description The bbs command displays the field values of the BB slots. This information is sent to standard out (stdout).
PAGE 427
A Summary of Commands bbs • -h— Prints information about the hardcoded portion of the BB. • -l — Generates a long listing. The system displays all fields. The column headings and meaning of the columns in the bbs listing are given in Table 28 on page 388. In the table, the letter l indicates the long option, which causes the corresponding heading to appear. The all option means that the heading always appears. Table 28.
PAGE 428
A Summary of Commands Table 28. bbs bbs Column Headings Column Name Option Description SKEY (l) The semaphore key associated with the process and slot QID (l) The message queue ID RE-SPA (l) The number of respawns from the last restart of the voice system WKCNT (l) The ET work count for process Upon successful completion, bbs returns an exit status of zero.
PAGE 429
A Summary of Commands ccarpt ccarpt The ccarpt command generates a call classification data summary report. Synopsis ccarpt ccarpt Description The ccarpt command generates a call classification data summary report. This report is stored in standard out (stdout). The , , and arguments may be in the form mm/dd/yy or mm/dd/yyyy.
PAGE 430
A Summary of Commands cddrpt Examples The following two examples generate the call classification data summary report for October 10, 1993, and are equivalent command statements. ccarpt 10/20/93 ccarpt 10/20/1993 The following two examples generate the call classification data summary report from October 14 through October 20, 1993, and are equivalent command statements. ccarpt 10/14/93 10/20/93 ccarpt 10/20/1993 10/20/1993 cddrpt The cddrpt command generates a call data detail report.
PAGE 431
A Summary of Commands cddrpt Description The cddrpt command generates the call data detail report. This report is sent to standard out (stdout). Before this can be done, the database system must be up and running, but the voice system does not need to be up. The parameters for the cddrpt command are: • — This parameter represents the number of records to be reported. It can be any number, a range of numbers, or all indicating all records in the system.
PAGE 432
A Summary of Commands cddrpt Examples The following two examples generate a call data detail report for the first 100 pieces of call data collected on date October 20, 1993 for application “balance_chk” and are equivalent command statements. (Call event data, if any, is also included in the report.) cddrpt 100 balance_chk y all 10/20/93 cddrpt 100 balance_chk y all 10/20/1993 The following example generates a call data detail report for all call data in the system without including call event data.
PAGE 433
A Summary of Commands cdsrpt cdsrpt The cdsrpt command generates a call data summary report for a specific date. Synopsis cdsrpt Description The cdsrpt command generates the call data summary report for a date specified. The report is stored in standard out (stdout). Before this can be done, the database system must be up and running, but the voice system does not need to be up.
PAGE 434
A Summary of Commands • cdsrpt — This parameter is the date the data was collected in the system in the format mm/dd/yy or mm/dd/yyyy. If a 2-digit year argument is used, the following rules apply: ~ If the year argument is 70 and above, the 20th century is assumed. For example, 5/27/96 is interpreted as May 27, 1996. ~ If the year argument is between 00 and 69, the 21st century is assumed. For example, 5/27/06 is interpreted as May 27, 2006.
PAGE 435
A Summary of Commands codetype Error Messages CANNOT FIND /vs/trans/.D OR MALLOC SPACE FOR IT If you get the above message while running cdsrpt, take the following remedial steps: • Make certain the /vs/trans/.D file exits and is current. • Remove unnecessary files from the /vs/trans/ directory. codetype The codetype command identifies the type of coding header in a speech file (SSP only).
PAGE 436
A Summary of Commands configure_tam See Also addhdr striphdr configure_tam The configure_tam command is used to download the configuration file for the TAM unit. Syntax configure_tam There are no arguments for this command. Description The configure_tam command downloads the configuration file for the TAM unit. The configuration settings are saved and used as the active TAM configuration on reboot. UCS 1000 R4.
PAGE 437
A Summary of Commands copy copy The copy command copies a phrase from a UNIX talkfile to a UNIX talkfile (SSP only). Synopsis copy phrase from talkfile to Description The copy phrase command copies a phrase from one UNIX talkfile to another UNIX talkfile. The path name for the file may be the full path name or the relative path name. If no path is specified, the file is created in the current working directory.
PAGE 438
A Summary of Commands cpuType Examples The following example copies phrase number 2 from talkfile 1 to the file /speech/talk/a.1. copy phrase 2 from talkfile 1 to /speech/talk/a.1 The following example copies phrase number 174 from talkfile 25 to the file /speech/talk/h.4. copy phrase 174 from talkfile 25 to /speech/talk/h.4 See Also add erase list cpuType The cpuType command returns the type of central processing unit (CPU) used in the system. Synopsis cpuType UCS 1000 R4.
PAGE 439
A Summary of Commands cvis_mainmenu Description The cputype command returns the type of CPU on the system, either a 386 or a 486. If the cputype command returns a 3, you are using a 386. If the cpuType command returns a 4, you are using a 486. To determine the return value, examine the shell variable $?. cvis_mainmenu The cvis_mainmenu command accesses the administration menus. Synopsis cvis_mainmenu Description The cvis_mainmenu program is a menu interface used to access the Administration menu.
PAGE 440
A Summary of Commands cvis_menu cvis_menu The cvis_menu command accesses the Voice System Administration menu. Synopsis cvis_menu Description This command provides access to the Voice System Administration menu. See Also cvis_mainmenu dbcheck The dbcheck command checks the resources available in the database (Version 7 ORACLE). UCS 1000 R4.
PAGE 441
A Summary of Commands dbcheck Synopsis dbcheck -i dbcheck r dbcheck [w n[,m]] [-s] [-e] [-m user[~user...]] Description The dbcheck command checks spaces, usage, and rollback segment growth. The dbcheck command has three different usages. The -i option installs cron entries (optional) to run dbcheck at regular intervals and support for logger/alerter messages. (The -i option only needs to run once).
PAGE 442
A Summary of Commands dbcheck The third usage actually checks database space against a user set “water marks.
PAGE 443
A Summary of Commands dbcheck # dbcheck -w13,23 * Mon Feb 15 16:35:06 1993 dbcheck logTest.c:418 DBC001 -- -- --- Database 10 percent free, 3072 Blocks of 30720 available. Reason: Low DB Space. * Mon Feb 15 16:35:06 1993 dbcheck logTest.c:418 DBC002 -- -- --- Extents low, 100 used of 121, on object MY_TABLE Reason: Low DB Extents * Mon Feb 15 16:35:06 1883 dbcheck logTest.c:418 DBC003 -- -- --- Rollback segments=7680 blocks, 25 percent of total space. Reason: High Rollback Usage.
PAGE 444
A Summary of Commands dbcheck Diagnostics The dbcheck command returns the following values: 0 — Success, no limits exceeded 1 — Threshold exceeded 2 — Processing error 3 — Database is not running Caveat Once dbcheck log messages are installed using dbcheck -i, the alarm priorities, destinations, and thresholds can not be changed through the System Message Display screen as described in Message Administration on page 67, of Chapter 3, Voice System Administration .
PAGE 445
A Summary of Commands dbfrag dbfrag The dbfrag command lists fragmentation information on the database (Version 7 ORACLE). Synopsis dbfrag [-h -b] Description The dbfrag command is a shell script that reports on database allocation, usage, and fragmentation. The block size reported is in ORACLE blocks (2048 bytes). You can request the information to be reported in Mbytes with the -b option.
PAGE 446
A Summary of Commands dbfrag # dbfrag -b SYSTEM Tablespace, Space is in Mega-Bytes ALLOCATED FREE % FREE AVG/FRAG LARGEST FRAGMENTS DB_FILES ROLLBACK ----------------- ---------------- ------------ ---------------- -------------- ------------------- -------------- ---------------129.00 108.88 84.40 5.44 108.12 20 1 7.91 Examples The following example gets the largest contiguous ORACLE space available.
PAGE 447
A Summary of Commands dbfree dbfree The dbfree command checks the space available in the database by partition (Version 7 ORACLE). Synopsis dbfree [h] Description The dbfree command is a shell script that lists the amount of free space in the database by free contiguous blocks. The result is a detailed listing of each free memory area followed by the sum of each partition. The free blocks are listed in 2048 bytes/block (ORACLE blocks).
PAGE 448
A Summary of Commands dbfree Contiguous extents TABLE SPACE NAME FILE_ID START_BLOCK ---------------------------------- ---------------- ---------------------SYSTEM 1 5142 SYSTEM 1 5560 SYSTEM 1 4892 1 7892 SYSTEM SYSTEM 1 4164 : : : : : : : : SYSTEM 1 5598 SYSTEM 1 8946 SYSTEM 1 12650 SYSTEM 1 25179 SYSTEM 1 14939 sum MBYTES FREE --------------------.02 .03 .04 .04 .05 : : .73 4.00 4.45 10.00 20.00 --------------------47.
PAGE 449
A Summary of Commands dbused Caveats The dbfree command creates a temporary table “dba_fragments” under user system that compresses the adjacent entries provided by the dictionary view “dba_free_space.” See Also dbfrag dbcheck dbused dbused The dbused command provides database use by oracle user (Version 7 ORACLE). Synopsis dbused [hs] [u ] Description The dbused command is a shell script that shows the amount of space used by each object for a given user.
PAGE 450
A Summary of Commands dbused the entire database. The -h option skips the header message. This option is useful if you are parsing. The -u option allows the user to specify the oracle user id and password (the default is sti/sti, all for all users). Below is an output summary for user “all.” # dbused -su all Space allocated to objects.
PAGE 451
A Summary of Commands dbused # dbused Space allocated to objects. Oracle blocks (2048 Bytes/Block) NAME ------------------------------C1 CCA CCASUM CDH CDHSUM E2 EVENTS EVSUM LDBCOLS TYPE BLOCKS MBYTES EXTENTS MAX_EXTENTS ---------------- ---------------- ---------------- -------------- ---------------------INDEX 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .01 1 99 TABLE 5 .
PAGE 452
A Summary of Commands decode decode The decode command converts adpcm16 or adpcm32 files to pcm64 files (SSP only). Synopsis decode [adpcm32/adpcm16] Description Decode is a filter that converts ADPCM16 or ADPCM32 files to PCM64 files. Warning Coding headers should be stripped (using the stripdhr command) before running decode. See Also addhdr codetype encode striphdr UCS 1000 R4.
PAGE 453
A Summary of Commands defService defService The defService command defines an IRAPI service. Synopsis defService [-h] [-n] [-s ] [-p ] [-t P | T] [-a 0 |1 |2 |3 |4] [] Description The defService command is for use by IRAPI application developers. It creates the registration file for an IRAPI service that is necessary for assigning or deleting service to or from a channel or DNIS and/or ANI.
PAGE 454
A Summary of Commands defService When the application is started by the Application Dispatch (AD) process, the IRP_SERVICE_NAME is set to the -s argument if is non-NULL. Otherwise, IRP_SERVICE_NAME is set to , where the default is NULL. The -t option specifies whether the process that provides the IRAPI application is a permanent (P) or transient (T) process. The default is P for permanent.
PAGE 455
A Summary of Commands delete card/channel The argument specifies the IRAPI application. No default exists for this argument. Upon successful completion, the defService command creates the /vs/trans/.T file. Files /vs/trans/*.T See Also assign delete tas iRAPI -AD(4irAPI-AD) irRegister(3irAPI) delete card/channel The delete card/channel command removes a card or channel from a service or an equipment group. UCS 1000 R4.
PAGE 456
A Summary of Commands delete card/channel Synopsis delete card from [eqpgrp] delete channel from [eqpgrp] Description The delete card/channel command removes the specified card or channel from a service or equipment group. The parameters for the delete card/channel command are: •
PAGE 457
A Summary of Commands delete card/channel Examples The following example deletes card 4 from service group 1. delete card 4 from svcgrp 1 The following example deletes channels 10 through 13 from equipment group 3. delete channel 10-13 from eqpgrp 3 See Also delete eqpgrp delete service UCS 1000 R4.
PAGE 458
A Summary of Commands delete eqpgrp delete eqpgrp The delete eqpgrp command removes an equipment group. Synopsis delete eqpgrp Description The delete eqpgrp removes an equipment group. The argument is the equipment group list. To remove all equipment groups, use “all” as the group number. Examples The following example removes equipment group number 3. delete eqpgrp 3 The following example removes all equipment groups.
PAGE 459
A Summary of Commands delete service/startup delete service/startup The delete service/startup command unassigns the assignment of a service to DNIS and ANI numbers or of a service assigned directly to a channel.
PAGE 460
A Summary of Commands • delete service/startup — Contains a list of one or more channels or telephone numbers separated by blanks. The word “any” or “all” shows that service is removed from all calls regardless of what number was dialed. The chan_list variable indicates channel numbers or channel number ranges in the form chan1-chan2. Use a comma or space to separate the list of channel numbers or ranges.
PAGE 461
A Summary of Commands delete service/startup The following example deletes the service stdout to DNIS 5000 through 5008 and ANI any. delete service stdout from dnis 5000:5008 and ANI any The following example deletes the service stdout from DNIS 5000 through 5008 and ANI 6000. delete service stdout from dnis 5000:5008 ani 6000 The following example deletes the service stdout from DNIS any and ANI 6000 through 9000.
PAGE 462
A Summary of Commands detach detach The detach command places a card or channel in the NONEX state. If a card is detached, it can then be replaced by hot swapping (that is, like-for-like replacement). The blue LED indicates that is ready to be removed from the system. Synopsis detach unit number [-i] [-n] Description The detach command places a unit currently in the manual-out-of-service (MANOOS) state into the nonexistent (NONEX) state.
PAGE 463
A Summary of Commands detach • -n — This optional parameter disables prompting from the system whether to wait until a conflict has been resolved (see the -i option below) or to terminate the request to detach. • -i — This optional parameter is used to enable secondary command registration. If T1 diagnostics are being run, this option allows the “detaching” of another card.
PAGE 464
A Summary of Commands detach Examples The following example detaches card 4 and places it in the NONEX state as far as the system is concerned. detach card 4 The following example detaches channels 1 through 3 and places them in the NONEX state as far as the system is concerned. detach channel 1-3 See Also attach remove restore UCS 1000 R4.
PAGE 465
A Summary of Commands diagnose bus 1 diagnose bus 1 The diagnose bus 1 command tests a bus while it is in service. Synopsis diagnose bus 1 Description The diagnose bus command changes the temporary state of a unit to diagnostic (DIAG). If a unit fails the diagnostics, the permanent state is changed to BROKEN; otherwise, the permanent state is unchanged. The output is sent to the screen and also saved to a file in /vs/data/diagnose called busDiag.1. Example The following example diagnoses bus 1.
PAGE 466
A Summary of Commands diagnose card diagnose card The diagnose card command tests a card while it is in service. Synopsis diagnose card card# [option]... Description The diagnose card command is done at the card level for any card in the system. The card number option is the card number you want to diagnose. The word “all” can be used to specify all cards. This command changes the temporary state of a unit to diagnostic (DIAG).
PAGE 467
A Summary of Commands • diagnose card -i — Enables secondary command registration. See the description of -i for LSPS/SSP cards below. For LSPS/SSP cards, the valid options are: • -n — Disables prompting from the system whether to wait until a conflict has been resolved (see the -i option) or to terminate the request to diagnose. • -i — Enables secondary command registration. If T1 diagnostics are being run, this option allows another card to be diagnosed.
PAGE 468
A Summary of Commands diagnose card offline tests and a conflict is detected, the user is asked whether to wait until the conflict is resolved or to terminate the request to diagnose. If a unit fails the diagnostics, the permanent state is changed to BROKEN. If the unit being diagnosed previously was marked BROKEN and it passes diagnostics, it is put in the MANOOS state. Otherwise, the permanent state is unchanged.
PAGE 469
A Summary of Commands diagnose card diagnostic routine. If, while running diagnose, you want to stop the command, a message similar to the following may appear: Aborting request. Further administrative action may be needed to reach desired state. The diagnostics command for board board number has been stopped. The card will be marked as BROKEN. Or, the system may display: Could not stop diagnostics for board board number. The diagnostics may continue to run in the background.
PAGE 470
A Summary of Commands dip_int dip_int The dip_int command sends DIP interrupt to a script on a channel or a range of channels. Synopsis dip_int channel dip_int channelStart-channelEnd Description The dip_int command sends a message or messages to TSM requesting that TSM send interrupt messages to the script running on channel or the range of channels channelStart-channelEnd. If no script is running on the channel or if TSM does not own the channel, no action is taken for the channel.
PAGE 471
A Summary of Commands dip_int Examples The following example requests that TSM send interrupt messages to channel two. dip_int 2 The following example requests that TSM send interrupt messages on channels one through 32. dip_int 1-32 Return Values If the dip_int is successful, a 0 value is returned. If any value other than 0 is returned, the dip_int command completely or partially failed. If dip_int returns a value of 2, then dip_int failed due to temporary condition.
PAGE 472
A Summary of Commands display assignments display assignments The display assignments command displays the services assigned to channels. Synopsis disp assignments [option] [option] Description The display assignments command is used to display all the services and startup services assigned to channels. The display assignments command options are shown in Table 29: Table 29.
PAGE 473
A Summary of Commands Table 29. display assignments display assignments Command Options Option Description startup startup name Displays channels assigned with a specific startup service channel chan# Displays assignments for the channel specified by chan#. A range of channels can be specified. Note: If more than one option is used, the system displays only channels that satisfy all the options given. If an invalid combination of options is given, the system displays an error message.
PAGE 474
A Summary of Commands display card display card The display card command displays information about specified cards. Synopsis disp[lay] card [option [option] ] Description The display card command displays data about a specified card or about cards in a specified state. In the output, the physical slot number, the osindex, and the voice system card number are all the same. The output also correctly reflects which card is primary master, which is secondary master, and which cards are slave.
PAGE 475
A Summary of Commands display card • mtc — Displays all cards being used by the maintenance process. • manoos — Displays all cards in the manual out-of-service state. • broken — Displays all cards in the broken state. • ins[erv] — Displays all cards that have at least one channel in the in-service state. • netoos — Displays all cards that have at least one channel in the network out-of-service state.
PAGE 476
A Summary of Commands display card Sample output: CARD 4 STATE: Manoos CLASS: Signal_Processor(SSP) NAME: CWB1 OPTIONS: slave,tdm1 FUNCTION: play+code O.S.INDEX: 4 CARD 6 STATE: Manoos CLASS: Digital(T1) NAME: CWB2 OPTIONS: primary_master,tdm1 FUNCTION: E&M O.S.INDEX: 6 CD.PT 6.0 6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.
PAGE 477
A Summary of Commands 6.17 6.18 6.19 6.20 6.21 6.22 6.23 17 18 19 20 21 22 23 Manoos Manoos Manoos Manoos Manoos Manoos Manoos Mar Mar Mar Mar Mar Mar Mar 24 24 24 24 24 24 24 11:26:02 11:26:02 11:26:02 11:26:03 11:26:03 11:26:03 11:26:03 display card feature_tst feature_tst feature_tst feature_tst feature_tst feature_tst feature_tst - 2 2 2 2 2 2 2 tdm tdm tdm tdm tdm tdm tdm T1.5 T1.5 T1.5 T1.5 T1.5 T1.5 T1.
PAGE 478
A Summary of Commands 15.10 15.11 15.12 15.13 15.14 15.15 15.16 15.17 15.18 15.19 15.20 15.21 15.22 15.
PAGE 479
A Summary of Commands 16.8 16.9 16.10 16.11 16.12 16.13 16.14 16.15 16.16 16.17 16.18 16.19 16.20 16.21 16.22 16.
PAGE 480
A Summary of Commands display channel display channel The display channel command displays channel information. Synopsis disp[lay] channel option [option] disp chan option [option] Description The display channel command is used to list information at the channel level. The display channel command options are: • number — Displays information on the channel specified by channel number. A range of channels may be specified in the form m–n. • all — Displays information on all channels.
PAGE 481
A Summary of Commands display channel • t1 —This options displays all channels assigned on T1 cards. • sp — This options displays all channels assigned to SSP service. • netoos — This options displays all channels assigned to network service. • hwoos — This options displays all channels assigned to hardware service. • foos — This options displays all channels assigned to facility service. If more than one option is used, the system displays only channels that satisfy all the options given.
PAGE 482
A Summary of Commands display dnis display dnis The display dnis command displays the services assigned to DNIS and ANI numbers. Synopsis disp dnis Description The display dnis command is used to display all the services assigned to DNIS and ANI numbers. Example The following example displays information for all the services assigned to DNIS and ANI numbers: disp dnis UCS 1000 R4.
PAGE 483
A Summary of Commands display eqpgrp/group display eqpgrp/group The display eqpgrp/group command displays an equipment group report. Synopsis disp eqpgrp group number disp group group number Description The display eqpgrp command is used to list all the equipment assigned to the specified equipment group. The group number is the number of the equipment group. If the group number is missing, the system displays a syntax message. If you specify "all", the system displays every equipment group.
PAGE 484
A Summary of Commands display equipment The following example lists all equipment assigned to all equipment groups. disp eqpgrp all See Also assign card/channel delete eqpgrp display equipment The display equipment command displays the following output: • serial number — displayed for E1/T1, SSP, and SBC (including CPU, IO, MEML, MEMU, and VGA cards). Not available for the LSPS. • vintage — displayed for E1/T1 and SSP. • suffix — displayed for E1/T1 and SSP.
PAGE 485
A Summary of Commands display messages Synopsis display messages [priority ] [-c] [start ] [stop ] [card ] [channel ] [ID ] [source
PAGE 486
A Summary of Commands display messages The priority argument should be used to display messages with specific types of urgencies. Two groups of priorities exist: alarms and events. Alarms are messages that have been reported as *C (critical), ** (major), or * (minor) priorities. Events are all the remaining messages that have no priority, for example, status messages.
PAGE 487
A Summary of Commands Display Message Options display messages To display only specific types of messages, you may precede the number of messages to be displayed with one or more of the following options: • start • stop • card • channel • id • source • pattern • number If more than one of the options is specified, the system displays only messages that meet all of the specifications. start The start option allows you to specify a starting time for display of messages.
PAGE 488
A Summary of Commands • “05/01/93” • “05-01-93” display messages Examples of specifying the time are: • hh:mm:ss • hour=hh • min=mm • sec=ss where hh is 0 to 23, and mm and ss can be 0 to 59. DO NOT mix the hh:mm:ss format with the item==xx format. If portions of the time are not specified, the time default is 0 hours, 0 minutes, and 0 seconds. Also, giving only the time of day indicates the current date.
PAGE 489
A Summary of Commands display messages stop The stop option allows you to display messages logged up to a specific time. The date and time syntax is the same as that for the start option. Therefore, display messages stop today displays all messages that were logged before today. The start and stop options can be used together to display messages that were logged over a specific period of time. For example, display messages start “May 1” stop “May 2” displays all messages logged on May 1 of this year.
PAGE 490
A Summary of Commands display messages You can also use the card option to display messages logged about a specific type of card. For example, display messages card t1 displays all messages logged about T1 cards. channel The channel option works like the card option. For example, display messages channel t1 displays all messages logged about T1 channels, whereas display messages channel 5 displays all messages logged about channel 5. Note: The channel option requires an argument.
PAGE 491
A Summary of Commands display messages occurrences of that message, display messages id TWIP004,TWIP009 displays all occurrences of both messages. source The source option allows you to display messages logged by a particular system process. Table 30 shows some of the standard system processes. Table 30.
PAGE 492
A Summary of Commands display messages pattern The pattern option allows you to specify a regular expression as accepted by logCat that may appear in any part of a message. (See logCat on page 514 for additional information.) The pattern must enclosed in quotes and surrounded by slashes (/). For example, display messages pattern ‘/XYZ/’ provides all messages that use the pattern XYZ anywhere in the message. Note: The pattern option is case-sensitive.
PAGE 493
A Summary of Commands display messages system message formats along with definitions and examples. Each message displayed conforms to the following format: PR DAY MON DD HH:MM:SS ZZZ YYYY TTTTTTTT YY UU NUM TEXT... TEXT (continuation if necessary.) SOURCE blank line Table 31.
PAGE 494
A Summary of Commands Table 31. display messages System Message Formats Field Definition Examples UU Unit Type CA (Card) or CH (Channel) or -- if N/A NUM Unit Number 000 to 999 or --- if N/A TEXT Message Text Varies with message (see example); can be more than one line long.
PAGE 495
A Summary of Commands display_permissions display_permissions The display_permissions command displays the current voice system security permissions for a particular user. Synopsis display_permissions Description The display_permissions command displays the current voice system security permissions for a particular user if any are assigned. The argument represents the user for which permissions are to be displayed.
PAGE 496
A Summary of Commands display services display services The display services command lists all valid services or scripts. Synopsis display services disp services Description The display services command lists all valid services or scripts on a system. Example The following example lists all valid services or scripts currently on the system.
PAGE 497
A Summary of Commands dspActAlarms Synopsis display_tam There are no arguments for this command. Description The display_tam command displays all the values of the sensors monitored by the TAM unit. If necessary, the display_tam command sends this output to page. dspActAlarms Synopsis dspActAlarms [-H] [-t cnt] [-b cnt] [-a startTime] [-z endTime] [-s /searchPat/] Description Display the active alarms. Variables include: • -H — suppress header lines prior to the first alarm.
PAGE 498
A Summary of Commands dspRetAlarms • -b lines — show beginning "lines" of file. • -a locant — specifies the place to start printing. • -z locant — specifies the place to stop printing. • -s locant — search for specific patterns or times. There may be more than one specification. See Also dspRetAlarms retireAlarms dspRetAlarms Synopsis dspRetAlarms [-H] [-t cnt] [-b cnt] [-a startTime] [-z endTime] [-s /searchPat/] Description Display the retired alarms.
PAGE 499
A Summary of Commands edExplain • -t lines — tail the last "lines" of file. • -b lines — show beginning "lines" of file. • -a locant — specifies the place to start printing. • -z locant — specifies the place to stop printing. • -s locant — search for specific patterns or times. There may be more than one specification. See Also dspActAlarms retireAlarms edExplain The edExplain command edits the explanation text for one or more message tags. Synopsis edExplain {msgID} [...] UCS 1000 R4.
PAGE 500
A Summary of Commands edExplain Description The edExplain command edits the explanation text for one or more message tags. The following are environment variables for the edExplain command: EDITOR This is the program used to “edit” the explanation text. The default is vi. EXPLAINDIR This is the root directory of the explanation texts. The default is /gendb/data/explain VERBOSITY If set to anything, edExplain will run verbosely. An explanation file is basically a clear text file.
PAGE 501
A Summary of Commands edExplain The translateLst file should be updated to include the msgID, msg string, and file name, in which the explain text can be found (usually just the msgID name). When exiting the translateLst file, enter :w! followed by q. Two exceptions exist to the rule that the file contains clear text that will be displayed to the user: • Any line beginning with a pound sign (#) character is considered to be an internal comment and is not displayed. • Lines beginning with “.
PAGE 502
A Summary of Commands encode encode The encode command converts ADPCM16 or ADPCM32 files to PCM64 files. Synopsis encode [adpcm32/adpcm16] Description Encode is a filter that converts PCM64 files to ADPCM16 or ADPCM32 files. ADPCM16 is easy to code and saves space, but does not provide good quality sound. Warning The voice header used by GSE should be stripped (using stripdhr) before running encode.
PAGE 503
A Summary of Commands erase See Also addhdr codetype decode striphdr erase The erase command deletes a phrase from a UNIX talkfile (SSP only). Synopsis erase phrase from talkfile Description The erase command deletes the phrases identified by the phrase ID from the UNIX file.
PAGE 504
A Summary of Commands erase After you enter the erase command, the system displays the following message, asking you to confirm the command before each phrase is erased: Do you want to erase phrase ? (y/n) If the “all” option is used for phrases, the system prompts you only once to confirm the command: Are you sure you want to erase ALL phrases from talkfile ? (y/n) If the specified phases does not exist, the system displays: Phrase does not exist in talkfile No
PAGE 505
A Summary of Commands explain The following example erases phrases 218 through 222 and phrase 225 from talkfile 26. erase phrase 218-222, 225 from talkfile 26 The following example erases all phrases from talkfile 29. erase phrase all from talkfile 29 See Also add copy list explain The explain command displays on-line error message explanations. Synopsis explain {msgID} [...] explain -l {pattern} [...] explain -d {msgID} [...] UCS 1000 R4.
PAGE 506
A Summary of Commands explain Description The {msgID} is one of the two forms of identification that comes with each online error message. The primary form is {CLASS}nnn, where {CLASS} is the class of messages, such as CGEN, TSM, and nnn is the index of the message within the class of messages. The second form, which is available with most messages, is the mnemonic form (for example, CGEN_NOMSGQ or CGEN_MSGRCV.
PAGE 507
A Summary of Commands explain PAGER The pager program used if the explanation is longer than 24 lines or more than one explanation is requested. The default is pg. If you do not want paging even for long explanations, using -d or setting PAGER=cat will disable paging. A one-line form would be: PAGER=cat explain {msgID} or explain -d {msgID} EXPLAINDIR The directory in which the explanation directories are found. The default is ${PRODUCTROOT}/gendb/data/explain.
PAGE 508
A Summary of Commands explain The explanation file itself is almost a clear text file of what you want the user to see when they ask for the explanation. There are two features of the file that are not plain clear text. All lines beginning with the pound sign (#) character are treated as internal comments and are not output. Also lines of the form explain {msgID} have special meaning. They cause the inclusion of the explanation text specified by the {msgID}.
PAGE 509
A Summary of Commands explain second example has a truncated file name, because file names are limited to 14 characters in most UNIX systems and if you want to use source code control, then the file name must not be longer than 12 characters. The recommended way to store an explanation is under a file name related to the mnemonic {msgID} rather than the {CLASS}nnn name, since the later is meaningless.
PAGE 510
A Summary of Commands findHomes Files /gendb/data/explain # directory in which explanation directories are located. /gendb/data/explain/translateLst # file containing the synonym list of {msgID}s. See Also edExplain findHomes The findHomes command populates your home directory with user files saved as part of an assisted upgrade.
PAGE 511
A Summary of Commands findHomes For each user, the entire directory structure (including all files) preserved from the user home directory on the pre-upgrade machine is moved to the user home directory on the upgraded system. If a saved file has the same name as a file that already exists in a user’s home directory on the upgraded system, the saved version is moved to o. in that directory.
PAGE 512
A Summary of Commands fixLogFile fails, then the files are restored in a directory with the full path name of the user’s home directory on the preupgraded system. Note: A message is printed indicating any directory for which all the files are not successfully relocated. Example The following example causes all files found in /home/o.
PAGE 513
A Summary of Commands fixLogFile Description When classes of logging messages are expanded, contracted, inserted, or removed, fixLogFile can change the index assignments of messages. When this happens, messages whose indexes changed and were logged under the previous environment become unexpandable by logCat. The fixLogFile command, given information about the previous assignments and the new assignments, upgrades logged data so that it remains expandable by logCat. Each message is examined.
PAGE 514
A Summary of Commands fixLogFile Normally, fixLogFile generates a short message about each file that it converts. The -S flag suppresses this output. The fixLogFile command requires access to the old o.systemLog.h and o.textLogFmt files and the new systemLog.h file to perform its job. It expects to find these files in $LOGROOT/formats. If alternate sources of these files are to be used, the -o and -n flags are used.
PAGE 515
A Summary of Commands fixLogFile ${LOGROOT}/data is examined to see if it is a compressed logging file. If it is not, it is ignored. If it is, it is converted. After the files are converted, the time stamps are reapplied so they have the same date after conversion as they did before the conversion. Caveats The fixLogFile command only takes care of changes in classes of logging messages.
PAGE 516
A Summary of Commands iCk, iCkAdmin iCk, iCkAdmin The iCk process is the daemon process that performs various integrity checks on the system based on rules in a script file. The iCkAdmin command is a related administration command. Synopsis iCk [-v NNN] [{envName}={value}] [{rule-file}] iCk -c [-i | -f {file} | cmd...] iCkCmd [-i | -f {file} | cmd...] iCkAdmin [-c] [-a {on|off}] [s {entryType [:{ID}]}] [-e {entryType [:{ID]}] [iCk.
PAGE 517
A Summary of Commands iCk, iCkAdmin As a daemon process, iCk accepts one flag, the -v flag, which initializes the internal verbosity flags according to the value NNN provided. This value can be in decimal, hexidecimal, or octal. None of the symbolic flag names apply in this mode. Table 32 describes the bit meanings. Table 32.
PAGE 518
A Summary of Commands Environment Variables iCk, iCkAdmin The iCk command also accepts environment variables from the command line of the form: {variable-name}={value} These can be used to set the following environment variables that also affect the behavior of the iCk command: VERBOSITY This is an alternative way to set the internal verbosity flags. The meanings of the bits are the same as for the value supplied to the -v flag.
PAGE 519
A Summary of Commands iCk, iCkAdmin When iCk is executed with the -c flag or by the alternate name iCkCmd, is run as the command interface to the iCk daemon process. -i This option specifies that iCk to run in interactive mode. This causes it to generate prompts as it requests information from its standard input. Without the -i flag, iCk silently accepts input from its standard input. This might be useful if used in a shell script.
PAGE 520
A Summary of Commands • iCk, iCkAdmin a {on|off} This option causes the rules file to be read, the autoReboot entry set the specified state, and written back out again. • -s {entryType[:{ID}]} This option causes the rules for the specified entries to be shown. • -e {entryType[:{ID}]} This option allows interactive editing of the specified entries. This feature is not yet complete.
PAGE 521
A Summary of Commands iCk, iCkAdmin • {runlevels} — This is specification of the run levels at which to perform the activity. The syntax is the same as used by init, that is, 4 = run level 4, 234 = run levels 2, 3, or 4. • {checkPeriod/Time} — This indicates the activities performed repetitively will have a specification of either how often to perform the activity or at what times of the day or week to perform the activity.
PAGE 522
A Summary of Commands iCk, iCkAdmin All five elements are required for the specification to be accepted. Each element can be: • * All items in class (days of the month, hours in the day, and so on.). • N The specific item • N-M The items between N and M inclusive • N,M The individual items N and M in the class The items within each class are: • {monthday} — 1-31 • {weekday} — ASCII day of the week (sun, mon,...) • {hour} — 0-23 • {min} — 0-59 • {sec} — 0-59 UCS 1000 R4.
PAGE 523
A Summary of Commands iCk, iCkAdmin For example: “* * * 0 0” means perform each hour on the hour. “13 fri 12 0 0” means perform the activity at noon on any Friday the 13th. • {cmd} — This specific command is executed if the activity so dictates. Within the command itself, there are four meta-words that can be used to generate flexible commands. Not all four meta-words have meaning in all cases.
PAGE 524
A Summary of Commands Activities • iCk, iCkAdmin $timingMsg {process} {runlevels} {checkPeriod/Time} This activity causes a timing message to be sent to a specified process at regular intervals whenever the system is at one of a specified run levels. Currently, the TSM and the VROP processes expect to receive timing messages once every 2 seconds.
PAGE 525
A Summary of Commands • iCk, iCkAdmin $autoReboot {off/on} {u-reboots} {ubPeriod} {runlevels} {setPeriod} This activity controls the feature that automatically sets the UNIX kernel autoreboot flag. If the entry is marked “off,” then the autoreboot flag is not automatically turned on. It can still be manually set with an iCk command. If the entry is marked “on,” then the automatic setting is enabled. The remaining parameters control when the flag is set.
PAGE 526
A Summary of Commands iCk, iCkAdmin For example, typing $autoReboot on 5 60m 4 5m, which is the standard default setting, specifies that if fewer than five unanticipated reboots occurred in the past 60 minutes, the autoreboot flag is set in the UNIX kernel 5 minutes after reaching run level 4. If five or more unanticipated reboots occurred in the past 60 minutes, then the autoreboot flag is not set until 60 minutes after reaching run level 4.
PAGE 527
A Summary of Commands iCk, iCkAdmin The command specified is executed. In this case the meta-words %f, %d, and %b are defined as the various parts of the file name and can be used in the command. • $fileCheck {file} {runlevels} {checkPeriod/Time} {type} {owner} {groups {modemask} {modes} [cmd] This activity can be used to ensure that a specific file or files exist and have the proper ownership and modes. {file} specifies the file or a pattern that selects a set of patterns.
PAGE 528
A Summary of Commands iCk, iCkAdmin and {modes} were 0444, then the check would be to ensure that the file is readable by anyone, but whether it is writable or executable is not of interest. If on the other hand {modeMask} was 0777, while {modes} was 0444, then the check would be to ensure that the file is only readable and must not be writable or executable by anyone. If a file fails to pass a $fileCheck test, it is always reported. If the optional [cmd] is specified, then this command is executed.
PAGE 529
A Summary of Commands iCk, iCkAdmin $fileCheck /etc/shadow - - f root - 0777 0400 Check only once. The /etc/shadow file should be owned by root and be read-only to root. $fileMax /tmp/*.lst 10000 - remove Remove all the files in /tmp ending with an extension of .lst if they are bigger than 10,000 bytes. Do this only once. $fileMax /tmp/*.hist 0 - exex ~/bin/mv %f %d/o.%b~ For any nonzero-length files in /tmp with an extension of .hist, save them as /tmp/o.*.
PAGE 530
A Summary of Commands iCk, iCkAdmin then the window period of time for the $autoReboot rule is used. This command generates three numbers: the total number of reboots in the specified period of time prior to and including the current boot of the system, the number that were anticipated (or deliberate), and the number of unanticipated reboots. This request does not communicate with the iCk daemon process. • autoReboot {set|clear} This command forces the kernel autoreboot flag into the specified state.
PAGE 531
A Summary of Commands • iCk, iCkAdmin quit This command causes the iCk daemon to exit gracefully. (Since iCk is normally run from the /etc/inittab file, init immediately respawns the daemon.) In interactive mode, the command requires confirmation. • verbosity {value} This command sets the iCk daemon’s verbosity flags to the specified values. In this case, the symbolic names are accepted as well as octal, decimal, or hexidecimal values.
PAGE 532
A Summary of Commands iCk, iCkAdmin there is the a_clockID, which is nonzero if an alarm is running for the current activity and the a_nextAlarm, which indicates at what time the next alarm is set to expire.
PAGE 533
A Summary of Commands • iCk, iCkAdmin timingMsg This object is all the $timingMsg activities. • hungProcess This object is all the $hungProcess activities. • autoReboot This object is the $autoReboot activity. • fileMax This object is all the $fileMax activities. • fileCheck This object is all the $fileCheck activities. • miscellaneous This object applies to the print command only.
PAGE 534
A Summary of Commands iCk, iCkAdmin All remaining information is activity specific. By activity the information logged is: • $timingMsg The name of the process, the Bulletin Board slot, and instance. • $hungProcess The name of the process, the PID, the Bulletin Board state, work count, time, flag, slot, and instance.
PAGE 535
A Summary of Commands • iCk, iCkAdmin core This command is available for debugging purposes. It causes iCk to produce a core file in /tmp/iCk.core via a core dump operation is a spawned child process. In other words, iCk itself does not stop, but you do get a reliable core of iCk for debugging evaluation. Default File The iCk process responds to default parameters placed in /vs/etc/default/iCk. Initially there are two values.
PAGE 536
A Summary of Commands iCk, iCkAdmin Files /vs/etc/iCk.rules # the default rules file /tmp/iCkPipe # the named pipe used to speak to iCk /vs/etc/default/iCk # default parameters Caveats The iCk process is a daemon process running as “root.” Since the rules support the concept of executing an arbitrary command, the /vs and the /vs/etc directories need to be protected against tampering and the iCk.rules file should only be writable by authorized users. See Also logCat UCS 1000 R4.
PAGE 537
A Summary of Commands logCat logCat Syntax [-{t|b} lines] [-c] [-m] # Simple behaviors [-a locant] [ -z locant] # Beginning and endings [-s locant] [-q locant] [-R] # Selection of messages [-P priority] [-d data -l log-prefix | # Source of data -L {cmpMsg} | file] [-r root] [-f format] [-V] # Display options [-w width] [-p continuation-prefix] [-T textLogFmt] [-A {s|c}:abbreviations] [-B breakChrs] [-[U|H]] [-v] [-D] # Misc/debug options Default behavior with no arguments is to display all the files of
PAGE 538
A Summary of Commands logCat • -c — Continuously display last lines of file • -m — Meticulous time check. Normally the log file name and the creation date are used to determine the date of the file. To be sure that the creation dates are accurate, use the -m flag. This causes the time stamp of the first message in each log file to be used instead of the name and modification date. This is slower, but more reliable. • -r root — Specify alternate "root" directory for textLogFmt file.
PAGE 539
A Summary of Commands logCat • -p continuation-prefix — The string to be appended to each continuation line. The default is no continuation prefix. The continuation prefix can also be provided via the environment variable LOGCONTPREFIX. • -d data — Name of the directory to find the log files in. The data directory can be provided in the environment variable LOGDATA. The default is ${LOGROOT}/data. • -l log-prefix — Prefix of the log files to examine.
PAGE 540
A Summary of Commands • logCat -P — Selects messages by their priority. Priorities can be specified as a number or as the symbolic representations - for E_NONE, M for E_MANUAL, * for E_MINOR, ** for E_MAJOR, and *C for E_CRITICAL. More than one -P can be specified if more than one priority is of interest. For example: -P 3 -P 4 # All E_MAJOR and E_CRITICAL msgs. -P * -P *C # All E_MINOR and E_CRITICAL msgs.
PAGE 541
A Summary of Commands logCat • -U — Unhide "hidden" messages. This option causes all messages, including those being hidden by the "hideMsg" command to be displayed. • -H — Enable the "hide" message feature. This option is used to toggle off the -U switch when it appears earlier on the command line or in the $HOME/.logCatRC file. • -D — Set a debug flag, which causes locants to be printed at the beginning and some statistics to be listed at the end of the run.
PAGE 542
A Summary of Commands logCat specified date, in other words, "Oct. 11, 97" and "10/11/97" are assumed to be "10/11/97 00:00:00". A month and a day without a year are assumed to be in the current year unless this would put it more than 1 month in the future, when it is assumed to be the previous year. For example, assuming that it is currently "Mar. 3, 98", if the user specifies "02/15", it is assumed to be "02/15/98".
PAGE 543
A Summary of Commands logCat sigh (+) sign immediately following the s or q for the second and subsequent locant that is to be OR’ed together. For example: "-s/GEN006/" "-s+!/New York/" means on messages containing "GEN006", but not containing "New York". It is also possible to apply search locants to specific fields of a message by specifying a "synthetic field" and an equal sign prior to the search pattern. For example, "-s@sym@=!/LG_BADARGS/" means all messages that are not of type "LG_BADARGS.
PAGE 544
A Summary of Commands logCat The second search language uses the standard "regular" expression syntax. It is in effect when the -R flag is specified. It supports: • ^ — Beginning of message • $ — End of message • . — A single unspecified character • [xxx] — Any character is the list "xxx". "xxx" may include ranges of characters: A-Z, etc.
PAGE 545
A Summary of Commands logCat Format The basic format of the message can be controlled in a number of ways. The "-f" option or the LOGFORMAT environment variable specify the format using the following special sequences to specify the various parts of a message. The default format is: "%P %T %N %S:%L\n%M" • %P(...) — Priority level format: %d or %s • %T(...) — Time level format: all options supported by "date" cmd.
PAGE 546
A Summary of Commands • logCat \{chr} — Standard C backslash conventions • ... — All other characters are printed as is. • Synthetic Fields — Synthetic fields are alternate names for %P, %T, %N, %S, %L, and %M fields, but they also give access to specific fields within the %M field by name or index. The legal synthetic fields are: ~ @index@ OR @id@ OR @i@ — The absolute index of the message. ~ @symbol@ OR @sym@ OR @s@ — The symbolic name of the message. ~ @class@ OR @c@ — The class of the message.
PAGE 547
A Summary of Commands logCat Abbreviations It is possible to translate common abbreviations. The -A option controls this behavior. Abbreviations and acronyms can be translated using a translation script. The feature is turned on with the -A c|s abbreviations option. It can be forced off, if enabled via the environment variable, via the -A a option. The file abbreviations is the source of the translations. Translations is done in one of two forms, "simple", denoted by s, or "complex", denoted by c.
PAGE 548
A Summary of Commands lComp ignored. If either the abbreviation or the translation includes white spaces, it must be enclosed in quote characters as was shown in the example above. The abbreviations feature can also be enabled by setting the environment variable LOGABBREVIATIONS=M:file, where M is either s or c, and file is the name of the file. lComp The lComp command combines a series of message files and produces a file of compressed format files and an expansion format file.
PAGE 549
A Summary of Commands lComp backslash and newline characters, by lComp and treated as one long line during compilation. lComp produces five files: a header file, a compressed format file, an expansion format file, a data dictionary file, and a data dictionary mapping file. The default names are systemLog.h, cmpLogFmt, textLogFmt, dataDictLog, and ddMapLog, respectively. -s name -c name -t name -d name -m name Changes the systemLog.
PAGE 550
A Summary of Commands lComp the expansion formats, which expandLog uses to convert a compressed logging file into a human-readable statement. The dataDictLog file contains SQL names for the variable fields in each message. They are of the form: abs_index fld-name,type[,length[,precision]]... The abs_index is the index number of the message within the universe of all messages compiled by lComp.
PAGE 551
A Summary of Commands list list The list command lists the directory entries for specific phrases in the UNIX file (SSP only). Synopsis list -l [phrase ] [in] [talkfile ] Description The list command displays the phrases stored in the specified talkfile. The valid arguments for the list command are: • — Specifies the number (or range) of the phrase or phrases to be listed. To list all phrases in a particular talkfile, enter all for .
PAGE 552
A Summary of Commands list The listed entries are sorted by talkfile number and phrase. The information printed for each phrase consists of talkfile number, phrase number, phrase size in bytes, phrase size in blocks, the phrase length in seconds, and the speech coding type. Note: The list command lists the directory entries for specific phrases in the SPEECHDIR default directory, which is /home2/vfs/talkfiles. Examples The following example displays phrase 174 as stored in talkfile 25.
PAGE 553
A Summary of Commands logCat logCat The logCat command reads the compressed logging files and outputs human readable messages. Synopsis logCat [-{t|b} lines] [-a locant] [-z locant] [-v] [-c] [-m] [-r root] [-s locant] [-q locant] [-w width] [-p continuation-prefix] [-d data -l log-prefix | file] [-f format] [-V] Description The logCat command reads in a file of compressed logging messages generated by log and expands them to a readable format.
PAGE 554
A Summary of Commands logCat • -m — This option is the meticulous time check. Normally, the log file name and the creation date are used to determine the date of the file. If the creation dates have been messed up, the -m flag causes the time stamp of the first message in each log file to be used instead of the name and modification date. This is slower but more reliable. • -r root — Specifies an alternate root directory for textLogFmt file. The default is /usr/spool/log.
PAGE 555
A Summary of Commands logCat mday=mm mon=nn or mon=mmm year=nn[nn] wday=n or wday=ddd yday=nnn. Portions left out default to this date, 0 hours, 0 minutes, and 0 seconds; that is, giving only the time of day indicates today’s date. If the form “item=xxx” is used, all elements not specified default to ‘*’; hence “wday=Sun” means all messages on any Sunday. Do not mix standard format with the “item=xxx” format. The results are not predictable.
PAGE 556
A Summary of Commands logCat • -w width — If lines are to be wrapped, this is the width at which the wrapping should take place. 0 means no wrapping and is the default. The width can also be supplied via the environment variable LOGCOLUMN. • -p continuation-prefix — This is the string to be appended to each continuation line. The default is no continuation prefix. The continuation prefix can also be provided via the environment variable LOGCONTPREFIX data.
PAGE 557
A Summary of Commands • logCat %N Name of process specified by the loginit call of the process %S Source file name %L Line number %M Message text %% The % character \{chr} Standard C backslash conventions ... All other characters are printed as is. The format can be provided via the environment variable LOGFORMAT. -V — This option makes the control characters visible. They are printed as \X if they have a special C notation.
PAGE 558
A Summary of Commands logCat LOGDATA This variable is the directory in which the log data files are found. The default is ${LOGROOT} /data. LOGFORMAT This variable is the format in which to print the log messages. The default is %P %T %N %S:%L n%M. LOGCOLUMN This variable is the column at which to wrap long expansions. The default is0, meaning do not wrap long messages. LOGCONTPREFIX This variable is the string to be prepended to continuation lines when long lines are being wrapped.
PAGE 559
A Summary of Commands logDstPri logDstPri The logDstPri command creates the shared memory containing the dynamic destinations and priorities of logging messages using the logMsg() interface.
PAGE 560
A Summary of Commands logDstPri After changing the rules file, it is recommended that the rules be checked before they are put into service. The -c flag causes logDstPri to read the rules file and report any rules that are misformatted or not understood. The return value from logDstPri is the number of errors detected. To see the error complaints and install the rules all at once, specify the -v flag. This causes the verbose complaints to be generated. The -c flag implies the -v flag.
PAGE 561
A Summary of Commands logEvent/logMsg Shared Memory Segment The shared memory segment is keyed off the inode of the rules file and the define symbol LDP_KEY, defined in log/head/logDstPri.h. The library routine ftok({file},LDP_KEY) is used to generate the shared memory key. See Also logCat logMsg logDstPri msgDst logEvent/logMsg The logEvent/logMsg command allows shell scripts to log a specific message. Synopsis logEvent [script] [msg] [dst] [pri] [srcFile] [srcLine] ...
PAGE 562
A Summary of Commands logEvent/logMsg generates messages within the logging system, but which always uses SYSMSG as the message format for the messages it generates. The logEvent command emulates the logEvent( ) library routine, while the logMsg command emulates the logMsg( ) library routine. The logEvent command requires a destination and a priority when it is called. Messages logged via this interface are explicitly logged to the specified destinations and at the specific priority.
PAGE 563
A Summary of Commands logEvent/logMsg Table 33 defines the command line arguments. Table 33. Argument Descriptions for logEvent/logMsg script Name of the shell script for which the message is being logged. Normally, this is either basename$0 or in ksh ${##*/} msg The symbolic name of the message, for example, LG_OUT_OF_RANGE dst This is only used with the logEvent command. It is the bit mask specification of where the message will be sent.
PAGE 564
A Summary of Commands logEvent/logMsg Table 33. Argument Descriptions for logEvent/logMsg srcLine The line within the file from which the logEvent or logMsg command is being issued. If you do not care, you can use “-.” You might use $LINENO from the ksh environment, which is the line with the script or within a function. arg1 For each argument required by a specific message format, one and only one argument is required. Neither too many or not enough is acceptable.
PAGE 565
A Summary of Commands logFmt logFmt The logFmt command displays and changes the parameters used to display messages and explanation texts, specifically the messages mnemonics and screen width. Synopsis logFmt [global] {display|interactive|{opt}={value}} Description Each logging message has a class name and a mnemonic name associated with it. A class name, for example ICK001, is the combination of the name of the class, for example, ICK, and the index of the message within the class, for example, 001.
PAGE 566
A Summary of Commands logFmt Table 34 defines the logFmt command line arguments. Table 34. Argument Descriptions for logFmt Argument Description global This modifier causes the action specified to operate on the “global” (system-wide) parameters that control the behavior of display message. You must be root if you want to change the global parameters. You can examine the global parameters without being root. display This verb causes logFmt to display the current parameters.
PAGE 567
A Summary of Commands logFmt Table 34. Argument Descriptions for logFmt mnenonics=enable This option causes mnemonics to be displayed when logging messages are examined with display messages. mnemonics=disable This option causes mnemonics not to be displayed when logging messages are examined with display messages. width=NN This option causes the screen width to be set to NN, where NN is between 40 and 199 columns. The default setting is 75.
PAGE 568
A Summary of Commands logFmt Examples The following example enables the mnemonics. This affects only you and overrides the system-wide setting. logFmt mnemonics=enable The following example sets the system-wide default so that mnemonics are not displayed. Any user who wants to see mnemonics has to personally enable them. You need to be root to execute this command. logFmt global mnemonics=disable The following example displays the system-wide settings for mnemonics and screen width.
PAGE 569
A Summary of Commands mkAlerter mkAlerter The mkAlerter command reads an alerter description and generates C or C++ code that implements the description. Synopsis mkAlerter [-M] [-o {executable}] [-p {templ-path}] [-t [-f]] [-q] [-v] [-l] [X=Y...] [{alerterfile}.A...] Description The mkAlerter command is a program that reads an alerter description and translates it, with the help of code template files, into compilable C or C++ code. It also produces a make file for compiling the code.
PAGE 570
A Summary of Commands mkAlerter pieces, one containing main () and the other containing everything else. The source file containing main () ends in “Main.c” with truncation as necessary. Once produced, this file, like the make file, is be overwritten. If you want to produce your own initialization, you can use the -M option and then make your changes to the “*Main.c” file.
PAGE 571
A Summary of Commands mkAlerter The following is a current list of template files and their contents: AlertInc.t Description of include files. AlertCopyR.t Copyright notice. AlertHead.t Template of the header file. AlertMain.t Description of main () function. Alerter.t Primary template describing the alerter program. AlertTest.t Description of the code to respond to timeouts for alerting. AlertMsg.t Template describing a subroutine to process messages for a particular logging destination.
PAGE 572
A Summary of Commands mkheader Normally mkAlerter produces #line directives, which are used by the C compiler to report where errors are detected during compilation. While these are good during the compiling phase, they mislead most debuggers and make debugging difficult. The -l option suppresses the #line directives and is recommended when the debugging phase includes the use of a process debugger, such as sdb or pi.
PAGE 573
A Summary of Commands mkheader Description The mkheader program creates an address in user memory for each script variable. This information is stored in an application-name def.h header file and is used in naming both the output file and the allocation program. The joint usage of the same header file enables the script to interact with the transaction state machine (TSM). The -e option specifies exact string matches.
PAGE 574
A Summary of Commands • mkheader It prompts the operator to enter header files that are needed to make the files covered in the third section compile. They should be named in the order of dependence. For example, if information in the header file b.h is needed by the header file a.h, header file b.h must be entered first and then header file a.h. Full pathnames must be given. The file mesg.h and the structure mbhdr are common to all scripts and are entered automatically.
PAGE 575
A Summary of Commands mkheader As a shortcut, the input for the three prompts may be stored in another file (data file) and read in each time. For example: mkheader application_name < data file Once the header files are entered, mkheader writes a program called application_name_aloc.c to allocate the rest of user memory. The resulting source code is automatically compiled, using mkheader.a library functions, and then executed. This adds the remaining structure definitions to the application_name def.
PAGE 576
A Summary of Commands mkheader console input: mkheader FIRST PROMPT: Type in the variables you need space for according to the following format: type name [length] Example 1: int yn Example 2: char dg 20 (End input with CTRL-D) Variable?: char dg 20 Variable?: int yn Variable?: short cid Variable?: int iom Variable?: (CTRL-D) SECOND PROMPT: Please enter any dependency files that the header files in the next section will need in order to compile. Use full path names.
PAGE 577
A Summary of Commands mkheader Header file?: /att/msgipc/tsmdipappl.h Structures or all?: dowj Header file?: (CTRL-D) Compiling: application-name aloc.c Running: application-name aloc Output is called: application-name def.h This is the final application_namedef.h file produced by this example.
PAGE 578
A Summary of Commands mkheader In this second example, the command line includes a data file from which the system gets the information usually entered by the users in response to system prompts. The data file, called “data” in this example, contains the following information: char name 20 int answer short reply ^D /att/include/shmemtab.h ^D /att/msgipc/cdata.
PAGE 579
A Summary of Commands mkheader Variable?: Variable?: Variable?: Variable?: Please enter any dependency files that the header files in the next section will need in order to compile. Use full path names. (End input with CTRL-D) File name?: File name?: Enter the header file names and structure names needed to create the def.h file. Use full path names. (End input with CTRL-D) Header file?: List of structures or all?:Header file?: Compiling /usr/has/another/test6_aloc.
PAGE 580
A Summary of Commands mkheader /******* DAY_PNTR STRUCTURE *******/ #define DAY_PNTR 26 #define FILE_FIRST 26 #define REC_FIRST 28 #define FILE_LAST 30 #define REC_LAST 32 #define SZDAY_PNTR 8 /******* CDATA STRUCTURE *******/ #define CDATA 34 #define SCRIPT 34 #define CHAN 50 #define EQUIP 52 #define STARTTIME 54 #define STOPTIME 58 #define EV0 62 #define EV1 66 #define EV2 70 #define EV3 74 -: -: -: #define EV96446 #define EV97450 #define EV98454 UCS 1000 R4.
PAGE 581
A Summary of Commands mkimage #define EV99458 #define SZCDATA428 Note: Make sure that all variable names are unique without respect to case because lowercase letters are changed to uppercase for the final output. mkimage The mkimage command performs a complete system backup of all the contents of the root disk file system. Note: Mkimage performs only complete backups. The option to perform a partial backup of the root disk file system is no longer available.
PAGE 582
A Summary of Commands mkimage When specifying the mkimage command, the voice system requests that the system be placed into single-user mode. The mkimage command aborts if you do not give the system permission. Once in single-user mode, you must log in again and reexecute the mkimage command to continue the mkimage process.
PAGE 583
A Summary of Commands mkimage actually written to the tape. $DIFFOUT contains the difference between these two files. Analysis of these files may help in understanding the nature of the failure. Also, be sure you are using the supported cartridge type and that your tape drive is being cleaned regularly. Execute the -init 6- command to return to multiuser mode. The mkimage command then returns the voice system to multiuser mode by rebooting.
PAGE 584
A Summary of Commands newscript Example The following example backs up the root and usr file system to cartridge tape: mkimage newscript The newscript command updates the changes to all currently assigned scripts. Synopsis newscript Description The newscript command notifies the TSM and CDH processes that an existing script in the /vs/trans directory has been changed. After newscript is run, TSM reloads all scripts from disk the next time it is run instead of using a copy in the system memory.
PAGE 585
A Summary of Commands pkgadd Example The following example notifies the TSM and CDH processes that an existing application in the directory /vs/trans has changed. newscript pkgadd The pkgadd command transfers a software package to the voice system. Synopsis pkgadd [ -n ] [ -a admin ] [ -d device ] [ -R rootpath ] [ -r response ] [ pkginst1 [ pkginst2 ] ...] pkgadd -s spool [ -d device ] [ pkginst1 [ pkginst2 ] ...
PAGE 586
A Summary of Commands pkgadd The pkgadd command has the following parameters: Note: When executed without options, pkgadd uses /var/spool/pkg (the default spool directory). When transferring a package to a spool directory, the -r, -n, and -a options cannot be used. • -a — Define an installation administration file, admin, to be used in place of the default administration file. The token none overrides the use of any admin file, and thus forces interaction with the user.
PAGE 587
A Summary of Commands • pkgadd -r — Identify a file or directory that contains output from a previous pkgask session. This file supplies the interaction responses that would be requested by the package in interactive mode. Response must be a full path name. Note: The -r option can be used to indicate a directory name as well as a filename. The directory can contain numerous response files, each sharing the name of the package with which it should be associated.
PAGE 588
A Summary of Commands pkginfo See also pkginfo pkgrm pkginfo The pkginfo command displays software package information. Synopsis pkginfo [ -q | -x | -l ] [ -p | -i ] [ -r ] [ -a arch] [ -v version ] [ -c category1, [ category2 [ , ... ]]] [ pkginst [ , pkginst [ , ... ]]] pkginfo [ -d device ] [ -R rootpath ] [ -q | -x | -l ] [ -a arch ] [ -v version ] [ -c category1 , [ category2 [ , ... ]]] [ pkginst [ , pkginst [ , ...
PAGE 589
A Summary of Commands pkginfo Without options, pkginfo lists the primary category, package instance, and the names of all completely installed and partially installed packages. It displays one line for each package selected. The parameters for the pkginfo command are: Note: The -p and -i options are meaningless if used in conjunction with the -d option. The options -q, -x, and -l are mutually exclusive. • -a — Specify the architecture of the package as arch.
PAGE 590
A Summary of Commands pkginfo • pkginst — Specify the package instance or list of instances to be installed. The token all may be used to refer to all packages available on the source medium. The format pkginst.* can be used to indicate all instances of a package. • -q — Do not list any information. Used from a program to check whether or not a package has been installed. • -r — List the installation base for relocatable packages.
PAGE 591
A Summary of Commands pkgrm pkgrm The pkgrm command removes a software package from the voice system. Synopsis pkgrm [ -n ] [ -R root dir ] [ -a admin ] [ pkginst1 [ pkginst2 ] ...] pkgrm -s spool [ pkginst ] Description pkgrm removes a previously installed or partially installed package from the system. A check is made to determine if any other packages depend on the one being removed. If a dependency exists, the action taken is defined in the admin file.
PAGE 592
A Summary of Commands pkgrm Options The pkgrm command has the following parameters: • -n — Noninteractive mode. If there is a need for interaction, the command exits. Using this option requires that at least one package instance be named when the command is invoked. • -R — Define the full path name of a subdirectory to use as the root path. All files, including package system information files, are relocated to a directory tree starting in the specified root path.
PAGE 593
A Summary of Commands reinitLog reinitLog The reinitlog command is the control program and is used to inform logdaemon that a new config file is to be used. Synopsis reinitLog Description The reinitlog command is used during the procedure of creating a new logger message destination. It sends a message to the logdaemon that informs it that a new config file is to be used. The reinitlog command causes the logdaemon to reread the configuration file and reopen the various logging files.
PAGE 594
A Summary of Commands remove remove The remove command places a unit in the manual-out-of-service state. Synopsis remove [-i] [-n] rem [-i] [-n] Description The remove command is used to remove a unit from service when its temporary state is idle. It changes the permanent state of the unit to manualout-of-service (MANOOS). It does not remove a unit that has a temporary state of busy.
PAGE 595
A Summary of Commands remove • -n — Disables prompting from the system whether to wait until a conflict is resolved (see the -i option below) or to terminate the request to remove. • -i — Enables secondary command registration. If T1 diagnostics are being run, this option allows the removal of another card. If -i is used and another maintenance command is being run (remove, detach, attach, restore, diagnose), the request to remove card is blocked and a message is printed to the screen.
PAGE 596
A Summary of Commands remove • immed — Removes a card or channel even if it is in use. Active calls are likely to be dropped when this option is specified. This option is necessary when the card or channel must be removed from service as soon as possible, and you are willing to terminate any active calls. You may also want to use this option to get control of a channel that is hung and not providing useful service. • min_delay — Used to avoid waiting for channels to be granted.
PAGE 597
A Summary of Commands remove To delete out of the command, press D ELE TE . If this does not stop the command, you may need to press C ON TR OL and backslash simultaneously. If, while running remove, you want to abort the command, a message similar to the following may appear: At the user’s request, administration of the following cmd(s) has been interrupted. CARD NUMBERS: To assure proper operation of the identified card(s), run diagnostics at the earliest opportunity.
PAGE 598
A Summary of Commands restore See Also attach detach restore restore The restore command restores a unit to the in-service state. Synopsis restore [-i] [-n] Description The restore command is used to change the permanent state of a unit from manual-out-of-service (MANOOS) to in service (INSERV). The specified unit is placed in the INSERV state unconditionally, unless its current state is not MANOOS. The parameters for the restore command are: • • — Identifies the unit.
PAGE 599
A Summary of Commands restore a port of card#. If port# is not given, all ports of the card specified are restored. If no card number or channel number is given, the system displays a syntax message. • -n — Disables prompting from the system, whether to wait until a conflict has been resolved (see the -i option below) or to terminate the request to restore. • -i — Enables secondary command registration. If T1 diagnostics are being run, this option allows “restoring” of another card to be performed.
PAGE 600
A Summary of Commands restore T1 diagnostics are executing online tests and a conflict is detected, the restore command is blocked. If T1 diagnostics are executing offline tests and a conflict is detected, the user is asked whether to wait until the conflict is resolved or to terminate the request to restore. To delete out of the command, press D ELE TE . If this does not stop the command, you may need to press C ON TR O L and backslash simultaneously.
PAGE 601
A Summary of Commands retireAlarms The following example restores all cards to service. restore card all See Also attach detach remove retireAlarms Syntax retireAlarms [-t] [-u user] [-r reason] ["selector" ... | ALL] Description Variables include: • -t — Add alarm times to the display in interactive mode. • -u user — Mark the alarms as retired by user. The default is $LOGNAME. • -r reason — Reason alarms are being retired. UCS 1000 R4.
PAGE 602
A Summary of Commands retireAlarms • selector — Generally a regular expression identifying the alarms to be retired, though it can also be index numbers. • ALL — Retire all currently active alarms. Normally, retireAlarms operates in an interactive mode. If started with no arguments, it displays the currently active alarms and allows the user to select those to be retired. Selection can be by index number or by use of a matching pattern.
PAGE 603
A Summary of Commands rmdb rmdb The rmdb command displays the state of the resource manager (RM) and modifies the debug levels. Synopsis rmdb [-l] [-s] [-u] [-d [] ] [-g [] ] [-f [] ] [-p [] ] [-C [] ] [-T [] ] [-P [] ] [-i [] ] [-tL [] ] [-tA [] ] [-tc ] [-tC ] Description The rmdb displays the state of the resource manager and modifies the debug levels.
PAGE 604
A Summary of Commands Table 35. rmdb Argument Description for rmdb Variable Definition -l Takes the rmLOCK while sampling data structures. This ensures that the sample is internally consistent. However, if the RM data structures are left in a locked state, this causes the rmdb to block until they are unlocked. (Leaving the rm data structures locked is a system fault). Also, other processes that attempt to use the RM data structures are temporarily blocked until rmdb completes its query.
PAGE 605
A Summary of Commands Table 35. rmdb Argument Description for rmdb Variable Definition -T Prints out the channel touchtone queues (by channel number). -P Prints out channel profiles (by channel number). -i Repeats the display, with a sleep interval of the specified number of seconds between samples. 2 of 2 The -tL sets the trace level mask. Supported masks are shown in Table 36. Table 36.
PAGE 606
A Summary of Commands rmdb Table 37. Rmdb Trace Area Mask Mask Value RM_TA_TIMER 0x1 RM_TA_RESOURCE 0x2 RM_TA_INPUT 0x4 RM_TA_PROFILE 0x8 RM_TA_MTC 0x10 RM_TA_MSG 0x20 RM_TA_INTERNAL 0x40 The -tc sets the trace channel low end. The -tC sets the trace channel high end. UCS 1000 R4.
PAGE 607
A Summary of Commands show_sys show_sys The show_sys command allows you to retrieve configuration and administration information from customer sites.
PAGE 608
A Summary of Commands • Oracle database tables • Directory files in /oracle/dbs • Cron information for root • Local and remote database information • ASP driver (speech card) version • DNIS information (if T1s are present) • T1 card information (if T1s are present) • Device Information • SAR Snapshot • Parallel Printer Information • UUCP information • Devices file • Permissions file • Systems file • Installed cards • Parameter file(s) for assigned applications • Databases u
PAGE 609
A Summary of Commands soft_disc • CCA report for the previous week • Call data report for a specific day of the previous week • Traffic report for a specific day of the previous week The -l option prints details about each of the information that can be retrieved with the show_sys command. Example show_sys soft_disc The soft_disc command sends a disconnect to a script on a channel or channels.
PAGE 610
A Summary of Commands soft_disc channelEnd> be sent interrupt messages. If no script is running on the channel or if TSM does not own the channel, no action is taken for the channel. The soft_disc command waits for a response from TSM. When it exits, TSM has acted on all the requests for all the channels by sending disconnects to the scripts or rejecting the requests. Scripts running on the channel receive the ESOFTDISC event. Return Values If the soft_disc is successful, a 0 value is returned.
PAGE 611
A Summary of Commands soft_szr See Also dip_int soft_szr The soft_szr command starts a script on a channel. Synopsis soft_szr