SQL/MP Programming Manual for C

HP NonStop SQL/MP Programming Manual for C—429847-008
7-1
7 Program Execution
This section describes the execution of a NonStop C program containing embedded
SQL statements and directives in the OSS environment. The section provides details
about the required access permissions, the TACL DEFINES used, and the steps to run
the TACL RUN command. It further explains how to run a program at low PIN and how
to determine compatibility with the SQL executor.
Topics include:

Required Access Authority

Using TACL DEFINEs on page 7-2

Entering the TACL RUN Command on page 7-3

Running a Program in the OSS Environment on page 7-3

Running a Program at a Low PIN on page 7-4

Determining Compatibility With the SQL Executor on page 7-7
Required Access Authority
To run a NonStop SQL program file, you (or the creator process, if you use a
process-creation procedure such as PROCESS_CREATE_ or NEWPROCESS) must
have the following access authority:

Read and execute authority to the SQL program file

Read authority to the catalog in which the program is registered

Read authority to any catalogs in which tables or views used by the program are
registered for SQL statements that require automatic SQL recompilation
For an embedded SQL statement (static or dynamic), to access and operate on a
database object, such as a table or view, the process started by the program must
have specific privileges associated with it. The privileges for both the process access
ID (PAID) and the group list are evaluated to determine if a process can be granted
access to a database object. The group list is always associated with the creator
access ID (CAID), which represents the user who starts the process. The PAID
depends on the PROGID setting.
If the program owner does not enable the PROGID attribute for the program file, the
PAID will be the same as the user ID of the process creator (that is, the CAID). When a
user executes the program, the process uses the privileges of the process creator and
accesses only resources to which the process creator has access.
If the program owner enables the PROGID attribute for the program file, the PAID will
be the same as the user ID of the program owner. When a user executes this program,
the process uses the privileges of the program owner and accesses only the resources
to which the program owner has access. PROGID programs enable one user to