HP OpenVMS Systems Documentation

Advanced Server uses its data cache for caching the security databases, in addition to client file data. To ensure a balance of cache usage, the file server periodically monitors its use of the data cache, as follows:

• Total security databases utilization
  The file server monitors the total utilization of the data cache by the security databases. If the file server detects that the utilization of the data cache for these files exceeds thirty-five percent (35%), a warning message is posted to the file server log file indicating that the current cache configuration may not be adequate for the current load imposed on the file server.
  For example:

  BlobCache Warning: Sum of Blob file control areas is 950272 bytes (45% of data cache).

  
  The condition reported by this warning message will not prevent the file server from being able to properly process requests associated with the security databases. The message (shown below) indicates that you should increase the size of the data cache.
• Individual security database utilization
  The file server monitors utilization of the data cache by individual security database files. When the database expands in size, more cache resources are required to continue operating. If the file server detects that an operation will cause a database file expansion, and that expanding the database file will cause it to utilize more than fifty percent (50%) of the data cache, error messages are recorded in the file server log, as in the following example:

  BlobCache Error: The largest single Blob file control area is 1187840 bytes (57% of data cache). BlobCache Error: The largest single Blob file control area is PWRK$LMROOT:[LANMAN.DOMAINS]DOMAIN1.

  
  In addition to recording the problem in the file server log, the software generates an operator message and raises a server alert.
  These messages indicate that the operation will prevent the file server from completing the current and future operations. In this case, you should use the Configuration Manager (ADMIN/CONFIG), as described in Section 7.2, Using the Configuration Manager, to increase the size of the data cache so that utilization of the data cache by a single database file remains under 50%. The change to the data cache size takes effect the next time you start the server.

You can use the ADMIN/ANALYZE command to monitor these warning messages and error messages, as described in Section 6.1.4.2, The Advanced Server Common Event Log.

6.2.2.4 Problems with Services

Table 6-10, Procedure for Solving Service Problems, describes how to determine the cause of a network service problem and what do to about it.

6.2.2.5 Client Connection Problems

Table 6-11, Procedure for Solving Client Connection Problems, describes how to determine the causes behind many typical client connection problems and what to do about them. For information about problems connecting to shares or specific files, see Section 6.2.2.6, Share Access Problems.

6.2.2.6 Share Access Problems

• Allowing access to users who are members of user groups that have access to the share
• Setting permissions to allow access to the share such as read access
• Setting OpenVMS file and directory protections, if the Advanced Server and OpenVMS security model is in use
• Setting the maximum connection limit to allow the required connects

Table 6-12, Procedure for Solving Share Access Problems, describes how to determine the causes behind some typical share access problems and what to do about them.

6.2.2.7 Printer Problems

Table 6-13, Procedure for Solving Printing Problems, describes how to determine the causes behind some typical printing problems and what to do about them.

6.2.2.8 User Account Problems

Table 6-14, Procedure for Solving User Account Problems, describes how to determine the causes of typical problems in user account definition and what do to about them.

If a client reports a failure to log on to the network, use the procedure described in this table.

6.2.2.9 Privileged User Problems

If users are unable to perform privileged operations, use the procedure described in Table 6-15, Procedure for Solving Problems of Privileged Users, to determine the cause of the problem and what to do about it.

6.2.2.10 Problems Connecting to the Advanced Server

6.2.2.11 License Acquisition and Validation Problems

• Client-based license from a License Server
• Server-based license from the Advanced Server system to which the client connects

A client-based license is acquired once, and thereafter it is verified during client startup. The License Server is responsible for assigning and verifying client-based licenses. Once acquired, the client-based license is presented for validation when establishing a session to any PATHWORKS server. The License Registrar on each PATHWORKS server is responsible for validating client-based licenses or assigning a server-based license, if available, when clients establish a session.

A server-based license is assigned to a client only for the duration of the client's session with the server.

Note that client-based licensing involves two distinct operations:

• Obtaining (or verifying, once initially acquired) the appropriate license from a License Server during startup
• Validating the appropriate license when establishing a session to an Advanced Server.

Clients using client-based licensing may report license acquisition (or verification) problems during startup. These problems typically result in a "LICnnnn error" being displayed on the client. Refer to the Compaq Advanced Server for OpenVMS Guide to Managing Advanced Server Licenses for more information about these messages.

All clients, whether using client-based licensing or not, may also report problems connecting to a server that could be the result of a license validation issue. Table 6-17, Procedure for Solving License Validation Problems describes how to determine the cause of license validation problems and what to do about it.