SQL/MP Installation and Management Guide

Managing Database Applications
HP NonStop SQL/MP Installation and Management Guide—523353-004
10-29
Planning for TS/MP Requirements
Planning for TS/MP Requirements
Transaction processing applications can access both SQL and Enscribe databases. To
access an SQL database, the servers must use embedded SQL statements coded in
host language programs such as COBOL, C, or Pascal. To access an Enscribe
database, servers use languages, such as COBOL, FORTRAN, C, or Pascal, or TAL
statements, with calls to Enscribe I/O procedures. A single server can access both an
SQL database and an Enscribe database with the appropriate database statement for
each type of table or file access.
To access either an SQL or Enscribe database from a TMF environment, programs can
use logical names with the actual file names specified at compile or run time. To use
logical names for an SQL database, use SET SERVER DEFINE commands coded in
the PATHMON configuration file. To use logical names for Enscribe files, use SET
SERVER DEFINE or SET SERVER ASSIGN commands in the PATHMON
configuration file. Servers can use hard-coded names (table or view names for SQL or
file names for Enscribe) to access either database.
When you are running HP NonStop TS/MP, make sure that the security of the SQL
objects allows the user ID running TS/MP to access the same tables and views that the
servers use.
If you want to log SQL compilations and automatic recompilations for your application
environment, you must add the =_SQL_CMP_EVENT DEFINE mapped to a disk file.
The disk file must be accessible by the user ID under which the applications are
running. Recompilations are automatically logged to $0 unless you either turn logging
off or designate a different device with a DEFINE. For more information on logging, see
Monitoring Compilations on page 10-5.
Planning for Pathmaker Requirements
Three column attributes are particularly useful for applications generated by the
Pathmaker application development tool. These are the HEADING, HELP TEXT, and
UPSHIFT attributes. If these attributes are assigned when the columns are defined, the
Pathmaker tool automatically incorporates their use in the DB requesters.
•
The HEADING attribute assigns an alternate heading for the column. If no heading
is assigned, however, the Pathmaker tool uses the column name as the default
heading.
•
The HELP TEXT attribute associates help text, which is stored in the COMMENTS
table, with the column. When building an application, the Pathmaker tool retrieves
the help text from COMMENTS and inserts the text into its HELP facility.
•
The UPSHIFT attribute signifies that the data will automatically be upshifted before
storage in the column. UPSHIFT is supported for single-byte character data types
only.
For additional information about how the Pathmaker tool uses these column attributes,
see the Pathmaker Reference Manual and the Pathmaker Programming Guide.