" interval and yield the expected results.
"
" Run a call volume with PROCALL and observe that there are no power
" ring failures.
"
"
"BKOUT.********************************************************************"
"
" If during the installation of this BWM, or at any time
" during the SOAK period, you feel that the applied updates
" should be backed out of the system, enter the following
" command(s):
"
UPD:BKOUT:UPNM:BWM81-1241!
"
"OFFICIAL.*****************************************************************"
"
" To make the updates applied in this BWM official, wait the
" prescribed SOAK interval and then enter sequentially the
" following command(s).
"
UPD:UPNM BWM81-0241;OFC!
"
"END BWM81-0241
Figure 5-3 Example of a Message File
5.3.3 SCCS AND MASTER CONTROL CENTER INTERFACE
The software updates are normally activated remotely by the SCCS. Communication between the SCCS and the
program update subsystem is over the maintenance channel. The local office can be unattended.
Software updates may also be activated locally at the master control center (MCC) video terminal. If the software
updates are to be requested from SCANS by the local office, a 1200-baud terminal [other than the maintenance
cathode ray terminal (MCRT)] must be present. The terminal must be full duplex, capable of printing at least 80
characters per line and must have a 212A-type data set. If the software updates are to be loaded into the switch
from a tape, the 1200-baud terminal is not needed.
5.3.4 GENERAL FORMAT FOR ACTIVATION OF SOFTWARE UPDATES RECEIVED FROM SCANS
5.3.4.1 Reception from SCANS
To receive software updates, first a dial-up link must be established with SCANS. When the dial-up link is
completed, the proper login, password, and subpassword are used to gain access to the SCANS data base. When
access is obtained, a listing is requested of all items from SCANS. This listing is reviewed, and all applicable
software updates are stored.
The office storage space required for each software update binary data package is provided in the software change
size section of the software update. Prior to data transmission, it must be determined that sufficient file space is
available in the directory on disk where the software updates are to be stored. If file space is insufficient, memory
audit and space reclamation techniques are used to create space, or the software updates are requested in stages
(one or two at a time) as space allows. When enough file space is available, the office is primed for binary data
package delivery by using the
IN:REMOTE:START;
message. During priming, file space is reserved and a
transaction identifier (ID) is established. This transaction ID provides additional security at the application level in the
file transfer process.
235-105-210
October 1999
Copyright © 1999
Page 5
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...