类似地，使用相同的URL启动机制，类JournalEntry又让您启动了一个新条目以显示日志本身。
Similarly, the JournalEntry class also lets you launch a new entry using the same URL launching mechanisms to show the journal itself.
处于缓冲模式下时，次要服务器会暂存来自HDR 的任何日志页面数据，可以使用 onstat-gdrickpt显示日志暂存的统计数据，如下所示。
While in buffering mode, the secondary stages any log page data coming from the HDR, onstat -g dri ckpt shows the log staging statistics as shown below.
日志应该显示一个云服务类型拥有何种类型的安全问题，以及该问题是在何时和如何修复的。
The log should show what type security problem a cloud service type had and when and how the problem was fixed.
清单1中的命令帮助日志文件显示了创建、保存和启动新的业务级应用程序所需的操作集。
The command assistance log file in Listing 1 shows a set of actions necessary to create, save, and start a new business-level application.
日志应该显示应用程序处于什么状态，以及状态完成是否成功。
The log should show what state the application was in and whether completion of the state was a success.
日志结尾部分显示统计信息，包括泄漏了多少内存，使用了多少内存，以及总共分配了多少内存。
The section at the end of the log displays statistics, including how much memory was leaked, how much was used, and the total amount allocated.
显示此日志条目的集群节点认为自己不具有浮动资源。
The cluster node showing this log entry will disown the floating resource.
图3显示了带消息日志记录的请求流，图4显示了带消息日志记录的响应流。
Figure 3 shows the request flow with message logging, and Figure 4 shows the response flow with message logging.
清单1显示了在日志文件中捕获的、完成此任务所需的一些命令的示例。
Listing 1 shows a sample of some of the commands captured in a log file that are necessary to complete this task.
指定日志文件的路径，就可以看到一个慢速查询的排序后的列表，并且还显示了它们在日志文件中出现的次数。
Specify the path to the logfile, and you're given a sorted list of the slow queries, along with how many times they're found in the log.
图52显示一个关于逻辑日志的报告。
Figure 52 shows a report generated to get more information about logical logs.
通过查看清单3中显示的逻辑日志，可以看到日志位于同一位置上。
By looking at the logical logs shown in Listing 3, you can see logs are at the same position.
页面的上半部分现在有一个饼图，显示逻辑日志的已用空间、空闲空间和已备份空间使用量。
The upper half of the page now has the pie chart, breaking it up to illustrate the usage of logical log as used space, free space and backed up space.
Recommendation andactions选项卡显示达到了日志文件结转阈值，但是某个问题影响了成功的转接。
The Recommendation and actions tab shows you that the log file rollover threshold was reached, but some problem prevented successful rollover.
您可以使用WebSphereStudio来创建您自己的基于JSP或者servlet的应用程序来显示审核日志数据。
You can use WebSphere Studio to build your own JSP-based or servlet-based Web application to display audit log data.
最后，日志文件显示Chom pQ . pl在队列上成功启用了触发机制。
Finally, the log file shows that ChompQ.pl successfully enabled triggering on the queue.
消息Console显示动作的日志条目。
DB 2ContentManagerAPI日志dklog . log显示，调用RM检索文档花费了2.9秒的时间。
The DB2 Content Manager API log, dklog.log, shows that calls to RM to retrieve document is taking 2.9 seconds.
启动该流程后，系统的日志显示只有第一个行为可以执行，如图16所示。
After starting the process the system log shows that only the first activity has been executed as shown in Figure 16.
location列显示每个逻辑日志所处的位置。
The Location column indicates where each logical log resides.
图1显示了组成日志方案的高层组件，并定义了日志客户端与Web服务进行交互的两个场景。
Figure 1 shows the high-level components constituting the logging solution and defines the two basic scenarios where logging clients and web services can interact with each other.
Size列显示每个逻辑日志的大小，第四列Used 表示每个逻辑日志上已经使用的空间量。
The Size column displays the size of each logical log, and the fourth column, Used, informs the user of the amount of space filled up on each logical log.
notes列显示逻辑日志的状态。
The Notes column informs the user of the state of the logical log.
Number列显示逻辑日志的编号。
The Number column indicates the number of logical logs sequentially.
图24显示了到控制台的消息的日志记录。
清单10显示了运行这个日志版代码时输出的日志。
Listing 10 shows what the log prints when I run this logged code.
您可以使用该选项接着显示错误日志中的输出，例如，要在将错误写入到日志的同时查看这些错误。
You can use this to follow the output in an error log, for example, to see what errors are appearing as they're written to the log.
请注意关系图中没有显示外部信息，如调试日志记录等。
Note that the diagram shows no extraneous information, such as debug logging.
然后验证模型，在错误日志中显示出任何的错误或警告。
The model is then validated and any errors or warnings are shown in the error log.
图2显示了异常日志、解决和通知的总体架构。
Figure 2 shows the overall architecture for exception logging, resolution and notifications.
应用推荐