Starting Multiple User Mode Processing

During z/VM installation, the VMSERVS, VMSERVP, VMSERVU, and VMSERVR machines are usually set up so multiple user mode processing is automatically started for them when z/VM itself is started on your processor. If z/VM fails and is restarted, multiple user mode processing for VMSERVS, VMSERVP, VMSERVU, and VMSERVR is also restarted.

The only time you should need to start these servers is after you have explicitly stopped them (perhaps for dedicated maintenance mode activity), or if they have stopped because of a problem, or if someone at your installation has deleted the automatic logon for the server.

The instructions in Generating a File Pool and Server for defining other servers include setting up the server for automatic starting. If the instructions were followed, those servers will also be started automatically when z/VM is started. As with VMSERVS, VMSERVP, VMSERVU, and VMSERVR, the servers should need to be restarted only in special circumstances.

If you are already logged on to the server machine, and want to start multiple user mode processing, enter the FILESERV START command:

fileserv start

If you are not logged on to the server machine, do the following to start multiple user mode processing:

Log on the server machine that owns the file pool minidisks. CMS is automatically loaded in the server machine.
If you see the VM READ status notice after CMS is loaded, press ENTER. The PROFILE EXEC issues a FILESERV START command to start multiple user mode operation.
You see a series of informational messages ending with these messages:
```
DMS3060I Initialization complete
DMS3045I Ready for operator communication
```
When you see message DMS3060I you know the server is running in multiple user mode. If, instead, you receive an error message, fix the cause of the error and enter the FILESERV START command:
```
fileserv start
```
If you are not sure how to fix the problem, see z/VM: CMS and REXX/VM Messages and Codes.

The amount of time it takes the server to start varies depending on the amount of restart recovery the server must do. Restart recovery is a process during which the server looks at the log minidisks to determine whether there is any incomplete work that needs to be resolved. If there is, the server resolves the incomplete work as appropriate, then immediately starts multiple user mode processing.

Incomplete work may be recorded in the logs if the server did not end properly the last time it ran (perhaps the system failed) or if you entered a STOP IMMEDIATE operator command (see Stopping Server Processing). The file pool repository logs would record logical units of work that need to be complete and the CRR logs would record coordinated transactions (sync points) that need resynchronization processing.

For more information, see FILESERV START.
Now disconnect from the server by entering:
```
#cp disconn
```
Finally, log on the secondary user machine. The secondary user machine typically has file pool administration authority. Ensure CMS is running in that virtual machine. (The secondary user and initial administration machine for VMSERVS, VMSERVP, VMSERVU, and VMSERVR is MAINT.)
It is important for either the primary or secondary user to be logged on during multiple user operation. The server displays few messages during its operation, but those that are displayed should not be ignored. They are often early warnings of conditions that will require attention.