have selected, the remaining minimum number of servants, as specified, are started. Note that WebSphere Application Server itself does not start anything, it tells WLM to start them. WebSphere Application Server is only interested when they have all completed starting, but WLM is what controls the start up flow. If multiple Control Regions are configured at your installation, each Control Region and its servants initialize independently. This means that multiple Control Region/servant pairs can initialize concurrently. This is true of both WebSphere Application Server 6.1 and WebSphere Application Server 7. Therefore, one approach to reducing long initialization time for WebSphere Application Server 6.1 is to divide your servants among multiple Control Regions. However, in doing so, you would lose the ability to balance the workload among all your servant address spaces. You can find more information about WebSphere Application Server workload balancing options in: http://publib.boulder.ibm.com/infocenter/wasinfo/v5r1//index.jsp?topic=/com.ibm.we bsphere.zseries.doc/info/zseries/ae/crun_wlmzos.html As each servant completes initialization, the following messages are written to Syslog: BBOO0222I: WSVR0001I: Server CONTROL PROCESS t2sr00a open for e-business BBOO0020I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS T2SR00A. The Control Region does not fully initialize until all servants have signaled open for e-business. However, sometimes the Control Region initialization complete message can be written before all servants have issued their equivalent messages. This occurs when a time lag occurs between the open for e-business and BBOO0248I messages. However, regardless of the sequence in which the messages reach Syslog, the Control Region is ready for work when the following initialization-complete message is issued: BB000222I: WSVR0001I: SERVER CONTROL PROCESS t2sr00a open for e-business