Guardian Application Conversion Guide

Appendix D Considerations for Migrating
Any Application
096047 Tandem Computers Incorporated D–1
This appendix provides information about processing changes that may require minor
conversion of your application even if you do not intend to take advantage of the
D-series extensions. Without these modifications, your C-series application might:
Fail to run on a D-series system
Produce erroneous or unexpected results when run on a D-series system
Potential Application
Problems
Potential application problems on a D-series system can be caused by:
Using undocumented procedures
Relying on undocumented side effects of documented procedures
Undocumented Procedures Some undocumented C-series procedures are not supported on D-series systems. The
following table lists some of the most commonly used undocumented procedures.
Undocumented Procedure Documented Procedure Replacement
BULKREAD, BULKWRITE, BULKAWAITIO READX, WRITEX, AWAITIOX
(with SETMODE 141 for transfers of up to 56 KB)
GETPEEKXGLOBAL PROCESS_GETINFOLIST_
SETDATAFREELIST or SETINDEXFREELIST None. These procedures apply only to DP1 files. DP1
cannot exist in a D-series system
To ensure that your C-series application runs successfully on a D-series system,
modify your application to eliminate the use of undocumented procedures.
Undocumented Side
Effects of Documented
Procedures
If your application relies on undocumented side effects of documented procedures, it
might function differently on your D-series system than it did on your C-series system.
To ensure that your C-series application runs successfully on a D-series system,
modify your application to eliminate the use of undocumented side effects.
Other Potential Application
Problems
Other potential application problems are summarized in table D-1 and described in
detail in subsequent subsections.