Lucent Technologies MERLIN LEGEND Release 7.0 System Programming Manual page 154

MERLIN LEGEND Communications System Release 7.0
System Programming 555-670-111
2 Programming with SPM
Using SPM
Determining the Release Number of a
Backup File
If you have a backup disk but do not know its release number, you may be able to
find this information in the backup header.
Beginning with later versions of Release 1.1, the backup file contains a backup
header 128 bytes long. Approximately 59 of these bytes are currently used. Bytes
55 through 59 of the header contain the MERLIN LEGEND Communication
System Release number, as shown in
of Release 1.1 do not contain this information in readable form.)
Table 2-4.
Size
Examples
The release number is found in the first two bytes (four characters) of the
identification number—for example, 0600 = 6.0, 0402 = 4.2.
If the backup file is compressed (Release 1.1 and later), you can read the header
but you cannot read the data area following the header. Use type [backup
filename] to read the header on a DOS system or cat [backup filename] to read
the header on a UNIX System.
Note that it is the communication system release number, not the version number
of SPM, that reflects whether the backup file is compressed or uncompressed.
Release 1.0 backups are uncompressed and Release 1.1 and later backups are
compressed. Uncompressed files take longer to restore.
Considerations
Review the following items before you begin the backup procedure:
The communications system does not have to be idle during backup;
however, extension programming is blocked.
Any objects that are in a maintenance-busy state are stored in that state.
When you restore system programming, these objects are busied out, even
if they have since been released from the maintenance-busy state.
Backup Header: Release Number
Release No. Build No.
2 bytes 12 bytes
06 00 32
04 02
2
Table 2-4. (Release 1.0 and early versions
System Size
1 byte
01
Issue 1
April 1999
2-28
Mode
1 byte
01 (Key)
02 (Behind Switch)
03 (Hybrid/PBX)
2