Assigning passwords to UDS/SQL files

UDS/SQL protects files that are generated automatically by the DBH (i.e. the SLF, ALOG file, RLOG file and temporary realms) by means of a password.
In some cases such a password is not used to protect the contents of the files against unauthorized access; it is used to prevent files which are employed in various sessions from being inadvertently deleted. These files, which are protected by the unchangeable password C'UDS'BLANK'', only contain database management data.
The SLF is always protected with the default password: C’UDS'BLANK'’. The ALOG file and the temporary files are also protected with the default password C’UDS'BLANK'’, assuming that no other password was specified with the DBH load parameter PP CATPASS.

As the database administrator, you can also assign passwords to UDS/SQL files. This can be done by using the BS2000 command MODIFY-FILE-ATTRIBUTES (see the commands manuals for "BS2000 OSD/BC"). The only exception is the RLOG file. Each RLOG file is always protected with a specific UDS/SQL-internal password.

As the RLOG files are generally deleted again by the DBH when they are no longer required, you do not need to manage the password. However, if in exceptional cases an RLOG file does need to be deleted for other reasons, you can issue the password using the RLOGPASS utility routine in the UDS-SQL-T package.

The passwords for UDS/SQL files must be made known with the load parameter PP PASSWORD or the DAL command ADD PW.

The following points should be considered when assigning passwords to UDS/SQL files:

• A read password should be assigned to all UDS/SQL files as minimum protection against the access of non-UDS/SQL systems.

• Assigning a write password is recommended only where selected non-UDS/SQL read accesses are to be granted without the files forfeiting the write protection.

• Password assignment should be economical; not every file requires its own password.

• The password C’UDS'BLANK'’ and read passwords specified via PP CATPASS, PP PASSWORD or the DAL command ADD PW should not be used for other files, because UDS issues these passwords internally, so in special situations files would become accessible which users want to protect.

Special consideration must be given to the COSSD file, because it is required for COBOL compilations (COBOL85 oder COBOL2000).

If this file is to be protected, the database administrator must either

• make available to the user a compilation procedure containing the COSSD password. This procedure must itself be protected by a read and execute password, and only the execute password must be known to the user.

or

• where extreme security is required, perform compilations of COBOL-DML programs on the user’s behalf.

When passwords are assigned to the file containing the DBH load parameters, care should be taken that UDS/SQL is always granted access. UDS/SQL must have write access to the following files:
the SLF, temporary files and the DB status file.
UDS/SQL must have write access to realms and ALOG files unless their databases are run in SHARED-RETRIEVAL mode. 

Organizational measures

The following organizational measures are recommended when passwords are to be assigned to UDS/SQL files:

• Make use of BS2000 password encryption at system generation time (see the commands manuals for "BS2000 OSD/BC", ADD-PASSWORD command).

• Assign a logon password for the configuration user ID.

• Files containing passwords, such as CALL-PROCEDURE procedure files, ENTER files and files containing DBH load parameters, should be

  • protected by passwords

  • only deleted by specifying DESTROY in the DELETE-FILE command.

  Provision must be made during system generation to ensure that UDS/SQL cannot be abnormally terminated as a result of password contraventions (see the manual "Introduction to System Administration" CL2-Option):

  PWACTIVE system parameter:
  The value must be at least one more than the number of passwords which can be attached concurrently by means of PP PASSWORD and ADD PW.

  PWENTERD system parameter:
  The value must be much larger than the number of passwords. If realms are to be frequently attached and detached in the course of a session, it is advisable to use the maximum value (= default value).

  Before files are attached or detached, UDS/SQL respectively always issues and revokes all known passwords.

  PWERRORS system parameter:
  The value should be much larger than the number of UDS/SQL files protected by the same password. Otherwise just a few errors in entering the password can result in UDS/SQL tasks being abnormally terminated by BS2000 (maximum value = default value).