ODBC Server Reference Manual

Stored Procedures
HP NonStop ODBC Server Reference Manual—429151-002
5-58
Security
Security
The NonStop ODBC server issues the ServerClass_Send in such a way that the
Guardian user ID with which the client is connected participates in the call. As
described in the NonStop TS/MP Pathsend and Server Programming Manual,
LINKMON performs authorization checks to ensure that the user ID conforms to the
OWNER and SECURITY attributes configured for the server class.
The NonStop ODBC Server user ID need not exist on, nor have remote passwords for,
the node where Pathmon is, or the node containing the server class process.
Break Handling
If client sends a “break” signal, the NonStop ODBC Server terminates further
processing for a stored procedure invocation. If a PATHSEND is still outstanding, the
NonStop ODBC Server calls CANCEL to cancel the request to the Pathway server
class program. The CANCEL aborts the current transaction. The Pathway server class
program can receive the CANCEL system message or a notification that the
transaction has disappeared. The program should then issue a REPLY and end the
program.
A stored procedure that uses the shell routines can handle a break or CANCEL
message by checking reply_err for a value of 2. If reply_err is 2, the stored
procedure should perform any necessary clean-up routines and then return to its caller.
For example:
rc = encode_row_data(env,
max_len,
sdao90,
output_buffer,
reply_err);
if (rc != SPELIB_OK)
{
EXEC SQL CLOSE govtst90_cursor;
goto LIBERR;
}
/* check for cancel */
if (*reply_err == 2)
{
EXEC SQL CLOSE govtst90_cursor;
freevar_SPE_90();
return rc;
}
Sharing Procedures
One mechanism is used by the NonStop ODBC Server to support stored procedure
execution for both TSQL mode and CORE mode. The primary requirement is that
users in each mode can execute stored procedures defined for that mode (use a valid
name, obtain results, and be able to access catalog information about the procedures).