HP 3000 Manuals HP 3000 Manuals
Examining Potential Problems
Examine potential problems to plan necessary revisions and modifications
to code.
The Potential Migration Problems Checklist below will help you identify
these problems.
Potential Migration Problems Checklist
Check each program by answering the questions below.
1. Does the program access intrinsic definitions in a file other than
the default file SYSINTR.PUB.SYS?
2. Does the program call external routines written in other
languages?
3. Does the program contain ANYPARM calls as described in appendix G
of the HP Business BASIC/XL Reference Manual?
4. Does the program use real data types in data files shared by
programs that execute in compatibility mode?
5. Does the program use a TurboIMAGE database?
6. Does the program use floating-point real data types?
If you answered "no" to all the above questions, your program should run
without any source file changes.
If you answered "yes" to any of the above, take the following actions.
Each action corresponds numerically to one of the preceding questions.
1. Port the intrinsic file. You will need to rebuild it in the HP
Pascal/XL compiler using BUILDINT. MPE XL provides switch stubs
that allow native mode programs to access compatibility mode
intrinsics. You need to create either switch stubs or ports to
native mode for the routines in the intrinsic file. Switch stubs
are necessary if the SPL routines either cannot be ported or are
shared by programs that you want to run in compatibility mode.
Refer to the Switch Programming Guide part number 32650-90014 for
more information about the switch subsystem and programmatic
access through switch stubs.
2. Examine the interfaces to routines written in other languages for
compatibility problems caused by data alignment changes. Set up a
native mode program to call procedures that are in a Compatibility
Mode segmented library (SL) by using switch intrinsics if you
cannot port the external routines or if compatibility mode
programs share the external routines. Refer to the Switch
Programming Guide part number 32650-90014 for more information
about the switch subsystem and programmatic access through switch
stubs.
3. Rewrite the externals for these ANYPARM calls. The formal
parameters have been changed from two bytes to four bytes. The
fields in the actual parameter table have changed in these ways:
a. The address of the parameter has been expanded from a 16-bit
address to a 32-bit address.
b. Each type and dimension field for each parameter has been
expanded from one byte to two bytes.
4. Examine the source program to make sure that there will not be
overflow or underflow problems during real change between IEEE and
MPE V real format. See chapter 7, "Accessing Compatibility Mode
Data Files."
5. Make changes to your source code if real data types are used in
databases. Also, change your source code if your program depends
on information returned in word 5-10 of the status array. See
chapter 5,"Migrating TurboIMAGE/V Databases," in this manual for
detailed information.
6. Examine your source code carefully to make sure that the
differences in the real ranges and digits of accuracy will not
cause problems.