SQL/MP to SQL/MX Database and Application Migration Guide

Converting SQL/MP Applications to SQL/MX
Applications
HP NonStop SQL/MP to NonStop SQL/MX Database and Application Migration Guide—666211-001
4-57
Managing Modules of Embedded SQL/MX
Applications
For more information about similarity checks and automatic recompilation in NonStop
SQL/MX, see the
SQL/MX Programming Manual for C and COBOL.
Managing Modules of Embedded SQL/MX Applications
In NonStop SQL/MP, the SQL compiler, SQLCOMP, stores SQL object code and query
execution plans in the SQL program file. In NonStop SQL/MX, the SQL/MX compiler,
MXCMP, stores SQL object code and query execution plans in module files, which
exist separately from the program executable files. The module files are stored by
default in the OSS directory
/usr/tandem/sqlmx/USERMODULES. You can also co-
locate module files in the same OSS directory as the program executable. For more
Attributes:
ALLOCATE
AUDITCOMPRESS
BUFFERED
CLEARONPURGE
EXTENT (primary and secondary)
LOCKLENGTH
MAXEXTENTS
NOPURGEUNTIL
OWNER
SECURE
SERIALWRITES
TABLECODE
VERIFIEDWRITES
Yes Yes
Statistics on the table Yes Yes
Column headings Yes Yes
Catalog where table is registered Yes Yes, could be in
different schema
Number of columns—more columns at run time than
at compile time
Yes but with the
same attributes
and no SELECT
*
No
View definition different at run time than at compile
time when selecting a view
No for shorthand
views
Yes for qualified
protection views
No (ANSI views
are equivalent to
shorthand views)
N.A. for
protection views
Table 4-15. Comparison of Similarity Checks Between NonStop SQL/MP and
NonStop SQL/MX (page2of2)
Difference Between Compile Time and Run Time
Similarity check
passes in
NonStop
SQL/MP?
Similarity check
passes in
NonStop
SQL/MX?