Administrator's Guide


Starting, Halting, and Restarting the Server


Task Required Privilege Class
Start, halt, and restart the server System or operator

Starting the Server

To start the server, edit and run the ANRSTART job from ASAMPLIB dataset.

The parameters you must update before running this job are the following:

The following figure is a sample ANRSTART job with the job statement parameters added.



 //TIVSM     JOB (999,POK),'SERVER START',CLASS=A,MSGLEVEL=(1,1),
 // MSGCLASS=T,TIME=1440,REGION=128M
 /*JOBPARM L=9999
 //JOBLIB   DD DSN=TIVSM.LINKLIB,DISP=SHR
  //SERVER  EXEC PGM=DSMSERV,DYNAMNBR=300
 //OPT      DD DSN=TIVSM.DSMSERV.OPT,DISP=SHR
 //DSMAMENG DD DSN=TIVSM.ANRMSG(ANRMENU),DISP=SHR
 //DSK      DD DSN=TIVSM.DISKLOG,DISP=SHR
 //HLPAMENG DD DSN=TIVSM.ANRHLP(ANRHENU),DISP=SHR
 //IMAGES   DD DSN=TIVSM.SANRIMG(ADSMSERV), DISP=SHR
 //SYSPRINT DD SYSOUT=*

This job starts the server as a batch job. When the startup completes, the system console displays the following message:

ANR0993I TSM server initialization complete.

This message is followed by the server prompt. The server is now up and running.

If the server detects an invalid system date and time, the server is disabled, and expiration, migration, reclamation, and volume history deletion operations are not allowed. An error message (ANR0110E) is displayed and you may either change the system date if it is in error, or issue the ACCEPT DATE command to force the server to accept the current system date as valid. After the system date is resolved, you must issue the ENABLE SESSIONS command to re-enable the server for client sessions.

The date and time check occur when the server is started and once each hour thereafter. An invalid date is one that is:

Halting the Server

You can halt the server without warning if an unplanned operating system problem requires the server to be stopped.

When you halt the server, all processes are abruptly stopped and client sessions are canceled, even if they are not completed. Any in-progress transactions are rolled back when the server is restarted. When the server is halted, administrator activity is not possible.

If possible, halt the server only after current administrative and client node sessions have completed or canceled. To shut down the server without severely impacting administrative and client node activity with the server, you must:

  1. Disable the server to prevent new client node sessions from starting, as described in Disabling or Enabling Access to the Server.

  2. Query for session information to identify any existing administrative and client node sessions, as described in Requesting Information about Client Sessions.

  3. Notify any existing administrative and client node sessions that you plan to shut down the server. The server does not provide a network notification facility; you must use external means to notify users.

  4. Cancel any existing administrative or client node sessions, as described in Canceling a Client Session.

  5. Find out if any other processes are running, such as server migration or inventory expiration, by using the QUERY PROCESS command. If a database backup process is running, allow it to complete before halting the server. If other types of processes are running, cancel them by using the CANCEL PROCESS command.

  6. Halt the server to shut down all server operations by using the HALT command.

Note:The QUIESCE option on the HALT command is recommended only if you plan to do a database dump by using the DSMSERV DUMPDB command immediately after halting. Because TSM supports online database backup (BACKUP DB command), the DSMSERV DUMPDB command should be rarely, if ever, needed.

Restarting the Server

To start the server after it has been halted, follow the instructions in Starting the Server.

When you restart the server after it has been halted, TSM rolls back any operations that had been in process to ensure that the database remains in a consistent state.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]