SQL/MX Comparison Guide for SQL/MP Users

Comparing the Differences in the Products
HP NonStop SQL/MX Comparison Guide for SQL/MP Users—523735-003
1-3
Frequently Asked Questions About Differences
Yes, but DEFINEs for table naming are not necessary in NonStop SQL/MX.
DEFINES can be used only for SQL/MP objects referenced through the SQL/MX
application. SQL/MX objects cannot be referenced with DEFINES.
In addition, DEFINEs must be available to NonStop SQL/MX at run time, or you will
receive an error. NonStop SQL/MP does not have this requirement.
•
Does NonStop SQL/MX support similarity checking and execution-time name
resolution?
Yes. NonStop SQL/MX supports similarity checking and execution-time name
resolution with some limitations.
•
Does NonStop SQL/MX support Report Writer?
Yes. In addition, you can use third-party tools for reports. If you need assistance in
choosing a tool, contact your HP representative.
•
Can NonStop SQL/MX run under both the HP NonStop Kernel Open System
Services (OSS) and Guardian Services environments?
Many key SQL/MX processes run as OSS processes (as do HP NonStop Tuxedo,
HP NonStop DOM, and Java processes). Your applications can be run on
Guardian with an OSS pass-through command. See the SQL/MX Programming
Guide for C and COBOL for more information.
•
What benefits will NonStop SQL/MX provide for OLTP applications?
You can now build your OLTP application by using ANSI-standard SQL. This
feature allows you to leverage the expertise that your developers have gained in
working on other ANSI-standard databases and quickly transfer those skills to
SQL/MX development. It also allows you to build applications that can be ported
between DBMS systems with a minimum of change. Several new SQL/MX
features, including rowsets and compound statements, provide significant
performance improvements for OLTP applications. NonStop SQL/MX also supports
a publish and subscribe feature that supports transactional-based queuing.
•
Does TACL support NonStop SQL/MX?
Yes. TACL supports SQL/MX objects when the Guardian name of the object is
specified. TACL commands do not accept ANSI names as input and do not return
ANSI names in their output. These TACL commands support SQL/MX objects:
°
FILEINFO
°
FILENAMES
°
FILES
°
#FILEGETLOCKINFO
°
#FILEINFO
°
#FILENAMES
°
#LOCKINFO
°
#OPENINFO
°
#XFILEINFO