Upgrading the System
Inter-Release Compatibility
It is important to understand compatibility between files created on each of the
different versions of SPM, not only for upgrading but also for programming.
Table 2-6 summarizes programming compatibility. (It is assumed that the
majority of the programming is done in surrogate mode and backed up on disk).
Table 2-6. Programming Compatibility
SPM
Version
1.13
1.16
2.09
2.16
3.XX
1.16
2.09
2.16
3.XX
2.09
2.16
3.XX
2.16
3.XX
3.XX
* The backup file must be converted before it is restored
NOTE:
The default barrier code and any programmed barrier codes will be carried over
to Release 3.0 with no change and the barrier code length will be four (4). It is
the responsibility of the system manager to change the barrier code length and
the barrier codes if so desired.
Program
Backup on
1.0
1.0
yes
1.0
yes
1.0
yes
1.0
yes
1.0
yes
no
1.1
no
1.1
1.1
no
no
1.1
2.0
no
2.0
no
no
2.0
2.1
no
no
2.1
3.0
no
Restore on
3.0
1.1
2.0/
2.1
no
no
no
no
no
yes
yes
yes*
no
no
yes
yes*
yes
yes*
yes*
no
yes
no
yes
yes*
no
no
yes
yes*
yes*
yes
yes*
no
yes
no
no
yes
no
no
yes
yes*
no
no
no
no
no
yes*
yes
no
no
Programming with SPM
2-49
Need help?
Do you have a question about the MERLIN LEGEND Release 3.0 and is the answer not in the manual?
Questions and answers