TS/MP 2.5 System Management Manual

A System Management Scenario
You know that users are encountering difficulties with some of their workstation client applications.
The applications will not come up. By asking a few questions, you determine that RSC is running.
Investigation on the host side reveals no telecommunications outages, so the problems must be in
the PATHMON environment.
1. You use the STATUS SERVER * command to determine which server classes are currently
running.
2. You notice that no server processes are running in the server class A-NAMESERVE. You know
that this server class is required for all client applications.
You also know that all other server classes must be stopped before the A-NAMESERVE server
class can be started.
3. You decide to gracefully shut down existing applications using the FREEZE SERVER *
command.
4. You use the STATUS SERVER * command to confirm that all server classes are frozen.
The STATUS command display reveals that two server classes are still running, presumably
because they contain servers processes that are still completing long transactions. These two
server classes are named B-NAME-SERVE and CNAME- SERVE.
5. You use these two commands to attempt to freeze the two server classes:
= FREEZE SERVER B-NAME-SERVER !
= FREEZE SERVER C-NAME-SERVER !
6. You use a STOP SERVER * command to stop all server classes.
7. You use the STATUS SERVER * command again to confirm that all server classes are stopped.
Now B-NAME-SERVE and C-NAME-SERVE are stopped, as are all the other server classes.
8. You use the START SERVER command to start server class A-NAME-SERVE.
9. You use the THAW SERVER * command to thaw the other server classes, followed by another
STATUS SERVER * command to confirm that all these server classes are thawed.
10. You use the START SERVER * command, followed by another STATUS SERVER * command
to confirm that all the server classes have started.
To ensure proper maintenance of your PATHMON environment, you must monitor its performance
on a regular basis, make changes when required, and always monitor the effects of any changes
that you make.
Displaying Configuration Information
The INFO command displays global configuration information. You can display configuration
information about your overall PATHMON environment or about specific objects−the PATHMON
process and SERVER objects. You can also display information about specific messages sent to
user terminals through the TELL command.
NOTE: If your environment includes the Pathway/iTS product, you can also use INFO to display
information about TERM, TCP, and PROGRAM objects. For information about using the INFO
command with Pathway/iTS objects, see the Pathway/iTS System Management Manual.
The INFO PATHWAY Command
The INFO PATHWAY command displays configuration information about your overall PATHMON
environment:
= INFO PATHWAY
Example 3 (page 82) shows an example of the configuration information displayed when you run
the INFO PATHWAY command.
Displaying Information About a PATHMON Environment 81