NonStop NS-Series Database Migration Guide

Preparing to Migrate to an Integrity NonStop
NS-Series System
HP Integrity NonStop NS-Series Database Migration Guide—540469-001
1-6
Assess the Current System’s Applications and
Database Environments
Application
programs
and source
code
•
Objects by quantity of type (for example, executable objects, build
objects, and SRLs)
•
How objects are stored and versioned
•
Scripts by quantity of type (for example, TACL, JSP, and ASP)
•
Location of all source code and related components used to build the
current application programs
•
Whether each program is native or CISC (accelerated), runnable as
high PIN or low PIN, runnable as a licensed program, and the type of
library used (for example, public SRL, private SRL, or DLL)
•
The language (for example C, C++, COBOL, Java, TAL, pTAL, or
FORTRAN) of each source code component
•
Whether each source code component uses SQL/MP statements or
SQL/MX statements. Also identify compilation directives, special
DEFINEs, the effects of CONTROL TABLE or CONTROL QUERY
DEFAULT statements, whether parallelism is on or off, use of
CONTROL QUERY SHAPE (NonStop SQL/MX only), and use of
indexes.
•
For each source code component, identify any occurrences of PRIV
codes, machine instructions or architecture-specific usage, I/O buffer
access before nowait I/O completion.
•
Source code using Guardian and OSS APIs that might need to be
changed. For more information, see the H-Series Application Migration
Guide.
•
Memory and structure usage for potential data alignment problems
•
Language-specific changes that might be required for C, C++, COBOL,
pTAL, and Java programs
Table 1-2. Assessing the Applications and Database on the Current
System (page 2 of 3)
For this
environment Obtain this information