-START ACCEL command (Db2)

The Db2 command START ACCEL notifies the Db2 subsystem that it should use the specified accelerator servers.

Abbreviation: -STA ACCEL

On successful completion of the command, queries for the specified accelerator servers can begin to run. Db2 resets trace statistics to 0 each time that you execute the START ACCEL command.

Environment

This command can be issued from a z/OS® console, a DSN session under TSO, a DB2I panel (DB2 COMMANDS), an IMS or CICS® terminal, or a program that uses the instrumentation facility interface (IFI).

Data sharing scope: Group or member

Authorization

To execute this command, you must use a privilege set of the process that includes one of the following authorities:
  • SYSOPR authority
  • SYSCTRL authority
  • SYSADM authority

Db2 commands that are issued from a logged-on z/OS console or TSO SDSF can be checked by Db2 authorization using primary and secondary authorization IDs. Start of changeA logged-on z/OS user ID must be defined in RACF or a similar security server.End of change

Syntax

Read syntax diagramSkip visual syntax diagramSTART ACCEL(*)(, accelerator-name)ACCESS(*MAINTEXPLAINONLY)SCOPE(LOCALGROUP)MEMBER(, member-name)

Option descriptions

(accelerator-name)
The accelerator server name.
(*)
Indicates that the start command applies to all accelerator servers.
ACCESS
Specifies whether access to accelerator servers is general or restricted. Valid values are:
(*)
Allows general access; all authorized users can use the accelerator server.
(MAINT)
Allows only installation SYSADM and installation SYSOPR access to the accelerator server.
(EXPLAINONLY)
Prohibits use of the accelerator server except for SQL EXPLAIN execution. No queries will be executed by this server.
SCOPE
Specifies the scope of the command. In a non-data-sharing environment, the option is ignored. Valid values are:
(LOCAL)
Starts the accelerator server for the current member.
(GROUP)
Starts accelerator servers for the entire data sharing group.
MEMBER
Restricts the start of the identified accelerator server to specific members of the data sharing group. The default behavior is to start accelerator servers on the local member. This option is not supported in non-data sharing environments.

Usage notes

When to issue START ACCEL commands
You must issue START ACCEL when you add a new accelerator server to the SYSACCELERATORS pseudo-catalog table, or when you have modified the information in this table and issued the -STOP ACCEL command.
Specifying both SCOPE(GROUP) and MEMBER(member-name)

Start of changeIf both SCOPE(GROUP) and MEMBER(member-name) are specified, the command will be executed only on the specified member or members.End of change

You can monitor the status of a started accelerator server by running the -DISPLAY ACCEL command.

Trace information for commands issued with group scope
If this command is issued with options that specify group scope in a Db2 data sharing member, it also runs on all other active members. IFICID 090 trace records for other group members can show that the same command was issued by the SYSOPR authorization ID from the 016.TLPKN5F correlation ID, in addition to the trace records from the member where the original command was issued. See Command scope in Db2 data sharing.

Example

The following command starts all accelerator servers. 
-START ACCEL

Sample results:

Start of change
 DSNX820I ) DSNX8STA START ACCELERATOR SUCCESSFUL FOR BLINK1
 DSNX820I ) DSNX8STA START ACCELERATOR SUCCESSFUL FOR BLINK2
 DSNX820I ) DSNX8STA START ACCELERATOR SUCCESSFUL FOR BLINK3
 DSNX821I ) DSNX8STA ALL ACCELERATORS STARTED
 DSN9022I ) DSNX8CMD '-START ACCEL' NORMAL COMPLETION
End of change