Table 2-2. Backup Header: Feature Module Identification Number - AT&T MERLIN LEGEND Release 2.0 System Programming Manual

Programming with SPM
Approximately 59 of these bytes are currently used. Bytes 55 through 59 of the
header contain the feature module identification number, as shown in Table 2-2.
(Release 1.0 and early versions of Release 1.1 do not contain this information in
readable form. )

Table 2-2. Backup Header: Feature Module Identification Number

Size
Examples
The release number is found in the first 2 bytes of the feature module
identification number (0200 = 2.0, 0101 = 1.1).
If the backup file is compressed, you can still 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 on a UNIX system.
Note that the feature module release number, not the version number of SPM,
determines whether the backup file is compressed or uncompressed.
Release 1.0 backups are uncompressed. Release 1.1 and 2.0 backups are
compressed. Uncompressed files take longer to restore.
Before you begin a backup procedure, note the following:
The communications system does not have to be idle during backup;
however, station 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.
If you plan to store your backup file on a diskette, be prepared with a
DOS-formatted diskette. (DOS formatting can be done on a UNIX
system PC or a DOS PC.)
Uncompressed backup files are 100,000 — 210,000 kbytes in size;
compressed files are about 70,000 — 85,000 kbytes.
Maintenance data (error logs and other data used by qualified service
technicians) is not saved in the backup file.
2-14
Using SPM
Release No. Build No.
2 bytes 1 byte
02 00 3 2
01 01
Mode
System Size
1 byte 1 byte
01 — Key
01
02 — Behind Switch
0 3 — Hybrid/PBX