SQL/MP Installation and Management Guide

Managing Database Applications
HP NonStop SQL/MP Installation and Management Guide—523353-004
10-38
Manipulating Program Files
= FREEZE SERVER SRV-SDB102
= STOP SERVER SRV-SDB102
= ALTER SRV-SDB102, DEFINE =EMP , CLASS MAP, &
= FILE \SYS1.$VOL2.TEST2.EMPLOYEE
= ALTER SRV-SDB102, DEFINE =DEPT, CLASS MAP, &
= FILE \SYS1.$VOL2.TEST2.DEPT
= ALTER SRV-SDB102, DEFINE =JOB , CLASS MAP, &
= FILE \SYS1.$VOL2.TEST2.JOB
= THAW SERVER SRV-SDB102
= START SERVER SRV-SDB102
You can delete the existing DEFINEs for a server with these commands:
= FREEZE SERVER SRV-SDB102
= STOP SERVER SRV-SDB102
= ALTER SRV-SDB102, DELETE DEFINE =EMP
= ALTER SRV-SDB102, DELETE DEFINE =DEPT
= ALTER SRV-SDB102, DELETE DEFINE =JOB
= THAW SERVER SRV-SDB102
= START SERVER SRV-SDB102
After you alter DEFINEs for a server, automatic recompilation occurs every time the
server is started. For this reason, you might want to explicitly SQL compile the server
after altering DEFINEs.
You do not need to cold start the PATHMON environment when you alter the DEFINE
set for the server classes. To change the MAXDEFINES attribute, however, you must
cold start the Pathway transaction processing environment.
The PATHMON process manages the active set of DEFINEs while TS/MP is running.
DEFINEs in this environment are completely separate from DEFINEs associated with
the command interpreter process or other processes. You can alter DEFINEs outside
of the transaction processing environment without affecting the active set for your
TS/MP applications.
Manipulating Program Files
SQL program files can be manipulated just like other program files:
•
SQL programs stored in Guardian files can be objects of the FUP commands
RENAME, PURGE, and SECURE; the TACL commands RENAME and PURGE;
and the system procedures FILE_RENAME_ , FILE_PURGE_ , and SETMODE.
•
SQL programs stored in OSS files are manipulated by using OSS utilities such as
rm and mv. For more information about OSS utilities, see the Open System
Services Shell and Utilities Reference Manual.
SQL program files, unlike other SQL objects, can reside on nonaudited volumes.
SQL DDL statements that require all other dependent objects to be available, such as
DROP TABLE, can complete when a dependent program is not available if the
program’s catalog is available. If the program file is available, these DDL operations
invalidate the programs by registering the invalidation in the catalogs and program file