
temporary disk file is thrown away, and the system boots from the official file, effectively backing out the update(s).
When a temporary update is made permanent, an updated version of the file is built in the same directory as the
original version. A windowless move then takes place to effectively make the new version official. The in-core
memory is not touched when an update is made official since the update has already been installed there.
The software updates can also be activated by maintenance personnel at the SCCS or MCC by printing the
message file of the applicable software updates and manually installing the required messages.
5.3.4.5 Backout
During the soak interval, the temporary software update is observed to ensure proper performance. If the software
update does not perform properly at any time during the soak interval, it should be backed out using the
UPD:EXEC:CMD:BKOUT;
message. The BACKOUT section backs out the designated change, plus any
subsequently installed temporary changes; that is, the backout process can only delete changes in the exact reverse
order of application. A sequential list of changes that are in the temporary state may be obtained using the
UPD:DISPLAY;TEMP;
message.
5.4 EMERGENCY FIX
5.4.1 GENERAL
Regular program updates are performed in a timely and orderly fashion through software updates. Unexpected
problems with the software release can occur that require immediate correction, not allowing time for the normal
software update development and issue processes. These immediate corrections are known as emergency fixes.
Emergency fixes are accomplished on a word-by-word basis under the direction of Lucent Technologies Customer
Technical Support (CTS) [formerly Product Engineering Control Center (PECC)].
Emergency fixes are assigned a sequential craft number similar to the software update number. The program
update subsystem provides emergency fixes with the same status and processes as software updates (that is,
make temporary, backout, make permanent). Emergency fixes specify the address to be changed, the new data to
be inserted, and the old data to be matched. Emergency fixes are also known as address-data couplets.
5.4.2 SCCS AND MCC INTERFACE
As with software updates, most emergency fixes are activated remotely by the SCCS. Communication between the
SCCS and the program update subsystem is via the maintenance channel. The local office can be unattended
during the activation of the fix. Emergency fixes may also be activated locally through the MCC.
5.4.3 GENERAL FORMAT FOR EMERGENCY FIX ACTIVATION
5.4.3.1 Activation
The
LOAD:UPNM....;
message causes a temporary change to be made at the specified location. After a suitable
test and soak period, the
UPD:UPNM....;OFC;
message makes the change permanent, and normal backout
procedures can no longer be used.
5.4.3.2 Backout
Normal backout can be accomplished only while the fix is in a temporary state. The backout procedure can be
implemented using the
UPD:BKOUT:UPNM;
message. This message backs out the designated change, plus any
subsequently installed changes, because the backout process can only delete changes in the exact reverse order of
application. The
UPD:DISPLAY:TEMP;
message provides a sequential list of changes that are in a temporary state.
235-105-210
October 1999
Copyright © 1999
Page 8
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 ...