In the case of CSLD, steps 1-5 are synchronous.
对于CSLD，步骤1 - 5是同步的。
Disk quota Settings CSLD does not set quota for users.
磁盘配额设置CSLD不对用户设置磁盘配额。
This means that there are 5 parallel CSLD task threads.
这意味着有5个并行的CSLD任务线程。
Tracing of the CSLD task and archpro should be de-activated.
对CSLD任务和archpro的跟踪应该不激活。
JRE supported 1.3 and 1.4 - Starting 8.3 JRE is shipped with CSLD.
支持的JRE 1.3和1.4——8.3 jre随csld一起发布。
Figure 12 shows the unarchived document with the CSLD archive button.
图12显示未存档的文档以及CSLD Archive按钮。
Note that if you are using Web retrieval, CSLD jobs will not be employed.
注意，如果使用Web检索，将不会部署CSLD工作。
As discussed before, the CSLD task services all jobs in a CSLD job database.
如前所述，CSLD任务为CSLD任务数据库中的所有任务服务。
A good way to verify the parallel setup is to look at the CSLD job database.
验证并行设置的一个好方法是看CSLD任务数据库。
The threads are automatically started by the CSLD task and will run in parallel.
这些线程是由CSLD任务自动启动的，并且并行地运行。
A CSLD task thread accesses the Domino server via the Notes API and reads the data.
一个CSLD任务线程通过NotesAPI访问Domino服务器，并读取数据。
The single CSLD task thread processes all archive requests for the journal database.
一个CSLD任务线程处理对日志数据库的所有归档请求。
As long as there is just one CSLD task thread active, only one CM agent will be busy.
只要只有一个CSLD任务线程是活动的，那么就只有一个CM代理在忙。
During the archiving and retrieval process, the CSLD task modifies the Notes document.
在存档和获取过程中，CSLD任务会修改Notes文档。
CSLD would have to retrieve the same document several times, without additional benefit.
CSLD就不得不多次获取同一文档，这是没有意义的。
Users tracking (how many users, for example) CSLD does not have user tracking out of the box.
用户跟踪(比如有多少用户)CSLD本身没有提供用户跟踪功能。
Cases 1 to 4 show how the CommonStore throughput can be increased by multi-threading the CSLD task.
案例1到4展示如何通过多线程CSLD任务增加CommonStore吞吐量。
This unnecessary load also has a negative impact on overall CSLD archiving and retrieval performance.
这种不必要的负载还会对CSLD总的存档和获取性能产生负面影响。
On first look, opening a document should simply trigger the automatic creation of a CSLD retrieval job.
初看上去，打开文档应该简单地触发CSLD获取作业的自动创建。
But this will not improve performance at all because of the sequential processing done by the CSLD task!
但是这样做根本不能提高性能，因为CSLD任务是按顺序的方式进行处理的！
You can then set up four separate (single-threaded) CSLD tasks, each servicing its related job database.
那么可以设置4个单独的(单线程)CSLD任务，每个任务为它相关的任务数据库服务。
Figure 5 shows an example where the CSLD job database is located on the same server as the mail database.
图5显示一个例子，其中的CSLD作业数据库位于邮件数据库所在的服务器上。
In the sample mail template shipping with CSLD, the retrieve action is implemented similar to the archive action.
在CSLD附带的邮件模板示例中，获取动作的实现方式与存档动作相似。
As soon as the retrieval is successfully finished, the CSLD retrieval task sets its value to 99 (green diamond icon).
一旦获取操作成功完成，CSLD获取任务就会将这个属性的值设置为99(绿色菱形图标)。
After a successful archiving, the CSLD archiving task is configured to set its value to 48, corresponding to a CD icon.
在成功地存档之后，CSLD存档任务将它的值设置为48，这对应于一个CD图标。
Increasing the number of parallel CSLD tasks and particularly their internal threads, however, is not as straightforward.
然而，增加并行CSLD任务的数量，特别是增加它们内部的线程数，并不是件容易的事情。
This means that the action should be available when the message has either not yet been archived by CSLD or already retrieved.
这意味着，当消息还没有被CSLD存档时以及在存档后又获取的情况下，这个动作都应该可用。
If you have several job databases, you need to do the same analysis for each CSLD job database and sum up the parallel threads.
如果有多个任务数据库，那么需要对每个CSLD任务数据库进行相同的分析，然后总计出并行线程数。
The archive status field can be configured in the archive task profile of the CSLD configuration database, as shown in figure 2.
存档状态字段可以在CSLD配置数据库的存档任务配置文件中进行配置，如图2所示。
The purpose of these script libraries is to make the creation of CSLD jobs (archiving, retrieval, for example) as easy as possible.
这些脚本库的用途是使CSLD作业（比如存档、获取）的创建尽可能容易。
应用推荐