ATT System 25 Call Management System Manual

							Section 8: Archiving Data 
						

							Overview
Archiving is the process of copying historical data from the hard disk onto
floppy diskettes.You need to archive data when the hard disk begins to run
out of space and you want to save your old files. You should archive data
once a month to keep the system running efficiently.
This section discusses how to archive data and contains information about the
directories and files CMS uses. It includes procedures for copying the system
tables and historical data files to a floppy diskette using the MS-DOS copy
command, and for erasing these files from the hard disk using the MS-DOS
erase command. This section also tells you how to restore archived data to
the hard disk so that you can print historical reports.
TRANSFERRINGTo print historical reports from archived data, you need the system tables and
HISTORICAL DATA ONTOhistorical data files for the days in which you’re interested. The system tables
DISKETTESfile includes the information that identifies the lines, splits, and agents
contained in historical data that have been saved. Up to four historical data
files and one system tables file fit on a single 360K floppy diskette.
To clear space on the hard disk, you can simply erase your oldest files.
However, if you want to save the data for possible future use, you should
archive those files onto a floppy diskette first, and then erase them from the
hard disk. Copy the four oldest data files and the oldest system table to the
floppy diskette. After you verify that the files were copied, erase those files
from the hard disk.
If you archive files on a regular schedule, such as once a week, you can avoid
running out of space on the hard disk. Figure 8-1 shows the locations of the
directories and files CMS uses.
Overview 
8-1 
						

							Copying the System Tables File
To copy the system tables file, do as follows:
1 If you are in CMS, exit to MS-DOS by pressing [F8] (labeled Exit to DOS)
on the CMS Menu.
2 Access the cmsmgmt directory on the hard disk by typing
cd  cms  cmsmgmt
and pressing [Enter].
3 To copy the system tables file for the current date, type
copy c:systbls.cms a:syymmdd.cms
where yymmdd is the date, and press [Enter]. For example, to copy the
system tables file on 04/19/88, copy it to a file called s880419.cms.
If you copy the system tables file only when a change affecting line, agent,
or split assignments has been made, use the date the change became
effective. For instance, if the change was made Monday morning before
call management was started, use Monday’s date. If the change was
made after call management stopped on Monday, use Tuesday’s date.
Copying Historical Data Files
To copy the historical data files, do the following:
1 If you are in CMS, exit to MS-DOS by pressing [F8] (labeled Exit to DOS)
on the CMS Menu.
2 Access the cmsrept directory by typing
cd  cms  cmsrept
and pressing [Enter].
3 Type a series of commands in the form
copy c:dyymmdd.cms a:
where yymmdd is the date on which data were collected. Press [Enter]
after each command. For example, if you want the historical data file for
04/19/88, you would copy the file d880419.cms.
To copy 10 days’ data at a time, for instance, files from 07/20/88 through
07/29/88, type a command in this format:
copy c:d88072* .cms a:
then press [Enter].
Erasing Files from the Hard Disk
To erase the archived files from the hard disk, do as follows:
Type a series of commands in the form
erase c:dyymmdd.cms
where dyymmdd.cms is the name of the file to be erased. Press [Enter] after
each command.
8-2 Overview 
						

							GENERATING HISTOR-
