21.   The module owner is generally the person or organisation who pays for the module to be developed, although this user has no specific LIFESPAN privileges.

22.   Most LIFESPAN users have no contact with the Hard Copy system.

23.   If this occurs the user should check that there is sufficient disk quota in the specified directory and that the user has write access to the directory.

24.   To perform these checks, PI requires that the specified user has no mail in the LIFESPAN mail system on invocation.

25.   User must have access to all modules to be read prior to calling READ--COMPLETE--ROOT--PACKAGE.

26.   User must have access to root package prior to calling READ--COMPLETE--ROOT--PACKAGE.

27.   The specified user has insufficient privilege to perform LIFESPAN QA.

28.   In the case of ORACLE RDBMS a registered user must have an account created in the same instance into which LIFESPAN RDBI is transfering data.

29.   This password, known only to LIFESPAN RDBI, ensures that no unauthorised users have direct access to the database.