SQL/MP Reference Manual
HP NonStop SQL/MP Reference Manual—523352-013
A-28
Considerations—ALTER PROGRAM
expanded new name must be unique among objects in the network. Both program 
and new-name must have the same volume and node name.
If the program is managed by SMF, new-name must be either a virtual or direct 
name. Only the virtual name changes; the physical name on the physical volume is 
preserved.
Considerations—ALTER PROGRAM
To alter security attributes for a program or rename a program, you must be a 
generalized owner of the program file. You must also have authority to read and 
write the program file.
To rename a program, you must also have authority to read and write to the 
catalogs that describe the program and any associated objects. Renaming a 
program does not affect the validity of the program.
If the program is protected by the Safeguard security subsystem, requirements 
depend on the Safeguard protection settings. For example, if access is restricted to 
the super ID, you must be the super ID or error 199 (Disk file is Safeguard 
protected) occurs. If you are the super ID, ALTER PROGRAM executes 
successfully, but the new security attributes take effect only if Safeguard protection 
is removed from the program.
Only one DDL statement can operate on a given SQL object (or partition of an SQL 
object) at a time. An error occurs if you attempt to execute an ALTER PROGRAM 
statement while another process is executing a DDL operation on the same object. 
The specific error depends on the DDL operation involved and the phase of the 
operation at which the conflict occurs. For more information, see DDL (Data 
Definition Language) Statements on page D-20.
The security attribute information for an SQL program in a Guardian file is stored in 
the file label and in the PROGRAMS table of the catalog when the program is 
created. ALTER PROGRAM changes the information in the catalog and in the 
associated file label on disk.
These dependencies apply when you alter the program security attributes:
OWNER and 
PROGID
Specifying OWNER turns off the PROGID attribute.
OWNER and 
SECURE
A change in the ownership of a program affects the 
interpretation of the security string. The security string is 
interpreted at run time against the new owner and, if 
applicable, a new group.
If another process is using a program when the owner or 
security string is changed, the process might not be able 
to access the program after the program stops executing.
SECURE A security string must ensure that users who have write 
access also have read access.










