SQL/MX 2.x Installation and Management Guide (H06.10+, J06.03+)

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—544536-007
11-12
Assigning Permissions for Running Database
Applications
In a distributed environment, when you create an SQL/MP alias name for an SQL/MP
object on a remote node, use a fully qualified SQL/MP object name. The SQL/MP
aliases must be in SQL/MX user catalogs that are visible on the nodes where the
programs exist. For information about registering catalogs to make them visible in an
SQL/MX distributed database environment, see Using Catalog References in an
SQL/MX Distributed Database on page 13-8.
You can use OBEY command files or scripts to automate the process of creating large
numbers of SQL/MP aliases for applications that you will run in the SQL/MX production
environment. Create the SQL/MP aliases before you start processing or running
applications in the production environment.
For information about SQL/MP aliases, see the SQL/MX Reference Manual.
For information on how to code SQL/MP aliases in SQL programs, see the SQL/MX
Programming Manual for C and COBOL.
Assigning Permissions for Running Database
Applications
Managing Permissions for Files in OSS Space
For SQL applications and user modules stored in OSS space, you control access to
the files with the OSS commands that manage OSS files and directories, including:
•
Displaying and setting file and directory permissions
•
Setting the user mask
•
Changing owners and groups
You use permission codes to specify the types of access that users have to your files.
You can give each of the three types of users (user/owner, group, and all others)
separate permission to read, write, or execute each of your files and directories.
Use the ls command with the -l flag to display the current file permissions for all files
and directories in the current directory.
You must be the owner of a file or directory or a SUPER.SUPER (super ID) user to
change its permission. Use the chmod command to set or change the permissions for
your files and directories.
Every time you create an OSS file or directory, the process you are running
automatically establishes a default permission code for it, so you do not need to
specify one. To further refine the default permission code, you must specify a user
mask with the umask command. The user mask is a numeric value that determines the
maximum access permissions when a file or directory is created. As a result, when you
create a file or directory, its permissions are set to what the creating program specifies,
minus what the umask value specifies.
To change the owner of a file or directory, use the chown command. To use this
command, you must have the same privileges as a SUPER.SUPER user. To change