ICAL REPORTSIf you have transferred old CMS data from the hard disk onto floppy
diskettes, you may later want a report or a complete set of reports for a
particular date. The procedures that follow explain how to copy the system
tables and data files for the date from the floppy diskette onto the hard disk,
so that you can then generate reports for that date.
Saving the Current System Tables
You have to save the current system tables file in a temporary file so that you
don’t lose it when you copy the historical system table file to the hard disk.
To save the current system tables file, do as follows:
1 If you are in CMS, exit to MS-DOS by pressing [F8] (labeled Exit to DOS)
on the CMS Menu.
2 Access the cmsmgmt directory on the hard disk by typing
cd  cms  cmsmgmt
and pressing [Enter].
3 To copy the current system tables file to a temporary file, type.
copy systbls.cms temp
then press [Enter].
This copies (and saves) the current system tables file to a file called “temp.”
(You can choose another name for the file if you want.) Remember to copy
the current system tables file back into systbls.cms in the cmsmgmt directory
before you have CMS begin managing calls again.
Copying the Historical System Tables to the Hard Disk
You should still be in the cmsmgmt directory. To copy the system tables files
for the date you want, type the following:
copy a:syymmdd.cms c:systbls.cms
where yymmdd is the date of the system tables file. Press [Enter].
Copying the Historical Data Files to the Hard Disk
You should still be in the cmsmgmt directory. To copy the historical data files
from the floppy disk to the hard disk, do as follows:
1
2
3Access the cmsrept directory by typing
cd   cms  cmsmpt
then press [Enter].
Type a series of commands in the form
copy a:dyymmdd.cms c:
where yymmdd is the date of the data you want. Press [Enter] after each
command.
When you’re finished copying data to the hard disk, type
cd  cms
then press [Enter].
Overview 8-3 
						

							Generating Reports
The system tables file and data for the date(s) you’re interested in should now
be in the correct locations on the hard disk. To generate the reports you
want, follow the instructions in “Generating CMS Reports” in Section 7.
RESTORING DATA
COLLECTION
CONDITIONSNow that you have the historical reports, you must restore the hard disk to
its previous condition. Otherwise, CMS cannot effectively store new data
when it resumes managing calls. To do this, erase the historical data from
the hard disk-data remains saved on the floppy diskette-and restore the
current system tables file to the proper file.
Erasing the Historical Data from the Hard Disk
To erase the historical data from the hard disk, do the following:
1 If you are in CMS, exit to MS-DOS by pressing [F8] (labeled Exit to DOS)
on the CMS Menu.
2 To access the cmsrept directory, type
cd  cms  cmsrept
then press [Enter].
3 To erase a data file, type
erase c:dyymmdd.cms
where yymmdd is the date of the data file to be erased. Then press
[Enter].
Restoring the Current System Tables File
To restore the current system tables file to its appropriate place in the cms
directory, do the following:
1 To access the cmsmgmt directory, type
cd  cms  cmsmgmt
and then press [Enter].
2 To restore the system tables file, type
copy temp systbls.cms
and press [Enter].
You should now have the historical reports you wanted, and CMS should be
ready to store new data.
8-4 Overview 
						

							Section 9: Troubleshooting 
						

							Overview
This section of the manual suggests corrective action for problems that may
occur with your CMS. It is organized as follows:
Startup Problems
Suggests corrective action for problems the CMS program detects during call
management startup.
Call Management Problems
Identifies problems that can cause CMS to stop managing calls and suggests
corrective action.
Voice Announcement Unit Problems
Suggests corrective action for problems that effect voice announcement units.
Printer Problems
Identifies and suggests corrective action for problems that can prevent you
from printing CMS screens and reports.
Agent problems
Anticipates and suggests solutions to problems you and your agents are most
likely to encounter as you begin to use CMS.
System Errors
Explains messages beginning SYSERR that may appear on your status screens
and/or Events Log screen during CMS operation.
Running CMS from a Floppy Diskette Backup
Tells you how to run CMS using the floppy diskette backups in the event that
the PC’s hard disk is damaged.
Managing Calls When CMS is Not Running
Tells you how to use your System 25 Direct Group Calling (DGC) Coverage
feature to manage calls until CMS is running again.
Overview 9-1 
						

							Startup Problems
The following pages identify and suggest corrective action for problems that
may occur when you start up CMS call management. The problems are
grouped as follows, according to the kind of message they cause to appear in
the information portion of the Initialization screen:


