The startServer command reads the configuration
file for the specified application server and starts the server.
You do not have to use a user name and password
with the startServer command because this command launches
a server process but does not invoke an MBean method.
Avoid trouble: You can use the administrative
console to change the Java virtual machine Classpath setting or the
environment entries settings for a server. However, before making
these changes you should understand the following consequences of
making these changes:
gotcha
For more information about where to run this command, see the Using command line tools article.
Syntax
The command syntax is as follows:
startServer <server> [options]
where
server is
the name of the application server to start.
This argument is optional.
If this argument is not specified, a server is assigned based your
profile name. If you use the profile named default, the <server> argument
is set to server1. If the profile name is not default,
the <server> argument is set to the profile name.
Parameters
The following options are available
for the startServer command:
- -?
- Prints a usage statement.
- -curlib <product_library>
- Specifies the current library to use for the underlying Submit
Job (SBMJOB) CL command.
- -cpyenvvar
- Tells the startServer command to set the environment variables
that are currently defined for the application server process. The
default is to not set the currently defined environment variables.
- -help
- Prints a usage statement.
- -inllibl <library_list>
- Specifies the initial library list to use for the underlying Submit
Job (SBMJOB) CL command.
- -inlaspgrp <ASP_group>
- Specifies the initial ASP group for the underlying Submit Job
(SBMJOB) CL command.
- -jobd <product_library/job_description>
- Specifies the job description for the underlying Submit Job (SBMJOB)
CL command.
- -jobq <product_library/job_queue>
- Specifies the job queue for the underlying Submit Job (SBMJOB)
CL command.
- -nowait
- Tells the startServer command not to wait for successful
initialization of the launched server process.
- -outq <product_library/output_queue>
- Specifies the output queue for the underlying Submit Job (SBMJOB)
CL command.
- -profileName
- Defines the profile of the Application Server process in a multi-profile
installation. The -profileName option is not required for running
in a single profile environment. The default for this option is the
default profile.
- -recovery
- Specifies that the server will start in recovery mode, perform
a transactional recovery, and shut down. The server will not accept
any new transactions while it is in recovery mode. When you start
the server again, resources that were unavailable due to questionable
transactions will be available.
Use this option if a server fails
and you do not want to accept new transactions during the recovery
process.
When you invoke the
startServer command
with the
-recovery parameter and the recovery
process is unsuccessful, the following error message occurs in the
SystemErr.log and
SystemOut.log files:
CWNATV03I: Application server xxxxxx in profile xxxxxx has completed recovery. Server stopped.
The
message does not indicate that the recovery process was unsuccessful.
If you use the
-recovery parameter, check the
SystemErr.log and
SystemOut.log files
for the server that you are starting to determine if the recovery
process was successful.
- -sbs <product_library/subsystem_description>
- Specifies the subsystem to use for the underlying Submit Job (SBMJOB)
CL command.
- -trace
- Enables tracing of the native process code
that starts the application server. The trace output is written to
the was_jobname-jobuser-jobnum.log file which
is located in the profile_root/logs directory.
- -timeout <seconds>
- Specifies the waiting time before server initialization times
out and returns an error.
- -usejobd
- Specifies to use the job description from the Submit Job (SBMJOB)
process for the server when switching to the Run-As user ID.
Note: This
command does not affect the USER field of the current job description.
Usage scenario
The following examples demonstrate correct syntax:
startServer server1 (starts the server1 server for the default profile)
startServer server1 -trace (starts the server1 server for
the default profile and produces trace files under the
profile_root/logs directory)
startServer -profileName mytest (starts server mytest
configured under profile mytest)