新的日志管理器也使用这种文件。
db2logmgr：日志管理器。
通过日志管理器高速缓存执行的读取。
这些记录必须成功写入到队列管理器日志，以便应用程序能够正确地提交其更新。
These records must be successfully written to the queue manager log for the application to correctly commit its updates.
导航到队列管理器日志注册表项。
在选择同步还是异步写日志时，要考虑的一个重要因素就是当数据库管理器发生错误时情况会怎样。
An important factor to take into account when selecting between synchronous or asynchronous log writing is what happens when a database manager error occurs.
队列管理器日志的配置因操作系统而异。
Configuration of the queue manager log varies by operating system.
次日志文件扩展由队列管理器在主文件耗尽的情况下动态分配。
Secondary log file extents are allocated dynamically by the queue manager when the primary files are exhausted.
完全可能让数十或数百个应用程序并发执行，而不会对队列管理器日志性能造成任何负面影响。
It is possible to have tens or hundreds of applications running concurrently without any detrimental impact on queue manager log performance.
另外，建议您把队列管理器日志定位于它自己的磁盘上。
It is also recommended that you locate the queue manager log on its own disk.
该延迟可以有助于减少与写日志记录相关的数据库管理器开销。
This delay can help reduce the database manager overhead associated with writing log records.
该参数使数据库管理器调用用户出口程序来归档和检索日志。
This parameter causes the database manager to call a user exit program for archiving and retrieving logs.
在您继续之前，等待直到“扫描管理器完成操作”信息出现在事件日志中为止。
Before you continue, wait until the "Scanner Manager is FINISHED" message is displayed in the Event Log.
由于消息在传输到队列管理器之前得到加密，因此数据在内存、队列文件、日志和跟踪记录中受到保护。
Because the messages are encrypted before they are passed to the queue manager, the data is protected in memory, in the queue files, in logs, and in traces.
注：数据库管理器每次写一个事务日志。
Note: The database manager writes to transaction logs one at a time.
如果使用持久化事件或活动，一定要记得调优mq队列管理器来优化日志。
If you're using persistent events or actions, it's important to tune the MQ queue manager to optimise logging.
队列管理器错误日志——寻找关于失败连接的详细信息。
Queue manager error logs — look for details on failed connections.
这涉及在提交消息流程的消息处理的时候同步写到队列管理器日志。
This involves synchronous writes to the queue manager log at the point at which the message processing for the message flow is to be committed.
Tivoli配置管理器提供了一个控制系统来管理开发日志。
Tivoli configuration manager does offer an inventory control system to manage deployment logs.
如果您希望更改为队列管理器分配的日志文件扩展的数量，您将需要在注册表中更改这些值。
If you wish to change the number of log file extents that are allocated for the queue manager you will need to change the values in the registry.
在ha1上删除安装中的部署管理器日志目录。
Remove the deployment manager log directories from the installation on ha1.
如果您希望更改队列管理器的日志缓冲区大小，将需要在注册表中更改此值。
If you wish to change the size of the log buffer for the queue manager you will need to change the value in the registry.
如果您希望更改为队列管理器分配的日志文件扩展的数量，您将需要在qm . ini文件中更改缺省值。
If you wish to change the number of log file extents that are allocated for the queue manager you will need to change the default value in the queue manager qm.ini file.
无论队列管理器运行于哪个操作系统上，您都应该确保日志记录的性能是高效的。
Regardless of the operating system your queue manager runs on, you should ensure that the performance of logging is efficient.
部署管理器服务器已启动，且系统输出和错误日志中未记录任何异常或错误消息。
The deployment manager server starts, without any unexpected exceptions or error messages in the system output and error logs.
观察部署管理器上的日志文件和控制台上的日志文件。
Watch the logs on the deployment manager along with the logs on the console.
当数据库管理器关闭日志文件时，会归档日志文件。
Log files are archived when the database manager closes the log file.
每个日志文件扩展的大小在队列管理器创建时指定，以后不能更改，因此务必在首次定义队列管理器时就正确设置此参数。
The size of each log file extent is specified on queue manager creation and cannot be changed subsequently so it is important to get this right when first defining the queue manager.
调优MQ队列管理器的日志记录。
循环日志记录是创建队列管理器时的缺省选项。
Circular logging is the default option when creating a queue manager.
应用推荐