Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Servers
Open System Services Management and Operations Guide527191-005
4-29
Configuring a Server
b. Use the STOP FILESET Command to stop the started fileset.
4. Use the START FILESET Command to start (mount) the new or stopped fileset
assigned to the new OSS name server. This action automatically starts the new
OSS name server.
5. If your site uses the STARTOSS utility and the new OSS name server services a
new fileset, you should also add the new fileset name to the OSSINFIL file. See
OSSINFIL File on page C-19 for more information.
Other servers, such as the network services servers, do not need to be added to an
OSS configuration database. Such servers can be added to the OSS environment by
starting them. See Starting a Network Services Server on page 4-38.
Configuring a Server
How and when you configure a server depends on the type of server.
Configuring an OSS Name Server on page 4-29
Configuring the OSS Message-Queue Server on page 4-30
Configuring the OSS Sockets Local Server on page 4-30
Configuring the OSS Transport Agent Servers on page 4-31
Configuring Network Services Servers, Tools, and Applications on page 4-31
Other servers used by OSS applications require separate procedures. For more
information, see the manual appropriate for a specific server.
Configuring an OSS Name Server
You configure an OSS name server by adding or deleting an entry for it in the Enscribe
database ZOSSSERV file. Remember that a fileset cannot be managed by more than
one OSS name server; however, an OSS name server can manage more than one
fileset.
To add a new OSS name server to a configuration, follow the procedure described in
Adding a Server
on page 4-28. To remove an OSS name server from a configuration,
follow the procedure described in Removing an OSS Name Server
on page 4-49.
If the initial or default values for the attributes of a specific OSS name server are not
optimal, see the procedure described in Reconfiguring an OSS Name Server on
page 4-46. The attribute values appropriate to the best performance on a specific
system depend on factors unique to each site’s configuration and mix of applications.
Use nondefault values to tune your system only after gathering performance data,
analyzing process memory requirements, and considering the effects of a default
configuration on system overhead.