To start the application server in a VM/ESA system:
The SQLSTART EXEC is on the production disk, and the application server has access to it. This is the format of the SQLSTART EXEC:
>>-SQLSTART--Dbname--(server_name)----+------------+------------> '-dcssID(id)-' >-----+-----------+---+------------------+--------------------->< '-AMODE(nn)-' '-PARM(parameters)-' |
You must type the parentheses in the parameters. The parameters for the SQLSTART EXEC are:
SQLSTART DBNAME(SQLDBA) |
The DBNAME parameter must be the first or second parameter specified. For the DBNAME keyword, you can use any initial substring (such as DBNAM or DBNA).
SQLSTART DBNAME(SQLDBA) DCSSID(SAVEDSEG) |
If DCSSID is not specified, the id value from the dbname SQLDBN file on the production disk is used. If neither value is available, SQLDBA is used.
If you do not know what to specify for id, you can ask your VM system administrator. If specified, DCSSID must be the first or second parameter. You can specify ID instead of DCSSID for the keyword. No other abbreviation is valid. Refer to the DB2 Server for VM System Administration for more information about saved segments.
Refer to the DB2 Server for VM System Administration for more information about this parameter.
The initialization parameters in PARM define how the application server operates.
For example, if you intend to maintain the log and automatically archive the database, use the initialization parameter LOGMODE=A.
Because initialization parameters are optional, you can omit the PARM keyword. For example, you can start the application server to access the SQLDBA database without specifying initialization parameters:
SQLSTART DB(SQLDBA) |
Note that you cannot run the application server in a conversational monitor system (CMS) batch machine.