Use these pages to find the message that identifies your problem, and take
the corrective action(s) described.
Error Messages
Problems that generate error messages on the CMS Initialization screen always
bring the call management startup procedure to a halt. Until you have
corrected the problem, you have to manage incoming calls on CMS lines
according to the instructions in “Managing Calls When CMS is Not Running”
at the end of this section.
ERROR--NO Lines in CMS. Must ADMINISTER Lines/Groups.
Effect on Call Management: Until this problem is corrected, CMS cannot
manage calls.See “Managing Calls When CMS is Not Running“ at the end
of this section of the manual.
Possible CauseCorrective Action
You omitted one or1 From the Initialization screen, in
more steps when yousequence, press [F8] (labeled
administered your“Exit Call Mgt”), 
[F4] (labeled
CMS line groups.
min CMS, and [F2] (labeled
Lines/LineGps) to get the
Administer Line Groups screen.
2 Follow the instructions under the
heading “Administering CMS Lines
and Line Groups” in Section 4 to
administer line groups.
3 Make sure you have completed at
least one shift configuration as
described in “Building or Editing
Shift Configurations” in Section 4.
4 Restart call management from the
CMS Menu by pressing [F1]
(labeled “Start Call Mgt”).
9-2 Startup Problems 
						

							
Effect on Call Management: Until this problem is corrected, CMS cannot manage
calls. See “Managing Calls When CMS is Not Running” at the end of this
section.
Possible Cause
You omitted one or
more steps when you
built your shift
configurations.
Corrective Action
1 From the Initialization screen, in
sequence, press [F8] (labeled Exit
Call Mgt), 
[F4] (labeled “Admin
CMS”), and 
[F4] (labeled “Config
List”) to get to the Configuration
List screen.
2 Build at least one shift
configuration according to the
instructions in “Building or Editing
Shift Configurations” in Section 4
of this manual.
3 Restart call management from the
CMS Menu by pressing [F1]
(labeled “Start Call Mgt”).

Effect on Call Management: Until this problem is corrected, CMS cannot
manage calls. See “Managing Calls When CMS is Not Running” at the end
of this section of the manual.
Possible CauseCorrective Action
CMS was not
administered or was
administered
incorrectly.
1 From the Initialization screen, press
[F8] (labeled Exit Call Mgt); then
press 
[F4] (labeled Admin CMS)
to access the Administration Menu
screen.
2 Administer CMS according to the
instructions in Section 4 of this
manual.
Startup Problems 
9-3 
						

							
(X refers to PC jack CU1 or PC jack CU2).
Status Indicator: CU1 or CU2 (flashing)
Audible Signal: A beep from the CMS PC Interface Card.
Effect on Call Management: Until this problem is corrected, CMS cannot
manage calls.See “Managing Calls When CMS is Not Running” at the end
of this section.
Possible CauseCorrective Action
There’s a loose cableMake sure one end of the cable is
connection betweensecurely plugged into the CU1 (or
the CU1 and/or CU2CU2) jack at the back of the PC and
jack and the System 25the other end is securely plugged into
wall jack.the wall jack assigned to CU1 (or
CU2).
If this does not work, have the System
25 Administrator check the station
interconnect panel (SIP) connections to
the System 25 cabinet for CU1 and/or
CU2.
The cable is faulty.Try switching the two cables around
(unplug the cable from the CU1 jack
and plug it into CU2, and vice versa).
If the CU1 indicator on the screen
stops flashing and the CU2 indicator
goes on (or vice versa), you know the
problem is either a faulty cable or a
faulty System 25 component.
The System 25 ATLHave the System 25 Administrator
port(s) assigned to CU1check the ports on the ATL Line
and/or CU2 is faulty.Circuit Pack.
The wrong cable type
The cable must be a 4-pair modular
is being used.cable, D8W-87, the type of cable that
came with your CMS PC Interface
Card.
The CU1 and/or CU2If none of the previous actions corrects
jack on the CMS PCthe problem, contact your equipment
Interface Card is faulty.supplier for assistance.
9-4 Startup Problems