
NOTE:
The
UPD:BKOUT:UPNM;
message only restores the words specified in the change. If memory other than
that specified in this change is mutilated, a system BOOT may be required to restore the switching system
to normal.
5.5 SPACE RECLAMATION
5.5.1 RECLAIM SPACE IN SOFTWARE UPDATE STORAGE DIRECTORY /etc/bwm
As software updates are brought into /etc/bwm and activated, the space available in /etc/bwm for future software
update storage is gradually reduced. To avoid running out of space, the file space occupied by software updates
which have been made permanent should be cleared. Such space in /etc/bwm is cleared using the
UPD:CLR:BWM;
message. A listing of permanent updates should be obtained using the
UPD:DISPLAY:OFC;
message and compared to the contents of /etc/bwm using the
OP:STATUS:LISTDIR,DN="/etc/bwm";
message.
5.5.2 RECLAIM PATCH SPACE
Update functions are installed in patch space. After an update has been soaked and made permanent, the old
functions and decision functions are normally no longer needed. These should be removed from execution, and the
space reclaimed for use on future updates. After BWM 91-0105 and later software releases, the space reclamation
is performed automatically when the update is made permanent.
5.6 ERROR CONDITIONS
Tables 5-1 and 5-2 contain listings of possible error conditions that may be encountered during file transfer.
Should any error conditions arise during update activation that are not listed in the table, refer to the error condition
listing in 235-600-700,
Input Message Manual
, or 235-600-750,
Output Message Manual
for the particular message
in question.
Table 5-1
File Transfer Error Conditions (SCANS Interface)
CAUSE
EFFECT
ACTION TO BE TAKEN
Insufficient space for incoming file (Initial
size for directory /etc/bwm is 5 MB).
File transfer session terminated.
(1) Verify and install applicable software
updates received from SCANS-2.
(2) Clear directory /etc/bwm after
updates have been made
``permanent.''
(3) Enter second request for
remaining software updates.
Incoming file length exceeds maximum
file length permitted (2 MB max.).
File transfer continues with next file.
(1) Invalid software update. Contact
ESAC and PECC.
File with identical pathname already
exists.
File transfer continues with next file.
(1) Verify all software updates at
completion of session.
(2) Clear those software updates in
which verification was unsuccessful.
(3) Enter second request for any
remaining software updates.
Incoming file interrupted by sending
process.
File transfer session will be terminated if
three consecutive files are interrupted.
(1) Enter second request for affected
software updates.
(2) If problem persists, contact field
update administrator.
Sending process is unable to continue
File transfer session terminated.
(1) Verify and install applicable software
235-105-210
October 1999
Copyright © 1999
Page 9
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 ...